Hello All!

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

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


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

Hi, August!

23 ¬ © 21 08:49, August Abolins -> All:

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

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

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

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

Have nice nights.
Brother Rabbit.

--- Œ â, ª®­¥ç­®, ­¥ ãªà è ¥â ¬®î à¥çì, ­® ¤¥« ¥â ¬®¨ ¯à®áì¡ë ¡®«¥¥ ¯®­ïâ­ë¬¨.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/58.10)

Hello Brother Rabbit!

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

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

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

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

At first, it was believed that between ']' and '(' there can not be even
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)

Does Synchronet have any markup support?

Yes, but not [,] or (,).

Synchronet uses..

*for bold text*
/italic text/
#inverse text#
_underline text_

--- BBBS/Li6 v4.10 Toy-4
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.3)

Hi Brother,
...Greets from my Telegram app!

Hi, August!

23 ¬ © 21 08:49, August Abolins -> All:

[Ubuntu on an iMac]
(https:photos.kolico.catmpubuntu-on-imac-IMG_20210522.jpg)

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

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

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

Have nice nights.
Brother Rabbit.

Hey @BroRabbit, ..I'd like to point out that the two /'s, (one after kolico.ca, and the one after tmp), went missing when that text link passed through your bot.
https://brorabbit.g0x.ru/pic/60ab0c6b.jpg


Ciao!
/|ug (https://t.me/aabolins)

... Searchable Help for OXP https://openxp.kolico.ca
--- Want fido for iOS/MacOS/Android/Win/Linux? Info=https://shrtco.de/tpJ9yV
* Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)