• Re: Bad behaviour not wanted.

    From Carol Shenkenberger@1:275/1000 to Dan Clough on Sat Feb 18 15:05:48 2023
    Re: Re: Bad behaviour not wanted.
    By: Dan Clough to Carol Shenkenberger on Sun Dec 11 2022 06:28 pm

    Carol Shenkenberger wrote to Dan Clough <=-

    Re: Re: Bad behaviour not wanted.
    By: Dan Clough to August Abolins on Thu Nov 17 2022 07:54 am

    complete and utter clusterf**k. Effectively not readable
    due to format mangling, lack of quoting, and general
    stupidity.

    You keep ignoring the fact that your first instance of a
    complaint in LITRGP was based on a quoting issue due to
    Aftershock, and not Tg. I agree with your latter point though;
    since your participation, stupidity has emerged.

    I don't know (or care) what Aftershock is, and either way, whether it's that or TG, or both, the end result is: The echo is trashed and basically un-useable by those using "traditional" Fidonet software / message reading tools. Your claim that I'm stupid is just sour grapes
    at being called out on it. Anyone can see that I'm telling the truth by simply trying to read messages in that group. It's that simple, simpleton.

    Dan, can you tell me why my ASIAN_LINK never had that? We were
    in the first few, and we welcome Telegram users. There have been
    no issues otherthan a few *early* ones that caused odd tear
    lines. They did not affectoperations and were quickly patched by
    Stas.

    Have you considered checking/reading echomail more often than once a
    month? I've been all through this and don't feel like re-hashing it yet again. Read the complete thread.



    ... All the easy problems have been solved.
    === MultiMail/Linux v0.52

    Why should I Dan? If you can't explain it, then it never happened.

    xxcarol
    --- SBBSecho 2.12-Win32
    * Origin: Shenk's Wandering Star (1:275/1000)
  • From Dan Clough@1:123/115 to Carol Shenkenberger on Sat Feb 18 19:42:00 2023
    Carol Shenkenberger wrote to Dan Clough <=-

    complete and utter clusterf**k. Effectively not readable
    due to format mangling, lack of quoting, and general
    stupidity.

    You keep ignoring the fact that your first instance of a
    complaint in LITRGP was based on a quoting issue due to
    Aftershock, and not Tg. I agree with your latter point though;
    since your participation, stupidity has emerged.

    I don't know (or care) what Aftershock is, and either way, whether it's that or TG, or both, the end result is: The echo is trashed and basically un-useable by those using "traditional" Fidonet software / message reading tools. Your claim that I'm stupid is just sour grapes
    at being called out on it. Anyone can see that I'm telling the truth by simply trying to read messages in that group. It's that simple, simpleton.

    Dan, can you tell me why my ASIAN_LINK never had that? We were
    in the first few, and we welcome Telegram users. There have been
    no issues otherthan a few *early* ones that caused odd tear
    lines. They did not affectoperations and were quickly patched by
    Stas.

    Have you considered checking/reading echomail more often than once a
    month? I've been all through this and don't feel like re-hashing it yet again. Read the complete thread.

    Why should I Dan?

    Well, I guess so you can (maybe) understand what is being discussed
    here. Duh.

    If you can't explain it, then it never happened.

    That's just it... I *HAVE* explained it, several times, in the
    discussion thread. As I already said, if you'd read it you may see
    that.

    Well done on going *TWO* months this time before bothering to "catch up"
    with reading echomail.



    ... So easy, a child could do it. Child sold separately.
    === MultiMail/Linux v0.52
    --- SBBSecho 3.20-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:123/115)