224 karma · joined September 20, 2017
I mean it likely is quite good based on their velocity and quality. But if we're to learn anything I'd really like to see its source code.
This picture shows some surrounding towns https://images.theconversation.com/files/541855/original/fil...
And string templates looked exciting to me. But after skimming https://openjdk.org/jeps/430
it sounds like they want to avoid backticks for "safety"? Like we can already use the plus operator to append strings why would it be any less safe to give us an ergonomic way to do that? Oh well, Java isn't exactly known for being ergonomic.
To make things weirder, the article claims that only mobile networks are affected. I wonder why that is. Is this just the decisions of a handful of telcos and it's being reported as a state-imposed restriction?
Edit: also in my opinion, "blocking at the protocol level" is a bit misleading since they can't actually see the packet contents. Wireguard for example is just UDP packets. They have to infer from other patterns that the traffic is Wireguard and drop packets that meet those criteria.
We'll go back to difficulties in exchanging secrets. But encryption as a whole will still work.
To me this is definitely not "accusing WEI-Opponents of Being Criminals". I don't support WEI but to claim that's what he's saying here is very dishonest.
If you just use wireguard then you have free reign to make any topology you want. And then you get to troubleshoot the routing mess you've made.