Subj : unwrapped link test for telegram
To   : Brother Rabbit
From : August Abolins
Date : Sun May 23 2021 13:39:00

Hello Brother Rabbit!

** On Sunday 23.05.21 - 18:45, Brother Rabbit wrote to August Abolins:

 AA>> [Ubuntu on an iMac]
 AA>> (https://photos.kolico.ca/tmp/ubuntu-on-imac-IMG_20210522.jpg)

 BR> I agree. One line feed can be allowed, as sometimes it is
 BR> more convenient and aesthetically pleasing.



 AA>> This one should not wrap, but I'm putting the (https://)
 AA>> part immediately after and below the [text part]

 BR> At first, it was believed that between ']' and '(' there can not be even
 BR> a line feed. Now I think, can also allow a space?


Yes.. Something like this would allow cases when a link is  
pretty long:

 [Link 1]
 (https://a really long http address for something can go here)

 [Link 2]
 (https://another really long address for something that could  
otherwise wrap)

 [Link 3]
 (https://yet another really long address string here)


BTW, what was the goal for this markup recognition?  
Technically, from the fido side "[text](link)" markup can be a  
lot of work.

Yes.. the result looks nice and compact on our Telegram apps,  
but I would almost prefer seeing the link in-the-clear rather  
than being "hidden" in the [text].

Telegram makes anything that looks like a link (https://)  
clickable. And all that one has to do is this:

 Link 1
 https://a really long http address for something can go here

 Link 2
 https://another really long address for something that could  
otherwise wrap

 Link 3
 https://yet another really long address string here

(Note.. no use of ] or [ above)


Was your goal to support multiple links in a short line, ie:

 [link1](http://lsdkfjd) and [link2](http://skjdkjf) ?

 ..but even that is a lot of work that only supports Telegram  
users at this point.  Does Synchronet have any markup support?

--
  ../|ug
--- OpenXP 5.0.50
 * Origin: The ONLY point that matters --> . <-- (1:153/757.21)

.