8,360 karma · joined March 21, 2014
goisser94@gmail.com
https://hobofan.com
Mastodon: @hobofan@toot.berlin (Twitter: @hobofan)
---
Currently building https://github.com/EratoLab/erato
At this point I'm not even sure if it can properly create a simple primitive solid.
Japanese car manufacturers were late to EVs, and in order to prevent a gap in the market where EV-first competitors can steal market share from them, they lobby the government to subsidize and create a new market segment in the form of hydrogen cars. There they have a head start via some latent research and more reuse of ICE car platforms. I'm sure the hydrogen division is well aware that they are doing research on a dead-end technology (at least for the automotive sector).
The exact same thing happened in Germany. In 2020 there was a huge push from politicians to push more hydrogen technology to distract from the fact that German car manufacturers were lagging behind, as well as general missed initiatives for renewable energy. Now, 6 years later those initatives are deader than ever.
I do think that self-reports on permission usage are a step in the right direction, and can also help in decentralized uncovering of unintended API access.
However I think with the recent pace of supply chain attacks, I think we'll be in for a rough couple months until a sandboxing system is added.
I am curious how well this works out in practice for the ecosystem, though. In my experience blanket scans have a good chance to produce false-positives (= CVE exists but doesn't apply to the context it's used in), so the scans need some know-how to interpret correctly, which can lead to a lot of maintainer churn.
I'm not sure that "Plugins will declare what they access" should be interpreted as a planned sandbox system. My (cynic) interpretation that it's an opt-in honor system, that would give a good overview about well-maintained plugins, but doesn't do anything to restrict undesired API access by malware.
EDIT: Net contributions seem to be $3bn/year (total, independent of tech) while loss for other EU countries due to corporate tax evasion is $6bn/year.
From some of the videos you can find of it on Youtube, the cigarette butt claim doesn't look believable. It can definitely leave smaller debris behind, and certainly won't pull lag bolts out of the ground.
My rough blueprint for introducing formatter or linter nowadys would be:
- Recorded knowledge share session around how to set up the tools for local use 1-2 weeks before the initial rollout, and outline how the process will take place
- On the day of the initial rollout send out a reminder + the recording again
- Do the initial PR
- Incrementally do the rest of the migration, and subscribe to the PRs that drag out the process
I had to introduce a formatter in a few sizeable codebases in the past (few 100k to few million LOC), and I always did it incrementally via a script that reformatted all files that are not touched in any open PR. The initial run reformatted 95% of all files. Then I ran the script every day for ~two weeks and got up to 99.5% of all files and then manually each time one of the remaining ~dozen PRs that were WIP for longer were merged.
Yes, because it throws all partial outages into one bucket, which is a dumb idea because the bigger a platform becomes with more loosely coupled components the more untainable high uptime number become.
Looking through the incidents, a good portion of them are regarding Copilot and Codespaces, two products I couldn't care about less. I do also have my regular run-ins with Github outages, but that website is just hyperbolic.
IPFS in theory has a similar model, but in practice I've mostly found that if the original seeder goes away, at least part of a dataset becomes inaccessible.
I'm not sure that this will actually solve the problem. This seems more like a facade for a move they wanted to do anyways.
The only real alternatives would be:
- Kicking off a deep research-like investigation for each simple query
- Introducing a trusted middleman for sources, significantly cutting down the available information (e.g. restricting Wikipedia to locked-down/moderated pages)
- Not having any information at all, as at some point you can rarely every verify anything depending on how hard your definition of "verify" is
There are more and more independent AI inference providers without VC backing that serve open weight models on a ~cost-plus basis that show that subsidies are not significant for AI inference.