Thread

Zero-JS Hypermedia Browser

Relays: 5
Replies: 16
Generated: 10:21:14
Looks like I'm gonna have to stop using NOSTR. It seems that in the last month or so (roughly since I started actively posting from my travels) NOSTR has eaten up so much data that it's financially unsustainable for me. I only operate on local 4G SIM cards when I travel and don't have access to public wifi very often - I'm not a digital nomad going from coffee shop to coffee shop and coworking space to coworking space, 95% of my time is spent somewhere in the woods or desert. I'm terribly sorry about this, as NOSTR is my favorite platform and if I had any real enthusiasm for growth anywhere, it was here (unlike Twitter and Facebook). So if anyone happens to have any ideas on how to avoid this huge data consumption (like only using 1 app? Or just on a laptop in a browser? Or somehow remotely? Or do some magic with relays?), I'd love to get back to actively posting on NOSTR. But I'm shutting down for now, because realistically I don't have the money for more internet this month, and next time it'll be a decision between food and internet and guess what wins based on the opinions of the rest of the family :D. So see you guys. For now... image
2024-03-01 13:21:10 from 1 relay(s) 11 replies ↓
Login to reply

Replies (16)

Some client like #Amethyst allow to download media contents only with wifi or event by explicit requesting it. This can help to reduce the data consumption.
2024-03-01 13:26:55 from 1 relay(s) ↑ Parent Reply
Maybe using just one relay would help. Anyway, I love your posts, hope you can connect at least when you get on wifi!
2024-03-01 13:42:53 from 1 relay(s) ↑ Parent Reply
Try Nozzle. No profile pictures and no media unless you decide to load it. You could also set your read and write relay list to just one relay to save bandwidth, nostr:nprofile1qqsrg73rwzgq6xd5u36kyg2ef69a5ur2uhrcthsfuk0yvp0ergplf8qpr9mhxue69uhkymmnw3ezumr9vd682unfveujumn9wsq3jamnwvaz7tmwdaehgu3wd3jkxar4wf5kv7fwdejhgl68gu7 bostr instance is good for that. And deactivate relay autopilot in Nozzle.
2024-03-01 13:54:14 from 1 relay(s) ↑ Parent 2 replies ↓ Reply
i got similiar problem, yet i am the one who fix it. there's a way to fix it: 1. remove all relays in your client, make it to only connect to an bouncer like bostr. you could use mine: wss://bostr.lecturify.net (allows both read and write) 2. save it and you will see bandwidth usage went reduced 5x than before. unless your timeline is full of heavy images, it's recommended to disable auto load in your client. for my case (android), here's my recommendation: 1. very lightweight: nozzle + bostr 2. fair: any client + bostr
2024-03-01 14:05:38 from 1 relay(s) ↑ Parent 3 replies ↓ Reply
Hey guys, thanks a lot for all the suggestions. I hope the problem will have a solution. I guess I used too many clients and too meny relays and I am going to need to develop better and more sustainable behavior. Thanks for all the advices and I will try to use them when the times are better. Right now I am without money and with only few GBs left (which I need for other things), so after the times get better I will surely solve it somehow (thanks for all the advices from you). AWESOME COMMUNITY, see you in 5.
2024-03-07 11:52:24 from 1 relay(s) ↑ Parent Reply