X-Git-Url: https://jfr.im/git/irc/freenode/web-7.0.git/blobdiff_plain/9f71a395db5a63f93759d71910a93821e20fb56f..HEAD:/content/news/2007-08-26-cia-bots-the-instant-version-control-informants-an-annoyance.md

diff --git a/content/news/2007-08-26-cia-bots-the-instant-version-control-informants-an-annoyance.md b/content/news/2007-08-26-cia-bots-the-instant-version-control-informants-an-annoyance.md
index 948bfc5f4..734c351ac 100644
--- a/content/news/2007-08-26-cia-bots-the-instant-version-control-informants-an-annoyance.md
+++ b/content/news/2007-08-26-cia-bots-the-instant-version-control-informants-an-annoyance.md
@@ -1,3 +1,4 @@
+---
 author: christel
 date: 2007-08-26 19:20:55+00:00
 slug: cia-bots-the-instant-version-control-informants-an-annoyance
@@ -5,6 +6,8 @@ title: CIA Bots - 'The Instant Version Control Informants' -- an annoyance?
 category: community
 category: freenode
 category: projects
+imported: yes
+robots: noindex
 ---
 While most FOSS contributors will be familiar with [CIA](http://cia.vc) and likely to utilize it for tracking commits for their project(s) and contributors, we occasionally have concerns raised from projects who find that CIA-* joined their channel unexpectedly and not on their request, this may be because someone typoed a channel name when setting things up over at the CIA page, or because someone decided to be helpful and share the joys of CIA with a new project/channel but forgot to ask the project admins/channel owners whether this would be a-ok.. and occasionally we find ourselves getting a bunch of notices alerting us to a CIA-* bot as a potential spambot as it tries rejoin a channel from which it has been banned, or when its been misconfigured and cycle a channel which has a forward set (this tends to confuse most bots!).