• 1 Post
  • 29 Comments
Joined 2 years ago
cake
Cake day: June 20th, 2023

help-circle





  • I get why 2FA is adopted so widely: companies need to cover they asses. Even if you don’t care if a hacker gets ahold of your password for a flash game website, that password leak could cause issues later on, and opens the website up to responsibility.

    What really bothers me more, is that 2FA is relying so heavily on phone numbers, which is an extremely flawed security system. At least some of the larger companies are open to using authenticator apps, or sharing the private key for storing in a database. But so many websites do 2FA by “requiring a phone number”, which just puts a lot of security responsibility on the phone carrier now. The user doesn’t really gain any extra responsibility for having good opsec, because phone companies fuck up all the time and assign phone numbers to new sim cards all the time, often on concerningly small amounts of information






  • I relate to this style more than the other comments in this thread, this seems more typical of a large company.

    You need to define clear needs out of your request: start with your end goal, the processes you need, the mechanical details of the processes you need to write, how much detail you are comfortable with, and the format in which you want it . and take all of that to the senior or director level of whatever department manages those systems. They may or may not know the exact information you need, but it should be their job to delegate and translate the request such that their reports can collate what you need in the form that you need it. And because it’s the director delegating, the engineers have inherent CYA and will be a lot more comfortable giving you what you need.

    Unfortunately this adds to the bureaucracy, but it really is the most effictive way of translating business needs to engineering needs. It’s not a straightforward process, and accurately defining the steps that need to happen for a job to get done, takes someone with a lot of experience and training.

    If you’re in a startup or smaller company, then I think the other comments that prioritize asking and listing to what the engineers recommend, is the best approach.









  • I like /all too, just to be clear. But sometimes I’d like to browse the equivalent of /all, just without politics. Sometimes it’s a little much and the feed could be 70%+ posts about the US election

    Plus, some instances seem to have a certain “style” to them. I feel like it would be cool if there was some currated feeds that instances presented, that include content across multiple instances that fit that “style”. Would just be an easier way to explore those niche communities. It would also kinda solve the issue with having fractured communities for the same topic across multiple instances