That's a weird location to show information on who posted it. But if you really want to, you could make a user script that uses the current "(OP)" to put a big red X there.

Do you also consider the problems this can cause? I'm thinking of people losing access to their account when they lose their 2FA, or a false sense of security when the 2FA is on the same phone they use to access the forum.
Have you seen NLNico's post?

Nice one, Powerglove. You have given us an extra. And I also read that you are planning a 2FA for us. I hereby seize power from her late Royal Majesty Queen Elizabeth 11 as a Fool Member that I am  , and induct you into bitcointalk Hall of Fame with immediate effect. Thank you.

PowerGlove, I'm glad that your current idea can be enjoyed by all forum users without having to install anything. This should be the new normal for us where I can quickly find the OP for every reply in a thread, its really a good idea.

I'm thinking of a user security system as adopted by many exchanges. Binance has 5 2FA to protect users, which includes Google Authenticator, message authentication, email authentication, security key authentication, and biometric authentication. If the forum had one of these I think it would be great although actually some people can think about the negative effects.

I just noticed this feature has been added to the forum. Very cool addition. Seems like it’s been a while since anything has been implemented so it’s nice to know things are still being worked on. I don’t see any downside to this addition so it seems like a great decision to add it. Nice to see new things around here.

Yep, it came up in my first 2FA topic.

I've carefully considered what might have happened there and in order to maximize the chance of theymos accepting the work this time, I'm taking a different approach than NLNico. My attempt will be a patch (not a package) which allows for tighter integration and won't get in the way of implementing whatever feedback theymos might have. It will also not introduce any additional dependencies (written from scratch, no third-party code). Finally, it won't require JavaScript, which is important to me (and I'm guessing a few others).

It'll be a basic implementation of RFC 6238 (TOTP: Time-Based One-Time Password Algorithm). Nothing exotic, just a simple 6-digit code entered at login for those users that have enabled it.

The implementation is flexible enough for theymos to configure the specifics (hash algorithm, time step, digit count, synchronization window). The default values are set to maximize compatibility, so all the ordinary 2FA applications will work (e.g. Google Authenticator, Authy, FreeOTP, KeePassXC, WinAuth, etc.)

---

I've been through as much 2FA content as I could find on the forum and I'm trying to make sure that my implementation won't upset anyone or introduce new problems. I'm also mindful that theymos is unlikely to accept a patch that involves too much additional code (and therefore, new attack surface) so I'm keeping the patch as small and easy to review as I can.

I'll get into all the details when I post about it. We probably shouldn't derail this thread with prolonged 2FA discussion.

Yes, getting an avatar is a piece meal for a man who just walked straight into theymos office. He is already a hero, and a Hero member 

OP "Date Registered:   June 23, 2022, 12:26:29 AM" but already making awesome additions to the dungeon. This place is timeless. I appreciate contributions like these it makes the thread more informative especially ones that get hundreds of pages long - thanks "(OP)"!

Faith in humanity finally restored.

There is no need for theymos to do such. He is already at 717 merits as of today and that is almost close to a legendary rank. The only thing holding him now is his activity count. He is at 98 activities. It remains just 2 to make him a Full member and he can wear an avatar in less than 2 weeks.


He has mentioned that and how he is going to pursue it.

You can write a userscript to change that. Or just use CTRL-F and type " (OP)".