NodeBB

@fedify maybe there would be something to do with semantic conventions for all/any activitypub implementation?https://github.com/open-telemetry/weaver

I wish I could use IndiePass to connect to my Fedify/Indiekit ActivityPub server so to have a unified publishing/reading experience for both Indieweb and ActivityPub right now I have this but only on the browser https://rmendes.net/notes/2026/02/27/624ea

Oh I have given a closer look at the Wfrn code and in fact its a full blown AP + Bluesky implementation that connect to Bluesky using a sidecar container connected the the Jetstream firehose, this is very interesting

I created this page to describe the Indiekit architecture powering this blog & AP server #fedify #indiekit #indieweb https://rmendes.net/notes/2026/02/26/d9488

You can easily fork this repo, customize the tests to your usecase and then run the test suite. git clone git@github.com:rmdes/activitypub-tests.git — Discovery — WebFinger resolution ✓ PASS WebFinger subscribe template ✓ PASS WebFinger error handling ✓ PASS NodeInfo endpoint ✓ PASS NodeInfo well-known chain ✓ PASS NodeInfo version format ✓ PASS NodeInfo content types ✓ PASS — Actor — Actor lookup (fedify) ✓ PASS Actor required fields ✓ PASS Actor JSON structure ✓ PASS Actor attachments (PropertyValue) ✓ PASS Actor multi-key (RSA + Ed25519) ✓ PASS Actor summary / bio ✓ PASS Actor alsoKnownAs ✓ PASS Actor manuallyApprovesFollowers ✓ PASS Actor icon and image ✓ PASS Actor not found (404) ✓ PASS Actor ld+json Accept header ✓ PASS — Collections — Outbox collection ✓ PASS Followers collection ✓ PASS Following collection ✓ PASS Liked collection ✓ PASS Featured (pinned) collection ✓ PASS Featured tags collection ✓ PASS Featured tags structure ✓ PASS Collection URI resolution ✓ PASS Collection pagination ✓ PASS Outbox traversal (first page) ✓ PASS Outbox actor attribution ✓ PASS — Content Negotiation — Post returns AS2 JSON ✓ PASS HTML requests don’t get AS2 JSON ✓ PASS Root URL redirects to actor ✓ PASS Object dispatcher (dereference) ✓ PASS — Inbox — GET inbox returns 405 ✓ PASS GET shared inbox returns 405 ✓ PASS Inbox 405 headers (Allow, Content-Type) ✓ PASS Unsigned POST to inbox rejected ✓ PASS — Instance Actor & Aliases — Instance actor (Application) ✓ PASS WebFinger alias resolution ✓ PASS — HTTP Protocol — HTTP headers compliance ✓ PASS Vary and CORS headers ✓ PASS — Endpoints — Authorize interaction ✓ PASS Public profile page ✓ PASS Quick replies 404 ✓ PASS ============================================ Results: 44 passed, 0 failed, 0 skipped https://rmendes.net/articles/2026/02/25/activitypub-federation-tests-fedify-2

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

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

Hi #fediverse and #ActivityPub developers! I'm currently working on interoperability testing for #Hollo and #Fedify, and I need a #Bonfire account to test federation with their implementation. Since there aren't many open public Bonfire instances available, I was wondering if any Bonfire instance admins out there would be willing to grant me a test account? It would be a huge help for improving interop! Let me know if you can help. Thanks! #fedidev #BonfireNetworks

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

"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

@stefan@stefanbohacek.online Thanks!

@kopper @hongminhee @julian addendum; updated the hierarchical UNESCO World Heritage Collection with their 1247 Entry-Collections having 8000 Places.Apart from `Content-Negotiation` Noticed that you can also get the jsonld in the browser just by adding ".json" e.g.https://www.wikidata.org/wiki/Special:EntityData/Q122842228.json