**Laurens Hof** @LaurensHof@fediversereport.com · + 2025年01月07日 18:16

**Laurens Hof** @LaurensHof@fediversereport.com · + 2025年01月07日 18:16

Laurens Hof @LaurensHof@fediversereport.com

+ 2025年01月07日 18:16

Laurens Hof @LaurensHof@fediversereport.com

Last Week in Fediverse – ep 98

Welcome back to Fediverse Report! I’ve had a great holiday break spending time with family and friends, and that has given me some more time to think about why I care about the fediverse, the open social web and why I spend all this time writing Fediverse Report. Explaining to family members what I do was helpful to make this clear: telling an uncle that I write about decentralised technology mainly leads to confusion. But even extremely offline family members easily understand and agree with the idea that having all of our big social platforms being owned by billionaires leads to significant social problems.

As such, it has helped for me to make it more explicit that I care about decentralisation insofar it is a tool to get somewhere else: I care about better forms of governance and ownership of the social web. I want a social web where people are in control, not a few billionaires (nor nationstate governments, for that matter). Building social networks with decentralised technology is a way to get there.

The idea that the value of alternative social networks is in governance is far from new. I’ve regularly posted hot takes on my Mastodon to the same effect as well. But for 2025 I want to bring this more into focus for this newsletter. Writing a newsletter that is a weekly update tends to amplify shiny new software that has recently been released. In contrast, explaining how governance works on the fediverse does not align well with ‘this happened in the last 7 days’, as it involves more structural and slower moving forces. I’m experimenting with ways to bring coverage of governance in the fediverse better into focus. Expect more like this newsletter, where I zoom in on an offhanded comment by Misskey developer Syuilo as an illustration of the issues that come with interoperability between different places on the open social web.

The News

Mastodon has belatedly published their Annual Report for 2023. The organisation acknowledges the delay, and says that the Annual Report for 2024 is planned to be released in Q1 of this year. Mastodon had a total of 545k euro in donations in 2023, with 476k in costs. The large majority of costs go to personnel expenses, in total 343k was spend on salaries, 72% of the total budget. The popularity of Mastodon’s own servers also come with significant costs, in 2023 they spend 75k on servers and hosting. With a rough estimate of averaging around 250k active users on mastodon.social, this means mastodon.social costs roughly 30 cents per active user per year. The Annual Report also looks at the updates Mastodon has made to the site and apps. Mastodon also shares more about their hiring process, and in a great move for transparency, also published all the salaries of everyone in the organisation.

Back in the present, Mastodon is hiring again, this time for a senior front-end developer. The organisation also held a crowd-funding campaign in late last year to fund and hire a Trust and Safety lead. The community seemed to have had little appetite for funding such an endeavour, with funding barely pushing past the 12k after a month. It is an indication of the difficult spot the organisation is in; the community has been asking for more safety features in Mastodon, but is not funding a Trust and Safety Lead. The organisation could clearly use someone who writes clear policy and design goals for the direction the software should go in. Currently, not even a Mastodon employee can explain why a safety feature for Mastodon that is fully developed and waiting to be approved has been waiting for approval for over 2.5 years. It turns out that writing the code is often the easy part of making changes in the fediverse, and navigating the social structures to get the code used by people is much harder, and a dedicated Trust and Safety Lead could have certainly helped here. Instead, even after large community outcry we still do not know why Mastodon has not merged this safety feature developed by their own employee.

Surf is a new app by Flipboard for the open social web. It is a beautifully designed app that allows people to build their own custom feeds. The power of Surf is in that it supports many networks, and you can combine posts from Mastodon, Bluesky, Threads, YouTube and Flipboard all into a single custom feed. How Flipboard markets Surf is interesting, describing it as a ‘browser for the social web’. The way Flipboard CEO Mike McCue sees it, Surf pulls in content from the social web, and gives you the possibility to display that content in custom feeds of your choice. Surf also allows you to filter a custom feed by content: for example, you can scroll through an entire feed, or switch over to a different tab that shows only videos in that feed, for example.

For more info on Surf, WeDistribute has a closer look at all the features, and The Verge has more context and comments by McCue. Custom feeds on Bluesky have mainly gone in the direction of the power user and community builder: tools like Graze offer an huge potential in programmability and flexibility. This is especially useful for those who want to build custom feeds that other people will also use. Surf takes a different approach, by instead prompting people to build their own feeds as much as possible. It’ll be interesting to see which approach will gain traction, and if there is space for both ways of building custom feeds.

Misskey developer Syuilo made some comments contemplating breaking federation with Mastodon. Misskey is mainly used in Japan, and has a wide feature set that differs notably from Mastodon. The main reason that Syuilo gave is that she feels Misskey development is constrained by having to meet the needs and requirements of maintaining federation with other (types) of software. That Misskey is considering letting federation between Mastodon and Misskey break is an indication of one of the downsides of how ActivityPub is designed: You can send out anything you want with ActivityPub, but it is exceedingly difficult to know how other software will actually receive and display the things you send out with ActivityPub. There is a significant freedom for fediverse software in how they implement and support even more basic functions. For example, see this comparison table for how the different platforms support hashtags, and how many variations there are.

Personally, I think it would be healthy for the fediverse as a whole if more fediverse software would start publishing what they deem as necessary for other software to federate with them. The fediverse mainly currently works on the assumption that any form of federation between projects is fine, even if that means that another federated platform will stripping out all markup and images of a post. It might be healthy for a platform to state minimum functional requirements, such as ‘we only want to federate with software that also shows the emoji reactions as we view this to be an integral part of a message’. For now, Syuilo’s post mainly seems to be to vent some frustrations, so it remains to be seen where any of this will actually go.

The Links