Our port of Messaging to Compose was clearly not vibe coded as both the parent comment and yours are wrongly portraying it. Experienced developers have been working on overhauling the app for months with a lot of back and forth code review to get the pull requests into shape. We don't have a policy against using AI for assistance as long as the resulting code meets our high standards.
We definitely use frontier AI models with cybersecurity access unlocked for code review. Those often find problems we didn't catch via multiple rounds of human review. The output is filled with hallucinations and incorrect details but an experienced developer can sift through it, identify the real issues it uncovered and get those fixed.
How did my comment portray your port as you are vibecoding it? I just said that AI is being used.
It seems obvious to me that you guys would use it responsibly.
I appreciate all the hard work the Graphene team has done all these years with advancing alternative mobile OS and have been following them for years so I hope they don’t take this the wrong way -
The project would benefit from more polished, professional image/interactions with the community. I (personally) have a hard time trusting my data to a project that is constantly bickering (“no, we don’t vibecode, did you even look at the repo”) in public forums like this under the official letterhead account.
I’d love to see y’all discussing these types of technical details with individual, identifiable (even under fixed pseudonyms if you want) developers’ accounts, and leaving the official letterhead account to stick to posting marketing material.
Just my 2 cents.
[dead]
[flagged]
We've explained we're using a GrapheneOS project account due to libelous personal attacks, stalking and harassment towards our founder and other team members. Hacker News has many past threads filled with libelous personal attacks towards our team. We repeatedly asked for moderation intervention and it hasn't happened. We regularly had our replies in those threads flagged because it went against the bandwagon of hate towards us.
Your account is persistently engaging in inappropriate personal attacks towards our founder. It's inappropriate to keep dropping someone's personal name who has never participated with their name on this site even aside from the personal attacks.
You're seeking out threads with discussion about GrapheneOS to post misleading and inaccurate claims about it in order to troll. You previously set your profile bio to a hostile remark towards the GrapheneOS project and have now changed it to pretend to be a GrapheneOS supporter.
Flagging personal attacks, harassment content, trolling, AI slop, engagement bait, shady advertising for products and deliberate attempts to mislead people is an appropriate use of the feature from our perspective.
We've been reaching out to the Hacker News moderation team for a while to discuss the years of libelous personal attacks and harassment content posted on the site. They can reach out to us at contact@grapheneos.org where we can discuss that.
You don't deny the flagging operation. Thanks for confirming it
More world salad to distract. No sources.
I'll send you some proof that my device is running GrapheneOS btw. How would you like to arrange that?
Yes my support of the project is variable, highly influenced by how it is run and how the directors act on social media. The project does not have a right not to be criticised and that includes the people running it. It's the flip side of the coin of engaging in a public forum
"HN is a community—users should have an identity that others can relate to" – it's not designed for corporate PR accounts. We all know it's you purely by your style of writing and persecution complex