-
Hey,
The username Policy has not changed, it is still forbidden to squat a username :
The username I want had no activity since its creation (10 years), and last time he logged was 6 years ago. I don’t understand why my request is denied as the account violates the rules. |
Beta Was this translation helpful? Give feedback.
Replies: 39 comments 91 replies
-
Hi @fudjia and welcome to the community. First of all, we cannot discuss account-specific matters on this forum. That’s what GitHub Support is for. Their answer seems clear to me:
The fact that name squatting is disallowed, does not change the fact that currently no new requests for the release of these names are being reviewed. A simple reason for this may be the following excerpt from the Username Policy, although that is just speculating from my side.
|
Beta Was this translation helpful? Give feedback.
-
I’m a bit late to this thread, but I hope github reverses this policy. Without enforcement, name squatting is rather allowed.
This can’t really be the reason they declined to review the request. Without a review, github wouldn’t even know whether the account has non-public activity. If they simply wished to avoid the hassle of having to review for non-public activity, then they should just remove their stance against name-squatting. |
Beta Was this translation helpful? Give feedback.
-
You’re confusing a few things here. First of all, having a name-squatting ban in your ToS doesn’t actually mean you’re enforcing it. It just means it isn’t allowed, and serves as a good legal basis to remove accounts should they pose a problem. It doesn’t create an obligation to also actively enforce the rule. Furthermore, enforcing anti-name-squatting guidelines isn’t the same as allowing anyone to challenge the legitimacy of an account. GitHub may very well be enforcing this rule by, for example, automated checks on (private) account activity. This doesn’t really mean they have to allow anyone to challenge other accounts.
So this isn’t true, since by definition name-squatting is disallowed.
As I said; they may very well just run automated checks on account activity. User reporting and manual review isn’t the only way to check/enforce these things.
No, they don’t have to do anything. Name-squatting isn’t allowed, but it’s enforced without the help of user reports. Unfortunately those are the rules. If the name you desire is taken but there seems no public activity, I’m very sorry for you. GitHub won’t take review requests. And there is a good chance there still is private activity on the account. Try picking a different name and regularly check back on the other account: who knows some day might be your lucky day. |
Beta Was this translation helpful? Give feedback.
-
Hi, I saw that you managed to get the username you wanted. Would you mind telling me how you did it? |
Beta Was this translation helpful? Give feedback.
-
Is there no recourse to try and get an inactive user removed anymore then? I had to do this twice for 2 orgs I am part of as they both had users who made an account and had no public activity since joining, I am in the same boat again where there is a user account which is squatting an org name I would like to use to split off some private repositories. It feels like removing this feature is a bad move, as you could still allow it but behind the scenes just have the support ticket check when the last user login/action and how many repositories they have interacted with, if they have not logged in for years and have never carried out any actions then take it through as a request for github to look, if not just have the ticket be binned so it doesnt waste peoples time with accounts that do things privately. As it currently stands there is a user who has no activity in over a decade other than making an account and I am powerless to request they be removed so I can make use of it. I implore github to rethink this. |
Beta Was this translation helpful? Give feedback.
-
They ghosted me essentially. I asked if a trademark would force them to uphold their squatting policy and they refused to answer.
Please excuse my brevity as this message was sent from my smartphone.
Spencer C. Imbleau (he/him/his)
… On Sep 9, 2022, at 19:03, Raj ***@***.***> wrote:
@simbleau what did GitHub reply when you tried with a trademark?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.
|
Beta Was this translation helpful? Give feedback.
-
I get the squatting thing...is it another thing if someone clearly argumented he has no interest in keeping the account, offered you to rename and free up the name already but keeps asking for "payment" to do so? Wonder if that's something I should open a ticket for and if Github still deals with that kind of stuff. |
Beta Was this translation helpful? Give feedback.
-
I think Github should start the name squatting policy again. |
Beta Was this translation helpful? Give feedback.
-
I don't see why i can't dispute an username that has been dormant/inactive for 13 years. I hope they change the policy again. |
Beta Was this translation helpful? Give feedback.
-
I hate you Github. Bring back the policy |
Beta Was this translation helpful? Give feedback.
-
@github-staff This can't be the full story. I'm currently looking into the username "stryker" and the username was only registered in October 2022. There's no way this username wasn't in use before that so unless someone with the username personally signed on and deleted their account out of the goodness of their hearts, something must have happened to make this username available again. Side note, it seems the new user is squatting it, of course. |
Beta Was this translation helpful? Give feedback.
-
Я просто удивлен, что имя пользователя @russian не использовалось до 2020 года... |
Beta Was this translation helpful? Give feedback.
-
Thread tl;dr There are so many examples given by the community where it is apparent that accounts are dormant, so please don't try to fool us that they are all doing private stuff 24/7. |
Beta Was this translation helpful? Give feedback.
-
We also encourage GitHub to change their policy and actions and to release dormant/inactive usernames. We had to create a stupid username just because the brand we were using is a dormant username. |
Beta Was this translation helpful? Give feedback.
-
I don’t even think releasing them outright is a great idea. I think it is better served as an “ask and you may receive” type of deal but just actually enforced. If we’re going to involve humans in the process (which should be the case regardless) there should some sort of “good faith” argument where someone who wants some short dictionary word that probably doesn’t represent their identity elsewhere on the web should have to provide something to show they use the name, like owning a domain name bearing the name. Otherwise people using names as vanity plates or bragging points will win and legitimate organizations who cannot afford to change names willy-nilly (like an inactive account with no URL changes to worry about) will be lost on the name they want because a more sophisticated squatter, some user who just wants a fancy name, was able to ask GitHub for the name first. Since this is more detrimental to orgs who place value in their names as well as not having to change them later it would undo the whole purpose of this to just release them freely. |
Beta Was this translation helpful? Give feedback.
-
I couldn’t file a request nor find a way to contact
On Wed, Oct 18, 2023 at 3:26 PM coderipper ***@***.***> wrote:
Have you filled another request?? did you manage to communicate with
github when trying to get a used username?
—
Reply to this email directly, view it on GitHub
<#23495 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOOQ5SPKCWWLBE7FU37N4XTYAAUOJAVCNFSM54ZVEOS2U5DIOJSWCZC7NNSXTOKENFZWG5LTONUW63SDN5WW2ZLOOQ5TOMZRHEZTAMI>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Adam Haas
|
Beta Was this translation helpful? Give feedback.
-
Maybe the solution is to go to GitLab.com? |
Beta Was this translation helpful? Give feedback.
-
Still words, no actions. Damn it. |
Beta Was this translation helpful? Give feedback.
-
Still words to comfort, no actual actions... |
Beta Was this translation helpful? Give feedback.
-
A name about an anime counts as DMCA? |
Beta Was this translation helpful? Give feedback.
-
at least gitlab take request for username squatting for paid customers. |
Beta Was this translation helpful? Give feedback.
-
Throwing my name on the pile of those frustrated by this. I know policies take a long time to review, and I'm sure github has a lot on its plate. But... I recently changed my legal name and was hoping to change my github account to reflect this. I found that my new name belongs to an account that registered it in 2010 and has no public activity since. |
Beta Was this translation helpful? Give feedback.
-
I gave up, they don't give a shit. A person been using my name for decades without activity for over a decade. Seems I'll just stop using them.
On Wednesday, February 14, 2024 at 07:49:45 PM MST, dkassler ***@***.***> wrote:
Throwing my name on the pile of those frustrated by this. I know policies take a long time to review, and I'm sure github has a lot on its plate. But... I recently changed my legal name and was hoping to change my github account to reflect this. I found that my new name belongs to an account that registered it in 2010 and has no public activity since.
Sure, maybe they've been busy privately. But knowing that it's a short name, knowing that 2010 was the early days of github, a time when domain name squatters are most active cornering all the short, desirable seeming names... I can't help but suspect that this is what happened here.
If the user really hasn't been doing anything with it, I would really hope there's a way to fix this. Username/domain squatters are the worst.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
queenofcorgis we appreciate your previous communication on this matter. Is it possible to share the outcome of the internal investigation with the community? I assume it has concluded over the past 11 months, and the overlords have decided it's not a priority? I guess it's just cheaper and easier to no longer review requests to release dormant or inactive usernames; GitHub is on a tight budget, after all! |
Beta Was this translation helpful? Give feedback.
-
honestly, this is great. i have my first name as my username (which I claimed from someone else), now i can i sleep peacefully knowing I can do absolutely nothing for the next 10+ years because an unenforced policy is basically as if it doesn't exist. it feels great to benefit from something that others cannot. glad to see github is on the right side of progress! |
Beta Was this translation helpful? Give feedback.
-
I also find it unfortunate that GitHub name squatting is no longer being fought. I don't begrudge active GitHub users a good/short user name at all and am glad that they have one. However, it is a shame that there are users who have been using these names for several years, even though they hardly seem to be inactive anymore. Even if it involves a lot of bureaucratic effort, the re-release of inactive GitHub usernames would certainly be a great enrichment for the community. |
Beta Was this translation helpful? Give feedback.
-
I'm in a similar boat to others in this thread, and it's a shame that GitHub aren't interested in exploring this policy which clearly isn't working in its current state. Well, not working for end users, but probably working for GitHub in the sense of less work to do responding to squatting/abandoned requests! There's an organisation that appears abandoned which has an abbreviated/shorter name of a GH organisation I own. I appreciate that private activity and members aren't visible, but this organisation has no extra metadata (description, URL, etc.), no custom avatar, and no public activity or members. On top of that, I've confirmed with GitHub's GraphQL API that the organisation's created and updated timestamps are identical, so it hasn't been changed since its initial creation. There are some suggestions in this thread about having mechanisms where if an account/org hasn't had activity in x years, etc. then it can be considered abandoned. I'm not sure that kind of strategy is suitable, because there are valid use cases where an org or user might be owning a repository that is archived (no changes), but of significance to still be available. However, in my case, I'd suggest that an org which has seemingly no activity or members, and according to the API has literally not been updated since it was created, is an acceptable candidate for being considered "abandoned." As far as steps I've tried to take: I've reached out to support multiple times, where they've (correctly) informed me that it's not appropriate to divulge whether an account has private activity (completely understandable). I've also attempted to open issues/discussions with an Some folks have suggested a mechanism to contact an org owner/user (without revealing their email). However, in my case, where I have strong reason to believe the org is abandoned, that wouldn't offer any advantage. At the very least, I'd just like to be told by GitHub: "hey, it's actually active, there's some private repos." At least with a response like that, I can give up on this constant chase to see if the org can be acquired. |
Beta Was this translation helpful? Give feedback.
-
Any updates here? |
Beta Was this translation helpful? Give feedback.
-
Don't think this will be resolved |
Beta Was this translation helpful? Give feedback.
You’re confusing a few things here.
First of all, having a name-squatting ban in your ToS doesn’t actually mean you’re enforcing it. It just means it isn’t allowed, and serves as a good legal basis to remove accounts should they pose a problem. It doesn’t create an obligation to also actively enforce the rule.
Furthermore, enforcing anti-name-squatting guidelines isn’t the same as allowing anyone to challenge the legitimacy of an account. GitHub may very well be enforcing this rule by, for example, automated checks on (private) account activity. This doesn’t really mean they have to allow anyone to challenge other accounts.
So this …