deckiedan
Joined 14 years ago
Joined 14 years ago
It's a feature many apps implement in all kinds of ways already, especially games and social media stuff, so this, in theory, just makes it easier and consistent?
I'm against leaking our kids ages, and all the privacy and other concerns as much as anyone, but are we just getting overly angry too quickly on this one?
I get that it's a slippery slope too.
I fully expect both.
Also, given that AI content is still the responsibility of the person prompting, and not the AI company, then *surely* anthropic must be liable for this?
resist evil, but flee temptation.
Build willpower through disciplines, such as fasting, meditation, stillness.
Think about the larger value that a smaller temptation points to - junk candy food is an echo of the celebration food from a community event - the connection of enjoying delicious food together with others is something beautiful, so invest and look forward to that. How can we have more deep celebration times, and less binge snacking?
Life is complex!
Peace
https://derlien.com/ "Disk Inventory X"
regularly to find stuff to clean up.
If you want more proof, then you can take the essay, give it to chatGPT and say, "Please give me a report showing how this essay is written to en by AI."
People treat AI like it's an omniscient god.
But for people with extremely limited experience, LLMs offer a "create an app by talking!!" Zero understanding required. So they won't know to not leak user PII in JSON responses or have publicly writable endpoints or keeping private keys for external services server side and outside of the code base, etc... Let alone anything more complex.
There's still some glitches, occasionally the entire app code would get replaced by the function the LLM was trying to update. I could fix it by telling it that's what had happened, and it would then fill everything in again... Waiting for the entire app to be rewritten each time was a bit annoying.
It got the initial concepts of the app very very quickly running, but then struggled with some CSS stuff, saying it would try a different approach, or apologising for missing things repeatedly...and eventually it told me it would try more radical approaches and wrote online styles... I wonder if the single file approach has limitations in that respect.
Very interesting, very fun to play with.
I'm kind of concerned for security things with LLM written apps - you can ask it to do things and it says yes, without really thinking if it's a good idea or not.
But cool!
And anything which helps with the internet to be full of small independent quirky creative ideas, the better.
A one-off script to extract data for a report - potato.
A brochure website for a company that'll be replaced in 6 years, a small house (or even just an interior of a house, or kitchen revamp...).
It looks like a start of a packages.lock.json kind of tool for dependency resolution eventually?
Or am I missing something?
Is writing software closer to growing potatoes or designing the Sagrada de Familia, or writing the Clarinet Concerto?
I'd argue that writing a web browser is a lot closer in scope to writing a symphony than building a house - at least in audience and durability. In a house's life time, maybe 100 people live in it, and perhaps 2000 people visit it, but a browser, or a symphony, will have an audience of millions.
The market is massively smaller. The impact massively larger.
So... is this the same strategy as their "flatten the curve" early COVID policy?
Slow everything down because resources aren't available, hoping that the entire system doesn't go bankrupt and explode, because that would be worse?
Hoping that eventually some kind of solution will be available, and wanting to still at least exist when that time comes?