Skip to main content


Speaking of #Pinafore, based on a blog post from Nolan Lawson, it looks like it might not be maintained too much into the future. That's sad, but I totally respect that. I just contributed some a11y pull requests, but I'm now wondering whether I need to focus on the official UI instead. Hmm. https://nolanlawson.com/2022/11/22/thoughts-on-mastodon/
in reply to Jamie Teh

Well, whatever you decide, you'll help the Mastodon community either way. And if @nolan no longer wants to maintain Pinafore at some point, he can always transfer ownership to someone he trusts to keep the project alive and healthy.
Unknown parent

Jamie Teh
@fireborn It really is. Having said what I said (based on the author's blog), it seems development is still pretty active and pull requests I submitted a couple days ago have already been merged, so we'll see. It's definitely not retiring just yet.
in reply to Jamie Teh

Was just searching #pinafore and this was prescient. It's good that Nolan forecast the situation. Just want to let you know since you contributed, and I understand the tech debt concerns he had, that I'm operating a fork of Pinafore to allow it to continue on in relation to contributor interest.

I'm operating the fork via the Collective Code Construction Contract which is pretty lightweight and clear as far as maintenance goes. You can find the fork and more about that at https://github.com/weex/pinafore
in reply to David Sterry

@weex Great! You may wish to chat with @nickcolley, who I believe is also starting a fork.