Just want to make sure you saw this thread nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s as it still seems to be an issue on the latest build
Discussion
That note loads for me
Loads for me without damus relay as well
🤷‍♂️ 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.
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.
I can at least reproduce it on your account… so i can look into it
Thank you! Let me know if I can help test anything.
Any luck figuring this out? Would love to try the new TestFlight builds but still can’t load this conversation on latest.
No but thx for reminding me
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!
My laziness prevails once again
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
