What?! No way. Client side all the way. We’ve barely started to optimize all that we could on the client. Server rendering is a relic of the past.
Would like to see more nostr clients fetching/rendering server side, would significantly improve UX
https://oddbean.com/ comes to mind
Maybe then have a Nostr Police extension that verifies events after rendered, pulls from random relays, etc
Optimistic UX pattern
Probably worth experimenting with
Discussion
what about for bandwidth/load time optimization we add a "don't send me these event IDs" field tho
i don't think that's server side at all, that's just "i already got these" you wouldn't believe how many times nostr relays send the same events over and over again even when the client has cached them
That's a good point but would make REQs huge, no?
not with bloom filters, and they aren't that expensive to compute... you could make both options, most clients don't have to process the hex IDs they have them verbatim so it's only a memory cost, and a small bandwidth cost... average events are around 700bytes, so 32 bytes to avoid 700bytes is still worth it, also if the event type is a list, in some cases that can be an extraordinary saving
also, some reqs are already huge, only outdone by follow lists
But sometimes its nice if someone starts prepping your meal before you sit down for dinner.
Time is more scarce than bitcoin!
Sounds controversial but would be cool to experiment with it. Client side at the moment, and especially on nostr, is quite terrible - particularly on websites. Sure I hope it gets better
I say this as a local-first maxi. Typically not an issue with apps after first load, but I find websites suck at keeping good caches (even nostrudel with nostr-relay-tray struggles). Every time I come back it's spinners everywhere.
Yup. I think all our sites are just super naive still. I know mine are. We’ll get there.