Avatar

darrsil

darrsil@lemmy.world
Joined
5 posts • 30 comments
Direct message

If there is one thing Google is committed to, it’s being unstabally committed to all of its products.

permalink
report
reply

Probably because the cat is already out of the bag there. Hard to reign them back in and they’d have tons of bad press if they do that.

permalink
report
parent
reply

For exactly the reasons you state - Google doesn’t want ad blockers in their browser.

permalink
report
reply

TWiT is definitely in trouble. The last time I listened to them, one of their advertisements was for… doing advertisements on TWiT. They were also pushing their subscription every chance they got.

Their whole network comes off as a bunch of boomers complaining about technology. I don’t think they’ll be around much longer.

permalink
report
parent
reply

I’m sure they have all hands on deck trying to recover the site, but yeah some communication from the admins would be appreciated.

permalink
report
reply

Just be careful with it. It doesn’t confirm that your code is correct before enabling it, and the way it gets set up doesn’t work on a number of different authenticators (such as Authy).

Best way to do it is to enable it in settings add it to your app, and then while the settings screen is still open, open an incognito tab and try to log in.

permalink
report
parent
reply

Just got another redirect, it’s definitely still happening.

permalink
report
parent
reply

It may be an isolated incident, but it would have been avoided had Lemmy confirmed the 2FA code before enabling it on the account. Like standard practice.

Besides, this issue refutes your entire premise - that automated 2FA set up is flawless.

See this thread: https://lemmy.eus/post/190738

It’s an issue with many different authenticators, and it’s an issue with the way Lemmy sets up its 2FA and doesn’t do a confirmation afterwards. This needs to be fixed.

permalink
report
parent
reply

That doesn’t address the issue. Yeah, that makes setting up a code easy on your device - but the code still should be verified and confirmed as working by the website before 2FA is enabled on the account.

Case in point: I used your revered “automated 2FA key implementation” for Lemmy in Authy. It set up the account in my Authy list, and 2FA was supposed to be working. I opened an icognito tab, went to log in, put in my 2FA code and… it didn’t work.

Luckily, I still had my settings open in my other window and was able to deactivate 2FA.

The code should be tested and confirmed by the site before it’s enabled. Otherwise you can easily get locked out of your account. This is standard practice when implementing 2FA on websites.

permalink
report
parent
reply