Disgusting. Do you take a bath in the sink, too?! smh

That was predictable.

But maybe I could see it coming because i have such great 4cite.

Sovereignty is the deeper moral right. It is any sovereign individual or group’s right to accept or reject an authority they choose to, and they must deal with the consequences of that (often implicit) choice.

A sovereign entity who is by choice or otherwise subject to a malign power will become a channel for that malign power, regardless of whether or not they intend to. And even when there is no malign intent, there can be fundamental disagreements between sovereign states.

It is very possible the individuals don’t support Russia. But aside from aiding and supporting defection, there’s not much we can do until Russia demonstrates a will to relinquish a hold on Ukraine, who has clearly demonstrated their sovereignty.

There are points of power (like code run all over the world) that are desirable targets for malicious actors.

So, those who are subject to a malicious foreign power, whether they are innocent or not, because they are subject to a power that is not innocent.

We don’t need to attack those people, but we need to deny the Russian state the capacity to affect those points of power where we can. They claim Russian citizenry, and so they are impacted by Russia’s choices, and the international responses to Russia’s actions.

There will always be something to pick at, and with the number of trolls on here to inflame and manipulate any legitimate concerns, i highly suspect the troll farms and related pawns would find something to bitch about.

The fact is, not everyone has the EQ to state the issue perfectly clearly in terms everyone can accept.

“No, do you really expect me to look past what Russia is doing? Absolutely fucking no,” is basically reasonable.

Wisely.

I mean, do you? This is a violation by Russia of another sovereign state. Thus, everyone in Russia is affected by the consequences of that action.

The Russian kernel coders, no matter their innocence, are subjects of a nation that can compel them to misbehave.

Now, if they were leaving Russia and defecting, that’s another matter, where they are pulling their individual sovereignty away from the Russian state.

So your advice is basically “come on, guys, you can resist russian aggression in ways that don’t involve conflict, stop the sanctions and side with Russia pls”?

No. As the instigator of this conflict, Russia can back the fuck down.

Sanctions have effect precisely because they are a broad tool.

Sorry that was such a bad argument that I did not even consider it being one.

Savage truth.

Then other countries should make sanctions on the US where it masters to them to do so.

He followed legal advice from lawyers and removed some russians from being kernel maintainers to comply with sanctions.

It’s not about punishing Russia, is admit preventing vulnerability to a country that has an ongoing effort to compromise infosec.

Not at all saying Israel doesn’t suck balls right now.

This isn’t exactly “can’t live without,” that would be HomeAssistant. But what I Immediately thought of?

Beyond All Reason

This is an RTS game in the spirit of Total Annihilation.

• labor of love
• fully 3d, including ability to rotate or raise/lower view
• tens of thousands of units without hardware lag for reasonably modem hardware (3-4 years old)
• all shots actively rendered, leading to:
• realistic friendly fire
• even air units can get hit by ballistic shots targeting land units (although odds are fairly slim)
• redirect-unit-to-dodge micro is effective in some situations
• meaningful terrain
• radar will have blind spots based on line-of-sight
• radar gives clear indicator of coverage during placement
• two factions, almost 200 units each, with tier 1, 2, and 3 units. A third (currently playable with a setting change) faction is in the works.
• crafty, non-cheating ai opponents
• free server hosting (!)
• active servers all times of day

The overall feel and balance of the game is great. The changes they make to balance are generally light and reasonable, and the game had a good community.

Fam and friends play together often.

Fair enough.

Honestly, it’s pretty normal for Linux. It’ll fracture until it becomes glaringly obvious that there’s a problem, and then it’ll get standardized, and the standard may be supported in the next version.

Ubuntu could have gone flatpak. They didn’t. Kde and gnome could have come to a common agreement about desktop-related stuff they have in common. They didn’t. So it goes. The real pain points eventually get fixed.

Better than external ones, I suppose.

Hold a sec while I insert this hyperactive thyroid. …just one more transplant…

Meh, it was ok on the ad front.

If I understand correctly, Wayland does provide better desktop security. At least two of the common issues are tied directly back to that.

Screen sharing apps, which need to access what one or more other apps are showing, and screen readers for the deaf, which need to access what text other apps are displaying.

Wayland intentionally recuses itself of these problems. That’s understandable, as these problems aren’t specifically in the realm of a display protocol. However, this has led to some significant problems.

Specifically, since there is a power and implementation void, and the Wayland crew haven’t stepped in or endorsed any particular way to fill it, each compositor/desktop library is now implementing it’s own means to achieve these ends. This leads to other problems.

You want to write software for X for some of these things, and regardless of the DE you’re working in, there are more fundamental ways to address the information you need. But if you want to do so with Wayland, there’s no “fundamental” layer to reach for, because it’s handled by the DE compositor and toolkits.

So you need to do it the KDE way, or the Gnome way, or the wlroots way, etc etc - and what if you want it to work with all of them? Simple: just code it multiple times and deal with multiple different frameworks, each with their own learning curves, restrictions, and quirks.

…by which I mean, “/s, jk jk, not actually simple.”

Really, my hope at this point is that maybe kde/plasma and gnome will standardize around wlroots (i.e., there is no hope).

So, failing that - maybe a single library for accessibility that does the work once (multiple times, but once), and is adopted and used by kde/gnome/wlroots, and a single library that does the same for display sharing.