Hacker News: latable

New comment by latable in "Why are so many young people getting cancer?"

latable — Mon, 08 Jun 2026 20:32:03 +0000

Wrong about olive oil that never need hexane extraction. Hexane is used to do a second extraction of the residues from the first extraction, to increase the yield. Of course it is somewhat poisonous. It is done for most cheap olive oil ! When buying olive oil, you have to make sure it is extracted mechanically and not chemically, in France at least it is written as such.

New comment by latable in "Running local models on an M4 with 24GB memory"

latable — Tue, 12 May 2026 10:22:25 +0000

Not the person asked but on a medium bug that would span a few python files, I found the MOE be too enthusiastic trying things without trying to understand first the issue, when the dense model though hard and added debug statements to understand how to fix it. But the dense model is quite slow (Q4KM quant, MI50 32GB, llama.cpp, pi)

New comment by latable in "Original GrapheneOS responses to WIRED fact checker"

latable — Tue, 21 Apr 2026 21:28:19 +0000

I think this is the case of a lot of successful OSS. Intrigued people of all horizons comes and interact with few people building something meaningful, mostly on their free time, and expect to be welcomed as customers by the company spokesman. Torvalds had a famous way to express himself freely and hurt some feeling on the Linux mailing list, yet Linux is still a successful OSS project.

I would go on a stretch to say that people that express themselves naturally, without detour, are maybe more trustful than the usual silver-tongued corpo.

New comment by latable in "Original GrapheneOS responses to WIRED fact checker"

latable — Tue, 21 Apr 2026 21:01:41 +0000

What does it means to "behave well" for you in this case ?

New comment by latable in "Original GrapheneOS responses to WIRED fact checker"

latable — Tue, 21 Apr 2026 20:59:42 +0000

It looks like a very mature action to me: It certainly avoided the compromission of an OS that aims to be secure after all. It is not some windows OS with encryption keys sent to the cloud, so if security is compromised I fully expect targeted devices to break.

New comment by latable in "Original GrapheneOS responses to WIRED fact checker"

latable — Tue, 21 Apr 2026 20:51:21 +0000

Exactly. It was a bold and necessary move to defend the users and the project. Some users got bricked OSes, but had he handed over the keys it would have put those users at risk and would have destroyed the credibility of the project. Also, and as from what I understood from the GOS response he was not an employee of the company and had the ownership of his OS, and CopperOS would have been able to use their own signing keys but they never did which is strange, so even legally it looks like a "level-headed" response.

New comment by latable in "Old laptops in a colo as low cost servers"

latable — Fri, 10 Apr 2026 16:42:58 +0000

I would agree with you about autoscaling if ECC was enabled in every consumer computer :'/

New comment by latable in "Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised"

latable — Wed, 25 Mar 2026 10:35:12 +0000

So now we feel the need to add malware protection into the CI, like we put comodo on windows 7 and pray while surfing shady torrent websites ? It is pretty ironic that an extra tool used to protect against threats gets compromised and creates an even bigger threat. Some here talks about better isolation during development, CI, but the surface area is huge, and probably impractical. Even if the CI is well isolated, the produced package is compromised.

What about reducing the number of dependencies ? Integrating core functionalities in builtin language libraries ? Avoiding frequent package updates ? Avoiding immature/experimental packages from developers of unknown reliability ?

Those issues are grave. I see no future when those get rarer, and I am afraid they may wipe the open-source movement credibility.