• 0 Posts
  • 232 Comments
Joined 1 year ago
cake
Cake day: July 9th, 2023

  • Fines and taxes are incentives. Companies will do whatever’s cheapest, so you can make the good thing cheaper, or the bad thing more expensive. Both will have a similar effect, it’s just a question of where the margins are.
    If a company is selling something at-cost and gets taxed, then they’ll have to raise prices for the consumer, but if they’re getting a stimulus from the government it gets covered by tax payers. Which one ends up being the right choice depends on the product and company in question.









  • I already had a server running docker, so throwing a few more containers in was trivial. There’s a docker-compose.yml published in the lemmy repo.

    Since my server was already running and had free space, it was literally free, but if you’re starting from scratch there’s more to consider.

    I’ve been self-hosting for over a year now, and the storage does add up. The postgres DB is 11GB, and pictrs service is getting bigger at 29GB. Between all the different services, it can eat up a decent bit of CPU. My (admittedly 10 year old CPU) sits at a load average of 1.9, so you’ll probably want 3 or 4 cores minimum. And based on my stats, 4GB of ram should be just enough to keep everything loaded.




  • xthexdertoTechnology@lemmy.worldWhat the hell Proton!English
    arrow-up
    9
    arrow-down
    0
    ·
    10 days ago
    link
    fedilink

    The ISP will always know the IP you’re connecting to. Encrypted DNS might get you slightly more privacy for sites using shared IPs like with Cloudflare. But in a lot of cases, there’s only 1 website per IP, so the ISP still knows where you’re browsing. A VPN solves this by routing all traffic through the VPNs IP first. But you can still be tracked just the same by the VPN and to an extent, the VPNs ISP.





  • Storing credit card data has its own set of strict security rules that need to be followed. It’s also the credit card company’s problem, not yours, as long as you dispute any fraudulent charges early enough.

    I’m coming at this from the perspective of a developer. A user can always use a longer password (and you should), but it’s technically possible to make an 8 character password secure, thus the NIST recommend minimum.



  • xthexdertoTechnology@lemmy.worldNIST proposes barring some of the most nonsensical password rulesEnglish
    arrow-up
    2
    arrow-down
    0
    ·
    20 days ago
    edit-2
    20 days ago
    link
    fedilink

    Newer password hashing algorithms have ways of combatting this. For example, argon2 will use a large amount of memory and CPU and can be tuned for execution time. So theoretically you could configure it to take 0.5 seconds per hash calculation and use 1 GB or more of ram. That’s going to be extremely difficult to bruteforce 8 characters.

    The trade-off is it will take a second or two to login each time, but if you’ve got some secondary pin system in place for frequent reauthentication, it can be a pretty good setup.

    Another disadvantage is the algorithm effectively gets less secure the less powerful your local device is. Calculating that same 0.5s hash on a beefy server vs your phone could make it take way longer or even impossible without enough ram.