216
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 22 Oct 2024
216 points (97.8% liked)
technology
23313 readers
129 users here now
On the road to fully automated luxury gay space communism.
Spreading Linux propaganda since 2020
- Ways to run Microsoft/Adobe and more on Linux
- The Ultimate FOSS Guide For Android
- Great libre software on Windows
- Hey you, the lib still using Chrome. Read this post!
Rules:
- 1. Obviously abide by the sitewide code of conduct. Bigotry will be met with an immediate ban
- 2. This community is about technology. Offtopic is permitted as long as it is kept in the comment sections
- 3. Although this is not /c/libre, FOSS related posting is tolerated, and even welcome in the case of effort posts
- 4. We believe technology should be liberating. As such, avoid promoting proprietary and/or bourgeois technology
- 5. Explanatory posts to correct the potential mistakes a comrade made in a post of their own are allowed, as long as they remain respectful
- 6. No crypto (Bitcoin, NFT, etc.) speculation, unless it is purely informative and not too cringe
- 7. Absolutely no tech bro shit. If you have a good opinion of Silicon Valley billionaires please manifest yourself so we can ban you.
founded 4 years ago
MODERATORS
Hexbear is going to be one of the few places on the internet where you can say "death to Israel"
Death to Israel.
They will turn the screws on the hosting providers if (and when) it comes to it.
And even if the hosting provider doesn't, the US government can just seize the domain. .net is administered by US-based Verisign.
So what's our plan B? If the domain is seized, I'm assuming that we'll get updates from the fediverse account. But if there's some sort of problem there (matapacos.dog is seized, or no updates get posted because those with access to the matapacos @hexbear account have been arrested, or other unforeseen problem) how do we re-group?
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:
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.
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. It is very much a local organizing problem. The tech does not circumvent this.
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.
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.
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.