Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • pleroma pleroma
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 647
    • Issues 647
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 88
    • Merge requests 88
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PleromaPleroma
  • pleromapleroma
  • Issues
  • #351
Closed
Open
Issue created Oct 30, 2018 by shadowfacts@shadowfactsContributor

Support Mastodon 2.6 bidirectional pagination API

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.

Assignee
Assign to
Time tracking