From: krewat@kilonet.net (Arthur Krewat)
Subject: [TUHS] unix "awesome list"
Date: Tue, 8 May 2018 12:18:02 -0400 [thread overview]
Message-ID: <92064c68-1ab9-085f-3259-10efdf94da11@kilonet.net> (raw)
In-Reply-To: <20180508151722.49CFC18C079@mercury.lcs.mit.edu>
On 5/8/2018 11:17 AM, Noel Chiappa wrote:
>
> There's a certain irony in people complaining that ukernel's have more
> overhead - while at the same time time mindlessly, and almost universally,
> propogating such pinheaded computing hogs as '_mandating_ https for everything
> under the sun' (even things as utterly pointless to protect as looking at
> Wikipedia articles on mathematics), while simultaneously letting
> Amazon/Facebook/Google do the 'all your data are belong to us' number; the
> piling of Pelion upon Ossa in all the active content (page after page of
> JavaScript, etc) in many (most?) modern Web sites that does nothing more than
> 'eye candy'; etc, etc.
>
Part of the https wave is the fact that the Tin Foil Hat Society thinks
they are being maliciously monitored by the gov't. The move towards
privacy on the Internet is fostered by this conspiracy-minded
thoughtlessness. Meanwhile, it just adds another step to any entity
wanting to figure out what you've been doing online. Either monitor your
browser (ala telemetry), or the websites themselves. If one were to see
https traffic to a website that's known for it's racist content, then
that pretty much defines what you've been doing without having to
decrypt the actual packets. Much less get your search history from
Google in the first place.
I've heard this very same privacy concern from what I consider
moderately intelligent people I associate with.
I have a (very) small website in http that has a few TOPS-10 items for
download. That doesn't need to be https, but for some reason, I've heard
that Google will lower my rankings because I'm not using https. What
tomfoolery is this?
ak
next prev parent reply other threads:[~2018-05-08 16:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 15:17 Noel Chiappa
2018-05-08 15:22 ` Warner Losh
2018-05-08 16:18 ` Arthur Krewat [this message]
2018-05-08 19:37 ` Dave Horsfall
2018-05-08 19:54 ` Grant Taylor
-- strict thread matches above, loose matches on Subject: below --
2018-05-07 18:22 A. P. Garcia
2018-05-07 21:10 ` Dave Horsfall
2018-05-07 21:53 ` Steve Johnson
2018-05-08 12:24 ` Theodore Y. Ts'o
2018-05-08 13:51 ` Bakul Shah
2018-05-08 14:53 ` Clem Cole
2018-05-08 15:23 ` Jon Steinhart
2018-05-08 15:31 ` Steve Johnson
2018-05-08 16:32 ` Clem Cole
2018-05-08 17:33 ` Theodore Y. Ts'o
2018-05-08 18:40 ` William Cheswick
2018-05-08 21:25 ` Bakul Shah
2018-05-08 21:15 ` Bakul Shah
2018-05-08 16:31 ` Michael Parson
2018-05-08 17:20 ` Larry McVoy
2018-05-08 17:49 ` Michael Parson
2018-05-08 20:48 ` Dave Horsfall
2018-05-08 17:53 ` Theodore Y. Ts'o
2018-05-07 21:54 ` Steve Nickolas
2018-05-08 8:14 ` Mutiny
2018-05-07 22:34 ` Andy Kosela
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=92064c68-1ab9-085f-3259-10efdf94da11@kilonet.net \
--to=krewat@kilonet.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;
as well as URLs for NNTP newsgroup(s).