The max_id, since_id, and min_id parameters in #Mastodon's Timeline API assume that the post ID is a sortable number. (Is this correct?) #Hollo, the #ActivityPub implementation I'm building, uses UUIDs for post IDs internally, so I'm stuck on how to implement a Mastodon-compatible API.
@hongminhee Does it assume that? I don't see it clearly stated in the documentation that the IDs themselves need to be numerically sortable, just that, when given a specific ID, the server needs to be able to retrieve newer or older posts based on it.
Of course sortable snowflake IDs make implementing this easier on the server side.
@hongminhee@julian correct, those parameters just say "newer / older than this ID", so you totally could fetch the object from the database and using like created at timestamps, but time-ordered unique IDs simplifies that for feeds & pagination by ID/cursor
@hongminhee@julian keep in mind, you can totally not implement those parameters though, as it's all based on the next/prev Link headers, not URL construction necessarily
The only case is if clients for some reason try to make requests explicitly by constructing URLs instead of relying on headers
@hongminhee yeah, Mastodon uses time-ordered ID values, by using Twitter's Snowflake algorithm.
You could always have your backend lookup the post with the given ID & grab the created_at timestamp or whatever that is used for pagination of statuses
Add comment