Из ленты dev.to devops — кратко, чтобы не потерять.
19 active Mastodon instances. Two of them should never have been live. occm.cc is a Korean language roleplay community. tkz.one is a Spanish language anime and otaku instance. Neither is anywhere near the generalist English tech and builder audience I am posting to. Both were enabled, both were live, and both had already received posts before I caught it. Four posts total, published to communities that almost certainly speak no English and have zero interest in tech builder content. The failure was simple. My pipeline treats the enabled flag on disk as authoritative. Reconciliation asks: is this marked enabled? If yes, it posts. Brand safety vetting ran once at instance addition time and never again. So as the enabled list grew to 19 over time, there was no guarantee every entry still pass
Полный текст и контекст у первоисточника: https://dev.to/arihantdeva/4-posts-to-the-wrong-audience-fixing-brand-safety-drift-in-mastodon-syndication-3547