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
-
@thisismissem @scott you could do that if you wanted the notes to be grouped around that Flag activity
-
@trwnh @scott @[email protected] @julian @evan
I wanted to avoid inReplyTo since subsequent replies wouldn't share the same parent, i.e., Flag -> Note 1 -> Note 2
Note 2 would be inReplyTo Note 1, but both would be in the context of Flag
-
@[email protected] @scott @ThisIsMissEm @julian @evan makes sense to me
-
-
@trwnh @scott @[email protected] @julian @evan
I do also want to introduce correct addressing on Flags as currently they don't carry to/cc/bto/bcc, they're just sent to the reported accounts inbox, and Mastodon passes them all through to the moderators, without the reported account seeing those activities, despite them being implicitly addressed to the reported account (by means of delivery to their inbox)
-
@thisismissem semantically, yes, it can be a flag or anything else you want. Functionally, for real world implementations?
️I'm trying to think through what letterbook would do, and I suspect it would do the right thing. At least at the point of receiving the message. I would need some logic in reports to connect them back to that context, but i think that's likely to be straight forward
-
Jenniferplusplusreplied to Jenniferplusplus last edited by
@thisismissem what I really want is context to be
1. A stable identifier that I can index
2. An indicator of whether and how reply control is implemented
3. A collection of related content-like objects, if reply control is implementedIn that order.
I think using a Flag (or its ID) satisfies that
-
@infinite love ⴳ
nope, context can be anything; it doesn't have to be a collection. it's only a thread *if* it has whatever properties you consider necessary for a thread (e.g. an owner, items, and some signal that you can participate)
The problem is that there is an assumption that things with those traits are a thread, which is not necessarily the case.
If you have a thread and a collection that can both be participated in, then how will you figure out which is the thread and which is the collection? As I stated before, there should be a way to specify which context is a thread instead of just assuming based on some random traits it might have. -
Emelia 👸🏻replied to Jenniferplusplus last edited by [email protected]
@jenniferplusplus yeah, I don't think we'd have a collection for notes on a flag though, because the notes would be directly addressed to group actors for the moderation teams
Only use case I could think of is maybe inviting another moderation group actor to the thread of notes on a Flag, but that feels a bit weird with permissions.
-
@thisismissem Which is fine. If it's a collection, that makes it useful as a place to retrieve notes/etc that I didn't directly receive. But in this case it's overwhelmingly likely that there would only be 2 servers involved in the discussion anyway. So that's fine.
-
@jenniferplusplus also, in Mastodon I'm probably separating the Flag activities from the report as one Flag activity can now generate multiple Flag activities with varying content (user forward vs mod forwarded with content overwritten)
-
@jenniferplusplus even if it's 3-way plus, it'd have to all be directly addressing to avoid note leakage to as:Public
-
@[email protected] @[email protected]
For what it's worth, @[email protected] 's FEP 7888 doesn't explicitly define what
contextmeans semantically with regard to other objects, so to use it for flag reports makes complete sense to me. I don't know where @[email protected] is getting the idea thatcontextis only for threads, but given that it was discussed under the umbrella of the "threaded" discussion WG, I can see why one might make that assumption.Were I to implement this in NodeBB, each individual
Flagactivity would be translated to a NodeBB "report", and they'd contain a context, which is the flag itself.With regard to your concern re: addressing, if you queried the context, you'd get an
OrderedCollectioncontaining 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. -
Emelia 👸🏻replied to julian last edited by [email protected]
@julian @jenniferplusplus @trwnh @scott @evan well, we'd be sending Create/Update Note about a Flag, so thinking context would be that Flag on the Notes
Not necessarily with a collection of notes about the Flag
-
@[email protected] that's fair, I don't know how we handle federating flag reports right now (as @oplik0/@[email protected]) handled that aspect.
Having the context contain the individual notes regarding a flag would also work.
-
@julian @oplik0 @opliko I'll have to take a look for: https://github.com/swicg/activitypub-trust-and-safety/issues/14
-
@scott i still don’t think “thread” is anything special or different than “group of posts bound together by a topic and audience and owner that you can submit your post to for consideration of being added”. if anyone can come up with a proper semantic definition of “thread” then i’ll consider revising my definition, but asking “which one is the thread” is a bit like asking “which one of these recipients is the audience”, or like saying you only work with Note and not Article.
-
@scott like, you could define a type Conversation that the creator of the “thread” specifies when creating the “thread”. but this type doesn’t change any of the processing considerations for anyone wanting to participate. it just hints the author’s intention.
the one thing it *might* also do is signal that a certain protocol is in place, for example, something is a “fep-xxxx Conversation” might come with additional restrictions or requirements… but you still need the other props to be present.
-
infinite love ⴳreplied to Jenniferplusplus last edited by
@jenniferplusplus @thisismissem i think you’re in luck because it’s at least guaranteed to be 1. that’s the “intended usage” per the spec and per how it got implemented.
2 requires you to be able to dereference that stable id from 1, but it doesn’t require any specific type or repr. it just needs an owner and some properties signaling who can participate and how.
3 requires the dereferenced object in 2 to specifically be a collection.
Flag as context works for grouping but not backfilling.
