#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

# Test Also a test ========== ``` this is a test ``` *this is also a test* plus **this is a test** _yet another test_ [definitely a test](https://coracle.social) > finally, this is a test as well

@ hodlbod did you ever consider inverse labels for NIP-32? Something like ['L', '#t'], ['l', '-sfw-photography', '#t'] to remove an event from a hypothetical #sfw-photography hashtag I have a couple of use cases but moderation is probably the primary one.

Why do nostr events carry their own id? It's derived from the rest of the event, isn't it? That's 72 wasted bytes on every event as far as I can tell, which isn't *that* much, but I don't understand why it's there at all.

Bluacle? I kinda like it tbh (I didn't change all of the colors so some of the contrasts are weird)