Oops
Discussion
š
Nice it works! This will allow us to mention users in DMs without that horrible āfailed to decryptā bug 
It will also allow you to mention users without notifying themā¦ not sure what the UX for this will be when posting though.
Will it allow us to reliably mention them by account name? Thatās the biggest pain for me on mobile, where I canāt open a second tab.
Iām gonna miss those
Does not yet show "@fiatjaf" on amethyst #[4], but the raw bech32.
Its somewhat new (nip27). Not sure why we have another mention spec but Iāve been seeing it a lot so I guess I need to implement it š¤·āāļø
Humm... It should look like below. Are you on the latest? It's either a bug or your relay list doesn't include fiatjaf kind-0 info..
There is a space after nostr:, maybe you have a bug?
Good catch
I think our nip10 implementations are incompatible, I canāt read your threads right. Should switch to markers.
I gave up trying to use markers to assemble threads... It never works. :(
But I can add markers on posts to make things easier.
Some threads donāt do positional nip10 (I think coracle) and those threads donāt load at all in damus. Will need to do another pass at my nip10 code to handle markers, long overdue.
I was wondering why more threads recently sometimes cannot load the parent events. I thought it was maybe relays or network. It knew itās he event had a parent, but just never loaded.
itās caused by damus canāt figuring out which is the event being replied to. There are multiple e references and if they are not in the correct nip10 order then it will fail to walk up the thread.
Thatās what Iāve always liked about computers, the million ways to do the same thing.
Clients should probably do positional NIP-10 too, why not? It's easy. I always saw the markers just as a nice addon. nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn