edelbitter

Ubuntu is not really targeting multi-user any more. Security update installation is deliberately delayed for all users, until at some point all unprivileged users ended all processes launched from the vulnerable snap image. (Firefox RPC breaks when you replace the binary, so having to reopen your browser to keep opening tabs simple because security upgrades were applied in the background would be inconvenient)

This is much bigger than subsidies. IONOS is already making serious money in selling "we host FOSS for you" to both users and (though generally: small) companies. They can expect to gain substantially greater revenue from acquiring larger commercial and municipal/federal customers.. IF the full package attains sufficient interoperability to withstand the usual anti-competitive tactics.

Has there ever been a GDPR fine that actually exhausted all applicable legal challenges within a sufficiently short delay from initial violation to actually matter?

> If you don’t use Copilot this will not affect you.

How does this work for a private repository with access granted to additional contributors? Which setting is consulted then?

> dependency resolution. conda could take 30-60 minutes

Quite literally this is what first raised the alarm bells for me. Dependency resolution complexity is more of a symptom. If that delay ends up being the point where Ops finally agrees that things have gone very wrong, then fixing that delay is not really helping hire the maintenance folks that can make those dependencies.. well, "dependable" again.

Have you looked at the .github/ folder of any actively developed python packages lately? It has become difficult to find one where there isn't a few interesting people with code-execution-capable push/publish/cache-write access somewhere along the blown up transitive dependency/include chains.

Its weird that still so many consider bug triage a problem to be circumnavigated, somehow in the way of "actual" contributions. Those are actual contributions! Even if they never make it into structured documentation or even python code. And especially so since that work can less usefully be augmented with newly available tool use.

A number of times now, I have found real value in someone just dropping into the bugtracker to restate the bug description in clearer terms or providing a shorter reproducer. Even if the flaw in Django had been fixed right away, I would not have pulled patches from master anyway. So the ticket comment was still a useful contribution to django, because I could use it in resolving the issue in how my software triggered it.

This is not a regulators move. This is the industry slightly adjusting their recommendations to parents. Will this change anything? Maybe it will help the industry avoid being targeted by actual regulation.

>whatever that library is called

https://news.ycombinator.com/item?id=47259177

To complete your analogy: To this day there are humans who have never in their life exceeded 300km/h outside of an airplane. Mostly people in places that had become used to driving. Used to subpar travel times, safety, efficiency and cost. In hindsight, those that saw the horses swapped for electric ones with the carriages mostly unchanged should have been more protective in their transport planning. Could have saved us from the 110 year detour that scarred almost all urban centers.

For commits you author.

Kernel guidelines now have a more verbose section about tagging: https://www.kernel.org/doc/html/latest/process/submitting-pa...

One particular chasm to keep an eye on, possibly even more relevant than Ubuntu using Rust: When it comes to building important stuff, Ubuntu sticks to curl|YOLO|bash instead of trusting trust in their own distributions.

https://github.com/canonical/firefox-snap/blob/90fa83e60ffef...

Mozilla suggests policies [1] (which, in turn are capable of default-setting or enforcing most prefs and has proper release notes) and has removed a bunch of pages that previously recommended directly editing prefs.js or shipping user.js (which had been changed in backwards-incompatible ways before when the parser was swapped).

[1]: https://mozilla.github.io/policy-templates/

To be fair, Mozilla-affiliated developers have accomplished some serious cleanup in recent years. New & redesigned features are fake tabs with special permissions instead of that unholy intertwining of web standards and local UI in C++. Storage is almost-proper sqlite3. Dynamic linking against system libraries old&new just works(tm). Even the vendored Rust packages more or less build fine, now even across multiple compiler versions. Plus, AMDs new-ish CPUs with ginormous L3 brought recompile (and thus, bisect) times to almost reasonable levels, so that is not as pressing of an issue any more. I would guesstimate only 25 years left at the current speed till Firefox can be considered maintainable again.

Its not just that each new "feature" is unnecessarily difficult to disable, and already active-with-privacy-side-effect by the time you notice.

Most new "features" are by now covered by an existing setting and/or policy. Yet I recognize a pattern of introducing new "but did you opt out of THIS NEW thing?" or "but did you opt out of VERSION TWO of this previously rejected thing?" setting/policy. It has become unsafe to upgrade to new Firefox releases, because each one will disrespect previous user choice in another unexpected way.

This new "please accept cookies and scripts to prove you are running Google Chrome without Adblockers" Internet does not exactly look like mission accomplished to me. And that is before we even get to the part of the Internet that goes straight to "please run this Android app so we can ask Google who truly owns your device".

If Mozilla was not busy "offering" (renamed the no-thank-you setting once again) so many "experiences" they could be doing much of the same stuff they did back in the day.

I sometimes use lwn.net as an exemplary showcase of things non-tech journalists should learn (e.g.: add references whenever paraphrasing material some or all readers might have direct access to)

As long as grid upgrades & maintenance continue to work reasonably well across western Europe, bad examples from the US are not particularly worrying. Economics of scale still very much apply; there is a point in maintaining expensive grid infrastructure. Especially so when using it to improve other expensive infrastructure, such as electric high-speed passenger rail.

I would love for steam to offer even the complement: Only distribution & SSO services, so I can have fast downloads and quick non-replayable-auth for games I buy/subscribe elsewhere (not subject to steam peculiarities about squeezing out maximum price for each region by purchasing power).

Of course, that would need to have a wildly different fee schedule than when they carry major legal & reputational risks plus more significant customer support volume.

One would expect the results to be highly correlated to corrected vision which is all over the place.. but they get suspiciously tightly grouped results.

Did they maybe not measure how many pixels we can see.. but rather how laughably bad COTS IPS are at contrast, as the examined pattern approaches their resolution? I wonder what happens if you repeat that with a reasonably bright 16K OLED.

Bernstein also published a simple checklist [1] of what people are likely to do wrong if not ruled out by design. Bullet point 2 on that list was:

> Your implementation leaks secret data when the input isn't a curve point.

[1]: https://safecurves.cr.yp.to/

Having your customers suddenly require proprietary machinery (only sold/licensed by you) to unlock the full potential of your upgraded product line.. does seem compatible with the SF startup way of thinking.

The almost-superset relationship of the respective non-waivable human/employee/consumer rights, and the weak enforcement of a level playing ground in each market.

If you want to have competitive business both sides of the pond, the logical choice is to put the money on the American side and achieve ROI before the EU dishes out noteworthy fines for non-compliance. In maybe 10 years when you have outgrown those sums. Much cheaper/easier than the other way around: build a company in Europe and to European standards.. and then try to make it skip all the costly procedures it may legally skip when doing business with/against Americans.

Replace "leading LLM" with progressively more evil things and see at what point the "if they exist, they better be European" logic stops seeming logical to you.

I can subscribe to the people I want to keep up with just fine. I do not need alternative ad-money-fueled intermediaries that get to decide what to insert into and remove from my feed. If there are no indefinitely growing profits to be made there, that is perfectly okay.

Can't tell if any Americans call it that, but it is widely known by the name https://en.wikipedia.org/wiki/The_Hague_Invasion_Act in Europe.

It actually makes things a easier for both blocking and allocating (e.g. VPS hoster) side.

Once the "oh no, we can't afford that many unique allocations" excuse is away, algorithms that enforce quotas for every prefix size at the same time (with no excuses for CGNAT weirdness) stop being too ruthless.

You can distribute your addresses as needed, and I can track successful and failing attempts - at whatever distribution scheme you use. E.g. group your "unverified" or "trial" accounts at a larger prefix size, so they get each other blocked - but not your paying customers.

> An exception isn’t just another event. It’s your code telling you it failed, in a specific place, with a specific context.

No! The other way around! All the other events should have context as well. I want to cry every time when I get a random warning-severity log that may or may not indicated something I need to look into.. without collecting the context which is collected on error-severity logging.

So the text was truncated? What? Where? Why? (don't truncate passwords before comparison, please!?) So the kernel logged some WARN dump? In response to what operation? Does only the 6.12 do that, or am I receiving this one from 6.14 machines as well? So the library says the "update()" method is deprecated? Which one of 10 update() methods in that library? Called from where?

Well then go check if you are for some reason using any of the other surprise features [1], like honoring the CURL_CA_BUNDLE env variable, or not honoring the PROXIES env variable if REQUEST_METHOD is set.

1: https://requests.readthedocs.io/en/latest/api/#requests.Sess...

Wait till you see the cPython stdlib email parser..

Any programming language these days should ship a decent rfc5234 API in the standard library, so you do not get these kinds of problems in slightly different fashion for each and every library/program.