> There are any number of tools that will generate me a pretty and useful database schema diagram if I point them at a relational database.
I'd even go so far as to design database schema with these ER diagram tools in mind: if the automatic diagram is messy then that's more-often-than-not a code-smell in need of refactoring (before being hit with production data).
So a typical 80db commercial drone flying at 300m (CAA minimum) would be 50db at ground level (closest point), or about a loud conversation (but less than quiet road traffic).
I'd corrupt the quote slightly to factor informational effects of propaganda:
"a wealth of [conflicting] information creates [an apathy] of attention and a need to [withdraw] that attention efficiently among the overabundance of information sources that might consume it."
In this way, information sources can destroy attention rather than foster efficient allocation (which is hard work).
So the only hangover from bad parties is that the party ends?
The biggest, baddest parties will always draw the popular crowd, and the same DJs will know better when to quietly slip out the back door with bags full.
How does a well-regulated party compete against that without calling for more regulation?
Linux keeps track of "credit" for entrophy pool sources.
Anyone can write to /dev/random - this mixes data into the entrophy pool but it won't be "credited" as securely increasing /proc/sys/kernel/random/entropy_avail . https://www.whonix.org/wiki/Dev/Entropy
If the point of /dev/random is to provide crytographically secure random numbers, then some level of paranoia is needed for determining which sources are "credited" for initializing the pool. https://lwn.net/Articles/760121/
Edit - a visual explanation of this journey: https://www.youtube.com/watch?v=IfVwelta1fE