Wish list for low data client:
iOS
Hacker news style
Performance over everything else
Super Low data usage
Absolute minimum features, read notes, reply, react
Don’t need any profile info, followe counts, reaction counts, translations, optional image loading.
lynx. You’ve described lynx. 😉
What’s lynx? An iOS app?
It’s a text-only web browser from the 90s!
oddbean.com but iOS and based on your npub?
I’ve been working on a nostr over ham radio client and server. The data has to be very low. Images are going to be optional, but compressed to about 250px.
5 to 10 notes at a time download, signed messages, emojis, replies. Optional preload avatars, and other data, saved in do for offline use.
Notes stripped to barebones as possible.
Long term goal would be zaps.
No need for avatars. Don’t even care about emojis not reactions really. Nice to have but not necessary. Read and write is all I really want on the shittiest of shitty connections 😂
Unfortunately, since I'm using data radio, I have to use Linux or windows server that can interface with the radio.
When I'm done, there may be an easy way to port, not sure.
I'm working with 300 baud rates, slower than even the slowest connections!
Yeah, why is Damus @ 9gb on my phone?
I think you get this with an embedded relay, using a single caching relay, some updated queries for relays, and lots of optimization.
Supporting Negentropy is necessary for low data mode
I don’t know what that is
A protocol that reduces data usage on Nostr. strfry implements it. No clients implement it yet.
There was one client that claimed it was low data usage.
I don’t remember the name.
Nostur has a lot data mode. No images, etc.
A lot of data mode :p I know you meant low but that came out funny
One of the first things I did when I heard of nostr was experiment with a protobuf mapping to reduce bandwidth. @jb55 later gave me the helpful hint that strfry already maps to flat buffers internally (afair). So that may be the easiest way to go. Just modifying a strfry to serve flat buffers.
I wonder if zapthreads (web component) could be used to create such an experience if connected to just one proxy/cache relay. It's quite minimal (~40kb compressed), few features, offline first and does not make unnecessary queries
I don’t know. That’s for the dev wizards to figure out 😆
This is one of the potential routes for my Swift client Seer. I’ve always wanted something super lightweight. It’s either gonna be this or nip29 client. I’ll decide after turkey day.
Oddbean new post about login | logout