Notices by curtmack (curtmack@floss.social)

@mcc Well they can't very well live at the bottom of the ocean *without* the tubes, now can they?

Every now and then, I'm reminded that this product exists, and I feel a slight tug pulling me towards it. Like "the call of the void."

It's like a Razer Tartarus for people who know that God is dead and everything is permitted.

@errorbody @spritely I see what you mean, but to me it's pretty clear she's pointing back behind her.

So, to recap: it is the opinion of Chrome's and Edge's developers that they can ignore autocomplete="off", and any workarounds you deploy today may not work in the future. In fact, the only reason they recognize that a website would want to disable autocomplete is... to provide its own autocomplete implementation.
Chromium delenda est.
https://karsep5.hashnode.dev/browser-autofill-for-web-developers
#webDev #wtf

A fact that should be obvious to all web developers, but would apparently be mindblowing to the Chrome developers who made this decision:
Sometimes, a web form asks for a name, date of birth, etc. for a person, and it is expected that this person is not the user of the application.

I found it! It was in a DEF CON talk on homograph attacks by The Tarquin from 2018:
https://youtu.be/Ec1OOiG4RMA?t=122

"Remember, 'Unicode' is the name of the consortium, the encoding standard is called 'Unicode's monster.'"

- Stolen with ❤️ and 🤗 from a conference talk that I can no longer find

@alcinnz A fun trick I learned from a blog post by a game dev (Factorio, I think) is that you can use Djikstra's algorithm over a coarser map, and then use that as your heuristic function for A* on the detailed map. If the coarse map is cheap to produce, or if it only needs to be updated rarely, then this can be a huge improvement over using Euclidean distance as your heuristic, as it quickly routes around lakes and other large barriers.

@mcc I had a dream that I was cuddling with a cat who was somehow tangentially related to the latest Stallman report, and I spent a long time trying to decide if it was okay for me to cuddle the Stallman cat before realizing it was, in fact, my cat, and she had crawled into my bed to cuddle with me.

So far, GitHub users have found that Winamp's "community" repository:

1. Originally had a comically non-free license, so they replaced it with a license that's still not free
2. Accidentally committed the source code for an entire separate product they own
3. Revealed they are violating the GPL and likely have been for years
4. Also included proprietary code by Dolby *and* Fraunhofer for good measure

Incredible. They should have sent a poet.

@foone Meanwhile, DOOM: 🫠