• 1 Post
  • 99 Comments
Joined 1 year ago
cake
Cake day: July 16th, 2023

help-circle


  • So what happens when a platform grows and that threshold is reached one day? Force everyone to de-anonymize and potentially reveal sensitive information about themselves or abandon their account?

    There’s just no good way to force only some to de-anonymize without running into problems.

    While I believe in the right to online anonymity, I also don’t think that de-anonymization would even work, when I see the same garbage being posted in places that enforce real names. It just doesn’t seem like a detractor to those types of people.

    Instead, I’d rather want to see harsher punishments for big sites failing to moderate their content. I’d also take a look at these personalized “recommendation” engine and maybe ban them altogether. (Bonus points if it also affects personalized ads.)



  • I’d be more concerned as well if this would be an over-night change, but I’d say that the rollout is slow and gradual enough that giving it more time would just lead to more procrastination instead, rather than finding solutions. Particularly for those following the news, which all sysadmins should, the reduction in certificate lifespan over time has been going on for a while now with a clear goal of automation becoming the only viable path forward.

    I’ll also go out on a limb and make a guess that a not insignificant amount of people only think that their “special” case can’t be automated. I wouldn’t even be surprised if many of those could be solved by a bog-standard reverse-proxy setup.


  • Part of this might be my general disdain towards sysadmins who don’t know the first thing about technology and security, but I can’t help but notice that article is weirdly biased:

    Over the past couple of days, these unsung heroes who keep the internet up and running flocked to Reddit to bemoan their soon-to-be increasing workload.

    Kind of weird to praise random Reddit users who might or might not actually sysadmins that much for not keeping up with the news, or put any kind of importance onto Reddit comments in the first place.

    Personally, I’m much more partial to the opinions of actual security researchers and hope this passes. All publicly used services should use automated renewals with short lifespans. If this isn’t possible for internal devices some weird reason, that’s what private CAs are for.




  • I can’t find a way to dodge the paywall to that article, but the short blurb I was able to translate, makes it sound like my guess is at least part of the problem:

    As long as the sun shines the most, Skåne benefits from cheap solar energy from our neighboring countries. As soon as solar energy declines, the price of electricity rises throughout Southern Sweden. The poor Swedish transmission capacity means that we cannot benefit from cheap northern hydropower.

    That said, I do agree that Germany should’ve long been split into two zones, at least until transmission capacity catches up. But alas, most people in Germany don’t even recognize that the lack of transmission capacities as the source of the problem and rather blame it on us importing expensive electricity from France.

    It’s actually those parallels why I’m so distrustful: I’m far from an expert on the topic, quite the opposite if anything, but given how many people, even politicians, put out even dumber claims much more confidently, I’m always wary about such statements.


  • Based on the article, it seems more like that’s more of a problem of south Sweden just having a big energy deficit in general, not as a result of imports/exports or the actions of Germany particular.

    The way I understand it, it’s more that a new connection just wouldn’t make sense because Germany already has a problem from moving energy from its own offshore wind parks in the north to the south.

    I couldn’t find a good article explaining the current energy situation in south Sweden, but looking at ElectrityMaps, I’d guess that part of the problem is that there’s a huge amount of nuclear energy being produced in South Central Sweden, saturating the grid and making the transfer of cheap hydro and wind energy from the northern Zones difficult.








  • Depends a bit on the clients.

    • KeePass: Will ask you if you want to synchronize/overwrite/discard the database when saving.
    • KeePassXC: Will autoreload the database in the background, so merge conflicts shouldn’t happen in the first place. Otherwise there’s ‘Merge database’ in the menu.
    • KeePass2Android: So I mixed up the names and this is the client I actually use. This one does all changes to an internal copy of the database that is then synchronized on request.
    • KeePassDX: As far as I can see it also has a mechanism similar too KeePass2Android.

    Assuming you only have one desktop and mobile client you should never run into any issues. If you do have multiple KeePassXC clients it’s all fine as well assuming Syncthing always has another client it can sync with.




  • Technically you can do everything through email, because everything online can be represented as text. Doesn’t mean you should.

    PRs also aren’t just a simple back and forth anymore: Tagging, Assignees, inline reviews, CI with checks, progress tracking, and yes, reactions. Sure, you can kinda hack all of that into a mailing list but at that point it’s becoming really clunky and abuses email even more for something it was never meant to handle. Having a purpose-built interface for that is just so much nicer.