3 ms·

I know there were/are a few blind people working on Mozilla's stuff and the move to anything that is not open source will make it much harder for them. There wa

I know there were/are a few blind people working on Mozilla's stuff and the move to anything that is not open source will make it much harder for them. There was a person[1] who had done significant work on the Rust compiler and said that he would have a much harder time doing it now, since the move to Discord and that he might not be able to participate in the community after the switch[2]. Proprietary solutions are a little bit better for the 80% of people, but way worse and/or unusable for the 1 to 5 percent, depending on how techy the community is. We have to realize that those solutions have big gains, but they also have huge tradeoffs. IRC inconveniences some people. Discord excludes some completely. [1] http://camlorn.net/posts/April%202017/rust-struct-field-reordering.html http://camlorn.net/posts/April%202017/rust-struct-field-reor... [2] This thread https://twitter.com/camlorn38/status/1121879891035602945 https://twitter.com/camlorn38/status/1121879891035602945

ohithereyou 8y ago
It's really frustrating to me how inaccessible Discord is. At its heart, Discord is text and voice chat, which you would think would be the easiest forms of communication to make accessible. Due to a genetic condition I have that predisposes me to blindness I have preemptively installed NVDA on Windows and Orca on Linux, and the inability of either of these tools to deal with Discord the last time I tried is shameful.
spicytunacone 8y ago
Bryan Smart's reply to that Twitter thread depresses me. >Don’t worry. They’ll totally fix Slack and Discord around the time everyone is using VRChat and VisualTeam. It’s always been this way. Accessibility is catchup work. The next big thing always destroys our gains. The language at the end of the blog post "We are evaluating products, not protocols" and "We aren’t picking an outlier" almost guarantees we're looking at solutions as heavy as Slack and Discord which I would not have been able to run on my laptop back when I was involved in the switch to Firefox Quantum. It's challenging enough having to advocate for "niche" (my words) features and work out their implementations, but IRC was also necessary to keep track of which builds on what dates would introduce which breaking changes, since this information was published nowhere else, and also to minimally participate in decision meetings that ended up in video chats anyway. If they do move to a heavier, but closed, solution, I hope they also find ways to make contribution less reliant on chat. For what it's worth, I thought Mozilla had a fairly decent wiki page for IRC[0]. I always believed a streamlined quickstart section, suggesting one or two clients at most, walking through steps to registration and configuring authentication with ghost killing, and how to get activity from when you were offline either via bouncer or just logs[1] would more than adequately address ease-of-use without rolling out a newer, modernized client. Even working from libraries wasn't an issue for me using web-based clients like Kiwi IRC. [0]: https://wiki.mozilla.org/IRC https://wiki.mozilla.org/IRC [1]: https://mozilla.logbot.info/ https://mozilla.logbot.info/

ohithereyou 8y ago

It's really frustrating to me how inaccessible Discord is. At its heart, Discord is text and voice chat, which you would think would be the easiest forms of communication to make accessible. Due to a genetic condition I have that predisposes me to blindness I have preemptively installed NVDA on Windows and Orca on Linux, and the inability of either of these tools to deal with Discord the last time I tried is shameful.

spicytunacone 8y ago

Bryan Smart's reply to that Twitter thread depresses me. >Don’t worry. They’ll totally fix Slack and Discord around the time everyone is using VRChat and VisualTeam. It’s always been this way. Accessibility is catchup work. The next big thing always destroys our gains. The language at the end of the blog post "We are evaluating products, not protocols" and "We aren’t picking an outlier" almost guarantees we're looking at solutions as heavy as Slack and Discord which I would not have been able to run on my laptop back when I was involved in the switch to Firefox Quantum. It's challenging enough having to advocate for "niche" (my words) features and work out their implementations, but IRC was also necessary to keep track of which builds on what dates would introduce which breaking changes, since this information was published nowhere else, and also to minimally participate in decision meetings that ended up in video chats anyway. If they do move to a heavier, but closed, solution, I hope they also find ways to make contribution less reliant on chat. For what it's worth, I thought Mozilla had a fairly decent wiki page for IRC[0]. I always believed a streamlined quickstart section, suggesting one or two clients at most, walking through steps to registration and configuring authentication with ghost killing, and how to get activity from when you were offline either via bouncer or just logs[1] would more than adequately address ease-of-use without rolling out a newer, modernized client. Even working from libraries wasn't an issue for me using web-based clients like Kiwi IRC. [0]: https://wiki.mozilla.org/IRC https://wiki.mozilla.org/IRC [1]: https://mozilla.logbot.info/ https://mozilla.logbot.info/