Sunday, June 19, 2011

How it all happend

There was some pretty big news in the IRC world yesterday. I had finally left FOSSnet, forever (and I did it in style). Here was the quit message I used: bikcmp says I can't share logs about kyle with kyle. As much as it pains me, I can not live under his governance. I will not be his  lackey. War is peace, ignorance is wisdom, and I am done

Now, before I start, I must say that I have nothing personal against bikcmp. I just didn't like the way he ran the network and how he was unwilling to change. There have been many attempts at fixing the network led my Null, Kyle, and myself, but they never made much progress as the rules were, as always, disregarded by bikcmp.


The first attempt we made led to the establishment of a voting system. You can find the channel #fossnet-ospnet-debate on irc.freenode.net, however, it is invite only. Here are the logs I have from that channel: http://paste.ubuntu.com/629416/
As you can see, we clearly had established a voting system. This is the same voting system I talked about in my first post here. An interesting link I have there was the OSPnet Declaration of Independence. Please note that this was more of a joke and was not endorsed by anyone other than myself (although I think Kyle and Null likely agreed).

However, something that was not intended happened. A vote was called by Null to remove bikcmp from staff and the vote passed. Bikcmp, by the voting policy, really isn't staff anymore. More logs, yay.

As you can see at the end of those logs, Spitfire and I, and later, JStoker, began working on a new decision making policy which is more like the one used on Wikipedia. It never went anywhere other than a bunch of great ideas.

The Final Time
Well, now that you have the history of the conflict, I can make a quick summary. Null was destaffed and klined. Kyle was klined and destaffed (for no reason by bikcmp). I managed to get Kyle back into staff and un-klined.

So, having made it this far, here is the final log of #staff. The log where I discuss Kyle being destaffed. As you can see, nothing sensitive is in this log and only small parts of it were shared with Kyle. But yet, bikcmp insists on saying that I can't share things he says about Kyle with Kyle (and yet, he shares logs all the time). As Null said, "bikcmp is the log sharing king."

He made up this rule that logs from #staff can't be shared and used it to destaff Kyle. Because of this rule, I decided to akill myself from the network, but I was already destaffed. So, I went with the best akill message I could think of: bikcmp says I can't share logs about kyle with kyle. As much as it pains me, I can not live under his governance. I will not be his  lackey. War is peace, ignorance is wisdom, and I am done

I hope you can now see what really happened. bikcmp has since taken these logs out of context to make me look bad. Here are two instances I will share with you:

10:49 <WaffleZ> [10:26:50] *MemoServ* Memo 1 - Sent by bikcmp, Jun 18 19:55:19
                2011
10:49 <WaffleZ> [10:26:50] *MemoServ* ------------------------------------------
10:49 <WaffleZ> [10:26:50] *MemoServ* before you speak out of your ass again, I
                didn't K:Line aj00200.  It was completely his choice.  Hell, he
                could of remained a staffer but he insisted on HIM AKILLING
                HIMSELF.  22:01:53  <@aj00200> then you are just  as stupid for
                letting me be staff. Why don't I let you akill me.
10:49 <WaffleZ> [10:26:50] *MemoServ* Memo 2 - Sent by bikcmp, Jun 18 19:56:22
                2011
10:49 <WaffleZ> [10:26:50] *MemoServ* ------------------------------------------
10:49 <WaffleZ> [10:26:50] *MemoServ* just to add to that: 21:45:16  <@aj00200>
                bikcmp: if I'm not allowed to give them logs about them, then I
                will kline myself.
10:49 <WaffleZ> [10:26:50] *MemoServ* Read 2 memos.



and



18:05 < Maniac> emoquit
18:05 < Maniac> i thought i wouldn't live to see one of those again
18:05 <@bikcmp> ikr
18:06 < Maniac> bikcmp: stop abusing your poor staffers
18:06 <@bikcmp> Maniac: i kinda figured that people in a +i channel know not to leak logs of that to people who wish to ddos us
18:06 <@bikcmp> i guess he didn't understand
18:06 <@bikcmp> what else would you expect
18:07 < Maniac> ddos is funny
18:07 < Maniac> unless it happens to you


Thanks for reading. I hope that you now understand the problem with FOSSnet and why it is not a safe network. Your ideas don't matter, only bikcmp's ideas. He has used this network to get attention, but it will now be his downfall. He has used all the staff as lackeys but he will no longer. The truth has come out and there is little he can do to stop it.

Thank you,
AJ00200