Home | Notifications | New Note | Local | Federated | Search | Logout
Note Detail
Reply to @silverpill@mitra.social
Phantasm@phnt@fluffytail.org (2026-06-14 21:04:49)
@silverpill
>And one thing that caught my attention is the use of Accept and Reject activities for managing approvals.
This is an ActivityPub issue more than anything else. The "spec" is clear that the side-effects are to be determined by the type of the Object. There is no other indication, you effectively must check the type of the Object referenced. And I think that is correct, the same way Mastodon is correct in its usage of these two Activity types.
If you split the type for other Accept/Reject Activities, like AcceptFeatured or whatever, you are still left with more type determining logic anyway [at least in function non-pattern matching languages :)]. You just moved it somewhere else instead.
---Reply---
lain, author of the quixote@lain@lain.com (2026-06-14 21:07:32)
@phnt @silverpill looking forward to the first activity with an array of types targeting an object with an array of types
Reply
---Replies---
Phantasm@phnt@fluffytail.org (2026-06-14 21:10:16)
@lain @silverpill Somebody probably made that already. Objects with type arrays have been talked about recently-ish I think. Those are even more insane and should be made into a specific type instead.
https://codeberg.org/fediverse/fep/src/branch/main/fep/2277/fep-2277.md#multi-typing