SocialCG/ActivityPub/OAuth 2.0 Scopes
Appearance
< SocialCG
These scopes have been added to the Basic Profile for Social API Servers in the OAuth scopes section. Changes to the scopes should be made as issues in https://github.com/swicg/actvitypub-api/issues.
This was a workpad for developing a list of scopes for ActivityPub social API servers.
Design goals
- Action-oriented. They are about what the app can do.
- User-level. They are for actions that a user would be aware of: liking things, following people, reading my followers list.
- Fine-grained. People on the Fediverse like fine-grained control and tuning.
- Bundled. Some bundled scopes to make it easier for clients.
- Unambiguous. It's clear from each scope what is being requested.
- Easy for clients to determine. Client developers can figure out what scopes they need to request easily, based on what they request and what they send.
- Easy for servers to check. Server software can easily check these scopes at runtime.
- Complete. It should cover everything you can do with the ActivityPub social API.
Scopes
"You are authorizing the app to..."
Notes
- "read" = HTTP GET
- "see" = HTTP GET
- "all your data" = actor + actor's collections + objects that the actor created + files
- "your server" = same origin as actor ID
- "on its own server" = same origin as CIMD identity, using proxy
- "any server" = own server or any other, using proxy
- "post" = create an activity with these address types
- "post to anyone" = any addressing
- "Interact with" = like, share, reply to, add/remove from collection, ...?
- "content" = at least Web content like text, images, audio, video, plus polls. Maybe other types, like events, places, etc.? Extended types as well?
- "account" = user-level word for "actor" that isn't limited to people and doesn't enumerate Person, Group, Organization, Application, Service