1. Forum
  2. Fidonet
  3. LITRPG

  • Oooooooo I like

    From Dr Sharon Aitken@2:460/256 to All on Wed Nov 2 18:15:11 2022
    Oooooooo I like it

    --- tg BBS v0.7.1
    * Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)
  • From Dan Clough@1:123/115 to Dr Sharon Aitken on Wed Nov 2 11:34:00 2022
    Dr Sharon Aitken wrote to All <=-

    Oooooooo I like it

    You like what? Learn how to quote some context when replying.



    ... Ignorance can be cured. Stupid is forever.
    === MultiMail/Linux v0.52
    --- SBBSecho 3.15-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:123/115)
  • From John Dovey@4:920/1.1 to Dan Clough on Wed Nov 2 12:49:14 2022

    Dr Sharon Aitken wrote to All <=-


    Oooooooo I like it


    You like what? Learn how to quote some context when replying.

    As it happens, Sharon uses Telegram to participate in this echo. on Telegram, it was quite clear what she was responding to.

    JD

    --- AfterShock/Android 1.6.8
    * Origin: Firecat Mobile (4:920/1.1)
  • From Dan Clough@1:123/115 to John Dovey on Wed Nov 2 13:43:00 2022
    John Dovey wrote to Dan Clough <=-

    Dr Sharon Aitken wrote to All <=-

    Oooooooo I like it

    You like what? Learn how to quote some context when replying.

    As it happens, Sharon uses Telegram to participate in this echo.
    on Telegram, it was quite clear what she was responding to.

    Yeah, that's nice. What percentage of the readers in this echo do you
    think use Telegram? That's right, very few.

    Replies like that break the conversation for everyone else, and do not
    conform to the established/preferred methods of communicating on a
    FidoNet echo.


    ... He does the work of 3 Men...Moe, Larry & Curly
    === MultiMail/Linux v0.52
    --- SBBSecho 3.15-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:123/115)
  • From Dr Sharon Aitken@2:460/256 to Dan Clough on Wed Nov 2 21:59:49 2022
    Dr Sharon Aitken wrote to All <=-
    Oooooooo I like it
    You like what? Learn how to quote some context when replying.
    ... Ignorance can be cured. Stupid is forever.
    === MultiMail/Linux v0.52

    Psycho-analysing....

    --- tg BBS v0.7.1
    * Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)
  • From John Dovey@4:920/1.1 to Dan Clough on Wed Nov 2 14:03:55 2022

    John Dovey wrote to Dan Clough <=-

    Dr Sharon Aitken wrote to All <=-


    Oooooooo I like it

    You like what? Learn how to quote some context when replying.

    As it happens, Sharon uses Telegram to participate in this echo.
    on Telegram, it was quite clear what she was responding to.


    Yeah, that's nice. What percentage of the readers in this echo do you

    think use Telegram? That's right, very few.

    Bzzzzt. nope. In THIS echo, which I created and moderate, a majority of the people who participate regularly use Telegram.


    Replies like that break the conversation for everyone else, and do not

    conform to the established/preferred methods of communicating on a

    FidoNet echo.

    So?


    JD
    --- AfterShock/Android 1.6.8
    * Origin: Firecat Mobile (4:920/1.1)
  • From John Dovey@4:920/1.1 to Dr Sharon Aitken on Wed Nov 2 14:04:10 2022

    Dr Sharon Aitken wrote to All <=-
    Oooooooo I like it
    You like what? Learn how to quote some context when replying.
    ... Ignorance can be cured. Stupid is forever.
    === MultiMail/Linux v0.52

    Psycho-analysing....
    LOL.

    JD
    --- AfterShock/Android 1.6.8
    * Origin: Firecat Mobile (4:920/1.1)
  • From August Abolins@2:221/1.58 to Dan Clough on Wed Nov 2 17:54:00 2022
    Hello Dan Clough!

    ** On Wednesday 02.11.22 - 13:43, Dan Clough wrote to John Dovey:

    Replies like that break the conversation for everyone
    else, and do not conform to the established/preferred
    methods of communicating on a FidoNet echo.

    No problem here. The message was sequential to the original
    post.

    And I don't think you alone can define and support what are "established/preferred methods". :D


    --
    ../|ug

    --- OpenXP 5.0.51
    * Origin: What're you doing in the wardrobe? - Narnia business. (2:221/1.58)
  • From Dan Clough@1:123/115 to John Dovey on Wed Nov 2 20:06:00 2022
    John Dovey wrote to Dan Clough <=-


    John Dovey wrote to Dan Clough <=-

    Dr Sharon Aitken wrote to All <=-


    Oooooooo I like it

    You like what? Learn how to quote some context when replying.

    As it happens, Sharon uses Telegram to participate in this echo.
    on Telegram, it was quite clear what she was responding to.


    Yeah, that's nice. What percentage of the readers in this echo
    do you

    think use Telegram? That's right, very few.

    Bzzzzt. nope. In THIS echo, which I created and moderate, a
    majority of the people who participate regularly use Telegram.

    Bullshit.


    Replies like that break the conversation for everyone else, and
    do not

    conform to the established/preferred methods of communicating on
    a

    FidoNet echo.

    So?

    Since I intentionally left the steaming pile of mess above the way it
    appears in a non-telegram message reader, I'd say the answer is obvious,
    isn't it?

    Don't be an ass. Telegram sucks, badly.


    ... Your proctologist called. He found your head.
    === MultiMail/Linux v0.52
    --- SBBSecho 3.15-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:123/115)
  • From Dan Clough@1:123/115 to August Abolins on Wed Nov 2 20:21:00 2022
    August Abolins wrote to Dan Clough <=-

    Replies like that break the conversation for everyone
    else, and do not conform to the established/preferred
    methods of communicating on a FidoNet echo.

    No problem here. The message was sequential to the original
    post.

    "Sequential" isn't the main issue. It's the complete lack of quoting
    for context; or, if there is an attempt at quoting, it's a garbled up
    mess of junk, very difficult to read. Look at the John Dovey reply to
    me in this very thread for a perfect example of that.

    And I don't think you alone can define and support what are "established/preferred methods". :D

    It isn't me alone. If you've been around Fidonet for a while, it's just
    a known thing. Has been for 30 years, and any actual Fidonet user/sysop
    knows this.

    Telegram sucks, it's that simple.


    === MultiMail/Linux v0.52
    --- SBBSecho 3.15-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:123/115)
  • From John Dovey Firecat@2:460/256 to Dan Clough on Thu Nov 3 04:28:25 2022
    August Abolins wrote to Dan Clough <=-
    Replies like that break the conversation for everyone
    else, and do not conform to the established/preferred
    methods of communicating on a FidoNet echo.
    No problem here. The message was sequential to the original
    post.
    "Sequential" isn't the main issue. It's the complete lack of quoting
    for context; or, if there is an attempt at quoting, it's a garbled up mess of junk, very difficult to read. Look at the John Dovey reply to
    me in this very thread for a perfect example of that.
    And I don't think you alone can define and support what are
    "established/preferred methods". :D
    It isn't me alone. If you've been around Fidonet for a while, it's just a known thing. Has been for 30 years, and any actual Fidonet user/sysop knows this.
    Telegram sucks, it's that simple.

    === MultiMail/Linux v0.52

    What's interesting is that the post that you complained about was *not* from Telegram, while this one is.
    If you did a microsecond of self reflection, you'd realize that no-one is going to get off your lawn.

    JD

    --- tg BBS v0.7.1
    * Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)
  • From August Abolins@2:221/1.58 to Dan Clough on Wed Nov 2 21:40:00 2022
    Hello Dan!

    ** On Wednesday 02.11.22 - 20:21, you wrote:

    ..Look at the John Dovey reply to me in this very thread
    for a perfect example of that.

    I did. But I guess YOU didn't notice that his message was NOT
    from using Telegram. ;)
    --
    ../|ug

    --- OpenXP 5.0.51
    * Origin: What're you doing in the wardrobe? - Narnia business. (2:221/1.58)
  • From Dan Clough@1:123/115 to John Dovey Firecat on Thu Nov 3 07:37:00 2022
    John Dovey Firecat wrote to Dan Clough <=-

    August Abolins wrote to Dan Clough <=-
    Replies like that break the conversation for everyone
    else, and do not conform to the established/preferred
    methods of communicating on a FidoNet echo.
    No problem here. The message was sequential to the original
    post.
    "Sequential" isn't the main issue. It's the complete lack of quoting
    for context; or, if there is an attempt at quoting, it's a garbled up
    mess of junk, very difficult to read. Look at the John Dovey reply to
    me in this very thread for a perfect example of that.
    And I don't think you alone can define and support what are
    "established/preferred methods". :D
    It isn't me alone. If you've been around Fidonet for a while, it's just
    a known thing. Has been for 30 years, and any actual Fidonet user/sysop knows this.
    Telegram sucks, it's that simple.

    === MultiMail/Linux v0.52

    What's interesting is that the post that you complained about was
    *not* from Telegram, while this one is. If you did a microsecond
    of self reflection, you'd realize that no-one is going to get off
    your lawn.

    I'm not asking anyone to get off my lawn. I'm not even asking anything
    of you, personally. At least you have demonstrated that it is
    *POSSIBLE* to correctly quote context and submit a decently formatted
    message to the echo. It seems that many (most/all) other users of
    Telegram seem to be unable to do that. Since many/most echo users DON'T
    use Telegram, couldn't some "pressure" be applied to those others to
    *TRY* to post better? That's all I'm looking for. I don't care what
    you use to post to a Fidonet echo, but your post should look like other
    posts look. Like they have for 30 years in Fidonet. Whether "AA"
    believes it or not, there *ARE* established "proper" methods of posting.



    ... So easy, a child could do it. Child sold separately.
    === MultiMail/Linux v0.52
    --- SBBSecho 3.15-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:123/115)
  • From Dan Clough@1:123/115 to August Abolins on Thu Nov 3 07:40:00 2022
    August Abolins wrote to Dan Clough <=-

    ..Look at the John Dovey reply to me in this very thread
    for a perfect example of that.

    I did. But I guess YOU didn't notice that his message was NOT
    from using Telegram. ;)

    Indeed I did not notice. That almost makes it worse. You saw how that
    post looked. Is that how a message should look in a Fidonet echo?
    Completely trashed/garbled/line breaks, and no proper quoting? You like
    it that way? You think that's perfectly OK?

    As I just wrote to him, I don't give a rat's ass what you or anyone uses
    to post to this or any other echo. But the post should be properly
    formatted to look correct, like (most) posts have been for 30 years.
    You know that's right, so don't argue just for the sake of arguing.



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