I support Israel 🇮🇱.

Depends on the client, here's what it looks like on the new nostr.watch

I am approaching the problem from a very different perspective; instead of building a superapp I’m betting on making the protocol incredibly interoperable; the superapp route was always going to be possible but I think it ultimately undermines the whole point of nostr.

What I want is a flourishing ecosystem of apps that tightly integrate with each other without ever having to know of each other; there’s a reason I wrote NIP-31 (display unhandled events), NIP-89 (handle unknown events), NIP-90 (DVMs), NIP-60 (interoperable wallets)

I didn’t continue the work on Honeypot at the expense of Olas; I am finishing that work BECAUSE Olas, and Highlighter REQUIRE it.

Maybe I’m completely wrong but I think an extremely composable ecosystem is the only way that this can possibly ever work in the long run; much like outbox (or something like it) is required for nostr to work in the long run.

wss://relay.jellyfish.land is the first relay ever to use the banner  property in its NIP-11.

Reply guy

Strfry does this, please use that if you prefer the plugin model

This optimizes for simplicity

why developing a whole relay for one specific feature? when they can be designed to accept plugins or add-ons. this model make it hard ro scale these relays...

Finished the countryside. What do you think?

people say this was the birth of the internet. except the http protocol was released on the existing internet over the gopher protocol 🤷 nostr:note17hayhhacu3vh9qt665kvp5f9lrzulg703rt3kcuqgs9l06n504xsgzpv4k

Gaddafi would have been the first to buy bitcoin for his country if they hadn’t killed him