Not necessarily, but most inverters (in Europe, at least) aren't designed to function without a grid anyway.
Some models of inverter brands like Victron (which isn't very common outside its niche of self-sufficiency because they are rather expensive and sometimes complex) can form a micro-grid. They have the option of a special circuit breaker [1] that decouples the inverter from the grid if the grid is detected to be down, which allows their use during a power outage.
I am exited as well but the OS is only one part of the equation. If the firmware BLOBs don't get updates we still have a problem. I really hope this cooperation means that Motorola commits to longer support for gOS devices.
Motorola Signature (2026) has 7 years of support. It's a subset of Motorola's future devices in 2027 and later which are going to support GrapheneOS since the current ones in 2026 didn't quite meet all of the requirements yet. The intent has never been to support their existing devices but rather for future devices to provide everything needed and official GrapheneOS support. There's a lot of work to do. Meeting all of our requirements on low-end devices is currently unrealistic but can be a goal further down the road.
Aside from that, we'll have a lot more access to the code for firmware, etc. and ability to do hardening below the OS layer through the partnership with Motorola and their partnership with Qualcomm.
They address this issue specifically (don't have the links now, I'm sorry) - basically one of the "must haves" for the hardware to be considered good enough (meaning pixels have it and new motos will have it) is a hardware capability of the strict separation between the os and devices, ie baseband unable to influence the os (snoop/inject stuff, etc).
Don't remember that at the moment, it should be one of the requirements they list under "future hardware" In the FAQ.
What's the difference compared to a phone with a radio firmware by a US company?
In both cases it's something closed and the government has shown overreach. (Yes, China a lot more than the US, but still ... things are not looking good a the moment. And I have no more trust, even if the political direction changes for a presidency period or two.)
But yes, ultimately we want open source firmware. Still, then there could be hardware backdoors anyways ...
I dont think grapheneos handles radio firmware on pixels, radios also not made in the US. I wonder if even apple does, as their radios are also not made in US.
brave seems to have some special sauce since it appears to be able to hide the fact that ads were removed. I am guessing they are doing so without triggering dom events.
Sure! I've been using "WINEDLLOVERRIDES=icu,icuuc=d". I think I found it on some Wine bug report after like half an hour of trying things from other bug reports/github issues before eventually discovering this one that worked.
No, don't need anything extra, `extra/yt-dlp` works perfectly fine and is enough. You'll get a warning if you run it without the flag:
WARNING: [youtube] [jsc] Remote components challenge solver script (deno) and NPM package (deno) were skipped. These may be required to solve JS challenges. You can enable these downloads with --remote-components ejs:github (recommended) or --remote-components ejs:npm , respectively. For more information and alternatives, refer to https://github.com/yt-dlp/yt-dlp/wiki/EJS
Providing one of the flags automatically lets it automatically get what it needs. No need for AUR packages :)
Edit: Maybe I misunderstood, now when I re-read your post. You meant it'll prevent the automatic download at runtime perhaps? That sounds about right if so.
Yes exactly, if you install the package you don't need the download the solver on the fly. AT least that's my understanding of what the package is supposed to do. Personally I have no need for it.
reply