Things #musl libc will never do (broad but not comprehensive):
- Nag you to update.
- Phone home to check it if should nag you to update.
- Tell you a CVE can't be fixed without updating to the latest version.
- Try to force you to switch from glibc to musl.
- Get other software you depend on dependent on musl.
- Rant against "wokeness" or "DEI".
- Integrate "AI" into your libc.
- Give you up.
- Let you down.
Details on progress in this post to the #musl mailing list: https://www.openwall.com/lists/musl/2025/06/11/1
Actual draft code repo is now up too, at https://github.com/richfelker/musl-uca-draft
Update on #musl LC_COLLATE work: NFD code is functional and Unicode test vectors for normalization to NFD all pass.
.rodata 14161 bytes
.text 1089 bytes
🎉
One consequence of the move to Treehouse, which was not planned or intended, is that if Treehouse goes through with plans to defederate Fosstodon on July 1, this account will lose A LOT of followers.
During the migration I saw how many, because, with the instance already being "limited", I had to manually approve each follow request.
If you're following from Fosstodon, don't plan to move, and want to continue following, please express to the admins that you want to see the sort of meaningful changes needed to turn the instance around.
As for the choice of Treehouse Systems, this was the outcome of a long delay trying to find the right place to move to.
What it came down to is that:
- Shared values on safety and moderation: Particularly on the type of situation that led to this move.
- Shared values on the responsibilities of an instance: Not to play games with defederation, ragequitting, etc. and break people's social graphs without adequate notice and chance to move.
- Connection to community: Lots of people and projects using musl are already associated with Treehouse.
This thread by @ariadne on Treehouse's intent to defederate from Fosstodon lays out more details, in more diplomatic terms:
https://social.treehouse.systems/@ariadne/114632131776730666
I (@dalias) have tried my best to engage with the new Fosstodon admin in good faith on what mistakes they're making, only to be met with assertions that their comfort is more important than marginalized folks' safety on their instance. I cannot in good conscience ask folks to maintain a relationship with Fosstodon in order to follow #musl libc updates on the fedi.
After some extended discussion with the rest of the Treehouse moderation team, as well as extended discussion with Gina, the new owner of fosstodon, we are planning to take incremental steps that will result in full defederation of fosstodon from Treehouse. Fosstodon has been a consistent moderation headache for our team for years, initially because of the same problems we have seen from many of the tech instances: drive-by snippy and unhelpful comments like "oh YOU wouldn't be having that problem if you just used GNU/Linux instead!" In the past year or so, however, things have changed in the nature of the moderation issues we have seen from Fosstodon. While the "reply guy" behaviour is still present, the overall temperature has shifted in the direction of the alt-right, both in terms of moderation incidents and, as recently seen, staffing incidents. Gina has outlined her philosophy regarding [the management of Fosstodon and its role in the greater fediverse](https://ginablogs.com/views-on-the-fediverse-zghd), however this blog does not address any of the specific problems we, and our users, have observed from their community. We are increasingly unconvinced that the situation will improve in any meaningful way, so we conclude that defederation is the only option. These conclusions are always disappointing, but as a community of queer hackers, these decisions are necessary to protect the psychological safety of our local Treehouse community. As we begin to bring our federated relationship with Fosstodon to a close, we encourage our local community to be thoughtful and kind in regard to their frustrations with the Fosstodon community. To help with continuity, instead of immediate defederation, Fosstodon will be upgraded to a full limit with report suppression in a few hours following this announcement. This will allow local users to continue to interact with Fosstodon users that they explicitly consent to interacting with while they make the transition to a new instance, and allows for reversal if Fosstodon commits to acceptable management practices which we have already outlined in our discussions with Gina. In the event that nothing meaningfully changes, Fosstodon will then be fully defederated on July 1.
@musl The immediate cause for this move is that the admin and moderation staff at Fosstodon have proven themselves untrustworthy and unsafe.
Following an incident in which a person on their moderation staff was found to be using moderation privileges specifically and intentionally to harm LGBTQ folks, Fosstodon claimed to have "cleaned house" and committed to change.
The new admin immediately proceeded to recruit mods with the exact same values, and dug in and tone policed when challenged on that.
Fosstodon is proving itself a "nazi bar instance".
Cassandrich
musl libc