#opensocialweb #fediverse #bluesky #nostr
very interesting conversation between @rabble.nz and @mike
(and I wish @rabble.nz had a #peertube channel 🙂 )
#opensocialweb #fediverse #bluesky #nostr
very interesting conversation between @rabble.nz and @mike
(and I wish @rabble.nz had a #peertube channel 🙂 )
Free your Social Media/ Soziale Medien jetzt aneignen! – Kommt in's bunte selbstverwaltete #Fediverse!
Input und Workshop auf dem @dearfuture in der Volkshochschule #Dresden
dresden.network, @datenkollektiv und @BitsUndBaeumeDresden bieten im Rahmen des #DearFuture-Festivals am 14. Mai von 16:00 Uhr bis 19:30 Uhr in der VHS Dresden einen Workshop gezielt für Vereine, Initiativen und ähnliche Organisationen zum Fediverse an.
Alle wichtigen Infos findet ihr hier online:
https://dearfuturedresden.de/festival2025/programm/datenkollektiv-net
Fediverse Report #115 - This week's #fediverse news:
- @peertube launches v1 of their mobile apps
- @Mastodon shares more information on their team is growing
- @swf launches places.pub, a way to put OpenStreetMap data directly on #activitypub
The other day I finally got it. Why #Bluesky is so popular with "regular people" (aka non-techies). It's because it's CENTRALIZED (of course the Bluesky folks would never admit it out right).
One name: Bluesky.
One official URL to join / browse / post messages
One official app: "Bluesky Social" on app stores
In this post-literate society where people have been trained by commercial social media for 2 DECADES to choose the easiest, most frictionless option, of course they will pick Bluesky over the #Fediverse.
Try introducing the concept of servers / instances and names like Mastodon, Sharkey, Pleroma, GoToSocial, Friendica, Pixelfed, PeerTube, Lemmy to people not familiar with them. They'd think you're speaking a foreign language.
The Fediverse is made up of thousands of independent servers. You can't log in to https://joinmastodon.org or https://joinpeertube.org to browse Mastodon or PeerTube. Conversely, when you log into Bluesky you see messages by Bluesky members.
People need to be educated first about defederated options and their numerous advantages.
I get it now. I'm still 1000% in when it comes to the Fediverse but I understand.
And I'm tired.
And I'm posting this here on my GoToSocial account because I wanted to say my piece in one go and I would have run into Mastodon character limits.
How many people have I convinced to join the Fediverse in my 9 months advocating for it through a blog? TWO. How many people are still active on it? One.
Off I go play with LEGOs with my little one - in 12 years, when she's old enough I will set up her own instance. So Fediverse, you gotta be thriving in 2037.
Some questions for all the #GoToSocial users out there.
How many gigabytes of disk space (roughly) does your instance use?
How long has it been online?
And does the growth in storage slow down after the first seven days (on the default configuration), when cached images start clearing out?
#FediHelp #SelfHost #SelfHosted #Fediverse
I found this cool #Fediverse software called #NeoDB via @dansup 's awesome FediDB website.
https://fedidb.com/software/neodb?version=latest®istration=open
It's a tracking / shelf platform for #TV / #drama, #movies / #films, #books, and #games
Automated import from #Goodreads work well. Just provide the required URL and voila. If it doesn't appear immediately, it is probably waiting for server workers or waiting for the server load to lower or Goodreads request limit, just be patient, only submit the same URL once! If in doubt, contact the admins instead of resubmitting.
Unfortunately, the software doesn't support import (automated, API, or manual) from Trakt, SIMKL, MyAnimeList, and other popular tracking/shelf services for TV/drama and movies/films. There is one, Douban or something, which I think is popular in the Chinese and Japanese speaking markets.
Anyway, what if the item you want to add doesn't exist in the database yet?
Worry not! There are three ways NeoDB software populates its database.
* Method 1: You can add the details yourself
* Method 2: Search the other NeoDB instances for existing similar items
* Method 3: Search for the item from TMDB, IMDB, IGDB, Steam, Goodreads, and other supported sites (no TVDB), and paste the URL to NeoDB's search box and it will import it to your instance
Method 2 is already sweet. That is the entire idea of the #SocialWeb. But Method 3 is even sweeter!
Methods 2 and 3 are the best because it's a win-win for everyone. Regular users can forget about manually re-entering new data. Seriously, who wants to manually duplicate data from one DB to another? I certainly don't! I contribute to #TMDB but I'm definitely not repeating the same effort in #TVDB.
Secondly, there's no need for instances to duplicate large databases just to ensure their site is useful for any user. Items are added as local users interact with the items. It keeps the db small instead of having thousands of items no one has interacted to yet (or probably not).
Check my accounts:
* Flagship server: @youronlyone
* Instance: @youronlyone@eggplant.place
~~Hmm… I haven't checked but I think music is not supported (yet?). NeoDB can use the largest #OpenDB for music: #Musicbrainz ~~
UPDATE: Music is supported, as well as, #podcasts .
🖖🏽🙇🏽
EDIT: the person I contacted replied and the new posts have the correct attribution. So the problem is solved.
There is a Mastodon instance that publishes content from its own PeerTube instance. These contents are narrated aloud, likely by an AI, in several languages, and are based on articles that appear online. Today this happened with an article I shared from my blog.
The problem is that there is no attribution to the original author and or the original source site. On the contrary, it gives the impression that the content was produced directly by whoever runs that site or instance.
This is completely detached from the idea of properly sharing information. Taking inspiration is a wonderful thing. Claiming someone else’s work as your own is not.
I contacted the account in question this morning. I have not received any reply, even though other content has been published in the meantime. A short while ago I also contacted the instance administrator.
I will wait until tomorrow morning. If I do not receive a satisfactory response, I will publicly disclose the instance and the related content and block the entire domain. There are additional details that I prefer not to reveal at this time which further worsen the situation.
This is not how we act in the Fediverse.
In the Fediverse we respect one another.
Let us avoid bringing improper practices here. You are free to use my posts as you wish. You can even make money by applying my advice.
Just do not take away my attribution.
Noch auf der Suche nach #News und offiziellen Accounts von Medien hier auf #Mastodon und im #Fediverse?
Meine immer aktuelle Tabelle enthält jetzt nicht nur Accounts auf Mastodon und anderen Fediverse-Diensten, sondern auch welche auf #Flipboard, #Threads und #Bluesky – allesamt von hier abrufbar.
Insgesamt sind es jetzt 942.
➡️ https://fingolas.eu/fediverse/overview.html
(hinter dem "Custom Search Builder" links darüber gibt's eine mächtige Suche)
After shutting down #HolosDiscover, we're rethinking the approach with #HolosIndex: users explicitly opt in by adding #HolosIndex to their bio with interest tags, then submit their profile. No assumptions, no default settings.
This will power interest-based discovery across the #Fediverse, helping people find each other through shared interests. Still all through #ActivityPub of course, with real-time deletions and updates.
It's probably less of a problem now that the fediverse is much bigger (than it was 5 years ago). But one of the things I've heard puts newbies off alternative social apps/ networks is too much meta-discussion about development and deployment of the apps/ networks themselves.
Maybe we could agree on a standard way of tagging this stuff (eg #DevMeta)? Then the DevMeta tag could be filtered out by default for newbies.
(1/3)
Fediverse Icons
https://github.com/reiver/fediverse-icons
Free, and in SVG format.
#DeSo #Fediverse #FediverseIcons #Calckey #Castopod #Forgejo #Friendica #FunkWhale #Gitea #GreatApe #Hubzilla #Lemmy #Mastodon #Misskey #Pixelfed #Pleroma #WordPress #WriteFreely
Week in Fediverse 2026-02-13
Servers
- Stegodon v1.7.1
- Hollo v0.7.2
- Manyfold v0.132.1
- Mbin v1.9.1
- tootik v0.21.0
- Mitra v4.18.0
- ActivityPub for WordPress v7.9.1
- flohmarkt v0.14.4
- PieFed v1.6.4
- Trunk & Tidbits, January 2026 (Mastodon)
- OpenSimulator ActivityPub Bridge
Clients
- Fedilab v3.36.1
- toot v0.51.1
- tooi v0.21.0
- Jerboa v0.0.85
- Interstellar v0.11.2
- Pixelix v4.3.0
- Fedi Reader: A link-focused Mastodon news reader for iOS and macOS
Tools and Plugins
- ap-thread-reader: ActivityPub-compatible Thread Reader (not only for Mastodon)
For developers
- Progress Report - February 2026 (GoActivityPub)
Articles
- On fediverse content warnings and filters
- Trusting Trust in the Fediverse
- Adding Fediverse Comments to a Pelican Blog
-----
#WeekInFediverse #Fediverse #ActivityPub
Previous edition: https://mitra.social/objects/019c3449-e714-29e9-b9f6-03cc6804b4aa
There's a lot of energy on the #Fediverse right now to discuss/find a #Federated alternative to #Discord using #ActivityPub.
@strypey suggested that I put this out there to anyone who's thinking about it. We could probably rebuild most of Discord's features as an #Emissary inbox without doing a lot of back end code.
I'm too swamped to start on this right now. But if you're a great HTML+CSS designer, I'm able to give some time to a team who wants to take this on.
As someone who has developed several #ActivityPub software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.
The challenges are numerous:
First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.
Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.
Perhaps most concerning is the poor #accessibility. Most implementations simply use the emoji code (like :party_blob:) as the alt text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.
What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.
3 THINGS I'm grateful for when it comes to the #Fediverse:
1: I (almost) never see any AI slop. I'm subscribed to @404mediaco and I'm constantly horrified by their articles on AI slop - so common on Meta platforms. Not here. So #ThankYouFedi.
2: I'm never force-fed content by people I don't follow – so common in other places where algorithms rule. My time & attention are treated with RESPECT.
3: People here protect the privacy of children / don't post their pics. Consent is BIG. #ThankYouFedi
Just rolled out some fediverse-related improvements:
- Now you can follow Write.as blogs from Ghost! There was a tiny bug with this that we just fixed. (WriteFreely PR: https://writefreely.org/pull/1373)
- We now support the `preview` property as a fallback for Articles. This will make your posts look much nicer as more platforms support it! (WriteFreely PR: https://writefreely.org/pull/1374)
#WriteAs #WriteFreely #WriteFreelyDev #Ghost #fediverse #ActivityPub
Since #NeoDB also has a "social" feature, it's awesome that we can login in #Fediverse apps. For users who prefer to use their NeoDB account beyond just a shelf/tracking/library can do so.
For example, this post was made via the #Fedilab #Android app.
Excited to be collaborating with this incredible group of people to advise @fediforum and help push the #SocialWeb and #Fediverse forward.
See you at #FediForum (June 5-7, online)!
Register now: https://events.humanitix.com/fediforum-june-2025/tickets
❤️ Thank you @bagder for maintaining #curl since 1998. What would we do without it, how long would it take us, and what code quality would those solutions have without you? Thank you so much! ❤️
...and how on earth would people be able to check the weather forecast without curl? 😉
(Please join me in thanking Daniel, and let others here on the #Fediverse know about your favourite ways of using #curl )
I've got a quick favour to ask. If you're reading this post on Mastodon (or the Fediverse), please click boost.
How come?
I recently moved across to my own self-hosted single-user server (using GoToSocial.org). For a bunch of reasons, including visibility across the Fedi, it would really help out.
#Fediverse #FediHelp #gotosocial #mastohelp
#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
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.
Wenn Euch ein Beitrag gefällt und Ihr deshalb möchtet, dass dieser möglichst vielen Anderen angezeigt wird, dann ist TEILEN das Mittel der Wahl!
Favorisieren ist für die/den Verfasser:in nett, bringt darüber hinaus aber gar nichts.
Da es im #Fediverse keine Algorithmen gibt, die irgendwas thematisch nach oben spülen, erfüllt allein das Teilen die Funktion, lesenswerten Beiträgen Reichweite zu verschaffen.
Week in Fediverse 2025-05-09
Servers
- Owncast v0.2.2
- Mastodon v4.3.8
- Mitra v4.2.0
- snac v2.76
- Misskey v2025.5.0
- NeoDB v0.11.6.7
- tootik v0.16.0
- kmyblue v18.1
- Vernissage Server v1.12.0
- Gush! v0.18.0
- May 2025: What’s In The Pipeline (Bandwagon.fm)
- Blocking users (Ghost)
- Trunk & Tidbits, April 2025 (Mastodon)
Clients
- Voyager v2.34.0
- Blorp v1.4.0
Tools and Plugins
- Lemmy Schedule v1.15.0
- Enable Mastodon Apps v1.4.6 (WordPress plugin)
- peertube_recomendation_algorythm: A browser extension that monitors the peertube videos your watch and stores them locally
For developers
Articles
- When decentralization can get too big!
- Town squares, backyards, better metaphors, and decentralised networks
- Il Fediverso a scuola: uno strumento didattico per la cittadinanza digitale
- Fediverse Report – #115
-----
#WeekInFediverse #Fediverse #ActivityPub
Previous edition: https://mitra.social/objects/0196929b-a80a-322f-a1ba-f42864034290