Let's not forget the effect of helicobacter pylori bacteria on ulcers, they are in general held to be the main cause these days.
I have another theory about the beneficial effect of aspirin, caffine, etc. We evolved with them. Our diet was rich in salycilates and chemicals similar to theobromine or caffine. They came from the plants we ate, some of which were mildly toxic and which we evolved to process to the point that we became dependent on some of their effects. There are a lot of things in the primitive diet that modern people don't eat much at all, like acorns which had to be soaked to remove alkalai and tannin.
If this is the case, taking aspirin and drinking coffee or tea replace substances found in a more primitive diet.
Looks like we aren't waiting for the Changlings to create the Jem'Hadar. A little on the small scale, but maybe they had to start somewhere?
Maybe I have been watching too much DS9?
If this was a drone and was just using the mobile frequencies for communication, it would probably use an off-the-shelf cellular modem module to communicate normally over the cellular network. A special testing authority from the FCC would not be necessary.
Given the regulatory requirements this makes sense. At one major US financial institution, where I worked, this is the norm, because the risk of information leakage is an issue. You even need to use application such as Mobile Iron or Good for accessing company e-mail. Company issued iPhones had the the essentials an nothing more, with certificates limiting what you could do with the phone.
At the same time, there was a move towards BYOD, which does provide a bit of a chink in the wall, but still requires Mobile Iron or Good for accessing company e-mail and a certificate limiting certain operations. You can't copy/paste from Mobile Iron or Good, for example.
These companies need to show to regulators that they are meeting requirements and maybe even going slightly beyond. All e-mail in and out is recorded for 7 years.
One challenge I have with npm are the dead projects and the apparent inability to take over the dead project, even if your project has become the accepted source of truth in GitHub. The workaround is to create a new package, but that just adds to the confusion.
It would be nice if there was a way for a project to either be flagged as possibly dead or require some other mechanism to red flag a project, either automated or via reporting.
Maybe I am alone in this feeling?
Don't tell me how hard you work. Tell me how much you get done. -- James J. Ling