Notices by f (f@todon.nl), page 5

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.

Here's an idea: a #NoJS challenge.

Making a website? Avoid using JavaScript.

See how much of the functionality and design you were planning can be done using plain HTML, CSS and other web technologies that are now embedded in the typical browser without needing JavaScript code to do any of it.

Even if it seems impossible, look it up. It just might be possible.

There's so much stuff in there now, even a seasoned webmaster could be surprised.

The Pedagogy of Intersectionality

Facebook splits up the word “sponsored” to sneak past adblockers

Alternatives To Dispersions

Looking forward to giving a talk on Why Open Source? to a local business. One of the reasons will be:

"Because your developers say so, and if you don't do as they say they'll go work for someone else."

I'll sugar-coat it a bit. But this is a real reason many businesses support FOSS. It's worth calling it out, both as real talk, and to remind the devs in the audience they have power.

The great thing about being an anarchist is I can flat-out say "I'm just an anarchist" to my coworkers during a political discussion and since the term has gotten so watered-down and idiomatic that they all just nod

"cena familiar cancelada por que se rompió el Outlook" gracias Microsoft

Cowmen and Marx: Collected Lectures

when you see a website that's HTTPS rather than HTTP, it means the connection is secure. most popular browsers will display a green padlock in the URL bar to symbolise that (and colour it yellow or red if something's wrong).

to verify that a connection is secure (and not just someone saying it's secure), you need a certificate, a file that verifies that you are who you say you are.

a certificate can be revoked at any time by anyone. you can deny facebook's certificate if you like, and facebook will stop loading for you. more importantly (and practically), the issuer of the certificate can deny it, and the site will stop working until they get a new one. this means that if facebook "goes rogue", the CA (certificate authority) is allowed to remove their certificate, guaranteeing (in theory) that if the site is HTTPS, it's definitely secure.

these certificates don't last forever. they need to be renewed, to prove that you're still there and still complying with them. gargron had certificate auto-renewal set up, which means the certificate will automatically get renewed when it's close to expiring. so why did the cert expire? why did .social go down? the answer is because while a new certificate was installed, it wasn't actually loaded. nginx, the server software that .social uses, was supposed to automatically load the new cert, but it didn't for some reason (computers are weird!), and thus .social went offline for about an hour.

#LynneTeachesTech

The Return of Lenin

*se va de su burbuja progre por tipo 2 segundos* uy la gente es una mierda