I'm happy to see new canadian social media like https://ehnow.ca/ and https://hey.cafe #canada
But so far, I still think #activitypub #mastodon and the #fediverse are the superior options.
Mostly because it's #decentralized and #federated
But most non-tech (normal) people don't understand those concepts.
They don't wanna deal with the fediverse because the learning curve is too high and they simply don't understand.
They just want something simple and that works.
Inaugural Post for Lemmy, a decentralized, easily self-hostable #reddit / link aggregator alternative, intended to work in the #fediverse:
【联邦宇宙正在发展:为什么去中心化社交媒体在2026年很重要】
https://blog.elest.io/the-fediverse-is-growing-why-decentralized-social-media-matters-in-2026
Attending the 'Growing the Open Social Web' online get-together by @fediforum.
Always nice to have the chance to talk with people (👋 @benpate) on the possibilities of the 'Open Social' web and learn from each other.
Compartimos esta gran noticia con ustedes!
A partir de esta semana estará funcionando en nuestros servidores, además de la instancia de Mastodon Uruguay, un relay activitypub. ¿Que es un relay? Es un servidor intermediario entre instancias del fediverso, que envía y recibe publicaciones "públicas" desde y para los servidores que estan suscritos al relay, sin importar si las instancias estén federando con esa cuenta o instancia.
Actualmente se dá el caso, por la arquitectura granular del fediverso, que haya cuentas que realicen publicaciones con visibilidad pública, que no aparecen en instancias amigas, por el simple hecho de que no hay nadie de la instancia suscrito a esa cuenta. Si las cuentas publican utilizando #hashtags, podrían llegar igual, porque los hashtags se federan, pero si no lo hace, esa cuenta seguramente no aparezca en los muros de federada de otras instancias. Cuando una instancia se suscribe a un relay, envía todas las publicaciones con visibilidad pública al relay y recibe de éste, las publicaciones con visibilidad "pública" de otras instancias.
Es una forma de potenciar el intercambio y el flujo de publicaciones entre instancias para agrandar el fediverso visible. Existen muchos servidores relay, pero generalmente están en el norte. Los servidores relay consumen recursos y ancho de banda por lo que muchas veces solo se admiten instancias manualmente que cumplan con ciertos criterios, como por ejemplo, estar en alguna región geográfica, ser instancias temáticas o comunidades específicas.
Es por esto que para poner la frutilla de la torta luego de la migración nuestra instancia a un servidor dedicado y mejora de los servicios en general, que decidimos montar nuestro propio relay cuyo fin será potenciar el fediverso latinoamericano.
Mensaje para admins:
Si quieren suscribir vuestra instancia al relay activitypub, deben contactar a @j3j5 o @admin por privado, desde las cuentas admin de la instancia. Solo agregaremos por el momento, instancias latinoamericanas. La URL del relay para agregar en la consola de administración de Mastodon es https://relay.mastodon.uy/inbox
Complete this sentence:
"I experience #fediverse as a .."
#Poll #AskFedi #Microblogging #Mastodon #ActivityPub
Options: (choose one)
There's a new project called Holos which makes it a lot easier to host a Fediverse server on your own mobile device. You can follow the project at:
➡️ @HolosSocial
The official site explains how it works:
➡️ https://holos.social/how-it-works
To manage expectations, it's still in its early days and mainly for techy people at the moment. However, it will be interesting to follow its development 🙂
Holos is by the makers of the Mastodon/Fediverse mobile app Fedilab.
RE: https://social.growyourown.services/@homegrown/116155421471110983
Existe un nuevo proyecto llamado #Holos que brinda la facilidad de tener tu propio servidor del #Fediverso en tu dispositivo móvil. Puedes seguir el proyecto en:
➡️ @HolosSocial
La web oficial explica cómo funciona:
➡️ https://holos.social/how-it-works
Para calmar expectativas, aún está en sus etapas iniciales y orientado a personas con conocimientos técnicos por ahora. Sin embargo, será interesante seguir su evolución 🙂
Holos es creado por los desarrolladores de la aplicación móvil para Mastodon/Fediverso #Fedilab.
I've been saying for a while that we need something like FediCon in East Asia. A dedicated conference is still a stretch, but I've been thinking about a smaller step:
@COSCUP 2026 (Taipei, Aug 8–9) is accepting proposals for community tracks. It might be worth trying to open a Social Web track there—something in the spirit of the Social Web devroom at FOSDEM.
Nothing is decided yet, but if you're working on #ActivityPub, the #fediverse, or anything in the social web space and might be interested in speaking (or co-organizing), I'd love to hear from you.
Miło nam zaoferować społeczności fedi wydajny hosting #WordPress z #ActivityPub czyli pełną obsługą #Fediwersum w Twojej domenie.
Efekt "fedi hug of death" nie występuje, możesz śmiało publikować dla szerokiej publiczności, podbicie przez konta z dużą ilością obserwujących nie wyłączą ci strony!
Zainteresowani?
Koszt to 300zł rocznie 🚀 wsparcia naszej organizacji. Twój WordPress nasza opieka i serwery 🛟
Opinia użytkownika @LukaszHorodecki prowadzącego znany blog Silva Rerum @silvarerum :
> "Wszystko działa idealnie" 👍
Zapraszamy do kontaktu 📬
Loops just shipped support for more interactionPolicy types, giving our community more control to limit certain interactions, like disabling comments or QuotePosts.
Huge shout out to GotoSocial and @dumpsterqueer for stewarding this ActivityPub extension to better protect our communities.
Isn't it amazing what is possible when projects that would normally compete with each other, can instead collaborate and build safer communities for all?
We all win when we put people first.
Loops Starter Kits are almost ready to ship!
Consent is crucial to prevent abuse, so you will need to get approval for every account you want to include in each kit.
We will add a setting to auto approve every request, as well as the ability to disable this for your account to auto reject if desired.
Shipping soon!
🐍🤖 Saiu post novo no blog!
Ontem no encontro da https://bolha.us sobre ActivityPub a gente bateu um papo incrível sobre bots no Fediverso — e esse post é o resultado prático disso.
👉 Construindo Bots para o Fediverso com Python e apkit
https://www.riverfount.dev.br/posts/translate-bot/
Cubro tudo o que você precisa pra criar um bot ActivityPub do zero:
→ Por que usar apkit em vez de Mastodon.py
→ WebFinger, HTTP Signatures e RSA na prática
→ Um bug real de produção com digest SHA-256
→ 96 testes e os padrões de mock que aprendi na prática
O caso de estudo é um translate-bot: recebe menções, detecta o idioma e responde com a tradução direto na thread.
El #takahe me chiva los tuneos que hace la gente con #activitypub
ERROR - ('Invalid JSON-LD syntax; "@id" value must be a string.',)
Type: jsonld.SyntaxError
Code: invalid @id value
Details: {'value': None} | from: users.identity actor:https://cryptid.cafe/users/rowan @cryptid.cafe
In the #Fediverse, most software is built around a specific platform model. One for microblogging, one for video, one for photos... and new ones will keep coming.
With #Holos, your phone runs your own #ActivityPub server. You control your data and can use your own domain as your identity.
Built on the protocol, not a platform model, Holos is not limited to a single use case. One account that adapts to your needs.
That's where we're heading, and we hope for your support.
Decentralize it. We're getting there. The details are:
Servers and apps for reading, watching and listening that require no middleman. See #ghost #wordpress @wallabag #peertube #owncast #podcasting
The social news feed that lets important news and ideas go viral without algos or anybody being able to shut down access for large portions of the network. That's everything using #ActivityPub.
Direct automatic funding of journalism using an open protocol. #interledger #PublicPatron #FediForFiat
From today each user with an account on synthpub.com can drop and share their (uncut) #synth or #modular jam sessions on our new #funkwhale instance 🔊 DM me to get a free access code and start sharing! #activitypub #fediverse #eurorack
My first drop 😎
https://sound.synthpub.com/library/tracks/2
Week in Fediverse 2026-02-27
Servers
- Bookwyrm v0.8.5
- Gush! v0.0.31
- Hollo v0.7.4
- flohmarkt v0.16.0
- Mastodon v4.5.7
- Wafrn v2026.02.02
- GoToSocial v0.21.0
- Loops v1.0.0-beta.10
- Ktistec v3.3.1
- Mitra v4.19.0
- Stegodon v1.8.0
- Hometown v1.2.0
- gathio v1.6.1
- Castopod v1.15.5
- NodeBB v4.9.0
- PieFed v1.6.7
Clients
- Pachli v3.4.0
- tooi v0.22.0
- Summit v1.78.1
- Photon v2.3.0
- Blorp v1.10.3
- Phanpy changelog
Tools and Plugins
- Poduptime v6.2.1
- Fediverse invitation
For developers
Protocol
- FEP-a427: Server Domain Migration
- FEP-fc48: Generic ActivityPub server
Articles
- Self-Hosting Pixelfed: Federated Instagram Without the Algorithm
-----
#WeekInFediverse #Fediverse #ActivityPub
Previous edition: https://mitra.social/objects/019c7c6f-742a-7930-2413-73b1d9611c99
There's now a proper rendered web interface for FEPs at https://fediverse.codeberg.page/fep/fep/*/, which is much nicer to read than the raw Markdown source on Codeberg. But the canonical permalink, https://w3id.org/fep/*, still redirects to the Markdown file rather than the rendered page.
Would it make sense to update the w3id.org redirect to point to the rendered version instead? It seems like the better experience for anyone following a FEP link, and arguably what a “permanent” link should resolve to—something human-readable.
I'm not sure who manages the w3id.org/fep/ redirect configuration. (It lives in the perma-id/w3id.org GitHub repo, so it would just be a PR, but I'd want to get community consensus first rather than just send one in unilaterally.)
Recently, there was a discussion about generic #ActivityPub servers. Several people claimed that they were working on one, but it turned out that their "generic" servers only support activities defined in the ActivityPub specification. Such a server shouldn't be called generic. It is not difficult to build, neither it is an interesting concept because competing protocols (e.g. Nostr) already offer much more.
I've been writing a #FEP that describes how to build a real generic server. It is not finished yet, but I feel like now is a good time to publish it:
FEP-fc48: Generic ActivityPub server
This kind of server:
- Can process any object type, and can process non-standard activities like EmojiReact.
- Compatible with FEP-ae97 clients.
- Does not require JSON-LD.
I attempted to implement it when I was researching security properties of FEP-ae97 API: https://codeberg.org/silverpill/fep-ae97-server. Back then I didn't know what to do with side effects, but now I think that we can simply force clients to specify them.
https://mnmm.top/AH6
Tumblrの #ActivityPub 対応、ひと頃は期待もしていたけれど、今更ながらだけど必要ない気がするのよね。
今更リソース費やして再構築しなくても「Tumblr」って名前で #Mastodon サーバ立てて、ソレっぽくカスタマイズすればいいだけの話だし、でもそうしてしまうとソレはTumblrでは無いよね。
#Threads の様なActivityPubに流し込むだけの対応なら、同じ #Automattic 社の #Wordpress がプラグインで実現しているし、とうのThreadsがその対応自体を消極的評価でとりやめてしまうし。
Started laying out a rough plan for implementing FEP-ef61: Portable Objects in #Fedify—server-independent #ActivityPub identities backed by #DIDs, multi-server replication, and client-side signing. It's going to be a long road (13 tasks across 5 phases, with a few open questions that need answering before we even begin), but I think it's worth doing right.
https://github.com/fedify-dev/fedify/issues/288#issuecomment-3971459585
The intro to HDA (Hypermedia-Driven Applications) I've been raving about today seems relevant to the ongoing discussions about C2S APIs for the fediverse, especially the proliferation of the monolithic server+web-app antipattern. I've started a SH topic on it;
But SH seems like a ghost town ATM. Tried to post on ActivityPub.space but their interface hates my mobile browser (Fennec from F-Droid) 🤷♂️


