PIA and Freenode joining forces
freenode.net
freenode.net
Well, no. All your old opers left because money from donations keeps disappearing. Your new opers probably don't even know how to apply a k-line and rely on that supybot you have to administer the network. I'm safe.
I'd be interested to know however whether the US government can intercept traffic to/from:
- Servers located in the USA but operated by VPN companies incorporated and staffed outside the USA.
- Servers located outside the USA but operated by VPN companies incorporated or staffed inside the USA.
It seems to me that as long as you're using a US-based VPN server, there's always the risk the cloud or transit provider can be compelled to intercept traffic regardless of the owner's jurisdiction.
The question of how well protected non-American servers operated by Americans are still seems to be unanswered too. Microsoft seems to be winning their case against handing over overseas data[0] but Google seems to be losing[1].
[0]: https://secure.politico.com/blogs/under-the-radar/2017/01/mi...
[1]: https://www.washingtonpost.com/news/volokh-conspiracy/wp/201...
I have no idea how exactly it affects PIA though.
Not terrorism/other serious crimes, but Megaupload had the same constellation (they had some US colocated servers), and it will unfortunately likely end with Kim Dotcom being deported to the US. So yes, such a service constellation may very well lead to deportations to the US as soon as some bought-off or incompetent US judge/DA gets his rubberstamp.
The massive outreach of the US (not just this, but also that their citizenship is bound to paying taxes, even abroad - leading to the massive ... called FATCA) is something that really angers me. But hey, it's difficult to argue with a country that might send four dozen Tomahawks based on the current Fox News programming. (Obviously sarcastic, but the "the US regularly abuses its foreign power" still stands)
Source: https://thatoneprivacysite.net/vpn-comparison-chart/
Please can we use the actual title of the actual blog post.
Edit: Thanks!
Wild speculation based on "I think it sounds like that" isn't actually constructive.
I've had the blog post updated to say "allied with" rather than "joining the family of" in the hopes that people will actually read the words going forwards rather than jumping to conclusions.
As it stands, the blog post just isn't very transparent. It mentions PIA "provid[ing] us with opportunities and resources going forward, including an operating budget", and that it is "now officially part of the PIA family".
So you have money changing hands, and property changing hands. That doesn't sound like a sale, it's what it is.
Unfortunately, it's rather thin on substance regarding future intentions. But I guess it could indeed make sense purely as a pro-bono project with a bit of a PR windfall for PIA.
I completely agree. The former doesn't generally result in a press release and/or public announcement that includes phrases such as "... will continue to operate as a not-for-profit entity under the same management, with the same principles, ...".
Personally, I don't care one way or the other whether this was a "purchase" or a "merger" or "alliance" or whatever you want to call it. I have been a freenode user (and, if memory serves, an "occasional financial supporter") since (probably) shortly after it became freenode and I expect that I will continue to be a freenode user in the future (unless something major happens to change that).
Vaguely worded announcements and a lack of detail, however, tend to cause things like "wild speculation" and "jumping to conclusions".
Submitters: Please use the original title unless it is misleading or linkbait, as https://news.ycombinator.com/newsguidelines.html asks.
EDIT: Nevermind, seems that was done below.
During the javascript irc flooding attacks a while back, efnet took 1 day to patch their servers, rizon took 3, freenode took 7 months (of nonstop netsplits and network breakage)
In return, Freenode has consistently sabotaged the Tor service so that the only way to connect safely is with a VPN.
It's now fixed.
If you continue to have problems, please file a support ticket rather than throwing around unfounded accusations of sabotage.
I did briefly attempt to understand the relevant chunk of C code, but my eyes crossed and I developed a headache.
So sorry if that's a bit vague.
No. Some idiots decided to brute force passwords via tor. They finally fixed it after a few years or so.