2,533 karma · joined June 18, 2013
The list of open issues on GitHub in the native encryption component is quite telling: https://github.com/openzfs/zfs/issues?q=is%3Aopen+is%3Aissue...
- https://eclecticlight.co/2021/03/11/time-machine-to-apfs-und...
- https://eclecticlight.co/2021/04/16/time-machine-to-apfs-usi...
Debian Jessie is terribly out of date and hasn't seen regular security updates for five years now, from https://www.debian.org/releases/jessie/:
> Debian “jessie” Release Information
> Debian 8.11 was released June 23rd, 2018. Debian 8.0 was initially released on April 26th, 2015. The release included many major changes, described in our press release and the Release Notes.
> Debian 8 has been superseded by Debian 9 (stretch). Regular security support updates have been discontinued as of June 17th, 2018.
edit: it looks like the SteamOS build for custom hardware is no longer available for download, as the download link now leads to a "Download SteamOS: Steam Deck Image" page.
And the CISA announcement: https://www.cisa.gov/news-events/news/when-tech-vendors-make...
Battery storage could earn you more if you discharge at the right moment, but energy prices aren’t negative often enough to warrant the expenses on a battery pack. You could also trade on intra-day pricing differences (buy low, sell high) but I doubt this will be an interesting business case for the average consumer.
Of course large scale battery parks work the same way, but they will have contracts with the grid provider to balance capacity, a more lucrative market.
Large scale electrolysis has the same problem as home batteries: big investment, so you won’t recoup the investment unless you can run the electrolyser often enough. Another issue is that electrolysers can’t scale up or down very quickly, so you can’t respond to capacity issues and get lucrative deals in that market.
Also, unrelated to its use of macros, Rocket development seems to have stalled after August of last year.
The introductory blog post is helpful: https://tokio.rs/blog/2021-07-announcing-axum
It also drops AVX-512 support entirely, presumably because the efficiency cores don’t support it and the problem you mention isn’t easily solvable.
https://nvd.nist.gov/vuln/detail/CVE-2011-0227
https://nvd.nist.gov/vuln/detail/CVE-2015-1097
https://nvd.nist.gov/vuln/detail/CVE-2015-5843
https://nvd.nist.gov/vuln/detail/CVE-2016-4654