nostr:note13acnqsrhmnz6fuxdl69rycf35aa0ug58mel9u9g5feu3vkst76lqxspne5
In fact *no* changes are required!
Discussion
Snort doesn't like nsecbunker. 😟
snort doesn't like Highlight events (kind:9802)
if only there were two simple NIP PRs that would COMPLETELY fix this user experience FOREVA'
https://github.com/nostr-protocol/nips/pull/500
https://github.com/nostr-protocol/nips/pull/530
nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 👀
The final NIPs?
hahahha, I was thinking about that EXACT analogy today 🙌
Highlighter is already linking to itself there. Why not link to this highlight itself ... somehow? Or do you need the ID for that?
Yeah, exactly; a non-replaceable event can’t link to itself
The link could link to the pubkey's profile on highlighter or using a filter for the timestamp still find it reliably.
with NIP-89 none of this will be necessary, the client that doesn't know how to handle the event 9802 will simply be able to link to the right client with the right URL 😅