Discussion
Loading...

Post

Log in
  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
julian
julian
@julian@activitypub.space  ·  activity timestamp 4 weeks ago

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][//w3id.org/fep/7888] 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

  • Copy link
  • Flag this post
  • Block
silverpill
silverpill
@silverpill@mitra.social replied  ·  activity timestamp 4 weeks ago

Hm, it appears that none of my objections have been addressed.

Once again, why there are two activities Move and Remove, and not a simple Update or a new activity type?

View
  • Copy link
  • Flag this comment
  • Block
julian
julian
@julian@activitypub.space replied  ·  activity timestamp 4 weeks ago
⁂ Article

Re: FEP-f15d: Context Relocation and Removal

Hi @silverpill@mitra.social right;

  1. Move and Remove are explicit actions concerning membership of a context in an audience.
  2. Update is 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?)
  3. It is likely that sending audience as 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 audience may not be used at all in some.

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.

  • Copy link
  • Flag this comment
  • Block
silverpill
silverpill
@silverpill@mitra.social replied  ·  activity timestamp 4 weeks ago

What is so difficult about comparing a cached object with a new object when handling Update?
Move and Remove are just as broad, and these are activities for manipulating collection items. I guess they work well for you because you don't use them for anything else.

  • Copy link
  • Flag this comment
  • Block
julian
julian
@julian@activitypub.space replied  ·  activity timestamp 4 weeks ago

Re: FEP-f15d: Context Relocation and Removal

@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

  • Copy link
  • Flag this comment
  • Block
julian
julian
@julian@activitypub.space replied  ·  activity timestamp 4 weeks ago

Re: FEP-f15d: Context Relocation and Removal

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, and Piefed as of v1.5

As the implementors work through any issues, the FEP and this topic will be updated to reflect those changes.

  • Copy link
  • Flag this comment
  • Block
julian
julian
@julian@activitypub.space replied  ·  activity timestamp 4 weeks ago

Re: FEP-f15d: Context Relocation and Removal

Tagging relevant parties:

  • @rimu@piefed.social of Piefed
  • @nutomic@lemmy.ml of Lemmy
  • @bentigorlich@gehirneimer.de and @melroy@kbin.melroy.org of Mbin
  • Copy link
  • Flag this comment
  • Block

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances
Bonfire social · 1.0.2-alpha.7 no JS en
Automatic federation enabled
Log in
  • Explore
  • About
  • Members
  • Code of Conduct