“Setting the record straight on Freenode” [pdf]
techrights.org
“Setting the record straight on Freenode” [pdf]
1–10 of 307 posts
Re: “Setting the record straight on Freenode” [pdf]
#2This link initiates a download.
Re: “Setting the record straight on Freenode” [pdf]
#3This link initiates a download.
It's a PDF. Firefox just displays it in the browser with no download prompt.
Re: “Setting the record straight on Freenode” [pdf]
#4Once again showing that the hardest problems in tech are not actually technical problems - they're social problems.
Re: “Setting the record straight on Freenode” [pdf]
#5This is probably a pdf of this blog post: https://freenode.net/news/freenode-is-foss
I'm not familiar with the situation, but find it odd, that the author signs off as "Chairman, freenode limited" where he seems to be the owner of the company that owns Private Internet Access (PIA) [0]. This form of selectively under-reporting has a weird smell to it.
Re: “Setting the record straight on Freenode” [pdf]
#6As an outsider who hasn't used IRC or Freenode in over a decade, this situation is impenetrable. Neither the posts by the Freenode volunteers nor this post by Andrew paint a coherent narrative I can follow (maybe I'm just old).
Best I can gather, the flashpoint that triggered this series of events is a dispute over the control of the freenode domain name and DNS servers?
Re: “Setting the record straight on Freenode” [pdf]
#7I want my usenet back
Re: “Setting the record straight on Freenode” [pdf]
#8> The former staff leave, destroying the network andits community in the process
Baffling lack of self reflection on display.
Own your mistakes.
Re: “Setting the record straight on Freenode” [pdf]
#9Once again showing that the hardest problems in tech are not actually technical problems - they're social problems.
[deleted]
Re: “Setting the record straight on Freenode” [pdf]
#10As an outsider who hasn't used IRC or Freenode in over a decade, this situation is impenetrable. Neither the posts by the Freenode volunteers nor this post by Andrew paint a coherent narrative I can follow (maybe I'm just old). Best I can gather, the flashpoint that triggered this series of events is a dispute over the control of the freenode domain name and DNS servers?
The FreeNode staff (rightly) don't want FreeNode's operations taken over by the owner of a VPN company and former CFO of Mt Gox.
They're not obliged to work for this cretin.