New blog post: Google's reCAPTCHA Clampdown: Are You Even Human on Your Own Android?

Google's latest changes to reCAPTCHA are causing headaches for de-googled Android users, raising uncomfortable questions about digital identity and who truly controls your device. It's more than just an inconvenience; it's a battle for autonomy in t...

https://rhodzy.com/blog/googles-recaptcha-clampdown-are-you-even-human-on-your-own-android

#android #privacy #degoogled #digitalrights #opensource #techfreedom

rhodzy.com

@GrapheneOS

Hardened OSs like #GrapheneOS do a great job, but we have a major blind spot: The Hardware.

Modern phones are networks of dozens of "black box" computers (UFS, Baseband, Wi-Fi) running proprietary code we can't audit, disable, secure or replace.

Why this matters:
1️⃣ Persistence: Malware in your UFS/SSD controller survives a factory reset.
2️⃣ Tracking: Hardware Attestation acts as an immutable digital fingerprint.
3️⃣ Shadow Attacks: Zero-click exploits hit your Wi-Fi or Baseband before the OS can even react.

We are calling for #HardwareSovereignty. Inspired by the #OpenBSD philosophy, we demand:
✅ Open & replaceable firmware for ALL subsystems.
✅ User-controlled hardware toggles.
✅ Trust minimization that includes the manufacturer.

It's time to move from "Vendor-Enforced Security" to User Sovereignty.
Read the full Open Letter here: https://pastebin.com/RzRbzhwn

#HardwareSovereignty #Infosec #CyberSecurity #Privacy #OpenSource #TechFreedom

The next #TechFreedom newsletter goes out soon! Sign up here: https://newsletter.techfreedom.eu

From Digital Neofeudalism to Sovereignty: How I Built My Own Knowledge Operating System

Most of us live today in a state of digital neofeudalism. We have become digital sharecroppers: our notes, thoughts, and technical documentation are "leased" from large SaaS corporations. If Notion goes down, your knowledge disappears. If Evernote changes its terms and conditions, your data becomes hostage.

I decided to say "enough." I built a system that is 100% mine, self-documenting code, and works the way I think: nonlinear.

🧠 Knowledge Architecture: A Network Instead of a List

A traditional blog is a list. My knowledge base is a graph. I use Markdown and the Zettelkasten approach to create a network of connections. Thanks to Hugo (@gohugoio), each note knows who links to it.

How does it work?

One article contains reasons, which are the titles of separate publications. These, in turn, have backlinks like "this motivated me to...".

graph TD
A[homelab.md] -->|why?| B[digital-neofeudalism.md]
A -->|business model| C[digital-sharecroppers.md]
B -->|solution| A
C -->|motivation| A

I use transclusion (include) to inject fragments of technical documentation where they're needed. No more "copy-paste."

🏗️ Hardware: Division of roles in the ecosystem

My homelab isn't one big server. It's specialized units:

| Machine | Role | Characteristics |
| --- | --- | --- |
| R3930 | Workhorse | heavy containers, databases. |
| Wyse 5070 | Guardian | DNS (Pi-hole), Proxy, SSO (Authelia). |
| DELL GB10 | AI Accelerator Cluster | LLM. |
| Laptop | Command Center | This is where the code is written, and this is where Ansible runs. |

Why is the Gateway (Proxy/SSO) on a small Wyse? Because it's quiet, energy-efficient, and supposed to run 24/7, even when the "workhorse" is resting.

🛠️ Infrastructure as Code (Ansible)

I don't configure servers manually. Everything is defined by SSoT (Single Source of Truth) in YAML. One file describes the entire lab:

services:
- id: "technical-docs"
name: "Wiki"
fqdn: "docs.lab.arpa"
target_host: "R3930"
is_private: false
category: "Knowledge"

Ansible takes this list and:

  • Deploys the container on the appropriate host.
  • Configures nginx-proxy on the Wyse to route traffic to R3930.
  • Injects authorization rules into Authelia.
  • Updates the Homepage dashboard.
  • 🔒 Security: SSO and Custom CA

    Let's Encrypt has no place on the .arpa network. I built my own Certificate Authority (Own CA) based on Smallstep.

    • Authelia (SSO): One login and password (plus 2FA) to access all private services.
    • Smallstep SSL: Every service in the *.lab.arpa domain has a "green padlock." Ansible ensures that my laptop and all servers trust my Root CA.

    Development Challenge: Automating SSL via the ACME protocol on my own network is pure magic. Nginx automatically requests a certificate from the local CA server. Without accessing the internet.

    📊 Result: Dashboard

    The end result is the Homepage – a dashboard that generates automatically. I can see every service, its status, and information about which physical hardware it currently resides on.

    🚩 What's next?

    My knowledge operating system is growing, but it has one weak point. If the Wyse DNS server goes down, I'm out. So in the next post, we'll cover DNS2 redundancy and data synchronization using Gravity Sync.

    Homelab isn't a goal, it's a process. And you? Are you still working your tail off in the cloud?

    #DigitalIndependence #OpenSource #SelfHosting #DataPrivacy #TechFreedom #BuildingTheFuture
    #DigitalNeofeudalism #DigitalSharecroppers #KnowledgeOperatingSystem #Ansible #Homelab

    Your messages don't have to live on someone else's server.
    AmnyX allows you setup a self-hosted relay server.
    🚀 Full control,chats stay local, and latency is instant. If you care about privacy, speed, AmnyX is your friend #AmnyX #SelfHosted #DataPrivacy #Messenger #TechFreedom @AmnyX www.amnyx.com

    Cal.com is restricting its license, but the community is already responding. Cal.diy is a new fork that preserves the original MIT-licensed codebase.

    It’s a great reminder that open source provides a permanent "exit strategy" from proprietary shifts. If you value a truly open scheduling tool, Cal.diy is the one to watch. ✨

    https://itsfoss.com/news/cal-com-goes-proprietary/ #opensource #privacy #techfreedom

    Cal.com Goes Close Source Because "AI Can Easily Exploit Open Source Software"

    That said, the old codebase will live on as Cal.diy under the MIT license.

    It's FOSS

    Frustrated by website builders that charge $16+/mo and still limit which plugins you can use? Proprietary platforms often lock your content into their ecosystems, making migration a nightmare. 🕸️

    WordPress on PikaPods gives you the full power of open-source CMS starting at just $1.80/mo. No artificial feature gates—just your site, your data, and 60,000+ ways to customize it. 🔓

    https://pikapods.com/pods?run=wordpress #opensource #techfreedom