From: "David P. Reed" <dpreed@deepplum.com>
To: starlink@lists.bufferbloat.net
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starilnk terminal detector
Date: Mon, 19 Dec 2022 18:14:56 -0500 (EST) [thread overview]
Message-ID: <1671491696.919711872@apps.rackspace.com> (raw)
In-Reply-To: <mailman.5.1671469201.26830.starlink@lists.bufferbloat.net>
[-- Attachment #1: Type: text/plain, Size: 729 bytes --]
The pragmatics of 21st century warfare to me suggest that the hypothetical Starlink detector is basically an irrelevant piece of propaganda.
You need actual insight into tactics and behavior of the "adversary" to manage operations that have significant effect.
Look at all the money and effort ARPA wasted (under McNamara's DoD) trying to "win" the Vietnam war in the field. This is what results when you let arms-designers (even hacker level wannabes) try to decide what will be useful in the field.
If you want to understand the Ukraine war, buy a plane ticket to Poland or Ukraine, bring your tools, and go out with the actual combatants. (don't forget to get trained with weapons and basic combat skills).
[-- Attachment #2: Type: text/html, Size: 1669 bytes --]
parent reply other threads:[~2022-12-19 23:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mailman.5.1671469201.26830.starlink@lists.bufferbloat.net>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1671491696.919711872@apps.rackspace.com \
--to=dpreed@deepplum.com \
--cc=starlink@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox