Conversation

Replying to

@_venikx

and

@andrestaltz

For anyone bumping on this, project has been revived apparently: grapheneos.org

Replying to

and

CopperheadOS exists and continues on.

copperhead.co

Secure Android - CopperheadOS - Copperhead

Secure Android built for encrypted and secure phones by a privacy focused company. Available as security-centric and privacy focused Google-free Android for the latest Pixel devices.

Replying to

and

The name != ideals. Read: (OG CopperheadOS dev now GrapheneOS)

Quote Tweet

Daniel Micay

@DanielMicay

Sep 9, 2019

GrapheneOS is the continuation of the project formerly known as CopperheadOS. GrapheneOS is open source and is in the process of being properly revived and moved forward. grapheneos.org attestation.app github.com/GrapheneOS reddit.com/r/GrapheneOS @GrapheneOS

Show this thread

Replying to

and

Sustainability is one of the core ideals of Copperhead and CopperheadOS is sustainable.

Replying to

and

Copperhead spends it's time where it counts: creating partnerships, keeping up to date with the latest security and enabling a community. Something we don't do is call people scumbags on Twitter. twitter.com/DanielMicay/st

This Tweet is unavailable.

Replying to

and

CopperheadOS used to be ahead in terms of security, not just keeping up-to-date. While I don’t support the way

@DanielMicay

handled the situation you linked, why bring this up? It has nothing to do with CopperheadOS nor GrapheneOS. 1/

Replying to

and

it actually has *everything* to do with CopperheadOS. Toxic behavior is contagious.

Replying to

and

Toxic behaviour as in threatening contributors to the GrapheneOS project by copy striking their own contributions? See renlord.com/posts/2020-03-

Replying to

and

Part of my roles and responsibilities as the CEO is protection of Copperhead IP. This site asserts a bunch of false, non-lawyer legal claims about Daniel's code which makes it a bad example.

Replying to

and

IP protection itself is a toxic concept, specially in open source

Replying to

and

James has taken the path of fraudulently claiming ownership over our work since they aren't capable of doing anything more than poorly ripping it off. I own all of the code that I wrote for CopperheadOS.

8:59 PM · Jun 17, 2020Twitter Web App

Replying to

Some facts: I never had any work contracts to do work on it for Copperhead, and I never had an employment agreement or salary. I was not an employee of the company. James thinks he can retroactively go back and rewrite history to his benefit but it doesn't work that way at all.

Replying to

There was never any copyright assignment. The commits were clearly authored by me and attributed to me, using my personal email address. I used the company email address only for company business. The open source project was not company business. It started before Copperhead.

Show replies