Using Nostr on a throttled mobile connection while traveling internationally often means I don't use Nostr unless I'm on WiFi. Most apps just don't work well, making dozens of network connections and attempting to download massive images or videos. This is a problem.
Discussion
Need text only mode and low bandwidth mode. I added both of these on x21.social and they work well - but, everyone wants native clients π
Use in these cases voyage
Fast, simple, reliable and amber login
I'm just about to look at memory usage on Plume, it's ridiculous.
use - measure - LIMIT in os level or app - mobile data hits u get alarm
5G speed easy 20Mbps to 80Mbps - issue is SUPER EXPENSIVE
Yip Amethyst is a great example always on wifi and try not to tuch it outside the zones π€£π
We're stuck in a mental model centered around those wanting to see everything from everybody we follow, which results in all those connections. I think we need to explore other ways of using relays. I want the option to select one relay for my Bitcoin stuff, one for my human rights group, and "visit" each one. One connection to one relay... it's fine if I miss posts to other relays. I have no interest in crochet, so I don't need to make a connection and download posts from nostr.crochet just because one person I'm following posted there one time.
have you tried browsing relays on yakihonne? that experience you're describing already exists, but I think it has a lot of room to improve
nostr:nprofile1qqs9xtvrphl7p8qnua0gk9zusft33lqjkqqr7cwkr6g8wusu0lle8jcpzamhxue69uhkummnw3ezuurpwfjhgmeww3hhwmsprpmhxue69uhhqun9d45h2mfwwpexjmtpdshxuet5cfkclk 's caching server is a HUGE data saver for me, but if that's not enough then Voyage by nostr:nprofile1qqswgvmv65ja7706f5a0xe8ajcqdfvgdeeppt2jvx0kh06sggg6ykyqpp4mhxue69uhkummn9ekx7mqpr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqceeen8 is probably what you need.
Primal didn't even work for me while in the UK in a throttled connection in November.
Maybe they already started blocking Nostr?
I mean, it's the UK, I expect anything π
Not sure Voyage is still maintained... But worth a try. Very fast, caching everything, and no media DL.
we joke lol but it's also entirely a possibility that will be attempted some day. thankfully, it won't be easy. they could block some relays, but i can just use other ones and/or turn on tor.
Same feeling. I just don't use Nostr on the road.
Asknostr.site doesn't have this issue. This is an area where the server/client model shines
I've only been talking about this for nearly the whole time I've been on nostr.
π
So yeah. Nostr suuuucks on bad networks and it doesn't have to.
It won't ever be as efficient as centralized CDNs blasting cached content from local mirrors on big pipes, but it must be made more efficient to reach the people that really need to use it.
The new amethyst lets you set an aggregator relay to read from and disable outbox and the 1000 relay connections it causes.
I don't know any aggregator relays.
That's cool.
relaytools-android is pretty good at using smol data. It has images off by default (including PFPs) and only connects to a couple of relays. Lots of caching too.
It is very snappy. I'm liking it for coagulating reactions to notes!
just a little over 3 years ago, i used 10GB of mobile data the first 5 days of january. i don't think much as changed since then.
I don't is amethyst much anymore, so... My data usage is way down.
Caching efficiency would help a ton. IMO. In don't know why clients can't use an on-device nostr DB to preferentially pull common data from. I shouldn't have to have every client on a device have a separate copy of my follow list's latest pfp. For example.
Yes, caching is a big one. nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpz9mhxue69uhkummnw3ezuamfdejj7qghwaehxw309amxjar0wghxummnw3erztnrdakj7qgswaehxw309ahx7um5wghx6mmd9ud62lxp may be working on this?
That was the point of Citrine (a single cache for all apps), but it never really panned out. We realized each app needs different things, and if everybody just put everything into one db that db becomes way too large (60GB) that is impossible to manage.
We need to figure out a way that apps can tell this central database to delete stuff that they are not using anymore. Which means that the DB needs to track which information is useful for which app and that alone might make the DB even larger.
Hard problems to solve.
On Amethyst, it all depends if the app is getting killed all the time or not. If it stays in memory, the use of data is not that big.
And it should stay in memory. But some people love killing the app and reloading everything.
Citrine works well for text, but we still need local profile caching. Or perhaps we need am easy way for Citrine to crawl your contacts and sync their profile data π nostr:nprofile1qqs827g8dkd07zjvlhh60csytujgd3l9mz7x807xk3fewge7rwlukxgppemhxue69uhkummn9ekx7mp0qydhwumn8ghj7argv4nx7un9wd6zumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezumrpdejz7d9xcpk thoughts?
For profiles I could build something, maybe just get your contacts and sync their profiles.
In amethyst it could also send the profiles to the local relay if the user has a local relay.
Maybe a wot relay option in citrine could work of we just use a small set of kinds
seeing how some clients become saturated by everything they download at once, I don't know if a solution could be that instead of trying to download everything at once, download things sequentially? download a small number of events first and let them be the ones you will see first and once those events are not on the screen, delete them and load the following ones to avoid overloading the RAM of the devices. because I see that many clients reach a point where they exceed GB of space
That feel when you only have access to mobile networks
Mhmh, true.