RE: https://mastodon.social/@dansup/115596350786859898
Debating whether I should make Public playlists an OrderedCollection so they can be federated.
Since we allow playlist reordering, need to take that into consideration too.
If you have a fediverse account, you can quote this note from your own instance. Search https://mastodon.social/users/dansup/statuses/115596404697985830 on your instance and quote it. (Note that quoting is not supported in Mastodon.)
There are two kinds of "collections" in ActivityPub:
- Containers. These are basically objects that represent groups of other objects: threads, playlists and photo albums. ActivityPub clients can create, update and delete them.
- Views. These are generated on the fly by the server, can be paginated and filtered. Inbox and outbox are most common examples.
Both are supposed to be [Ordered]Collection objects with items property. However, in practice they are different. For example, it's reasonable to Update a playlist to change its name, but what an Update of a followers collection would mean?
Usually, I argue that containers and views shouldn't be mixed. Don't add items to your thread/playlist/album, create a separate collection instead.
Are there other options?
@mariusormarius How do you deal with this problem in GoActivityPub?
RE: https://mastodon.social/users/dansup/statuses/115596404697985830