@shadowfacts I wonder if it’s a Pleroma bug. It does seem to resolve itself eventually. In that case, ignore the post since it’s technically invalid, and continue parsing the timeline? If it fixes itself on a future fetch, then great, it’s valid? From the end user standpoint, in this case the problem is less that single item and more how the timeline gets stuck until some point in the future because of the error.