I really like Scaleway too ! I went with them because Linode got bought and I thought, since I was moving my things anyway, let's go to a French provider. And I got a bad experience with OVH, so Scaleway it was.
But really, I wonder why it's not used more ? Price are maybe a bit high for some things ?
I asked myself the same thing, trustpilot is pretty rough on them and a lot of people tell you online to stay away from them. I also had very good support experience so far. Their shared TEM IP had some deliverability issues at times, but they seem to have cracked down on this recently. I am on dedicated IP now, so I can't really judge if there have been improvements.
They used to have competitive prices for a while, with their dedibox line.
I think they are not as well known. It’s a bit of a side project of the parent company, Iliad. They could benefit from heavy investments and some more aggressive marketing, but perhaps it’s not worth the risk and a slow but steady growth is what they prefer.
+1 for bad experience with OVH, their control panel is a mess (only the Italian provider Aruba is probably worse) and their backend is riddled with bugs. If something is broken in the control panel, the support team candidly invites you to do it via their APIs instead.
Another bad experience with OVH here. In fact not bad but catastrophic. They enabled 2FA without my consent and then demanded a signed letter on paper by post to let me back into my account. Their online customer service was beyond useless and the nightmare took weeks to resolve. This after I had been a loyal customer for years. Just when I was preparing to punish them by moving, my VPS went up in smoke at that fire in their Strasbourg datacenter. "Oops, our bad", went the email. Beyond parody. It's almost a surprise to me that this company is still in business.
With Hetzner now for several years without incident.
At that point, if you are not sure a data point is accurate, should you really display it ? You have no proof appart from "The LLM said it was ok" which is kind of poor.
I disagree with the idea that data must be accompanied by a guarantee of accuracy to be used or published. That standard would rule out almost all datasets for which the underlying data is not programmatically generated.
My guess is that this dataset is probably more accurate on the whole than many datasets used by the kinds of calorie-tracking apps that outsource their collection of nutrition information to users. But an analysis would be required.
Regardless, the only workable approach is to describe the provenance of your data and explain what steps have been taken to ensure accuracy. Then anyone who wants to use the data can account for that information.
That is one exception, and it's only because Huel reports that info since it's a fortified meal replacement product. The same way a multivitamin would have that info on its label.
But consider that OpenFoodFacts can't give you that info on just about anything else, especially not basic foods like "apples" or "tofu" or "chicken breast".
I'm not dumping on the project. It's really useful to have a database of packaged food labels. It's just not trying to solve this problem.
Hi, Pierre, Open Food Facts NGO co-founder. We have an issue to propose approximation of micro-nutrients from reputable database. Feel free to join the project and contribute your time/coding skills to help us solve this: https://github.com/openfoodfacts/openfoodfacts-server/issues...
Your other comment is too deep in the thread for me to reply, but just wanted to say I appreciate you checking out the project and commenting, and appreciate the many years of effort you've undertaken in this space. How OpenNutrition can work with OpenFoodFacts is something I have thought a lot about (I think MacroFactor set a great example) and it's certainly something I'll consider moving forward.
Firefox on iPhone is Firefox on iPhone, but it uses WebKit instead of Gecko.
Chrome on iPhone is Chrome on iPhone, but it uses WebKit instead of Blink.
The reason this is important for you to keep in mind is because Firefox is whatever Mozilla says Firefox is, and Chrome is whatever Google says Chrome is. There's no reason to suppose the iPhone version of some product should share any code with the Android version of the same product.