Добро пожаловать, Гость. Пожалуйста авторизуйтесь здесь.
FGHIGate на GaNJa NeTWoRK ST@Ti0N - Просмотр сообщения в эхоконференции ENET.SYSOP
Введите FGHI ссылку:


Присутствуют сообщения из эхоконференции ENET.SYSOP с датами от 10 Jul 13 21:42:12 до 03 May 24 12:02:39, всего сообщений: 12492
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 10335 из 12492 ===================================== ENET.SYSOP =
От   : Alexey Vissarionov               2:5020/545         14 Feb 21 22:00:22
Кому : Michiel van der Vlist                               14 Feb 21 22:00:22
Тема : Ping
FGHI : area://ENET.SYSOP?msgid=2:5020/545+60297347
На   : area://ENET.SYSOP?msgid=2:280/5555+6028f7de
= Кодировка сообщения определена как: CP866 ==================================
Ответ: area://ENET.SYSOP?msgid=2:280/5555+6029b25e
==============================================================================
Good ${greeting_time}, Michiel!

14 Feb 2021 11:04:12, you wrote to me:

AV>> The PoC invalidates these lines. The "two steps before becoming the
AV>> reference implementation"
AV>> https://github.com/huskyproject/hpt/blob/master/misc/pong.pl does
AV>> almost the same thing, being forked from the PoC code. Are there any
AV>> good reasons not to do that?
MvdV> 1) I am not a lemming, I do not just follow for the sake of
MvdV> following. Not even the "two steps before becoming the reference
MvdV> implementation".

The author of PoC had some really good reasons to do that, n'est pas?

MvdV> 2) It violates my principle of "pass 'as is', unless there is a
MvdV> clear technical reason for not doing so".

Reply != pass

MvdV> So far I have seen no clear technical reason for invalidating
MvdV> tear lines and origin lines in a PING respons. Origin lines do
MvdV> not belong in netmail anyway, so that would be a case of GiGo.
MvdV> So.. can you give me a clear technical reason? "PoC does it",
MvdV> is not a valid clear technical reason.

The robot does pass all original messages "as is". But when it generates _new_ _message_ with the reply, it _must_ (as in FTA-1006) make sure nothing would affect further processing of that message.

Quoting the original message back (as in FSC-0032) could be a good solution. However, the FSC-0032 explicitly states: "Kludge lines, including tear lines and origins lines are not normally quoted, but when they are - they must never be quoted exactly - this definitely causes problems with other software!"


--
Alexey V. Vissarionov aka Gremlin from Kremlin
gremlin.ru!gremlin; +vii-cmiii-ccxxix-lxxix-xlii

... that's why I really dislike fools.
--- /bin/vi
* Origin: ::1 (2:5020/545)

К главной странице гейта
Powered by NoSFeRaTU`s FGHIGate
Открытие страницы: 0.069554 секунды