this post was submitted on 22 Oct 2024
216 points (97.8% liked)

technology

23382 readers
184 users here now

On the road to fully automated luxury gay space communism.

Spreading Linux propaganda since 2020

Rules:

founded 4 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] xj9@hexbear.net 25 points 2 months ago* (last edited 2 months ago) (1 children)

we need significantly more resilient communications infrastructure. though this applies equally to disaster prep since the internet is extremely fragile. i see this as a problem with a bunch of parts, but some of the main pieces look like this to me:

  1. organizing computers (spare phones, spare laptops, actual server hardware) into cloud-like infrastructure components
  2. writing software that actually works well running on trash (fediverse nodes really hate it when hostnames change, so hexbear itself may not adapt well if the domain gets seized. they aren't a good match for disaster services either since you can't guarantee that global DNS will work)
  3. building overlay networks to connect nodes over the internet (yggdrasil+i2p looks like a winner in the short term)
  4. building a physical mesh network to link nearby computers together over fast links (BATMAN for no se vende mesh here in LA)
  5. developing a mobile adhoc mesh routing protocol that can setup a usable internet using only smartphones that interoperates with the fixed mesh noted in 4 (this will likely replace BATMAN, but is also a research problem and would represent a novel capability)

there are a bunch of shitty mesh apps and hardware components out there that may also be applicable, but its hard to get anything useful out of them without more planning and coordination. (meshtastic, briar, secure scuttlebutt, simplex, et al. come to mind)

i've been working on minibase for the micro-cloud component in an experimental capacity for years using alpine linux (just cuz i like it), but I've recently started working on a production version based on nix.

[–] PorkrollPosadist@hexbear.net 11 points 2 months ago (2 children)

4: building a physical mesh network to link nearby computers together over fast links (BATMAN for no se vende mesh here in LA)

5: developing a mobile adhoc mesh routing protocol that can setup a usable internet using only smartphones that interoperates with the fixed mesh noted in 4 (this will likely replace BATMAN, but is also a research problem and would represent a novel capability)

I think there is a strong tendency to put the cart before the horse when it comes to mesh networking. People imagine how cool it would be to have widespread mesh networks, but setting up a digital radio doohickey accomplishes nothing if there is nobody listening on the other end. We need social organizations first. Then, communications technology can be built to serve the needs of these organizations.

[–] someone@hexbear.net 6 points 2 months ago* (last edited 2 months ago) (1 children)

The other issue of course is that mesh networks only work in very densely-populated areas.

I'm in full agreement on your points about organizing being the real task, not the tech side.

[–] xj9@hexbear.net 2 points 1 month ago* (last edited 1 month ago)

WISPs use a lot of infra mesh tech and they're also really great for low-cost network deployments in rural areas too since you don't need to dig long trenches. Just point a couple of high-gain yagis at each other every 30km or so and you're good.

The main problem with MANets is 1. TCP is incompatible with variably high latency and partial connectivity and 2. there's no IP routing algorithm that handles variable topologies well. so you end up burning the majority of the already limited wireless bandwidth on tracking routing tree changes and not on data transmission. Density is only really an issue because of problem 1. ICNs handle the latency issue more gracefully, but without a solid solution for 2 it doesn't matter lol.

[–] xj9@hexbear.net 3 points 1 month ago* (last edited 1 month ago)

That and nobody actually knows how to make mobile adhoc mesh networks beyond toy demos. I think NDN is probably the furthest along based on my reading between the lines of some routing algo papers coming from UCLA (read: .mil applications). I'm personally trying to make micro clouds (or mist computing if I'm being cheeky) a little easier and continuing research into MANets because I think its a really interesting problem that there's very little incentive to solve since the profit potential is tiny. I think a lot of this is applicable for making websites that can't be deleted, but like you say, the social organization comes first. Without the will to maintain the systems, no amount of tools will make a difference.

The infra meshes in berlin and elsewhere are basically volunteer-based wireless ISPs and can't be run without people willing to put in the work. They also aren't that much more resilient to disruption than a typical corporate WISP like starry or whatever, its just theoretically possible to have a community owned/operated setup because the infra is relatively cheap. No Se Vende Mesh is a project that was already happening in LA when I got here and I'm trying to be supportive. Some of the volunteers are struggling with motivation though because, well, its LA and organizing is hard.