Hacker News new | past | comments | ask | show | jobs | submit login

As an ex-freenode staffer, this is simply untrue.

You took over with zero transition plan, and no engagement with staff - none. You had had no involvement in the running of freenode until this week and had no relationship with any of the team.

You marched in, announced that you were saving freenode from the "hostile takeover" of their own consensus-based, transparent, self-organisation, and SURPRISE they decided that they didn't want to work with a mystery absentee landlord who rocked up, proclaimed themselves, and demanded their land back with a team of lawyers.

You have no track record on freenode, of working with the ex-staff team, and clearly don't understand the community.

Why else would volunteers who have been working on a project for ACTUAL DECADES FOR FREE ALL WALK OUT OVERNIGHT? This is not what people do with things they love unless something very odd is happening.

As far as I'm aware no-one damaged everything - and went to pains to leave in an orderly line. They just didn't want to work for you when you swooped in.

You even had the head of staff working with you to let you figure out how your new toys work. Any damage to data or infrastructure is, I think, the responsibility of the management.

Which if you are to be believed has been you for years anyway.




Is it true that they pulled freenode’s mail server?

I see lots of emotion here, and emotion is fine. But yanking someone’s existing infrastructure isn’t very nice.

If that part isn’t true, though, then someone here is lying.


The mail server was working when the whole staff team resigned.

What happened after then will have entirely been within the control of the freenode management, their administration, and their sponsors.

Every ex-freenode staffer I have talked to has been exceptionally cautious about damaging the data and systems they tended for literal decades, and to my knowledge none were disrupted.

I think here, you have to look to Andrew, ask what his transition plan was, and what he thought would happen when he started throwing lawyer's letters at the head of a functioning and healthy team of sysadmins and staff members who were happy to continue the job they'd been doing for years, for the community, indefinitely..


I'm having a hard time following anything.

Andrew claims they brought a lawyer in after their access to the DNS was revoked and their request for that to be undone was denied. They supposedly have had access for 5 years without issues, and according to Tomaw it's something they'd "probably never do anything with."

Why should Andrew accept that, even if the only thing Freenode Ltd. owned was the domain and name? If they didn't do anything nefarious for 5 years, what changed that made the domain takeover now necessary? Especially since the person taking over the domain apparently admits Andrew wouldn't do anything to it... or was that exchange fabricated?


I don't think tomaw was aware that freenode ltd owned anything apart from the freenode live conference, until the legal discussions happened. So from his point of view it would have been a case of "Why should the people we ran a conference with in 2017/2018 have access to our domain?"


That implies christel was the only staff with access to DNS until now and was hiding that fact, since the domain's been registered to Freenode Limited since at least 2018 and they'd have noticed the change had they been accessing it.

I've been reading more into it and it seems that wasn't the case [1], but that just leaves me with more questions.

[1]: https://gist.github.com/realrasengan/f569c5e4727d21eb939fff9...


Understanding that:

(a) Freenode ltd had access to the domain

(b) Freenode ltd should have access to the domain

(c) Freenode ltd is the rightful owner of the domain

are three very different matters. How often do you whois your employer's domain?

Otherwise, if you've just been appointed leader of an operational staff and believe your organisation owns everything involved, it doesn't seem unreasonable to start introducing basic infosec practices around limiting access (or if it was caused by mandating security measures like 2fa, as mentioned elsewhere in thread)


Not often, but maybe when its parent company goes through a merger and the head of staff makes a public announcement saying "the freenode project will continue being part of and having access to support from the Imperial Family Companies (formerly London Trust Media Holdings (LTMH))." [1]

Since I believe freenode to be completely community-owned apart from some holding company that's supposed to host a conference, at that point I might check our WHOIS records and maybe our own policies [2] and question who I'm actually volunteering for.

[1]: https://freenode.net/news/freenode-pia-changes

[2]: https://web.archive.org/web/20180606130945/https://freenode....


Why the anonymous account?


That's his name on Freenode too. I don't think that's anonymous. He very clearly reads HN, as his "Freenode is FOSS" post links PGs fierce nerds post.


I'm talking about whomever ex-fnstaffer is. That's this person's name on Freenode?


Fair enough, my fault.


They value anonymity?


And for all I know, ex-fnstaffer is a tomaw alt. Do you not see the problem with all these anon new accounts that were apparently created for the express purpose of saying they don't like Andrew Lee? This reeks of astro-turfing, and for all I know it could be one person behind like 5 different accounts.


As someone who has participated on 4chan in the past, I personally have learned to take comments at face value and not place much weight in the names. It's true that anyone can claim anything, and I don't think there is much benefit to seeing an identity tied to the user's posts.

I've seen mobbing in general against both sides of this ordeal, and I would be unsurprised to see astroturfing efforts as well. It upsets me that people tend to stoop that low, but I'm attempting to gather all info I can from both sides in order to come to my own conclusion.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: