Comment by yard2010
10 hours ago
How come such slop is allowed here, what value do these vibe coded zero shot "projects" add? Why not just post the prompt?
10 hours ago
How come such slop is allowed here, what value do these vibe coded zero shot "projects" add? Why not just post the prompt?
Seriously. When I first looked this project had been pushed the first commit two hours prior. Projects should be at least 3 months old or automatically removed.
Fwiw git history can be forged pretty easily. You can re-timestamp commits
But then that would have the downside of falsely blocking projects that were developed in private and then just pushed to Github (or any public repo). Like I always use my own, self-hosted Forgejo for everything by default.
If it's a project you actually care about and are actively working on it'll be just as good 3 months from now.
If it's something that'll be irrelevant in 3 months why should anyone care about it?
1 reply →
If you develop on your own private instance and then mirror to GitHub to release it then there will be 3 months of git history in the logs.
For the same reason that GitHub has a releases page for uploading binaries.
Convenience? Am I supposed to take the prompt and use my own tokens on it? Why should I have to do that?
Recruiters used to use the candidate's Github "sources" page for evaluating candidates as a kind of proof-of-work.
And recruiter agents still do.