Dusty @ChlorideCull@fuzzy.systems

big if true

i did a funny

nintendo told steam to remove dolphin from their store, allegedly due to it's hardcoded inclusion of the wii common key

so here's a flag that represents the wii's common key, in hexadecimal form :)

EDIT: oops inkscape fucked it up in the export, i fixed it now lol
EDIT 2: fix'd info, everyone was wrong apparantly! doesn't change much but still

Deno: we can build an executable!
Me: Oh, that's cool how big is hello wor--

Deno: 69MB
Me:

Developer: "We don't need to write documentation. Users should obviously know what to give as input. "

Users:

So I just got done playing Mortal Kombat on my iPhone, and I wanted to unpack my thoughts on it, mobile gaming, and accessibility across mobile systems. So, I never thought I'd ever be playing Mortal Kombat on my phone. I mean, this is a little iPhone SE 2 with 64 GB storage and 3 GB RAM. And yet, on my AirPods Pro 2 even, I'm able to win fights, in the classic combat tower thing. My account is at like level 11, and I was able to even drag my Fujin card to be my main team member. Your main is in the middle, BTW.

Anyway, look at this though. The whole time, from navigating the interface, and in battles, VoiceOver is on. The app uses a Direct Touch Area during battles, then switches to an interface view when done. So, during battles, a tap or swipe is sent to the app, but the app can still send text to be spoken by VoiceOver. Then the interface is navigated using VoiceOver's usual commands. This isn't using some self-voicing screen reader made by the devs. And while one *could* do that on Android, the user would have to turn off TalkBack, and the game creator would have to design a whole self-voicing interface for the thing. And y'all know what? That's fucking sad. It's sad that people with Android can't play a game cause Google can't possibly have spent resources over the last ten years to make frameworks that devs can make intuitive, powerful, seemless experiences with. And I'm not saying this game is perfectly accessible either. It'll tell you VO functionality on the iPhone isn't perfect yet. But on the iPhone, game developers can use this stuff, and Injustice 2, not the original, has this kind of stuff too, although I wasn't able to get far into it. And if big studeos like NetherRealm can do this much, it ain't because it's the right thing to do as much as it's gotten easier and better to do this. The iPhone can *definitely* be a great gaming system, even for blind people.

#accessibility #iOS #apple #MortalKombat #android #google

I will never, ever stop loving Bill Atkinson’s dithering algorithm. If you cut your teeth on Macpaint or Hypercard, you probably recognize it without even realizing it.

Noticed that mastodon.social has become the origin of bot spam waves? This was all Gargron's plan when pushing mastodon.social as the entry point for the Mastodon Network so there is only a single instance to block to get rid of the spam. Thank you for the sacrifice ❤️

Don't try to minimize the amount of open issues in your issue tracker! Issues are *contributions* from users, telling you about problems that you were not aware of yet - they're not pests to get rid of.

Closing issues without either solving them or a good(!) reason why they won't be fixed - for *any* reason, including stalebots - will just sour people on your project. They won't tell you that; they'll just stop showing up. And the issue still won't be fixed.

Instead, treat your issue tracker like a priority queue: accept that you're never going to get to zero, accept that some issues will remain open a long time because they are not urgent, and find a good way to order the list by your criteria of importance.

Work on things as time permits, in order of importance, communicate this to users, and establish a good rhythm of bugfixes that users are happy with even if *their* specific bug isn't fixed yet.

There are a lot more useful thoughts on this topic in this article: https://apenwarr.ca/log/20171213