Comments on: Another Freenode Annoyance

By: Ed Marshall

Ed Marshall — Thu, 05 Nov 2009 21:10:17 +0000

A little late to the party, but I just found out the same thing happened to me when I tried to change my email address on my nick.

Well, not my nick. Now, apparently, it’s someone else’s. Fabulous.

All the noisiness in the world on the IRC servers themselves doesn’t help me a whit if I only log in sporadically. Why on earth did I register an email address with NickServ if they didn’t intend to use it?

Bah. Ah well, so be it. FreeNode isn’t of much use to me at this point anyway.

By: MJ Ray (software.coop)

MJ Ray (software.coop) — Tue, 11 Aug 2009 16:39:21 +0000

Some of the settings (half-bans) involve more than simple configuration, while others (auto-identify) require script-writing in many clients.

Bottom line: the problem John encountered was a completely avoidable boneheaded freenode policy decision.

By: KI

KI — Mon, 03 Aug 2009 12:00:31 +0000

it’s hardly “playing obsessively” to configure the software you use, to utilize a service you signed up for…

By: MJ Ray

MJ Ray — Mon, 27 Jul 2009 08:13:32 +0000

Wow, that sucks. There but for the grace go I.

@Thomas – yes, freenode have extensive instructions on how everyone should configure every client they use to work with freenode (auto-identify, recognise half-bans and so on), but that just isn’t realistic. We’re meant to be developing software, not playing obsessively with IRC clients.

By: Thomas

Thomas — Sun, 19 Jul 2009 12:41:32 +0000

I know it will be no solace now that you’ve lost your nick, and I’m not a big fan myself after the Mibbit fiasco, but they do make quite a noise about the recommended way to set up your nicks. This includes setting your client to auto-identify, either by using your password as the IRC server password, or by automatically sending a message to nickserv when you log in.

By: Bernhard R. Link

Bernhard R. Link — Fri, 17 Jul 2009 10:35:43 +0000

I think the part about OFTC never deleting nickserv is false. I know at least one case in the other direction on OFTC (where someone was able to gain a nick after enough inactivity on the other side).

By: Caracal

Caracal — Fri, 17 Jul 2009 02:16:02 +0000

Actually, it did … here’s the full text of the notice:

Jun 09 02:48:27 -christel- [Global Notice] Good morning all, in two days, we’ll be dropping expired nicks and channels. This is a semi-automated process to clear out the deadwood in the services db. Please remember to identify to NickServ and see http://bit.ly/Q6iKn for more further information. Have a good day and thank you for using freenode.

And the linked web page gave more details.

All that’s very well and good, but you still lost your long-time nick, which sucks. And it sounds like their response was quite substandard, which sucks much worse. Lilo was a personal friend of mine, and whenever there was an issue on Freenode, I could usually get it resolved with his help. Since his passing, nobody there knows me, so I’m just another fish in the ocean.

By: John Goerzen

John Goerzen — Fri, 17 Jul 2009 00:48:57 +0000

I’m glad they did go to some effort to announce it. Obviously I didn’t see that notice, but it does make me feel a bit better about it.

I don’t know if I was logged on during that period or not; even if I was, it’s possible the notice crossed my client while I was asleep. With the baby pretty close at that point, various unusual projects, and our bedtime issues with Jacob, I wasn’t on IRC much in June.

But even given that message, I don’t think it would have triggered me to do anything. After all, I keep logging on to Freenode; why would I expire? It should have explicitly said that if you don’t IDENTIFY, you may be expired.

By: Caracal

Caracal — Fri, 17 Jul 2009 00:19:43 +0000

Actually, Freenode did a one-time clearout of “deadwood” last month, and announced it noisily several days in advance. One sample message, which I was sick of by the time they actually did the deed: “This coming Thursday (June 11th) we’ll be pruning the Services database, removing expired nicks and channels. Please make sure you IDENTIFY to NickServ to avoid disappointment.”

Granted, Freenode hasn’t been the same since Lilo died, but to say that “they never notified people of the new policy” isn’t quite accurate. If you were logged on during the announcement period, you knew about it.

And I’m guessing that “OFTC doesn’t ever delete nickserv registrations” should probably read “haven’t ever so far”. And that’s because they’re not big enough or old enough yet.

By: Florian

Florian — Thu, 16 Jul 2009 21:55:46 +0000

Actually I’ve totally had forgotten about OFTC and just stumbled over it again earlier today.
Seems all of the project that I follow seem to stick with freenode… weird