

I was going to post this exact reasoning but you beat me to it.
I was going to post this exact reasoning but you beat me to it.
It’s an industry security standard. Not a defect. If you don’t agree with it, fork the software and modify it to suit your needs.
Some self hosted services refuse to work if you use a self signed certificate with your public facing IP. They only allow self signed certificates when using one of the handful of private addresses.
Some apps on mobile devices for the service you use won’t work unless a trusted certificate is used. A self signed certificate behind the scenes creates an error that isn’t handled and you can’t connect.
You lose the ability to have a proxy in front to handle abuse so your server is spared the headache. You need a domain to do this.
TLS.
While technically you can use TLS with a self signed certificate, it creates additional problems with a public facing service. Only recommended for internal services.
This reference will never get old tbh.
Interestingly, that site is owned by ESPN and at some point in time it was archived by ABC. Why it was put to use for this is strange.
I was under the impression that Tahoe translates to “big water” which is funny.
But “Tar pit Tar pit”, “Way Way” and “Desert Desert” are indeed infuriating.
No. It’s not neutral like a car. The transmission is still engaged, thus cranking the pistons up and down in the engine. With no oil flow from the systems, it’s not very friendly to the metal bits inside. Lol
You either set the DNS settings per device to the system running PiHole / AdGuard Home, or if your router allows, set the DNS there. It’s ideal to set it on the router.
Any time a device makes a DNS request to a domain, it’s checked against the list. If found, it’s stopped. If not found, it gets sent upstream to your choice of a public DNS configured during setup. I use Cloudflare (1.1.1.1, 1.0.0.1).
Generally, big releases bring bugs that may not have been caught during development. And sometimes a change or fix was planned but deferred until later.
Think outside the box. Get a previous generation. Pixel 8 was about to be released. To move inventory, Google discounted the 7 series by like 30-40%. I got the 256GB 7 Pro for $600. Without the sale, $600 is the same price as the 128GB 7. I got a top of the range flagship phone for the cost of a midrange. My mom did something similar with a Samsung phone. She got an S20 when the S22 released. Huge discount when Verizon offered it for $449.
Our taxes at work. I’d much rather defund Israel and just continue supporting Ukraine. Take all that money we send to Israel and use it to fix our own problems.
I’m finding it hard to believe this statement.
System wide DNS over TLS (DoT) as it’s called “Private DNS” was introduced in Android 9. Which was released in 2018. I’d genuinely like to know what Android device today ships with 8 or older, or, ships with 9 and later but has it intentionally removed. If you’re still using an Android device running 8… Why?? It has not received security updates since 2021 and is officially unsupported.
iOS devices can import certificates to enable system wide DoT. This was introduced in iOS 14. Which was released in 2020. Given how Apple has a 7 year track record for device support, the oldest Apple device to get 14 was the iPhone 6. Which shipped with iOS 9 on release.
- Nissan Versa - 16.925
- Kia Rio - 16.75
Cool, so three. That’s still abysmal. The others don’t count once you factor in tax and title. It puts the total purchase price over 20k.
Just throwing it out there: There’s only one new car sold in the US below 20k. The Mitsubishi Mirage.
All these conspiracy theories are fascinating to me. I legitimately read them all and think to myself “How do people come up with this!?”
but the containers are still running as root, as the daemon itself raises the access to root.
No. The daemon can run without root, as such the containers don’t have root. My docker install doesn’t have root access. None of my stacks / containers need any root access tbh. I don’t have any troubles with deplyong stuff.
As of 2020, Chromium was made more permissive in accepting additional code. Before this, Chromium rejected a lot of outside code. Microsoft is now the biggest contributor outside of Google. Samsung, Intel, ARM and Apple are other notable contributors. There are several features found in the code that aren’t used by Google at all. Chrome is 100% Google’s agenda. Chromium does include Google services that Google rejects the removal of. Of course Google would rather you use them. Microsoft just removes them. As do others. But the features others have submitted to the Chromium code are of course used in their forks and possibly others. I would say Chromium is less of Google’s agenda than it used to be. As it’s not entirely neutral, there is still Google influence behind it.
If you’re interested at all:
Google Chrome is a fork of the open source Chromium with several Google proprietary features. Chromium uses the Blink engine. Blink is a fork of a large component of WebKit called WebCore. Apple primarily develops WebKit (and by proxy WebCore), itself being a fork of KHTML and KJS which were actually discontinued this year.
TeamSpeak is doing an overhaul to be similar to Discord. You can self host.