hodlbod

> Given this, does a single adversarial relay, or relay + client combo undo this NIP's stated benefit? No, because it will still work for anyone who cares enough to...

Coracle now supports this for marking notifications as read. I currently use NIP 59 to wrap the events. If the user's signer doesn't support NIP 44 I fall back to...

> Is this implemented anywhere? Coracle uses it for keeping track of notifications that have been seen. I'm still trying to decide if it's a good idea, because small bugs...

> simply stores the .created_at of the newest post This is what I used to do, and it might be the better option. We should specify where to store this...

Yeah, we could also break it down pretty granularly with canonical names, e.g. `mentions_last_checked` but there would probably always be views that departed from our expectations 🤔

> nostr dads 😆 The "generic triples" thing was discussed [here](https://github.com/nostr-protocol/nips/pull/878). The argument against was summarized well by @vitorpamplona [here](https://github.com/nostr-protocol/nips/pull/878#issuecomment-1810597033) — generic key/value data is a One Ring to confuse...

> Why not just take OpenStreetMaps's schema and use that as the Nostr schema then? Because I assume the reason there are multiple schemas that do the same thing is...

The consensus seems to be that this widens the scope of the protocol too much, and is a bad idea anyway. Maybe an external repository could be created with standards...

> Could clients reliably implement this by just visually appending the content of annotations to the bottom of the original post? That's how I would do it, maybe after a...

Agreed, just updated the NIP text.