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


Присутствуют сообщения из эхоконференции FTSC_PUBLIC с датами от 13 Sep 13 18:57:24 до 15 Nov 24 00:30:01, всего сообщений: 7128
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 5308 из 7128 ====================================== FTSC_PUBLIC =
От   : Rob Swindell                     1:103/705          18 Dec 20 23:20:47
Кому : Maurice Kinal                                       18 Dec 20 23:20:47
Тема : alternative DateTime (ref: fts-0001.016)
FGHI : area://FTSC_PUBLIC?msgid=30759.ftsc_pub@1:103/705+244357f6
На   : area://FTSC_PUBLIC?msgid=1:153/7001+5fdd88a8
= Кодировка сообщения определена как: ASCII ==================================
Ответ: area://FTSC_PUBLIC?msgid=1:153/7001+5fddc190
==============================================================================
  Re: alternative DateTime (ref: fts-0001.016)
  By: Maurice Kinal to Rob Swindell on Sat Dec 19 2020 04:59 am

> Hey Rob!
>
>  RS> I find it interesting you would cause the type 2.2 packet header
>  RS> a "scam".
>
> I got burned by it way back when and almost quit.  However the fighting
> spirit later got awoken in me and it sparked a bout of backwards engineering
> which is still part of the routine(s) being deployed in this neck of the
> woods.  Anyhow I will still cite it as evidence that not all is as it seems
> in Fidonet wrt backwards compatibilty/standards/whatever.
>
> Are you defending it?

I'm not defending anything, just sharing my observations on how FidoNet (collectively) is vehemently opposed to anything that is not interoperable with FidoNet software from the 80's or 90's.

>  MK>> isn't the pktheader in fts-0001.016 not supported by ALL
>  MK>> concerned especially the echomail movers?
>
>  RS> Isn't it?
>
> Nope.  Like I said previously I only am aware of one and it's been awhile
> since I tested it there so even that one may not support it anymore.  He is
> still moving mail and it wouldn't be too hard to test it out if needed.
>
>  RS> And type 2.2 packet headers are backward compatible with type
>  RS> 2.0/stone-age headers, so it's pretty easy to autodetect the
>  RS> type and support all the type-2 variants of incoming packets.
>
> Really?

Really. And it's been that way since about 1992.

> Have you actually tested that?

Of course.

> Or is this some type of blind faith statement on your part?

I don't operate that way.

> Also, while I am at it, I only found one that could
> handle Type 2+ pktheaders and it wasn't the same one that could do type 2
> pktheaders.  Most are 2.2 only and don't even know it.

"Most" what? SBBSecho defaults to exporting type 2+ packets and can import and export type 2.0, 2e, 2+ and 2.2. Type 2.2 packets are actually pretty rare from what I've observed.
http://wiki.synchro.net/ref:fidonet_packets

>  RS> Whoa there skippy! What on Earth are you talking about?
>
> :-)  Nothing you need to worry about ... I think.

Sounds like it. :-)
--- SBBSecho 3.11-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

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