Ah, so you don't differentiate between paged and unpaged in your data model? Do you just return a paged collection for all collections past a certain size?
So the first link is to the collection, which of course links to the latest page at the time of generation
The second link's query parameter points at the first item from this page you'd like (assuming it is indeed in the collection) then gives the N (eg 20) items in the page. Then link to then next one!
@cwebber I really like the id of the page query param pointing to a specific item id and just returning the next N items. Elegant way of expressing dynamic paging.
@jdormit @cwebber That's how I do paging at rhiaro.co.uk too. Internally everything is stored as AS2 collections and then 16-item pages are dynamically generated, eg. https://rhiaro.co.uk/tags/activitypub?before=https://rhiaro.co.uk/2016/05/minimal and secret feature, you can add &limit=x to the URL to change the page size. It works with conneg to application/activity+json too if you curl it
@jdormit I think that you shouldn't really allow activity submissions on a paged collection. In my opinion the client/server adding the activity should dereference the parent collection IRI (from the partOf property) and submit it there.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!