• 4 Posts
  • 117 Comments
Joined 2 年前
cake
Cake day: 2023年6月1日

help-circle
  • 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.



  • I despise this clickbait post title that doesn’t name the company, even though the article’s title names it directly.

    Thank you to folks who did name it (Jolly Rancher) and had excerpts. Here’s more:

    The FSA says they contain chemical compounds - mineral oil aromatic hydrocarbons (MOAH) and mineral oil saturated hydrocarbons (MOSH) - that are “not compliant with UK laws”.

    “MOAH is a genotoxic carcinogen, therefore no exposure is without risk to human health.”

    MOAH and MOSH are used in confectionery to prevent stickiness and create a glossy appearance.

    According to the agency, The Hershey Company has been working with the UK government body to remove the affected Jolly Rancher products from the UK market since 2024, but some businesses in Britain have continued to import the products.

    The article title "Some Jolly Rancher sweets unsafe to eat, FSA says " is ambiguous whether it is a contaminant affecting some batches of candies, or if it is a recipe issue. Sounds to me like it is a known concerning ingredient they intend to keep including.






    • 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!




  • Not related other than learning resource - but I’ll also mention on the off chance it’s useful to anyone, I like these resources for practicing kana:

    Each are useful in their own right, but I was kind of contemplating making an opensource repo that has similar (but hopefully refined) capabilities, maybe detecting when you commonly confuse two characters and then offer to give you a short drill of just those characters to reinforce.

    Obviously less and less useful as time goes on and the hiragana are cemented in your memory, but it makes me sad to think someone might take them down one day and they’d just be lost.







  • Amazon is helping TimmiXyZ29 sell me a new washer. TimmiXyZ29 is not a certified salesman for Whirlpool Washers. Timmi is actually refurbishing old washers and selling them as new. My washer burns the house down. I think we all agree Timi is responsible, but where do I start?

    • The manufacture says they can’t be responsible because Timi/Amazon aren’t selling certified Whirlpool goods.
    • Timmi says he is just selling a product, it’s not his fault
    • Amazon says they’re just selling a product, it’s not their fault

    Now add an additional level; the order is fulfilled by Amazon. Timmi, Whirlpool and other sellers now give Amazon these washers, and Amazon keeps them in a communal pool and sends it on Timmis behalf. Now we don’t even know where the original washer came from.

    What if amazon deletes, hides, or deprioritized disparaging reviews that showed the product was dangerous, and you now buy it?

    There’s so many levels of possible problems that it can be hard to consistently ascribe blame to any one party when sold through amazon.

    I do expect that if a party is selling goods that end up being dangerous, and users have consistently reported the failures/problems in amazon, amazon should perhaps be responsible if they did not block the seller/product or adequately raise awareness about the concern.