Home | Notifications | New Note | Local | Federated | Search | Logout
Note Detail
silverpill@silverpill@mitra.social (2026-06-14 20:52:07)
I've been reviewing the new FEP from the Mastodon team today, and one thing that caught my attention is the use of Accept and Reject activities for managing approvals. Another day, someone proposed to use Follow activity for "watching a thread".
So now, when you receive a standard activity, you need to use increasingly complicated heuristics to figure out what the activity does, because it is not possible to infer that from its type anymore.
This has to stop. I think we need to start giving our activities better names.
#ActivityPub
---Reply---
marius@mariusor@metalhead.club (2026-06-14 21:04:00)
@silverpill I think you're wrong. It feels perfectly natural that the same activity can be used with different objects. That's the whole purpose of the Activity vocabulary itself being split between activities and objects, isn't it?
And yes, that sometimes means that different side-effects need to be implemented for processing the same type of activity.
Reply
---Replies---
silverpill@silverpill@mitra.social (2026-06-14 22:07:12)
@mariusor Wrong about what, using different names for different things?
Only a few activities from Activity vocabulary work well with any type of object. For example Create and Update.