Punch nazis, trebuchet TERFs.

I am building Voyager, a client for lemmy!


I mainly pose under @aeharding@vger.social now.

  • 3 Posts
  • 98 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle






  • I made a purchase on a sketchy site (during Covid when things were hard to find). A day or so later, some unauthorized transactions were made on my card. “Bank” called from actual number of my bank, to verify if I actually made the transactions. provided some of my personal information, transaction amount etc then asked to verify ssn. It was very convincing.

    Luckily I refused because I know anyone can call you claiming to be any number, and I didn’t give out any info, and said I would call back that number (my bank).

    Bank had no knowledge of a call.

    15 minutes later, get real fraud department call from my bank. They just wanted to know if it was fraud or not and didn’t ask for any other info.

    Moral of the story: if someone calls you, never give out personal info. Tell them you will call back if needed.









  • There are absolutely reasons where a native app is worth it - I just don’t think building your own backend or not factors into that decision much.

    Maybe the point you are trying to make, is when you have enough resources/large enough company, having duplicate teams for each native app isn’t that big of a deal? I agree financially, although is is harder to technically coordinate two teams with dual releases and implementing features twice, with twice the bugs, and it slows things down. (Maybe not a big deal to Bitwarden - their app featureset may be quite stable, IDK)

    (Disclaimer - I’ve been on teams building kotlin/swift apps and also cross platform apps professionally, so this is my firsthand anecdotal experience.)