https://s00.yaplakal.com/pics/pics_original/6/8/3/14737386.jpg


--- tg2fido.pl
* Origin: Telegram to fido gate by Stas Mishchenkov ()

Brother Rabbit wrote to All <=-

https://s00.yaplakal.com/pics/pics_original/6/8/3/14737386.jpg

Starting to get a little frustrated with the Telegram integration.
Fidonet's always been about communication, and one of the things I
appreciate about it is the long-form capability of Fido echoes - most
BBSes and offline readers support paragraphs and formatting, unlike
Facebook or Twitter.

Posting links to jpegs with no accompanying text loses something in
the translation once it gets back to the BBSes it originates from.

When I see a message in a Fido echo with no content save for an image
URL, I'm reminded that just because something can be done, that it
doesn't follow that it should be done.

Or, maybe I'm just old-school.



... Start where you are. Use what you have. Do what you can.
--- MultiMail/XT v0.52
* Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/700)

Hello Kurt!

** On Friday 18.09.20 - 07:38, Kurt Weiske wrote to Brother Rabbit:

Posting links to jpegs with no accompanying text loses
something in the translation once it gets back to the
BBSes it originates from.

I missed having the accompanying text on those posts too, but
I think those were just one-of tests. At the same time, Stas
was showing us that a picture/file post has convenient storage
on his system. It's very nice and easy to work with image
attachments and sharing files when posting on the Telegram
side.

Without accompanying text with an image link it would be no
better than people who just post pics on facebook. Echomail
can be better than that. We can always help educate
participants to do better.


--
../|ug

--- OpenXP 5.0.46
* Origin: (2:221/1.58)

Answering a msg from Kurt Weiske:

Brother Rabbit wrote to All <=-

https://s00.yaplakal.com/pics/pics_original/6/8/3/14737386.jpg

Starting to get a little frustrated with the Telegram integration.
Fidonet's always been about communication, and one of the things I
appreciate about it is the long-form capability of Fido echoes - most
BBSes and offline readers support paragraphs and formatting, unlike
Facebook or Twitter.

Posting links to jpegs with no accompanying text loses something in
the translation once it gets back to the BBSes it originates from.

When I see a message in a Fido echo with no content save for an image
URL, I'm reminded that just because something can be done, that it
doesn't follow that it should be done.

Or, maybe I'm just old-school.

... Start where you are. Use what you have. Do what you can.

I do like like seeing some explanation at least. I don't mind clicking the link to go check it out if I know what it is. I'm used to doing that on my desktop with my telnet client and a browser already.

The formatting should be fine and quoting, while not as easily "pick and choose" as it is in a full screen editor, can still be done.


--- tg2fido.pl
* Origin: Telegram to fido gate by Stas Mishchenkov (2:460/58)

Hello Richard!

** On Sunday 20.09.20 - 16:12, Richard Miles wrote to Kurt Weiske:

Starting to get a little frustrated with the Telegram
integration. Fidonet's always been about communication,
and one of the things I appreciate about it is the long-
form capability of Fido echoes - most BBSes and offline
readers support paragraphs and formatting, unlike
Facebook or Twitter.

The Telegram gate doesn't reduce communication. I think it has
the potential to expand it and reach smartphone initiates.

Paragraphing is possible. All you have to do in TgM is disable
the SEND on CR LF in the settings.

When I see a message in a Fido echo with no content save
for an image URL, I'm reminded that just because
something can be done, that it doesn't follow that it
should be done.

We can continue to remind each other to follow some FTN-
etiquette: eg. top-quoting, the little indentation on a quoted
paragraph.

Or, maybe I'm just old-school.

Not at all. I think FTN way of doing things has evolved out of
what's better for text communications.

I do like like seeing some explanation at least. I don't
mind clicking the link to go check it out if I know what
it is. I'm used to doing that on my desktop with my
telnet client and a browser already.

On the TgM side, the image is rendered immediately. That could
have the tendency of making new users lazy on the reply that
just has an image.

The formatting should be fine and quoting, while not as
easily "pick and choose" as it is in a full screen
editor, can still be done.

I do miss the pick-n-choose paragraph quoting on the TgM side
when using R)eply.

--
../|ug

--- OpenXP 5.0.46
* Origin: (2:221/1.58)