Testing nip19 in damus nostr: nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gpp4mhxue69uhhytnc9e3k7mgpz4mhxue69uhkg6nzv9ejuumpv34kytnrdaksjlyr9p

Reply to this note

Please Login to reply.

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 messages from #[3]​ 😅

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

Yes - this 😭😭

Not working for me.

Hey Will, the ssl cert for your nip-05 expired. You’re probably aware, but I wanted to give you a heads up just in case!

This is great news: nostr:nevent1qqspvq9wuprstmfejnc62nf7cmnq9q2hhhs2xl0anx7pdxwp9kpqmlcsu4h8u

Hopefully soon we can bury NIP-08 and keep just NIP-27 for everybody.