Thanks for reporting this, @hans_derycke. This was a bug where unpublishing and republishing a blog post caused the read state to get out of sync between two internal Redis sets. When you marked the story as read, an optimization incorrectly thought it was already handled and skipped the update, so it kept coming back.
I’ve fixed your account and deployed a code fix so this won’t happen again.