forge/Vervis
1
0
Fork 0
Code Pull requests Activity

FEDERATION.md: Use participants for non-actor followers collection

Browse source
This commit is contained in:
fr33domlover 2019-05-30 10:40:09 +00:00
parent 48529627b6
commit 81d41bfb8a
1 changed files with 4 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
FEDERATION.md
View file

@ -565,6 +565,10 @@ Requirements, suggestions and details:
are, and it allows people to opt out of notifications if they previously are, and it allows people to opt out of notifications if they previously
commented on some topic but don't want to be in the discussion anymore. This commented on some topic but don't want to be in the discussion anymore. This
makes it very easy for clients to correctly address comments. makes it very easy for clients to correctly address comments.
- The wording in the ActivityPub spec implies that `followers` is a property of
actors, and I'm unsure whether it's safe and compatible to use it with
non-actors. So until this point is discussed, the temporary proposed name for
the followers collection is `participants`.
`GET /luke/outbox/A0O8l` `GET /luke/outbox/A0O8l`
@ -598,8 +602,6 @@ Requirements, suggestions and details:
TODO: TODO:
- `followers` is for actors, it seems, by the AP spec? So, what do we call the
collection of followers of a ticket?
- `replies` and how the C2S object nesting depth proposal - `replies` and how the C2S object nesting depth proposal
- Use `nonActors` in the example? - Use `nonActors` in the example?
- Content format? HTML? Markdown source? Tags? Referenced ticktes? - Content format? HTML? Markdown source? Tags? Referenced ticktes?