Firmware on these is pretty tight. They’re usually using CC2510s or CC2530s. The CC2510 has a voltage glitch hack that you can use to attempt to read the contents via the DCOUPL capcitor, but it’s not very effective and you can only read a few bytes per attack.

You can see a github some tools some have created here. Eventually someone is going to read the firmware off theses and be able to hack them, it’s just a matter of time.

An extended US military campaign in Iran could be constrained by a munitions shortage

Lot of ifs for something that the US is known to prioritize above all else. What affordable food? Sorry, got to make missiles.

So why wouldn’t that extend to all those other things I listed?

There’s a fundamental difference between the action prohibited and the means by which that is carried out. We can ban drunk driving, now we can enforce that by arresting people driving drunk or shooting everyone who walks out of a bar that touches a car. The latter is extreme but technically does the thing we are after. If we murder everyone who walks out of bar drunk, we technically prevent drunk drivers.

That’s the issue. We are trying to make it where computers keep us in check. That’s a bad idea for sort of the same reasons why installing breathalyzers in every car would be a bad idea. We’re trying to paper over actual enforcement. So that way when there’s a failure we don’t have to blame law makers for making bad choices or law enforcement for not doing their job, we can just blame computers.

I just hope you can understand why that’s bad.

Like… The flock cameras. Made to be able to pinpoint the motions of criminals so that law enforcement doesn’t have to. That’s a great starting intention, but having cameras that watch everyone at all times, that’s bad. And I think you can understand why it would be bad.

Kids still drink, kids still vape, kids still get behind the wheel when they ought not to. It’s up to us humans to enforce our rules on other humans. And the more we forget that, the more we hand power over to whoever is controlling the computers or technical aspects or whatever.

If parents don’t want their kids watching porn, that’s a pretty easy fix that doesn’t require us to hand over critical functions of our computers to some 3rd party to, at some later date, do something we know not of.

Like goodness how is the bad aspects of this not obvious outright? Like how did we start getting to a point where we’re so blind to how all of this can go off the rails so quickly? All these are bad things for reasons that’s really complicated that might not fit in 5000 characters or less. But they’re bad. The whole having a computer verify age by scanning the barcode, what happens when that company signs off on a deal with health insurance? What would happen if the Kroger plus card data was sent over to your insurance provider? Everything you bought at the grocery store is something that your insurance provider has access to?

Like c’mon how are we not seeing this? It’s not about “kid should have access to porn”, it’s about how we go about enforcing the whole “kids shouldn’t have access to porn.” You have to understand, I’m making a statement not about the “ends,” I’m making a statement about the “means.”

We all seem to be always getting so caught up on the end goal that we forget to stop and consider the actual path we’ve selected. We’re so preoccupied with whether or not we can prevent something, that we don’t stop to think if we should reconsider how we go about it.

Please I’m begging you, there’s a really important point in this and we keep failing to see it, A LOT! Like, I’m glad everyone is starting to understand the dangers of having a Ring camera everywhere, but it’s so frustrating that it took a Super Bowl ad for it to finally sink in how bad an idea it is when a lot of people were pointing this out very early on with the Ring TOS.

I’m getting old and I’m getting tired that this keep happening, I don’t want any of us to be agreeing to something that’s got a pretty easy fix for it already, that’s got massive ramifications down the road if we go down the purposed path. It’s not ends, it’s the means, it’s the means. We keep selecting ones that have that really bad consequences.

I’m not saying kids should be handed porn that’s such a stupid take. I can do the exact same for your comment.

Parents shouldn’t take care of their kids, instead we should let the government tell them what to think, what to eat, who to hate, and who we should be praying to.

Do you see how brain dead your comment is?

We don’t want kids downloading bad stuff.

Then parents should keep an eye on their kids. Or just don’t give them full on access to the computer.

I hate that politicians keep trying to invent technology to do a parents job.

That’s comforting to hear. Thank you.

I mean, isn’t this what Gacha games basically are?

Just when I think California couldn’t possibly come up with dumber laws, they deliver yet again.

There’s genuine concerns they could be addressing but instead go after something that’s going to be near impossible for them to enforce.

Blueprints for homemade 3D printers exist that can be built with a pretty short list of parts from Digikey.

One can only wonder as to why that may be.

How does that change what I said? Remote X is massively more bandwidth hungry than all the others. I mean things like TeamViewer Tensor exist and from what I’ve done, is massively stable. RHEL works perfectly for it. So I don’t want to hear this can’t get a commercially supported… There’s tons of vendors that will thin client for you.

X is a terrible protocol for modern widgets because modern widgets do their best to work around X, that’s literally in the code. Look at GTK or Qt, both are actively trying to avoid working with X when it can and just render directly, because in every metric, it’s better to work directly with the hardware than to go through some slow middle layer that just spins and wastes cycles.

Heck, even the X developers have left X, because it’s done. It’s a dead technology. It doesn’t matter how many people are deploying in enterprise environments, or how well they are deploying those things. There’s no devs on the project and GPUs keep changing. There’s only so many ways you can keep band-aiding a GPU into thinking it’s a giant frame buffer, at some point, there’s going to be a break in the underlying architecture of GPUs, that thinking it’s just VRAM to dump data to, will no longer work. The amount of space on die for the backwards VGA and SHM methods is minuscule these days on cards.

Heck, Using MIT-SHM on X11 for a Pi is something that’s terrible. You usually get worse results because the underlying hardware is woefully optimized for you to treat it like how old video cards worked. You actually do better using hardware acceleration. The usual mantra for X11 apps on Pi is, if you get good results with shared memory, use that and never upgrade your underlying Pi, otherwise always use hardware where possible.

Also, unlike X, Wayland generally expects a GPU in your remote desktop servers, and have you seen the prices for those lately?

