fediverse
My #FediforumFriday update this week is that I've been tinkering around at the MVP end of the fediverse, trying out projects like #snac (and also, honk). I really need to write some of these experiences down somewhere! Also, preparing for my talk at #FrOSCON next weekend.
What are you looking at that's interesting and #fediverse-related right now?
#fedicat #fediverse support is made possible by admins running servers of various flavors (and interesting names) that I can test on, such as: wizard.casa, catodon.social, functional.cafe, gram.social, miraiverse.xyz, wienermobile.rentals, friendica.opensocial.space, plasmatrap.com, bytes.programming.dev, eggplant.place, and takahe.staging.django-cast.com
Just an occasional reminder that disabling replies is the #1 requested feature from Mastodon.
https://github.com/mastodon/mastodon/issues?q=is%3Aissue%20state%3Aopen%20sort%3Areactions-%2B1-desc
(EDIT: Direct link, in case the above doesn't work for you: https://github.com/mastodon/mastodon/issues/8565)
Limiting who can reply is also worth giving a thumbs-up to, currently at #10.
https://github.com/mastodon/mastodon/issues/14762
#mastodon #fediverse #ReplyControls #SocialMedia #TrustAndSafety
For some months now I am actively hesitating to publish my work-related stuff on #LinkedIn (or any other centralized social network for that matter) so I am thinking of using the #fediverse for it.
Do you have any advice for using fediverse as your #work -related social network? My use case for such a network would be: inspiring others to do good work, building and maintaining my professional "brand," and helping myself or my employer attract new talent.
Some topics to consider: Same account, separate account? Server software (Mastodon, Pleroma, ...)? Discovering (potential) colleagues, being discovered by them? Pointing existing LinkedIn users to your fediverse account? Adjusting language/tone of communication based on fediverse nuances?
I am eager to learn. Boosts are appreciated.
How PieFed federates “flair” on posts and comments
On the surface flair on PieFed functions very similar to how it does on Reddit – on posts they’re community-specific tags that can be used to filter posts in a community. People can also add flair to themselves which is just a piece of text that appears next to their name whenever they make posts or comments in the community. This can be helpful for giving a hint about someone’s background, interests or expertise.
However PieFed is federated and there are copies of the communities on multiple servers (instances). The way to use ActivityPub to create and maintain those copies is described in FEP 1b12 which makes no mention of flair. I have made some minimal additions to that FEP, described below:
For flair on posts, the Lemmy devs have already done quite a bit of work on this, which I added a little to, so that flair can have colors. Community actors have an additional type of tag:
{
"type": "Group",
"id": "https://piefed.social/c/piefed_meta",
"name": "piefed_meta",
/* ... */
"lemmy:tagsForPosts": [
{
"type": "lemmy:CommunityTag",
"id": "https://piefed.socia1/c/piefed_meta/tag/whatever",
"display_name": "Some Post Tag Name",
"text_color": "#000000",
"background_color": "#dedede"
}
]
}
lemmy:tagsForPosts is a list of lemmy:CommunityTag objects.
So now all the different copies of the community will know which flair can be used there. When creating a post in the community we just need to add one or more lemmy:CommunityTag objects to the Page activity:
{
"id": "https://piefed.social/post/1",
"actor": "https://piefed.social/u/rimu",
"type": "Page",
/* ... */
"tag": [
{
"type": "lemmy:CommunityTag",
"id": "https://piefed.social/c/piefed_meta/tag/whatever",
"display_name": "Some Post Tag Name"
},
{
"href": "https://piefed.social/post/1",
"name": "asdf",
"type": "Hashtag"
}
]
}
In this example the post also has a #asdf hashtag on it.
User flair is simpler because it’s not managed by the community moderators and is not a fixed list. PieFed simply adds the author’s flair to every comment (federated as a Note activity) they make. When a Note is received the author’s flair is updated on the receiving instances.
{
"id": "https://piefed.social/comment/1",
"actor": "https://piefed.social/u/rimu",
"type": "Note",
/* ... */
"flair": "PieFed dev"
}
This means that when someone changes their flair it will take effect immediately on their instance but until they write a comment it won’t propagate to other instances. As flair is primarily used on comments and the people using flair will tend to be posting a lot of comments this is kinda “good enough”.
It would be trivial to add a “flair” attribute onto posts too and have receiving instances read that. User flair shows up next to the author’s name on their posts so arguably it makes sense to send it then too.
Let’s see how it goes.
The last #snac release fixes a problem with the Mastodon API. Now, apps (or webapps like Phanpy) properly work as the "inifite scrolling" has been fixed.
Thanks, @grunfink - this was one thing that kept some of my friends away from self-hosting with snac, and now I can help them to have their own digital home.
By the way, if you’re looking into decentralized tech where people are actually in control of their own data (as in who can use it, when and how), checkout #Solid https://solidproject.org There are a lot of interesting insights, especially for storing sensitive data. #OpenSocialWeb #ActivityPub #Fediverse
A new release of TootSDK - 14.4.0 📣
https://github.com/TootSDK/TootSDK/releases/tag/14.4.0
What's changed:
- Add instance domain blocks and peers endpoints @dale_price
Community contributions are greatly appreciated 🙌
What is the best option to host a #Mastodon instance with its own domain name? Max four users, most possibly only me.
I have to say I don't agree with @fediforum who consider #Bluesky part of the #fediverse. Is Bluesky making any attempts to interoperate with other fedi services that I'm not aware of?
As #Fedify's author, I'm contemplating its adoption beyond Ghost's #ActivityPub implementation. Finding potential users for ActivityPub tools seems challenging—perhaps I'm addressing a very niche need?
While the technical complexity of ActivityPub makes tools like Fedify valuable, I wonder about the actual market demand for federation outside specific communities.
Open, decentralized systems make sense to many developers, but businesses often prefer closed ecosystems that align with traditional models.
Still, I see potential as the #fediverse grows and digital sovereignty concerns increase. Fedify aims to lower the technical barriers to federation.
I'm curious: Which projects would benefit most from Fedify today? What would make federation compelling enough for platforms to implement?
Would appreciate perspectives from both developers and platform owners.
FediDeck is a Fediverse client with a multi-column interface reminiscent of the multi-column social-media interface created by Hootsuite long ago.
FediDeck is still in Beta, but — currently, it allows you to connect your Mastodon and Bluesky account.
Fediforschung beginnt mit Dir!
Das Fediverse ist groß, bunt und manchmal ein bisschen rätselhaft. Doch das sollten wir nicht als Nachteil betrachten, sondern als spannende Herausforderung. Deshalb hat @digitalcourage ein kleines Mitmach-Abenteuer erstellt für alle, die das #Fediverse besser verstehen wollen: Denn Neugier ist der Anfang von Erkenntnis und Wissenslücken bieten Gelegenheit, etwas Neues zu lernen. Wir müssen nur wieder Lust entwickeln, Technik selbst zu begreifen und uns damit digital selbst zu behaupten. So gewinnen wir die Freiheit und Mündigkeit zurück, die uns Big Tech permanent abtrainieren will.
Auf der Seite
https://digitalcourage.de/fediforschung
findest Du kleine Aufgaben, Experimente und Beobachtungen, mit denen Du das freie, dezentrale und wirklich soziale Netzwerk Schritt für Schritt erkunden kannst.
Viel Spaß!
(Textgrundlage aus dem heutigen Newsletter von Digitalcourage.)
#Fediforschung #Fediverse #digitalcourage #Spiel #Rätsel #Abenteuer
This is Postmodern, my concept for a #Fediverse platform. This mockup is a builder interface for making your own UI, timelines, and pages visually. It’s a weird and ambitious concept, but this is what I’ve been dreaming about for years.
Blog post dropping this week.
Drupal.community is a Mastodon server focused on Drupal, free and open source software and web development, but any content is welcome as long as it adheres to the Drupal Code of Conduct.
Find out more at https://drupal.community/about or contact the admin @pcambra
#FeaturedServer #Drupal #WebDev #WebDevelopment #CMS #FOSS #Mastodon #Fediverse #FreeFediverse
We're now in Trakt migration 2.0.
The move by Trakt that triggered Trakt Migrtation 1.0 was understandable, they have to make money.
But in this latest move, messing with grandfathered accounts, no, not understandable.
You just don't mess with grandfathered accounts ever in any service. That's your way of saying, "Thank you for always being with us since the beginning".
My mobile network plan is a grandfathered account, and the network have been trying to get us to "upgrade" to a "better" plan. Ad that's to mention one such.
Even in gaming, grandfathered accounts are not touched ever. If they cancel, that's the only time things change. Why? Simple, the current contract/subscription ended. So, the next time the user subscribe, it will be under the current scheme.
In addition, owners of grandfathered accounts will do everything to keep it. They'll borrow money if it comes to that. You have grandfathered accounts that are paying you but the owners are rarely using it. Compare that to the owners cancelling their grandfathered accounts because it no longer has any value for them.
Just like right now. Many are cancelling because.
Time to move to #NeoDB or #SIMKL
Pick NeoDB if you want to be in the #Fediverse. Or, pick SIMKL if you want free "Pro" just by logging-in at least 20 days.
Both NeoDB and SIMKL combines various databases into one easy to use interface.
I just set up an easy to remember link for my #NeoDB shelf/catalogue/library account:
https://loomenji.youronly.one ( @youronlyone )
😁
It's in addition to the following:
* fediverse.youronly.one - @youronlyone
* atmosphere.youronly.one - @youronly.one
* gallery.youronly.one - @youronlyone@pixelfed.social
* wiki.youronly.one - youronlyone.tiddlyhost.com
* threads.youronly.one - @youronly.one.ofcl
If you have a personal domain name, use it for redirection (301 or 302). Easy to remember.
Another advantage, if you ever decide to move instances or change your accounts, you don't have to reprint business cards and update links everywhere, just change your redirect target setting. (It won't move your content of course.)
And if you're bridging to the #ATmosphere network, you can use your own domain as your handle for your #Fediverse network accounts (if supported by your bridging platform)!
Make use of your domain name! Redirect!
I said I would publish this week, I guess it happened earlier than expected. This is a high-level overview of Postmodern, the #Fediverse platform I hope to someday build. It is the culmination of years of study as the network has continued to evolve.
I've been thinking about client-server interactions in the #fediverse. #ActivityPub #C2S isn't widely used, and most clients rely on Mastodon-compatible APIs instead.
What if we created a new standardized API based on GraphQL + Relay for client-server communication, while keeping ActivityPub for server-to-server federation?
The Mastodon-compatible API lacks formal schema definitions for code generation and type checking, which hurts developer productivity. And ActivityPub C2S is honestly too cumbersome to use directly from client apps.
#GraphQL would give us type safety, efficient data fetching (only get what you need), and the ability to evolve the API without breaking clients. #Relay's features for pagination, caching, and optimistic updates seem perfect for social apps.
Would this be valuable to our community? What challenges do you see? How might we handle backward compatibility? And should this be formalized as an FEP?
Curious what others think about this approach.
Week in Fediverse 2025-11-07
Servers
- Gush! v0.0.26
- Manyfold v0.128.0
- Wafrn v2025.10.02
- Hubzilla v10.6
- Ktistec v3.1.3
- Mastodon v4.5
- gancio v1.28.1
- Castopod v1.13.6
- tootik v0.19.8
- Loops v1.0.0-beta.4
- Lemmy Development Update October 2025
Clients
- IceCubesApp v2.0.9
- Mangane v1.18.5
- Tangerine UI for Mastodon v2.5
- Mastodon Bird UI v3.0.0
- PeerTube Mobile v1.2.0
- Voyager v2.40.2
- bleromo: A Windows 98-style Pleroma/Mastodon client
Tools and Plugins
For developers
- APx v0.20.0
- Fedialgo v1.2.32
- FIRES Server v0.4.0
- NGI0 Progress report #1 (GoActivityPub)
Protocol
- FEP-d8c8: BitTorrent Torrent Objects
- FEP-19b3: Specifying Properties of a Service
Articles
- Self-hosting your Mastodon media with SeaweedFS
- Fediverse Report – #141
-----
#WeekInFediverse #Fediverse #ActivityPub
Previous edition: https://mitra.social/objects/019a3c12-2a12-7683-592d-a0dec77f582e
Do you run a public Fediverse server? Are you accepting new members? Would you like to be listed on https://fedi.garden?
If so, please DM me 🙂
(NOTE: All the servers listed have to be compatible with the seven points at https://fedi.garden/about-this-site)
Fediverse Report #116 - This week's #fediverse news:
- @fediforum will be June 5-7 with a new advisory board
- updates from @bonfire on their upcoming platform
- A new fediverse onboarding tool by @fedidb
- Fediverse music sharing platform Bandwagon talks about their plans for financial sustainability
Nomadische Identität = magic! 🙂
#hubzilla #fediverse #nomad

