I got so pumped for a twitter #spaces on #vibecoding that I vibe coded this #vibecrap at https://VibeCrap.com ⚠️ Warning: Pain for your eyes, head, and browser ⚠️Source: https://github.com/profdiggity/vibe-crap

VibeCrap.com gobbles memory, freezes tabs, and generally reminds us that coding can go very wrong, very fast. It’s educational parody, not production code. Treat it like the cursed sibling of the Acid tests.

#VibeCrap might be a learning exercise. It might be a warning. It might inspire you to smear vibe crap all over the web. Make of it what you wish... you're gonna do what you want anyway, and we're not your parents.

Features include:
• Chaos Control Panel
• Layout thrashing + forced reflows
• Node spam into the thousands
• Glitchy canvas animations
• Mutation observer meltdowns
It’s a Hall of Shame for bad practices.

Insecurity Demos:
• Fake XSS
• Clickjacking
• CSRF auto form
• Cookie flags gone wrong
• Open redirect
• Prototype pollution

These demos are safe and purposefully limited, but they're proof that bad coding can lead to security nightmares.

Of course, the source code is published. Want to make #VibeCrap even worse? Fork it, add your awful ideas, and submit a pull request. https://github.com/profdiggity/vibe-crap

This project isn't malicious and the examples are limited and therefore "fake" - but the lesson is real. #AI prompt systems can spit out code fast and automated bots can fill the web with it.. whether or not it's complete crap.

Shoutout to the @ivycyber team for building the @privacysafe software, which is definitely not vibe coded. Like what we do? Check out our products and support our work: https://ivycyber.com