Icon nowrite
This forum page has been archived. Please do not make any further edits unless they are for maintenance purposes.
Forums: Index > Wiki discussion > FOWchatbot, chatlogs and user rights

Our new chat botEdit

As most of you already know, I have imported a script from our friends at the Runescape wiki that allows us to automatically log chat. A little background first:

  • When I became active in chat, GhostAvatar always kept the chat logs. When Ghost left, I took it upon myself to log chat. Manually logging chat requires that you leave chat open in a window all the time and periodically save the page.
  • Logging chat has proven to be a critical issue when situations arise in chat that are brought to the entire wiki's attention for remediation. Without logs or screenshots from logs, there is scant real evidence of what happens in chat, other than people's imperfect memories.
  • There have been times when action was needed on events that occurred in chat that I was unable to provide logs for. Lack of clear evidence made those situations much harder to prosecute.

Due to infrequent connectivity issues and some changes made to chat, it soon became impossible to log all of the activity in chat manually. I searched for solutions and found a couple of wikis that log their chat. A few questions about use of the scripts went unanswered though. After Agent c suggested looking into the Runescape chatbot, I approached Joeytje50 about use of his script. This gave birth to FOWchatbot and its associated logs. Now that the chatbot's use has been ironed out and it's proven stable enough to successfully log chat, a few minor issues have to be addressed:

  • I have changed the chat window heading to include a notice that the chat is recorded and logged, with links to the logs. The logs are available to see, as the script uploads them to the wiki every hour.
  • I'm considering FOWchatbot to be an "official" Nukapedia account. I will maintain primary use of the account, but during times of my absence (I've got some vacation planned soon) I will pass the log-in details of the account on to another administrator who can maintain a constant presence in chat to log in my stead.
  • FOWchatbot needs to run in a separate browser window than any that I am logged in on my master account. I makes no sense for me to have two chat windows open at the same time, so as Ghost had before me, I've taken to chatting from the bot account.

Due to my above use of the FOWchatbot account and the need to protect the chat log pages from tampering or vandalism, I need to grant the FOWchatbot account sysop rights. The bot script will not be able to write to the protected chat logs unless it has sysop rights. I will also be able to use the chat mod tools when monitoring chat from the FOWchatbot account, should the need arise.

Unless anyone has any legitimate reasons why FOWchatbot should not be granted sysop rights to do it's job, I intend to grant that account those rights. Speak now or forever hold your peace.


No Objection. I think theres precedent for "sock" accountsm for admins/moderatosr being given mod rights before. Agent c (talk) 01:25, January 12, 2013 (UTC)

I see no reason to object to something like this, although I just went to take a look at the logs and noticed for some of the longer posts you have to scroll all the way to the bottom and manually click the right arrow key to scroll over. Unless I'm doing something wrong. Is there any way to make the posts wordwrap to imrove the log readability? Great Mara (talk) 02:07, January 12, 2013 (UTC)

It all sounds good. My only suggestion is that the number of people who know the account's password should be limited on a need-to-know basis, since an account with multiple users logging in on it could possibly cause trouble if one user decided to do some undesirable tasks with it (how will we know who?)... But I trust all of our sysops and I doubt that'll be a real problem, maybe just something to keep in mind. --Skire (talk) 03:11, January 12, 2013 (UTC)

Agreed. We do similar things for the email, youtube, formspring and twitter accounts. Agent c (talk) 03:21, January 12, 2013 (UTC)
Very easy solution. Re-set the account password after each new day passes where another user had access to the account from the day before. Lock down the account and track where it was logged in from last if someone else decides to take it over. ForGaroux Some Assembly Required! 03:31, January 12, 2013 (UTC)
A password reset every day seems anything but simple... Seems like a pain in the kneck.... Agent c (talk) 03:34, January 12, 2013 (UTC)
I change all of my passwords every week. :P Changing a password on Wikia only takes a couple of minutes at most. ForGaroux Some Assembly Required! 03:35, January 12, 2013 (UTC)
Periodic password changes are great. Doing it daily is too much. --Skire (talk) 03:44, January 12, 2013 (UTC)
I don't see any issues. And I think a bi-weekly password change would be good (daily seems a little bit excessive). USA Flag Pre-War User Avatar talk 03:28, January 17, 2013 (UTC)

(Technically, since I'm the legal account holder, and the ToU state that the responsibility of the password is mine to keep secure, what I'll probably do, when I need to have someone cover for me, is that I'll change the password when I assume control of the account again each time. Sound reasonable? The Gunny  380px-USMC-E7 svg 03:38, January 17, 2013 (UTC)

Good plan. USA Flag Pre-War User Avatar talk 03:40, January 17, 2013 (UTC)
Community content is available under CC-BY-SA unless otherwise noted.

Fandom may earn an affiliate commission on sales made from links on this page.

Stream the best stories.

Fandom may earn an affiliate commission on sales made from links on this page.

Get Disney+