Tootfinder

I’m constantly accidentally resizing windows on my iPad in iPadOS 26… for the love of Steve Jobs’ turtleneck sweaters Apple, bring back Split View.

This is only a problem for Reddit as long as the spammers don’t pay. The “solution” will be a paid program for “product placement” or something, and presto, they become valued customers.
The future’s so bright, it burns my eyes.
https://9to5mac.com/2025/06/26/r…

The EU-US deal is a steaming pile of shit.
It looks like it's going to have to be the citizens to do the whole work, here, as the politicians proved to be worse than useless.
Borrowing a phrase from the Canadians, elbows up.
https://ec.social-network.europa.eu/@E

European Commission (@EUCommission@ec.social-network.europa.eu)
Attached: 1 image The EU-US deal restores stability and predictability for citizens and businesses on both sides of the Atlantic. It secures continued access for EU exports to the US market, preserving deeply integrated value chains and safeguarding jobs. It provides the basis for continued collaboration. The deal sets out the parameters of the EU-US trade relationship. It is the first step in a process that will be further expanded over time to cover additional areas and continue to impr…

Subtooting since people in the original thread wanted it to be over, but selfishly tagging @… and @… whose opinions I value...
I think that saying "we are not a supply chain" is exactly what open-source maintainers should be doing right now in response to "open source supply chain security" threads.
I can't claim to be an expert and don't maintain any important FOSS stuff, but I do release almost all of my code under open licenses, and I do use many open source libraries, and I have felt the pain of needing to replace an unmaintained library.
There's a certain small-to-mid-scale class of program, including many open-source libraries, which can be built/maintained by a single person, and which to my mind best operate on a "snake growth" model: incremental changes/fixes, punctuated by periodic "skin-shedding" phases where make rewrites or version updates happen. These projects aren't immortal either: as the whole tech landscape around them changes, they become unnecessary and/or people lose interest, so they go unmaintained and eventually break. Each time one of their dependencies breaks (or has a skin-shedding moment) there's a higher probability that they break or shed too, as maintenance needs shoot up at these junctures. Unless you're a company trying to make money from a single long-lived app, it's actually okay that software churns like this, and if you're a company trying to make money, your priorities absolutely should not factor into any decisions people making FOSS software make: we're trying (and to a huge extent succeeding) to make a better world (and/or just have fun with our own hobbies share that fun with others) that leaves behind the corrosive & planet-destroying plague which is capitalism, and you're trying to personally enrich yourself by embracing that plague. The fact that capitalism is *evil* is not an incidental thing in this discussion.
To make an imperfect analogy, imagine that the peasants of some domain have set up a really-free-market, where they provide each other with free stuff to help each other survive, sometimes doing some barter perhaps but mostly just everyone bringing their surplus. Now imagine the lord of the domain, who is the source of these peasants' immiseration, goes to this market secretly & takes some berries, which he uses as one ingredient in delicious tarts that he then sells for profit. But then the berry-bringer stops showing up to the free market, or starts bringing a different kind of fruit, or even ends up bringing rotten berries by accident. And the lord complains "I have a supply chain problem!" Like, fuck off dude! Your problem is that you *didn't* want to build a supply chain and instead thought you would build your profit-focused business in other people's free stuff. If you were paying the berry-picker, you'd have a supply chain problem, but you weren't, so you really have an "I want more free stuff" problem when you can't be arsed to give away your own stuff for free.
There can be all sorts of problems in the really-free-market, like maybe not enough people bring socks, so the peasants who can't afford socks are going barefoot, and having foot problems, and the peasants put their heads together and see if they can convince someone to start bringing socks, and maybe they can't and things are a bit sad, but the really-free-market was never supposed to solve everyone's problems 100% when they're all still being squeezed dry by their taxes: until they are able to get free of the lord & start building a lovely anarchist society, the really-free-market is a best-effort kind of deal that aims to make things better, and sometimes will fall short. When it becomes the main way goods in society are distributed, and when the people who contribute aren't constantly drained by the feudal yoke, at that point the availability of particular goods is a real problem that needs to be solved, but at that point, it's also much easier to solve. And at *no* point does someone coming into the market to take stuff only to turn around and sell it deserve anything from the market or those contributing to it. They are not a supply chain. They're trying to help each other out, but even then they're doing so freely and without obligation. They might discuss amongst themselves how to better coordinate their mutual aid, but they're not going to end up forcing anyone to bring anything or even expecting that a certain person contribute a certain amount, since the whole point is that the thing is voluntary & free, and they've all got changing life circumstances that affect their contributions. Celebrate whatever shows up at the market, express your desire for things that would be useful, but don't impose a burden on anyone else to bring a specific thing, because otherwise it's fair for them to oppose such a burden on you, and now you two are doing your own barter thing that's outside the parameters of the really-free-market.

