Conversation

twitter.com/DanielMicay/st GitLab reversed this decision and ended up releasing the GrapheneOS name from the name squatter. They don't act upon issues like impersonation of a project but they do have a policy to release names that are being squatted and ended up doing that for us.

Quote Tweet

Daniel Micay

@DanielMicay

Dec 29, 2020

GitLab cares as much about people impersonating an open source project or organization as GoDaddy. By that, I mean they don't care at all and won't do anything unless ordered to do so by a court. Pretty sad how much better LinkedIn and GitHub have been about dealing with this.

Daniel Micay

@DanielMicay

Jan 2, 2021

We've succeeded in resolving these kinds of issues with LinkedIn, GitLab and matrix.org now.

@Namecheap

has yet to do anything to address their involvement in the ongoing attacks on the project, despite it clearly being malicious behavior:

Quote Tweet

Daniel Micay

@DanielMicay

Dec 30, 2020

Copperhead registered the grapheneos.ca and grapheneos.net domains and redirected them to their site. I had my lawyer intervene and those redirects are now removed but they still have the domains. It's yet another example of their desperate attempts to harm us.

Show this thread

This Tweet was deleted by the Tweet author. Learn more

Replying to

and

The project was started in 2014. It was publicly renamed to GrapheneOS in 2018. That wasn't the beginning of the project. grapheneos.org/#history You can see that there are publicly available forks of our repositories going back to early 2015: github.com/GrapheneOS/pla

5:18 AM · Jan 2, 2021Twitter Web App

This Tweet was deleted by the Tweet author. Learn more

Replying to

and

Look at all of the domains that are available: domains.google.com/registrar/sear Are you suggesting we should register all of them? GrapheneOS is an established trademark. Unregistered marks have protection. It's not legal to maliciously register a domain this way. What's your point?

Show replies