-
bromite
Bromite is a Chromium fork with ad blocking and privacy enhancements; take back your browser!
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
hardened_malloc
Hardened allocator designed for modern systems. It has integration into Android's Bionic libc and can be used externally with musl and glibc as a dynamic library for use on other Linux-based platforms. It will gain more portability / integration over time.
> You made numerous baseless claims without evidence in your posts.
Please list them.
> If you're not one of those people, you should have posted from an established account where it wouldn't come across as yet another fresh account from a small group of people.
As I've stated before the reason I'm posting under a fresh account is to protect my identity so I don't face the wrath of you and your community. You've threatened to unleash this upon people in the past [0], despite constantly claiming that you're the one being harassed and attacked.
> A starting point is making a list of the posts you've made with throwaway accounts across platforms recently, showing us which ones were you and correcting the inaccurate claims you're making in them.
Yet another sockpuppet accusation. I hope anyone reading this is able to filter through strcat's baseless accusations and focus on the actual arguments being presented on both sides. I'm not sure why posting the same arguments under an established account should have any significance on the validity of the arguments.
You have failed to provide any evidence of anti-GrapheneOS sockpuppet accounts so far, but there actually has been clear evidence of a GrapheneOS lead developer encouraging the community to actively create sockpuppet accounts on Twitter, Reddit, and HN in order to promote GrapheneOS [1].
> People can look at our chat rooms and forums to see that this is clearly not true.
I actually encourage people to do this, because it very much is true.
[0] https://github.com/bromite/bromite/pull/2102#issuecomment-11...
[1] https://web.archive.org/web/20210913221117/https://sethforpr...
Screenshot of the GrapheneOS Matrix room from the article: https://web.archive.org/web/20210914180603im_/https://sethfo...
Note that "anupritaisno1" has changed their online identity a few times and is currently going by the name "randomhydrosol". It looks like they aren't listed under the GrapheneOS GitHub organization anymore, but they are e.g. one of the administrators of the privsec.dev website: https://privsec.dev/about
Throwaway because I don't want to be "ousted" from the privacy/security community for saying something negative about GrapheneOS [0]. I'm a big fan of the project but unfortunately it has formed a cult-like community that unquestionably goes along with every move that the project and its administration makes. I think it's important to always be critical, even of things you like, because this is the only way things can improve.
As some basic background: GrapheneOS is a FOSS Android fork aiming to improve privacy and security. CalxyOS is another such project. Strangely there has been a long history of drama between GrapheneOS and CalyxOS, despite both sharing similar goals. I won't get into it here because it's not relevant or very interesting. The gist of it is: the GrapheneOS and CalyxOS projects/communities don't get along very well.
Recently there was a controversy where the founder of GrapheneOS told the Bromite project (another FOSS project I'm a fan of) that they could no longer use any GrapheneOS code simply because they accepted a single contribution from a CalyxOS project member. The Bromite developer who accepted the contribution didn't even know he was involved with CalyxOS and was unaware of any animosity towards CalyxOS on the GrapheneOS side. I understand refusing to work directly with members of a community you despise, but this is blatantly ridiculous. The GrapheneOS project is setting a standard where, if you associate with any members of any "blacklisted" projects in any way, you are at risk of being cast out of the GrapheneOS community and denied access to GrapheneOS code. This is completely against the nature of free and open source software.
https://github.com/bromite/bromite/issues/2141
This obviously attracted attention in lots of places, but notably not on HN for some reason [1], despite GrapheneOS being a popular topic here [2].
In general I'm no fan of drama, but I think this reflects poorly on the GrapheneOS project and I think all GrapheneOS users should be aware of it.
[0] https://grapheneos.org