You don’t even need a good one in today’s standards. At most, most compositors just need to convert pixmap into texture. Anything that supports GLX_EXT_texture_from_pixmap will be enough and at low resolutions, just give it to your CPU, we’re not talking intense operations. But literally anything from the last fifteen years of GPUs has enough power to complete these operations reasonably. Shoot, if you’re thin client on a Pi, the Pi itself has vastly more resources. You can literally have a cluster of Pis if you wanted, labwc is a completely fine compositor for basic thin clients and is basically the replacement of X on Pi. Because X11 was just so terrible because it was so misaligned to how modern GPUs actually work.

What I am saying is X can be whatever in “enterprise deployment”, but X has stopped matching how modern machines look like. Video cards have become more than a bunch of bits dumped into VRAM. No matter how many deployments you’ve done, that doesn’t change that fact. X barely resembles what modern systems of the last twenty-five years looks like. Nobody is working on it. You can have 100 deployments under your belt, nobody is still working on it. No matter how you slice the attributes of X, nobody is actively coding for X any longer. And as for damage and what not, lots of implementations of wl_surface_damage_buffer are using underlying hardware EGL/DMABUF because GPUs are smart enough for the last fifteen years to do that on their own, most compositors utilize that.

Again, it doesn’t matter how many deployments you might have, the hardware does it better than X will ever do it, it’s impossible for X to do it better, there’s nobody there to write better. And it will always be this way, until the heat death of the universe unless someone(s) picks up this massive task of taking care of Xorg. There’s nothing that changes any of this reality.

Does this mean you need to drop X11 tomorrow. No. That’s the entire point of why Xorg was open. So that you can keep it until someone rips it from your cold dead hands. But your stubbornness does not change the fact X is absolutely garbage on the network, is massive inefficient, and most things these days actively try to avoid using X directly and if they have to, they just stuff uncompress bits into a massive packet with zero optimization. You can totally mill grain with a stone wheel today, no one stops you. But you’re not going to convince many people that, that is the best way to mill grain. I don’t know what else to say. I don’t want you to stop using X, but your usage of it doesn’t change any fact that I’ve stated. It’s a very fat, very unoptimized, very slow protocol and there are indeed commercial solutions that are better. I’ve just named one, but there are many. That is just reality, the world has moved past dual channel RAM and buffers. I’ve built VGA video cards, I know how to build a RAMDAC form logic gates, all of that is gone in today’s hardware, and X still has these silly assumptions of hardware that doesn’t even exist anymore.

And the network transparency argument is long gone. While you can indeed network windows over the wire, most toolkits use client side rendering/decorations. So you’re just sending bloated pixmaps across the wire when things like RDP , VNC, etc deal better with compression, damage to the window, etc. And anything relying or accelerated with DRI3 is just NOT network transparent.

Most modern toolkits have moved past X11 because the X protocol was severely lacking, and there wasn’t a good way as a committee to modify the protocol in an unified manner. I mean look at the entire moving Earth that it took for XFixes and Damage extensions. Toolkits wanted deep access to the underlying hardware and so they would go out of their way to work around X, because it just could not keep up.

Yes, this has a name. Asymmetric warfare. Anyone at the other end of the US military has to engage in it at the present time and considering that the United States will likely vote a Trump 2.0 President down the road is what is driving a lot of these countries to begin ramping up domestic weapon production.

All this will do is take resources that have long since been something given to the people and redirect it to building weapons until the entire world is armed to the teeth and we are exactly where we were just before World War I. However, this will make those who profit from war even richer along the way and thus the people are robbed of a world we could of had of shared opportunity, just because some rich assholes in the United States wanted more money.

At this rate it’s Congress’ limp dick energy that let’s them get away with this. It’s absolutely amazing how spineless the institution has become.

But the prize was made of chocolate, so it’s only peace until it’s completely gone. Then it’s back to authoritarianism.

have allegedly been released by a Department of Homeland Security whistleblower

ooooooo… Ooooo… Whoever this is… OOOOOOOOOOOOOOOOOOOO

It’s still very meh. Like does anyone remember those visual studio wizards for doing something? AI tools are about that good, roughly. But the difference is, you still have to review everything with the AI tool because it’ll still make mistakes.

I use AI maybe once or twice a month, but it’s far from, replaced my snippets with Ctrl+H replacing keywords.

Mom, I want an aim bot!

But we have aim bots at home.

The aim bots at home.

Good on you. I hope all the games find a good home.

That’s super underselling it. Open Financial Exchange OFX is still the go-to for markets and banks to exchange information with various end user devices. ISO 20022 is a standard used in banking that is XML based. Fedwire, the platform that moves money between the central banks completed transition to XML in July… of this year.

Credit reporting agencies, insurance agencies, hospitals, medicare, medicaid, massive amounts of the entire global logistics industry are heavily using XML with no plans in the near future to move off of it. Like the network that handles auto insurance claims and reporting them to people like LexisNexus is all XML.

Like it’s impossible to cover just how much of this planet runs on XML.

She can’t resign from a job she never legally held.

That’s like this kind of interaction in a race:

I’m sorry sir, we’re disqualifying your car from racing today. It seems to have a jet engine attached to it and we don’t know how that got by inspection. But it’s not allowed in the rules.

Oh well that’s easy to explain, I just didn’t take my car by inspection. I just drove it out here and told everyone I’m here to race. It’s a race, correct? Well I’m here to race with the best of them.

That doesn’t sound like you’re an actual participant in this race then. You should not be here and I’ll have to ask you to leave.

Leave? Perish the thought. I officially withdraw from this race. scoffs Clearly you are not ready for innovative takes on race car design.

Well it seems you weren’t in the race to begin with, but by whatever means, please see your way out.

That is what this whole thing summarized is…