Conversation

Daniel Micay
@DanielMicay
I previously posted this gist (gist.github.com/thestinger/ecd) about our failed attempt at getting Twitter verification for
@GrapheneOS
. The project account linked to this here: twitter.com/GrapheneOS/sta A malicious actor quite possibly paid to attack GrapheneOS is misrepresenting it.
Quote Tweet
GrapheneOS
@GrapheneOS
If you're curious, these are the 10 news articles we provided to demonstrate notability: gist.github.com/thestinger/ecd They want at least 3 with verified accounts from the past 3 months and was provided there. Also, bear in mind they stalled our initial request >1 year due to a bug.
Show this thread
1
18
Daniel Micay
@DanielMicay
Yae4 is repeatedly trying to push the claim GrapheneOS is not open source. They're trying to base that around us requesting that a project (Bromite) which stopped allowing us to use their code stop using our code in return, which we followed up by relicensing Vanadium as GPLv2.
1
8
Daniel Micay
@DanielMicay
Last time I checked, GPLv2 is an open source license. Yes, we used it to stop a GPLv3 project using our code since we are unable to include that GPLv3 in Vanadium. We've made GPLv2 more permissive with 3 exceptions permitting the WebView linking, Apache 2 and upstreaming work.
1
8
Daniel Micay
@DanielMicay
We didn't find it particularly fair that a project is including our code while we would be unable to use theirs even if we were willing to include GPLv3 code because they do not grant the exception we would need for linking the WebView with non-GPLv3 compatible apps in the OS.
1
9
Daniel Micay
@DanielMicay
Replying to
@DanielMicay
GrapheneOS cares about being able to upstream code. As part of using GPLv2 we require contributors authorize upstreaming code under the preferred upstream license, which only applies if it's accepted. Blocking the upstreams from using their code is exactly what Bromite is doing.
8