@Tusky thanks for the details!

I've just commented on the ticket and asked @dansup if see he sees it as something that needs to be fixed on Pixelfeds end.

If so, I'm gonna pick it up first thing, tomorrow morning.

@Tusky@mastodon.social @feditips@mstdn.social @Ralph@mstdn.ca

I also tried to get this done with #Mammuthus. Made some progress, but still i wouldn't really trust the current situation. Unfortunately the documentation on https://docs.joinmastodon.org/methods/notifications/#get is not very clear, not complete and includes at least one mistake.

So thanks for providing https://docs.joinmastodon.org/api/guidelines/#pagination - as this confirms at least some parts of my implementation now.

Doing some monitoring how a original #Mastodon server responds, i never (!) saw the described link header! The response may include no link header or a header like this: Link: ; rel="next", ; rel="prev"

On my research i saw something in the #Tusky source, that looks like Tusky as clients seems to generate a link header? If so, why?

"link: ; rel=\"next\", ; rel=\"prev\""

https://github.com/tuskyapp/Tusky/blob/develop/app/src/main/java/com/keylesspalace/tusky/components/notifications/NotificationsPagingSource.kt#L107-L178

Besides of details, if the header should be named "Link:" or "link:", i'm totally missing the information, when the server should provide which links... and also i'm still confused, why i never saw Mastodon (in this case norden.social) to respond with a Link header, that really includes URLs.

For now i provide a filled Link header, if the result is not empty and this empty Link header, if no (new) notifications are retrieved. If it is not able to get notifications at all, no Link header will be included.

Tusky 22 now sometimes reports an array index out of range (-1) or similar (taking this from my memory, for exact message, i have to check it again).

During development i also saw Tusky sending requests for notifications in an endless loop... wondered why.

And obviously the way, Tusky fetches notifications, changes more or less totally from Tusky 21 to 22.

And... could someone clarify the difference between since_id and min_id? If Mastodon will handle this differently?

since_id = String. Return results newer than this ID
min_id = String. Return results immediately newer than this ID

What should be the difference between "newer" and "immediately newer"?

Currently #Mammuthus is handling since_id and min_id in the same way.

But i just experienced "Problem 2", not "Problem 1", as described here:
https://github.com/tuskyapp/Tusky/issues/3580#issuecomment-1527198806

Would be nice to get my code working in a stable way for all Mastodon clients, including Tusky in version 21 and 22... and all coming versions... :-)

Have a nice sunny Sunday.

@SuitedUpDev@mastodon.online @dansup@mastodon.social