I have added the ability to my #activitypub deployment to subscribe to https://tags.pub federated hashtags but even tho I’m subscribed to a bunch of tags I’m not getting any content.

🤔 something is wrong and an afternoon debugging this proved a few issues but now I’m not sure what else to investigate to make this work…

Currently my only working Hashtag explorer from the Fediverse is built on fetching public server API timelines and kind of grep Hashtags from a selection of public servers, this allows me to build a multi instance hashtag timeline, it’s nice but I really wanted to get tags.pub working.

🔗 https://rmendes.net/notes/2026/03/22/48fbd

So, an interesting issue came up in the #Fedify repo that I've been thinking about: #629.

You know how every #fediverse server uses schema:PropertyValue in actor attachment for profile metadata fields (like “Website”, “GitHub”, etc.)? Turns out, strict #AS2 validators like browser.pub reject it, because the AS2 spec says attachment should only contain Object or Link—and PropertyValue is a schema.org type, not an Activity Streams 2.0 type.

The thing is, we can't just drop the type like we did with Endpoints (#576), because Mastodon and others rely on seeing "type": "PropertyValue" to render profile fields. But at the same time, it's technically not spec-compliant.

I'm leaning towards writing a #FEP to formalize this existing practice rather than trying to invent a new type (like toot:PropertyValue extending Object), which would be a nightmare to migrate across the whole fediverse.

What do you all think? Has anyone else run into this? Would love to hear thoughts from implementers and spec folks.

#fedidev #ActivityPub #ActivityStreams #ActivityStreams2 #AS2 #PropertyValue

Just had to add a workaround to #Fedify for http://joinmastodon.org/ns, a JSON-LD context URL that has never actually served a JSON-LD document. Mastodon has always inlined the term definitions, but some implementations put it as a bare URL in their @context, so Fedify's JSON-LD processor tries to fetch it and gets a 404 Not Found. Now Fedify ships a bundled copy of a context that never existed in the first place.

https://github.com/fedify-dev/fedify/pull/631

#fedidev #ActivityPub #JSONLD

My ActivityPub “reader” aka the view where I can check my home timeline and also explore public instance timeline is ugly but it works and it has this feeling that I built it, so if I’m not happy with it, I’m the only responsible to improve it.

Still… its an odd feeling that this is my fediverse home now and there is no coming back !

🔗 https://rmendes.net/notes/2026/03/17/2ae2c

Fedify - Hong Minhee

online, Monday, April 6 at 12:30 PM UTC

Good day all! Upcoming episode of Fireside Fedi!

The #livestream will be on: https://stream.firesidefedi.live

Special Guest: @[email protected]

An intersectionalist, feminist, and socialist living in Seoul (UTC+09:00). @tokolovesme's spouse. Who's behind @fedify, @hollo, and @botkit. Write some free software in #TypeScript, #Haskell, #Rust, & #Python. They/them.

So don't miss it!

It will happen on 06 March 2026 at 08:30 US Eastern Time ( UTC-4 )

If by any ungodly chance you miss the show:

#PeerTube ( #VOD ): https://tubefree.org/@firesidefedi

#firesidefedi #fediverse #fedi #interview #freesoftware #opensource #userfreedom #freedom #resistance

https://freestreamers.btfree.org/event/fedify-hong-minhee

@[email protected] follow

🔗 https://rmendes.net/notes/2026/03/15/b8609

If you see this post, please interact with it with a reply or like, I will then be able to retrieve your interaction to my blog/AP fedify instance and then I will test replying to your reply to demo threaded reply backfilled to my site
You can also comment using IndieAuth/indieweb if your site support it !

🔗 https://rmendes.net/notes/2026/03/15/fbb7d

I've been thinking about adding federation health monitoring to #Fedify—not as a separate data store or custom API, but by extending the existing #OpenTelemetry integration. The idea is to expose delivery outcomes, signature verification failures, and per-remote-host error rates as OpenTelemetry metrics alongside the spans Fedify already emits. If you already have a Prometheus or Grafana setup, you'd get federation observability basically for free. Circuit breaker behavior (temporarily skipping a remote server that's been consistently unreachable) could surface as OpenTelemetry events, keeping everything in the same trace context rather than scattered across separate logs.

Does this sound useful to you? I'm curious whether people building on Fedify—or running federated servers in general—would actually reach for this, and what kinds of things you'd most want to observe. Happy to hear any thoughts.

#fedidev #ActivityPub

I've been thinking about adding federation health monitoring to #Fedify—not as a separate data store or custom API, but by extending the existing #OpenTelemetry integration. The idea is to expose delivery outcomes, signature verification failures, and per-remote-host error rates as OpenTelemetry metrics alongside the spans Fedify already emits. If you already have a Prometheus or Grafana setup, you'd get federation observability basically for free. Circuit breaker behavior (temporarily skipping a remote server that's been consistently unreachable) could surface as OpenTelemetry events, keeping everything in the same trace context rather than scattered across separate logs.

Does this sound useful to you? I'm curious whether people building on Fedify—or running federated servers in general—would actually reach for this, and what kinds of things you'd most want to observe. Happy to hear any thoughts.

#fedidev #ActivityPub

This might be a dumb question, but if anyone here has used #botkit by #fedify : is there any way to host more than one bot without using different subdomains?

I'd like to self-host more than just my Ralsei bot and, as far as I know, an easy way to do it would be to use different subdomains for each one. However, right now I only have access to neofox.dedyn.io and no way to register/use other subdomains through my DDNS (and I'd like to keep using that for the time being)

From what I understood through the docs there might be a chance to achieve what I'm thinking about by using a custom Bot.fetch() method instead of passing the built-in one to Deno/Bun, but I'm not too sure, and that's why I'm asking here first