Practical #selfhosting and #privacy enthusiast. Evil #emacs user. Enthusiastic hiker & cyclist. DevOps Engineer at DuckDuckGo
Practical #selfhosting and #privacy enthusiast. Evil #emacs user. Enthusiastic hiker & cyclist. DevOps Engineer at DuckDuckGo
Posts
Practical #selfhosting and #privacy enthusiast. Evil #emacs user. Enthusiastic hiker & cyclist. DevOps Engineer at DuckDuckGo
Practical #selfhosting and #privacy enthusiast. Evil #emacs user. Enthusiastic hiker & cyclist. DevOps Engineer at DuckDuckGo
I'm writing/updating a doc for my wife for "what if" scenario in case I'm incapacitated and can't deal with tech in our lives. It's been a sobering experience. DNS, Email, various self-hosted services, passwords/2FA/recovery codes, home-automation, networking, encrypted backups....
#selfhosting is great and I would not discourage folks from it, but if others depend on you - don't be a single point of failure with no recovery. Stuff happens...
Practical #selfhosting and #privacy enthusiast. Evil #emacs user. Enthusiastic hiker & cyclist. DevOps Engineer at DuckDuckGo
The fact that compiling #Firefox fails because my desktop with 64GB RAM runs out of memory is making me furious. ld taking 41GB of RAM? What?
Out of memory: Killed process 3290862 (ld.lld) total-vm:56461336kB, anon-rss:43114148kB, file-rss:432kB, shmem-rss:0kB, UID:30001 pgtables:96296kB oom_score_adj:0
Practical #selfhosting and #privacy enthusiast. Evil #emacs user. Enthusiastic hiker & cyclist. DevOps Engineer at DuckDuckGo
Practical #selfhosting and #privacy enthusiast. Evil #emacs user. Enthusiastic hiker & cyclist. DevOps Engineer at DuckDuckGo
Practical #selfhosting and #privacy enthusiast. Evil #emacs user. Enthusiastic hiker & cyclist. DevOps Engineer at DuckDuckGo
Practical #selfhosting and #privacy enthusiast. Evil #emacs user. Enthusiastic hiker & cyclist. DevOps Engineer at DuckDuckGo
Practical #selfhosting and #privacy enthusiast. Evil #emacs user. Enthusiastic hiker & cyclist. DevOps Engineer at DuckDuckGo