That page had some description, but not enough for my liking. You can poke around the page and find links to the related documents, though (may have to click “see text”

Energy efficiency

If I’m understanding your question, you’re asking about the energy efficiency index rating (EEI) (the letter) vs the battery endurance per cycle (the time), which aren’t the same, but are mathmatically related using the devices voltage x battery capacity.

• (2)   ‘battery endurance per cycle’ means the time a smartphone or slate tablet can operate running a defined test scenario with an initially fully charged battery, before the device shuts off automatically due to a drained battery, expressed in hours (h);

• (10) ‘energy efficiency index’ means the ratio between the battery endurance per cycle (ENDdevice) and the nominal voltage of the battery multiplied by the rated capacity of the battery;

The rating of the “Energy efficiency index” appears to be threshold based, and the best class (A class) makes no distinction for devices just meeting its criteria vs far exceeding, so it’s also possible that very similar devices might have dissimilar runtimes if their energy efficiency diffs substantially within the same class. I’d recommend that if a device is substantially better than the best class, that they would add some form of multiplier to the displayed class. Or even better, just include the EEI I’m Smalltext somewhere.

My takeaway is:

1. customers who only care about runtime need only focus on the rated runtime
2. customers who care about runtime AND energy conservation should try to pick the device with the best runtime amongst the A class of EEI.

** if you plan to carry a battery pack, (1) is not wholly correct. The amount of time your battery pack will add will be heavily dependent on the EEI of the device.

deleted by creator

I was wondering what it tastes like. It’s 35% whey according to Wikipedia, so I’m guessing that for “original” /“plain”, it’s watered down whey flavored? Seems like there are lots of flavors of it too.

Red, Blue, Green, Refresh, Grapefruit, Mint (Switzerland); Yellow, CLIQ Peach, CLIQ Rhubarb, Elderflower (Switzerland, discontinued); Original, Green tea, Cranberry, Pineapple, Raspberry (Netherlands)

Usually, it’s a chain of errors/failures that leads to accidents, after the many years of dissecting and trying to prevent air disasters.

2002 Uberlingen collision is one such case where the reliance on a sole air traffic controller was part of that chain. And that was with one controller instead of the desired two. 50% headcount. Here it’s 1 or 2 instead of 14-15? That’s 7-14% headcount.

We know overworking people and understaffing introduce substantial risk to managing, assisting, and responding to flights. Even supposing this poor soul could adequately manage the workload by themselves, the introduction of a single problem could throw all of it off.

I realize it’s just another framework. But I think the next time I’m building something useful beyond a basic CLI I will try textualize. https://github.com/Textualize/textual?tab=readme-ov-file

I don’t care much about aesthetic and a similar interface for terminal/web seems like it would be useful.

That said, I fully agree that it’s daunting to have to deal with any existing ui. It’s really tiresome to jump through multiple hoops just to get/show info - even before trying to make it pretty.

• Access to my entire music library remotely
• A directory structure view, rather than just Album/Artist/Genre views
• Transcoding while streaming to minimize mobile data usage
• Syncing parts of my library for offline usage

FWIW, you can partially hit most of these with Navidrome with another frontend. I like using Symfonium (android) which allows local downloading, and has a directory view. I don’t think it would work offline though for the directory view. I don’t know about caching/downloading on desktop though; feishin is my favorite desktop frontend, but I don’t think it has a DL/play from DL feature.

The above is only partial. Thank you for your work and sharing. I think the discouraging comments miss that this was a passion project of yours to fill your own use case. Good work!

I always liked the concept of blaze, but it seems like development stopped 2 years ago.

https://github.com/blenderskool/blaze

Using webtorrents for multi-peer transfers & being able to UL/DL from a URL.