mirrors/fep
1
0
Fork 0
mirror of https://codeberg.org/fediverse/fep.git synced 2026-08-05 19:55:46 +00:00
Code Packages Wiki Activity

Merge pull request 'FEP-1b12: Some changes to section "threads and comments"' (#42) from nutomic/fep:fep-1b12-update4 into main

Browse Source 
Reviewed-on: https://codeberg.org/fediverse/fep/pulls/42
This commit is contained in:
David Sterry
2022-11-30 17:04:17 +00:00
parent 3d0aba190d 139273c902
commit 6ea63d361d
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
feps/fep-1b12.md
+4 -2
View File
@@ -60,7 +60,7 @@ Actors can send such an activity to the group inbox for publishing.
## Threads and comments
Each `Group` actor represents a single forum. Each forum usually contains many user-submitted threads, which can be represented as `Page` objects. Forums can have comments which are usually represented as `Note`, and contain a field `inReplyTo` linking the thread it belongs to. Object representations may differ based on the requirements of each application.
Each `Group` actor represents a single forum. Each forum usually contains many user-submitted threads, which can be represented as `Page` objects. Forums can have comments which are usually represented as `Note`, and contain a field `inReplyTo` linking the thread it belongs to. Object representations and types may differ based on the requirements of each application.
A thread:
```
@@ -85,7 +85,9 @@ A comment in that thread:
}
```
There are reference links provided for navigating up from a comment to the respective thread and group. Comments MUST provide a field `inReplyTo` linking to the thread they belong to. As mentioned before, both threads and comments MUST include a field `audience`, which allows resolving the group they belong to.
There are reference links provided for navigating up from a comment to the respective thread and group. Comments MUST provide a field `inReplyTo` linking to the thread they belong to, or to the parent comment in case of a nested reply. As mentioned before, both threads and comments MUST include a field `audience`, which allows resolving the group they belong to.
Implementations MAY use the `context` field to reference the corresponding thread, as well as other comments or activities in the thread.
To navigate down from a group to threads and comments, implementations MAY expose them as collections. Groups MAY have a `replies` collection which contains all threads. Each thread MAY again have a `replies` collection which lists all comments responding to the thread.