• 0 Posts
  • 35 Comments
Joined 2 years ago
cake
Cake day: July 9th, 2023

help-circle




  • It would be easy to find enough solar panels to charge an electric vehicle in most sunny areas, though it would probably be easier to just look for a large enough existing install and skip all the DIY. (Just look for the shiniest roof.)

    But I think the real problem is in the EV itself. Batteries self-discharge and chemically degrade over time, so unless the apocalypse was recent, a lot of EVs you find might have damaged batteries, especially if fully discharged to begin with.

    You could cannibalize one or more EVs to cobble together enough good cells to get past the safety cutoffs, but it would take a while and you would need to be careful since internal voltage in EVs tends to be high (like 400-800 volts).

    TLDR: if this is a movie depiction, definitely use a montage.


  • Lol I noticed the same. They evidently have some ongoing internal disagreement as to their target audience. Docs and functionality says “our audience is enterprise developers” but their marketing definitely says “our audience is end users.”

    It may be explained by recent partnerships with former custom ISO devs (seeking legitimacy and offering a sizable user base in turn). I expect the plan is eventually to sell premium support for an enterprise toolset, but for now their target audience is the non-dev-but-tech-savvy end user. And those happen to be surprisingly opinionated re: java and electron.


  • Forgive me for not explaining better. Here are the terms potentially needing explanation.

    • Provisioning is just initial system setup, but usually implies a more regimented or repeatable process.
    • Virtual Machine (VM) snapshots are like a save state in a game, and are often used to reset a virtual machine to a particular known-working condition.
    • Preboot Execution Environment (PXE, aka ‘network boot’) is a network adapter feature that lets you boot a physical machine from a hosted network image rather than the usual installation on locally attached storage. It’s probably tucked away in your BIOS settings, but many computers have the feature since it’s a common requirement in commercial deployments. As with the VM snapshot described above, a PXE image is typically a known-working state that resets on each boot.
    • Non-virtualized means not using hardware virtualization, and I meant specifically not running inside a virtual machine.
    • Local-only means without a network or just not booting from a network-hosted image.
    • Telemetry refers to the data harvesting apparatus. Most software has it. Windows has a lot. Telemetry isn’t necessarily bad but it is easily abused by data-hungry corporations like MS, so disabling it is a precaution.
    • MS = Microsoft
    • OSS = Open Source Software
    • Group policies are administrative settings in Windows that control standards (for stuff like security, power management, licensing, software and file system access, etc.) for user groups on a machine or network. Most users stick with the defaults but you can edit these yourself for a greater degree of control.

    Many of these concepts are IT-related, as are the use-cases I had in mind, but the software is simple to use if you pick one of the premade playbooks. (The AtlasOS playbook is popular among gamers, for example.)


  • Just a tip: if you must use consumer editions of Windows regularly, consider adding an automatic provisioning tool like AME to your workflow.

    The example above uses customizable “playbooks” to provision a system the way docker compose would a container image, so it can fill the role of a VM snapshot or PXE in non-virtualized local-only scenarios.

    The most popular playbooks strip out AI components and services (there are many more than just Recall) but also disable all telemetry and cloud-based features, replace MS bloatware with preferred OSS, curtail a truckload of annoying Windows behaviors, setup more sensible group policies than the defaults, and so forth.

    I have a few custom playbooks for recurring use cases so that, when one presents, I can spin up an instance quickly without the usual hassle and risk.



  • even old data retroactively

    My impression is that retroactive opt-out data grifting represents the lion’s share of user data sales today, and that it’s a popular strategy because it works.

    The formula: appraise the data and find your buyers in advance. THEN update the privacy policies to include the data you want to sell. That way, the moment new policies go into effect, all you have to do is hit the transfer button.

    After that, it’s done. Users that find and flick your new opt-out toggle only stop you from selling their data to additional buyers, and that’s nbd since data brokers only pay top-dollar for exclusive access to stuff that’s not already on the market.

    It’s why I consider the introduction of any opt-out privacy policy an explicit admission of data theft.








  • He’s making a point about instantaneous versus overall energy use, which it sounds like you already understand. “Power” and “energy” are already kind of loose terms, which could make that conversation confusing IMO.

    But for anyone confused by this:

    For the typical energy consumer, Watts (W, kW) are relevant when considering circuit capacity. Otherwise, Watt-hours (Wh, kWh) is likely the metric you’re looking for when considering energy use.

    Concretely, your coffee maker might pull 1.2 kW while in use, more than most appliances in your house, yet it probably represents a minuscule portion of your electric bill, perhaps less than 1 kWh, since it only needs to boil a small amount of water with each use.