What is up with NOSTR lately? I'm not getting all the notes I'm supposed to be seeing, including some of my own replies, and it's not isolated to one client (appears to be both Damus and Primal; Primal is usually my go-to to find if something is off in Damus). But lately I'm getting most complete results on Yaki and Jumble. I don't expect a helpful response, as these things are highly individual, and I suspect the answer is just "something is up with your relays," which won't help since as far as I can tell they're the same across clients and haven't changed in a while. I blame Divine though...I think using it did something.

Replies (110)

Jim Smij's avatar
Jim Smij 1 week ago
i feel it. I just moved from #wisp dark back to #amythest. wait a few versions, move back or others to try too.
Also, I’m almost certain the note issue is relay related and not damus because I fixed that when I started running relay.tools 🤷‍♀️
Cheese has been online this whole time, just fumbling around with his settings trying to reply 🤭
This what I have. Let's drop it though, nothing will fix it, of that I'm certain certain: image
try adding wss://relay.mleku.dev/ just for funsies i don't remember when it started happening, lots of outbox clients out there now, but it gets pretty busy on my relay too.
I had your other one sometime back, that you whitelisted me on, but then I think you removed me so I dropped it. I'll try this one. Right now though, it appears to be a combination of kind 1111 issues, and likely hidden relay mismatch stuff (prob divines fault). That's my intuition. Fairly sure about the 1111 stuff being part of problem, as I have examples I shared with someone that sorta confirmed it
If you go to hodlbods profile, and check his replies, you will not see anything earlier than 1 or 5 days. Even though he posted under an hour ago (a reply). It's kind 1111, someone told me. I got a notification for it on primal, but can't click into it. Then I checked all 4 clients and it wasn't there. THEN I restarted phone and it was still not there, except for Nostur, where it now shows up (WTF) I am told it won't show on primal or Damus as they're "legacy clients" currently. That's just one thing going on. The other is more slippery and I can't replicate it consistently, and I'm getting g angry just thinking about it
Seems I'm the only one in this hellthread who is bothered! Just did some dishes and threw sheets in washer.
yeah it's wide open now, no filtering. has been for some time i gave up on that shit for now. also is not terrible on mobile, if your device is moderately recent - like my 2025 pixel, it runs pretty sweet. some quirks still in the mobile post writing views on threads and main feed views. i've almost got most of the bugs ironed out of the one i was running at https://smesh.lol now, clanker is grinding away at the last pieces, completing the fully complete upgraded compiler/language spec and all the tests seem to be green so far, in the final straight now. it's way faster and much better layout design and once it's working i can flesh out a few more features to support things that have become common since then. pretty sure it already supports 1111 reply events already, has a pretty dang decent markdown renderer for longforms. the marmot DM support is in there too but not quite complete. i'm not gonna spend hella time on making this app shiny for current use but i miss having it especially on mobile, so smooth and fast. the app is 100% wasm, no virtual DOM, everything walks the real DOM tree and inserts and removes things. also, because of apple - i assume you run iOS device, it has to have a built-in signer because most mobile browsers don't support extensions, but it's safe to run it, the signer is an independent wasm module that has linear memory that can't be inspected by anything running in it. and on top of that, it doesn't allow loading *any* external content - youtubes are just thumbs with a play button, no embeds of any kind anyway. idk for what reason but nobody in web dev has built a pure wasm UI before. probably because each wasm module is single threaded and most programming languages make cross-thread communications hard. moxie is *designed* for cross-thread communication, it's the only way it can do parallelism. so, there is a stack of workers that check signatures, a stack of relay clients in the relay proxy, and the relay proxy itself is actually built out of mostly the same code that the actual relay runs. one codebase, all the things. you'll see, anyway. if anyone would sponsor me to build these things i could show y'alls how it's done. i still will, just not so fast because moxie and iskra are my main mission. building a decent nostr client only extends so far as my own personal use.
Yeah it's possible for anyone to log in to anyone else's profile but you can't see what you can't see XD Which is the issue of nostr, tree falls in the forest...
I knew that's what you meant, but if when logged in as me, I tell you "go to xxx profile, and tell me if you see it load fully or not," you could get a good idea, right? I suspect my relays are messed up slightly, maybe from signing into divine, but in a way that doesn't display in my clients. Type 0 events? I dunno. I get your point in general
the root cause is nip22. ttis notion that threaded comments need to be a different kind, introducing different event reference tags, dramatically complicatos one of tte most complex tasks a client has to do.
It seems to be working better today, though Damus client specifically now was giving me issues. For instance, when I went to your profile, I saw only a really old note. Crashed it, and now when I go they seem to all show up. I think we can write this off as a mystery of nostr and leave it at that. Stuffs ok for now imo...
Just the past couple! And here and there in the past. Sorry.. Things seem better today. I'll check this out later, but of a busy morning today! Thanks
Not to worry, Will is gonna get right on the Damus updates and Users will be sorted come 2038. It will be in his pet project which nobody but Derek uses, next week.
Sound pretty dumb to upgrade a decentralized protocol core standard without making it backwards compatible. Though i don´t know why did they upgrade or why it isn't compatible.. I might research later.
↑