Arvid E. Picciani

165 Followers
298 Following
241 Posts
I do https://kraud.cloud and other small business with positive intentions and negative balance sheet.
@davidgerard nay. LLMs are trained with basic ethics.

You, an idiot: ChatGPT and GPT-4 are enormous advances that raise real questions about whether computers have consciousness.

Me, a genius:

@mspro wird bestimmt ein Erfolg. So wie truth social und so. 🚀

@cyborgcabbage @nattiegoogie yes. Companies within the EU are in fact adding additional layers to delete-for-real to comply with regulations. It's just happening very slowly because enforcement is slow and fairly mild. But it'll happen.

Of course Facebook et all might not because idk loopholes or whatever.

@dalias @marcan good point, then let's maybe meet in the middle. Make it fail below 32bit and make it assume 0 above 32 bit. This works on little endian because the further away from the end of vararg, the more likely you get trash.

@dalias @marcan It's pretty clear the buggy caller intended to pass 0, so i think the fix should at least honor that intention. This is a very common bug for people used to C++ zeroing out optional args.

I still think the correct fix is to assume any number above ulimit should be ignored because it doesn't work anyway, so any legitimate code would have never worked.

@marcan @dalias you keep underestimating the popularity of userspace choices that don't match yours.

@dalias @marcan yeah sure, but i'm saying it could be done correctly i think.

upstream linux will figure it out i guess.

@marcan @dalias uh wait, why is there no middle ground?

i'm not sure why you used 1024 in your patch.

any number larger than ulimit would fail anyway, so it might as well change the api contract to specifically enforce that.

@azonenberg whats the current way to get a cheap reliable linux board? and "reliable" now also including "i can actually buy this chip"