@tootapp hmm so this one is toot! being stricter than the spec? I can send a temporary image for now, I'll have to create one for the header. Did you see any other errors or is this our last one on the timeline parsing?
Edit: ah! Whoops, didn't see the neither. Fix incoming!
@tootapp Alright our output is now a lot closer to mastodon.social, and I've removed a bunch of optional fields to make things easier to debug. What's the parser dying on now?
@tktech Very oddly, apparently nothing at all? Will have to investigate that further...
@tktech Looks like you are missing the Link headers to track newer and older statuses?
@tktech You'll need it to make some of the timelines work at all, such as follower lists.
@tootapp Interesting, alrighty. My understanding was that a missing `Link` header implies that there's no next or previous page available. We'll add support for it but I'm not sure what to do in that case (what happens when a site only has a single status?) I will have to investigate.
It wasn't noticed initially because the clients tested against so far like Tusky are doing the pagination directly without using the Link header.
@tktech Yeah, doing it that way only works as long as the IDs in the actual data are sequential, which they are not in places like follower lists.
@tktech Also, there's always going to be a previous page available, because that is where newer entries would go when they appear. I think a missing next means the end of the timeline, but there should always be a previous. If both are missing that means an empty timeline, which is why Toot! will show an empty timeline in that case.
@tktech mastodon.social returns 'link: <https://mastodon.social/api/v1/timelines/public?max_id=109587048907649843>; rel="next", <https://mastodon.social/api/v1/timelines/public?min_id=109587049292283879>; rel="prev"', when I tried it now.
