Ask HN: What's slop? what's AI written text and why read/not read?
news.ycombinator.com/item?id=49289341#49290428
Any conversation
I got jumpscared by the moon rising because itโs visible from where Iโm sitting and itโs huge.
I love full moon. It does something to me.
โฆ
i dont think its all talk, these are smart people that have been in ai since the 2000s, and they raise good points. current incentive structures are very dangerous long term
they too have every incentive to exaggerate because they are selling safety and/or books on the topic. I donโt believe we wonโt see it coming. Any issues that will manifest will be very visible and weโll have plenty of time to mitigate their impact.
they could be making a lot more money by just working at ai firms i fear. the thing that got me worried the hacking incidents lately, huggingface etc.
if the capabilities consistently outspeed the development of safety measures, and if the private arms race logic continues, i dont think this is a good spot to be in long term
@kapankatsuragiprofilefollow
I may know more about Disney History and trivia than you. Maybe, I dunno.
I write about pop culture on Super Review Time.wrote:
I may know more about Disney History and trivia than you. Maybe, I dunno.
I write about pop culture on Super Review Time.wrote:trying to revive the blogging golden days. recommend some blogs with rss feed about game, movie reviews, and animation. or comic strips, traditional or webcomic.
ennek a laptopnak mindegy mรกr szegรฉnynek, annyi minden tรถrtรฉnt mรกr vele, most telepรผl rรก a Gemma 4 26B A4B QAT, az eredeti tervek szerint, amik lehet, hogy nem is a mi terveink, de arrรณl mi mรกr nem nagyon tehetรผnk, mert a kรถrรผlmรฉnyek รกldozatai lettรผnk
This laptop doesn't matter anymore, poor thing, so much has happened to it, now Gemma 4 26B A4B QAT is being installed on it, according to the original plans, which may not have been our plans, but there's not much we can do about it, because we've become victims of circumstances
Really glad to be using Haskell for work - especially in today's climate with agentic coding.
Our team uses containers to keep our development environment consistent across team members, though, and most agent sandbox approaches want to either offload your work fully to the cloud or they want to sandbox the agent harness process itself.
We're not ready for full cloud based development (yet?) and sandboxing just the agent doesn't work for us when the agent needs to run docker.
... because letting the agent run docker gives them a too-easy escape hatch from their sandbox.
So we're currently stuck with using VMs. This turns out to be tricky but seems do-able.
My current approach is to provision a VM image and use Incus for the execution. My main goal is to keep my current workflow of local/non-agent dev working seamlessly and share the source with the VM/agent.
This means sharing my working dirs with the agent VM but overlaying artifact dirs from VM-owned block devices so we don't take too big of an IO perf hit.
I also don't want the agent to be able to
git push so that means we need some quirky git config to rewrite origin paths and thread through some agent specific PATs ("thanks" GitHub) for read-only repo access. These ALSO need to be threaded through to the development containers - they need to clone private repos.... in the end, this seems to work but I haven't lived with it for long.
There are still some quality of life issues to work out, but I think it'll work out.
At this point, I've removed all coding agents from my host - and that's nice.
Curious, why does using Haskell make a difference here?
It's tangential to the sandboxing topic, really. I started the first post with a broader intent in mind and then elaborated on the sandboxing setup I'm working on.
For AI-assisted coding, though, it's nice because Haskell provides a lot of feedback earlier in the development process compared to lots of other languages. It tends to work once it compiles (obviously not all the time).