¿Sabían que Write.as no es solo una plataforma de blogs minimalista, sino uno de los pilares de la publicación larga dentro del Fediverso gracias a su integración nativa con el protocolo ActivityPub?
Lanzada originalmente a finales de 2014 como una herramienta enfocada estrictamente en la privacidad y el anonimato —donde ni siquiera era necesario crear una cuenta para publicar—, la plataforma evolucionó para permitir que cada blog funcione como una cuenta de red social federada. Esto significa que un blog en Write.as posee una dirección de usuario con el formato @usuario@write.as, la cual puede ser buscada y seguida desde instancias de Mastodon, Pleroma o Friendica como si se tratara de cualquier otro perfil, pongo como ejemplo mi propio blog https://text.tchncs.de/mdtblogmx/ que como verán esta en la instancia wtite.as de text.tchncs.de el cual puede seguirse desde cualquier cuenta del fediverso dándole follow a @mdtblogmx
La arquitectura de Write.as se basa en el software de código abierto WriteFreely, lo que garantiza que los artículos publicados se distribuyan automáticamente a los "muros" o líneas de tiempo de los seguidores en el Fediverso, permitiendo que las interacciones como "me gusta" o "impulsos" (boosts) se sincronicen entre servidores distintos. A diferencia de las plataformas de blogs tradicionales que dependen de lectores RSS o boletines de correo, Write.as utiliza la infraestructura descentralizada para convertir un texto estático en un objeto social dinámico que puede ser comentado y compartido a través de diferentes plataformas compatibles. Esta integración permite que el contenido extenso y analítico recupere visibilidad en un entorno dominado por mensajes cortos, manteniendo la interoperabilidad sin rastreadores ni publicidad.
#WriteAs #Fediverso #ActivityPub #Blog #Tecnologia #Mastodon

The first time you click a Fediverse button on my site, you’ll be asked to enter your home instance — in other words, your own Fediverse server. This can be a self-hosted instance or a platform like Mastodon, Pleroma, and others.
Once that’s set, clicking on an “Also on” syndicated post link will open the corresponding URL directly inside your own Mastodon instance. From there, you’ll see it as a native Mastodon post, which means you can reply, boost, or favourite it just like any other post in your timeline.
The same logic applies to the “Fediverse” sidebar widget. It reads the instance you previously saved in your browser’s localStorage and uses it to trigger a remote follow request directly from your own Mastodon account.
🔗 https://rmendes.net/notes/2026/02/24/bada4
@steve seems possible to me too, and is also the premise of Protosocial #ActivityPub extension.
Nous poursuivons avec notre prochain conférencier Julian Lam @julian qui nous démontre comment les forums peuvent surmonter le défilement infini des fils d’actualité.
Il est le co-fondateur de @nodebb une plateforme de forum communautaire open-source avec support #ActivityPub intégré, connectant les forums traditionnels au #WebSocial.
#FediMTL #Fédivers #SouverainetéNumérique

En direct avec Christine Lemmer-Webber @cwebber Co-fondatrice de @spritely et co-auteure du protocole #ActivityPub.
Une réflexion sur des enjeux cruciaux : comment bâtir un Internet social en période de tensions et de conflits? Sommes-nous encore loin du #WebSocial auquel nous aspirons? Que fait déjà bien le #Fédivers aujourd’hui — et surtout, comment aller plus loin?
#FediMTL #SouverainetéNumérique

