ccTLD are best, as they don’t have a contract with ICANN setting their service. While ICANN tries to be a multi-stakeholder, international organization with broad representation… underneath all the bylaws and process and so on it is a US company incorporated in California.
Probably the TLD of your own country is good!
If you don’t care about that, then either .coffee or .soy for sure. 😉
I’m a NixOS user and I didn’t even know there was another way other than editing configuration.nix… ¯\_(ツ)_/¯
The answer is AGPLv3, or an exception if a corporation pays for one (in which case it just becomes a commercial license).
I think that you have to do quite a bit more setup on email than most other services. There’s SPF and DKIM and DMARC and so on. Plus spam filtering, setting up accounts and authentication, …
Plus email is arguably more important than anything else, since it’s kind of the lowest common denominator of the Internet; your dentist will probably send you an email to remind you of appointments, job offers will arrive via email, password resets arrive via email, and so on.
So it is a bit scary.
Having said that, as long as you’re not hosting from a residential IP addresses it is definitely achievable. You can start with one domain and use it for low-value purposes (or for accounts that allow multiple email addresses, like GitHub).
No long pink, pale blue, and white stockings?
I think that ZeroSSL are owned by an American company.
I worked on the Yeti Project a while ago, which showed that an independent group of operators can run root servers.
Managing the contents of the root zone was out of scope… we used the ICANN root.
That sounds like terrible reliability. If my home lab had an outage like that I would shut it down as I clearly don’t know how to run a dependable system. 😅
It depends on the file system, doesn’t it?
I don’t know of any resolvers that simply fail after not getting responses from a single name server. Please name and shame!
I use restic to:
Also, any non-trivial system has failure modes that are not binary. Like, if your convertible car has the roof stuck down you can drive it, but you will be sad if it rains. So, is the car “up” or not? Similarly, if your site has writes offline for a database upgrade, but reads work fine, is it “up”?
The concept is just advertising and something that makes sense to senior management, but provides no actual useful metrics.
I had one Raspberry Pi that needed to be hooked up to a monitor after it failed to reboot after an Arch kernel upgrade. The device name for the Ethernet card changed, and the netctl setup I was using to set up some route or other no longer worked.
In my years of using Arch that was literally the only problem.
I’ve had pain with several Debian upgrades, mostly due to exim4 becoming more strict and me actually having to learn something about my email setup. Also an issue with a Debian upgrade changing Dovecot version. Neither really avoidable by Debian, but it was not less painful somehow than Arch.
Actually this reminds me of why I moved to Arch on Raspberry Pi. I had a SD card go bad, and ext4 just happily used corrupted data. I wanted to switch to btrfs, which I could do with Debian, but any time Debian updated the kernel it wiped my setup and I had to do work to get it booting again. Arch supports btrfs out of the box and has worked smoothly and easily.
I came from Debian and Arch and was pleasantly surprised at how easy to set up and run NixOS is. I’ve been using it on my personal laptop for months now without any major issues.
I use MoCA at home, 1 GBit. It works pretty well, and I get almost full speed.
Every now and then I have some blip and have to power cycle on one of the coax-to-Ethernet connector, so that’s annoying. It’s like twice a year, so not a huge problem.
The biggest drawback is high latency. It’s milliseconds instead of microseconds in the house. I guess it’s buffering and framing, so maybe unavoidable.
I also do see some small packet loss. Less than WiFi, but not zero like you’d see from a proper Cat6 cable.
Maybe just but a pair of MoCA adapters to try in your setup?
Lots of different reasons.
Some hated the GPL, viewing it as less free (which is kind of true depending on who’s freedom you care about… personally I care about freedom of users and protecting society from large corporations, but you do you BSD fans).
Some disliked the crappy network stack (the superior UDP performance and IPv6 compliance were much touted at the time… although my own benchmarks didn’t confirm the BSD folks beliefs there). It may be hard to imagine with all of the innovation in networking layers that continues in Linux now, but that was the situation 20 or 25 years ago.
Further on networking, some disliked the ipchains/iptables (now nftables I guess) firewalling and whined constantly about how much better pf was. My firewalling needs have always been simple (except for whatever horrors Docker forces on me), so I never understood the rage.
Some complained about the terrible threading model in Linux (back before this was essentially solved in Linux, leaving Linux threading far superior to BSD threading).
Some pointed to the plethora of distributions as inferior to the obviously better model of the OS shipping with a blessed set of tools (think FreeBSD “base” or whatever).
Some bemoaned the lack of “jails” in Linux (essentially a primitive form of containers).
Anyway.
I think basically it was just annoyance that people used Linux instead of their favorite.
I used to use Linux.
I still do, but I also did in the past.
I worked at a company filled with BSD zealots. Their burning hatred for Linux was all-consuming, bad really put me off of the lot.
We were so close to a phone usable by non-enthusiasts with the Nokia N1. The Nokia Linux phones were killed when Nokia hired a former VP at Microsoft to be their CEO. I’m still bitter.
I use nightly backups. I keep them 2 weeks.
After that I keep a weekly backup for 2 months.
After that I keep a monthly backup for 2 years.
I keep my yearly backups forever.