• 0 Posts
  • 76 Comments
Joined 3 years ago
cake
Cake day: June 20th, 2023

help-circle
  • I would hope that in 25-50 years from now, gendered locker rooms and bathrooms will be a thing of the past, and slowly replaced with individual unisex stalls. Maybe for high volume places (like a stadium or airport) there will still be bathrooms with a wall of urinals, but those will probably not be labeled “men’s” and will just be urinals.






  • I’ve never seen any interview as invasive as this, but i think simple take home assignments are useful to weed out people who don’t have basic skills for the role, can’t read instructions clearly, and/or don’t care enough for the role. It avoids me spending 30 minutes to an hour interviewing them to just reject them.

    The roles i interview for are mid level devops based, and we’ve found that the best way to do this is to provide the candidate a simple git repo with 2 branches, which can’t be merged due to a merge conflict of two text files; no coding required. Just asking the candidate to resolve the merge conflict and write a README with the steps taken is enough to have more than half of the candidates unable to complete the task. If we interviewed all those candidates first, and then had to reject them, it would probably be 1 full working day per month in aggregate that would be utterly wasted.







  • The standard is called TOTP and Google became synonymous with it because they pushed it in the late 2000s for Gmail and have a large user base. Other sites did have systems beforehand, like Paypay which had a dedicated fob, but that was not widely used. Gmail was likely most people’s first experience with MFA and Google pushed their own Authenticator app (and didn’t really advertise that others could be used). As other sites got on board, it was easier to tell people to use the app they use for google to get their code, since you could assume people had the app.

    Basically that made a situation where people who had a different TOTP app knew their app would work with “Google Authenticator” but for those without an app or using Google Authenticator, they were likely unaware of the interoperability and standards behind the mechanisms.




  • I would assume they do something, but I have not used any of these services myself. My feeling is they’re kinda like the tax filing software, they might be useful tools, but their whole business relies on things being unnecessarily burdensome for the average person. I wouldn’t be surprised if it came out that these companies lobby for lax regulations for data brokers, just enough for their product to be useful but not enough to put them out of business.

    Overall, I feel if I freeze my credit, and occasionally google my name for data broker websites, going through the opt-out on the ones, I think that’s enough to put me above 90% of the US population, and then it’s just a numbers game of not getting scammed.




  • bamboo@lemmy.blahaj.zonetoMemes@lemmy.mlWe don't even care anymore
    link
    fedilink
    English
    arrow-up
    48
    arrow-down
    1
    ·
    3 months ago

    None of your SMS data is encrypted anyway, all of it can be obtained by your cell provider or the recipients cell provider. TBH Google is probably the least of your problems with regard to SMS safety. I had a friend who sent an invite code to some gambling website to her husband, so she could get promo credit, and AT&T flagged her text as spam and blocker her across their whole network for a week or annoying period of time.