Hacker News new | past | comments | ask | show | jobs | submit | tobias2014's comments login

I hope you bring that up as an example in favor on open-source, as an example that open-source works. In a closed-source situation it would either not be detected or reach the light of day.


In a closed source situation people using a pseudonym don't just randomly approach a company and say "hey can I help out with that?"

It was caught by sheer luck and chance, at the last minute - the project explicitly didn't have a bunch of eyeballs looking at it and providing a crowd-sourced verification of what it does.

I am all for open source - everything I produce through my company to make client work easier is open, and I've contributed to dozens of third party packages.

But let's not pretend that it's a magical wand which fixes all issues related to software development - open source means anyone could audit the code. Not that anyone necessarily does.


I was interested and looked at the actual patent: https://patents.justia.com/patent/4348422 (there seem to be multiple patent documents, but this one adds some explanation), and he writes "I have now surprisingly discovered".

https://tastydecafs.com/blogs/learn-about-decaf/co2-decaf further explains "The story of C02 decaffeination goes back to 1967. It was then when a chemist at Max Planck Institute named Kurt Zosel stumbled upon an interesting discovery. Zosel, like many other chemists, was using high-pressure C02 to remove individual substances from other mixtures."

It must have something to do with caffeine being an alkaloid, while coffee overall is acidic. So I suspect that this pressurized CO2 is able to dominantly remove such alkaloids... I leave the details to a chemist :)


To add some clarification: decaffeination is as old as 1903 (also Germany: https://en.wikipedia.org/wiki/Decaffeination)


But the parent comment is about CO2 decaffeination specifically, not decaffeination in general.


This is why I think that modeling elementary physics is nothing else than fitting data. We might end up with something that we perceive as "simple", or not. But in any case all the fitting has been hidden in the process of ruling out models. It's just that a lot of the fitting process is (implicitly) being done by theorists; we come up with new models and that are then being falsified.

For example, how many parameters does the Standard Model have? It's not clear what you count as a parameter. Do you count the group structure, the other mathematical structure that has been "fitted" through decades of comparisons with experiments?


You are using the word "fitting" rather loosely. We usually "fit" models of fixed function form and fixed number of parameters.

You are also glossing over centuries of precedent that predate high-energy physics, namely quantum field theory, special relativity, and foundational principles such as conservation of energy and momentum.


To fuel your cosmic horror: Some of the dots may even be galaxy clusters


Hahahahaha cheers, I had just forgotten about this and was going to sleep, but hey, what's a couple more hours of freaking out! :)


It looks like this is being discussed, with a complication of additional symbols that were introduced https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068024


Thanks for this! I found this URL in the thread very interesting!

https://www.nongnu.org/lzip/xz_inadequate.html


It is an excellent technical write-up and yet again another testimonial to the importance of keeping things simple.


The other comments here showing that the backdoor was a long-term effort now make me wonder just how long of an effort it was...


It seems like this was the solution for archlinux, pull directly from the github tag and run autogen: https://gitlab.archlinux.org/archlinux/packaging/packages/xz...


it's shocking how many packages on distros are just one random tarball from the internet with lipstick


I find the article quite confusing and unclear to be honest. Are there any other sources?

This is the original NYT article from 2018 https://www.nytimes.com/2018/12/18/technology/facebook-priva... "Internal documents show that the social network gave Microsoft, Amazon, Spotify and others far greater access to people’s data than it has disclosed."

Facebook promised E2E at the end of 2023.


Here's the source media is probably using: https://www.courtlistener.com/docket/18714274/klein-v-meta-p...

To be honest I found I got much better grasp on the whole debacle by just reading the court papers themselves.


> Facebook promised E2E at the end of 2023.

Wait, seriously? Like 4-6 months ago? Like, yesterday in terms of how long they haven't had it? Sheesh, a day doesn't go by that I'm not reminded of how happy I am to have dropped FB so long ago.


They've had it for years, it was just opt-in. More recently they've applied it to everything.


Is academia supposed to compete? I think the researchers wish for that, but that's not directly how government funding agencies see it. From a government's funding perspective the goal is to train tomorrow's workforce. People learn in academia and then transition and contribute outside. As far as agencies like DOE go, that is an explicit goal.


isn’t government funding for academia mainly grants for research rather than investments in teaching.


Recently talked to a DOE program manager. I confronted them with the question why we do things like machine learning or quantum computing in academia, when there's no hope in matching industry for those things. His answer was that from an official perspective this isn't the goal, but future workforce training for national interests and security. NSF might differ slightly, but I think this makes sense.


Is knowing the presence of something more valuable than knowing the precise absence of something? In my opinion both drive our knowledge forward and challenge our current understanding and development of models.


Or even follow the idea of Stephen Wolfram's hyper graph, where space dimension and time are purely emergent properties of graph transformations.

https://arxiv.org/abs/2004.08210


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: