Project Voyager
The idea of Project Voyager came out in the first weeks of the Trump Chaos, when it became clear(er) that we couldn't trust American digital companies anymore. Of course we couldn't trust techbros even before, but the American fash tide was, with Trump, of a bigger magnitude. And it's not just about US, honestly. Digital surveillance is on the rise everywhere and it's a risk we all should consider.
Unfortunately, there is no way to be connected and, at the same time, to be completely safe. Mix this with my other big interest - collapse computing - and the result is the concept of unpermanently connected computing and memory devices, which can join the Internet as usual but also, better, use other means of communications. And store locally important chunks of information, from personal data to common knowledge.
The idea of a portable, (dis)connected, low-power memory/computing device is very old and I'm not inventing anything here. Mine is just another concept. That reminded me the Voyager missions, admirable for their use of scarce computing/storage power, reliability, stubborness in working years after their supposed end of life (and some snafu). So: Project Voyager.
First step: implementing the "Voyager model" with a standard notebook PC. This is the easiest trick - almost trivial, you can say - but it's also the best way to understand properly what's to be included (hardware, software, peripeherals, data, applications, scripts) and what not, because it's simply a nice-to-have, or impossible to get, or simply useless.