That is fine. We are as a matter of fact polyamorous and both bi. So, feelings free to join
That is fine. We are as a matter of fact polyamorous and both bi. So, feelings free to join
*american people
There, fixed it
I get your point. But to be fair: for landlords where massive subventions in place. This program ended amd was not renewed because of lack of interest.
But at least for new buildings, a policy to force charging stations at every parking lot would be a good idea
I totally forgot one essential fact: the reason for DNS over HTTPS itself was perfectly valid: ISP’s in the US are using DNS lookups of their customers for advertising. The idea is to prevent this kind of privacy breach. And it is very effective against it.
Just rye ideological driven implementation was bs
Sure, Firefox introduced a security feature: DNS over HTTPs. So instead if asking some DNS server that is configured on the local system, for the IP that belongs to a Domain name, am external service is asked via HTTPs.
While this is in theory a good idea, and has some benefits, the Firefox implementation was bad:
Users, that where forced into DNS over HTTPS could no longer resolve internal hostnames. This was a killer in office environments. And after the fix for that, everything was first submitted to cloudflare and only if cloudflare could not resolve the hostname, the local DNS server was asked, leading to potential information leaks. Also a no go for companies.
Firefox has fixed these issues by providing privacy policies, the option to choose other DNS over HTTPS providers and the option to define what domains should never be resolved externally.
But they lost trust in many professional environments because of that move.
Another answer: Netflix
While the Mozilla foundation had designed browser DRM that worked on Linux, Chrome has the first implementation. And that enabled Linux users to watch Netflix.
Next one: forced fucking cloudflare DNS over HTTPS. I dipped Firefox because of that.
As shitty as google behaved, that was a nono
At least here in Germany it is opt in. As the algorithm runs locally, I don’t see a big issue with this.
I didn’t opt in to this feature to be clear, and ghostery should help for tracking.
But if I wouldn’t have this option, I would be more willing to have my history evaluated locally, instead of having my history evaluated for 90% of the sides on some third party advertisers owned system.
Let me get this straight:
Until now, Google and other advertisers stored cookies on your device and tracked your browsing history on their servers.
Know, everything happens locally and this is somewhat worse then the old way to do it?
How?
Tuya requires cloud access and the API’s are on their way to be paid only.
Only use tuya zigbee. Keep away from wifi devices at all costs!
If you are by any chance some day near Zweibrücken/Landstuhl/Pirmasens give us a message and maybe we will grant you some time with our machines and stuff ( ͡° ͜ʖ ͡°)