Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 2021  |
|  Richard Miles to Kurt Weiske  |
|  Re: https://s00.yaplakal.com/pics/pics_o  |
|  20 Sep 20 16:12:10  |
 MSGID: 2:460/58 -1001206383505:138 REPLY: 2:460/58 134 PID: Telegram to fido gate by Stas Mishchenkov CHRS: CP866 2 TGUID: 249680311 REPLYTO 2:460/58 249680311 RealName: 0 Answering a msg from Kurt Weiske: >-=> Brother Rabbit wrote to All <=- > > BR> 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) SEEN-BY: 1/123 90/1 114/705 120/340 123/120 131 226/30 227/114 702 SEEN-BY: 229/101 424 426 452 664 1016 240/5832 249/206 317 400 292/854 SEEN-BY: 298/25 305/3 317/3 322/757 342/200 PATH: 460/58 640/1384 221/1 6 153/757 261/38 250/1 8 317/3 229/426 |
[ << oldest | < older | list | newer > | newest >> ]