0 Followers
0 Following
1 Posts
Can still request it without an arr stack - it just won’t download it :) Can then buy the Blu Rays and rip. Also jellyseer has a watchlist you can add stuff to to keep track
That’s one smart dog. Reading a book while running around. Dogs are awesome.
The partial headline certainly does suggest they are bragging about their wealth. The “only” is on their debt (Mortgage). If it were about not having enough your would imagine it would be written as “and I STILL owe xxx on my house” and “only have xx in savings”

Will this not just be taken to mean X (as the app maintainer) needs to have the ability to block users it considers to be abusive from the app.

I don’t think this rule is specifying what an individual user of the app must be able to do.

Elon Musk on Twitter

“And soon we shall bid adieu to the twitter brand and, gradually, all the birds”

Twitter

From a user interface perspective, it’s a pretty bad implementation. Really not dissing the devs here, as they have been doing an awesome job and and getting so much done in a short space of time with the massive new user load.

There is a reason that it is common practice to force a user to verify that they have TOTP (2fa) set up correctly by requiring them to enter the current 6 digit number to enable it. Otherwise it’s way too easy for users to lock themselves out.

Thanks. Quite odd, as I was getting no prompt. Uninstalling and reinstalling solved it though.
I’m not locked out, and can login via the web or with Mlem. I was just wondering if Memmy supported TOTP, or if I’d have to disable it for now if I want to continue using Memmy.

Does Memmy support 2fa (TOTP)

https://lemmy.world/post/1435988

Does Memmy support 2fa (TOTP) - Lemmy.world

Does Memmy support the 2fa implementation currently available on lemmy instances? I enabled it after the latest security issue, but now I cannot seem to log in. When I try I get a error that need to provide the TOTP code. I don’t see any open (or closed) GitHub issues referencing it.

Seems it was an AndroidTV update that caused it. The manufacturer pushed another update to the TV this evening that has fixed it. So nothing to do with the tvOS update at all.

Thanks for your help.