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
Login to reply
Replies (1)
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.

Smesh
A user-friendly Nostr client for exploring relay feeds