Alt. Profile @Th4tGuyII

  • 0 Posts
  • 133 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2024

help-circle

  • As others have said, a license is a legal tool that allows you to enforce how you want your program to be used.

    And in the case of FOSS this is a really big issue, because just publishing code doesn’t put it into the public domain, and leaves you open to exploitation by big companies.

    There are various types of licenses, but for FOSS the main ones are unlicensing and Copyleft licenses. Unlicensing essentially declares your code public domain, so anybody can use it for any purpose. Copyleft licenses are usually fairly permissive, especially for individuals, but obligate that any offshot/fork must also be made Copyleft - so prohibits close sourcing of your work.









  • For myself, it’s gaming consoles that I already own. Why go for the brand new when the things I already own not only still work - but have more functionality than they ever did before thanks to their respective modding scenes?

    Hell, just in 2025 the Xbox 360 got it’s first software exploit that works on all models - which was thought to be basically impossible outside of very limited scenarios like the King Kong Exploit…

    Forget soldering, forget RGH and JTAG - you can now have an almost cold-boot modded 360 with just a USB and 30-60 minutes of your time (and that’s not even counting the full cold-boot exploit teased by Grim Doomer on twitter).

    If you’ve got the right console, you could be sitting on a goldmine of fun right now and never know it until you try.




  • Do we need to remind people that LLMs don’t actually have a brain, and really, really shouldn’t be in charge of anything with real life implications?

    They aren’t actually doing a cost-benefit analysis on the use of Nuclear weapons. They’re not weighing up the cost of winning vs. the casualties. They’re literally not made for that.

    They are trained to know words, and how those words link in with other words. They’re essentially like kids doing escalation of imaginary weapons, and to them nuclear bombs are just a weapon particularly associated with being strong and deadly.


  • You mean to tell me that all these years of the UK Gov refusing to increasing the NHS’s budget to match inflation - in effect cutting their budget - has resulted in worse care outcomes, as it incentivises shorting on staff and cutting corners to meet targets?

    Writing rules and procedures can’t get you out of a problem caused by said rules and procedures not being followed due to external pressures.

    The UK Gov loves to fixate on dealing with symptoms rather than the actual problems behind them, then goes all Surprised Pikachu when their “fixes” don’t work. It’s been the same routine for decades now.



  • As I said in my reply directly to you, I don’t have an issue with vibe-coding itself.

    And I do understand that our interactions of the world are mediated by tools, but those tools are things we use to assist in our direct input.

    … And even independent tools like autocompletion requires me to actually type the words I intend to use. I have a direct input on what the autocompletion does, because its completing my words, not typing them for me.

    Prompting an AI to do something isn’t actually doing the thing, it’s managing another entity that does the thing for you. It’s a tool, but it’s a tool that thinks entirely for itself.

    So when vibe-coders say the “coded” something the AI produced, or vibe-artists say they “drew” something an AI generated, it grinds my gears - because its not the same, and will never be.

    If you code enough, if you draw enough, you get better at it. If you prompt an AI enough, you don’t get better at either of those things - you just get better at prompting the AI.


  • Yes, because I directly typed on that keyboard. My fingers pressed each and every key to make each and every letter of this text you’re reading.

    The keyboard is a tool to interface with a computer, in the same way you need a hammer to push a nail, a screwdriver to drive a screw, or a knife cuts through things.

    I didn’t ask somebody else to go hammer the nail, screw the screw, or cut the thing then take credit for doing the thing I didn’t do.

    Managing a process isn’t the same as doing the process, and in the same way, prompting an AI to make code for you isn’t the same as actually making that code, and never will be.

    Edit:

    I should say I don’t actually have anything against Vibe-coding itself, apart from the environmental implications of AI, and for personal projects I imagine it’s probably quite useful.

    What grinds my gears is when people say “they” coded something, knowing full well they didn’t write a single line of code. It’s like Vibe-artists saying they “drew” something DALI made.

    Its fine to do it, but just admit that’s what you did, rather than trying to take credit for a thing you didn’t do.



  • tinkerer built an app to control their own device with a PlayStation controller.

    who used Claude Code to reverse engineer the protocol

    Did they build it though? Sounds like vibe-coding to me


    the problem does not lie in the encryption used by the robot vacuum when communicating with its server, but that all the data is stored in plain text and can easily be read by anyone who gains access to the server.

    Having said that, this is atrocious!

    What’s the point in encrypting user data in transit if you’re just gonna leave it unencrypted at rest??

    If you’re going to store user data, at least have the decency to make sure its protected against malicious actors.

    It’s very lucky that the person who discovered it was a vibe-coding good Samaritan, rather than somebody willing to exploit it for money