

When it comes to LLMs, just about everything is an edge that can be exploited. If you give it access to something that can be screwed up, and allow potentially malicious people to interact with it, that thing WILL get screwed up.


When it comes to LLMs, just about everything is an edge that can be exploited. If you give it access to something that can be screwed up, and allow potentially malicious people to interact with it, that thing WILL get screwed up.


it’s got no problems with understanding that.
That’s because it doesn’t ‘understand’ things in the conventional way. It was trained to parrot its training data; it’s not actually working through the logic because its capability of using logic is highly constrained by its very structure and training. Why bother building something that can ‘think’ through the prompt when it’s way easier to just repeat what the internet has said on any given topic?
Sure, it can build a joke from first principles if it’s guided through the process, but you really have to guide it through the process - and even then, it’s going to be pulling from its training data like building blocks rather than truly being original about anything. It’s like rolling dice to make a joke; sure, maybe it resulted in a joke no one has told before, but is it truly creating something original?


I have a friend who wants to get one just so he can wrap it in a badly-aliased texture like the PS1 would have, just to riff on how much it looks like someone was scrimping for polygons when they designed it.


The real indicator of global warming.
Goto CAN be readable, it’s true.
The problem is that it’s easy to make code that is LESS readable; in order to prevent horrible unmaintainable spaghetti, it is forbidden nearly everywhere. A lot of coding ‘rules’ are really just ways to try to cut down on stupid coding practices by greenhorns and enforce code maintainability.
That’s because it’s not. It’s ignoring the meme format and just using the image without the context.
It’s pointing out the conflict between two coding ideals - first, reducing duplicate code so that you don’t have to reinvent the wheel and/or copy-paste code (which often means making calls to libraries) which is represented by the red penguin facing right, and second, wanting to reduce dependencies so that external variables are reduced (which would mean including code in your codebase that otherwise would be an external library call) which is represented by the blue penguin facing left.
The closer you get towards one ideal, the further away you get from the other.
IF and GOTO are the only flow control we need; everything else is for cowards.
Took me a bit. I was staring at it for a while thinking ‘What part of this is socially awkward?’


You’re ignoring the fact that you have to:
Crypto is many things, but it isn’t exactly as friendly as a credit card provided by your bank. Or PayPal, for that matter.


Nope, Monster Girl Academy got the axe too.
https://www.kickstarter.com/projects/krazykrow/monster-girl-academy-3-succubi-oni-centaurs-and-more


What? The thing we were all saying was going to happen is happening???
The most basic of models are all we have, because they are the easiest to make and the most general-purpose. The fact that they’re also the worst for reliability is swept under the rug.