@movq@www.uninformativ.de Oh, right, this feed. Well, if you detect some garbage (unparsable twts) with the range request, you can always fall back to a complete request. It probably works most of the time, but there are certainly plenty of pitfalls you can come across. You might detect the order of the feed and then formulate your queries accordingly. Maybe if you construct the range so that the last seen twt will be refetched, you can detect whether the request was off and a full sync needs to follow. Some metadata changes might be missed with the range request if the amount of bytes didn’t chance, but fully querying the feed once a day/week/whatever might take care of that – if metadata are actually of any use to jenny. But it’s getting complicated really quickly. So maybe some kind of pagination/archive would be easier.