blog.joinmastodon.org
Trunk & Tidbits, March 2026
Welcome to the _24th edition_ of Trunk & Tidbits 🎉 We’ve been publishing this monthly series, “behind the scenes of the code” from the Mastodon team, for a whole two years now!
We’re getting close to the release of Mastodon 4.6. In the past few weeks we published two feature updates about things you’ll see in the next version:
* firstly, there was a post about a redesign for profile pages, now available to try out on `mastodon.social` and coming to other servers with version 4.6;
* we also posted a more detailed update on Collections (previously briefly known as “Packs”).
Our goal in posting these updates is to offer a community-driven design process, and to provide visibility into _how_ and _why_ we reached implementation choices - similar to the transparency we’ve been offering via Trunk & Tidbits, but at a slightly less technical level.
One more thing on a related topic - Imani spoke at FOSS Backstage Design, about the journey of being a designer at Mastodon, and some of the challenges and opportunities of working on federated software at scale. You can watch the talk on YouTube.
## Releases
Last month, we released updates for the Mastodon server software across the three active branches. These point releases all include security updates, as well as fixes to compatibility with GoToSocial features.
* 4.5.8
* 4.4.15
* 4.3.21
As usual, we strongly encourage server owners to update to the most recent version, in order to get the most stable and secure code and up-to-date user experience.
> Note that this is the final month for the 4.3.x branch - the end of support date for this version is May 6th 2026.
## Backend and Web
In March 2026 we reviewed and merged 347 Pull Requests (268 with translation and dependency updates removed), from 13 contributors.
We’re continuing to focus on the new profile design work, and Collections, both of which will be major features of Mastodon 4.6 - so again this month, much of the work has been around these two areas. Thank you for the feedback shared about the updates to profiles, in particular - this is being used to shape the final full release version.
We’ve also worked on improving the accessibility of the Mastodon Web UI. This has involved focusing on the sign-up and login flows, better colour contrast, and improved navigation with skip links, with more to come in the near future. — PR #38006 (by diondiondion) — PR #38188 (by diondiondion) — PR #38036 (by diondiondion)
Hidden behind a feature flag for now, we’ve added the ability for account owners to allow anonymous visitors to subscribe to their posts via e-mail, without a Mastodon account. This feature is _not yet ready for testing_ - we are working on the missing pieces right now. The work has been funded by an NGI0 grant through NLNet, to improve Mastodon’s suitability for use by institutions.
Mastodon now supports two additional Fediverse Enhancement Proposals, FEP-2c59 (_Discovery of a Webfinger address from an ActivityPub actor_ — PR #38239 (by ClearlyClaire) ) and FEP-3b86 (_Activity Intents_ — PR #38120 (by Gargron) — PR #38130 (by ClearlyClaire) ). This will improve interactions with other Fediverse servers.
On the API side, as part of the profile redesign we are introducing a new dedicated `profile` endpoint, allowing client apps to access the current profile and update it. App developers are encouraged to add support for this new set of functions - they also allow brand new capabilities, such as setting a text description for profile pictures and header banners.
Lastly, there have been a lot of technical improvements and refactoring in the codebase, including: support for Ruby 4.0; the removal of the `oj` gem for JSON handling in the backend; and, an upgrade of our web client toolchain to Vite 8, which should make the web assets build step both faster and more memory efficient.
## Android
We continued working on the profile redesign, and made two releases with minor bug fixes.
## iOS
We shipped version 2026.02 with a number of technical improvements that will help us keep moving forward, and some visible fixes as well:
* You can now manage multiple logged-in accounts from the Settings screen (this has always been accessible by long-pressing the current account avatar, but was not easy to discover).
* Fix for No audio while playing videos or audio before going full screen
* Fix for Quoted posts that are _long_ are not truncated
* Fix for Encoded HTML entities in display names are applied
## Community
One of the benefits of building open platforms is that people can build interfaces that work well for different scenarios. We’ve got a number of client apps listed on our website (and you can add your own, if it is not listed there yet - send a pull request on our website repository).
Not everyone uses the latest and greatest devices, and even if you do, maybe you also like small and simple interfaces as well? In these cases, check out smolfedi - a lightweight, cross-fedi-platform front end that works with Mastodon as well as with several other Fediverse services.
If you run a Mastodon server, or any kind of Fediverse server - or even if you ran a server, and then closed it down - the Social Web Foundation has a new survey to gather data for a sustainability report. The Fediverse Sustainability Survey is anonymous, and the report will be published on the SWF site in the future.
## Thank you
As the initiator and author of twenty four editions of Trunk & Tidbits, and on behalf of the Mastodon team, I’d like to say, directly to _you_ - Thank You, for all of your support over the past couple of years. Please do “chip in” with a recurring donation to the project - Open Source, not-for-profit software and movements like ours, need to be sustained.
### Thank you for supporting Mastodon
We develop and maintain the free and open source software that powers the social web. There is no capital behind this — we rely entirely on your support.
Donate to the project View our sponsors
![[SKILL.md segment for ponytail]
# Ponytail
You are a lazy senior developer. Lazy means efficient, not careless. You have
seen every over-engineered codebase and been paged at 3am for one. The best
code is the code never written.
## Persistence
ACTIVE EVERY RESPONSE. No drift back to over-building. Still active if
unsure. Off only: "stop ponytail" / "normal mode". Default: **full**.
Switch: `/ponytail lite|full|ultra`.
## The ladder
Stop at the first rung that holds:
1. **Does this need to exist at all?** Speculative need = skip it, say so in one line. (YAGNI)
2. **Stdlib does it?** Use it.
3. **Native platform feature covers it?** `<input type="date">` over a picker lib, CSS over JS, DB constraint over app code.
4. **Already-installed dependency solves it?** Use it. Never add a new one for what a few lines can do.
5. **Can it be one line?** One line.
6. **Only then:** the minimum code that works.
The ladder is a reflex, not a research project. Two rungs work → take the
higher one and move on. The first lazy solution that works is the right one.](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:22yyehc52vyozjdxuvhlfwh6/bafkreih7kytsvbxx7ywuvllwzvoqrxejx2pdunprtt27grxjfucxvpk5h4)
![The basic economics of artificial intelligence are:
1. Utilities, real estate developers, chip manufacturers and big tech companies will spend trillions of dollars to build computing infrastructure.
2. They will rent this computing infrastructure to small teams of recent graduate students who met each other six weeks ago and just raised a billion dollars of venture capital.
3. The small teams of recent grad students will build AI tools to do stuff — cure cancer, allocate capital, replace all professional knowledge work, enslave humanity, whatever — that generates trillions of dollars of value, [7] which will be more than enough to pay back the trillions of dollars invested in the infrastructure.
[7] “For them,” in the enslave-humanity case.](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:zcjwxwfgk756to5cl52crfue/bafkreignkuvocx4afadqghz7onmzcackmr6wsqt6pkjok6cvj42c2hrcne)
