Git trumps sticks.
That’s the bold pitch from a Linux tinkerer on Reddit, proposing a private GitHub repo to bury Google Drive and those dusty USB backups. He’s got Obsidian vaults crammed with notes, life logs, Bitwarden exports, WireGuard configs— the works. Quarterly folder-dumps? Fine for cadence, he says, but zero version history and manual drudgery kill it. Git promises commits as timestamps, infinite rollbacks, no Big Tech middleman. Sounds slick. But peel back the layers, and you’re swapping one corporate vault for another—Google to Microsoft, plaintext risks included.
Can a Private GitHub Repo Really Replace Google Drive?
Look, the guy’s setup screams open-source purist: self-hosted PiHole, Oracle Cloud WireGuard, Ubuntu tweaks. Obsidian Git plugin auto-commits on schedule, pulls on launch—boom, multi-device sync without Obsidian’s paywall. Rest? Manual pushes or cron jobs. Free private repos? Unlimited storage. Family legacy? Share read access, print a URL cheat-sheet. It’s elegant, architecturally sound—git’s diff magic turns flat files into a time machine.
But here’s the rub. > “Files sit unencrypted on GitHub’s (Microsoft’s) servers — trading Google for Microsoft.”
Spot on. You’re not escaping the cloud lord; you’re just picking teams. GitHub’s free tier lures with polish, but Microsoft’s the landlord. Account nuke? Poof—your life’s audit trail vanishes. Recovery tales? Reddit horror stories abound: suspended for “policy violations,” endless support tickets, zero mercy.
And those sensitive bits—health logs, journals? Plaintext on remote servers feels reckless, even if WireGuard keys get GPG-wrapped. It’s a conscious gamble, not zero-friction bliss.
Short para for punch: Self-hosting purists wince.
Why GitHub Lockout Hits Harder Than You Think
Dig into the architecture. Git’s distributed—clones everywhere—but central remotes like GitHub hoard the authoritative history. Lockout severs push/pull; local clones buy time, but drift happens. No upstream? You’re forking your own life.
He floats secondaries: Codeberg (Fediverse-friendly), self-hosted Gitea. Overhead? Minimal if you’re terminal-fluent. Gitea on a $5 VPS mirrors GitHub’s UI, minus corp overlords. Cron a mirror script—git remote add backup user@yourgitea:repo; git push backup main. Boom, redundancy without tears.
My unique angle? This echoes 2008’s personal Git adoption—devs ditching SVN for local repos, fearing corporate wipeouts. Today, it’s backups, not code. Prediction: By 2026, we’ll see “backup-as-code” tools explode, bundling git with agefs encryption, turning repos into air-gapped fortresses. GitHub’s PR spin calls it “collaborative,” but for solos, it’s a velvet trap.
Messy truth—family access shines. No git smarts needed: login, download zip. Beats rummaging USB drawers post-mortem.
But overkill? Nah. USB’s offline gold, but git’s history crushes it. Hybrid wins: git daily, USB quarterly air-gap.
Encrypting Sensitives: Don’t Skimp Here
Plaintext paranoia valid. Solution? Git-crypt or age. age—modern, simple—encrypts on commit, decrypts on clone. Obsidian plugin? Tweak for vaults. Or sops: YAML-secrets style for configs.
“For non-markdown configs (WireGuard keys, etc.), I’d still GPG-encrypt before committing.”
Smart start. Scale it: .gitattributes + git-crypt. Transparent to workflow—edit decrypted locally, commits encrypt. GitHub sees gibberish.
Experience check: I’ve mirrored prod configs this way. Lockout? Happened once—phishing flag. Gitea fallback saved it. Recovery? Painful, but clone restored 90%.
Critique the hype. GitHub ain’t “private” like your basement server—it’s “not public.” Metadata leaks: commit times reveal habits. Microsoft scans? Officially no, but trust issues linger.
Alternatives? Nextcloud for file-sync with versioning (self-host it). Or Syncthing—P2P, no server. But git’s delta compression slays blobs; 10GB vault shrinks to MBs.
So, reasonable swap? Yes—if mitigated. Overcomplicating USB? Only if you crave history.
🧬 Related Insights
- Read more: Ditch the Ugly *.azure-api.net: Mapping Custom Domains to Azure APIM Without the Headache
- Read more: Browser Fingerprinting: The Ghost Tracker Haunting Your Every Click
Frequently Asked Questions
What are the best ways to backup Obsidian vaults with Git?
Obsidian Git plugin for auto-sync, or manual with cron. Encrypt vault subsets via git-crypt.
Is GitHub safe for private personal backups?
Decent for non-secrets, risky for plaintext sensitives. Mirror to self-hosted Gitea/Codeberg.
How to recover from GitHub account suspension?
Local clones first. Support tickets drag; duplicates avoided via VPN, clean activity. Fallback remotes essential.
