Assessing Your Level As A Bitcoin Enthusiast
https://krisconstable.com/assessing-your-level-as-a-bitcoin-enthusiast/
I would add another level just below running a full Bitcoin node where you run a light Bitcoin node. Doesn’t take up significant space, you can run it intermittently to just sync the state of the network, and it allows you to verify your personal UTXOs without deferring to anyone else
Guten morgen! Refactored Iris version is available at https://beta.iris.to and hopefully in production soon. UI freeze bug now resolved. Most of the differences are under the hood, improving content loading and making further development easier.
It uses #[0] 's Relaypool library https://github.com/adamritter/nostr-relaypool-ts . We would like to see web client developers working together on a library that takes care of the tricky stuff like subscription management and feed aggregation.

👆 stove used by the Finnish military, heated up to the point where it's called a strawberry.
Well done, guys!
It’s a Nostr proof-of-work generator library. You just pass in an event and a target difficulty and it returns the event with a nonce tag that produces an event id with your desired difficulty. That’s all, really.
I was just experimenting with how to get the computation to be as fast as possible. It’s a little weird compared to regular PoW in that the nonce is in plaintext, not binary
nostr-pow: A little npm Node module for finding Nostr event nonces.
On my Mac mini 3.2GHz 6-Core i7 I’m getting about 10 megahashes/second. Curious to see what others are getting 🤔
We can make paid seeders with Lightning as a BitTorrent extension, but would anyone really use that?
The thing is that once you start re-jigging BitTorrent to adopt a paid incentive structure you might as well opt for a much simpler protocol altogether
BitTorrent gets a whole bunch of things right, but it’s core fault (which I think is just an unfortunate case of its design predating cryptocurrencies) is that it doesn’t distinguish people who want to consume from people who want to provide.
This is something that Nostr gets right, and why it’s got a better chance of scaling vs scuttlebutt. There are people who run relays and there are people who use clients. And it’s possible economically because relay operators can charge for the service they provide.
For the BitTorrent network to be healthy users must try to balance what they take from the network by giving back to the network. This is hardly ever the case, so you end up with leeches on one side ruining the network, and lawful users who suffer for their good will.
If you can incorporate a currency to bridge the gap between consumers and providers you have yourself a much healthier system.
I still use it for undo and I hate it
Incognito DMs, let’s go!
After a week of back and forth between #[0] and I we have fine-tuned and finished a first draft for NIP-32 incognito DMs.
I have created a PR for the NIP to open up our idea to discussion and feedback. We will be publishing a reference client implementation for the NIP later this week, forked from #[1] ’s Hamstr client.
#[0] Not exactly sure what you meant regarding separating the testing and code and tlv parsing into their own functions, but for now I’ve moved all the code out to a separate file to clean things up.
This sounds very promising! Where does your client host the content?
Let me show you what I'm currently working on -
It's a monetization mechanism for everyone that allows you to easily put any content behind a paywall in just two clicks. (Only Bitcoin/Sat as payments)
Whether it's a blog, art, or videos, it enables you to monetize almost everything.
Paywall demo: https://zapforart.site/paywall/JThv2DqrRC8TzKR3nVWnpZ


Nice nostrage! Defo worth 10 sats
Damn, Firefox debug tools look great
Is there anything in particular I should do to reproduce this? Is it when scrolling? DMing? Any insights you have could help get the ball rolling
Sounds cool. What do you want to use this for?
Cleaned it up a bunch to leave the Swift portion of the codebase as simple as possible. Added the commit to the PR!
Created a PR on Damus to start extending support for NIP-27 (#[0], arthurfrance, #[1])
It adds the necessary parsing code to detect nostr: bech32 entities and represent them as regular mentions. nostr:naddr and nostr:nrelay get parsed but don’t have any special UI as of yet.
With this functionality, DMs are one step away from not leaking mentions any longer. Instead of converting mentions to #[idx] they could be converted to nostr:npub… and not added to the tags field.
Any feedback is welcomed!
https://github.com/damus-io/damus/pull/837
#[2] 
For the moment I’ve left the Mention object intact and have added a MentionBech32 that represents all the different Bech32 entities, but it might be easier to turn all inline mentions into Mention blocks without an index for now. Depends on how you feel about it. Don’t want to add too much complexity to your codebase :)
Yeah I think clients should pick a default for now and worry about that later. But at the very least it will improve the privacy of DMs

