“Scrollbars are becoming a problem”
The current state of scrollbars is, on the face of it, objective evidence that the people who run tech do not give a single solitary fuck about usability or UX https://artemis.sh/2023/10/12/scrollbars.html
This is exactly the kind of safety initiatives the world—and #rustlang specifically—needs. Capability based access control should be built into Cargo, but this is probably the next best thing.
https://davidlattimore.github.io/making-supply-chain-attacks-harder.html by @davidlattimore
Folks, i'm still looking for work -- either freelance or FTE.
I'm a full-stack web developer with a focus on PHP CMS-based systems (mostly CraftCMS and ExpresionEngine, some Wordpress, a smattering of Drupal). Also on the back-end: Laravel, Symfony, some Yii. On the JS side, i do mostly vanilla JS, some Vue and other smaller/less-intrusive frameworks (please don't make me do React!) I also write solid, semantic, accessible markup and CSS (by hand) and care deeply about accessibility in general. I'm also a fiend for content architecture and i love SQL!
If any of this sounds like a match for any project or opportunity you've got in mind, PLEASE let me know!
i have outright deleted a major patchset i wrote for a project under freedesktop.org stewardship, which someone else is probably going to write again in a year or two, because i realized the project had a real-name policy, and decided it wasn't worth it. i then lost motivation for the cool thing i was working on that needed me to write that patch
this is not the intended effect of a "real-name" policy, but it is the actual effect. and, as the cool kids say, "the system is what it does".
there is no such thing as a "real name". the concept of a "legal name" is fraught, and most certainly is not what you think it is, or what you are looking for, if you are a software developer. many assumptions you have about what a "legal name" is probably are not true.
consider this: the name on my birth certificate is different than the name on my drivers license, and that is different from the names i am called by my friends. those names are all different from what is likely to be on my passport when i get it, and all of those are different than the name i publish my open source projects under. all of these, in different jurisdictions, might or might not be something you could consider a "legal name". which one do you want me to use when i submit a major feature to your library? are you going to turn me away if i try to submit it as "linear cannon"? why? if i have a website and contact information under that name, why does this matter? how is it substantially different than an author of fiction novels publishing under a pen name? does it change if i produce a piece of government-issued documentation with that name on it? why, or why not?
if your real name policy does not answer these questions adequately, then there's a very good chance i'm just going to assume that you're going to turn me away, as has happened to me several times already
@eniko people always bring up this point and I think it's slightly missing the point, because the fact there isn't a single "real name" for a lot of people is part of the entire point of "real name" policies.
These policies are made to exclude those people. That's part of why they exist. They're made by people for who the question of a "real name" is easy to answer, and to keep out people for who it's not easy and simple.
"real name" policies are evidence that there are people in charge who have never moved to another country
you wanna know what my real name is? according to whomst, exactly? hell in the US various federal orgs couldn't even agree on what my name was supposed to be. no, scratch that, even the social security administration, internally, couldn't agree on what my name was and changed it like 4 times over a 6 year stay
curl bug postmortem: https://daniel.haxx.se/blog/2023/10/11/how-i-made-a-heap-overflow-in-curl/
to spell it out very clearly: curl, the command line utility, is not vulnerable in its default configuration because it happens to configure libcurl in a way that avoids this bug. But other applications that include libcurl are likely to be vulnerable
Gender is a lot like operating systems. People always assume you use one of the two big proprietary ones and if you don't, you're gonna have to deal with a lot of confusion and compatibility issues. On the plus side you get a lot more customisability and don't have to care about bullshit policies of the proprietary options.
ohhhhhhh i hate how everything tech in movies now is just holograms. no theory of interface, just "we'll get it in post." an article of convenience rather than speculation, untethered from the material conditions of reality
oh, and your regular reminder that if you want to help me keep doing stuff like this, https://liberapay.com/hikari_no_yume/ and https://github.com/sponsors/hikari-no-yume/ are two ways to do that. I'm very grateful for any support.
at long last, I am pleased to announce the "touchHLE app compatibility database"!
instead of a manually curated "app compatibility list", there's now a database that anyone can contribute to. if you find an iPhone OS 2.x app that works, you can add it!
some notes:
btw, I wrote the web app over the last 10 days and it's open source ^^ https://github.com/hikari-no-yume/app-compatibility-db
Trans woman, bisexual, someone's fiancée, forever a programmer, poly, and former total mess
Avatar by mavica