• 0 Posts
  • 18 Comments
Joined 6 months ago
cake
Cake day: April 8th, 2026

help-circle










  • It also doesn’t really define ‘vibe code’ the way that it is generally understood by developers. Lots of devs use LLMs to do the busywork parts of development without actually vibe coding. It’s when you don’t understand what your code does that it becomes ‘vibe code’ - i.e. you’re relying on the vibes rather than understanding the code itself to determine if it’s good enough. Under that definition, where the prompt typically isn’t detailed enough to be considered a significant creative work and the person doing the prompting not only does not - but cannot - understand what it is doing, vibe code is NOT copyrightable, full stop.

    If it gets included in a larger work that doesn’t fit that definition, then sure, the whole is copyrightable, but then it’s just chunks of vibe code, not a vibe coded product - and the contribution in the form of a pull request is not. It is public domain.





  • I will pay extra for devices that don’t spy on me. There’s a market for it, and I’m the target audience. If I don’t fork out for devices that respect my privacy, they won’t exist in the future, and I can kiss goodbye the chance of ever having a full suite of devices that aren’t constantly selling every moment of my life to advertisers and whoever else wants it.

    My next phone will probably run GrapheneOS. My car is a 2016 hatchback that I removed the OnStar module from myself. I don’t have Alexa, I don’t have a smart home, I don’t have a Ring doorbell. My laptop is a Framework that I’m strongly considering installing Linux on as its primary OS. Every computer I use has Firefox as its browser with multiple privacy-focused plugins. Your argument is shit and you should feel bad for making it. More devices that respect privacy is better, and just throwing your hands up and saying ‘They all do it, give up!’ is both idiotic and counter-productive.