A problem is that some sites that don’t need cookie banners use them anyway due to a poor understanding of the law and excess of caution.

Well… sort of.

Batteries perform differently under load. A battery that delivers 10Wh under a 1W load will probably deliver less (and get warmer) under a 10W load. Power supplies also perform differently under load, and DC-DC switching power supplies perform differently based on the output voltage. Generally, a larger voltage conversion and/or a higher load is less efficient. There’s also going to be some base power consumption in the circuit, so the most output power is probably achieved at some sort of medium load.

To make things more fun, batteries are usually tested under constant current, not constant power. The increasing current as the battery drains of a constant power load will result in less total power, and constant output power often means increasing input power as the battery drains.

In short, the real world is complicated. Giving best and worst case Watt-hours could be a reasonable approach.

I’d be a little concerned about safety. A manufacturer or distributor that’s willing to lie so blatantly about capacity might also be willing to sell cells that failed QC.

Powerbanks are where it’s most problematic. They’re usually reporting the capacity of the battery cells in mAh. Those cells will be at 2.8-4.2V during operation, but the powerbank outputs 5V, or in modern powerbanks some higher number. 5000 mAh at the 3.6V average of the cells during discharge is certainly not 5000 mAh at the 9V it’s giving to my phone.

It’s not going to give my phone 2000 mAh @ 9V or 18 Wh as the math would suggest either because it’s well below 100% efficient. I’m not sure what’s reasonable to demand in terms of advertising here since efficiency will vary with output voltage and output wattage.

I guess they could still lie about watt-hours

Your battery illustrates that; 9.9Ah * 3.7V is, indeed 36.63Wh. Buying anything without trust in the seller or verification by a third party is a crapshoot.

And I think we’d all agree a sophomore dating a college student would be pretty imbalanced.

I was a college student at 17, but I think you had a larger age difference in mind. I do think we can all agree there should be laws against adults sexually exploiting teenagers.

Yes, though legally that’s a bit of a grey area. It’s only really entrapment if law enforcement or informants entice the offender to commit a crime they weren’t predisposed to commit. I imagine it would be an uphill battle to convince a judge or jury of that when it comes to meeting minors for sex.

The decoys were careful so that it would never even be a question.

I remember looking up the people To Catch A Predator worked with and reading some of their chat logs. The decoy was always very upfront in giving an age unambiguously below the age of consent in their jurisdiction, and never initiated conversation about sex or suggested meeting in person.

Of course, the decoy would always agree to do so if the offender asked, but the criminal conduct was unambiguously criminal, and unambiguously the offender’s idea. What we see in this article appears to abandon that sort of rigor to manufacture more opportunities to confront someone.

We’ve decided, as a society, that humans cannot consent until 18.

Older criminal laws were based on that idea, usually called “statutory rape”. Modern laws about sexual abuse of children usually ignore the concept of consent entirely to allow for more nuance.

One example of nuance is exceptions for people close in age so that non-abusive relationships between teenagers don’t suddenly become crimes when someone has a birthday. Another is that consent is often a factor in the severity of the penalty.

I’m sure there’s a way around it for institutional customers.

Kind of defeats the purpose

That’s why the why matters. Some people might just not trust Windows to keep private data secure, but be comfortable running certain software on it in a VM, possibly a VM that isn’t usually allowed network access.

If you’re sufficiently motivated to get off Windows to invest time learning different workflows, there certainly are options. It sounds like you’ve tried some for image processing and found gaps. People might be able to help fill them if you go into detail about your current workflow, but there is no 1:1 replacement for Photoshop on any platform. If you’re a heavy Photoshop user, there may be no path to happiness for you.

There’s surely a 1:1 replacement for Visual Studio outside of Windows-specific development (which wouldn’t make much sense to attempt on Linux anyway).

I really want this to work out.

Why?

I don’t ask that to talk you out of it. I like desktop Linux. I’m typing this on desktop Linux. I’ve been using desktop Linux for most of my adult life. I ask because your reasons will inform the advice people can give you.

I do a lot of .NET programming and photo editing [with Windows-specific proprietary software]

There isn’t necessarily a good solution to this. Those are large, complicated programs with very deep workflows that are almost certainly going to be dissimilar in any substitute software, which is itself going to be large and complicated with its own ways of doing things. Using those specific programs may be more important to you than what OS you run them on.

It looks like Photoshop is probably usable with Wine, while Visual Studio isn’t. Using Wine means putting up with occasional instability and reduced performance. If you spend a lot of time in Photoshop, this may not be for you.

Another option is to run Windows in a VM for those apps. This will likely work smoothly with regard to the apps themselves, and generally performs near native, but does mean a less polished interaction with the rest of your desktop.

If you’re patient and want to gain a deeper understanding, try Arch itself rather than an Arch-based distribution that’s easy to install.

You’ll spend a long time on the initial installation and setup and you’ll read a lot of documentation in the process. When you have a usable system, you’ll understand what’s installed, how it’s configured, and why. Expect to spend a couple days just to get it usable though - this approach isn’t for everyone.

The Arch docs are top tier, but they’re not necessarily step by step guides because there’s more than one way you might choose to set things up. The docs tell you how the pieces can fit together, but it’s ultimately up to you to to do the assembly.

With ten finger typing, having the most-used keys on the home row is a significant advantage for speed and ergonomics. With swiping, having a sequence of characters close to each other makes it hard for the algorithm to predict the intended word. With tapping, it’s a disadvantage to have adjacent characters in a sequence on a small touchscreen because it increases the chance of fat-fingering them.

Maybe. I use Dvorak for real keyboards and QWERTY on my phone. I tried Dvorak on my phone and didn’t see any benefit.

Heliboard offers the option. The ideal layout for a small onscreen keyboard may be rather different from one for typing with all your fingers though.

We need root on our car computers.

The AI thing I’d really like is an on-device classifier that decides with reasonably high reliability whether I would want my phone to interrupt me with a given notification or not. I already don’t allow useless notifications, but a message from a friend might be a question about something urgent, or a cat picture.

What I don’t want is:

• Ways to make fake photographs
• Summaries of messages I could just skim the old fashioned way
• Easier access to LLM chatbots

It seems like those are the main AI features bundled on phones now, and I have no use for any of them.

it’s as simple as editing a single config file

It isn’t. Mastodon has a character limit hardcoded in two places. Critically, that’s not a limit on what it can receive and display, just on what local users can post. With Bluesky, it’s part of a schema that would be enforced on posts from elsewhere, if anybody was actually running a Bluesky-compatible appview in the wild.

There is a chance that I just don’t get microblogging. I’ve always felt that short character limits encourage people to make bad points that resonate emotionally but fall apart when thought through, and to yell at people they disagree with rather than being thoughtful.