Geeks assemble, spin up an email server, an XMPP server, get your friends on it, and keep the user count under 1000.

you have the knowledge, use it!

Also fight these laws. But that'll be harder.

No, "considering a stake in" isn't seizing means of production, this is forcing the private sector to do their bidding, extracting riches as they go.
Those are very different things.

Seizing means of production looks very different.

you still need to set it all up. Have a server somewhere.
Harder than it sounds.

Or use something decentralized, like bitchat. that has its own can of worms.

> One thing I do know is that France says this year is cooler than the last. https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fclimatologie.meteocont... [meteocontact.fr]

That is not what this link says, like at all. Read the graphS . Its graphed per month, and your assertion is only valid until march. In april it's way up again.
The seasonal graph, only available for spring, shows an increase for 2025.

No no, you're behind on your playbook. Now you're supposed to ask about the Krasheninnikov eruption.
Oh wait, that might kick in only in a few months. /s

> some portable cooling system which I feel isn't hard at all to manufacture

Fremen stillsuits! Lets get cracking.

Comes with the year of birth...

Point 1 is way more complicated... Sorting out paths is the easiest, then you need to figure out dynamic linking/import hierarchies, and in the end you will have 2 distros in the same filesystem side by side. That's AppImage/Snap/Flatpak.

The second is a "devops" problem: developer, integrator and distributor should be separate entities. All three would constantly push and pull with different requirements.

Language repositories could be a thing, if they could be integrated directly into distro package managers, with a sane retention policy, and a common set of package sanity tests.
Paludis tried with perl or ruby, but found out that the language repository was using invalid yaml files everywhere, and it only worked because of a bug in the language yaml library.

I really hope for the day when pip can be taken over by portage.
It wouldn't be worse than pip itself (which has no way to specify build time dependencies, as I discovered with sqlalchemy, which failed to update because of an old GCC on the system)
I'd also like cargo to be taken over by portage, but considering rust doesn't do dynamic linking, the only use would be auditing the system.
ie the package manger warning you "firefox is using an old crate", but that breaks once again, because rust's crate dependencies are of specific versions.

In other words: We're creating a completely unmanageable mess...

To be fair, it does have some nice features.
One of my favourites is the while/for ... else control flow mechanism.

Akregator for me. https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fapps.kde.org%2Fakregator...
I just can't work with GNOME UX.

"Beautiful clean coal, I told my people never use the word 'coal' unless you put the word beautiful clean before it"

> What if Tiffany had simply done it on the, popular and quite standard for years, recording?

That's the entire point: she probably wouldn't have.
This would never have made it into any human made meeting notes, as it was an inconsequential joke, the acceptability of which rests solely on her peers in the meeting.

Some risks are dependent on who's in the bed with her...

Yes, software.

> the PM is the authority on site

In my case he was the mediator, when things became problematic, and heads started running a little hot, he made us all take a step back and better identify the question at hand.

And considering our clients were the C-levels, yeah, he dealt with those too, thank god...

TBH the best PM I had did only that, but really delivered. He knew which team to contact, where to request work to be done, got us into contact with relevant technical people...
Essentially he:
- coordinated work across teams (ie created dependencies of work and got someone allocated to do it)
- made sure technical discussions happened in a timely manner (was 3 steps ahead of current state of project), within scope (even though he understood at best half of what was discussed) and with the correct people present
- got time estimates and accounted for delays, so we basically were never "late" even though we hit setbacks.

Working under him was a breeze, and he was a really nice guy too.