4,405 karma · joined October 15, 2013
Ignoring ESNI will probably work fine for a good length of time. If pornhub implements it or something I'd probably have to revisit. Or, since I control the clients I might disable it in their browsers.
If enough people bark up the filter vendor's tree I'm sure they'll add a checkbox to drop esni traffic. They added one for QUIC recently.
You might like Spam Nation: https://amzn.com/dp/B00L5QGBL0/
[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.SecurityProtocolType]::Tls12
At my org (a school) we used to disallow charging our students' laptops in class. We did that for about three years. During that time, it was not uncommon for a battery to fail in the first year, with most failing after two. Since we started allowing charging, most batteries stay above failure threshold the students' whole four years here. My hypothesis has been that students charging opportunistically avoid the deep discharge cycles that are very bad for batteries.
- It started with batteries, which are awesome for the price
- I bought a throwaway comforter + sheets to use for couch-sharing with the dog and they're my favorite set now. Better than my Ikea set which cost 2x as much.
I could go on but for random items the Amazon brand is often pretty decent.
I've stopped leaving Amazon reviews. Recently I was bored and went through a few bits of network equipment and PC hardware I purchased and reviewed a few of them. 3/6 of the reviews were rejected for being against community guidelines with no reason provided. Even after reading the guidelines it's not clear why they were rejected. I put in effort to describe why something got its rating from me. For example, I discussed the strengths/weaknesses the network equipment. From now on I might leave a star rating, but I'm not wasting time to get a review accepted. I'll leave that to the shills.
> By offering applications access to libcurl's own URL parser, we hope to tighten a problematic vulnerable area for applications where the URL parser library would believe one thing and libcurl another. This could and has sometimes lead to security problems. (See for example Exploiting URL Parser in Trending Programming Languages! by Orange Tsai)
Looking at their blog[1] they seem to do releases very infrequently. 3.5 was released 2014-11-20. 3.6 was released 2015-06-15. 3.7 was released 2016-12-12. It seems like each release is about a year and a half apart. By that cycle we're about due for one.