The TOTP feature in Bitwarden works, if you paste in the whole otpauth:// URI to Bitwarden’s Authenticator Key (TOTP) field. The URL specifies that the hashing algorithm should be SHA256. If you just import the secret= value into Authy, it probably defaults to using the SHA-1 algorithm, which may be why the codes generated by Authy don’t work.
SHA256 is more secure than SHA-1, which I guess is why Lemmy has chosen to use it for its 2FA feature.
It would have to be Gödel’s Incompleteness Theorem. Such a beautiful proof that shakes mathematics to its core.
The science communicator Veritasium made a nice video about it: https://youtu.be/HeQX2HjkcNo
I first learned about it in Douglas Hofstaedter’s masterpiece Gödel Escher Bach: An Eternal Golden Braid
He called Zuck a cuck?
Very good. I think a feature where a user can revoke all their cookie sessions is still worthwhile, and maybe I’ll look at raising a feature request for that, but it is good to know that cookies stolen during the recent hack have already been addressed.
It seems there is no way in Lemmy to invalidate all your session cookies? Without that, how can you secure an account which has a stolen session cookie?
Lenny is a national treasure, taking on the telemarketers and bringing them yo tears: https://www.kaspersky.com/blog/35c3-lenny-voice-chatbot/25275/
Presumably they mean that the CPU resources are over-provisioned, meaning that the virtual CPUs allocated to VMs have to share a smaller pool of physical CPUs. If the VMs have a lot of idle time, this can work well, but if your VM suddenly needs more CPU, the processes on your VM might need to wait for a physical CPU, as physical CPU cycles that would normally be available to you have been “stolen away” by processes running on other VMs.
Then change the title of the post to something open-ended like “How vulnerable is Lemmy to DDOS attacks?”. Taking out a major node which hosts many key communities is going to have an adverse impact.