FEP-f15d: Context Relocation and Removal
-
Threaded applications often have the need to move and remove content between groups/communities for curation purposes (i.e. resolving miscategorization, spam, etc.)
This is an extension of the Resolvable Contexts tree of FEPs.
The FEP draft has been submitted for review. In the meantime, it can be viewed here: https://github.com/julianlam/feps/blob/fep-f15d/fep/f15d/fep-f15d.md
-
The submission of the FEP and timing of this post are intentional as there are now two implementors supporting (part of) this FEP.
- NodeBB as of v4.7.0
- Piefed as of v1.5
As the implementors work through any issues, the FEP and this topic will be updated to reflect those changes.
-
Tagging relevant parties:
- @rimu@piefed.social of Piefed
- @nutomic@lemmy.ml of Lemmy
- @bentigorlich@gehirneimer.de and @melroy@kbin.melroy.org of Mbin
-
@bentigorlich@gehirneimer.de in the relevant issue in Mbin's issue tracker raises a wording concern: "resolvable context" is an unfamiliar term to those who have not read through FEP 7888.
I will update the FEP to make this definition more explicit.
https://github.com/MbinOrg/mbin/issues/248#issuecomment-3741019183
-
Hm, it appears that none of my objections have been addressed.
Once again, why there are two activities
MoveandRemove, and not a simpleUpdateor a new activity type? -
Hm, it appears that none of my objections have been addressed.
Once again, why there are two activities
MoveandRemove, and not a simpleUpdateor a new activity type?Hi @silverpill@mitra.social right;
MoveandRemoveare explicit actions concerning membership of a context in an audience.Updateis overly broad and receivers would have to infer audience change based on what the updated object contains (e.g. Audience Y is suddenly missing, and Z is new, was this always the case?)- It is likely that sending
audienceas an array will not be correctly interpreted by existing software, so this property is an unreliable indicator of context audience membership at best- Existing threadiverse apps check addresses, and
audiencemay not be used at all in some.
- Existing threadiverse apps check addresses, and
There is no conflict with
Move(Person), and I have not heard a convincing reason to adopt a new activity type when these two AS activities work quite well to describe what we want to accomplish. -
Hi @silverpill@mitra.social right;
MoveandRemoveare explicit actions concerning membership of a context in an audience.Updateis overly broad and receivers would have to infer audience change based on what the updated object contains (e.g. Audience Y is suddenly missing, and Z is new, was this always the case?)- It is likely that sending
audienceas an array will not be correctly interpreted by existing software, so this property is an unreliable indicator of context audience membership at best- Existing threadiverse apps check addresses, and
audiencemay not be used at all in some.
- Existing threadiverse apps check addresses, and
There is no conflict with
Move(Person), and I have not heard a convincing reason to adopt a new activity type when these two AS activities work quite well to describe what we want to accomplish.What is so difficult about comparing a cached object with a new object when handling
Update?MoveandRemoveare just as broad, and these are activities for manipulating collectionitems. I guess they work well for you because you don't use them for anything else.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login