Sorry I’m late to the party. I wanted to open a topic about this for a bit more de-nerdified perspective than the live-stream, but missed the switch-over. So I’ll try to not make it my longest post yet.
There are three main gripes that I’ve seen come up in several threads:
- Added Friction
- Anonymity
- Why Safety for a Porn Site?
Added Friction
I’m not gonna lie to you. If you haven’t used a password manager/passkey store/authenticator, then yes, you’ll encounter some initial friction. Once set up correctly though, it’ll be a breeze. Not only for this site, but for others. I myself have KeepassXC running as both a passkey store, as well as an authenticator that auto-fills the 6 figures for the 2FA. Was super easy, since I already use it for different stuff. @GFree : I think this solution could be something for you, since it’s only running on your PC.
Setting it up for the first time, can be a bit of a hassle for the non-technically versed though, since there are a few settings that must be set, for it to work this way - and of course there’s a lot of vocabulary that could be misunderstood. So if Free(dom) And Open Source isn’t a priority for you, you might wanna go with the other recommendations like the Authenticator from the Chrome Web Store or a passkey store (passkey’s are even easier and more secure, but 2FA has to be activated first, from what I understand).
Anonymity
There have been concerns that using an authenticator could link the real identity to ES. Which is an understandable issue. The good news is, that this does not have to be the case.
My KeepassXC database is local to my device and sits there encrypted, not even for my OS to read or even OneDrive or some other cloud provider, if I put it there. Once I decrypt it (through a password, keyfile, physical key, whatever), then the browser extension can ask it whether there are credentials for a specific URL, so I can choose which one to use. For that it needs to store the URL of the websites within the database. Since it is a local database and the source is open (anyone can see the program code), we know that that info stays where it belongs and isn’t matched with the rest of my data by or for a 3rd party.
Of course it could be that other developers like Microsoft/Google/Apple/Bitwarden do the same. But we can’t say for sure, because the code is often proprietary. So we need to trust them… which is why I run KeepassXC.
It is of course possible to run multiple accounts of password managers to separate the data and make it more difficult for companies to aggregate the metadata, but I don’t think that’s very practical. The big plus of these solutions though, is that the sync of the data over devices is already built in and usually the GUI is more user friendly. So it’s a judgement call for each individual.
Why Protect My Porn?
This one could be fleshed out and discussed ad infinitum. I’d like to make three points:
My personal view is that if we want to protect the anonymity of all the users and limit their traceability, then we have to protect the community as a whole from illegitimate access. There are some very sly people out there who could do damage. And this makes it more difficult.
The, who has a unique password on this site, that they don’t reuse on another site throw the first stone.
It is a common occurrence. And when your credentials leak from one place, bots test them out in other places. Using 2FA and this isn’t a problem anymore. That does not mean, that we should be using the same password everywhere though. Since we now have a password manager, we can use absolutely abominably to remember passwords and save them. Or create a memorable strong password if you like.
Concerning the throwaway email trick: you’re leaving more traces and metadata than you think. Except of course if you are using a separate trow-away account for every website and never integrate it into Outlook, Gmail or whatever Email software and have your cache and cookies perpetually cleaned/separated. Not touching the OS and other apps for brevity.
Second this. The internet is changing. For better and/or for worse. So we best be ready for it.
IIRC that might be because of the Discourse implementation issue.
There’s a “Enter manually” text underneath the QR, which shows you the key you can copy into your PC run authenticator.

