If your #blind, #signal does nothing to protect your #privacy. They use #hcaptcha, so if you can’t see the images, you have to enable cross site cookies and give them a valid email. And if you want to contact signal about it, sending your device info via unencrypted email is the default way. This is not how privacy or #security work. You’re better off with iMessage. Or even watsapp! At least they don’t hand your data over to a third party captcha provider. Or send your device info via unencrypted email.
Edit: thanks to the fediverse, I was alerted that Signal can be contacted in other ways. But you have to go look for them; pressing the "get support" button in the app sends an unencrypted email with a link to your device logs. I have edited this post for accuracy. #infosec#a11y#accessibility
@fastfinge@HNguyenLy Aren't they still allowing the text-based captcha? They certainly used to allow this. I know because I'm the reason it was turned on.
@fastfinge@HNguyenLy Hmm. When I signed up for Signal I didn't have to fill out a captcha. I wonder if I could reproduce that enough to file an issue and make some noise about it. I used to have contact with a very active developer but I think he left the team. He is the reason the desktop app has so much semantic markup now, though it's still not perfect.
Wow, another reason I didn't need to not like Signal. We host our own XMPP system but until just now, I'd never thought about having a blind users on it... You got me thinking about if blind folks can even use our OpenFire server now 🤔 thanks. 😊
@fastfinge No surprise there. I went on a Hell Captcha rant not too long ago. My DNS provider decided to implement it on all login requests, not just failed attempts after a threshold.
