Cancelled my Netflix account when they announced the password sharing crackdown (even though I wasn’t password sharing), and recently cancelled my Spotify family account when they increased the price.

Movies from the MCU: https://editorial.rottentomatoes.com/guide/marvel-movies-in-order/

the security team found out that only 93 Authy users out of 75 million were affected

Also this was a social engineering attack and if you’re syncing your 2fa seeds then you should be encrypting them with a secret. Cracking that should take years if not more.

I don’t think it’s just a Firefox problem. I have the same issue in Safari since the 0.18 update.

Maybe try using https://wefwef.app to connect to your lemmy instance.

We’ve pretty much settled on Lemmings

Just google doing what google does

Dragonite

If you enable location history, google maps will do this

I so want to see this happen but I feel like there will be so many rules and padding that it’ll end up being a borefest.

Cage match, anything goes! It’ll bring in huge audiences.

In your proposal, who would run these hub servers?

Same in NZ. We have a high minimum wage and already pay pretty high prices for everything.

Some Eftpos/Credit card terminals will even ask if you want to tip when you make a payment. Such an awkward moment pressing “No” right in front of the person serving you.

I’m not the dev. @gkd@lemmy.world deserves all the credit. He’s amazing.

There’s a “Buy me a coffee” link at the bottom of the github page: https://github.com/gkasdorf/memmy

memmy@lemmy.ml is the community.

@gkd@lemmy.world the lead dev is browsing this post so I’m sure he’s seeing everyone’s feedback.

As far as I know kbin doesn’t have API access enabled at the moment. They’re still trying to finalise how they do it. This means that apps can’t communicate with it just yet.

FYI, I don’t think kbin has enabled API access yet which is why apps won’t work with it

I was having such a good experience with Memmy I thought others should know about it too. The daily improvements have been amazing, keep up the great work!

I’m not the dev but I think that’s the intention based on the readme on GitHub.

It’s written in Expo/React Native which means it’ll be easier to support both iOS and Android.

If passwords are hashed on the client side and sent to the server to authenticate, then all an attacker would need is the password hash and not the original password to authenticate. So it could protect your original password but not your account.

Other than Mlem, there are others currently under development too. I’m excitedly following memmy by @gkd@lemmy.ml