Re: Parts Shortage?

From	Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com>
Newsgroups	sci.electronics.design
Subject	Re: Parts Shortage?
Date	2026-03-21 20:08 +0000
Organization	To protect and to server
Message-ID	<10pmtrg$588e$1@paganini.bofh.team> (permalink)
References	(4 earlier) <10pfa8q$7pri$1@dont-email.me> <10phmj4$3h2pn$1@paganini.bofh.team> <10pi5p1$15pcg$1@dont-email.me> <10pke4c$3reku$1@paganini.bofh.team> <10pljog$2901i$1@dont-email.me>

Show all headers | View raw

Don Y <blockedofcourse@foo.invalid> wrote:
|------------------------------------------------------------------------|
|"I stated that it was an example of how that identifying information    |
|can be propagated (publicly) in a message yet not parsable by           |
|mere mortals:                                                           |
|  "Others will encrypt 'identifying information' in an X-<header> for   |
|  their use without making it 'public'.""                               |
|------------------------------------------------------------------------|

Oops. Sorry.

|------------------------------------------------------------------------|
|"You are equating anonymity with identity."                             |
|------------------------------------------------------------------------|

Don Y publishes another insightful perspective.

|------------------------------------------------------------------------|
|"It can also apply to                                                   |
|location -- when you fear that (location) information can bias          |
|a service (that you want to use or rely upon) against you."             |
|------------------------------------------------------------------------|

It is not easy for me to avoid disclosing location
information. Persons often misinterpret the area code of the telephone
number from which I call, but not by very far.

|------------------------------------------------------------------------|
|"> Indeed, but I also need trustworthy emails and LinkedIn for important|
|> urgent contacts. For example, many days ago we discussed about        |
|> LinkedIn. I am a client of a person who knew neither an email address |
|> nor a telephone number for me. We live very far away from each        |
|> other. He needed a substantial response within thirty days, so he took|
|> the initiative to invite me to connect with him on LinkedIn. I        |
|> accepted this invitation and I rapidly responded helping him to       |
|> perform an excellent task for me. I also responded by informing him of|
|> email addresses and a telephone number for me.                        |
|                                                                        |
|[. . .]                                                                 |
|[. . .] (I dislike unsolicited contacts [. . .]"                        |
|------------------------------------------------------------------------|

This LinkedIn inviter is a person who was already working for me, but
we had not informed him of any rapid way (telephones or emails) to
contact me, and he realized that for a successful outcome that he has
needed a rapid response from me, so he has conveniently used LinkedIn
to rapidly ask me a crucial question.

|------------------------------------------------------------------------|
|"do you treat [. . .] lawyer[s]                                         |
|the same way?"                                                          |
|------------------------------------------------------------------------|

Almost. (This LinkedIn inviter was a (non-inhouse) lawyer.) I love
telling lawyer jokes to lawyers!

|------------------------------------------------------------------------|
|"does he bill you for those calls?"                                     |
|------------------------------------------------------------------------|

No.

|------------------------------------------------------------------------|
|"Have you looked at other third-party tools that can make sense         |
|of Tbird mailboxes?"                                                    |
|------------------------------------------------------------------------|

No.
(S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)

Back to sci.electronics.design | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Parts Shortage? Cursitor Doom <cd@notformail.com> - 2026-03-17 23:30 +0000
  Re: Parts Shortage? Martin Brown <'''newspam'''@nonad.co.uk> - 2026-03-18 09:26 +0000
    Re: Parts Shortage? Cursitor Doom <cd@notformail.com> - 2026-03-18 13:39 +0000
    Re: Parts Shortage? TTman <kraken.sankey@gmail.com> - 2026-03-18 22:03 +0000
  Re: Parts Shortage? john larkin <jl@glen--canyon.com> - 2026-03-18 03:35 -0700
    Re: Parts Shortage? Cursitor Doom <cd@notformail.com> - 2026-03-18 13:35 +0000
      Re: Parts Shortage? john larkin <jl@glen--canyon.com> - 2026-03-18 07:47 -0700
        Re: Parts Shortage? Lasse Langwadt <llc@fonz.dk> - 2026-03-18 17:17 +0100
      Re: Parts Shortage? Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-03-18 22:44 +0000
        Re: Parts Shortage? Don Y <blockedofcourse@foo.invalid> - 2026-03-18 15:51 -0700
          Re: Parts Shortage? Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-03-19 20:33 +0000
            Re: Parts Shortage? Don Y <blockedofcourse@foo.invalid> - 2026-03-19 17:53 -0700
              Re: Parts Shortage? Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-03-20 21:27 +0000
                Re: Parts Shortage? Don Y <blockedofcourse@foo.invalid> - 2026-03-21 01:10 -0700
                Re: Parts Shortage? Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-03-21 20:08 +0000
                Re: Parts Shortage? Don Y <blockedofcourse@foo.invalid> - 2026-03-21 13:48 -0700
      Re: Parts Shortage? Bill Sloman <bill.sloman@ieee.org> - 2026-03-19 18:39 +1100
        Re: Parts Shortage? bitrex <user@example.net> - 2026-03-22 17:25 -0400
    Re: Parts Shortage? Martin Brown <'''newspam'''@nonad.co.uk> - 2026-03-19 12:58 +0000
      Re: Parts Shortage? Cursitor Doom <cd@notformail.com> - 2026-03-20 18:06 +0000

csiph-web