@steveSteve Bate 
@jerger 
@mariusormarius
Yes, I was about to respond: Or in your own client, I suppose. The client then defines the app. A client video app would pick up and process a PeerTube as:Video activity, but care nothing about PeerTube. The type of the activity, and the properties the client needs to deem it valid for processing are then deciding, I guess. 🤔
@steveSteve Bate @jerger @mariusormarius
As an aside: I just learned about Holos-Discover, an AP search engine was taken offline by 
@HolosSocial after discussions relating to consent. The key finding was in https://toot.fedilab.app/@apps/116051469228002847
> This highlighted a real conversation the Fediverse needs about default settings.
Yeah. I would reformulate to say that this is about protocol capabilities vs. these weird things we call "apps".
Can't check the Holos-Discover info, as it was taken down, but it seems to me that relying on an "Indexable" setting is an app-specific thing. Hence it can't be part of a generic consent mechanism.
When it comes to "defaults", the fediverse as a whole has a problem in that Microblogging is seen as something foundational to #ActivityPub, a given upon which all else is built. Protocol capabilities. But this is, should not be, the case.
Microblogging constitutes a domain, a set of user stories with well-define particular behavior. Or as app domains (Mastodon) + FEP practices.
If you have a fediverse account, you can quote this note from your own instance. Search https://social.coop/users/smallcircles/statuses/116051902808996606 on your instance and quote it. (Note that quoting is not supported in Mastodon.)
