To be fair i've had more VPS downtime than cloudflare or aws combined. That goes for netcup, akamai, inmotion, and digital ocean. The only solution is to have multiple routes. I may have more downtime in my rack in small sporadic pieces such as during a node migration, or a switch update. Or more likely I had planed maintenance, because maintaining 10 physical machines, half a dozen switches, other network gear, and a couple dozen virtual machines requires much more downtime than a VPS. You just have to have some redundancy, even if your cloud only.

There is a palpable difference between downtime that results from your own activities (or incompetence), and downtime that you have zero control over as you wait, sitting on your hands, for your provider to return. It might mostly be an emotional pang, but it's one that inspires a resiliency and self-sufficiency mindset which can be harvested positively. Mild tangent: we can also self-host hardware and connect p2p, especially if NAT traversal and hole-punching keeps advancing. Then the only thing out of your hands is ISP. ....and for that there are always mesh networks.... We just don't have to accept this state of affairs or rationalize it.

Specifically on your side tangent: > especially if NAT traversal and hole-punching keeps advancing I'm wholly against this as it's been implemented now. Only because networks, as they have been designed, rely on very high levels of trust at the moment. Anything that is designed to traverse obscurity and hard protections is inherently breaking that trust barrier. It's an automatic assumption systems behind my firewalls can safely speak to each-other. It's as trusted network, we can drop the firewalls, the added encryption, honeypots, and paranoid routing gymnastics because we trust that, once configured my services are "safe" behind the walls.

many home LANs make it difficult or impossible for the average person to operate peer to peer. two people who want to run p2p personal servers with cryptographic identities should be able to send packets directly to each other no matter their DevOps knowledge, LAN setup or ISP's controls. I totally disagree with you :)

I think that sounds neat on paper, and I suppose many don't even have home internet now, their device is raw dogged on the (nat'd) open internet. But home infra as it exists, was designed around the idea that bad actors exist outside, and not inside the walls. That's just how it exists now. I don't think there is a safe way to transition. Home wifi connections, on devices, are generally considered to be known "safe", yes we have profiles on most modern OS (except android still tmk). I guess I realized I should state I'm sort of against true p2p for many privacy reasons, I've sporadically shared on my timeline. I don't want anything to do with relay outbox implementations and go way out of my way to block them. Because the internet infra, as it exists right now, makes assumptions to offer guarantees that fall apart when you side step them.

> many home LANs make it difficult or impossible for the average person to operate peer to peer. And I generally think that's a good thing.

I am something of a true p2p jihadist, so it makes sense we'd be far apart on this. I think it's a natural step in the decentralization, voluntarism and subjective-ication of everything. The timeline: 0. today. (standard client/server web with lots of intermediaries that are hard to exit while preserving desired utility) 1. decentralized, subjective contextual webs of trust (same physical/networking infra, but the lines begin getting drawn - by the participants themselves - **conceptually**/in code for voluntary islands of trust) 2. sovereign personal servers that you can fully trust; and connect to from edge devices (on an individual level, you own the full stack of client/server, but the servers still deal with lots of intermediaries and ISPs between each other) 3. personal servers that connect peer to peer directly based on contextual WoT (servers connect directly to each other, using WoT as their peer discovery and network topology guidelines. individuals' very light edge devices rely more and more on their sovereign personal server which connects directly to the servers of others) 4. mesh networks slowly overlay on top of ISPs and gradually replace them (those same p2p personal servers can connect directly over local mesh when a route is found. ISP censorship and infrastructure flakiness becomes irrelevant in these contexts. some problems may still exist in intra-mesh connections) 5. the lines drawn at step #2 are now fully realized in the physical infrastructure and network topology of very many overlapping voluntary networks and trust islands. people are free to re-jigger these physical and/or conceptual arrangements as needed. The end state being high-trust networked communities and economic zones that are truly antifragile and nearly impossible for a centralized enforcer to disrupt or censor short of enormous kinetic violence.

I am enthusiastic about providing people with optional pathways to opt out of guardrails they never asked for nor are even aware exist. consciously choosing a safer/hamstrung LAN doesn't have to come off the table, but the choice is lacking at the moment.

Sick 🤘

> high trust networked community I thought Bitcoin was no-trust

you'll love reticulum.network if you haven't already checked it out

I'm generally aware of it but haven't delved deep. thanks for the reminder