Hacker News Reader

Comment by danieldle | Hacker News Reader

I see that you are spreading your falsehoods here, too.

The issue with services was not due to the "previous team", but rather due to the sponsor pulling their box. The "previous team" had no access to them by that point.

As you might have guessed, the sponsors had a gentlemen's agreement with previous staff and not with Freenode ltd. Now most of them obviously don't like sponsoring their boxes for your company, so they are pulling them.

Stop lying, Andrew. If you would have approached this in a sane and respectful manner and not sent your bloodhounds out, you maybe wouldn't have inherited smoke and ashes.

View on HN

Leaving a project when you know that it will cause their infrastructure to collapse isn’t too professional. It seems pretty fair to characterize this as partly your fault, since, y’know, you caused it by leaving.

I think both sides in this are acting bizarre. You’re talking like it’s an oath of allegiance rather than an irc server.

If you're being paid, sure. But volunteers are allowed to withdraw their support at any point in time for any reason under the sun. They have exactly zero obligation to anyone but themselves.

It would not have collapsed at all. It simply disappeared because the sponsor of it was a sponsor of freenode, and didn't want to be a sponsor of Andrew Lee. This is entirely up to them and their decision, it is their box, their money.

OP stated the sponsor pulled the box after they no longer wanted to support freenode. How would the former staff have handled that more professionally? Begging the sponsor not revoke access?

If I were a sponsor who found out a project I was donating resources to was taken over under questionable circumstances by someone with deep pockets I'd have done the same.

Yeah, you're right. I guess it wasn't up to the volunteers; sorry.

It wasn't a very nice move by the sponsor to yank support without giving any notice – usually you'd get a week, or 30 days, or something – but it sounds like no one had any obligations to.

I recall just a few months ago when Amazon yanked the plug on hosting a company's infra with little more than 24hrs notice.

So I guess that's precedence for something like that, and yet, that company held a contract with Amazon to host their infra.... no such scenario in this case ;)

There was substantially more than 24 hrs ... amzn sent several communications to Parler explaining their issues with what Parler was (or was not doing). The final communication had a 24hr deadline.

Reply on news.ycombinator.com