-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disambiguate usage of attributedTo
#467
Comments
This issue has been mentioned on SocialHub. There might be relevant details there: https://socialhub.activitypub.rocks/t/fep-c7d3-ownership/4292/36 |
This was also mentioned in this SocialHub thread to be able to keep the instance actor as the Actor of the Flag activity, but the Flag still has an opaque identifier from the origin server that identifies the reporter without surfacing the identify specifically. This use case specifically might be something best suited to the Moderation, Trust & Safety Taskforce |
for that use case i think |
I agree with trwnh that the proxy actor solution is the best approach for
Flag, I'm not a fan of making another property here.
…On Fri, Sep 6, 2024, 11:44 AM a ***@***.***> wrote:
the Flag still has an opaque identifier from the origin server that
identifies the reporter without surfacing the identify specifically.
for that use case i think attributedTo is inappropriate since actor is
already a subproperty of attributedTo. the solution that makes more sense
in this case is to use a proxy actor. there's no reason it has to be a
singular "instance actor". it could be an anonymized actor that maps to
that user who filed the report. activitypub does not mandate a "1 actor per
user" mapping, or any other mapping between actors and users. i think
piefed for example is using proxy actors to anonymize upvotes/downvotes via
Like/Dislike activities:
https://socialhub.activitypub.rocks/t/anonymous-likes-dislikes-or-other-activities-via-proxy-user/4472
—
Reply to this email directly, view it on GitHub
<#467 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABZCV5CAVV5AUQTBRIDJCTZVHZYRAVCNFSM6AAAAABNMZ32LKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZUGYZDMMRWGI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
AP 6.2 Create Activity has this:
throughout examples used in the activitypub spec,
attributedTo
is used fairly consistently to signal attribution in the sense of who Created an object, or perhaps somewhat in the sense of who authored an object.however, the definition of
attributedTo
in AS2-Vocab is circular: https://www.w3.org/TR/activitystreams-vocabulary/#dfn-attributedtoand oxford defines "attribute"/"attribution" as:
so there is room left open for the following use cases in theory but not in practice:
attributedTo
a non-actor object, e.g. an object'slikes
Collection may beattributedTo
to that object itself, or it may beattributedTo
no one (signalling a server-managed collection?), or it may beattributedTo
the object'sattributedTo
, and so on.attributedTo
the Create activity that created it, instead of or in addition to the Create activity's actorattributedTo
another activity that caused or resulted in the current activity. (FEP-0391 currently uses this as a mechanism, in combination withresult
)more generally, there are a lot of potential meanings for "attribution" that could be spun off into their own more appropriate properties. even in the sense of authorship, we could use something like dublin core's
creator
or schema.org'sauthor
to be more precise; we can also use these to declare multiple-authorship while not breaking existing assumptions of a single "owner" (where "ownership" is in the sense described in https://w3id.org/fep/c7d3 as a formalization of the current practices on the fediverse).The text was updated successfully, but these errors were encountered: