Comment on Quit ChatGPT: right now! Your subscription is bankrolling authoritarianism | Rutger Bregman
JustTesting@lemmy.hogru.ch 15 hours agoMeshcore might be a bit better suited for this, if you want to reach a forum further than 50-100km away reliably.
With the room servers it almost supports this use case already
IAmNorRealTakeYourMeds@lemmy.world 14 hours ago
would be cool to make a browser and server that work with mesh[core/static]. and given the need for very basic and extremely lightweight websites and services, or even APIs, making a website/api shouldn’t be too complicated.
One can have a weather station and I can have a weather app that makes API calls through mesh[].
decentralized cache would also help, (if you are routing a call for a website, but you recently opened it and have it in your cache, you an send that, decreasing load on the network, and automatically making popular sites more accessible).
Also it could used as a backbone for more robust chat apps/forums/blogs/services.
JustTesting@lemmy.hogru.ch 14 hours ago
I agree, that would be amazing. I also hope it will help with some truly local community building (no troll farms from halfway across the planet spamming shit). Weather stations are already possible with sensor nodes, and most big repeaters have weather data. Though not like weather forecasts or anything.
The main issue would probably just be congestion, not even bandwidth. Once it’s used a lot, some packets will just be dropped due to congestion and you don’t get a reply at all.
A bit less of a problem with meshcore, with meshtastic in densely populated areas most users still don’t set their devices to client_mute, causing unnecessary rebroadcasts and even more congestion. Though with enough adoptions maybe governments might lower their restrictions on duty cycle, allowing for more traffic.
Cataphract@lemmy.ml 11 hours ago
Imagine local libraries and post offices pushing this technology to get around ISP’s grips on local infrastructure. Helps during emergency events, local organization, and could even put e-books available from the library. Post office’s make sense because of their rural locations extending the nodes and brings them into the 21st century delivering physical and digital mail.
CheeseNoodle@lemmy.world 11 hours ago
idk much at all about networking (beyond a home network) but if someone wants to begin building an alt-net I’d be willing to contribute a rasberry pi to the cause and leave it running 24/7.
IAmNorRealTakeYourMeds@lemmy.world 13 hours ago
wouldn’t the more users also mean more nodes? making the system scalable? as with more users, the network gets more robust?
JustTesting@lemmy.hogru.ch 11 hours ago
I’m definitely not an expert radio operator or anything, but this is how I understood it.
With Meshtastic, no, it actually gets worse beyond a certain point, especially in dense areas. Each radio rebroadcasts messages, so more message fill the air, causing more congestion. setting devices to client_mute (no rebroadcasting of messages) alleviates this to some extent, but most people don’t do that. In general, a few well placed nodes are better than a lot of clients.
Meshcore with dedicated Repeater nodes alleviates that a bit, as a node is either a client that can originate messages, or a Repeater that can only rebroadcast. And it has a bit better routing protocol, reducing unnecessary duplicates in some cases.
The radio band is license free in many countries, but there’s still some restriction, e.g. 10% duty cycle in my country, which means no radio can be sending more than 10% of the time (so 1 minute in every 10 minute window). That combined with (afaik) nodes only being able so send one message at a time limits how many messages can be in flight at an instant. And more clients increases background chatter from e.g. node announcements and duplicates, leading to further congestion. And in meshtastic, since packets “flood” out in all directions, and each node rebroadcasts again, and it’s not directional, all the packets travel all over the place when you send a message. You could have a packet traveling in circles between new nodes for a long time.
E.g. in my region, originally the default for meshtastic was 7 hops on long range fast preset. That led to congestion so they switched to medium range fast, then recommended limiting hops to 5, and now ideally to 3, just so there’s less chatter and less utilisation of the channel. 3 hops is barely enough for me to get out of the city I live in. Meshcore also does floods, but also can keep track of paths so you can have a relayed connection along a specific path that does not flood out in all directions, along with putting up repeaters being a conscious and strategic choice by users, so you get something more like a dedicated highway of repeaters that are placed high up and can relay messages much better than some client down at street level could. And the hop limit is more like 64 (I think it can be higher but that’s what is set somewhere in the firmware). And repeaters are stationary, so they don’t need to announce themselves to the network that often (e.g. every 3 hours in meshtastic vs every 24-48 hours in mesh core). All of that means less channel utilization and longer reach.