

Would the sandbox permissions in Flatpak be able to block this?


Would the sandbox permissions in Flatpak be able to block this?


Because Nyquil stops the coffin’.


The people who espouse such nonsense as “if you don’t use AI you’ll fall behind” believe that using AI will become an absolute necessity in the future, and that those who use AI now will have more expertise in using AI than those who don’t, giving them better prospects. Those same people end up saying “you’re just not prompting it right” when you point out flaws in the LLM’s responses.


Bots ruin the world.


Hackers. The movie is great, the soundtrack is greater.


to fix issues and errors
and create more issues and errors, like executing USB device names as root.
The cube thing from compiz had a similar effect back in the earlier years of Ubuntu.


The question is who is this useful for?
Anyone wanting to run FreeBSD services in OCI containers on a Linux host.


Respect is a two way street. I will provide respectful feedback for AI when companies start respecting my wish to not have AI shoveled into every system I use. Until then, the clankers can fuck off.
Six String Samurai.
“Nice tuxedo… nice tuxedo TO DIE IN!”


Not overall hostile, but there are hostile people. Make liberal use of filters and block lists, and your timeline will become friendlier.


and the only realistic way to achieve that is to make the people using their service reconsider.
So what exactly will naming the site achieve? If someone wants to boycott recaptcha (which I’m 100% onboard with, btw) they’ll just not comply with the captcha and leave the site when they encounter it. On the other hand, someone who would not otherwise visit the site cannot reduce traffic to the site by direct action. Telling their friends “don’t use that site, it uses recaptcha” is no more effective than telling them “don’t use any site that requires you to do QR recaptchas.”


Recaptcha is a service offered by Google. It doesn’t matter on which site the user encountered the QR code verification request - the problem is with Google (the company.)


Google. It’s their recaptcha service doing that. The QR code validation also gets rejected if you’re using a privacy oriented mobile OS like Graphene.


OP must be québécois.


What if this is the new normal? I reckon newer models won’t suddenly stop discovering flaws, right?
My (non-expert) impression is that what has been recently discovered is a particular category of flaws that had until now not been considered, and that’s why we’re seeing such a surge in found vulnerabilities: everyone and their grandmother is fishing across Linux subsystems for the novel pattern. The optimistic outlook is that there will be a saturation point where nearly all flaws matching this pattern have been found, and the incidence of new reports slows to a trickle.


Just wait a year or two and Google will kill Gemini on their own.
My career is already impacted by others using it, whether I use it or not. Those who rely heavily on LLMs produce worse and larger code, and those relying on it heavily are not the best in the first place. It’s turning -1x developers into -10x developers on account of them causing additional cognitive load on everyone else.
As for me? I don’t have FOMO. If I’m right and it’s a bubble that will collapse, then I’ll be better suited to weather it. If I’m wrong and LLMs are all they’re cracked up to be, then I will be able to get up to speed quickly.
It’s a stim. And yes, it helps.