Home | Notifications | New Note | Local | Federated | Search | Logout
Note Detail
Reply to @silverpill@mitra.social
Mike Macgirvin@mike@macgirvin.com (2026-06-12 04:42:44)
Right. It's failing signature verification on the request-target, which contains a query element. So I actually did implement that bit of ap:// normalisation someplace; but it was in an obscure part of the codebase and been so long it isn't easy to find any more. But that isn't important any more. I'll be removing the "posts" presentation and any "context" elements completely from my code, and can never be in full compliance in FEP-f228. Our application provides and stores and moderates and federates with activities. Posts lack "context". And sorry for the multiply-recursive joke. If this makes us non-compliant with ActivityPub, it isn't my problem any more. Our presence was outlawed for the crime of basing our work on ActivityStreams and ActivityPub, instead of basing it on Mastodon, who I will note, didn't even provide a resolvable context last time I looked.
---Reply---
Mike Macgirvin@mike@macgirvin.com (2026-06-12 06:56:45)
FEP-f228 is no longer supported in forte. As I still require a context element which contains activities for legacy compatibility, forte is now non-compliant with ActivityPub and I'm afraid this situation is permanent.
Please feel free to remove forte and streams from all implementation lists and drop FEP-171b. Embrace, Extend, Extinguish is complete - you can all finally celebrate and let loose with a coordinated "good riddance". Sorry it took so long to see that there was never really any other option.
Reply
---Replies---
silverpill@silverpill@mitra.social (2026-06-13 03:44:01)
@mike I still have no idea what your problem is. In the worst case, other implementations will not be able to backfill your conversations, that's all. It's not the end of the world.