Support Mastodon 2.6 bidirectional pagination API #351

Closed
opened 2018-10-30 23:16:51 +00:00 by shadowfacts · 3 comments
Member

See https://github.com/tootsuite/mastodon/releases/tag/v2.6.0

The new pagination param min_id is the symmetrical opposite of max_id, i.e. it can be used for stepwise pagination from older to newer statuses. The difference to since_id is that since_id will always return the latest statuses, just merely cut off by the provided ID. The new param is supported on all API methods that return statuses.

I'm not sure if this should be a broader issue for new Masto 2.6 API support in general, but this piece seems like it's pretty low-hanging fruit.

See https://github.com/tootsuite/mastodon/releases/tag/v2.6.0 > The new pagination param min_id is the symmetrical opposite of max_id, i.e. it can be used for stepwise pagination from older to newer statuses. The difference to since_id is that since_id will always return the latest statuses, just merely cut off by the provided ID. The new param is supported on all API methods that return statuses. I'm not sure if this should be a broader issue for new Masto 2.6 API support in general, but this piece seems like it's pretty low-hanging fruit.
Member

it seems unlikely that we will hit Mastodon 2.6.0 API level any time in the near future.

it seems unlikely that we will hit Mastodon 2.6.0 API level any time in the near future.
Owner

It’s likely going to be only after 1.0 unless we don’t have it soon™.

Also pleroma advertises the MastodonAPI level in /api/v1/instance (we could probably change the format to be saner/more-compatible like x.y.z+pleroma, like for glitch)

It’s likely going to be only after 1.0 unless we don’t have it soon™. Also pleroma advertises the MastodonAPI level in ``/api/v1/instance`` (we could probably change the format to be saner/more-compatible like ``x.y.z+pleroma``, like for glitch)

Shouldn't be too hard to implement though, maybe a good feature for someone new.

Shouldn't be too hard to implement though, maybe a good feature for someone new.
Sign in to join this conversation.
No milestone
No project
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pleroma/pleroma#351
No description provided.