came across a thread by @LiquidParasyte about things they are coming across that need work or are broken on @Bonfire
https://indieweb.studio/post/01KJ0T79KGJRWHYTKWJJF4254R
#fedidev #bonfire
fedidev
RE: https://mastodon.social/@reiver/116681762071911900
P2P CDN for Low-Cost Video and File Delivery
1/
A CDN is a service that stores copies of your website's files in many locations around the world so visitors can download them from a nearby server instead of one far away. This makes your website load faster and stay available even when lots of people are using it at the same time.
CDNs are not only important for Fediverse servers but they are important for the Web in general
…
#FediDev #CDN #ContentDeliveryNetwork #ContentDistributionNetwork
I've seen an ongoing debate between "Note" versus "Article" in ActivityPub / ActivityStreams.
When is something a "Note"‽
When is something an "Article"‽
Personally — I would probably have made the distinction this way.
An "Article" has a title.
A "Note" doesn't have a title.
(In ActivityPub / ActivityStreams, a 'title' seems to tend to get represented in the "name" field.)
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!
The next step in our #activitypub implementation is ready! This brings a simple instance actor object along with #webfinger support for it and a #nodeinfo endpoint.
We highly appreciate reviews from any #fedidev 🙏
codeberg.org/Klasse-Methode/...
We are really greatfull for @nlnet@social.nlnet.nl to fund this work and for @linos for being such a great mentor!
Started laying out a rough plan for implementing FEP-ef61: Portable Objects in #Fedify—server-independent #ActivityPub identities backed by #DIDs, multi-server replication, and client-side signing. It's going to be a long road (13 tasks across 5 phases, with a few open questions that need answering before we even begin), but I think it's worth doing right.
https://github.com/fedify-dev/fedify/issues/288#issuecomment-3971459585
When I first started working with #ActivityPub, before #Fedify existed, it felt like writing web apps in Perl and CGI in the late '90s. Interesting, even exciting—but never comfortable. That era where your business logic and your protocol plumbing were just… the same thing:
print "HTTP/1.1 200 OK"
print "Content-Type: text/html"
print
print "Hello, world!"Decades of web development have given us layers of abstraction we now take for granted. Nobody hand-parses application/x-www-form-urlencoded query strings anymore. Nobody writes their own JSON codec, or manually constructs HTTP request/response messages. These things just aren't your problem when you're building an app.
ActivityPub development still feels like they are your problem. What do you do when the https://www.w3.org/ns/activitystreams#actor property comes in as a string instead of an array? What about when https://www.w3.org/ns/activitystreams#object is an embedded entity rather than a URI? How exactly do you implement HTTP Signatures? And wait—what's Linked Data Signatures, and do you need that too?
The real issue isn't that ActivityPub is complicated per se. It's that you can't get away with understanding it at a high level. You have to know it the way an implementor knows it—every edge case, every inconsistency in how different servers serialize JSON-LD, every signature scheme that exists in the wild. That's a lot to learn before you can even start thinking about your actual app. And when developers understandably cut corners on the protocol to focus on their product, it quietly becomes an interoperability problem for the whole ecosystem.
What I want ActivityPub development to feel like: you spend a day understanding the big picture, and then you just… build your app. That was the goal when I started Fedify, and honestly, we're not fully there yet. But it's where I want to get.
FEP-f228: Backfilling conversations has been updated:
https://codeberg.org/fediverse/fep/pulls/853
I added tootik and Lemmy to the implementation list and did a little cleanup. This FEP feels complete, so I am requesting final comments.
Full text:
A sneak peak of another #activitypub project I'm working on - @pppond - a different way of social bookmarking. Coming soon!
Join the conversation here, there is a lot to discuss and figure out: https://matrix.to/#/#pppapp:matrix.org
#fediverse #fedidev #ruby #pppdev
Edited 159d ago
RE: https://mastodon.social/@fediversereport/116178002926045553
Laurens Hof is at it again highlighting the problems of our lack of an adequate ActivityPub API and the hurdles that are to come in it getting adoption.
#fedidev
FEP website now displays the number of implementations for each implementable proposal:
https://fediverse.codeberg.page/fep/final/
These numbers are based on the information that authors provide in the "Implementations" section of a proposal.
By default, proposals are informational, so authors need to opt in by adding type: implementation to the metadata block.
Właśnie zaimplementowałam w #Nicolium funkcjonalność usuwania Śledzika z wykorzystaniem kodu „5P13RD4L4J-5L3D21U” 🚀
https://codeberg.org/mkljczk/nicolium/commit/a8fc1717c443d091d5f90ea45b1e9af44dc45b0c
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.
Some of you have already heard of us as #Fedify Studio. We now have a proper name: DrFed, short for “Doctor Fed.” We've also just received funding from @nlnet, through the NGI0 Commons Fund.
#DrFed is a web app for debugging #ActivityPub interoperability failures. When two implementations don't federate, the slow part is usually figuring out where the exchange broke: signing, JSON-LD processing, WebFinger, or something less obvious. DrFed's first job is to show where it failed.
We're the team behind @fedify: @2chanhaeng, @gaebalgom, @hongminhee, and @z9mb1. We'll post updates when there's something to try.
@DrFed is our sister project, built alongside #Fedify to tackle the debugging side of #ActivityPub development. It just received @nlnet funding and now has its own account here: @drfed.
#DrFed #fedidev #fediverse #NLnet
RE: https://hackers.pub/@drfed/019ed3c9-7e8c-782f-a512-5fbc75a4610b
RE: https://techhub.social/@fedicon/117055044486671264
FediCon is happening today! Normally I'd be covering it, but work doodies call.
RE: https://blog.fabiomanganiello.com/article/Federated-replies-and-reactions-in-Madblog
Madblog by @fabio is really coming along!
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
I've been saying for a while that we need something like FediCon in East Asia. A dedicated conference is still a stretch, but I've been thinking about a smaller step:
@COSCUP 2026 (Taipei, Aug 8–9) is accepting proposals for community tracks. It might be worth trying to open a Social Web track there—something in the spirit of the Social Web devroom at FOSDEM.
Nothing is decided yet, but if you're working on #ActivityPub, the #fediverse, or anything in the social web space and might be interested in speaking (or co-organizing), I'd love to hear from you.
I have exciting news to share!! 
It looks like we're finally gearing up to start migrating people over into @Mastodon's new @zulip instance for certain parts of our community next week (#MastoAdmin #FediAdmin #FediDev #Mod etc.)! It has been a long time in the making and I'm sorry for the delay, but I'm so glad we're finally going to start getting people in there <3 We'll start by beta testing with a few individuals next week to make sure everything is ready for a larger wave of people to join <3 <3
More on #DefaultServerRecommendations soon too — stay tuned!
Edited 93d ago
The #CFP for the Fediverse & Social Web track at COSCUP 2026 (Taipei, Aug 8–9) is now open! If you're working on #ActivityPub, the #fediverse, or anything in the open social web space, we'd love to hear from you. The deadline is May 9. #COSCUP is free to attend.
👉 https://hackers.pub/@fedidevkr/2026/fediverse-social-web-track-at-coscup-2026-cfp
(Boosts appreciated!)
RE: https://mastodon.social/@bagder/116359048796181736
Could be potentially nice for fediverse server testing, as more implementations make the jump to final RFC 9421 HTTP signatures.
On the flip side, ever more complex curl invocations (here: Accept header plus signature fields plus key file, presumably) suggest use of more specialized CLI tools, such as provided by @fedify, or at least scripts/aliases.
Speaking of RFC 9421, which notable fediverse implementations can't handle it yet? Anyone keeping track?
ActivityPub.Academy was where many of us checked whether our activities actually arrived anywhere. Thanks @crepels for running it so well for so long.
We're carrying that forward. @z9mb1, @2chanhaeng and I maintain Fedify, and with @gaebalgom the four of us are building @drfed, a web platform for developing and debugging #ActivityPub implementations, with NLnet NGI0 Commons Fund support.
Fediverse developers, we hope it earns a place in your toolkit: https://drfed.org/.
Edited 13d ago
An interesting development happens in funfedidev/schemas project. It's a JSON schema validator for Fediverse:
https://schemas.funfedi.dev/activity-pub-question/
In this example it loads the JSON schema from FEP-9967: Polls, which you can use to validate your Question object.
Starting on FEP-ef61 (Portable Objects) in @fedify. It's a @sovtechfund milestone due September 30, and the scope is… substantial. Not a lot of runway. Wish me luck.