Once you've bought a knife, it will usually be illegal to carry it in public unless you have a good reason, and "self defence" is not a good reason.
Some particular knives, which have no apparent purpose except as weapons, are just illegal automatically except in some cases if you're a museum. In particular almost all swords (if they have a working blade) are in this category, and most things designed as concealed weapons (e.g. blade hidden in an umbrella, combs that are actually knives, push daggers)
I mean, are instances of kids <=17 year olds with knifes down? What about shivs and other things?
The reason I'm asking is because as a kid, if I had been told to not do something, I'd just find a way to do it. Not to use it, but to find loopholes and just say, _so what?, I can do x_
Reducing violence is a tricky thing because to a large extent it seems to me to be a symptom of broader and nearly intractable societal malaise. Not that it isn't worth removing nuclear weapons from circulation but the returns diminish quicker than most public policy folks seem to want to admit.
[1] https://commonslibrary.parliament.uk/research-briefings/sn04...
There was a spate of stabbing reports, about a decade ago. That seems to have died down. My guess (and it's only a guess) is that only drug dealers and people bent on mayhem carry guns or knives that aren't street-legal these days; what's the point in getting busted for carrying a penknife?
Incidentally, I don't get the point of the ban on locking knives. If you stab someone with a knife that doesn't lock, then I suppose there's a risk to your own fingers; but the dude you stabbed won't care if it was a locking knife or not. I do get the blade-length restriction though. You don't need a 3" blade to sharpen pencils.
My straight razors are street-legal, though, and I think they're quite a lot more dangerous than a 3" knife that locks. The sharpened edge of a razor is only about 2" long, so I assume it's street-legal; but you could really make a mess of someone's face with a razor (the preferred weapon of Pinky, the gangster from Brighton Rock).
My friend "got" a nice chat, and went on with his day, but did later comment that had he not had the outfit to go with them, and a vast array of obvious kitchen tools, he thought that they'd probably look at it a lot more seriously.
We'll have to ban rocks next though.
Then again, if you want to argue stone-age semantics: we can't ban anything and should just resort to continuous murder since rule-based society is too hard.
If airlines banned knives and someone posted a definition of “knife” that suggested they are only used for eating food, it would be perfectly reasonable for a reply to point out that there are dangerous uses which might have led to the bad, and that it’s disingenuous to suggest that the ban was obviously motivated by a desire to make eating difficult.
It’s still fair to debate the balance of use and the merits of the ban, but IMO it is not reasonable to be upset over a more complete definition and context.
https://hackernoon.com/domain-fronting-101-what-is-domain-fr...
"Amazon and Google bow to Russian censors in Telegram battle"
https://www.fastcompany.com/40568177/amazon-and-google-bow-t...
"U.S. Cloud Providers Face Backlash From China’s Censors"
https://www.wsj.com/articles/u-s-cloud-providers-face-backla...
>China’s Internet censors have strengthened content screening in recent months, creating difficulties for businesses and disrupting more commonly used firewall-circumvention software called virtual private networks, which connect users to the Web through a proxy server overseas. President Xi Jinping has ordered tighter control of online content that may undermine the ruling Communist Party, with bloggers facing jail for spreading what the government says are false rumors.
The CEO even came on HN to try to frame it as an abuse mitigation, accusing Lantern of exploiting Cloudflare and arguing that they were not a customer. That was obviously false because you need to have a Cloudflare zone configured for domain fronting to work. They were a customer as much as the targeted hate websites they strenuously defend.
https://news.ycombinator.com/item?id=9234367
Companies show their color in selecting who they will stand up for.
What actually happened was we started to get reports from customers that we were serving content from unrelated sites under their domains. Wasn’t happening a lot but for a reverse proxy that’s terrifying and about as bad as it can get.
The issue was domain fronting where SNI didn’t match Host causing us to handle the traffic incorrectly sometimes (infrequently but not zero). Since standard use of the Internet doesn’t need SNI and Host: to not match we blocked the use of domain fronting very fast to ensure the integrity of our service.
Lantern was domain fronting tickling this bug and causing our customers trouble. Hence we dropped domain fronting.
I remember this well because I actually debugged it myself and reported the problem in Jira. You weren’t involved and inventing a story about “China” is dead wrong.
I do remember one terrifying bug that Lantern was tickling which caused responses to cross streams, and I was involved in debugging that, but it was not due to the Host/SNI mismatch. It just happened around the same time that domain fronting was blocked. (I am going to respect my confidentiality agreement here, but if you want I can share what I remember here or in private.)
To be clear, that's not correct we did do this to mitigate the bug.
We were facing the bug that I described (the cross stream thing) showing up when Lantern was used. It was causing disruption to our service and customers were writing in. We were trying to understand what was happening and needed to stop it. One of the things we did to stop it was disable domain fronting. As we were seeing the customer reports we didn't know if this was an OpenSSL bug, something in NGINX, something in our code, but we did know that Lantern was somehow causing it and they were doing domain fronting which wasn't the standard use of our service and so we dropped it.
My point is that disabling domain fronting (or leaving it disabled after finding the bug's root cause) was a policy decision, not something necessary to mitigate the bug or prevent it from re-occurring.
Filippo: You, sadly, fall in the later camp and have for some time. You’re wrong here. You’re wrong most times you post uninformed speculation. It’s tiresome.
I wish you luck in whatever you’re doing post-Google and hope you find the success you’ve desired since our first conversation that will, I pray, stop you from your latent and seemingly unpatchable personality bug of making shit up and making yourself a more important figure in every story than you actually are or ever have been.
If you'd please review and follow the site guidelines, we'd appreciate it: https://news.ycombinator.com/newsguidelines.html.
No organization I am part of will ever do business with you if I can stop it.
You fought for Turing but I suppose the Uyghur concentration camps mean nothing to you. They are not British so how could their lives be worth fighting for when there is money to be made (for yourself) without regard to morality or any sense of decency.
But good job doing Cloudflare PR.
There was also a prelude to all of this that I think made things stickier and bizarrely personal. Prince and I share a mutual friend who introduced us just a few weeks prior. Prince said he supported what we were doing, but asked that I not talk about it publicly, presumably because of the pending China deal. The problem was that literally moments after our friend had introduced us via email, and before he made that request, I had a call with the WSJ where I talked about precisely this. I did everything I could to walk back the article, but Prince didn't buy it and seemed to go ballistic over it. After the WSJ piece, we pulled back from talking more publicly in general.
Oh, I forgot! We also partly stayed silent because they didn't actually shut down what we were doing at all =). They matched the SNI to the Host header, sure, but they missed a little detail: we weren't using SNI. Hehe. Lantern worked for another six months or so, and then, through a similarly bizarre sequence of events, we essentially tipped them/you off to what was happening. We remained a customer throughout, and we're a customer to this day.
Either way, though, Cloudflare does great work, and everyone has their faults, so I'm generally sympathetic over the whole thing with the one caveat that I am truly unclear how much ultimately did relate to China, most clearly in terms of any public support for these internet freedom techniques.
Oh, and I've wanted you to work on Lantern forever btw -- could get the band back together with @benjojo. Oooh actually if you're not aware of it, the uTLS Go TLS fork is a hugely impactful project that's in widespread use (I would guess maybe 50 million monthly active users rely on it in censored regions via various projects) but needs updating - https://github.com/refraction-networking/utls
Oh, and if you think we were effective in China then, you should see what we're doing in Russia and especially Iran now!
> Domain fronting is a technique for Internet censorship circumvention that uses different domain names in different communication layers of an HTTPS connection to discreetly connect to a different target domain than is discernable to third parties monitoring the requests and connections.
https://en.wikipedia.org/wiki/Domain_fronting
Cool, so we are bowing down further to oppressive regimes now.