This is what I saw for my first [link](http) test in FIDOTEST https://brorabbit.g0x.ru/pic/60aa507a.jpg
This is a *good* reason to abandon the program in which
the message was created.
First, it inserted a character that _isn't_ there;
secondly, it inserted a character that _shouldn't_ _be_ in
the Fido messages. I mean the character 0x0A (you see
%0A).
This is a *good* reason to abandon the program in which
the message was created.
Heheh! That's a good one. Made me laugh! :D
First, it inserted a character that _isn't_ there;
secondly, it inserted a character that _shouldn't_ _be_ in
the Fido messages. I mean the character 0x0A (you see
%0A).
The x0A is legit. It's the same as a hard CR when this system
prepares a message for which I've configured a maximum of 63
chars per line.
What I think your bot/tosser logic algorithm could do is look
for illegal chars in the string of the (http....) part, and
simply take them out.
IOW, if it detects a [ and ] and ( and ) as consecutive pairs,
then assume it is markup for a link, and then only allow valid
chars inbetween the round braces.
First, it inserted a character that _isn't_ there;
secondly, it inserted a character that _shouldn't_ _be_
in the Fido messages. I mean the character 0x0A (you see
%0A).
The x0A is legit. It's the same as a hard CR when this
system prepares a message for which I've configured a
maximum of 63 chars per line.
By the way, this is a violation of the standard. The 0x0A
symbol *MUST* not be in the message at all. The 0x0D
symbol should not appear where the author of the message
did not put it with his own hands.
What I think your bot/tosser logic algorithm could do is
look for illegal chars in the string of the (http....)
part, and simply take them out.
Although, the standard says that when processing messages,
the 0x0A character must be ignored.
IOW, if it detects a [ and ] and ( and ) as consecutive
pairs, then assume it is markup for a link, and then only
allow valid chars inbetween the round braces.
Yes. I can put such a spike, but it will mean that
formally I will have to change the message, which in
itself is not entirely good.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 44:55:47 |
Calls: | 6,648 |
Files: | 12,197 |
Messages: | 5,329,767 |