• 0 Posts
  • 14 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle





  • No testing a server side http-to-https upgrade/redirect without reconfiguring your browser. This seems like an unnecessary and bad idea.

    This could be easily done better by promoting such server-side configurations as a default.

    I mean, why should the browser attempt to correct inappropriately configured servers? Shouldn’t they rather be making PRs to NGINX/Apache/CAs or whatever?

    Also: can’t this be exploited to spoof an unavailable HTTPS and coerce an unencrypted connection?


  • Imagine you want to test your redirect from 80 to 443 when setting up your webserver.

    While I think for the normal user this enhances security by defaulting to HTTPS, however this makes no sense for a browser. This should be enforced server side, the browser is for browsing, i.e. viewing. Not controlling and competing with the server software for competency.

    Chromium is really leaning into bad code practice with the disregard for “separation of concerns”.








  • It’s starting to look like a pattern. An ugly, one I might add. Slowly making everything less inclusive, less accessible… Until it’s some radical right-wing brown swamp.

    I mean, it’s “only” social media platforms, but pretty much the playbook - “oh that… that’s an accidental side effect… don’t worry!” until key institutions are undermined and then switch to full on fascist regime.

    All not because of beliefs this would be best for humanity as a whole, but being in love with the idea of being the one who calls the shots. King of the hill made of feces.

    The lack of vision for an enlightened role of humanity in the universe disgusts me.

    Sorry for the rant, I might have gone from 0 to 100 pretty quick there, lol. Just pissed at a lot of these kinds of regressive developments lately.