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.

Reply to this note

Please Login to reply.

Discussion

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.

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

These are both good solutions.

I can send all profiles to Citrine as we download them. Do we want anything else there?

10002s