After the transformation away from US services and products, it's time to go one step further.
As I have already announced, I will soon be replacing my Pixel 9 with Graphene OS with a Fairphone 6 with /e/OS from Murena.
Although I personally really appreciate Graphene OS and am an avid user, I'm not sure what the future will bring under the fascist Trump. As I said, he can force US companies to hand over data of European users or turn off their services for Europe with t…

Where Things Stand
Policy bill: After releasing a 940-page version of their sprawling domestic policy bill overnight, Senate Republicans on Saturday were seeking the votes to pass it, a key step in advancing President Trump’s agenda. They cut deals with holdouts in their ranks that they hoped would be enough to speed the bill through the chamber as early as this weekend.

Final cost: If Senate Republicans begin debate on the sweeping bill on Saturday, they will do so wit…

Trump Administration Live Updates: Republicans Hunt for Votes to Bring Policy Bill to the Floor
Senate Republicans were trying to find enough votes to pass their domestic policy bill, a key step in advancing President Trump’s agenda. Three Republicans have voted against opening debate.

So #Gentoo #Python eclasses are pretty modern, in the sense that they tend to follow the best practices and standards, and eventually deal with deprecations. Nevertheless, they have a long history and carry quite some historical burden, particularly regarding to naming.
The key point is that the eclasses were conceived as a replacement for the old eclasses: "distutils" and "python". Hence, much like we revision ebuilds, I've named the matching eclasses "distutils-r1" and "python-r1". For consistency, I've also used the "-r1" suffix for the remaining eclasses introduced at the time: "python-any-r1", "python-single-r1" and "python-utils-r1" — even though there were never "r0"s.
It didn't take long to realize my first mistake. I've made the multi-impl eclass effectively the "main" eclass, probably largely inspired by the previous Gentoo recommendations. However, in the end I've found out that for the most use cases (i.e. where "distutils-r1" is not involved), there is no real need for multi-impl, and it makes things much harder. So if I were naming them today, I would have named it "python-multi", to indicate the specific use case — and either avoid designating a default at all, or made "python-single" the default.
What aged even worse is the "distutils-r1" eclass. Admittedly, back when it was conceived, distutils was still largely a thing — and there were people (like me) who avoided unnecessary dependency on setuptools. Of course, nowadays it has been entirely devoured by setuptools, and with #PEP517 even "setuptools" wouldn't be a good name anymore. Nowadays, people are getting confused why they are supposed to use "distutils-r1" for, say, Hatchling.
Admittedly, this is something I could have done differently — PEP517 support was a major migration, and involved an explicit switch. Instead of adding DISTUTILS_USE_PEP517 (what a self-contradictory name) variable, I could have forked the eclass. Why didn't I do that? Because there used to be a lot of code shared between the two paths. Of course, over time they diverged more, and eventually I've dropped the legacy support — but the opportunity to rename was lost.
In fact, as a semi-related fact, I've recognized another design problem with the eclass earlier — I should have gone for two eclasses rather than one: a "python-phase" eclass with generic sub-phase support, and a "distutils" (or later "python-pep517") implementing default sub-phases for the common backends. And again, this is precisely how I could have solved the code reuse problem when I introduced PEP517 support.
But then, I didn't anticipate how the eclasses would end up looking like in the end — and I can't really predict what new challenges the Python ecosystem is going to bring us. And I think it's too late to rename or split stuff — too much busywork on everyone.

from my link log —
Representing type lattices compactly.
https://bernsteinbear.com/blog/lattice-bitset/
saved 2025-03-12 https://…

How does someone get their first job as a registrar? Summer public relations intern Jeehyung Pyo interviews Grace Burns for our blog about her journey from #UniversityOfGeorgia student to intern to (now) staff member.

Portugal incluído. Nice.
https://flipboard.com/@euronews/green-news-8pjijreoz/-/a-mxqHnas_TPiVM9JgFxN9Ug:a:89340020-/0

EU and six member states take ‘historic step’ by ratifying UN treaty to protect the high seas
The High Seas Treaty has the potential to bring about a significant shift in global ocean conservation efforts. The European Union and six of its …