RX-69 🍕 Gundam @rrix@cybre.space

Logging off this fucking web site for a while, find me on matrix if you need me.

let's play bzip2 -9 youtube.com
5749 views

made a thing for seattleites https://afd.fontkeming.fail/

Yesterday I rode a bike down to West Point Lighthouse at the far edge of #Seattle 's Discovery Park. Poured myself a few cups of Japanese black #tea and hiked out.

e

there is no cloud, just someone else's on-prem

https://cybre.space/media/MIYze1kiokyuYJjKvL8

it's been

To be clear: DNS over HTTPS allows privacy violating libraries to side-step the host APIs for domain resolution and implement it themselves, with their own servers. Users using DoH to escape censorship regimes or ISP nuttery is something we *should* solve for, but not at the cost of user agency.

Fundamentally, I believe that users should be able but not required to control traffic that enters and leaves their devices. This should be a fundamental right every person with a connected device should be allowed to excercise.

Corporate interests that increasingly have the loudest voice in these discussions don't seem to hold that view, and the long term prospects of internet users' safety and autonomy are increasingly worrying me

https://blog.powerdns.com/2019/02/07/the-big-dns-privacy-debate-at-fosdem/

My take on DoH is that it will end up being used in a user-hostile to prevent DNS-based ad/tracker blocking solutions like pihole. With DNS over 53/UDP, DNS based ad-blocking solutions are a trivial firewall rule that can be made even on consumer routers.

With DNS over TLS, it's only a matter of time until adtech vendors and other privacy-invading beacons are using DoH/DoT to prevent users from inspecting & blocking these beacons through certificate pinning + traffic obfuscation.

have a cup of tea

How much bandwidth is spent in a year sending the text "(KHTML, like gecko)" over the internet

the emacs web wowser is not like gecko

khtml, like gecko

It's a party.

https://cybre.space/media/PwB3eiNfUNvruwZTl2k