That's what 8-bit text to speech was for, played from the PC Speaker for maximum effect. It sounded like Stephen Hawking choking on vodka, but that somehow fit the mood.
> It sounded like Stephen Hawking choking on vodka
I'm probably way, way overthinking this, but this seems philosophically quite deep and interesting, much like "what is the sound of one hand clapping" (ignoring Bart Simpson's masterful destruction of the ancient question).
If done correctly it doesn’t matter. SSR can yield an accessible HTML page and you won’t notice the difference. Client-side JS can adapt the web site to your needs -a personalization that is hard to achieve in static.
I have seen many sites scoring well on various accessibility metrics. There’s no inherent technical limitation of frameworks that would make accessibility impossible, even when dealing with text to speech. We will see many more next year with EAA coming into effect (and many European companies do care about compliance).
Despite regulation I don’t Believe it will actually get implemented even governments have regulations around audio accessibility for education in particular, for years now, and still nothing moves.
Accessibility of this page is pretty bad as far as I can tell, but not because it's plain HTML. And if I understand correctly you can mark ASCII art as an image (role="img") with alternative text too.
Hackers come in all ages, colors, shapes, and sizes. The ethos is one that is the very opposite of identitarianism. I would highly recommend getting to know more people in the community.
Also, I would guess that GP is making a joke based on a classic (and funny) stereotype.
There’s no such thing as single community of hackers with some ethos. Exactly because “identitarianism” isn’t their thing. The hats are of different colors.
GP may be making a joke, but you should read the irony in my comment too. From my experience people who disregard accessibility are often the ones who were never disadvantaged or discriminated. Hence the attributes I mentioned.
It does say "unauthorized", so I assume it should still be possible to get an official license to make a third party controller, though we'll have to see if that's actually going to be the case.
It doesn't have to be profitable for them. It can just exist, be the only option, and prevent others from making a competitive or superior product, forcing others out of the business.
It would be a shame if someone with a physical disability needed to find a different accessible controller for each platform they play on because each one only supports first-party controllers though.
I don't have a disability serious enough to need adaptive controllers like this, but I do have RSI, and when I find peripherals that I can use with minimal pain I stick to them. I have to imagine many with more serious disabilities would feel similarly.
This might be a sad day. Ben Heck has been making accessibility controllers for as long as I've been on the internet and I know the last few videos he's done on those have been based off a third party controller.
The other day they randomly changed the “Like” button for an “Add to Playlist” one. Though they did communicate that change pretty clearly (there was a popup notifying the user about this behaviour etc.), I think it was a horrible spontaneous decision. I’m glad they reverted the thing the same day it was rolled out. Why doesn’t Spotify add an opt-in for experimental features/updates or distribute an “experimental” version of the app through app stores?
The like button disappeared for me a while ago and was replaced by a ⊕ that adds it to the "liked songs" playlist. Are you saying your app still shows the heart button to like a song? Or are you talking about the thumbs-up button that was also removed at some point?
I liked the new add to playlist feature, at least on my iphone. I press it once to like the song and double press it to add to a playlist using a checkbox on a menu, and I can choose to take the song out of my liked playlist on that menu. This eliminated a few clicks and is easier while driving. Intuitive and easy to use once I recognized what they did.
Opt-in experiments carry a huge bias, which is hard to extrapolate to the general user base. As annoying as changes Spotify can be, at least it’s highly unlikely to be used for “important stuff” like emails or general business stuff. Easier to justify small annoyances.
and the like/add button doesn't have consistent placement or action. on some screens it still behaves as a like button and sometimes it's on the left. i had muscle memory to tap it and found i was disliking songs i wanted to like.
I find the Compose feature to be quite useful, so I used to have Compose key on Caps Lock on Linux. After I’ve switched back to Windows, I found WinCompose to be a pretty decent equivalent of Compose for Windows, and found out it can also override Caps Lock behaviour (though in about 1% of cases the default Windows Caps Lock behaviour breaks through for a brief moment) and reassign the Caps Lock function to some other, less frequent combination of keys. In my case pressing both Shifts at the same time acts as a Caps Lock toggle.
(edit: looked it up, and it seems to be a way to enter accented keyboard characters like é or ñ. It's standard on macos, and I guess in Linux you bind a key to it?)
Not really: shift must be used simultaneously and you only input a single key to be shifted, while compose takes a (“dead”?) sequence of inputs to be combined.
yes really. it's all the same thing. shift is just a simpler and more common subset. you are getting a glyph by composing from more than one key. whether ypu can let go of the key to do them in serial is immaterial. anyone could have an accessability setup for instance that allows shift to require only a single physical keypress at a time. It would still be shift.
It's immaterial if some key on some keyboard in some language happens to have a key that produces that glyph by composing with shift, or not.
If you asked how to type numbers, and I said "same way you type letters", that does not mean by typing "A" and wondering why it didn't produce "1".
The question was what is a compose key or what does compose key mean.
Shift is an example of a compose key that everyone is familar with, just no one calls it that. But everyone already understands what the shift key does. If you know what the shift key is and how to use it and what it does, then you know what a compose key is. It's that.
All the other possible compose keys just do exactly that same thing, just more of it for more and different glyphs and control codes.
I understand you mean compose as a generic term for a symbol modifier?
But for the compose key, the word composition is used as a synonym of combination, and that of a set of symbols; which is not the case of shifting each symbol into a corresponding set.
I agree that ctrl/alt/meta/shift are somewhat synonymous, and all those+compose are just instances of modifier keys.
But this combination meaning is specifically what makes the compose-key distinction useful and clear.
To get a particular glyph, or control code, you have to compose it out of multiple keypresses.
Some common examples happen to be modified versions of whatever glyph happens to be on a key, but that is just a subset, arranged that way for human sanity, humans would hate it if you had to press shift+g to get A, and really only in the latin languages whose writing even works that way. The glyphs could actually be anything, and outside of the latin languages they are. The poop emoji is not a modified form of any number or letter.
And it's not even just glyphs but any byte or byte sequence you want to produce. A single 0x01 byte is not a glyph, nor a modified form of any glyph, but you can still type it, and it's composed of the CTRL key and the A key.
You’ve misunderstood. No one said that they were equivalent, only that there was no functional difference between them. They certainly allow you to access different characters, but whether you hold down shift and then type a “d” to input a capital “D” or you tap shift and then tap the “d” to get the same result is merely a software setting that you can toggle. The same is true for AltGr and compose keys. You can configure your OS to require them to be typed as chords or as dead keys, whichever you prefer.
Nice! There’s a similar project by Anthony Fu: https://icones.js.org
I wonder if both share the same superset of icons, relying on the same Iconify framework?
I feel like the HN title here is misleading. You can’t delete your Threads profile, you can only delete your Instagram account and your Threads sub-account will follow.
Also this is quite clearly stated inside the Threads app: “Some settings, such as deleting your account, apply to both Threads and Instagram and can be managed on Instagram”.
Deactivating your Threads account, on the other hand, will not affect your Instagram account in any way, this warning is there in the corresponding Settings section as well.
