Salta al contenuto principale


Last Week in Fediverse – ep 87

Mastodon has officially launched a new version, a new Reddit-like with ClubsAll has launched, and IFTAS has started rolling out their content classifier system.

Mastodon launches version 4.3


Mastodon has released version 4.3, and the update comes with a better notification system, design improvements, displaying follow recommendations in the following feed for new accounts, and the ability to highlight the fediverse profile of the authors of shared articles.

There are two updates to the notification system: notifications are now grouped, and the ability to filter notifications. Grouped notifications means that you’ll see a summary of the number of people who liked and boosted your post, instead of getting each notification individually. This is especially helpful for posts that go viral, as your notifications become unusable without grouping. Third party clients also support grouping notifications of new followers, which Mastodon does not do. With notification filters, you can limit specific types of notifications, for example from people who are not following you, from new accounts, or to filter out unsolicited private mentions.

With the new carousel that displays follow suggestions for new accounts, Mastodon leaned on transparency. For each suggestion it is also displayed why an account is suggested. It seems there are four different reasons for an account to be suggested: ‘Popular on your server’, ‘Popular among people you follow’, ‘Similar to profiles you recently followed’ and ‘Handpicked by your server admins’.

For future plans Mastodon mentions three parts: working on adding quote posts, the ability for server admins to subscribe to managed deny-lists and improving how long-form text is displayed in Mastodon. Mastodon also features a request for donations at the end, noting that they are supported by donations and operate on less than 500k per year. It showcases the difficult spot that Mastodon is in: as the post highlights, their competitors have access to significant capital, which allows them to ship features significantly faster. While it is remarkable what Mastodon has accomplished with their budget, the small team also means that it has taken a year to ship this update 4.3, while the competition can move significantly faster. Not taking venture capital, not selling ads, and not selling data are great things to do, but the update cadence of Mastodon versus that of Bluesky or Threads shows that not doing so puts a significant limit on what the organisation can accomplish during this period of protocol wars.

ClubsAll has launched


ClubsAll is a new fediverse project, a Reddit-alternative similar to Lemmy, PieFed and Mbin. ClubsAll main goal is to provide a clean and easily-accessible UI, and explicitly positions itself as a Reddit alternative. The other focus is on live comments and live chat, where new comments that are made on a post flow in directly visible. The comment section includes both the traditional threaded view as well as a chatbox to invite more chat-like realtime reactions. Other features are easy cross-posting of new posts to up to three communities, and having multiple profiles under a simple login.

With their simplified communities, ClubsAll takes in posts from multiple communities from Lemmy, PieFed and Mbin, and brands them under a single club. This does solve a practical problem, namely that communities can get split over multiple servers, creating duplicates without a clear distinction between the different communities. It is unclear what the practical difference is between the fediverse community on lemmy.ml and the fediverse community on lemmy.world. PieFed solves this problem by having both communities (similar to Lemmy), as well as ‘topics’, which aggregates different communities into a single topic. PieFed makes it explicit that it aggregates posts from multiple communities. ClubsAll however, mostly hides this information, making it less clear that posts come from different platforms. I’m curious to see what the response to this by the community will be, as there are no clear norms so far on what is an acceptable use of federation, and what isn’t. When you take in posts from a different platform, what form of attribution is necessary? ClubsAll clearly attributes the original author, but should the original community also be accredited? The answer is unclear to me, and I’m watching to see how this evolves.

The News


IFTAS has been working on a Content Classification System, and the first classifier is now active. A few select server are working together with IFTAS, where all the media of these servers now get scanned for CSAM. In case of a hit, IFTAS handles the mandatory requirement and record-keeping, and issues a takedown. CSAM moderation is a difficult task for server admins to keep track of, both of the toll it takes on the humans, as well for the complex legal requirements that come with it.

NLnet has been a major sponsor of fediverse projects over the years. They announced the results their latest funding round this week in which they sponsor a large variety of open source project. The fediverse project that got funded is Loops, a TikTok-like short video platform by Pixelfed developer Daniel Supernault. Loops was scheduled for a public beta launch on Wednesday the 9th, but this has been delayed for 11 days. Supernault attributes the delay to the rumour that Threads is working on a Communities feature that is also supposedly called Loops, as well as to further polish the app and platform.

