I second this, and quoting the note via Primal that will definitely show up as reply to nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s when I view it on Damus.

nostr:note1znsa6mags7uzk2srmeylrn022gjhkyerf2nvy2rtzkhy459d5nhsmtr8kn

Reply to this note

Please Login to reply.

Discussion

Yup. 👍

vitor says no so I guess we can’t fix this. i forgot he runs the show over there now

I’ve documented this Damus implementation as DIP-02 since the nips repo is borderline useless these days

https://github.com/damus-io/dips/blob/master/02.md

Is this sorta what @⁣⁤mikedilger was upset about? Inconsistency within the NIP implementation, among other things? ⁤⁣

This proposed change breaks almost nothing and is relatively harmless, if its not merged its not the end of the world, i will just filter out mention markers like other clients and take the bandwidth hit.

This is terrible

He didn’t say no. I think you already have consensus. nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn reopened the PR.

nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z C’mon dude, we gotta fix this thing. Do it for the plebs.

I can fix this up on the damus side even though it feels like im just bandaid patching a huge issue

You just described all of Nostr.

The NIP update is merged. Long live q

Here’s to band-aid solutions!

it's all good then👍

I tried. Now it's with everybody else.

🙄