Fediverse Report – #104
Mastodon has announced it will add quote posts to the platform, and some more news.
The News
Mastodon has announced it is adding quote posts to the platform, a long-awaited feature. Mastodon got a grant by NLnet in 2024 to add quote posts, and they are now sharing an update on their work. Mastodon is adding a variety of features to quote posts, such as giving people the ability to opt out of being quote posted. They will publish the technical work to support quote posts as Fediverse Enhancement Proposals, and Mastodon is currently in the process of writing these proposals. The organisation does not say when quote posts will be added, only noting that it ‘will still take more time to develop.’
For a long time, Mastodon had not implemented quote posts because CEO Eugen Rochko saw them as bad. His main concern is that quote posts lead to ‘dunking’ and toxic behaviour. Dunking refers to the behaviour where people use quote posts to ‘dunk’ on other people’s post, often with the intent that this mocking will lead to their followers to also mock and harass the original poster. Dunking was a visible part of Twitter’s culture, and in popular belief dunking and toxicity became linked together. Research showed a more complicated picture. Hilda Bastian analysed over 30 studies on quote tweeting, and concludes: “There’s conflicting evidence on whether QTs [quote Tweets] increase or decrease incivility, and whatever effect there is, it doesn’t seem to be major.“
In 2023 Mastodon changed their opinion, and first started saying that the organisation was open to implementing quote posts. Still, toxic behaviour via dunking continued to be a main concern. This is visible in the accompanying design research that Mastodon has done in their work on quote posts. Mastodon’s view seems to be that quote posts are toxic at it’s core, saying that “the team started out with a shared view that Quote Posts can be misused.”
Mastodon takes a technical approach to dealing to the purported problem of toxicity of quote posts, and the blog posts lists three features to mitigate it: people can choose if their posts are able to be quoted, people get notified if they are quoted, and there will be the ability to withdraw your post from the quoted context. Bluesky also has these features for quote posts, and they’re generally received well. What I find missing here is a take by Mastodon on the effect of these features on Bluesky. Mastodon sees quote posts as being dangerous, and that is why they will implement some features to mitigate the risk. But do they think that quote posts are being used well on Bluesky? Is Bluesky’s behaviour and culture around quote posts something that Mastodon is striving towards? I’m not clear to me what Mastodon’s answer is here.
Mastodon’s design research also says that they will display quotes in a different way to ‘steer away from dunk culture”‘, a feature not mentioned in Mastodon’s announcement blog post. Mastodon is planning to display a quote post by first showing the quote, and showing the reply below it. This is similar to how Tumblr does quote posts. But it differs from how all other platforms that interoperate with Mastodon display quote posts: fediverse native platforms like Misskey, Akkoma and Streams, as well as connected networks like Bluesky and Threads, all display quote posts by showing the reply at the top, and the quoted post below.
Mastodon’s position is that quote posts are a risky feature invite misuse, and thus need a variety of safety features. But Mastodon is not an isolated platform, it is connected to various other platforms that all have their own ideas about quote posts. If displaying quote posts Tumblr-style (quote above, comment below) is preferred over displaying them Twitter-style (comment above, quote below), what is the expectation on how other platforms should interact with Mastodon quotes? Is Misskey expected to display Mastodon’s quote post differently? Meanwhile, Mastodon is planning to display quotes that originate from Misskey not in the way that Misskey does (Twitter-style), but in their own manner (Tumblr-style), saying that it has “very little impact on the semantics”.
I find these statements hard to square: on the one hand, Mastodon says it how quote posts are displayed has little impact on the semantics of a post, but at the same time it is assumed to have enough of an impact in that it can reduce “dunking culture”. But if the manner a quote post is displayed can impact people’s behaviour, it automatically follows that the manner a quote post is displayed impacts its semantics, as otherwise there would be no impact on people’s behaviour either. But if the semantics of a post are altered by using a different display method for quote posts, than it means that Mastodon is taking an active decision to alter the semantics of posts made on other networks like Misskey and Bluesky.
Mastodon’s choice to use a different way of displaying quote posts than the other platforms in their network opens up a new interesting avenue for federated diplomacy. We’ve seen both ways of displaying quote posts be successful, the way posts are quoted is a significant part of how conversations flow on Tumblr. But what is new here is Mastodon is part of a federated network, and that means that their decisions impact other players, and their decisions have impact on Mastodon as well. This interaction between different display types of quote posts is something we have not really seen before, leading to some interesting new types of negotiations: how Mastodon expect Misskey to display Mastodon quote posts on Misskey? How does Threads feel about having their quote posts being displayed differently on Mastodon? What is the expected behaviour of Bridgy Fed, the bridge that connects Bluesky with Mastodon? All those questions are still open, and I’m curious what the answer will turn out to be.
Tumblr is still planning to join the fediverse. I reported this recently, and now TechCrunch got a followup and a confirmation from Automattic, saying that ‘Automattic declined to share a time frame as to when the migration would be complete, given its scale, but a rep for the company called the progress so far “exciting.”’
The Social Web Foundation (SWF) has announced they are now a formal member of the World Wide Web Consortium (W3C). The W3C tends to favour institutional membership, but the W3C Social Community Group that concerns itself with ActivityPub is open to everyone. The SWF is working on various improvements to ActivityPub, such as adding end-to-end encryption and supporting data portability.
Event Federation is a WordPress plugin that extends the ActivityPub support plugin for WordPress by adding support for WordPress events. The plugin is now officially released as a 1.0 version.
Hexbear is a controversial Lemmy server that let domain expire. The Hexbear domain is now for sale, and an avid bidding war has driven up the price for the domain to over 2300 dollar at time of writing.
ForgeFed is an ActivityPub extension that adds federation support to software forges such as Forgejo. It has gotten a new NLnet grant, with the project now focusing on user research and documentation.
A few weeks ago, Fedidb removed fediverse platfrom GoToSocial from the database after refusing to honor robots.txt, and the GoToSocial developer spoofed data as retaliation. Fedidb developer Daniel Supernault later decided to properly add support for robots.txt, but stopped crawling for the entire fediverse in the meantime while it was implemented. Supernault now confirms that Fedidb honors robots.txt and has added GoToSocial back to the data set.
The Swiss Federal Institute of Technology in Lausanne has set up their own Mastodon server for all community members, including students.
The Links
#fediverse
fediversereport.com/fediverse-…
Since 2022, blogging site Tumblr has been teasing its plans to integrate with the fediverse -- the open social web powered by the protocol ActivityPub
Sarah Perez (TechCrunch)
Our new NLnet grant is officially signed! We're starting work :) The main focus is:- Creating materials to support the Forgejo federation implementation
- Documentation for the specification
- Implementing the Vervis backed API in the Anvil frontend
Forgejo could enjoy more Go developers joining the federation team! It might be the best way to contribute to forge federation right now.
--Pere
