So they believe that Democrats automatically means higher taxes for them, regardless of income level.

Should you manage to get them to consider the taxation would only target the wealthy, they are afraid the wealthy class will fire them due to the loss of money. Similarly afraid that stronger worker protections would just lead to the jobs going away. They think the benefits achieved by Democrats favor cities and rural areas don’t see their moneys worth. Now they didn’t spend that much money on taxes and they do get great benefit, but they see the cities get bigger stuff and that leaves an impression.

Speaking of jobs going away, they fear immigrants. Both on racist grounds and the general perceived increase in labor competition.

Fewer arms to Ukraine because they see it as wasting money on a cause that has nothing to do with them. More arms to Israel because they are afraid of Muslims.

Particularly dangerous as key people recognize this is a lot of people, but not the majority. So there’s a great fear that democratic voting means they would ultimately be marginalized. So they also are the party most inclined to game the vote however they can, mapping districts, limiting voting access, stalling absentee ballots.

What van are you thinking? Work vans do this all the time.

I think it was more how weird the downscale looked for that one, along with being posted next to AI generated ones.

Yeah, 3 out of 4 AI generated fodder and the 4th is using some weird downscale that manages to also give off AI vibes… I can understand the impression myself…

Well yeah… The electoral college consistently lets a minority opinion override the majority, so of course a majority want it done.

Problem is that minority that gets their way today aren’t going to yield if they can help it.

You are going to give them ideas…

Ironically, reinstall the whole system, make sure to add some CrowdStrike, SolarWinds, and Ivanti for security and management though…

Huge difference, Ukraine military operations were for a long time purely defensive, only engaging in their own territory. Now they are starting to target military facilities in Russian territory more with no evidince of excessive collatoral damage, which is still understandable. If Russia withdrew offensive forces, Ukraine would not be trying to ‘wipe out’ Russia.

Versus Israel where just tremendous indiscriminate operations are inflicting more ‘collateral’ damage than what would be considered understandable targets for deliberate damage. I think the world might have been pretty fine with surgical incursions against Hamas and Hezbollah, but Israel has not displayed that discipline.

Well, he might be on to something.

I’m studying world history for the first time and I’ve so far gotten to 1938 and while I know absolutely nothing that happened after that, so far it looks like this suggestion has worked with this Hitler fellow.

Resonates with my experience. A company that comes from nothing to be successful is likely to have a good leader. That hugely successful company that attracted the sharks and one of those managed to gain leadership? Bad times ahead…

I never really paid much attention to him, but to the extent I expressed skepticism about him folks would generally act like I was too cynical.

All well and good when ssh activity is anchored in a human doing interactive stuff, but not as helpful when there’s a lot of headless automation that has to get from point a to point b.

Problem they had was that ssh doesn’t really have any way to enforce details of how the client key manifests and behaves. They could ship out the authentication devices after the security team trusted the public key, but that was more than they would have been willing to deal with.

Rotating the passphrase in the key wouldn’t do any good anyway. If an attacker got a hold of your encrypted key to start guessing the passphrase, that instance of the key will never know that another copy has a passphrase change.

Meanwhile, my company has systems insisting on expiring ssh keys after 90 days…

Yeah, that localization was one of the reasons that was so well loved. The PSP redid all that and while still enjoyable, it wasn’t quite as compelling as the WD effort.

This article is an example where statistical confidence doesn’t help. The model has lots of data so it likely has high confidence, but it didn’t have any understanding of the nature of the relation in the data.

I recently did an application where we indicated the confidence of the output of the model. For some scenarios, the high confidence output had even more mistakes than the low confidence output

As I said, I’ve dealt with logging where the variable length text was kept as plain text, with external metadata/index as binary. You have best of both worlds here. Plus it’s easier to have very predictable entry alignment, as the messy variable data is kept outside the binary file, and the binary file can have more fixed record sizes. You may have some duplicate data (e.g. the text file has a text version of a timestamp duplicated with the metadata binary timestamp), but overall not too bad.

The bigger problem is […] trans […].

Such a transphobic statement.

I still have weird glitches where applications don’t seem to update on screen (chrome and firefox, both natively doing wayland).

Lack of any solution for programmatic geometry interaction. This one has been afflicted with ‘perfect is enemy of good’, as the X way of allowing manual coordinates be specified is seen as potentially too limiting (reconciling geometry with scaling, non-traditional displays), so they do nothing instead of proposing an alternative.

The different security choices also curtail functionality. Great, better security for input, uh oh, less flexibility in input solutions. The ‘share your screen’ was a mess for a long time (and might be for some others still). Good the share your screen has a better security model, but frustrating when it happened.

Inconsistent experience between Wayland implementations. Since Wayland is a reference rather than a singular server, Plasma, Gnome, and others can act a little different. Like one supporting server side decorations and another being so philosophically opposed to the concept that they refuse to cater to it. While a compositing window manager effectively owned much of the hard work even in X, the X behavior between compositors were fairly consistent.

I’ve been using Plasma as a Wayland compositor after many failed attempts, and it still has papercuts.

Thing is that they could have preserved the textual nature and had some sort of external metadata to facilitate the ‘fanciness’. I have worked in other logging systems that did that, with the ability to consume the plaintext logs in an ‘old fashioned’ way but a utility being able to do all the nice filtering, search, and special event marking that journalctl provides without compromising the existence of the plain text.

Uh… Sounds like it’s not really system’s fault, your setup is just terrible.

I don’t know his specific issue, but the general behavior of systemd going completely nuts when something is a bit ‘off’ in some fashion that is supremely confusing. Sure, there’s a ‘mistake’, but good luck figuring out what that mistake is. It’s just systemd code tends to be awfully picky in obscure ways.

Then when someone comes along with a change to tolerate or at least provide a more informative error when some “mistake” has been made is frequently met with “no, there’s no sane world where a user should be in that position, so we aren’t going to help them out of that” or “that application does not comply with standard X”, where X is some standard the application developer would have no reason to know exists, and is just something the systemd guys latched onto.

See the magical privilege escalation where a user beginning with a number got auto-privileges, and Pottering fought fixing it because “usernames should never begin with a number anyway”.