from julian@community.nodebb.org to swicg-threadiverse-wg@community.nodebb.org on 25 Oct 20:22
https://community.nodebb.org/post/101539
@julian said in Does context in AP have to be a collection, or can be be like a Flag activity? Say I wanted to Create(Note) about a Flag I'd received, I'd need:
If you queried the context, you'd get an OrderedCollection containing objects that you have access to view, but since in NodeBB only moderators can view flag reports, anybody querying it over ActivityPub would just get an empty collection.
The quote was in reference to whether disparate as:Flag activities could be grouped together under a common context (per 7888).
To be technically correct, it would contain the Flag activities... which reminds me of a discussion @trwnh@mastodon.social and @silverpill@mitra.social had about what a context collection could contain... objects vs. activities.
In this particular case, I suppose the context collection would contain activities, not objects, which would mean we'd need to relax any recommendation that they contain either objects or activities, since it could contain any mixture of both.
threaded - newest
@julian @trwnh @silverpill
I was thinking context would be the flag, you query it and get a Flag instead of OrderedCollection (we'd probably inline the object)
@thisismissem@hachyderm.io @trwnh@mastodon.social @silverpill@mitra.social Ah seems I misunderstood the assignment then heh
In that case the context collection would contain the note objects as you specified in the other topic.
Right now NodeBB's context resolver expects a Collection-ish type, so finding a Flag would cause it to back out — for now at least.
@julian @thisismissem @silverpill reporting happens in a different context than making posts, where backfilling isn’t really important. if backfilling was important then you could always create a collection. but otherwise, this is kind of like putting the context of your Note as another Note, instead of a conversation. valid, but maybe not what you want.
the other thing here is that the “other half” of context is audience.
@julian @thisismissem @silverpill which is to say: audience is what decides which objects you are even *aware* of, before you even get around to grouping them logically.
in a centralized system you would query for all objects in the database where the context was what you wanted, and where the audience included you.
in a decentralized system you work off of what’s in your inbox, and “follow your nose” to the context, which may have its own audience.