Re: Test
By: Michiel van der Vlist to mark lewis on Sat Jun 06 2020 12:44 pm
> Hello mark,
>
> On Friday June 05 2020 09:06, you wrote to me:
>
> ml>>> @MSGID: 2814.fido-fidotest@1:3634/12 233f62a9
>
> MvdV>> "2814.fido-fidotest@1:3634/12" is not a valid return address
> MvdV>> for the originating network, as mandated by FTS-009.
>
> ml> it seems to work perfectly fine in the years it has been being used...
>
> Your assertion is falsified by Tommi Koivula's observation that at least one
> software has problems with it.
I just read back through Tommi's posts here and did not find any observation of
any problem with Synchronet/SBBSecho's FTN MSG-IDs. Are you sure about that?
> ml> granted the software does not purport to even implement FTS-0009...
>
> "Purport" is not in my dictionary, Google translate seems to think it is a
> noun. Whatever "purport" means in this context, by using the "MSGID"
> identifier, it certainly suggests ands appears to follow FTS-0009.
Purport is a verb: https://www.merriam-webster.com/dictionary/purport
Synonym to "claim". And at least *I* (the author) claim that
Synchronet/SBBSecho implements FTS-9.
> If it does not implement FTS-0009 but some other means to uniquely identify
> a message instead, it has hijacked the MSGID identifier.
Nope, no hijacking going on.
> MvdV>> An anomaly does not need to be a problem in order to qualify
> MvdV>> for reporting.
>
> ml> i agree with you for real anomalies... these are not such
>
> So you say, but the classification of "real" vs "not real" is entirely
> yours. That it is not a "real" anomaly and therefore does not qualify for
> reporting is just your opinion, it is not fact.
>
> ml> and have been around in widespread use for decades...
>
> "for decades" does not unmake it an anomaly. There is no statue of
> limitation on anomalies. Many anomalies have been present for centuries and
> they still are anomalies.
>
> ml> limited horizons are not an excuse ;)
>
> "Limited horizon" is a pleonasm. An horizon is always a limit. By
> definition.
Speaking of "limited horizons", let's take a look at the MSG-ID of your posted
message: 2:280/5555 5edb7807
Huh... that "53db7808" looks suspiciously like a Unix time_t value:
time_t 1591441415 (0x5EDB7807) ISO 2020-06-06 04:03:35.000-07:00
So what happens on *your* system when 2 users (if you have any) post a message
in the same message area within the same wall-clock second? You, my friend,
have a broken FTN MSG-ID generation algorithm there on *your* system. You
should fix that, not that I really care. FTN systems are already broken in so
many ways, what's another? :-)
digital man
Synchronet "Real Fact" #21:
The first commericial sale of Synchronet was to Las Vegas Playground BBS
(1992).
Norco, CA WX: 66.1øF, 71.0% humidity, 5 mph E wind, 0.00 inches rain/24hrs
--- SBBSecho 3.11-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
|