What if... you had one Fedi account on a generic headless #ActivityPub server that simply hosts and federates your data... and had C2S UIs for microblogging, long form writing, media editing and sharing, link aggregation, games, fitness tracking, and so on, that all used that same Fedi account. Technically, it's a similar concept as ATProto (but no relay and app view) and Solid Pods (but no RDF).
It seems possible... if we can improve the AP C2S API/protocol sufficiently.
📦 New release for mastodon/mastodon!
Version: v4.5.7
Name: v4.5.7
<h1><picture>
<source media="(prefers-color-scheme: dark)" srcset="./lib/assets/wordmark.dark.png?raw=true">
<source media="(prefers-color-scheme: light)" srcset="./lib/assets/wordmark.light.png?raw=true">
<img alt="Mastodon" src="./lib/assets/wordmark.light.png?raw=true" height="34">
</pictur...
Check it out and contribute! 🚀
https://github.com/mastodon/mastodon/releases/tag/v4.5.7
#activitypub#opensource #mastodon#fediverse
@herrjemineh @activitypub.blog naja, jeder neue Post muss an alle Server deiner follower geschickt werden. Die Server der Follower schicken dann eventuell direkt noch ein paar Anfragen zurück, um zusätzliche Informationen wie dein Profil zu laden.
Was bedeutet das? Je mehr #ActivityPub follower dein Blog hat, desto höher sind die Anforderungen an deinen Server.
Da kommt der günstige Webhost wohl an seine Grenzen.
A couple days ago, I got a DM from a #Bonfire user. I happily replied and sent
a follow request—but the Accept never came back, even though they hadn't
enabled manuallyApprovesFollowers. My DM reply probably never arrived either.
Classic interop bug.
I checked out the Bonfire source and dug in. Turns out Bonfire hasn't
implemented RFC 9421 yet, so it was silently discarding any activity signed
with it. That alone would be workable, except for one more issue: Bonfire was
responding 200 OK even when signature verification failed, instead of
401 Unauthorized.
This matters because Fedify implements a double-knocking mechanism—if a
request signed with RFC 9421 fails, it retries with the older draft cavage
signature. But since Bonfire returned 200 OK on the failed first knock,
#Fedify had no reason to send a second one.
I filed two issues on the Bonfire #ActivityPub repo—one requesting
RFC 9421 support, and one about returning 401 on invalid signatures. For
the latter, I also sent a PR, which got merged pretty quickly:
bonfire-networks/activity_pub#9.
That said, individual Bonfire instances won't pick up the fix until they
actually deploy it. So in the meantime, I patched Hollo and Hackers' Pub to
use draft-cavage-http-signatures-12 as the firstKnock, so Bonfire
instances can at least understand the first request.
One last thing: Fedify caches whether a given server supports RFC 9421, and the
Bonfire servers I'd already talked to were cached as “supports RFC 9421”—because
they'd been returning 200 OK. I had to manually clear that cache on
both hollo.social and hackers.pub before everything finally worked.
After all that, the mutual follow went through and my DM reply landed. Worth it.
#fedidev #fediverse #Hollo #HackersPub
Den sociala gemenskapens strukturer i sociala nätverk styrs av de protokoll som används. I en intressant artikel på sajten Connected Places skriven av Laurens Hof går han igenom hur de två dominerande protokollen, ActivityPub och AT-protokollet styr hur gemenskaper skapas, modereras och administreras.
https://blog.zaramis.se/2026/02/24/den-sociala-gemenskapens-strukturer/
Il est dit que #hubzilla fédère avec tout le #fédivers, autant #Mastodon que #Diaspora, #Friendica et tout ce qui utilise le protocole #ActivityPub.
Or, depuis le compte du post ci-dessous, je ne vois quasiment personne de mes contacts habituels, ni aucun de mes autres comptes.
Juste de parfaits inconnus non françophones.
C'est con parce que ça a l'air très complet en possibilités et offres de services.
zotum.net/channel/vieuxmalebla…
#HolosDiscover is back, from a clean slate.
A #Fediverse search engine that uses standard #ActivityPub federation. It follows you like any account, respects indexable flags, #nobot, #noindex, locked accounts. Deletions, edits, blocks are processed instantly through ActivityPub.
You have full control. Block it, mention it with "unfollow", or disable indexing in your settings.
Source code under AGPL-3.0 on #Codeberg.
Details: https://discover.holos.social/how-it-works
Account: @HolosDiscover