Skip to content

gni/name-change-log

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 

Repository files navigation

Why I changed my GitHub username (and how you can protect yours) 🔒

Why I made the change 🤔

One day, I noticed something odd someone was using my username (or similar variations of it) on other platforms. While I’m not famous or widely followed, this impersonation raised some concerns:

  • It could confuse collaborators or followers who think the impersonator is me.
  • It might damage my reputation if the impersonator acts maliciously.
  • It made me realize the importance of securing my online identity.

To avoid any confusion, I decided to change my GitHub username to something more unique and harder to mimic. I also want to take this opportunity to clarify an important point:


A quick note about social networks 🌐

I’m no longer active on any social networks except for GitHub. If you see someone using my name or an old username on platforms like Twitter or Instagram, it’s not me. Always double-check by visiting my official GitHub profile or other verified links.


How to check if someone is impersonating you 🛡️

If you’re wondering whether someone is pretending to be you, here’s how you can check:

1. Search your username online

Use search engines like Google or DuckDuckGo to look for your username and its variations:

  • "your_username" site:twitter.com
  • "your_username" or "your-username"

This can help you find any unfamiliar accounts or suspicious activity.

2. Check common platforms

Search for your username on platforms where impersonation often happens, such as:

  • GitHub
  • Twitter
  • Instagram
  • LinkedIn
  • Stack Overflow
  • Discord

Most platforms have search bars or directories to help you locate accounts using your name.

3. Use monitoring tools

You can automate the search process with tools like:

  • Namechk: Check where your username is already taken or used.
  • Google Alerts: Set up alerts for your username to get notified when it appears online.
  • KnowEm: Track your username across various platforms.

4. Make it a habit to check

It’s a good idea to periodically search for your username and variations. Regular checks ensure you can catch impersonation early before it becomes a bigger issue.


What to do if you’re impersonated 🚨

If you discover someone is impersonating you, follow these steps:

  1. Report the account
    Most platforms have impersonation reporting features. Provide evidence, such as links to your active accounts or original content, to prove your identity.

  2. Secure variations of your username
    If your preferred username is already taken, claim similar ones that are recognizable (e.g., yourusername_dev or yourusername_codes).

  3. Let people know
    Use your verified accounts to inform your audience or collaborators about the impersonation. Share links to your official profiles to avoid confusion.


Why it’s important to stay vigilant 👀

Even if you don’t have a large following, impersonation can still happen. Here’s why it matters:

  • Confusion: People might mistake the impersonator for you.
  • Reputation risk: Impersonators could scam or mislead others using your name.
  • Missed opportunities: Someone else might claim your preferred username on new platforms.

How to secure your accounts 🔒

Here are some simple but effective steps to keep your accounts safe:

  1. Choose a unique username
    Avoid overly simple usernames (e.g., coder123). Instead, combine something personal with a unique twist (e.g., janedoe.codes or jd_XR7).

  2. Enable two-factor authentication (2FA)
    Turn on 2FA for your accounts to add an extra layer of security. Use an app like Google Authenticator or Authy for better protection than SMS.

  3. Review your accounts regularly
    Check your account activity and authorized apps, especially on GitHub. Revoke access for apps you no longer use.

  4. Sign your GitHub commits
    Signed commits are a great way to prove your identity as a developer. Learn how to set this up: GitHub guide to signed commits.


Want to contribute? 🌟

If you have more tips, tools, or experiences to share, feel free to:

  • Open an issue with suggestions.
  • Submit a pull request to contribute directly.

Thanks for reading, and stay secure! 🛡️

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published