The SocialCG, the W3C Community Group for ActivityPub has agreed on starting work to form a charter to transition towards a Working Group. The details require some knowledge of W3C processes (that I don’t fully grok either), but the very short summary is that a Working Group has more impact on making changes to the ActivityPub protocol.

FediMod FIRES is both a protocol for distributing moderation advisories and recommendations and a reference server implementation. Emelia Smith, who is behind the project, has updated the website with more information as well as a general timeline for when work on the project happens.

ActivityPods is a project that combines the Solid protocol with ActivityPub, and they have released their 2.0 version. ActivityPods allows users to create a single account for multiple different apps; with ActivityPub you need a separate accounts for Pixelfed and Mastodon, for example. ActivityPods gives you one place to store your data, your Pod, based on the Solid protocol, and the Inbox and Outbox system of ActivityPub. This update of ActivityPods gives the ability to set granular permission levels for the access to data than an app has that is build on top of ActivityPods.

The Links


That’s all for this week, thanks for reading!

#fediverse

fediversereport.com/last-week-…


content classifier dashboard
We are extremely proud to announce our Content Classification Service is up and running, with our first classifier active. We are starting with detecting child sexual abuse media for our opt-in connected servers, and our plan is to introduce additional classifiers over time, including non-consensual intimate imagery, terroristic and violent extremist content, malicious URLs, spam, and more.

For the time being we are operating in a closed test with a very small number of servers, and we have a slate of additional server admins ready to participate in our beta. You can learn more – and sign up to participate – on the CCS Web page.

Bonfire moderation workflow
In other news, we are kicking off an exciting collaborative with the Bonfire Networks developer team.

Bonfire is a governance-first community platform using ActivityPub, and the developer team are interested in reviewing proposals from the moderator community for rapid iteration of evidence-based, prosocial tooling and workflow in a co-design effort with the moderator community.

The Bonfire team have already rapidly adopted several proposals including:

  • greyscaling and blurring media in reported content – this reduces trauma for moderators reviewing harmful content
  • muting audio in media files – no sudden noises, loud volume or traumatic audio for the moderation workflow
  • removing clickable links from reported content and suggesting URL investigation tools – this reduces the chance of moderators clicking through to phishing, malware, and other harmful web sites

Our IFTAS Connect community is working to provide additional feedback, and anyone is free to suggest additional feedback on the Bonfire GitHub.

This is a fantastic opportunity for the Fediverse’s trust and safety community to interactively guide the development of modular tooling that we hope will not only benefit Bonfire communities but can benefit the ecosystem at large, through modular adoption of the tooling, Fediverse Enhancement Proposals, or other platforms incorporating the same evidence-based prosocial approaches to empowering community managers and moderators.

We urge all IFTAS Connect moderator members to join us in the Moderator Tooling Workgroup and tell us all the tools, features and functions you want to see added to keep you and your community safe!

IFTAS First 50 badge

Lastly, a huge thank you to everyone who has responded to our community support drive, we’ve raised over $2,000 this year in direct community support and our IFTAS First 50 page is filling up! As we head into giving season, a quick reminder IFTAS is a 501c3, all donations are tax-deductible for US supporters, and we accept a wide range of support. If you can, donate today to keep supporting our mission!

about.iftas.org/2024/10/03/ift…

#ActivityPub #BetterSocialMedia #Bonfire #Fediverse


reshared this

in reply to Laurens Hof

> A proposal to enable portability of identity and object storage within ActivityPub through the use of DIDs

I believe this work has already been done, in a series of FEPs based on the Zot/Nomad protocols developed by Mike Macgirvin for Hubzilla/ Zap. Including;

* FEP-ef61: Portable Objects

codeberg.org/fediverse/fep/src…

* FEP-61cf: The OpenWebAuth Protocol

codeberg.org/fediverse/fep/src…

* FEP-c390: Identity Proofs

codeberg.org/fediverse/fep/src…

#ActivityPub #FEP #PortableIdentity