Trump has already asked for action on TikTok to be delayed so that he has authority to “address” the situation. Trump doesn’t have to choose between the bribes offered, he’ll gladly take them all at the same time.

Using it from chrome is how I use it.

Two limitations:

• You cannot let someone else control your screen. This is fine by me, I never want someone controlling my screen anyway. If I want to collaborate with them, I use any number of better ways to get them shared access.
• You cannot control other folks screen. This is often a challenge as too many people offer this up as the only way to remotely help them. I hate doing this because even in Windows the experience is utter garbage, but sometimes the other party just forces my hand.

I feel like it’s not great to say “Congress is already prepping” instead of “Marjorie Taylor Greene is prepping legistlation”

Unfortunately, this time around the majority of AI build up are GPUs that are likely difficult to accomodate in a random build.

If you want a GPU for graphics, well, many of them don’t even have video ports.

If your use case doesn’t need those, well, you might not be able to reasonably power and cool the sorts of chips that are being bought up.

The latest wrinkle is that a lot of that overbuying is likely to go towards Grace Blackwell, which is a standalone unit. Ironically despite being a product built around a GPU but needing a video port, their video port is driven by a non-nvidia chip.

This was after applying various mechanisms of the traditional kind. Admittedly there was one domain specific strategy that want applied that would have caught a few more, but not all of them.

The point is that I had a task that was hard to code up, but trivial yet tedious for a human. AI approaches can bridge that gap sometimes.

In terms of energy consumption, it wouldn’t be so bad if the approaches weren’t horribly over used. That’s the problem now, 99% of usage is garbage. If it settled down to like 3 or 4% of usage it would still be just as useful, but no one would bat an eye at the energy demand.

As with a lot of other bubble things, my favorite part is probably going to be it’s life after the bubble pops. When the actually useful use cases remain and the stupid stuff does out.

It is a shock, but at least they received their money without being left holding the bag. They have a committed backlog over a year long, they seem to be avoiding manufacturing more than they have already sold …

I had some files that i knew had duplicates, but didn’t exactly match and while the filenames were not identical, you could tell by looking if they were the same.

Would have been very tedious to do all of them, LLM was able to identify a “good enough” number of duplicates and only made a few mistakes. Greatly sped up the manual work required to clean up the collection.

But that’s so far from most advertised scenarios and not compelling from a “make lots of money” perspective.

Both KDE and Gnome have a comparable set of default keyboard shortcuts.

The difference is if you are in KDE, you have easier ability to adjust to what you want with a lot more available shortcut actions, while in Gnome you generally are expected to live with the choices of the devs.

Which I find to be a weird stance.

Gnome also believes that a window must have control over its own titlebar to draw it as it sees fit while simultaneously declaring it must not have control over a tray icon.

Also funny that Gnome seems to have objected to KDE proposal and wrote their own even though they seem to say point blank that while they are dictating how all the other DEs will do it, they themselves will be ignoring it. Why get in the business of a protocol you don’t even want to implement in the first place…

Mainly because gnome is harder to ignore than a lot of other opinionated DEs.

It’s been the default target for fedora and red hat, and like other choices rh makes, it propagates throughout the broader ecosystem.

Even if you ignore them, they dictate how Linux desktops are broadly allowed to work by largely asserting authority over FreeDesktop and by extension Wayland.

One of these is that they absolutely hate the concept of server side decorations, as a result even as they begrudgingly allowed it as a Wayland protocol, they insisted that it must not be mandatory and they are allowed to ignore it. This means applications that do not care about their decorations otherwise now must care about their decorations. As a user, the consequence is that any GTK application you might use is likely to just pop out as a gnome looking window among a bunch of otherwise consistent windows.

I did that for a while, but ultimately got too frustrated due to a few things:

• Having to explore extensions in the first place for fairly basic functionally that I would have expected gnome to naturally implement
• Every update would break extensions, and I’d have to wait for the extension author to update it, and about a fourth of the time the extension was abandoned and I would just have to go without or search for a similar.
• At their best I always felt a lot of the extensions were having to settle for a lesser experience due to limitations of the extension mechanism.

Ultimately, I found that experience I was trying to get to that gnome never would normally support and would evaporate on updates and never be quite right anyway was just a natural featureset of Plasma. So I just do that and haven’t had to sweat updates nearly as much as when I kept trying to make a go of it with gnome shell. I kept giving it a shot because of my gnome 2 experience (admittedly augmented by compiz), but gnome 3/mutter have not been a good fit for me.

Well that’s not quite true.

I have some z-wave thermostats, which I know do not talk to the Internet, just a local system with a zwave dongle.

For a relative, recently set up a similar setup, but with a homekit thermostat. Similar deal, though it really really wanted to connect to a cloud server and you kind of had to trick it to a non apple homekit setup. The follow on model from that brand did drop homekit support, presumably because they wanted to force their cloud servers, which became required for any advanced functionally.

There are ways to get automation friendly devices without a cloud connected requirement, though admittedly you have to be paying pretty close attention. Generally offerings for business are more likely to be locally workable, but that’s hardly a given either

I have enjoyed VR, but the “metaverse” angle was something largely no one asked for.

I’ll admit even at its best it is still niche, but I have enjoyed it, particularly for simulation genre.