#Primal on android consumes A LOT of data, much more than #amethyst (that still consumes a lot).
I think that's because Primal "preload" much content from the feeds, so then can offer a smoother experience when scrolling.
I think that it needs to be:
- capped a bit
- better cached, it always receive GBs of data everytime you open the app...
Also for amethyst and all the other nostr client tested needs to be find a solution to have an effective "low data mode".
low data mode could be provided by a relay that forwards requests and a client that has a "low data mode" relay setting that designates a primary and backup low data relay that does this fetch-proxying for you
also if there was some kind of synchrony between relay and client, like, client could send a unique id with its reqs and the relay would not resend events it has sent previously - this requires the client to also follow some kind of common rule set about when to evict events from its cache
and need to be thinked a real and effective "low data mode" solution.
Hilariously sad state of mobile nostr. Still no caching after 2 years of work.
hey, I tried voyage, really cool approach! What confuses me is the lack of name on top of notes (I would expected it next to the "badge"). I dont know if is intentional, but I cant understand whats happening on screen 😅
