note1tdhscrduzalyr350gxr8wj6g3ty9ljkxcgyf38vxyzgx5qu9t9uq640lmh

I also noticed there are a bunch of errors in the console that show up after 30 seconds.

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'length')

at nostrgram.min.js?build=250:1:95913

at Object.success (nostrgram.min.js?build=250:1:15755)

at c (jquery.min.js:2:28327)

at Object.fireWith [as resolveWith] (jquery.min.js:2:29072)

at l (jquery.min.js:2:80045)

at XMLHttpRequest. (jquery.min.js:2:82499) #[1]

Reply to this note

Please Login to reply.

Discussion

The errors are uncatchable errors from fetching the Nip05 verification. Some hosts are blocking null CORS requests from webapps so the fetches fail. Unfortunately not much I can do about that. They should be allowing null CORS access to the nostr.json file if they want to be a Nip05 host. I'll look into the note that won't load.

Here you go. It still happens. It's not just one post. If I refresh the page I can open one of two conversations and then it starts spinning again. Let me know if there is a secret debug flag that I can enable and provide you some logs.

What's the note id of the thread you can't open?

Darn… it’s working now.

Pretty much any note. But here is an example - note19cgkdmpj4e40y3k7c5sul2ur535l7unj7sll8d478j2y52k6ydxsyw25hp