I feel like this has been done, but has anyone named a nostr client something like "Nosferatu"? If not I call dibs on "Nosbooratu"

IndexedDB actually isn't that bad once you get used to it...

#primal doesn't create events with nip-92 metadata? #asknostr

Is anyone else slightly annoyed that we have this rich structured format and NIP-92 uses space separation in strings? I don't really have a better solution but this is fugly.

When sharing a nostr link, most (all?) services won't generate a useful preview for js based clients like coracle or iris (I believe they look at the open graph meta tags in the html result), but I think I remember there was one service that would do server side rendering for your note, had decent previews, and had links to open the note in other clients. Anyone know what I'm talking about? #asknostr

#test another test > it didn't work the first time

#test test2

#test This is a test

Why doesn't NIP-96 have the authorization event commit to the upload hash? It *seems* like it should, but I guess it's not *necessary* because of https? It would actually be cool to not require https, since https (effectively) implies reliance on centralized CAs and DNS.

Now seems like a particularly bad time to release the #nostr software I was working on this past week, it'd just add to the fAr rIgHt fire. On the other hand, no such thing as bad publicity?

The bot problem on twitter is incredibly funny when you're having a technical discussion.

Presumably relays can set limits on number and complexity of filters and subscriptions, do any implementations do this currently? How do they handle this? I gave the nips repo a brief look and didn't see anything, but I wasn't very thorough. In particular, I want to subscribe to a set of pubkeys of interest, is there a practical limit to that set size? What happens if I hit that limit? #asknostr