Nostr clients need to get serious about efficient bandwidth usage, specially on mobile. Caching as much as possible, only requesting new data, using the outbox model to minimize open WebSocket connections... Ideally built into SDKs or libraries like nostrdb so the average dev doesn't need to worry about it and efforts are not duplicated. This is no easy task and it takes a lot of careful engineering work but it's fundamental if we want the world to be able to use the protocol. It's easy to churn out new features or implement NIPs but building solid foundations is way more important.
Discussion
Yes, but how about having request/response API in relays? Streaming API are naturally data consuming.
Faxx 🪄
Yes 💯
Highly recommend engineers make a trip to a beautiful developing country beach with 3G only and work from there till it improves.
Nothing beats real world.
nostr:note1qqqqve7fvjec5535xu5klgznrcufzgjfpcfgjlgzh2wag5fq2gss68w2d6
Also deprecate/adjust some nips. Kind 1 being post and reply is not bandwidth efficient for clients that allow displaying only one of these types.
And nip10 makes efficient reply querying impossible.
100%
fuck mobile users - they are faggots
I agree, nostr should by default work well over a bad connection, like a minimal Tor-connection. Things like profiles, names ( instead of npubs), avatar pics should just display (maybe by caching this on device). If that means (further) limiting Max follows, name size, avatar size etc. for this to work, so be it. Arbitrary limitations are necessary anyway, otherwise all implementations will vary to wildly to be interoperable
Like Secure Scuttlebutt?
Had/having huge probs too with these sorts of issues. Even maxing no. connections still has my timelines bouncing around (by as much as a week at a time) ... Impossible to maintain convo's/threads of thoughts, without referencing earlier notes, etc.