In the last few weeks, I have been trying to organise the #Mastodon development work, so our (very small!) resources are used efficiently. This led us to a tentative roadmap for Mastodon 4.3, with a (very optimistic) release date before Christmas.
We just published our first Trunk & Tidbits post! This will hopefuly be a monthly update where we showcase what we worked on last month, and what's coming next.
I hope this will bring more visibility to all the efforts and love that put on Mastodon
Hello fedi. i am trying to solve the "fetch all replies" problem once and for all that makes the fedi feel a lot more desolate and with a lot more reply guys in it than it should be. this is take two, where before i had it triggered by a button, but now i think it should happen on the server-side whenever you expand a post. can anyone help me out figure out how to make this more efficient by only fetching posts that the server doesn't already have? i am not sure what the best strategy would be, and if anyone with experience doing efficient rails and SQL stuff could give me some pointers that would be gr8. the patch is actually extremely simple it just needs a few nice things to make it not DDoS everyone.
To celebrate the release of the long awaited major upgrade, I've written a short blog with a list of the hard work that Big G, Claire, Renchap and the rest of the Mastodon community have completed over the last few months!
On the Mastodon Public Roadmap this feature isn't even in the "Planned" section: https://joinmastodon.org/roadmap 😐 (MAS-37 Restrict who can reply to a post)
If you too think this very basic safety feature, one of the most thumbsed-up on the Mastodon issue list, should be a higher priority, go to the Github issue and add your 👍 and a comment to bump it into the devs' awareness: https://github.com/mastodon/mastodon/issues/8565
New feature in Mastodon 4.2 that I am very happy about: non-dismissable and very red notices for server admins when there is a new security update available.
We also sent emails to admin. This is all done locally by your instance, it (anonymously) fetches the available updates from the central api.joinmastodon.org every 30 minutes.
I'm just a humble country chicken admin, but I've been thinking a lot about the cost of the fediverse and how we can improve it for all of the instances... in a coop kind of way
The cost of handing all of the media is THE major problem for me atm.
That seems like a pretty big change. I've got questions, like:
Why not put them under a "show tags" thing?
On Tumblr they're visible, but they show you the first line or so by default and then you can click to show the rest. Should we have that?
At the moment, when something appears in your Home feed because you follow a hashtag, there is no indication about why. If hashtags are hidden, people are going to be even more confused.
I get that people want to not see spammy hashtags at the end of posts, but to make them totally hidden to the reader seems a bit extreme?
Anyway, if you feel similarly, leave a comment on the Github pull request: https://github.com/mastodon/mastodon/pull/26260 (You might need to make a Github account, but that's pretty easy.)
"oh nice, #mastoDev has a professional design team, this will allow them to keep closer interaction with the community since programmers can focus on code while the professional design team participates in community discussions and respond to accessibility criticism with valuable feedback from users."
(He admins mastodon.social & mastodon.online too — whew!)
I've had the pleasure to get to know him in his work as a core contributor to #Mastodon through #FastForward, and I'm thrilled — his thoughtful approach and deep knowledge of networking ++ will help us scale in a sustainable and healthy way.
The #fediverse#socialweb is facing some tough problems, but we're in great hands with Renaud in this role!
For this weekend's coding project, I built a tiny single-user Bluesky→ActivityPub one-way bridge I named “Pinhole”. If there's someone on Bluesky whose posts you want in your Mastodon feed, you can download and run it yourself: :fietkau_software: https://fietkau.software/pinhole
Caveats: 1. I intentionally built it anti-scalable: you can use it to follow one Bluesky account from one fedi account, and that's it. 2. You need experience with web servers.
Now deployed on #PhanpySocialDev (dev.phanpy.social). Media-first UI experience only kicks in for #Pixelfed account log-ins. Basic features work, except:
Local and Federated timeline show the same thing
Trending, Bookmarks, Reply, Lists, and Filters don't work