This is so tiring. Don't get a single day without multiple serious attempts to harm the project by Copperhead and their associates. They reach out to tons of people trying to trick them with their false narratives in private. They threaten contributors.
They don't seem to get that they're never going to succeed at destroying the project. Considering that they're still copying our code, documentation and even things like tweets it's really not sure what they are trying to accomplish. They're nothing without our code and research.
In response to GrapheneOS getting more attention, they're ramping up their attacks. The privacy and security industries are full of these charlatans building businesses on dishonest marketing and harming others. This is such an extreme case. They're so invested in harming us.
I haven't been able to focus on development work for years now. They're relentless in their desperate war against us. The company has been turned into a weapon for attacking myself and GrapheneOS. That's what they do with the revenue from selling our work.
Their CEO spends his time contacting people, spreading misinformation and managing sockpuppet accounts. They try to spin things around and portray us as the ones doing something wrong for defending the project and our contributors / users. We're never going to give in to them.
Every attack they make on us is going to have a hundred fold response from our community. Help us with that. Spread the word about what they're doing. Counter the misinformation they spread. Show people what's happening. Don't fall for their narcissistic CEO sweet talking you.
I own 50% of the voting shares of Copperhead. I own the code they use. That company is going nowhere. If you buy a phone from them, you'll just end up being migrated over to GrapheneOS when I end up with full ownership of it. All you're doing is funding attacks on open source.
I fully intend to redirect all the old accounts and domains to the new name being used by the open source project. I'm halfway there. I own half of the company. We'll see how long they can keep grifting. They've engaged in criminal behavior and even worked with organized crime.
James Donaldson needs to be held accountable for fraud, theft and his other criminal behavior. If he wasn't a completely delusional narcissist he would have crawled away from this a long time ago. No idea what he expects to gain ramping up harassing/threatening our contributors.
Seriously James, fuck off. You're by far the worst 'friend' that I've had in my life. We're going to keep building GrapheneOS regardless of what you do. No amount of your bullshit will stop us. Cut your losses while you can. Stop threatening students working on open source.
The latest escalations are really the last straw. He throws a fit because GrapheneOS got some attention and starts threatening people and ramping up his misinformation. The fact that I own half of that pathetic company is the cherry on top. What are they even trying to do?
It's time for James to cut his losses and sell me the rest of the company so it can be wrapped up in a way that minimizes the harm being done to people. Can migrate the few customers to what they thought they were buying. It's getting more and more pathetic and needs to stop.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with DanielMicay

DanielMicay Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @DanielMicay

3 Feb


Copperhead is still squatting on these domain names. GrapheneOS was formerly known as CopperheadOS and we used that name for the project before the company existed. This name was adopted afterwards. They have no valid reason to be using it...
Maybe it's time to make another attempt to get @Twitter to return the open source project's Twitter account.

Copperhead tricked Twitter into letting them hijack it by reversing an email change months earlier away from daniel.micay@copperhead.co when I stopped trusting James...
To be clear, I'm talking about the project's previous Twitter account, not the new @GrapheneOS account created as a replacement for it. I created this personal account as the initial replacement for it in June 2018 after the original project account was hijacked by them.
Read 4 tweets
3 Feb
@CitadelHyperion @GrapheneOS It's a good comparison. The privacy and security industries are full of charlatans / scammers. James Donaldson (Copperhead CEO) is one of them. He's a narcissistic sociopath obsessed with causing harm to us in any way possible. He's obsessed with harming us in any way he can.
@CitadelHyperion @GrapheneOS He finds people he can trick, just like Craig. He gets sponsored reviews and content published by people that are trusted by others in the cryptocurrency community. Buys them phones, brings them into his business as resellers, etc. That's how he's getting resources to harm us.
@CitadelHyperion @GrapheneOS They sell a poor clone of our work with tracking for license enforcement for a huge amount of money. That money largely goes to bogus legal attacks and further promoting it in the same way. They're getting increasing desperate and are constantly spreading misinformation/attacks.
Read 4 tweets
30 Dec 20
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.
It's part of their continued attempts to fraudulently claim ownership over my work and to misrepresent themselves as the ones who created it. I started the project in 2014 before the company was founded in late 2015. The project has never been owned or controlled by Copperhead.
I created CopperheadOS before Copperhead existed. I never did that work for anyone but myself on my own time. It was formally agreed upon that I owned and controlled the open source project. Copperhead chose to ship the upstream releases of my project instead of making their own.
Read 13 tweets
27 Dec 20
CAKE works extremely nicely for providing fair allocation of outgoing bandwidth from a server:

tc qdisc replace dev eth0 root cake bandwidth 500mbit besteffort

Bandwidth parameter needs to be properly set so that it becomes the bottleneck and actually shapes the traffic.
It will evenly divide the bandwidth between hosts so a host opening many connections (download managers) doesn't end up with higher bandwidth. It also evenly divides the per-host bandwidth between the flows to the host. SSH latency will also remain very low even under heavy use.
CAKE:

* client A with 1 connection gets 48mbit
* client B with 8 connections gets 6mbit each adding up to 48mbit

No CAKE:

* client A with 1 connection gets ~6mbit to ~16mbit
* client B with 8 connections gets ~6mbit to ~16mbit each adding up to ~80-90mbit

Stark difference.
Read 6 tweets
25 Dec 20


android.googlesource.com/platform/frame… is the place to start if you're interested in finer details of the implementation.

For Pixel 2 and later, isWeaverAvailable() is true.

SyntheticPasswordCrypto.personalisedHash(...) is used to quickly derive a value with SHA-512.
For example, the Weaver key is made by passing "weaver-key" and the password token to SyntheticPasswordCrypto.personalisedHash(...). That way, the password token derived with scrypt isn't actually sent to the secure element. That's used for deriving a bunch of different keys.
There's also other hashing that's not really noteworthy such as the lockscreen implementation hashing the password in a similar way before passing it along, etc. The actual work factor is provided by scrypt and the SoC-specific hardware-accelerated, hardware-bound key derivation.
Read 4 tweets
18 Dec 20
Copperhead has gotten back to raiding our IRC / Matrix channel. I'm sure they're probably also busy editing Wikipedia, reaching out to people to spread more lies, etc. Since they just poorly copy our code months later, it's not like they actually develop an operating system.
It really says a lot that this is how they spend their time. Going to be adding substantially more moderators on IRC / Matrix and Reddit. Also going to be taking a much more active approach to banning concern trolls. Would appreciate if other communities do the same with them.
Matrix has much worse moderation tools than IRC and is far more easy to abuse. It's unfortunate. Would be helpful to get in touch with matrix.org admins so that we could gain control of some aliases they registered via concern troll sockpuppets + some other things.
Read 4 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!