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

help-circle
  • Proton had a reputation for being the good guy. In the span of a month, we saw them bend the knee, flip flop and throw shade at competition; all while pretending to be the hero. We essentially have to trust them with our data and they are showing signs that they are willing to act against that trust with worrisome agendas and biases. It’s not a good look, and since this marketing to users key issues, it’s going to cause some responses.


  • It all started with PAL: https://en.wikipedia.org/wiki/PAL the short version is that old cameras were tuned to work with the electromagnetic frequency, your camera either worked in Europe or in the US. This effected the frame rate of the end video (4%) and meant that tvs, video players and consoles ran at a different frame rate which lead to 2 standards NTSC and SECAM.

    As trade expanded publishers created trade routes and business partnerships that created a patterns of distribution. Later when we resolved those 2 standards with modern technology, we are still were using those methods to get the physical copies to the stores and those same stores are still handling digital distribution, using the same laws and regulations. It might seem simple to click download, but that’s built on a monolith of history and automation to deliver a good user experience.

    To actually get rid of it, I’m not a lawyer but I imagine we have internal trade treaties to visit? I don’t think it’s legal to sell PAL versions outside of their region unless you are also doing business there. I know Japanese pokemon games were hard to buy as a kid. Disclaimer: I know tech stuff.











  • Mostly customer provided certs, high end clients make all kinds of stupid requests like the aforementioned man-in-the-middle chain sniffers, clients that refuse DNS validation, clients that require alternate domains to be updated regularly. Management is fine for mywebsite.com, but how are you solving an EV on the spoofed root prod domain, with an sso cert chain for lower environments on internal traffic that is originally provided by a client? And do you want the cs reps emailing each other your root cert and (mistakingly) the key? I’ve been given since SCARY keys by clueless support engineers. I don’t want to do this every 3 months.


  • As someone who creates custom domain name applications, FUCK THEM WITH A PINEAPPLE SPIKY SIDE FIRST. This problem is on par with timezones for needless complexity and communication disasters. Companys and advertisers are now adding man in the middle certs for additional data collection/visibility. If the ciphers not cracked, changing the certs exposes significantly more failure, than letting one get a little stale.
    Sysadmin used slam! It’s super effective!