Moving topics/contexts between communities
Technical Discussion
5
Posts
2
Posters
0
Views
-
Moving contexts (aka topics/threads) between audiences (aka categories/communities) should be something that can be communicated outward.
NodeBB is experimenting with using the
Moveactivity to communicate this to other instances.When a context is moved from one audience to another, the object and all of its descendants go with it. This is communicated with a
Moveactivity with the resolvable context asobject, and withoriginandtargetreferring to the outgoing and incoming audience, respectively.An example
Move:{ @context: <... snipped>, id: "https://activitypub.space/topic/123#activity/move/1761362910015", type: "Move", actor: "https://activitypub.space/uid/1", to: ["https://www.w3.org/ns/activitystreams#Public"], cc: [ "https://activitypub.space/category/1/followers", "https://activitypub.space/category/2/followers", ], object: "https://activitypub.space/topic/1", origin: "https://activitypub.space/category/1", target: "https://activitypub.space/category/2", }The object
https://activitypub.space/topic/1doesn't necessarily mean anything to most implementors, so unless the object domain is yours, you are expected to resolve it to find the root object (and associated context if necessary.)Would adding a new property like
contextRootpointing to the root-level object be useful for implementors?If
targetisnull, theoretically this could signify the removal of a context from its audience.nullvalues are apparently a no-no in AP soRemoveactivity is recommended instead.rimu@piefed.social and nutomic@lemmy.ml melroy@kbin.melroy.org I wanted to ping you all as I am interested in your feedback as I move toward drafting this FEP.
-
undefined NodeBB shared this topic on
-
@julian If context is a collection,
Moveis problematic for the same reason asDelete. I think users shouldn't move server-managed views.It would be better to introduce a companion object (or an actor) for context collection. I guess I need to say something that in FEP-f228.
-
@julian If context is a collection,
Moveis problematic for the same reason asDelete. I think users shouldn't move server-managed views.It would be better to introduce a companion object (or an actor) for context collection. I guess I need to say something that in FEP-f228.
Would
updatework better?Moveis pretty self explanatory, and I don't have any issue with a collection being moved from a collection to another collection (despite how odd that sounds.) -
No,
Moveis a good choice, but I do have a problem with itsobjectbeing a collection. I am not sure if I can implement this in my ActivityPub client application.Are you opposed to adding a companion object?
-
No,
Moveis a good choice, but I do have a problem with itsobjectbeing a collection. I am not sure if I can implement this in my ActivityPub client application.Are you opposed to adding a companion object?
Not particularly, but I am worried about adding additional complexity since it affects developer buy-in.
I'll bring it up at the next ForumWG for debate.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
trwnh@mastodon.social oh, another one.
Glitch-soc apparently lets you hide follower counts, and federates a -1. That works but null would be a more explicit statement that the follower collection is hidden/not accessible.
-
Not particularly, but I am worried about adding additional complexity since it affects developer buy-in.
I'll bring it up at the next ForumWG for debate.
-
No, Move is a good choice, but I do have a problem with its object being a collection. I am not sure if I can implement this in my ActivityPub client application.
Are you opposed to adding a companion object?
-
Would update work better?
Move is pretty self explanatory, and I don't have any issue with a collection being moved from a collection to another collection (despite how odd that sounds.)
-
@julian If context is a collection, Move is problematic for the same reason as Delete. I think users shouldn't move server-managed views.
It would be better to introduce a companion object (or an actor) for context collection. I guess I need to say something that in FEP-f228.
-
@julian so this is still in effect a Remove or Update, not a Move. if you wanted it to be a Move, you would instead have an "uncategorized" category whose id is /categories/-1 or something like that.
-
trwnh@mastodon.social receiving a Move(Context) where target is null would tell NodeBB to move the topic to -1, uncategorized.
For those not supporting the catch-all bucket, deleting the context is ok too.
-
@julian but more generally my question is, what practical application would you need to make use of an empty set []? like, a consumer encountering a value should do A, encountering a null or missing property should do B, encountering an empty set should do C... what is the difference between B and C?
