![]() |
|
Limit the History of Username Changes - Printable Version +- Hack Forums (https://hackforums.net) +-- Forum: Hack Forums Official Information (https://hackforums.net/forumdisplay.php?fid=1) +--- Forum: Site News (https://hackforums.net/forumdisplay.php?fid=2) +---- Forum: Suggestions and Ideas (https://hackforums.net/forumdisplay.php?fid=134) +---- Thread: Limit the History of Username Changes (/showthread.php?tid=5282362) |
Limit the History of Username Changes - GrandpaSherman - May 25, 2016 Hello, Currently, UB3Rs have the ability to view other accounts' old usernames used in the past 6 months. I think it should be limited to 1-3 months because, hypothetically, if I wanted to get a start at taking UB3R accounts. I would go to random users without gauth enabled, and try to use leakedsource or other databases one would/could have access to search up their username. It may not sound too threatening, but what if the difference between someone's account/security is their old username on HF. Like if I changed my name to Sherman and someone wanted to search my username they'd come up short (even if it was a more 'username-like username' like Darthfire337 changed to Darth), it would take half of a year, 1/20th of a decade, for my account security/personal security to go away. Of course, I understand the defense of the current rule, and I know it's our responsibility to stay safe on HF. I just wanted to give my opinion on the username history feature. TL;DR Longer username history leads to higher chances of security breaches. Thanks for reading * - Xerotic - May 25, 2016 I disagree. Your suggestion protects non-Gauth enabled accounts. Better practice is to require Gauth for Marketplace use IMO. Or even Gauth enabled for a certain time period before making threads in the Marketplace. Oh, and you did hit the nail right on the head with this line: Quote:Of course, I understand the defense of the current rule, and I know it's our responsibility to stay safe on HF. I just wanted to give my opinion on the username history feature. HF has some pretty good password requirements and it is HIGHLY advised to use unique passwords when using multiple services (HF, facebook, email, etc). If you fear your old username will get your account hacked, just change your password and enable Gauth. * - william - May 25, 2016 People could go to one of their really old threads and look at one of the posts someone quoted them on. Example here: https://hackforums.net/showthread.php?tid=4893784 His current name is "Thierry" but when that guy quoted him it was "Man Chest Hair United" * - GrandpaSherman - May 25, 2016 (May 25, 2016 11:09 PM)Xerotic Wrote: I disagree. Your suggestion protects non-Gauth enabled accounts. Better practice is to require Gauth for Marketplace use IMO. Or even Gauth enabled for a certain time period before making threads in the Marketplace. I agree, I think everyone should use gauth. And making it a marketplace requirement would be an amazing improvement. (May 25, 2016 11:11 PM)williamnot. Wrote: People could go to one of their really old threads and look at one of the posts someone quoted them on. That's true, and the name in the quotes can be edited. * - Xerotic - May 25, 2016 (May 25, 2016 11:13 PM)GrandpaSherman Wrote: I agree, I think everyone should use gauth. And making it a marketplace requirement would be an amazing improvement. Omni isn't going to run a query to change EVERY SINGLE QUOTED POST when somebody changes their username. It simply isn't feasible. * - GrandpaSherman - May 25, 2016 (May 25, 2016 11:16 PM)🤝 Wrote: Omni isn't going to run a query to change EVERY SINGLE QUOTED POST when somebody changes their username. It simply isn't feasible. Of course, I wasn't suggesting a change to his point. It's simply not possible like you said. I just put my two cents in because you give a penny when you take a penny. * - Xerotic - May 25, 2016 (May 25, 2016 11:18 PM)GrandpaSherman Wrote: Of course, I wasn't suggesting a change to his point. It's simply not possible like you said. Oh, I thought you were suggesting to run a query, my misinterpretation of that specific post. Do you still think this suggestion is viable for HF? Or that it should be accepted? * - Truth - May 25, 2016 We should be able to lock our username so no one can have them * - GrandpaSherman - May 25, 2016 I think running a query, like you said, would be pointless. I actually discovered something while I was here. So thanks! |