I'm kind of worried that people think changing a date format is the same amount of work as changing themes (which rely on someone having the time to be/learn an artist, check colorblind/contrast/etc, work with all 9 browsers or whatever) or accessability features (which would need to work with every implementation of the accessability frameworks of each OS)
Twitter not having it is inexcusable, same with tumblr, bluesky, Facebook. but like, even mastodon can't be expected to implement them on a timeline thats nearly instant. they aren't places with teams that know the tools, that come in just to work on that. There's still the day to day, there's still the need to drive growth until a critical mass is reached, and then the pile gets chipped away at with what isn't going towards those. And cohost's update pace and feature pace is way less glacial than Twitter's, we just see them one at a time instead of ten every nine months.
especially if you hate electron, which is the way many smaller companies impliment the general suite of accessability features.
Software is often built in a spiral, with you needing to do things to make it easier to do the rest in a way that's able to be maintained instead of a liability. Working with one thing, getting blocked on it, doing things completely different to think, coming back, moving on and coming back later when insight hits. If you try to direct the work, often it's way less productive than bouncing around unless someone is working on something they've managed to line up all the right resources for.
I've been around volunteer and small employee count organizations for 20 years and the only thing I can promise you is tearing them down will make it harder to impliment features you want even ignoring the sour taste. criticize, sure. But try not to come at it from a place of ignorance or you'll undermine your point on your quest to make someone miserable on behalf of not having implemented the thing they should have.
I shouldn't need to say this. Put down the guns and talk. (edit: that goes for all sides.)
this isn't fucking Twitter. both stop acting like it, and stop expecting the same feature speed -- 7500 people means you can work on features in parallel, and VC and ad money means you can float on the features that get you revenue neutral and up. 3/7500 = 0.04%
Put down the guns and talk.
What are the "guns"? Complaining angrily is not a gun. People debating whether or not they should continue Cohost Plus is also not a gun.
Also, it's worth noting that when there's a flare up / increase in the volume of complaint, that's not coming from out of nowhere. Folks have been exercising patience and lower-velocity talking already.
The point that a tiny site doesn't have endless resources to throw at problems is well taken, but I would guess that everyone involved is aware of it and agrees. I think a little more transparency on how @staff is prioritizing planned accessibility features / what the roadmap is would go a long way toward making people feel less strung along about this stuff, but maybe that's me naive of me.
If making accessibility into a discourse is the what gets the broader cohost community to actually notice it, and makes it harder for staff to ignore -- and the official channels don't produce a visible response -- then people will be incentivized to start more discourse.
