News for hackers. Stuff that matters.
Re:“Setting the record straight on Freenode” [pdf] by wizzwizz4 on Friday May 21, 2021 @11:25AM (#27235249)
> In 2017, Christel, the former owner of freenode, asked me for assistance with funding and asked me to acquire it. I oblige.

Was Christel ever the owner of Freenode? I thought Freenode was anarchically-organised.

Re:“Setting the record straight on Freenode” [pdf] by mynameisvlad on Friday May 21, 2021 @11:28AM (#27235294)
Christel was the head of staff and created a limited corporation in the UK to manage freenode’s name and trademarks. What’s unclear is how much “freenode limited” owns in terms of the network itself.
Re:“Setting the record straight on Freenode” [pdf] by logical_person on Friday May 21, 2021 @11:38AM (#27235443)
the formation of Christel's corporation did effectively make her* the owner. any court would see a service she is involved in operating by his company's trademark, as belonging to that company. sad.
Re:“Setting the record straight on Freenode” [pdf] by mynameisvlad on Friday May 21, 2021 @12:14PM (#27235962)
As I said, the part that is unclear is how much “freenode limited” owns.

The core of freenode- the servers themselves- are sponsored and owned by third parties. The volunteers maintaining the infrastructure are not affiliated with the corporation either.

So really what this whole mess has boiled down to is what is the delineation between freenode limited and freenode-the-volunteer-run-sponsored-network. Andrew believes he owns everything, and the former staff believe he only owns the name, trademark, and potentially the website/domain.

Re:“Setting the record straight on Freenode” [pdf] by pedrocr on Friday May 21, 2021 @01:18PM (#27236964)
> the former staff believe he only owns the name, trademark, and potentially the website/domain

That's my reading too but apparently the staff did hand over the network on their way out. So now freenode is apparently actually consolidated into the Freenode Limited company with both the name/DNS/trademark and the network itself. The legal situation behind those moves is not public and is probably the only thing left to be known.

Re:“Setting the record straight on Freenode” [pdf] by mynameisvlad on Friday May 21, 2021 @01:36PM (#27237188)
It just goes back to my point, though, what is "the network" and what can any one person or group of people hand over?

The ssh keys to the servers? Sure, but that doesn't mean freenode ltd now owns the servers or the software running on them. They've just been given operational control over them (which I guess is exactly what Andrew wanted at the end of the day) but who exactly owns "the network" if that's even possible is still incredibly murky, at least to me.

A "network" is a very nebulous thing when everything is informal and run by volunteers and sponsors.

Re:“Setting the record straight on Freenode” [pdf] by pedrocr on Friday May 21, 2021 @01:49PM (#27237416)
I'd say that if you control both the DNS and own the network data (chanserv/nickserv/etc) you own the network. You can at any point stand up an entirely different infrastructure, staffed by entirely different people, switch over to it and the users just migrate over as they reconnect. It would look like a really bad net split that doesn't resolve without reconnecting. The splintering network can just advertise a new DNS and fork the network although legally they may not have a claim on the data.

In this case it seems the DNS might have been sold in rather murky circumstances a while ago although the technical control of the DNS was not handed over. That seems to be the DNS change that was the focal point for the current crisis, when, presumably under legal threat, the staff handed that over.

The network data doesn't seem to have been explicitly owned by anyone. The volunteers managed the servers donated by other entities. In a court it would probably be really hard to figure out who owned that data given the lack of an entity the users where agreeing to a ToS with. But now the Freenod Limited company does control everything at least technically. If there was a hostile takeover it was that one. The staff apparently didn't think they could just take a backup of the data and move it over to the new network either. Maybe they've conceded they didn't have a claim on that data or they were cautious for legal reasons.

Re:“Setting the record straight on Freenode” [pdf] by mynameisvlad on Friday May 21, 2021 @02:03PM (#27237601)
Very good points. I had read your other comment saying the same and it makes a lot of sense; the service databases likely are the "true" network since everything else can be changed around it.

> The staff apparently didn't think they could just take a backup of the data and move it over to the new network.

I doubt we'll ever find out if it's because they believed freenode ltd owned the data or just didn't want to deal with the inevitable legal battle that would certainly ensue. Sad that often times it's just the person with the stronger legal team that wins in these situations.

Re:“Setting the record straight on Freenode” [pdf] by admax88q on Friday May 21, 2021 @11:53AM (#27235638)
Her
Re:“Setting the record straight on Freenode” [pdf] by mrweasel on Friday May 21, 2021 @11:37AM (#27235419)
It’s a mess. I’d gotten the impression that Freenode just recently been bought.

Are the staff leaving due to issue dating back four years, because the owner have been so hands off that nobody noticed before now?

Re:“Setting the record straight on Freenode” [pdf] by c-cube on Friday May 21, 2021 @12:11PM (#27235915)
There is such as thing as letting the dust settle before you make your move. Look at what Facebook has done with whatsapp, a few years after the acquisition; clearly it was planned from the start but they had to wait a bit.
Re:“Setting the record straight on Freenode” [pdf] by zokier on Friday May 21, 2021 @01:41PM (#27237284)
That is kinda the problem; anarchically-organised community can not own a domain name, it falls always to some singular entity. And that is where the anarchy broke down when the community realized that they did not own the domain