Nostr Web Client

I tried Amethyst and Hamstr and the note loads normally on there. Will keep investigating…

Ok - it’s something related to 1.6 builds of Damus. The note loads normally using same relay set on 1.5 (8) version.

The note is a2d6c8aa963d45e8d2ead125c971cbdc1115f698af0b63a7bd171da4def9fd1f and even if I try searching for it directly on 1.6 (10) using my current relay set it says note not found. I dumped the REQ and copy pasted it in to a websocket with filter.nostr.wine and the note is there.

Oddly, if I add damus relay to my relay set, the note is found in 1.6.x, but not without the Damus relay even though the note is present on filter.nostr.wine.

nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s any chance this is cache/nostrdb related?

Reply to this note

Please Login to reply.

Discussion

Mazin 2y ago

I have improved feedback. It loads normally on 1.6.7 but does not load on 1.6.8 or newer with same relay set.

Mazin 2y ago

Just want to make sure you saw this thread nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s as it still seems to be an issue on the latest build

jb55 2y ago

That note loads for me

jb55 2y ago

Loads for me without damus relay as well

Mazin 2y ago

🤷‍♂️ not sure what the cause is/which relays/notes are affected and why unfortunately. All I know is that it loads for me with my relay set on every Damus version up to 1.6.7, as well as on all current versions of Snort, Amethyst, Hamstr, and Plebstr but not on Damus 1.6.8 or later.

Mazin 2y ago

What is the best/easiest way I can log the responses Damus is getting from relays? I can try to get you a better explanation of what’s happening.

Mazin 2y ago

https://nostr.build/av/6c0011deec4a63c396de375aa1a98158f05d9979485294c58c9fc5760f682fd6.mov

jb55 2y ago

I can at least reproduce it on your account… so i can look into it

Mazin 2y ago

Thank you! Let me know if I can help test anything.

Mazin 2y ago

Any luck figuring this out? Would love to try the new TestFlight builds but still can’t load this conversation on latest.

jb55 2y ago

No but thx for reminding me

Mazin 2y ago

Alright, I became a swift dev for the day because this was driving me crazy and the working test flight builds have expired. Our default json dump was escaping non ascii characters in content. ndb_builder_make_json_str fails as a result. We updated filter.nostr.wine to use UTF-8 instead to align with the NIP.

nostr:npub1t3ggcd843pnwcu6p4tcsesd02t5jx2aelpvusypu5hk0925nhauqjjl5g4 - tl;dr the issue is fixed!

jb55 2y ago

My laziness prevails once again

Mazin 2y ago

You win this round. I suppose everyone else uses standard json parsers so thats why I wasn’t able to reproduce it anywhere.

While I’m at it I’m looking at the tld parser for RelayPicView because it does not work with filter. Then again, we should really be serving favicon.ico at the subdomain level since there may be several different relays running on one domain. I’m assuming you did this because relay.damus.io/favicon.ico doesn’t resolve but I think keeping the subdomain is more compatible.

That way we can just use URL(string: relay) and https:// + url.host + favicon.ico

jack 2y ago

Original doesn’t load for me

Sasha 2y ago

It does for me. Maybe I can help.

formatting doesn’t load normally for me.

nobody 2y ago

these are all corpse eaters; limit physical-contact with their corrupted beings