I am sorry to say Graphene has fallen to the slop.

[davidgerard@circumstances.run]

@frutiger@mastodon.social mastodon.social, 14 followers, thanks slopbot

the source is reading their fucking AGENTS.md you dipshit

[davidgerard@circumstances.run]

@RogerBW @pndc @dysfun @FediThing @contrasocial yeah @zzt points out the fucking weird Motorola deal as the obvious proximate cause

[iain@kolektiva.social]

@davidgerard “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.”

Because every developers favorite part of using code analysis tools has always been sifting through all the false positives.

[davidgerard@circumstances.run]

@iain yeah that bit was very obviously someone pasting in a marketing excuse

[sharpcheddargoblin@reclusive.blog]

@davidgerard So how fucked up is /e/os with respect to LLM use? GrapheneOS is out of consideration, and I considered them to be the best de-Googled Android option, unfortunately.

[barubary@infosec.exchange]

@iain @davidgerard Reminds me of the C standard, which requires a conforming implementation to output at least one diagnostic for invalid code, but says nothing about valid code. So if your compiler simply prints "your code is bad" in all cases, even if the code is fine, it is conforming.

[mahryekuh@hachyderm.io]

@iain @davidgerard@circumstances.run This may be me personally but this approach feels beneath me.

I did not spend more than fifteen years honing my craft to be degraded to a babysitter for someone's poor quality tool.

[toxy@mastodon.acc.sunet.se]

@iain @davidgerard I’m no coder but doesn’t that suggest the developers should just craft the output themselves if the vibe output is shite?

[derivativethoughts@mastodon.social]

@davidgerard god fucking dammit! The whole appeal of this project was that commited experts would patch everything. What's even the point?

[dzwiedziu@mastodon.social]

@davidgerard
“I read your AGENTS.md” diss