Show newer

people are liking gotosocial a bit too much, we should introduce something terrible next release

re: :boosts_ok_gay:​Help with Linux Screenreaders 

@dangero yep.. Odilia seemed quite promising, keeping an eye on that for sure

It has been proven repeatedly that platforms prioritizing growth over safety are toxic to everyone else who doesn't present as white, straight, and a man.

No, I'm not going to debate it anymore. No, I don't care if people think I'm wrong to center safety in my dev efforts because I can live with it going sideways if that happens.

But in my experience as a dev and a citizen of the web for more than two decades, the missing link to rehumanizing social media spaces is safety for the most marginalized people that have historically been ignored.

And I'm going to create around that ethos.

Show thread

I'm going to repeat this so it's clear.

If the fedi fractures around the ideological lines of safety vs. unsustainable growth, I'm okay with that.

I am very comfortable with being part of the fedi that actually gives a shit about people rather than treating them as product.

I have no interest in repeating the same mistakes and creating decentralized rage engines.

I believe this space can be better.

re: :boosts_ok_gay:​Help with Linux Screenreaders 

@Seirdy@pleroma.envs.net got Odilla built and seems like an interesting project, but not much functionality yet. Definitely worth keeping an eye on though

re: :boosts_ok_gay:​Help with Linux Screenreaders 

@Seirdy@pleroma.envs.net right, might just have to dust off a windows vm instead then 🙄

From my understanding Orca just doesn't recognize any kind of landmarks/tree structure at all, and so it's practically useless for my testing because I can already see the same visible text it reads..

Odilia seems interesting, gonna try a build of that then

:boosts_ok_gay:​Help with Linux Screenreaders 

For better accessibility testing of the software I build, I've started testing more with screen readers.

On Android, enabling and using TalkBack is relatively straightforward, but for testing on my desktop, Orca is completely unusable.

I have a brand new Debian VM with GNOME, and Orca enabled, but actually using it in firefox just barely works. TalkBack has a nice workflow with highlighted elements that you move between as you read the page, but Orca seems delegated to using caret browsing and reading whatever your cursor is on? Am I missing shortcuts (which are also a pain, because the modifier can only be caps-lock or insert, not really conveniently placed)

Am I missing something, or is this the state of on ?
Also the tts quality is very poor, which would make this even worse for any prolonged testing, but maybe there are alternative engines?

this shit just doesn't work without desktop environment / gnome etc

im getting a debian gnome virtual machine 🥴

Show thread

re: linux question 

@schratze that would copy the entire drive info, with partition stuff etc, which you'd then also need to extend to the full disk size afterwards to use the new space.

But most cases i'd recommend formatting the new drive, and copying files over on the filesystem layer, through `rsync` across two mounts

accessibility is still fucked tho for some reason. Spoilered video's don't even get TalkBack focus, and when playing a video, it keeps constantly reading out the duration ffs

Show thread

check out the new video player and how it interacts with the lightbox now (work in progress, let me know)

gts-dev.pixie.town/@f0x/status

@handlerug great to hear :D I did some weird hacks to have plyr integrate with the photoswipe lightbox as well

this is awesome: See this page fetch itself, byte by byte, over TLS subtls.pages.dev/

@f0x@gts-dev.pixie.town check out the new GTS video player and media spoilers :3 (work in progress)

project management / issue tracker advice 

Don't try to minimize the amount of open issues in your issue tracker! Issues are *contributions* from users, telling you about problems that you were not aware of yet - they're not pests to get rid of.

Closing issues without either solving them or a good(!) reason why they won't be fixed - for *any* reason, including stalebots - will just sour people on your project. They won't tell you that; they'll just stop showing up. And the issue still won't be fixed.

Instead, treat your issue tracker like a priority queue: accept that you're never going to get to zero, accept that some issues will remain open a long time because they are not urgent, and find a good way to order the list by your criteria of importance.

Work on things as time permits, in order of importance, communicate this to users, and establish a good rhythm of bugfixes that users are happy with even if *their* specific bug isn't fixed yet.

There are a lot more useful thoughts on this topic in this article: apenwarr.ca/log/20171213

@f0x@gts-dev.pixie.town check out the new GTS video player and media spoilers :3 (work in progress)

Show older
Pixietown

Small server part of the pixie.town infrastructure. Registration is closed.