Replying to Avatar Vitor Pamplona

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..
Avatar
jb55 2y ago

There is a space after nostr:, maybe you have a bug?

Reply to this note

Please Login to reply.

Discussion

Avatar
Vitor Pamplona 2y ago

Good catch

Avatar
jb55 2y ago

I think our nip10 implementations are incompatible, I can’t read your threads right. Should switch to markers.

Avatar
Vitor Pamplona 2y ago

I gave up trying to use markers to assemble threads... It never works. :(

But I can add markers on posts to make things easier.

Avatar
jb55 2y ago

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.

Avatar
Blake 2y ago

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.

Avatar
jb55 2y ago

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.

Avatar
Kim Stock 2y ago

That’s what I’ve always liked about computers, the million ways to do the same thing.

Avatar
fiatjaf 2y ago

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

04
சாரு-秋陽 2y ago

Yes - this 😭😭