Discussion
I am sorry to say Graphene has fallen to the slop. thread: https://grapheneos.social/@GrapheneOS/117226938743085364
they are making out that their vibe coding isn't *vibe* coding how dare you, which may be worse https://news.ycombinator.com/item?id=49591796
@frutiger@mastodon.social mastodon.social, 14 followers, thanks slopbot
the source is reading their fucking AGENTS.md you dipshit
@davidgerard@circumstances.run oh nice they are not even arguing against the social and environmental problems and just talk about tool efficiency.
guess as long as Soylent Green meets the nutritional macros…
@davidgerard A cursory glance at their posts suggests they're stressing it isn't vibe *coding* if it's only "auditing" existing code?
Which is a very fine line that still results in /using/ the slop machinery.
I wish the software development ecosystem would fix the underlying architectural problems rather than keep brushing them under the rug. But we're now all so entrenched in arguing to slop or not to slop that few are talking about what it means not to slop.
@zimzat also it never, ever stays true. It's another "i'm totally not vibe coding, I'm" [list of things anyone else would call abject vibe coding]
@zimzat @davidgerard This post makes it sound like they're using it for code generation too; the same "oh but it's just a developer's private test branch" shtick as with the Bun Rust migration:
https://grapheneos.social/@GrapheneOS/117227346006458958
Plus, their AI-generated AGENTS.md explicitly talks of code generation, so yeah. I can imagine them perhaps being a tad more careful than many sloppers, but even then, AI use has this tendency to make the user less careful and less capable over time.
@davidgerard Only the finest artisanal slop
I was always suspicious of the fact that they focused mainly on using Google software honestly. They claimed it was because it has the best security features, but then go and use a method of generating code that's notorious for creating security problems?
@contrasocial @davidgerard Yup. It's pretty rich of Graphene to go AI after the long ranting threads they would post on the shortcomings of other projects. They trashed other degoogled Androids, they trashed non-Android Linux phones, they trashed other FOSS Android projects like F-Droid etc. Their way was the only true way.
@davidgerard That sucks.
I wonder if anyone has started making up a list of untainted/ethical/respectable OSS projects, as it's becoming increasingly hard to find projects that haven't given up to the broligarchs.
If not, should we start one? I reckon it might be depressingly short.
@davidgerard "Many valid issues are reported in between the hallucinations and other nonsense. It takes additional time to confirm which issues are real and address it."
Well, how does it help then?
How does it help?
In an OS that people use because they fear for their lives.
How does it help?
I am beyond angry. 
@davidgerard the part about contractors paying for their own llm tokens is pretty wild.
https://grapheneos.social/@GrapheneOS/117227373537383215
Also, the sock puppets seem like they used an llm.
@davidgerard They're literally doing the ""Guns don't kill people, we have to have guns to kill other people with guns" argument.
"Get more and bigger guns now, it's just a tool"
@davidgerard "Look man, it ain't gambling. See, I gots a system." <twitch>
Install bonfire.cafe
Get the full app experience
@davidgerard If ycombinator is the source on grapheneos issues, then it's not true. Some of you sound like religious nutjobs when asking about ai with words like 'tainted', a horseshoe version of twitter users who are psychotically pro ai.