Quest :ablobcatbongo:

Hello! I am an open source developer who stands for the things I love! 🏳️‍🌈 🏳️‍⚧️

Fuck AI :ai:
Fuck Capitalism :anarchopunk:
Fuck Cars :bancars:
Fuck Data Centers

- I am a professional Rust developer, and huge Rust advocate 🦀 .
- I self host a lot of stuff.
- I love doing research and hope I can do it full time one day!

#antiAI #noAI

Age: 20+
Pronouns: He/Him

Public Key

npub1ymd5rhr56wgc50exunsxqsggkq7puj2js4y5rjxsrer9qpa6h2yqv78adw

NIP-05 Address

corigan01_at_todon.nl@momostr.pink

Profile Code

nprofile1qqszdk6pm36d8yv28unwfcrqgyytq0q7f9fg2j2pergpu3jsq7at4zqprpmhxue69uhhyetvv9ujumt0d4hhxarj9ecxjmntqyg8wumn8ghj7mn0wd68ytnhd9hx2qg4waehxw309aex2mrp0yhx6mmnw3ezuur4vg5jrfq5

Publishing to

relay.momostr.pink

nostr.wine

relay.mostr.pub

Author Public Key

npub1ymd5rhr56wgc50exunsxqsggkq7puj2js4y5rjxsrer9qpa6h2yqv78adw

Show more details

Published at

2026-09-24T04:23:41Z

Kind type

0 Metadata

Event JSON

{ "id": "0498a0fea27f7ed43906fa5ad6f8b91fbd20aee3e445df9c051bafc0c2d74911", "pubkey": "26db41dc74d3918a3f26e4e0604108b03c1e4952854941c8d01e465007baba88", "created_at": 1790223821, "kind": 0, "tags": [ [ "emoji", "ai", "https://todon.nl/system/custom_emojis/images/000/590/755/original/071695a60f4bf174.png" ], [ "emoji", "anarchopunk", "https://todon.nl/system/custom_emojis/images/000/000/027/original/anarcho-punk.png" ], [ "emoji", "bancars", "https://todon.nl/system/custom_emojis/images/000/035/820/original/bancars.png" ], [ "emoji", "ablobcatbongo", "https://todon.nl/system/custom_emojis/images/000/393/592/original/45659f5143c538b9.png" ], [ "t", "noai" ], [ "t", "antiai" ], [ "proxy", "https://todon.nl/ap/users/116123075073157642", "activitypub" ], [ "L", "pink.momostr" ], [ "l", "pink.momostr.activitypub:https://todon.nl/ap/users/116123075073157642", "pink.momostr" ], [ "-" ] ], "content": "{\"name\":\"Quest :ablobcatbongo:\",\"about\":\"Hello! I am an open source developer who stands for the things I love! 🏳️‍🌈 🏳️‍⚧️\\n\\nFuck AI :ai:\\nFuck Capitalism :anarchopunk: \\nFuck Cars :bancars: \\nFuck Data Centers\\n\\n- I am a professional Rust developer, and huge Rust advocate 🦀 . \\n- I self host a lot of stuff.\\n- I love doing research and hope I can do it full time one day!\\n\\n#antiAI #noAI\\n\\nAge: 20+\\nPronouns: He/Him\\n\",\"website\":\"https://todon.nl/@corigan01\",\"picture\":\"https://todon.nl/system/accounts/avatars/116/123/075/073/157/642/original/07901df2d6122aed.jpeg\",\"banner\":\"https://todon.nl/system/accounts/headers/116/123/075/073/157/642/original/9ec11c384334a4ad.png\",\"nip05\":\"corigan01_at_todon.nl@momostr.pink\"}", "sig": "c6fdd1a03ad59ad1cce84a098fe49be374ed32036443cf6ddd03f22d533335ac34b03b9e09dc279293c60b9c6bad2230c2098cde81d092c9a008045e565c6b0a" }

Last Notes

2026-09-08 23:20:46 UTC

- reply

Hello again v2 lol,
I think that this is a valid concern and is something I am worried about too!
However, it is unfair to say that Graphene should contribute to the problem themselves just because everyone else is doing it. I think that while many dependencies are tainted, Graphene could still carefully manage it's own source.
We can bring up concerns with its dependencies's authors another time, however, we cannot begin without someone first taking a stance.

2026-09-08 22:55:41 UTC

- reply

Hello again,
Sorry your post is a little difficult for me to read, I will repeat your question to make sure I am not misunderstanding you.
> You say more AI generated code helps you detect it more often:
I am unable to find the study so I cannot claim it to be false definitively, but I will disagree with the following reasons:
- For many projects, AI code sticks out like a sore thumb due to its weird tendencies and behaviors. If those tendencies become ingrained in the project, how would you determine AI from not?
- Since these are indeed probabilistic models, you will notice they code like a stack overflow post. It doesn't always "correctly" fit into the project the way one might expect. It gives this weird off feeling, however, that relies on the project having good coding standards to begin with. Something that can be eroded by continuous use of AI.
Otherwise, I agree with your post. AI is very much like a slot machine and I don't know what long term use looks like. This is why I am concerned that a project like Graphene is so quickly adopting it. I just don't think we have enough proof or data to show its a healthy or productive thing to include in a project intended to be this secure.
If I disregard the ethics concerns, I could give Graphene a pass for using AI to exclusively pen-test their platform (no code generation), but I think allowing any code-gen is my real big concern here.

2026-09-08 22:21:01 UTC

- reply

Hello Laurage, and thanks for the response!
I think while not completely possible to detect all AI, I think the developers using it themselves in code creation brings up a bigger concern:
- The more one is exposed to AI generated code, the more that code becomes normalized within the project and the less likely you are to detect it in others.
- AI code removes the creative process of new novel solutions that might otherwise fix many issues.
- As far as I am aware, deskilling from AI happens quite quickly and its without ones own knowledge of it happening. I know the current developers are competent, but what's to say they will be long term? And what does that invite when we offload so much knowledge to the machine?
- I think AI invites too many edge cases that cause people to slip and invite the AI more and more until they are effectively not apart of the project themselves. Thinking you are immune to this problem only makes you more susceptible. AI is like a box of sirens.

2026-09-08 21:43:36 UTC

- reply

AI companies control what their bots do right? What if they tried to subtly place a vulnerability into graphene that your developers become too deskilled to notice? How do you know what is or isn't slop at that point? (We've seen nefarious PRs be accepted into the Linux kernel before AI, so humans cannot always be trusted to catch these types of vulnerabilities). I imagine the trust placed by the developers into these models only make this problem more of an issue.
- Who is the point of trust verifying slop from non-slop?
- Do you have extra security in place to test regressions imposed by AI models (that isn't an AI model itself)?
- What about the impending licencing issues? What if governments try to attack Graphene over illegally licenced code that was included from an AI model?
I think this is a bigger issue that needs more time to bake.