4 ms·
> I’m using an Hisense A5 Android phone. OK, but that puts you in the 0.0001th percentile of Signal users. Don't expect them to spend a lot of time debugging i
by rafram 4y ago
> I’m using an Hisense A5 Android phone.
OK, but that puts you in the 0.0001th percentile of Signal users. Don't expect them to spend a lot of time debugging issues with your very exotic phone.
> Signal is for everyone but you need to answer those idiocy first. It should be noted that I have a very good eyesight. I cannot imagine those with even minor disabilities.
Captchas pretty much always have audio alternatives for blind users.
> That’s also why I’ve always fought for the right to differences, why I’ve always been utterly frightened by "normalisation". Because I know nobody is immune. Think about it: I’m a white male, cis-gendered, married with children, with a good education, a good situation and no trauma, no disability. I’m mostly playing life with the "easy" setting.
Right. And if a bug in the Signal app convinces you that you've finally experienced oppression, you really need to read up on what oppression means.
- omniglottal 4y agoWatch out, big brother, for ignoring the fact that this user experience is not from the unique phone, but is about universal for all those not running Google Play Services. Your regurgitation of dogma without having honest context - it's oppressive. Couple questions: how does the audio play without JavaScript? Who serves that? How about the fact that the standard workflow just failed? If that is a bug, it would be fixed - right now, it's a feature, no?
- rafram 4y ago> how does the audio play without JavaScript? The HTML <audio> tag. > Who serves that? Whoever serves the captcha. Often that's Google, because they run ReCAPTCHA. > How about the fact that the standard workflow just failed? If that is a bug, it would be fixed - right now, it's a feature, no? The bug was fixed immediately. As the blog post says: "The bug was acknoweledged by the developers and fixed promptly."