[bug] offset
parameter doesn't work
#794
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#794
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Your setup
OTP
Extra details
No response
Version
3.13.2
PostgreSQL version
16
What were you trying to do?
The
offset
parameter of /api/v1/accounts/<>/statuses has no effect. This happens on all akkoma instances I've tested, but I filled out the details above with respect to my own instance.What did you expect to happen?
the
offset
parameter should offset the resultant posts by X many posts.What actually happened?
It has no effect (The most recent posts are shown)
Logs
No response
Severity
I can manage
Have you searched for this issue?
offset
is not a valid parameter for this endpoint, due to it being a moving timeline - unsure where you found it documented as being validmin and max id should be used
we are compatible with mastodon API, see https://docs.joinmastodon.org/methods/accounts/#statuses
for reference:
offset
is included in API specs via the genericpagination_parameters
eventhough it (Intentionally) has no effect. Likely this means it showed up as supported in swagger-ui and to avoid confusion we should split uppagination_parameters
into more specific sets