Prepping is about surviving the collapse of the system.

Resistance Infrastructure is about replacing the functions of the system so it doesn’t matter if it collapses or not.

This is the “Gray Man” strategy. If you have zero digital footprint in 2026, that absence of data becomes a data point itself. Anomalies get investigated.

I think we need to separate Camouflage from Logistics.

I’m not suggesting you delete your digital existence and live in a Faraday cage. By all means, keep the normie accounts. Post the cat photos on Instagram. Keep a Gmail address for the spam. Feed the algorithm just enough “conformist” content to look boring. That is your camouflage.

But Resistance Infrastructure isn’t about hiding, it’s about capability.

It’s about ensuring that when the “system” decides to de-platform your community group, or lock your bank account, or shut off the internet in your region during a protest, you still have a way to function.

Look, man, you can keep checking my syntax all night, but at the end of the day, I’m just a guy in Canada who checked the news and saw something terrible happen and thought how we could prevent something like this from happening again.

I wrote that post because I was genuinely curious (and maybe a little bit desperate) to know if I was feeling alone in this. I wanted to know if other people saw the same connection between the data we give away and the way it’s being used as a weapon. And more importantly, how we proceed moving forwards as people and a community, not for silly reasons you’d likely suspect from a bad actor. I do get where you come from though, this is going to be my final word on this matter. Now, I’m going to stop arguing about my sentence structure and continue actually helping people build

I’m a “malicious actor” because I’m telling people to stop giving their data to big tech and hide it on a local server? That is the least efficient data collection scam in history. If I wanted your data, I’d tell you to sign up for a “Free Privacy Newsletter” on a Google Form. Telling you to run an encrypted Vaultwarden instance literally locks me out too.

@PhoenixAlpha I’ll be sure to tell my 10th-grade English teacher that her lessons on rhetorical devices are now considered hallucinations. If “not X, but Y” makes me a bot, then half the op-ed columnists in history are running on silicon.

As for the Renee Good shooting, if you think the infrastructure of surveillance, license plate readers, and cross-referenced databases “had nothing to do” with how ICE operates in a city like Minneapolis, then you’re missing the forest for the trees. I’m not here to win a Turing test; I’m here because I’m tired of seeing tech used as a weapon, you know?

I’m definitely a human, just a concerned poster who actually gives a damn about what’s happening to our digital privacy.

I’ll take the “AI” comments as a compliment to my grammar, I guess, but it’s a bit sad that we’ve reached a point where structured thoughts and bullet points make people suspicious. I use the dashes and lists because I want this info to be readable, not because I’m a bot running on a server somewhere.

I’ve spent enough time working in tech and volunteering with seniors to know that if you don’t lay things out clearly, the message gets lost. I’m just someone trying to help people get their tech privacy back. No LLM required. Just a lot of caffeine and a genuine annoyance with where Big Tech is heading.

Actually, you’re exactly right about client-side encryption being the answer, and that is the standard we are pushing for. But the reason you don’t just dump those encrypted files into a Google Drive is because of the metadata. Even if Google cannot read your “letter,” they are still mining the “envelope,” they know when you wrote it, where you were, and who you sent it to. In 2026, metadata is often more dangerous than the content itself because it is so easy to automate into a threat profile.

As for the law, you’re right that a court order is a court order, but there is a massive difference in the “cost of surveillance.” Big tech companies have dedicated departments to automate data handovers for thousands of users at a time; it is a streamlined pipeline. A private server forces the state to slow down, to get a specific warrant for a specific physical machine, and to actually do the legwork. It turns a massive dragnet into a targeted investigation, which is exactly how the system is supposed to work.

And regarding the “Amazon engineer” versus a neighbor, an engineer might not know my name, but the Amazon algorithm knows my pulse, my politics, and my habits better than anyone. If I use E2EE, the person hosting the hardware doesn’t have the keys anyway, so they are just a landlord for my digital safe, not a spy.

