naturzukunftHave I already mentioned that the “Show thread” request is slowly driving me crazy?
@julian regarding #FEP7888 the as:context property is non-functional, so an array of contexts is allowed. do you accept that or do you throw an http 500 ;-) and do you know if others can hanlde an context array ? #activitypub #activitypubdev
wakest ⁂@julian @treefit I personally don't have any "horses in this race" other then getting things to work better. I would imagine #fep7888* would need serious "buy in" from Mastodon for it to really take hold as the way forward so if the way @jonny implementing this for Mastodon has potentially more of a likelihood of getting merged this year then I welcome it...
* https://socialhub.activitypub.rocks/t/fep-7888-demystifying-the-context-property/3021/19
FEP-7888: Demystifying the context property
Hello! Please use this thread to discuss FEP-7888 and any potential problems or improvements that can be addressed. Summary ActivityStreams Vocabulary defines the context property, but it is “intentionally vague”. Unfortunately, this makes the definition so vague as to be practically useless. This FEP aims to provide more guidance on possible uses of the context property, as well as formalizing some best practices. Full text: FEP-7888: Demystifying the context property
julianAs of today, the NodeBB-ActivityPub implementation now supplies both context and audience properties with every post.
N.B. When I say context and audience, these are also terms used by the ForumWG that refer to "topic" and "category", in NodeBB parlance.
Early indications from the last ForumWG meeting indicate movement towards the inclusion of context in a low-level as:Note object (a federated NodeBB post), resolvable as an as:Collection or as:OrderedCollection. The latter is what NodeBB will send, ordered by post time.
Discussions with @[email protected] also suggest that Discourse has the ability to parse an as:OrderedCollection context if provided, but currently does not if encountered as a property in a Note.
A minor change today also updates the audience property, which used to erroneously point to the context/topic, but now points to the audience/category. This change aligns usage of this property with FEP-1b12's expectations.
This change should allow other implementors to:
- automatically group objects together given a the provided context, and
- more thoroughly backfill a given object's context, without relying on
inReplyTotraversal
