• 0 Posts
  • 16 Comments
Joined 4 months ago
cake
Cake day: March 9th, 2024

help-circle
  • Funny, we get more complaints about DuckDuckGo browser than anything else, and that’s one of the few we don’t test on. I know this because I make it a point to have someone from CS tell me about consistent pain points users are having. I wonder how many complaints about Firefox not working your customer service team is getting daily and you just don’t hear about it because they’ve been told to tell users “just say Firefox isn’t a supported browser and to try installing Chrome.”

    You should ask someone in CS. Whichever agent bullshits the least (not the manager) - you might learn something.

    Almost 3/10 people accessing your sites are using Firefox. All those “images not loading right or whatever” are probably blatant to them, making them think “wow, what an absolute shit website.”

    3 out of 10.




  • Sucks that I have to preface but people can be jumpy here. This is genuine curiosity, I’m actually asking, because it’s really probably something I should already know. Can you explain the nuance to me please?


    My understanding, speaking mostly of apps/websites, I know jobs can be much different:

    Most places have the first factor as a password.

    First factor (or “login”) = username+password pair.

    For the longest time that was all there was, “your login” was just a login, which meant a username and password combination. Then 2FA/MFA (“2 factor authentication / multi-factor authentication”) came along in the form of username+password combo plus SMS/email/Google Authenticator/Yubikey/etc to verify as the 2nd form of authentication. You can have 3FA 4FA 5FA whatever if you want and if it’s supported by the app/website. So 2FA is MFA, but MFA is not necessarily 2FA.

    I know jobs can be set up a lot differently.



  • At that point its out of your hands. Once the users have fully decided only one browser is all they’re going to use, because most websites only develop for that browser (gee sound familiar?) then whoever owns that browser owns the web. That’s the point people are trying to get you to understand and you aren’t getting.

    its not like we wont notice a shift like that. It would be very easy to adapt

    This has has happened before. It took over a decade to get people to start using other browsers. Your little company can’t wave a magic wand and make the entire internet ecosystem shift, even though you were part of the cause.

    Firefox market share is going up. But because small vendors not testing on it, it’s preventing its adoption. So you’re letting Google own the web.









  • Friendly reminder that Bluetooth has a larger network stack than Wi-Fi. Much more code, much larger available attack base. There have been many numerous Bluetooth vulnerabilities that allow remote code execution or theft of files.

    This is truly becoming a surveillance state, in no way that can be debated. That want to be able to access everyone’s innermost thoughts (texts, notes, recordings, calendars, contacts, photos, you get it) without any chance of someone being able to protect against it.

    Reminder that Google was the 2nd or 3rd company to commit to NSA’s PRISM program of feeding American’s data for future analysis.


  • What guarantees do you have that Malus doesn’t copy your key to their cloud?

    I remember when I used a Samsung Galaxy as by daily driver a couple years back. I enabled full disk encryption and thought okay great, now that’s done. I noticed a very small, brief popup on my screen that lasted a few seconds, and it was a notice that my key had been sent to Samsung servers. Apparently you have to disable that option that’s hurried deep in the settings somewhere no one would think to look, and change your password again. If I hadn’t caught that brief notification at the bottom of the screen (not the normal location for notifications), I’d never have known.

    The encryption password is also a max of 15 characters.