The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Will Senn <will.senn@gmail.com>
To: Adam Thornton <athornton@gmail.com>, Larry McVoy <lm@mcvoy.com>,
	TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] FYI: Internet Old Farts Club
Date: Sat, 29 Jan 2022 20:10:42 -0600	[thread overview]
Message-ID: <cf71c638-b6b6-2068-dd8a-648026053c97@gmail.com> (raw)
In-Reply-To: <CAP2nic3Jbvw6dAk9i4p63oXRsd5xi+QyVANSaRSDyj2d+hr53g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]

On 1/29/22 7:20 PM, Adam Thornton wrote:
>
>
> On Fri, Jan 28, 2022 at 7:37 PM Larry McVoy <lm@mcvoy.com> wrote:
>
>      I can only speak for myself but hell will freeze over
>     before I have a Facebook account
>
>
> In this instance you're speaking for me too.
FB and I went round and round in 2018 when I opened an account and they 
disabled it that same day and demanded verification of my identity. They 
were never willing/able to enable the account for more than a few hours, 
even after I got the Better Business Bureau involved. The only single 
piece of content I ever posted to the account was a background image (a 
pic I took in Fort Collins, Colorado of a mountainside). After BBB got 
involved, they would enable the account (after I provided ID 
verification), only to disable it again after a few hours. This went on 
for about 5 months (I was tenancious and curious to see if it could ever 
be resolved). Eventually, I got bored and tired of going back and forth 
with BBB and the faceless monstrosity that FB is. An intelligence buddy 
of mine said it was all for the better anyway... I'm on the hell 
freezing over side of things :).

[-- Attachment #2: Type: text/html, Size: 2263 bytes --]

  reply	other threads:[~2022-01-30  2:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27  0:36 Rich Morin
2022-01-27  1:55 ` Jan Schaumann via TUHS
2022-01-29  1:59   ` Charles Anthony
2022-01-29  2:24     ` Theodore Y. Ts'o
2022-01-29  2:36       ` Larry McVoy
2022-01-29  8:48         ` Andy Kosela
2022-01-29 17:15           ` Jon Steinhart
2022-01-29 17:20           ` Seth J. Morabito
2022-02-01  2:12           ` Grant Taylor via TUHS
2022-02-01  2:21             ` Steve Nickolas
2022-02-01  2:23             ` Larry McVoy
2022-02-01  2:31               ` Steve Nickolas
2022-02-01  2:51               ` Grant Taylor via TUHS
2022-02-01 18:19               ` Clem Cole
2022-02-01 18:24                 ` Steffen Nurpmeso
2022-02-01 12:45             ` Blake McBride
2022-01-29 17:20         ` Blake McBride
2022-01-30  1:20         ` Adam Thornton
2022-01-30  2:10           ` Will Senn [this message]
2022-01-27  2:07 ` Grant Taylor via TUHS
2022-01-27  2:40   ` Larry McVoy
2022-01-27 21:11 ` Tomasz Rola
2022-01-27  2:52 Norman Wilson
2022-01-27 23:20 ` Nemo Nusquam

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=cf71c638-b6b6-2068-dd8a-648026053c97@gmail.com \
    --to=will.senn@gmail.com \
    --cc=athornton@gmail.com \
    --cc=lm@mcvoy.com \
    --cc=tuhs@minnie.tuhs.org \
    /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).