• she/her

@imhkr on twitter

late 30s trans girl

Video Games, Retro tech,

anime and tokusatsu nerd

behind the scenes @cathoderaydude

FFXIV Daria Imhkr@Ultros
FFXI Imhkr@bahamut

Art by @dataerase

Abandoned
https://bsky.app/profile/imhkr.bsky.social


hkr
@hkr

Some times you have to take things into your own hands instead of expecting everything to work for your specific case.

User styles exist and can alleviate the immediate issue. Does it suck that you have to do this? Maybe. Is it productive to launch into asshole mode and throw a temper-tantrum? No.

Not everything in the world can bend to your specific needs at the speed you need it to. You still have tools to take charge and bend them yourself. It would be far more productive to learn to use those tools than throwing fits.

Be kind to each other instead of assuming the worst all the time.

EDIT: I thought I had thrown the link in but apparently not



You must log in to comment.

in reply to @hkr's post:

The devs give a simple update as to what their priorities and progress on a native dark mode are. Implementing a full, complete darkmode takes a nontrivial amount of time, sure, implementing a quick and dirty one would take less and still be much better than nothing, but making a post or single comment that says "Hear ya loud and clear! Once we implement tipping, that's first on the docket" Takes, as I have just discovered firsthand, maybe 30 seconds.

My solution solves the problem immediately and doesn't involve being an asshole. You can use a user script to take care of the immediate and ask staff for an update. Seriously the user script thing is about six clicks.

It's a solution that doesn't scale, and staff has already been asked for an update, and basically said "you don't actually want that" in response. I don't really think it constitutes "being an asshole" to be up in arms about the pretty roundly hostile and dismissive response the cohost userbase has given to disabled frustration at not only a lack of an essential accessibility feature, but willful silence on the subject.

if you mean the color inversion feature, it generally sucks fuck for most applications, and even when it does work well enough, it's clunky. This also, again is asking the end user to put the legwork in to make something assessable for themselves when the amount of work it would actually take for cohost to make a better dark mode is much, much less than the sum total effort of all users who need a better dark mode need to, already have, and are currently putting in to make up for its lack.

Also the insinuation that it should simply be every phone's responsibility to invent a dark mode that works on all websites and apps, something that, hey, isn't actually easy, instead of a service's responsibility to implement basic accessibility features that, and I cannot stress this enough, would take a couple hours at most to implement to a serviceable if not perfect degree.

The companies that make the operating systems powering those devices are some of the largest corporations in history.

"every phone" means two, maybe three companies.