Hi, #snac author here. Thanks for reporting on the 'bot' account bug, I have to take a look at it.
Regarding the other issue, snac do support Mastodon API pagination. Many apps do this correctly, like Tusky, Fedilab or semaphore.social, so you can travel the full timeline. Other ones only request the first page, I don't know why.
@nowster@justine That's odd. Would you mind creating a test account on your server for me and sending the credentials to team@pachli.app. Then I can diagnose this further.
I've filed one of them at https://codeberg.org/grunfink/snac2/issues/241 (this also found a Pachli bug where errors during login weren't showing the underlying login error; I've fixed that now, thanks).
@justine@snac.smithies.me.uk I notice that the current version of #pachli doesn't stop requesting the timeline when it refreshes. What I'll miss when I eventually migrate will be following hashtags.
Hi, #snac author here again. I've installed Pachli and I'm experimenting the same issue than @nowster@fedi.nowster.me.uk: it keeps requesting the first page over and over again, with no max_id nor since_id fields to paginate.
Many apps work ok without the Link header kludge, they just keep track of the last seen post Id, and when they need more posts to be shown, they just use a since_id argument for the next page.
As you say, the Mastodon documentation is a bit ambiguous.
Anyway, I'll work on implementing it. Thanks for the conversation.
@grunfink@nowster@justine The Mastodon docs are a bit ambiguous about this. Arguably, if the link header is missing a client could assume it could behave as though it did exist, with the IDs of the first and last items in the returned page.
That might be what snac is doing. For interoperability purposes it's probably better to always return the link header.