@hj @lain I’ve considered this too. I considered adding an action field that lets you set it to listen, watch, play (for games), etc, but that legitimately does get into the realm of conflation and wackiness.
Worse yet, the ActivityStream vocabulary has Watch and Listen actions, but no Play action or Game document type. So in order to do this in a “sane” fashion we might need to just make up our own.
In the case of games, I would also add an /extend/ type endpoint that ingests a flake id or something and just adds to the length, since you can play a game for five minutes or five hours, depending on the whim of the user. But that would need to be federated like an edited post for it to mean anything.
This tangent leads to a lot of compelling design questions. For now, I’m going to sleep on it until my outstanding PRs resolve (get closed, get merged) and maybe experiment on my fork. If you want to check out what I’ve done unilaterally so far, get on breastmilk.club