the internet loves grapheneOS, the secure AOSP fork that also makes Android nicely usable without the LLM crap
-
the internet loves grapheneOS, the secure AOSP fork that also makes Android nicely usable without the LLM crap
<yelling from out of frame>
…ah. this just in, grapheneOS has decided to start codegooning core apps and security fixes and now they’re exhaustingly defending doing that
> Many valid issues are reported in between the hallucinations and other nonsense.
oh I see, what a relief
> Attackers are heavily using AI models to discover vulnerabilities and develop exploits. For example, Cellebrite is heavily using it including developing frameworks for reverse engineering and vulnerability discovery.
gotta use the wrongness machine, no sorry, “frontier models” because the coptech adversary is using them and also mythic’s great at finding vulnerabilities til you find out you can do the same job without it. great! https://grapheneos.social/@GrapheneOS/117226938743085364
@zzt this seems important, but what does it mean?
-
the internet loves grapheneOS, the secure AOSP fork that also makes Android nicely usable without the LLM crap
<yelling from out of frame>
…ah. this just in, grapheneOS has decided to start codegooning core apps and security fixes and now they’re exhaustingly defending doing that
> Many valid issues are reported in between the hallucinations and other nonsense.
oh I see, what a relief
> Attackers are heavily using AI models to discover vulnerabilities and develop exploits. For example, Cellebrite is heavily using it including developing frameworks for reverse engineering and vulnerability discovery.
gotta use the wrongness machine, no sorry, “frontier models” because the coptech adversary is using them and also mythic’s great at finding vulnerabilities til you find out you can do the same job without it. great! https://grapheneos.social/@GrapheneOS/117226938743085364
@zzt well, I guess I can cross “try out graphene” off my todo list.
-
also, here’s how much you can trust that they’re only using it strictly for reviews:
https://circumstances.run/@davidgerard/117235031728518322
> The AGENTS.md talks about the bot writing new code. On the available evidence I don't actually believe they're not coding with it.
not that “only doing using it for reviews” gets good results. you end up programming the way the LLM insists you should anyway. reviewing like this is exhausting and quality goes straight into the toilet. most people just cognitively surrender to the bot after a bit. this is an extremely common methodology in professional code, and it’s the reason why half the software you use right now fucking sucks.
@zzt Graphene’s super weird, hyperdefensive & combative comms person replying in 3…2…
-
@zzt Graphene’s super weird, hyperdefensive & combative comms person replying in 3…2…
@distractal don’t forget the fans, the second worst part of using grapheneOS
-
the internet loves grapheneOS, the secure AOSP fork that also makes Android nicely usable without the LLM crap
<yelling from out of frame>
…ah. this just in, grapheneOS has decided to start codegooning core apps and security fixes and now they’re exhaustingly defending doing that
> Many valid issues are reported in between the hallucinations and other nonsense.
oh I see, what a relief
> Attackers are heavily using AI models to discover vulnerabilities and develop exploits. For example, Cellebrite is heavily using it including developing frameworks for reverse engineering and vulnerability discovery.
gotta use the wrongness machine, no sorry, “frontier models” because the coptech adversary is using them and also mythic’s great at finding vulnerabilities til you find out you can do the same job without it. great! https://grapheneos.social/@GrapheneOS/117226938743085364
@zzt "sorry phones, it looks like its scientific experiments for the lot of you".
Really feeling out of options for electronic devices that aren't built to spy on me for advertising 24/7.
-
J jwcph@helvede.net shared this topic
-
> That increase is despite adding features slowly down a lot. A massive monolithic kernel written in a memory unsafe language is a bigger liability than ever.
rust in the kernel is in the corner like “am I a joke to you”
it’s uhhh real rich that the AOSP fork suddenly has a problem with a massive monolithic kernel written in a memory unsafe language now that LLMs are on the table
and the solution is just LLMs, only that. not fixing the massive, monolithic, or unsafe language bits at all. making them much worse, in fact. thanks!
@zzt if they really cared about this they would have ship a phil-c compiled kernel version and say "hey this may kill your perf and battery life, but if state actors are actually after you it is worth it"
-
the internet loves grapheneOS, the secure AOSP fork that also makes Android nicely usable without the LLM crap
<yelling from out of frame>
…ah. this just in, grapheneOS has decided to start codegooning core apps and security fixes and now they’re exhaustingly defending doing that
> Many valid issues are reported in between the hallucinations and other nonsense.
oh I see, what a relief
> Attackers are heavily using AI models to discover vulnerabilities and develop exploits. For example, Cellebrite is heavily using it including developing frameworks for reverse engineering and vulnerability discovery.
gotta use the wrongness machine, no sorry, “frontier models” because the coptech adversary is using them and also mythic’s great at finding vulnerabilities til you find out you can do the same job without it. great! https://grapheneos.social/@GrapheneOS/117226938743085364
@zzt
I really want to see an analisys on the quality and severity of those Linux CVEs.And also even if you're keeping a codebase secure with slop extrusion, and it works (I am generous for a moment), you don't have to glee about it (see also “it's fine if you don't think about ethics” argument).
I maybe could stomach the argument of using the forest burning machine, so the people protesting the forest from burning would have a secure tool, but that goes out window on extruding new code.
-
the internet loves grapheneOS, the secure AOSP fork that also makes Android nicely usable without the LLM crap
<yelling from out of frame>
…ah. this just in, grapheneOS has decided to start codegooning core apps and security fixes and now they’re exhaustingly defending doing that
> Many valid issues are reported in between the hallucinations and other nonsense.
oh I see, what a relief
> Attackers are heavily using AI models to discover vulnerabilities and develop exploits. For example, Cellebrite is heavily using it including developing frameworks for reverse engineering and vulnerability discovery.
gotta use the wrongness machine, no sorry, “frontier models” because the coptech adversary is using them and also mythic’s great at finding vulnerabilities til you find out you can do the same job without it. great! https://grapheneos.social/@GrapheneOS/117226938743085364
TIL: "codegooning"
-
TIL: "codegooning"
@jamesbritt the codegooners keep telling me I can’t call what they do slop so I found an even more appropriate term: https://mas.to/@zzt/117225094752753839
-
also, here’s how much you can trust that they’re only using it strictly for reviews:
https://circumstances.run/@davidgerard/117235031728518322
> The AGENTS.md talks about the bot writing new code. On the available evidence I don't actually believe they're not coding with it.
not that “only doing using it for reviews” gets good results. you end up programming the way the LLM insists you should anyway. reviewing like this is exhausting and quality goes straight into the toilet. most people just cognitively surrender to the bot after a bit. this is an extremely common methodology in professional code, and it’s the reason why half the software you use right now fucking sucks.
@zzt sad to report the presence of AGENTS.md and CLAUDE.md in the main Rust repo. And it's of course paid for by the some of the biggest LLM peddlers who are also represented on the board.
-
Living in the woods is no longer viable due to enshittificaiton.
-
@ehproque @c0dec0dec0de @zzt The woods are burning.
-
@ehproque @c0dec0dec0de @zzt And then the Techbro's will find a way to install AI on Trees.
-
-
@ehproque @c0dec0dec0de @zzt And then the Techbro's will find a way to install AI on Trees.
-
the internet loves grapheneOS, the secure AOSP fork that also makes Android nicely usable without the LLM crap
<yelling from out of frame>
…ah. this just in, grapheneOS has decided to start codegooning core apps and security fixes and now they’re exhaustingly defending doing that
> Many valid issues are reported in between the hallucinations and other nonsense.
oh I see, what a relief
> Attackers are heavily using AI models to discover vulnerabilities and develop exploits. For example, Cellebrite is heavily using it including developing frameworks for reverse engineering and vulnerability discovery.
gotta use the wrongness machine, no sorry, “frontier models” because the coptech adversary is using them and also mythic’s great at finding vulnerabilities til you find out you can do the same job without it. great! https://grapheneos.social/@GrapheneOS/117226938743085364
@zzt
Their intellectual dishonesty and aggression rubbed me wrong from the first time I saw them communicate, so...I never used nor recommended it.
I was right to, it seems.
-
the internet loves grapheneOS, the secure AOSP fork that also makes Android nicely usable without the LLM crap
<yelling from out of frame>
…ah. this just in, grapheneOS has decided to start codegooning core apps and security fixes and now they’re exhaustingly defending doing that
> Many valid issues are reported in between the hallucinations and other nonsense.
oh I see, what a relief
> Attackers are heavily using AI models to discover vulnerabilities and develop exploits. For example, Cellebrite is heavily using it including developing frameworks for reverse engineering and vulnerability discovery.
gotta use the wrongness machine, no sorry, “frontier models” because the coptech adversary is using them and also mythic’s great at finding vulnerabilities til you find out you can do the same job without it. great! https://grapheneos.social/@GrapheneOS/117226938743085364
just in case you thought graphene was at all on our side, they’ve decided to reply to my threads on this with generic corporate bullshit that has nothing to do with any of the points I raised:
https://grapheneos.social/@GrapheneOS/117235876960852305
this is only technically a better look than their previous behavior of flying off the handle as soon as anyone challenges them, but the bar is in hell
realistically they’re doing this because they’ve just done something incredibly unpopular and are getting a ton of pushback against it that they’re not reading
also, generic corporate shit plays better when you’re in a partnership with motorola, a company lenovo owns
-
just in case you thought graphene was at all on our side, they’ve decided to reply to my threads on this with generic corporate bullshit that has nothing to do with any of the points I raised:
https://grapheneos.social/@GrapheneOS/117235876960852305
this is only technically a better look than their previous behavior of flying off the handle as soon as anyone challenges them, but the bar is in hell
realistically they’re doing this because they’ve just done something incredibly unpopular and are getting a ton of pushback against it that they’re not reading
also, generic corporate shit plays better when you’re in a partnership with motorola, a company lenovo owns
their other reply is so bad that it’s literally just a copy and paste of a summary of their posts in the thread *I was replying to in the OP*: https://grapheneos.social/@GrapheneOS/117235863204199402
this isn’t funny, projects only do this when they fuck up bad
-
their other reply is so bad that it’s literally just a copy and paste of a summary of their posts in the thread *I was replying to in the OP*: https://grapheneos.social/@GrapheneOS/117235863204199402
this isn’t funny, projects only do this when they fuck up bad
@zzt “but everyone ELSE is using the baby mincer clearly it’s fine”
-
@zzt “but everyone ELSE is using the baby mincer clearly it’s fine”
@GroupNebula563 @zzt graphene literally just linked the lineage AI policy as a whataboutery
