Egregoros

there is nothing in the log about it either. just nginx when it hirts the top of somebody's timeline. I have been tearing my hair at this specficially for about an hour. I'm going to sleep and look at it again I think. couple shots of bourbon

@graf I think it might be related to max_id being set to an old post on some requests, which then results in old posts being fetched from DB for the timeline on the next request. How does the backend return an old ID is a mystery to me. It might also be something wrong with the pagination that causes it.

Anyways, suya..

@hj @graf That's a separate issue that I haven't seen in months. This one is on timelines and possibly related to searching for old posts, which makes no sense to me.

Edit: also it's not related to frontends, multiple frontends and mobile apps experience it.

@hj @graf Yes, that's a Pleroma-FE issue, but that's a frontend issue with hacks in the backend that need removal eventually. I don't think that is related unless it's somehow also in Nicolium, old Soapbox and Husky.