#Tag
I used to not like JSON-LD. And then I got exposed to CBOR. And, since then, I ended up liking JSON-LD more than I did before.
https://j12t.social/@j12t/114581086678041245
...
I was looking for performant ways of storing JSON-LD data, so that it can be looked up, queried, etc.
CBOR might actually be a way of doing that.
...
For me that is an odd realization given me liking JSON-LD is a reaction to CBOR.
#ActivityPub #ActivityStreams #CBOR #CBORLD #FediDev #JSONLD
⁂ Article
Native discovery of related tags (fedibuzz/tags.pub)
I was talking to my marketing guy about integrating a tags-based onboarding workflow for freshly installed forums.
The gist of it is, the forum admin adds a couple tags for the forum to globally follow, and achieves this via fedibuzz relay or tags.pub. Auto-categorization rules are automatically added and the forum starts receiving new (highly relevant!) posts through the magic of hashtag+federation ✨
He then asked whether it was possible to suggest related tags (e.g. add guitar suggest acousticguitar, electricguitar, etc.) for the admin to also add, to which I replied in the negative "for now".
But that got me thinking, is this something fedibuzz or tags.pub could achieve/offer in its API?[...]
⁂ Article
Native discovery of related tags (fedibuzz/tags.pub)
I was talking to my marketing guy about integrating a tags-based onboarding workflow for freshly installed forums.
The gist of it is, the forum admin adds a couple tags for the forum to globally follow, and achieves this via fedibuzz relay or tags.pub. Auto-categorization rules are automatically added and the forum starts receiving new (highly relevant!) posts through the magic of hashtag+federation ✨
He then asked whether it was possible to suggest related tags (e.g. add guitar suggest acousticguitar, electricguitar, etc.) for the admin to also add, to which I replied in the negative "for now".
But that got me thinking, is this something fedibuzz or tags.pub could achieve/offer in its API?[...]
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.
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.
This is a bonfire demo instance for testing purposes. This is not a production site. There are no backups for now. Data, including profiles may be wiped without notice. No service or other guarantees expressed or implied.
