Skip to main content


Musing about the end of Pinafore development and official Mastodon UI accessibility shortcomings, long post
Re the just boosted post about the end of pinafore development, I completely understand the situation but I'm still sad to see it go. Now Mastodon isn't Twitter so it'll probably work for months if not years to come, but IMO this is going to leave particularly Windows and Linux users without a good desktop or desktop-like client (Mac OS is going to be served by Mona very well once it gets feature parody). But for the foreseeable future I'm probably going to stick to Pinafore as my main desktop client because it offers a ton of logical keyboard shortcuts, has excellent autocomplete support and reads posts in a very clear way even including media descriptions. The official Mastodon UI is almost there in that aspect, but the speech feedback you get when navigating with its keyboard shortcuts has many shortcomings (see github.com/mastodon/mastodon/i…). Maybe this is the right time for this to get more love in either Mastodon or at least one of the forks like hometown, though that won't help anyone using something like Pleroma or its forks. #noxp
#noxp
This entry was edited (1 year ago)
in reply to Pitermach

Musing about the end of Pinafore development and official Mastodon UI accessibility shortcomings, long post
I think that got closed? My main issues with the web client are the "article 1 of 20" every time I navigate with J and K, and the fact that I always have to go to the first toot to start that kind of navigation (this last part happens sometimes in Pinafore too, but much less)..
in reply to Sukil Etxenike

Musing about the end of Pinafore development and official Mastodon UI accessibility shortcomings, long post
@sukiletxe Yes those two are annoying as well. As for that issue, true that it was closed but if you look at the comments the information presented lacks some important details like media descriptions and you only see absolute times while visually they're displayed as relative.
in reply to Pitermach

Musing about the end of Pinafore development and official Mastodon UI accessibility shortcomings, long post
Ah, I just skimmed through it. Yeah that's a pity
in reply to Pitermach

Musing about the end of Pinafore development and official Mastodon UI accessibility shortcomings, long post
I considered contributing to the official client instead of Pinafore, but I'm fairly sure that would require me to set up all the server stuff locally, since the front-end is tied to its instance. Setting up the Mastodon server is just not something I'm willing to invest time in, so the barrier to entry is just too high.
in reply to Pitermach

Musing about the end of Pinafore development and official Mastodon UI accessibility shortcomings, long post
I use TweeseCake for Windows with Mastodon. TC also has Mac support. It's aimed at blind users though.
in reply to Pitermach

Musing about the end of Pinafore development and official Mastodon UI accessibility shortcomings, long post
Just use damn Tweesecake. Problem solved.
in reply to Pitermach

Revisiting my pinafore thread from last week this time without a CW, hello world from @semaphore! Really happy to know that Pinafore's legacy will live on.

Brandon reshared this.

in reply to Pitermach

@semaphore Does Semaphore allow for one to follow hashtags? I noticed last week that I can't do that from pinaphore.
in reply to John Lipsey

@johnl1129 I don't think we support that get but it's something I'm (@nickcolley) keen on as I want to have easy access to cats. ☺️
in reply to Pitermach

@semaphore yay I will try it too. probable it will be indistinguishable for a blind person between those clients, good, as pinafore had a fantastic ui