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.
verbiricha
devs are spoiled. building software like everyone has an unlimited 5G data plan and a last gen phone. if you do the opposite (build for low end, low connectivity, spotty network access) you end up with something that works for the lowest common denominator and feels ultra snappy on higher end phones and better connections.
View quoted note →
Replies (42)
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.
Nostur has that iirc
use - measure - LIMIT in os level or app - mobile data hits u get alarm
5G speed easy 20Mbps to 80Mbps - issue is SUPER EXPENSIVE
Yep! Itβs not hard to vibe together. Every mobile client should do it.
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.
Primal didn't even work for me while in the UK in a throttled connection in November.
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
Haven't tried Yakihonne yet, but might make a point to do so. I use Amethyst, which I love, but speed is certainly not its strong suit.
That's not a bad idea. I could try disabling media in Amethyst next time.
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.
both Yakihonne and Jumble are great options to try this way of browsing nostr
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.
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 know any aggregator relays.
That's cool.
It's a new relay type. It works very well. You can also add the reverse, a blaster style relay too.
aggr.nostr.land
If you have a subscription. I'm trying this out right now as my only aggregator relay.
That's something I will have to look into.
Good to know. Thank you.
sendit.nosflare.com
im sure others exist too. i have a personal one.
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.
@Vitor Pamplona 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 π
@greenart7c3 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
These are both good solutions.
I can send all profiles to Citrine as we download them. Do we want anything else there?
Unused RAM is wasted RAM π€
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
I have 32 ram and some clients that I use stop working once they exceed 1 GB
10002s
That feel when you only have access to mobile networks
Mhmh, true.
