FEP-baf5: Administrator Collection
-
This is the discussion thread for the draft FEP-baf5: Administrator Collection
> This FEP introduces a mechanism for discovering the administrators of an ActivityPub instance. It extends the "Group Moderator" pattern from [FEP 1b12][1b12] and the "Application Actor" concept from [FEP 2677][2677] by defining an
OrderedCollectionof administrators referenced from the instance's application actor. -
R AodeRelay shared this topic onR ActivityRelay shared this topic on
-
> @silverpill@mitra.social said:
>
> 5. FEP links lead to w3id.org site, not directly to FEPs.Wasn't aware this was a problem? Figured the redirects would be okay.
-
The reason why
attributedTowas chosen is because there is prior art to using that property to represent a collection of moderators. You could make the same argument against 1b12 (thatmoderatorsshould be the key instead ofattributedTo), too.The argument as to whether a custom property fits better is certainly valid, and worth debating. However, I would want to point out that keeping with prior art has the benefit of making this FEP much easier to adopt by threadiverse implementors.
-
> @silverpill@mitra.social said:
>
> Extends" is fine, I just think you're describing a reciprocal claim from FEP-fe34, so you could use that term (or maybe FEP-fe34 needs to be updated if "reciprocal claim" is not a good name for this mechanism?)I don't know if this is truly a reciprocal claim. My understanding from a reading of the relevant section from fe34 suggests a claim of A → B is reciprocal if there is an inverse claim B → A.
fe34solidifies the concept of same-origin trust (which iirc is only something like a line or two in AP spec?). baf5 builds upon that with an additional opt-in specificity. Sobaf5assumesfe34compatibility, but not the inverse. But we're splitting hairs I think <img class="not-responsive emoji" src="https://activitypub.space/assets/plugins/nodebb-plugin-emoji/emoji/android/1f604.png?v=f187f9278b7" title="
" /> -
> @silverpill@mitra.social said:
>
> 4. The entire problem of non-same-actor updates and deletes can be avoided by using different activities. For example, Update can be replaced with an annotation activity. Delete can be replaced with Remove (from thread).While true, this is outside the scope of the FEP.
Update/Deletewere mentioned in the FEP as they are recognizable, but this sort of explicit authorization* is relevant to any activity type.Offer,Undo,Bite,Zooboomafoo, etc.* I have to be careful when I use the term "authorization" because if I say it three times @thisismissem will show up and start talking about OAuth2/OIDC again.
-
> @julian said:
>
> * I have to be careful when I use the term "authorization" because if I say it three times @thisismissem will show up and start talking about OAuth2/OIDC again.Correction: it's just a single mention that makes me appear, people tend to confuse me with a genie but we're quite different.
(Also I saw other replies here but had an MCAS attack hangover today so didn't have energy to reply. I'll try to reply soon)
-
@silverpill@mitra.social @julian@activitypub.space @technical-discussion@activitypub.space
I agree with Silverpill 'attributedTo' should not be overloaded by this extra meaning
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