What you're describing is a random number generator with a key to initialize it. Some of the good ones might be good enough (or might not). Anything you can keep in your head is going to be crap and fairly easily breakable. Either way, you're still better off to just exchange regular secret keys at your meeting, which can be concealed in a variety of ways. Even real one time pads can be fairly easily concealed - a "blank" USB key, for example.
You didn't say so, but I'm assuming you're encrypting your message using the book page as a one time pad, then obscuring it using steganography. If someone sufficiently motivated were after your criminals, they could break that. Steganography isn't much protection when someone knows there might be hidden messages. And your one time pad, while one time, isn't random. Book pages have quite a bit of structure.
Any structure in a one time pad makes it vulnerable. To the point where people have gone to great lengths to construct them using the best random numbers obtainable, from devices ranging from antennae monitoring the ionosphere to quantum devices.
One time pads have been, and probably are, used extensively. You send a bunch of random data to someone via some secure method, which is usually very slow (like hopping on an airplane with a DVD full of random numbers on your person). You can then exchange messages securely using a convenient and fast channel, such as e-mail. See the utility there?
Companies have been paying the post office to shove stuff in my mailbox for years. That actually causes physical annoyance, as I have to shovel it into the recycle bin and then toss it. Then there are those crazy people who hand out free samples on the street. I don't have to take it, but I still have to see them.
Whoever tagged this "first world problems" was dead on.
Then turn off automatic downloads. You can't hit a switch that says "download everything!" and then call it "jammed down your throat" when your phone does what you told it to and downloads the free song someone gave you.
I saw the fuss on Facebook and went to check. No U2 song. It was listed as something I could download if I wanted to. Whoopty doo.
Note also that I point out that the dependencies work in *both* directions; as antientropic points out Gnome requiring SystemD is absolutely an issue with the Gnome team and nothing to do with SystemD, but it does have implications in that it helps build a mess of inter-dependencies that is making it increasingly hard to strip systems down to the minimum. RHEL's insistance on NetworkManager by default, with all the baggage that brings, doesn't inspire confidence either, as this is apparently one of the next daemon in SystemD's sights - maybe SystemD can improve it, but I'm not holding my breath.
Anyway, regardless of that, we've made our choice and moved to BSD; SystemD played a significant part in that, but it definitely wasn't the only factor, as I noted in my OP. ?
A consensus is a bunch of people who share an opinion. You can have a consensus of scientists, but not a scientific consensus. Crichton was right (about that): science is about consistent, reproducible results, not opinions or consensuses. Politics often involves consensus.
Climate science doesn't care how many people, scientists or not, vote for a particular hypothesis. Climate politics do, and that's what's involved when we try to decide what to do. Unfortunately, people confuse the two.
A consensus is a bunch of people who share an opinion. It has nothing to do with right or wrong.
1. It effectively works as a monolithic replacement for several daemons, contra to core UNIX design tenets, and even though some of those sub-daemons can be swapped out with an alternative, often that works by running the second daemon in parallel - you can't actually disable the SystemD equivalent, let alone remove it altogether. This makes troubleshooting much more complicated when something goes wrong, especially if you have booted a system from a recovery disk to troubleshoot after a crash, compromise, or whatever and can no longer directly access several of the key sources of information necessary to do that.
2. Because of the growing number of packages that depend on SystemD, and vice-versa, it's creating a huge mess of package inter-dependencies that mean that it's getting almost impossible to build a stripped down and hardened server. Ballmer might have been right with his "Cancer" comment, he just wasn't specific enough: Gnome requires SystemD, $distro wants to bundle Gnome, therefore $distro adopts SystemD - and forces the default install of all the other package dependencies that go with it, thereby increasing the attack surface of the system. So much for hardening systems by removing all superflous code, huh?
3. All that cruft seems to be bogging the system down. We are currently migrating a large number (much larger than planned after initial results) of systems from RHEL to BSD - a decision taken due to general unhappiness with RHEL6, but SystemD pushed us towards BSD rather than another Linux distro - and in some cases are seeing throughput gains of greater than 10% on what should be equivalent Linux and BSD server builds. The re-learning curve wasn't as steep as we expected, general system stability seems to be better too, and BSD's security reputation goes without saying.
That said assuming that it "just works" a SystemD based desktop with everything from a desktop application down to the kernel talking through the same set of core services does sound like a nice idea. The problem is that most of us are not actually running Linux desktops; we're running servers and would just like the OS to mostly get the hell out of the way so we can get on with running whatever server daemons we are using. If SystemD were better architected - say a core PID1 init replacement, then a bunch of optional packages I don't even need to install if I want to use an alternative or not bother with at all, plus a massive clean up of the dependency hell that it has introduced - then I'd be a lot happier with it, but as it stands I just can't see including it on a hardened Internet facing server as being a remotely sane thing to do.
At this point in time, with almost no response by NATO/the West other than some obviously ineffectual sanctions, my money is on Russia successfully annexing enough of Eastern Ukraine and the Crimea (albeit as an "independant" state with its capital in Donetsk or Sevastopol) that it can resupply the Crimea via land from mainland Russia.