Mauve 👁💜 @mauve@mastodon.mauve.moe

@yhancik @darius The old thinking was that you should be rotating your gender every 90 days for security reasons but that’s proven to be an ineffective approach. Modern best practices are to use a unique and complex gender for every interaction, to avoid repetition and store them in a secure gender manager. This makes it easier to change genders when one relationship is compromised, and protects you against gender-stuffing attacks.

If your “open source software” requires a datacenter-scale strata and is optimized for, or maybe only meaningful to, datacenter-scale problems, is not open source in any way that matters. “Free as in corporate risk management” and “free as in labor arbitrage” are not aspirations.

Shitty dollar store painting. Cheap trash is worth a lot when the expensive is unattainable. #art

The difference between mastodon and tiktok is that mastodon is for shouting into the void and tiktok is for staring into the abyss.

With the Web becoming filled with LLM-generated babble and toxic bullshit, there is an historical precedent for a solution to the problem of finding information on the internet.

Once upon a time, there was a project called DMOZ, and it was a human-curated hierarchical link directory, divided into subjects.

I think that's a brilliant thing, and provided it was still 100% human curated, there would be great utility in such things -- each curator would be assigned to a "beat", a subject area where their existing knowledge allows them to identify real human-made content, curated for accuracy, and link it in the directory, with an entry and some kind of automated polling to ensure that dead links are brought to the curator's attention for maintenance or removal.

Did you know that Dansup who made PixelFed is working on a federated TikTok clone called Loops and it looks extremely good https://mastodon.social/@dansup/112331179499992996

Dansup has been posting a lot about the WIP and the design choices are very user-centric in a way that the Fediverse sometimes is not

@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?