"When you say 'I don't care about the right to privacy because I have nothing to hide,' that's no different than saying 'I don't care about freedom of speech because I have nothing to say.'" — Edward Snowden

We build software and hardware for people, not for shareholders, surveillance vendors, or the HR department that inevitably shows up to ruin it.

Most of tech got captured a long time ago. Your phone reports on you. Your tractor phones home to the manufacturer before it lets you fix it. Your "smart" device stops working the day the company decides it's done supporting it. Every product manager's dream is a subscription, a dark pattern, and a data pipeline straight to an ad broker.

We think that's a bad deal. We're not interested in "disrupting" anything or building the next acquisition target. We're here to make things that work, that you own, that don't spy on you, and that don't ask permission from a compliance team before doing the right thing.

• Privacy by default. If a feature requires harvesting your data to function, it's not a feature, it's a liability we won't ship.
• Anti-surveillance. We don't build tracking infrastructure, and we actively work to make it easier to avoid other people's.
• Right to repair. If you bought it, you own it. That means the schematics, the firmware, the parts, and the right to void whatever warranty you feel like voiding.
• Real ownership. No license agreements that quietly turn a purchase into a rental. No forced clouds. No bricking your gear from a server in another country.
• No corporate theater. No mandatory "synergy" meetings, no growth-hacking, no dark patterns, no engagement metrics dressed up as user value. We measure success by whether the thing is actually good.

We welcome contributions from anyone who shares the general idea: build good things, respect the user, don't be creepy about data. Open an issue, open a PR, or just fork it and do your own thing. That's the point of open source.

A few ground rules:

1. No telemetry, no analytics, no phone-home behavior in anything submitted here, ever, unless it is fully opt-in, disclosed, and off by default.
2. Document your work. Repair guides, teardown notes, and clear commit messages matter more than clever code.
3. License permissively where possible, so this stuff stays usable by everyone, not just whoever forks it next.

Unless a specific repo says otherwise, assume permissive open-source licensing (MIT/Apache-2.0/GPL depending on the project, check with each repo). We want this stuff copied, remixed, and spread around. That's the whole point.

Yeah, it's called shitpost.work. We're not a brand-safety exercise. We're people who are tired of pretending that corporate speak makes software better. If the name bothers you more than the surveillance capitalism does, this probably isn't your org.