3 ms·
For me it would be an annoyance for sure, but I've been not-using Google stuff long enough that I wouldn't really care. This is how I did that: 1. I self-host
by znpy 7y ago
For me it would be an annoyance for sure, but I've been not-using Google stuff long enough that I wouldn't really care.
This is how I did that:
1. I self-host my email and most of my emails are exchanged via my self-hosted domain.
2. I use nextcloud for cloud storage with automatic upload of pictures, videos and call recordings from my phone.
3. I use ZFS for snapshotting and replication.
------
Regarding my google account... I took the habit of taking notes of my previous password when I change it with a new one. I also took note of my backup codes.
------
Regarding self-hosting email... It's surprisingly low-maintenance. My current mailserver was set up in 2014 and I've touched very little since then (considering it's been on for six years).
It does require some learning in the beginning, but a) email is so old that's very, very, very well documented and b) time spent learning is never wasted.
Nextcloud is just awesome. It does have its quirks and an SSD would definitely help, but I've been running it off a cheap machine (~115€ dell optiplex 7010, 2nd gen i5, 8gb ram, 250gb HDD system disk + 2TB HDD data disk) and only had occasional problems (don't try and push too much stuff at the same time or postgress will basically kill itself if it can't keep up -- upload files to the data folder instead and let nextcloud rescan such folder).
ZFS is the real game changer. Hourly snapshots are extremely fast and cheap and make it easy to sync your precious data to another location (in case something goes wrong).
------
Sometimes I stop and think about how exploitative and predatory modern internet services providers are.
Most TOSes clearly state that they can terminate your service for any reason. Which is generally understandable but also mean that all of your data could be gone so fast...
The cloud isn't really the safest thing to put your stuff into.
- superkuh 7y ago> 1. I self-host my email and most of my emails are exchanged via my self-hosted domain. >Regarding self-hosting email... It's surprisingly low-maintenance. My current mailserver was set up in 2014 and I've touched very little since then (considering it's been on for six years). What will you do when you're email server's OS goes out of support? (or if VPS, they upgrade from ovz6 to 7, or worse) Or if you can upgrade but the packages for your original install are slightly changed or not available on the new version? How did you store the email? Virtual users on disk with dovecot or the like? How will you port to a new OS environment when required? It's isn't trivial. I'm in the same position having set up my personal mailserver in 2013 with very little maintenance since. But now the bill has come due with the need to upgrade OSes.
- znpy 7y agoNot a big deal, a full reinstall every 5-6 years is okay. I'm planning full OS update and mailserver reinstall (I'll probably be switching to CentOS 8). Regarding the downtime... Not a big deal either. I already have an mx backup host in place, along with (semi-automated) procedures to imports mails delivered to the mx-backup host into the mx-primary. > It isn't trivial. Well, it isn't super complicated either. It really depends on the degree/detail of your configuration. For the most parts you should be able to copy the old configuration files into the new postfix/dovecot installation and fix errors as they come up. Problems may arise if you have non standard features and/or if you interface with other services.