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.

A couple of them.

• I review flashlights and occasionally other everyday carry gear at https://zakreviews.com/
• I share photographs and very rarely words at https://zaktakespictures.com/

Both have RSS feeds and associated Mastodon accounts. It’s also possible to follow the latter directly with ActivityPub software that allows following users (not Lemmy). I might put up a third and talk about programming and tech.

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.

There’s a significant distinction between servers that are actively malicious as you’re describing and servers that aren’t fully compatible with certain features, or that are simply buggy.

Lemmy, for example modifies posts federated from other platforms to fit its format constraints. One of them is that a post from Mastodon with multiple images attached will only show one image on Lemmy. Mastodon does it too: inline images from a Lemmy post don’t show on vanilla Mastodon.

I’ll note that Lemmy’s version numbers all start with 0. So do Piixelfed’s. That implies the software is unfinished and unstable.

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.

Federation doesn’t inherently require large amounts of memory. Fundamentally, it’s a matter of selecting a list of unique servers (likely tens, maybe hundreds) from a larger set of followers (likely hundreds, maybe thousands) and sending an HTTP request to each when there’s a new post. There’s a speed/size tradeoff for how many to send in parallel, but it’s not a resource-intensive operation.

Growth beyond a few tens of megabytes was a bug in Writefreely, which is a likely-suitable option several comments here recommended.

I’d put it farther removed from the technical side than that; dreadbeef is thinking like a manager. OP might be better off paying a third party $3/month to handle the details and host a heavyweight, full-featured blog for them, but that’s not what they asked for.

This is selfhosted, which I think implies a desire to self-host things even if it might seem a wiser use of resources to do something else.

It’s pretty bad, however the headings appear be colored by the author’s moral indignation. Many models from brands in the “Avoid at all costs!” section are, in fact unlockable.

Here’s a list.

https://github.com/melontini/bootloader-unlock-wall-of-shame

I’m thinking like a programmer about what a basic blog has to do and the computing resources necessary to accomplish it. Software that needs more than a few tens of megabytes to accomplish that is not lightweight regardless of its merits.

This comment seems to be arguing that one should not demand blog software be lightweight because there’s inexpensive hosting for something heavyweight. That’s a fine position to take, I guess, but OP did ask for lightweight options.

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

It wants a gigabyte of RAM. Maybe that passes for lightweight in 2025, but given the fundamental things a blog has to do, I’d probably put the cutoff at less than a tenth that amount.

Some people have privacy expectations that are not realistic in an unencrypted, federated, heterogeneous environment run by hobbyist volunteers in their spare time.

It you have something private and sensitive to share with a small audience, make a group chat on Signal. Don’t invite any reporters.

I see where you’re coming from now. In most English-speaking cultures, it is not conventional to use hand gestures as a substitute for spoken words in a conversation. Breaking social conventions for no apparent reason is at least potentially rude.

You’re translating those conventions directly to chat. Chat is not spoken word, and it is conventional to use emojis, at least the really unambiguous ones, instead of typed words in chat some of the time. People do not usually do this with any rude or insulting intent.