Subnostr

nostr:note13acnqsrhmnz6fuxdl69rycf35aa0ug58mel9u9g5feu3vkst76lqxspne5

In fact *no* changes are required!

Snort doesn't like nsecbunker. 😟

Please Login to reply.

snort doesn't like Highlight events (kind:9802)

if only there were two simple NIP PRs that would COMPLETELY fix this user experience FOREVA'

The final NIPs?

hahahha, I was thinking about that EXACT analogy today 🙌

For new content types, (books, podcasts, etc) should developers create new event kinds, or rely on on #d tags in lists?

I think these things should use a `c` tag that describes the category, but this is far from the consensus view

I think showing the internals of an event when you don't understand it is a feature.

For us, but for 99% of people this looks broken

Nip 31 fixes this