IRC Controversy
- Posted by jimcbrown (admin) Aug 06, 2010
- 1876 views
it was he whose post i was replying to.
Please quote the post where I accused you of FUD.
Regarding any fud i may have produced: you're welcome. Same as when you kickbanned me from #euphoria and then blamed the bot and some one else. Yeas, long history, and it is neither getting shorter nor being addressed.
WHAT!! I have never, ever, banned you from anything. As you well know, you are the person I am entrusting control with the openEuphoria.com name and I've never had any doubts or worries about doing that. And that time you were kicked from #euphoria, I believe it was accidental due to some bad bot code.
Iamlost/jimcbrown kickbanned me from the irc channel, it was he whose post i was replying to. It was not accidental, and it wasn't the bot that did it.
useless
I feel it is important here to clairify exactly what happened here, specially considering how long ago it has been since these events happened.
On July 7, 2008, [TiggrBot] was removed from #euphoria due to the bot listing what Kat claims was a typo for "hello". At this point, automatic language enforcement was already supposed to have been disabled but I accidently reenabled this part of it when addressing a different issue. The result of this was that Tiggr ended up leaving the channel for good, despite my repeated enquires to Kat that Tiggr return. (The invitation to have TiggrBox return to the channel is still open.)
Much later, Kat changed to an ISP that used centurytel.net - which often was a rather unreliable ISP that had frequent connetion issues.
On June 14, 2009, in line with a general IRC policy that is described in http://meta.wikimedia.org/wiki/IRC/wikipedia/Channel_operator_guidelines#Other I experimented with some options to automatically deal with idle users (such as users whose computers are connected but who are physically asleep in their beds - a situation that happens often with me) who are having connection issues. At this time, Kat made clear that she was firmly against this. Since she was the only person at this time who had this sort of issue, I dropped this idea.
At that point, I decided to simply not apply that policy to Kat. No one had ever complained about it, so it simply wasn't a problem at that time.
On July 16, 2009, someone complained to me about Kat's client autojoining. Kat's refusal to consider any other solution aside from the /ignore command (a command that a person can use to censor or ignore text from other users on IRC) placed me in a difficult position. So I followed the policy to the letter.
After this, another solution was offered. Someone worked to set up an interface for Kat which would enable her to connect to the channel 24/7 but through a jumpbox that could transparently hide her connectivity issues. She never used this.
Kat instead stated that she'd never come back to the channel. I simply told her that she was always welcome back and left it at that. (Her post detailing her conversation with CoJaBo took place in that same channel today.) Likewise, her status as channel operator (which incidently includes the ability to remove bans, including bans set on herself) has remained intact this entire time.
I'm pretty sure you've brought this up every chance possible, but its out of context-
One thing I note is that there was a large interval of time between this happening and her first mention of this on the forum.
Another thing that I note is that a different user was temporarily kickbanned from #tiggrbox on March 3rd or 4th, 2010 due to ISP issues. (That is, for identical reasons.)
iamlost is absolutely careless at applying bans, making them ridiculously broad then leaving them indefinitely- no offense meant here, but I've complained about this several times before and yet it keeps happening. Last time I checked, most of the UK and anyone affiliated with the Apache project was banned.
This is entirely correct. I previously had an unrelated problem with a series of network trolls and did this in frustration. I later set up access for CoJaBo so he could fix this for me, which he did... but it may be time to ask him for more help.
