An interesting #UX lesson from a *very* old blog post by, I think it was Yahoo?
Never do total UI overhauls. Instead, take your "target UI", the thing that you're trying to work towards... and just change one thing. A single thing. A small one, that's easy to get used to.
Next week, do the same. The week after that, do the same. Introduce the changes very gradually and very slowly, so that the end user never feels lost, and never suddenly has to adapt to a new UI to get their work done. Ideally they shouldn't even notice the change.
There's a reason that so many especially older folks kept insisting on using Yahoo services, despite the severe mismanagement within the company.
i wonder if the disdain for stuff like frontend as "not real programming" etc just harkens back to [contempt culture](https://blog.aurynn.com/2015/12/16-contempt-culture), or what other factors are involved
Likewise, I think 'fake' vegan minced meat may now be cheaper than the real thing (though it's still of extremely questionable quality)
(Corollary: packages that boast "zero dependencies" on average tend to contain far more bugs and even security issues than equivalent packages with transitive dependencies; which is not that surprising, when you consider that this means it'll be reinventing a lot of wheels inline)
As a bit of extra background: I've been professionally auditing (probably thousands of) FOSS dependencies for years now, in a high-risk environment, and *not once* have I run across deliberately malicious code, not even questionably broken code, really.
Every single issue so far has been a security issue, none that were likely to be disguised backdoors. Many of them very common security issues that most developers are likely to create themselves when reinventing wheels (eg. when avoiding dependencies out of a misguided fear of malicious code).
That's where the *real* risk is.
This also feels like one of those cases of the metaphorical-law-I-forgot-the-name-of, where people perceive an uncommon event as being really common because it's so uncommon that it gets widely reported every time it happens, and therefore skews people's perception of its frequency
And no, it's not *just* security folks overestimating the threat level, tons of software developers do it too (and often at the same time overlook the things that are *actually* dangerous)
Pleroma TERFs & Nazis
This is why I have a general distrust of Pleroma users. I don't care that it is "more lightweight" than Mastodon. I don't care that it has extra features and multiple frontends.
Its Nazis all the way down. Even the official Pleroma website recommends Nazi-friendly instances, and their devs are openly friendly with out-and-proud Nazis.
Quite a few games these days use chromatic aberration filters as a "wow, trippy" effect and I wish they wouldn't because with my glasses everything not directly in front of me already looks like that.
I've seen cases where something in the corner of the game screen was chromatic-aberrationy and my glasses reverse-aberranted it back to normal.
Technical debt collector and general hype-hater. Early 30s, non-binary, ND, poly, relationship anarchist, generally queer.
- No alt text (request) = no boost.
- Boosts OK for all boostable posts.
- DMs are open.
- Flirting welcome, but be explicit if you want something out of it!
- The devil doesn't need an advocate; no combative arguing in my mentions.
Sometimes horny on main (behind CW), very much into kink (bondage, freeuse, CNC, and other stuff), and believe it or not, very much a submissive bottom :p
My spoons are limited, so I may not always have the energy to respond to messages.
Strong views about abolishing oppression, hierarchy, agency, and self-governance - but I also trust people by default and give them room to grow, unless they give me reason not to. That all also applies to technology and how it's built.