3 ms·

They are using AI [1]. I don't think messaging app is non-critical though. [1] https://github.com/GrapheneOS/Camera/tree/compose https://github.com/GrapheneOS/

They are using AI [1]. I don't think messaging app is non-critical though. [1] https://github.com/GrapheneOS/Camera/tree/compose https://github.com/GrapheneOS/Camera/tree/compose

BearOso 1mo ago
I dunno. If they're using AI, it's well controlled. I don't see a lot of artifacts you usually get from full-on vibe-coding.
- grapheneos 1mo ago
  Our code quality standards are very high. Vibe coding is not capable of meeting those standards. The details of how things get written and improved to meet our standards is up to individual developers. We don't have a policy against developers using AI for assistance. They need to understand all of the code and it needs to pass our code review. Our code review is now usually a lot more thorough than before. In addition to human review, we regularly pass code through a couple frontier AI models and then review the results to figure out which claims it makes are valid. Even the frontier models hallucinate many non-existent problems and often get a lot of details wrong when they find real problems, but they do find a lot of real problems. https://news.ycombinator.com/item?id=49592770 https://news.ycombinator.com/item?id=49592770
grapheneos 1mo ago
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.
- Cider9986 1mo ago
  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.
  - deleted 1mo ago
    [deleted]
  - montyanne 1mo ago
    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.
    - gib444 1mo ago
      [dead]
- gib444 1mo ago
  [flagged]
  - grapheneos 1mo ago
    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.

They are using AI [1]. I don't think messaging app is non-critical though. [1] https://github.com/GrapheneOS/Camera/tree/compose https://github.com/GrapheneOS/Camera/tree/compose

BearOso 1mo ago

I dunno. If they're using AI, it's well controlled. I don't see a lot of artifacts you usually get from full-on vibe-coding.

grapheneos 1mo ago
Our code quality standards are very high. Vibe coding is not capable of meeting those standards. The details of how things get written and improved to meet our standards is up to individual developers. We don't have a policy against developers using AI for assistance. They need to understand all of the code and it needs to pass our code review. Our code review is now usually a lot more thorough than before. In addition to human review, we regularly pass code through a couple frontier AI models and then review the results to figure out which claims it makes are valid. Even the frontier models hallucinate many non-existent problems and often get a lot of details wrong when they find real problems, but they do find a lot of real problems. https://news.ycombinator.com/item?id=49592770 https://news.ycombinator.com/item?id=49592770

grapheneos 1mo ago

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.

Cider9986 1mo ago
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.
- deleted 1mo ago
  [deleted]
- montyanne 1mo ago
  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.
  - gib444 1mo ago
    [dead]
gib444 1mo ago
[flagged]
- grapheneos 1mo ago
  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.