Oh My God :)) Now You can interact with my posts from your fediverse instance, by setting your instance in your browser localstorage, once this is set, click the Fediverse icon and you’ll see my post through your own mastodon/pleroma instance !
🔗 https://rmendes.net/notes/2026/02/22/d0c0e
working on writing FEDERATION.md i already found one easily fixable deviation (siteName instead of nodeName in nodeinfo).
#ktistec #ActivityPub #Fediverse
@m-goebel.info
Den Schritt bin ich auch gegangen. Der Blog meiner Webseite wird nun mit #ActivityPub ins Fediverse geschickt.
Obwohl das Protokoll das gleiche ist, wird ein Beitrag in Mastodon und Pixelfed jeweils ganz anders dargestellt. Beides sieht wieder anders aus, als der ursprüngliche Artikel. Das ist anfangs verwirrend. Bilder und zugehörige Texte werden z.B. getrennt oder es erscheint nur der Abstract und nicht der Text aus dem Beitrag. Man muss sich erst daran gewöhnen.
Btw. #GrassrootsStandards and standardization processes (such as the #FEP process) are a topic of Social coding commons and Social experience design, and we have a multi-author blog at https://coding.social ..
If you wish you might publish these results there as a report to spread about.
#SX #SocialCoding #SocialWeb #ActivityPub
Crafted this nice ActivityPub profile page for my Fedify/indiekit AP implementation, this is obviously for browsers, AP server receive an AP representation of my profile
Screenshot below is Fedify 2.0 built in debugger
🔗 https://rmendes.net/notes/2026/02/22/e0491
@toddsundsted very nice work! This is valuable information. #ActivityPub #FEP
Btw, just found the v2 release announcement of @fedify and that is a prime example on how, on the grassroots environment end of the spectrum we can maneuvre into better territory.
Kudos to the #fedify developers. Handing people tools they need to focus on solutions, and build without getting thrown into deep on-the-wire impl detail reeds to worry about.
That is the positive side of the equation. There's not only a big uptick in interest for the #SocialAPI i.e. #ActivityPub client-to-server, which offers new opportunity to correct course. But also are there more #FOSS projects focused on robust tool and library support for the 'Solution developer' stakeholder.
In the revamp of the delightful commons initiative, made possible with support of @nlnet I emphasized all these projects, while I de-emphasized the apps that are already doing good for themself, but contribute to further divergence from open standards.
https://delightful.coding.social
https://hollo.social/@fedify/019c8521-92ef-7d5f-be4d-c50eae575742
"Fedify 2.0.0 está aqui!
Esta é a maior atualização da história do Fedify. Destaques:
**Arquitetura modular** – O pacote monolÃtico `@fedify/fedify` foi dividido em pacotes independentes e focados: `@fedify/vocab`, `@fedify/vocab-runtime`, `@fedify/vocab-tools`, `@fedify/webfinger` e outros. Pacotes menores, imports mais limpos e a possibilidade de estender o ActivityPub com tipos de vocabulário personalizados.
**Painel de depuração em tempo real** – O novo pacote `@fedify/debugger` oferece um dashboard ao vivo em `/__debug__/` que mostra todo o tráfego de federação: traces, detalhes das atividades, verificação de assinaturas e logs correlacionados. Basta envolver seu objeto `Federation` e pronto.
**Suporte a relay do ActivityPub** – Suporte nativo a relays via `@fedify/relay` e o comando CLI `fedify relay`. CompatÃvel com os protocolos Mastodon-style e LitePub-style (FEP-ae0c).
**Entrega ordenada de mensagens** – A nova opção `orderingKey` resolve o problema do "post zumbi", quando um `Delete` chega antes do seu `Create`. Atividades com a mesma chave são entregues garantidamente na ordem FIFO.
**Tratamento de falhas permanentes** – `setOutboxPermanentFailureHandler()` permite reagir quando uma inbox remota retorna 404 ou 410, possibilitando limpar seguidores inacessÃveis em vez de tentar reenviar indefinidamente.
Outras novidades incluem negociação de conteúdo no nÃvel do middleware, `@fedify/lint` para regras compartilhadas de linting, `@fedify/create` para scaffolding rápido de projetos, arquivos de configuração para a CLI, suporte nativo à CLI em Node.js/Bun e diversos fixes de bugs.
Esta versão conta com contribuições significativas de participantes do OSSCA da Coreia. Agradecemos imensamente a todos envolvidos!
Trata-se de uma release major com breaking changes. Consulte o guia de migração antes de atualizar.
Notas completas da release: https://github.com/fedify-dev/fedify/discussions/580
#Fedify #ActivityPub #fediverso #fedidev #TypeScript"
@fediverse @tecnologia @academicos @internet (pode seguir para acompanhar os assuntos ou marcar para amplificar a postagem até no #lemmy tb)
@fedify https://hollo.social/@fedify/019c8521-92ef-7d5f-be4d-c50eae575742
@2ndStar Solchen Leute einfach mal #ActivityPub und #XMPP zeigen ubd sgen diese sollten aufhören in #proprietär|en Silos zu denken!
Fedify 2.0.0: Modular architecture, debug dashboard, and relay support
https://lemmy.ml/post/43537638
Fedify 2.0.0: Modular architecture, debug dashboard, and relay support
https://lemmy.ml/post/43537635
Though with regards to progress, there's a difference in both approaches.
At the #SolidProject side you have inertia by the slow standardization process. But should they figure things out in a good way, eventually the ecosystem catches up and the inertia can quickly decrease.
While at #ActivityPub side, since AS/AP remains stagnant, the ever increasing protocol decay and tech debt non-linearly increases inertia and progress. And on top of that, you are never done once you implemented the 'ad-hoc specs' of the installed base, and you have to account for continuous whack-a-mole development and maintenance burdens to fix #interoperability breakages.
The AS/AP based fediverse devolves into effectively no interoperability, and a situation that is more comporative to NPM dependency hell.