Mauve 👁💜 @mauve@mastodon.mauve.moe

@futurebird This is a good question and I wish I had an answer. The closest thing I have (it's an old book— it's been a while since I've done much Java) is "Bitter Java". It maybe is a slightly more advanced book, but. It is a book by a consultant who comes in to fix problems in other people's code. So it's all about "here's things people do wrong in Java— here's how to do them better". It's a very odd book, more philosophy than code, one of the best pieces of CS writing I've ever read actually.

Here's a brilliant neologism: "slop", for text generated entirely by LLMs and published, unwanted, on the Internet

> Watching in real time as "slop" becomes a term of art. the way that "spam" became the term for unwanted emails, "slop" is going in the dictionary as the term for unwanted AI generated content

Source: https://twitter.com/deepfates/status/1787472784106639418

Dunno if some dipshit will call me posting this FUD again, a mere week after the last time I said it. But once again: if you build your business on top of anything offered by Google in virtually any way, you are in "fool me seventeen times" territory here. No company has indicated its disdain for the developer ecosystem to the degree Google systematically does.

Everything that doesn't pull the revenue of Ads is eventually killed, and nothing pulls the revenue of Ads.

https://arstechnica.com/gadgets/2024/05/google-fit-apis-get-shut-down-in-2025-might-break-fitness-devices/

.....here's a hot take:

Phishing tests are a symptom of a failed security department.

If you 'need' those in your workflow, then you have failed to implement proper anti-phishing controls. You have failed to implement correct MFA. You have failed to implement telltales for message provenance. You have failed to filter spam and malicious traffic. You have failed to isolate services. You have failed to incorporate proper logging. You have failed to protect your coworkers and you are lying to them instead to cover up your continued failures.

Blue teaming is about -protecting- the users so that they are able to carry out their work in the high-trust environment required for effective collaboration. If you fucking -lie- to them, that cannot -happen-.

The question of whether CSS is a programming language serves only one purpose: to demote those who write it.

There is no confusion that needs to be clarified, and no other purpose in asking, beyond the most trivial kind of pedantry.

The debate itself is an act of gatekeeping, whether intentional or not. Its only significant effect is to elevate some work over other work, despite their essentially identical nature.

The only meaningful function of the question is segregation. #css

I am officially Totally Over Tailwind and I can't see myself using it again. Plain CSS really is so much nicer when you know a bit about what you're doing. My markup is so much easier to handle and read now. Everything's just... simpler and less noisy, and I can make big appearance changes without having to change a bunch of non-CSS code?

I am very pleased to be able to share that I've been awarded a grant by NLnet Foundation's #NGI Zero program (@NGIZero)

You can read all about it in my most recent blog post: https://cryptography.dog/blog/announcing-webxdc-evolve/