(#loerdxq) This seems to be a bit off: ``` DEBU[0007] cache: parsing https://feeds.twtxt.net/tiktok/twtxt.txt for tiktok https://feeds.twtxt.net/tiktok/twtxt.txt DEBU[0007] twts: [I am @ an automated feed that twts every 30m with the current time (UTC) 🕢 The time is now seven thirty 🌞] DEBU[0007] new: [] DEBU[0007] old: [🕢 The time is now seven thirty 🌞 I am @ an automated feed that twts every 30m with the current time (UTC)] ```

@xuu (#loerdxq) Commenting out `pos--` in `SplitTwts()` seems to fix this, I've been debugging this for an hour or so now, but maybe you can confirm. I _smell_ an off-by-one error here? 🤔 I'm just not 100% sure 🤣

(#loerdxq) Yes I _think_ the `pos--` produces an "off-by-one" error here. Here's why I think this. Say you have Twts: `A, B, C, D` ordered from oldest to newest (_from left to right_). Let's say C and D exceed `MaxTTLCache`. Therefore `pos` lands on C and we break out of the loop. But if we decrement `pos` again here with `pos--`, then we pos points to B. So we return new twts as A and old twts as B, C and D. Hence an off-by-one error since the older twtst were in fact C and D. Make sense?

(#loerdxq) Proposed fix: