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
