Home | Notifications | New Note | Local | Federated | Search | Logout

Note Detail

Reply to @silverpill@mitra.social
Mike Macgirvin@mike@macgirvin.com (2026-06-11 07:01:55)
Conversation owner can add any activity to the conversation. However, if a context property is present on the activity, its value SHOULD be identical to the ID of a conversation container.

Let's just remove this line from FEP-171b. Then I think I can make most everything else work. 

Tying the conversation target to the context in any way, shape, or form appears to be un-workable. That includes tying it to contextHistory instead. Thy are separate concepts, although implementations MAY choose to use the same identifiers for both.

About the 403 - was it fetched by your site actor perchance? They aren't one of my followers. I'm not seeing any permission issues currently, though I'll keep investigating.
---Reply---
silverpill@silverpill@mitra.social (2026-06-11 19:06:01)
@mike

About the 403 - was it fetched by your site actor perchance? They aren't one of my followers. I'm not seeing any permission issues currently, though I'll keep investigating.

No, I am making a request on behalf of my personal actor. Made another attempt at 2026-06-11T10:03:56Z with the same result.

Let's just remove this line from FEP-171b. Then I think I can make most everything else work.

OK, I will remove it.

---Replies---

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.