DefederateLemmyMl

  • Gen𝕏
  • Engineer ⚙
  • Techie 💻
  • Self hoster 🖧
  • Linux user 🐧
  • Ukraine supporter 🇺🇦
  • Pro science 💉
  • Dutch speaker
  • 1 Post
  • 115 Comments
Joined 2 years ago
cake
Cake day: August 8th, 2023

help-circle





  • You obviously didn’t know how it works if I had to explain it was already possible.

    If you read my comment properly, you’ll see that I wrote: “I know TLS termination and interception and recertifying with custom certificates is a thing”

    And it isn’t “madness"

    Yes it is. TLS interception should never be normalized because it breaks the chain of trust upon which TLS is based. It can be useful in some situations, like the fortigate firewall where you control the certificate, but ISPs nor the government should be trusted to wield this power over virtually the whole country. It is a very slippery slope.

    I am not aware of any mobile device that prevents you installing a new root CA.

    On Android, apps can’t install their own root CA. The user has to manually download it, then jump through a bunch of hoops and deeply nested menus to install it and in the process ignore all the scary warnings that their communication may be intercepted if they install and trust this certificate, and (at least on Pixel phones) they get a permanent warning in their notification tray that someone may be eavesdropping on them. Which is correct.

    It is a vastly better option than onerously demanding adults provide their identity to random and potentially adult themed websites where they could be victims of identity theft or extortion

    I’m strongly against government mandated age gates myself, but you’re objecting for the wrong reasons. You’re not providing your identity to the adult website. You’re providing it to the third party identity verifier, who then certifies to the adult website that you are an adult without passing on your actual identity. Keep this in mind when you’re arguing against it, because pro-age-gater puritans can use it to undermine your argument.

    I object to it first and foremost on principle. I shouldn’t have to request permission from a third party or the government to do perfectly normal legal adult things in the privacy of my own home.

    Secondly, there is still a privacy problem at the “identity verifier”. They may swear up and down that they do not store my identity data, but there is no way to prove that one way or another so I cannot trust that my data can’t be leaked through them.

    Thirdly, when viewing adult content, I don’t want there to be any association between my real identity and the adult content whatsoever, even through a third party, and I don’t want there to be anything that uniquely identifies me.

    Finally, I object to the (re)demonization of all things sexual in our societies. We seem to be backsliding into puritanism under the guise of protecting the children, while we’re doing nothing to protect them from real actually harmful online things that are damaging the younger generations beyond repair.

    I have a Gen Z stepson, and all the ways in which he is fucked up by the online world (no attention span, permanent online-ness, no real world friends, always seeking instant gratification, unrealistic expectations about life, an overly materialistic worldview, plenty of manosphere bullshit, … ) have precious little do do with viewing porn.


  • I know how it works, so spare me the explanation. It’s not that as easy as you make it out to be. OS and browser companies are actively fighthing “rogue” root CAs and making it harder and harder to use custom CAs, especially on mobile devices.

    And for good reason, because by accepting a rogue root CA that’s not your own, you’re basically undermining the whole trust system that SSL is based on and surrendering all your online privacy and security to the government and your ISP. Whoever has control over that custom root CA has the keys to your online life.

    Rolling such a system out countrywide is utter madness.


  • That’s a problem is for ISPs and content providers to figure out

    No, there are very good technical reasons why this approach can’t work.

    ISPs … deep packet inspection

    There is no deep packet inspection on properly encrypted TLS connections. I know TLS termination and interception and recertifying with custom certificates is a thing, but even if it were feasible to implement this on millions of client computers that you don’t own, it is an absolutely god awful idea for a million reasons and much worse for privacy and security than the age-gate problem you’re trying to work around.










  • The problem is not so much “paying for stuff without payment processors”. On an individual level, that can fairly easily be achieved.

    The problem is the chilling effect that the puritanical positions of these payment processors have on the creation of art. What are you going to do with your crypto if the game or art you wanted to buy gets self-censored for “compliance” or simply isn’t created anymore?




  • Write speeds on SMR drives start to stagnate after mere gigabytes written, not after terabytes. As soon as the CMR cache is full, you’re fucked, and it stagnates to utterly unusable speeds as it’s desperately trying to balance writing out blocks to the persistent area of the disk and accepting new incoming writes. I have 25 year old consumer level IDE drives that perform better than an SMR drive in this thrashing state.

    Also, I often use hard drives as a temporary holding area for stuff that I’m transferring around for one reason or another and that absolutely sucks if an operation that normally takes an hour or two is suddenly becoming a multi-day endeavour tying up my computing resources. I was burned once when Seagate submarined SMR drives into the Barracuda line, and I got a drive that was absolutely unfit for purpose. Never again.