[sf-lug] iris.well.com is unknown (meta)

Thu Jan 10 10:27:37 PST 2019

Michael,
I did not create the subject Wifi woes,
someone else did that. For the subject
of the message to which you responded
I had written "iris.well.com is unknown".
(I don't know how '(meta)' got up there
in this message.) I have verified my claims
of the Subject by seeing such in my
Thunderbird Sent "folder".

See attached screenshot showing Subject and timestamp

On 1/9/19 11:36 PM, Michael Paoli wrote:
>> From: "James Stockford" <jim at well.com>
>> Subject: Re: [sf-lug] iris.well.com is unknown <---!!
>> Date: Wed, 9 Jan 2019 22:43:16 -0800
>
>> The subject is "iris.well.com is unknown"
> Yes, because I changed the Subject: header.  These things don't happen
> by magic.  You responded and, ooh, almost by magic - but definitely not -
> by default ... you get the same Subject: header ... that I'd set.
JS: What do you mean "Subject: header"?

>
>> I did not mention "wifi" in the previous post.
>
> Your previous post started with:
> Subject: Re: [sf-lug] Wi-Fi woes
> So please explain to us all how that is not mentioning Wi-Fi/wifi.
> Not only is it mentioned, but it's mentioned first, and foremost -
> well before anything else, and before even *looking* at anything else.
> There's your opportunity to well and clearly specify what you wish to
> discuss or announce or such, and it says ... Wi-Fi woes.
> JS: I did not write that, someone else wrote that in lieu
> of a previous subject.
>
> Y' know, whole lot 'o folks actually look at the Subject:
> header, and it matters, many might look and see:
> Re: [sf-lug] Wi-Fi woes
> And think - I'd be more than happy to answer a relevant DNS question,
> but I'm sick of Wi-Fi cr*p ... [DELETE]
> And maybe the exact assistance you were looking for is a lost opportuntiy
> because you couldn't bother to update the Subject: header.
> It really gets annoying and tiresome after a while.
> Maybe I'll stop responding to messages - at least from some chronic
> offenders - that can't be bothered to reasonably update their
> Subject: headers
JS: I don't understand what you mean by "Subject: headers"(or "Subject 
header");
is this technical terminology referring to some kind of email header that
has to do with the Subject field?
>
>> For sure it is not wifi because my laptop only
>> lets me use a wired connection to my internet
>> access device.
>
> Great, then don't have it under pretense of Wi-Fi.
I didn't.
>
>>>> From: "James Stockford" <jim at well.com>
>>>> Subject: Re: [sf-lug] Wi-Fi woes
>>>> Date: Wed, 9 Jan 2019 12:27:04 -0800
>>>
>>>> I've discovered another post-disaster symptom
>
> And also ...
> How many millions of people died in this disaster?
> Uhm, thousands?
> Okay, how many human fatalities?
> Uh, ... zero, eh?
> Serious human injuries?
> Serious risk to life/property/environment/species?  How many were at 
> risk?
> I don't think I caught reference to it on the news, do you have a 
> credible
> reference to such?
> Disaster, huh?
JS: For me, it's been a disaster, but for the last
couple of transmissions from me I have not
mentioned wifi.
>
> Maybe you want to try or switch to a different forum type, that's
> typically significantly more tolerant of inaccurate and incomplete
> submissions, e.g. much more interactive, such as IRC.
> Many distros have support (also) via IRC, some/many of 'em even have
> quite highly excellent support there.  Many of them also log, and save
> and make that available continuously (or nearly so), or with (about)
> daily updates of each day's log being posted (and sometimes the
> saving and posting may or may not be something the distro does/supports,
> sometimes other(s) add it as "feature").
> JS: The sf-lug mailing list is open to anyone who has problems
> with Linux. My guess is that such people are less than thoroughly
> familiar with terms and concepts, especially if their problems are
> impactful to the point of frustration and panic. I have written some
> things that are erroneous, but I don't think I deserve snide replies.
>
> JS: For the last six or so years I have become discouraged, party because
> of the many changes in Ubuntu and partly because of the flame-war
> types of responses that I believe are not helpful. You and Rick blame
> me for mis-stating my problems, which is discouraging in itself, and
> adds weariness to my ability to read what may be helpful.
> Note, if you can, and no blame at this point if you can not, that in
> one of my early requests for help I asked for suggestions of commands
> I should run so I can send the output to help clarify. I don't think I am
> responsible for most of the bloat in these recent threads--I have tried
> politely to respond to your criticisms.

> Though for some such, on IRC, they might more-or-less expect folks to
> first at least reasonably check the relevant resources/information
> first (e.g. if you're hoppin' on to report and complain about a bug, and
> haven't even bothered to check if it's a known reported bug, one may
> typically expect such behavior to be frowned upon ... something much
> more appropriate might be like asking some particular question about
> a known reported bug that wouldn't really be appropriate for the
> bug tracking, but that folks may be able to point to relevant resource
> or information to get the question answered).
> JS: I have never done such. I look for similar problems based on
> text that my system presents, as best I can discover them.
> I am not in the habit of using IRCs; I am not familiar with them and
> do not usually think to use them.
>
>
> _______________________________________________
> sf-lug mailing list
> sf-lug at linuxmafia.com
> http://linuxmafia.com/mailman/listinfo/sf-lug
> Information about SF-LUG is at http://www.sf-lug.org/<br>
> Related Information <br>
> http://www.shallowsky.com/blog/<br>
> http://explainshell.com/ <br>
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: SentSubject2019-01-10 10-14-45.png
Type: image/png
Size: 21227 bytes
Desc: not available
URL: <http://linuxmafia.com/pipermail/sf-lug/attachments/20190110/40c625ae/attachment-0001.png>