• 0 Posts
  • 27 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle





  • Probably depends on the work and your endurance level. I used to do 12 hour warehouse work Saturday/Sunday over summer vacation in college while I played video games and hung out with friends the rest of the week. It felt freaking amazing. Three days in a row might’ve been pushing it, especially in my later 30s.

    But considering I’ve done intense development work for 12 hour sessions over 3-5 days, having had 4 days off instead of 2 would have certainly delayed or prevented my inevitable crash of burnout.





  • That’s correct, let’s say a database was breached and the hacker has every user and their password hashes. They can login with testuser@email.com with password “password123” and see if the generated hash matches any other user’s password hash. If so, they might be able to hack many accounts with the same password or even reverse engineer and decrypt every other password.

    Developers can make the hash more secure by adding arbitrary characters to the password (aka a salt), and this becomes the site’s “authentication algorithm”. But if the hashes are stolen, it may be a matter of time before the algorithm is figured out, which leads to updates, which leads to your pre-existing hash no longer matching.


  • There could be many reasons they don’t prompt you to change: they meant to send an email but your notification preferences disallowed it, they sent an email and you missed it, they wanted to keep it quiet, they forgot to add the message and ux flow to change password, or they’re incompetent and didn’t know they needed to do that.

    The Epic thing I’ve never seen before but that’s definitely incompetence and/or a very weird bug that just slipped past them.


  • If there were a data breach where a hacker could figure out the encryption algorithm, you don’t want users to reuse an older password because those older passwords could’ve already been cracked.

    By the way, this is why you should also never use the same password for every site. If one of your passwords is leaked and linked to a similar username or email, everything is vulnerable. I’ve had this happen before (the Target breach). After that I started using SSO exclusively, with a random 16 char password manager if SSO isn’t an option (crossing my fingers that bitwarden doesn’t get hacked like LastPass)









  • tillary@sh.itjust.workstoAndroid@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    72
    arrow-down
    1
    ·
    1 year ago

    USA mobile carriers have been charging for tethering since devices implemented the tethering feature. Android enforced it through carrier firmware. I don’t remember how apple enforced it.

    I remember having to jailbreak all my iPhones so I could get it for free. As iOS started feeling more limited, I bought a galaxy phone from Europe because the international phones didn’t have the carrier firmware.

    Then T-Mobile was the first big carrier to offer free tethering - I switched to them from AT&T. And now more carriers are offering free tethering because it’s losing them customers probably.