Likely going to have very positive news to announce about GrapheneOS in the near future.
It's unfortunate that others decided to pick up the torch of fighting an underhanded war against us after Copperhead started to stop. The past month SHOULD have been a huge relief, but no...
Nevertheless, there's probably going to be some great news. I hope others realize that waging a misguided war against us is not going to work out to their benefit and they can either stop or destroy themselves in the long run. I'll happily put very substantial resources into it.
One consequence of all the nonsense with Copperhead was lack of time to hire people. Now we have a lot of money we need to spend along with a lot more time and resources being freed up. I'll happily spend a substantial amount paying people to counter any further shenanigans.
Leave us alone and let us build our OS, apps and hardware in peace. Don't confuse our lack of marketing, etc. with lack of resources to do it.
I don't think it's a good use of money but draining resources of organizations harming us will save time/energy and I will 100% do it.
I think people greatly underestimate the resources we have available. It has been extremely difficult to get anything done because of the legal nonsense, etc.
I didn't have energy to find people to hire and didn't know how much money would be needed for the legal stuff, etc.
That time and money should now be able to go towards the project. I lack patience for more of this nonsense and I care about GrapheneOS a lot.
Burning so much money on legal fees has given me a new perspective. $5k/month fighting back against people bothering us is the norm.
Most donations to GrapheneOS were made with Bitcoin. We sat on most of it for the past few years as a legal fund. It's a lot of money.
It's going to fund a lot of development work. I don't need any of it, and haven't taken any BTC/Monero for myself. It's for hiring other people.
I want to hire developers to build useful things with it, not pay for lawyers, private investigators, documentation countering attacks, fact-based advertising campaigns against malicious parties, etc. We didn't do that not because we couldn't but because it would be a waste.
I'm entirely willing to start dedicating substantial resources to bringing all this nonsense to an end though. I don't have any patience left for it.
No point of having those resources if people are determined to make things a non-stop hell where we can't focus on our projects.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Despite previously claiming to be my friend and a supporter of my work, @nickcalyx has consistently engaged in trying to portray me as being deranged/crazy. He has participated in persistent harassment and bullying targeting me. It's far worse than anything Copperhead ever did.
I was naive and repeatedly tried appealing to him for help against attacks from Copperhead and then the even worse behavior from his own community.
Copperhead has stopped their attacks, at least for the time being, but Calyx has continued carrying it on and it's worse than ever.
Calyx took full advantage of what Copperhead was doing and tried to use it as a way to benefit themselves. They actively engaged in making it worse while playing the both sides angle. They've now done things far worse than anything Copperhead did in years of trying to hurt us.
There's not much downside to only having 1 slot per slab once slab allocations are 4096 byte aligned, which is what we refer to as extended size classes. This goes nicely with the guard slab feature.
By default, there's an unused guard slab between every possible usable slab that's left as unused PROT_NONE memory.
If the slabs have 1 slot, the allocations have guaranteed guard pages without paying the cost of actually making system calls to set them up during regular usage.
Having slabs with 1 slot originally wasn't supported but github.com/GrapheneOS/har… added support for it.
This does need a tiny little bit of unnecessary work but avoids other work (bitmaps). It's insignificant for allocations this large, especially with zero-on-free, etc. enabled.
Traditional epoll wakes every thread and they race to accept the connection. EPOLLEXCLUSIVE fixes it but uses LIFO order.
LIFO order is terrible for a web server. HTTP connections are generally long-lived and reused for mixed / varying workloads. That's even more true with HTTP/2 where clients are only supposed to make a single connection to each server and multiplex everything over it concurrently.
In a standard nginx setup on Linux, it uses EPOLLEXCLUSIVE. This gives nearly all the connections to the same worker until it starts getting overloaded. Even then, the most overloaded workers still keep getting the most connections among handling other events. It's pretty awful.
We've archived these tweets where Copperhead's CEO admits to them tracking devices via unique identifiers and using them as part of the update system.
He admits that their phone sellers with Copperhead emails, etc. have databases mapping unique identifiers to the customers too.
His excuse is that tracking devices via unique identifiers available to update server doesn't count as tracking users. They've designed it in a way that they can ship an update targeting a device. The excuse is they don't know which user has which device, but their seller does.
In that same thread, he also peddles the usual lie that Copperhead is source available. Meanwhile, the sources are not published and are not available for review. Multiple researchers including a Whonix developer have attempted to get access to the sources and could not get it.
@cankerwort_@sethisimmons@CopperheadOS@mamushi_io@GrapheneOS They're the ones choosing to a misinformation war against GrapheneOS along with threatening/intimidating anyone who contributes to the project, even people that are underage. You say it should be settled in court but they're making daily attacks on us causing lots of harm.
@cankerwort_@sethisimmons@CopperheadOS@mamushi_io@GrapheneOS GrapheneOS not a for-profit project. We're not selling any products. We're focused on building privacy and security technology. They're focusing all their resources on causing harm to us in any way that they can, and on marketing a product simply copy pasting our codebase.
@cankerwort_@sethisimmons@CopperheadOS@mamushi_io@GrapheneOS This is primarily not a legal dispute. It's largely a personal vendetta against me by James Donaldson and now also Max. Their poorly formed lawsuit against was primarily a way to exhaust my time, energy and resources along with intimidating people to stop them from contributing.