[bug] offset parameter doesn't work #794

Closed
opened 2024-06-05 19:44:55 +00:00 by KaitlynEthylia · 2 comments

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?

  • I have double-checked and have not found this issue mentioned anywhere.
### 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? - [x] I have double-checked and have not found this issue mentioned anywhere.
KaitlynEthylia added the
bug
label 2024-06-05 19:44:55 +00:00

offset is not a valid parameter for this endpoint, due to it being a moving timeline - unsure where you found it documented as being valid

min and max id should be used

we are compatible with mastodon API, see https://docs.joinmastodon.org/methods/accounts/#statuses

`offset` is not a valid parameter for this endpoint, due to it being a moving timeline - unsure where you found it documented as being valid min and max id should be used we are compatible with mastodon API, see https://docs.joinmastodon.org/methods/accounts/#statuses
Member

for reference: offset is included in API specs via the generic pagination_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 up pagination_parameters into more specific sets

for reference: `offset` is included in API specs via the generic `pagination_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 up `pagination_parameters` into more specific sets
Sign in to join this conversation.
No milestone
No project
No assignees
3 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: AkkomaGang/akkoma#794
No description provided.