I just started to use some Nostr client with my shared 5G data from my phone. It already consumed more than 1gb, that's so huge. Even if I have 140gb per month, that's only 4 to 5 gb per day. I need to be constantly connected over WiFi at home to preserve my monthly bandwidth. It's maybe the time to start containerizing some Nostr web client with Firefox over kasm ? Anyone interested ? I suppose that displaying Nostr events will consume less bandwidth than downloading them.
Discussion
Mozilla Firefox could be started over tor and with nos2x-fox already installed.
When you say NOSTR client, are you referring to twitter style clients such as primal or damus, or are you referring to clients such as zap.stream which you would expect to consume large amounts of bandwidth.
If twitter style clients are consuming this amount of bandwidth, how does this compare to centralised platforms such as twitter, instagram, facebook etc...?
Yes I'm speaking about Damus, Primal, Nostrudel, Snort, etc. The classical web client without any integrations of livestreams or something else. I think (but I may be wrong) the "note system" is more heavy regarding file downloads during a normal feed use. It already was a subject few months ago with Amethyst that was consuming a lot of network bandwidth on phone but it seems it's not an application issue, it's more a Nostr by-design behavior. I will do the test with kasm and I should be able to compare both use.
It would be nice to have a data saving option in the clients, who block the images and videos and you have to click to see it