Post
Remote status
Context
16@sun@shitposter.world Where is the source code?
@sun@shitposter.world I spot 20 emdashes in the tiny readme file and you didn't even add the .claude folder to your gitignore.
Also I can't read what license your repo uses without being required to make an account on your forge.
0/10 vibecoded retroslop
rad:z2gAKC6ESt5ZBV419uVPf2vFtEHCT
I use Radicle now because scrapers I have to lock down gitea
@sun@shitposter.world You honestly even did retroslop wrong because it is a javascript based single page app. The reason people like retroslop is because it was simple and there was no client side code, just pure serverside rendered HTML using something like PHP. This isn't even retroslop it's just aestheticslop.
@sun@shitposter.world That's not the point I am trying to make here.
@lain@lain.com @sun@shitposter.world I'm not very happy with seeing my long term mutuals promote their vibecoded garbage on the timeline. I really don't want to have to block you guys. I want to coonvince you to actually start developing free software again.
@sun@shitposter.world @lain@lain.com The problem is that output from LLMs currently has a legally ambiguous status. You can not risk integrating it into any existing free software right now, so that's why a lot of projects, with some exceptions, choose not to allow it or heavily limit its usage only to specific tasks.
And on a personal note I think obvious LLM output is extremely tasteless. Seeing someone not even use some effort to at least even write their own README file makes me cringe. I always compare it to the same type of feeling you get when you see a corporate logo which uses Comic Sans.
@sun@shitposter.world The risk for free software projects is actually the biggest, proprietary software can not be investigated that easily because their source code is secret.
As much as I appreciate you adding a proper copyleft license for this project, this unfortunately this does not matter much. The risk that your LLM pulls in code from other free software projects with an incompatible license is very minimal.
A much greater risk is that the LLM pulls in code from a proprietary software project. Because guess what? LLMs aren't trained from just from free software repositories obviously. Every person around the world that is using Cursor, Claude, Copilot, Codex, etc. while working on proprietary software projects is feeding their proprietary repositories into their ever growing training data set.
Replies
1