And they'll reproduce virtually the same problems, because code was never a primary issue for output. Products reflect organizational problems, which AI can't solve.
While the sun has nothing to the with the rest, >500g a week of red meat is linked to intestinal cancer[1][2] and the billionaires should be paying more taxes if you asked me
Can't you just read "3 MB of RAM" as a large amount of some scarce tech resource and move on?
What if you got a on-chip compression algorithm so advanced that you can fit a world in a few MB and now with corporations controlling memory distribution, 3MB of high compression memory is highly valuable in the black market.
Would be nice to know how much of a role a sedentary lifestyle plays in it or if it puts everyone at risk regardless of other habits. Maybe this just means you need to do cardio several times a week to keep using THC.
There's a sub 2k tier with a single 3090 that's also serviceable. Run https://github.com/noonghunna/club-3090 with beellama, fast inference at the cost of a reduced 102k context window
This is a double edge knife. In this specific instance this was absurdely important for that kid's life, but this work both ways. What if the US authorities deemed it necessary to snoop on foreign governments and citizens for political reasons, now leveraging AI to do it at an industrial scale?
One thing is certain though is that assuring privacy isn't top priority for any cloud provider. Companies doing cutting edge, sensitive work should be wary.
I prefer my WV Up! infotainment system. It's just a dumb radio/media with a factory phone mount. The actual radio has physical buttons to navigate the config and modes and for everything else you use the phone's touch screen. With 6.8" phone screen it's really good.
A good middle ground would be to have physical buttons to interact with the manufacturer interface and the touch screen to interact exclusively with CarPlay
It's encryption both at rest and on transit. At rest there are levels of encryption, at object level or at filesystem level. E2ee for immich would mean the objects are encrypted and transmitting the data is encrypted. If the scenario is the server is stolen, you need encryption at rest. Even at FS level is enough.
If they steal your homelab, e2ee doesn't help, it's encryption at rest. E2ee is for rogue devices sniffing the network, which is more or less of a concern depending on your setup. I'd not have unencrypted traffic in my network if I had for instance those shady TV boxes.
It's becoming self aware, it's looking at itself and it's not liking what it's seeing. What if instead of the hollywoodean view of AI controlled dystopias, this is what we get instead, a big "nope, not gonna do it, sorry, and stop doing that btw, it bothers me".
I got lucky I think, in which the workflow of using agents is quite fun and addictive for me. But to audit anything you need a basic level of understanding of the underlying architecture, because we aren't there yet to just leave the agent working unattended and have plausible results, so any audit requires careful human involvement.
It's just that... Take this tiny project of mine I did for the fun of it https://gitlab.com/gabriel.chamon/thoracic-atlas-viewer. Basically went to an online interactive thoracic atlas and saw that the files were 404ing for download, but the visualization worked, so I gathered evidence and asked the agent to rebuild the archive for me. I still need to hack together an offline viewer, but it's amazing how much you can do just by having a general idea of what you need to do.
That's the spirit. I was thinking about this that you are saying in general, and agents now make for a case that it's often better for you to rollout your own specialized solution than to adopt a more generic project, so it's really important to know when not to waste time with a project like this.
I am currently doing DevOps work describing a legacy infrastructure as code and instead of buying into a paid or opensource tool, it's nicer for me to roll out my own because even though the task isn't trivial, I can custom tailor the solution exactly to how I'm going to use it to conduct the project.
You are welcome! My point stands though. Evidence of agentic loop is a bad proxy for code quality. If you are interested in a project you need to do the legwork, vibecoded or not.
It's indeed strange, it's likely some agent running amok. Doesn't look good indeed, but if I was interested in the project I'd still investigate the code itself
Took a look at the readme and seems coherent enough. A readme is also a technical entrypoint, no problem in parts of it being generated, specially if you have quick start, tables and loose documentation there you need updating.
Email: [email protected]