🫧 socialcoding.. @smallcircles@social.coop
Public

@evanEvan Prodromou @julian @deadsuperheroSean Tilley

Except when they are called other names instead ;p

A timeline is a different thing than a collection imho. And an AS collection has some very particular functionality, which if I model a timeline in my app may not supported (e.g. reverse ordering).

Collection / 'timeline' is one of those words where sometimes they indicate an app domain, and sometimes a core protocol mechanism. Same is true with 'follow' which is sometimes a user action, sometimes indicates low-level publish/subscribe.

For core capabilities that must be part of the specs, in 'protocol space' it may be better to use terminology that is more common in messaging architectures and all the various architecture patterns that are involved. Perhaps idk we deal with a time-ordered event log or something like that.

Steve Bate @steve@social.technoetic.com
Public

@smallcircles🫧 socialcoding.. @evanEvan Prodromou An AS2 Collection cannot be a timeline (in general). It’s not even ordered. An AS2 OrderedCollection (a subtype of Collection) might be ordered by time or not, so it’s also not a timeline (in general). When they are ordered by some time value (unspecified in AP) they are often called “streams” in the spec. The Mastodon content timelines are not the same as AP activity streams although a filtered AP stream can be transformed to a content timeline.

0
0
0

If you have a fediverse account, you can quote this note from your own instance. Search https://social.technoetic.com/users/steve/statuses/116102983297261197 on your instance and quote it. (Note that quoting is not supported in Mastodon.)