phylogenetic analysis of AI slop 
GitHub
GitHub - sam-paech/slop-forensics
Contribute to sam-paech/slop-forensics development by creating an account on GitHub.
plantimals
rob@buildtall.com
npub1mkq6...r4tx
ΔC
https://drss.io -- bringing back the republic of blogs. and onramp for bringing RSS content, including podcasts, into NOSTR
https://npub.dev -- configure your outbox
https://npub.blog -- experimenting with reading articles in a client-side only setup
I made a little tool to publish a nip-65 relay list for you, the outbox style:
I think a lot of people onboarded before outbox was a thing and various clients implement this functionality, some do not. so why not a tiny app?
please let me know if you see any issues with it.
npub.dev
when using AI for coding, I find that it tends to add comments with wreckless abandon. just keeps adding them, before blocks of code, inline with things like //<---- this is the change, or commenting out code when it's trying to fix something. and all of that adds up and obfuscates the real code, making it hard for the AI to reason about the code, and sometimes making it impossible for the AI to even edit the code.
I have attempted to add linter rules, adding notes to the project rules, adding directives in each prompt even, but the comments just never stop.
can anyone confirm they see this same behavior? is it a problem for you?
has anyone been able to stop the AI from adding comments?
".... I take the prompts from the Product Manager AI, and give them to the engineer AI....
I'm a PEOPLE PERSON, GOD DAMNIT"
decentralized coherence networks