I’ve had ~15 cars over the past 25 years, different make and models, some really cheap, some fairly expensive. One thing they all have in common: their terrible infotainment UI.
I’m sure they are trying and it has gotten slightly better lately - but it’s still not great imho. If they really want to do it better than Apple etc., they seriously need to up their game - and I really wish they would, but I don’t see that happening, the cost is too high.
I started studying IT back in ‘99 and got a strict warning from the school my first year, because I had used the schools network to access the internet from my own laptop. I had “gained access” by plugging an ethernet cable into a random socket in the wall, and was doing some homework, when radom employee walked by. Since there wasn’t any rules (yet), that allowed nor disallowed it, I got of with only a warning ... from a school, that teaches IT :|
The comparison is somewhat skewed, since they went from an (expensive) virtual server to a cheaper dedicated server (hardware).
One of the new risks is if anything critical happens with the hardware, network, switch etc. then everything is down, until someone at Hetzner go fixes it.
With a virtual server it’ll just get started on a different server straight away. Usually hypervisors also has 2 or more network connections etc.
And hopefully they also got some backup setup.
It’s still a huge amount of of savings and I’d probably do the same of I were in their shoes, but there is tradeoffs when going from virtual- to dedicated hardware.
We've setup and used peer-relays since it was first announced and they've been great, but they do solve a somewhat specific problem.
Some of our users experienced fairly limited throughput from time to time. Under certain circumstances (eg. always ipv4 NAT/double-NAT, never for ipv6) their Tailscale client couldn't establish a direct connection to the Tailscale node in the datacenter, so data was relayed through Tailscales public relay nodes. Which at times was rate limited/bottleneck - in all fairness, that is to be expected according to their docs.
The first mitigation was to "ban" the specific public relay they were using in the policy. Which helped, but still not a great solution and we might just end up in a weird whack-a-mole-ish ban game with the public peer relays in the long run.
So we setup a peer relay, which networking-wise is in a DMZ sort of network (more open), but location wise still in the datacenter and allowed it to easily reach the internal (more restricted networking) Tailscale nodes. Which solved all throughput problems, since we no longer have users connecting through the public relays.
Also, the peer relays feels a little bit magic, once you allow the use of them in the Tailscale policy, it just works(tm) - there is basically zero fiddling with them.
EDIT: I'll happily provide more details if interested - we did a fair amount of testing and debugging along the way :)
Yeah, I'm already using nftables and I agree that it's better than eg. iptables (or the numerous frontends for iptables) and probably the best bet we have at this point - but honestly, it's still far from the UX I get from pf - unfortunately :/
Coming from FreeBSD and pf, all Linux firewalls I’ve tried feels clunky _at best_ UX-wise.
I’d love a Linux firewall configured with a sane config file and I think BSD really nailed it. It’s easy to configure and still human readable, even for more advanced firewall gateway setups with many interfaces/zones.
A have no doubt that Linux can do all the same stuff feature-wise, but oh god the UX :/
I’m sure they are trying and it has gotten slightly better lately - but it’s still not great imho. If they really want to do it better than Apple etc., they seriously need to up their game - and I really wish they would, but I don’t see that happening, the cost is too high.