I'm in a similar boat, but I've found where I once habitually put things in the same workspace every time and was able to trivially recall them, I now end up all over the place.

Also I've been missing scratch deeply.

I'm sure it's solvable with some diligence and config changes, but I haven't invested the time yet.

I'd agree with sph about having one workspace per activity. I've never had a rigid workflow with lots of permanent named workspaces, but I have a workspace-naming script that lets me label my numbered workspaces after they've been set up.

Other things that help include a fuzzel-based open window searcher and, to be honest, restrained use of Niri's flagship scrolling feature. Most of my workspaces most of the time are the same size as my screen, with the scroll used very sparingly for usually temporary overflow.

I guess it also helps that I never used the i3 scratchpad so I don't miss it.

I mentioned elsewhere that scrolling WMs shine when you use a workspace per activity. You should never "have stuff all over the place", you should be working on a single one until you context switch.

Its just market euphoria.

Every self checkout around here has an employee staffing ~6 terminals. They're supposed to be watching for things like that. Usually theyre just staring vacantly into space, which I get, that job pays nothing and provides 0 mental stimulation.

When you see a TV being purchased, though, it wouldn't be hard to just watch that it in fact got checked in as such.

> Usually theyre just staring vacantly into space

That's far from my experience. Usually they're overworked with a backlog of customers having some kind of issue needing attention. It usually takes a few minutes to flag one down when I need them to take a coupon or check and ID, because they're already busy doing something for another customer.

Same experience here. The one "monitor" employee is busy nearly full time helping out with some issue some customer is having, such that they simply can't be monitoring that everyone's items are ringing up as the actual item instead of "bananas".

But every terminal also has a spycam hanging above it to either "give the appearance" of a big-brother overlord watching to encourage honesty, or is recording everything so that someone can review footage later if some issue is discovered.

Depending on the store those cameras are definitely processing the feed locally to flag shady stuff. I've had a few times I've done something "odd" (not stealing anything but definitely not the normal flow of scan a single item and put in a bag) and have had those systems freak out on me, and the only part of it being weird it would have known was the camera feed.

Sort of a funny example since "batterygate" centered on degraded iPhone batteries in which Apple argued the best possible move is to throttle phones so they don't shutdown unexpectedly.

Most people would argue the best outcome is spending <100$ and 1 min of your time to have your phone restored to like-new speed.

In the grand scheme of things very little people use Termux on Android out of the billions of people who use Android. Additionally Termux's design is not aligned with Android's app model which has caused many headaches for them. Trying to force a terminal to exist on a phone is possible but it is being forced and is not a natural product that would exist if one was trying to design the best user experience.

No one accused Microsoft of writing good software.

Not really. It's not the same program at all. They just took the name for an inexplicable reason. They even had to make a paragraph disclaimer stating it isn't and never will be the same program.

It has the makings of a natural monopoly, except its compounded by RAM cartels colluding to shut out the last of the competitors.

Recently they had a second price fixing lawsuit thrown out (in the US).

Now with the state of things I'm sure another lawsuit will arrive and be thrown out because the government will do anything to keep the AI bubble rolling and a price fixing suit will be a threat to national security, somehow. Obviously thats speculative and opinion but to be clear, people are allowing it. There are and more so were things that could be done.

Well, they're presumably dead mains.

I really don't think it'd struggle with the correct procedure, either. It's very well documented how to test (and lock out) electrical circuits.

Whether or not they follow it correctly is another thing but it's not like you couldn't search it up and have false confidence before AI. This isn't manufacturing bombs or heart surgery in 10 easy steps.

I agree on both counts but don’t think it’s unreasonable to have safeguards around this kind of ask. With no additional information, this flag seems overly sensitive but we don’t have the full context. I’d expect the occasional superfluous flag when you’re in this neighborhood of conversation and that that’ll happen less as models improve

My main point is _flagging_ is very different from banning.

Flagging is a minor inconvenience just start a new chat or look it up the old fashion way. Not every use case will be as serviceable by every model today.

For what it’s worth, I asked Claude with opus 4.7/4.6 it gave me an answer straight away

Design language, meaning the feel and how the user interacts with a product.

They're saying it follows the patterns that AI biases towards regarding feel and UI.