That means a lot, the force multiplier thing is exactly why I posted this. Building for yourself is a great start, but bringing others along with you is how we actually scale the resistance. We need more nodes in the network, so keep doubling down.

You’re hitting on the two biggest myths of the current era: that “legal agreements” with giants actually protect you, and that a neighbor is a bigger risk than a faceless corporation.

First, when a tech giant gets a broad subpoena, they don’t fight it for you; they automate the handover because you’re just a line in a database of billions. When you host locally, you’re a specific node. If the state wants your data from a private server, they have to physically knock on a specific door. That is a massive increase in the “cost of surveillance” compared to a silent API request sent to a corporate data center.

Second, this isn’t about “trusting a neighbor” with your plaintext data. In a proper sovereign setup, the data is end-to-end encrypted. I can host your Vaultwarden or your Nextcloud backups, but I don’t have the keys; I’m just providing the “digital real estate.” It’s the difference between giving someone your house keys and just letting them provide the land your safe sits on.

The goal isn’t to make law enforcement impossible; it’s to make the “dragnet” impossible. If they want one person’s data, they have to work for it, rather than just pulling it from a corporate warehouse.

Honestly, you’re right about the skill gap, the convenience trap is exactly how Big Tech won in the first place, but I don’t think the goal is to turn every single person into a sysadmin. My time teaching at the library with the Cyber Seniors program showed me that people don’t need to know how to flash an OS to deserve privacy, they just need a doorway that isn’t owned by a corporation.

If the 5% who actually know how this stuff works start building “community nodes” for their family, their block, or a local shop, then the 95% get all the benefits without the technical headache. We don’t need everyone to be an expert, we just need enough local infrastructure so that “the cloud” isn’t the only option left. It’s not about total purity for everyone, it’s just about building enough exit ramps so the machine becomes optional, you know?

I feel this deeply. I used to volunteer at a library teaching “Cyber Seniors” digital literacy, and the biggest hurdle was always the fear of “breaking” something. The truth is, the big tech companies want you to think it’s too hard so you’ll keep paying them with your data.

You don’t need to be a sysadmin to start. It’s not about days of fixing errors; it’s about taking one small win at a time; like setting up a password manager first. If you can follow a recipe, you can build a node. We’re working on better, no-jargon guides to make sure the “thousand little errors” don’t stand in your way. You don’t have to be an expert to be part of the resistance.

Spot on. Self-hosting is the most effective form of quiet, material protest we have. Every time your family uses Syncthing instead of OneDrive, you’re starving the machine of the telemetry it needs to function.

Running that stack for your inner circle is essentially building a “digital mutual aid” node. You’re taking the burden of surveillance off their backs and putting it on your own hardware where you can actually defend it. That’s the work.

You’re right - you’ve successfully built an infrastructure that keeps you outside the slop machine. Kagi, Whoogle, fediverse, HackerNews - that’s strategic refusal working as intended. The slop is concentrated on mainstream platforms where people haven’t opted out. Instagram, TikTok, Facebook, YouTube - my friends still using those are drowning in AI-generated engagement bait, fake historical photos, GPT-written content. It’s not subtle anymore for people still plugged in. The kirkification angle is trickier though - it’s not just what you see, it’s how you’re represented in spaces you’re not in. Someone can generate deepfakes of you and you’d never know. Your digital body gets remixed without consent. Your “maybe I can’t recognize it anymore” point is real. The aesthetic tells are getting harder to spot. Five years ago it was obvious, now it takes active effort. Platform rules banning it would help but verification at scale is nearly impossible. The only reliable defense is what you’re doing - removing yourself from spaces where slop is profitable. But that’s also a technical barrier. I can set up Whoogle and fediverse accounts, but my friends on Instagram? That’s where their community actually is. Opting out means losing access for most people. This is why municipal-scale infrastructure matters - if a town runs its own services, suddenly opting out isn’t a technical hurdle, it’s just where the community is. You asking “where is the slop?” while others drown in it proves we’re already living in parallel internets. The bifurcation is real.