If Fidonet makes it to 2525 then this potentially could be a real message. Let's see how far it goes today.
Well I'll be.. a blast from the future!
Heh, heh. Thank you and I note that the 9 nibble hex string didn't cause any grief, nevermind the bogus obsolete FTN datetime string.
date --date=@$(printf "%d" 0x413ed49c0) = Mon Jan 1 12:00:00 UTC 2525
The ftn datetime stamp could easily be 2025 but that will still put it in the future. The above is the 'correct' datetime.
Yes it is, looks like you are about 7 hours ahead of me.
How about on the original (MSGID: 2:280/464.113 413ed49c0)? What is the ftn msgHeader's datetime stamp say? The virgin one I sent claims "01 Jan 25 12:00:00" which is just shy of six years from now ... assuming 2025 that is,
which of course is wrong. I noticed on a couple online so-called BBS's it was
altered to today's date but that might be just for display purposes. If the
header datetime got altered then I have no issue with it given that I figure i >is bogus even when correct which of course it never is, was or ever will be fo
all time.
It would be nice to know.
The message header here says 1st January, 2025 at 12:00.
Hey Zager And Evans!
If Fidonet makes it to 2525 then this potentially could be a real message.
Let's see how far it goes today.
do you mean 2025? that's the date in the header...
do you mean 2025? that's the date in the header...
Excellent, except it of course that it is wrong ... in more ways than one.
I see in your REPLY no issues with my 9 nibble hex string. That tells
the true tale.
i don't know where it got changed if it was and isn't just a
display anomaly...
especially those that only allocate 8 bytes for the serial number
portion of the string
I'd like to see an example. From what I've observed over the years
the MSGID causes more problems when it isn't there than how many
nibbles there are in the serial number portion.
It looks like it didn't get changed although I cannot confirm that. I'd need to put the node back online to be able to verify that.
But how are you going to find out if that happens in some corner
of fidonet.
You can hardley check every node in fidonet...
Just sayin' :)
That might just fly. What was the node number's name again? Little Mikey's
Brain? As far as I am concerned nothing needs to be changed and the IP addres
is exactly as it was.
I'll get back to you later today.
Quoting Maurice Kinal to Zager And Evans on 01-Jan-2025 12:00 <=-
Hey Zager And Evans!
If Fidonet makes it to 2525 then this potentially could be a real
message. Let's see how far it goes today.
Quoting Maurice Kinal to Alan Ianson on 31-Mar-2019 20:00 <=-
How about on the original (MSGID: 2:280/464.113 413ed49c0)? What is
the ftn msgHeader's datetime stamp say? The virgin one I sent claims
"01 Jan 25 12:00:00" which is just shy of six years from now ...
assuming 2025 that is, which of course is wrong. I noticed on a
couple online so-called BBS's it was altered to today's date but that might be just for display purposes. If the header datetime got
altered then I have no issue with it given that I figure it is bogus
even when correct which of course it never is, was or ever will be for
all time.
It would be nice to know.
Interestingly, in this packet I got this message twice... the
first time with the 2025 date in the header (see the quote header
above), and the second time with the actual date of 31Mar2019.
(just a little late with working through the packets, as often
the case)
Looks like I found a job for the raspberry pi thingy.
Little Mikey's CanadARM - Ladysmith BC, Canada (1:153/7001.2989)
I like it. However I was first.
In more ways than one considering this is a reply to a message that is currently MIA here at the Brain, even though I can see the little board that created it on my desk.
Good thing for backups eh?
Can you post something from the EuroPoint?
In fact there are 272 characters up to this character ->.
Speaking of firsts, you weren't first. The first point here was either/or/bot
points off Janis and/or Carol back around the turn of the century, maybe
sooner. When both were running the project was called "Das Both" but then the
US Navy torpedoed one of them. :::sigh:::
Would you like to inspect those pkt and confirm for me?
Would you like to inspect those pkt and confirm for me?
Yes I would. Please upload them but make sure they are in a tarball so I can differentiate them from regular pkt's.
They are in a file called 757pkts.zip, it's in your inbound.
@MSGID: 2:280/464.113 5ca959ee
@REPLY: 1:153/757.0 0911e3e5
Hallo Alan!
Can you post something from the EuroPoint?
Sure thing. Here is a reply to your msg "MSGID: 1:153/757.0 0911e3e5" requesting something from the EuroPoint. As usual there is at least one line (this one) that is really long. Much longer than 80 characters. In fact there are 272 characters up to this character ->.
Het leven is goed,3634/0
Maurice
... Huil niet om mij, ik heb vi.
--- GNU bash, version 5.0.3(1)-release (x86_64-pc-linux-gnu)
* Origin: Little Mikey's EuroPoint - Ladysmith BC, Canada (2:280/464.113) SEEN-BY: 153/7001 154/10 20 30 40 700 203/0 221/0 6 227/400 229/426 240/5832
SEEN-BY: 280/464 464 5003 310/31 340/800 396/45 423/120 770/1 3634/12 116/116
SEEN-BY: 123/25 150 755 135/300 153/7715 261/38 3634/15 27 50 123/50
SEEN-BY: 18/0 123/0 1/120
@PATH: 280/464 154/10 3634/12
@MSGID: 1:153/757.0 d238b9e4characters
@REPLY: 1:153/7001.2989 5ca95f35
@TZUTC: -0800
@CHARSET: LATIN-1
Speaking of firsts, you weren't first. The first point here was
either/or/bot points off Janis and/or Carol back around the turn of the
century, maybe sooner. When both were running the project was called "Das
Both" but then the US Navy torpedoed one of them. :::sigh:::
I have copies of this message arriving from 153/7715 and 153/250. It appears to me that the one coming from 153/250 does have some ^M
that the one from 153/7715 does not.
Would you like to inspect those pkt and confirm for me?
--- BBBS/Li6 v4.10 Toy-4
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)
SEEN-BY: 57/0 153/250 7001 154/10 20 30 40 700 203/0 221/0 6 227/400 229/426
SEEN-BY: 240/5832 267/800 280/464 5003 310/31 317/2 340/800 393/68 396/45 SEEN-BY: 423/120 712/848 770/0 1 10 100 330 340 772/0 1 210 500 3634/12 SEEN-BY: 116/116 123/25 150 755 135/300 153/7715 261/38 3634/15 27 50 123/50
SEEN-BY: 3634/0 18/0 123/0 1/120
@PATH: 153/757 250 770/1 280/464 154/10 3634/12
this one arrived here in perfect shape...
This line should be unwrapped and is 178 characters long
this message of yours has been manipulated as maurice has been talking about..
Would you like to inspect those pkt and confirm for me?
i would like to see them, if i may, please... please zip them and drop them in
my inbound or send them to my wkitty42 account on gmail...
This line should be unwrapped and is 178 characters long
@MSGID: 1:153/7001.2989 5caa174flong
@REPLY: 1:3634/12.73 5ca9bfbc
Hey mark!
this one arrived here in perfect shape...
How about this reply? It should also bypass the tosser in question from your perspective. This line should be unwrapped and is 178 characters
up to the period at the end.
Life is good,(1:153/7001.2989)
Maurice
... Don't cry for me I have vi.
--- GNU bash, version 5.0.3(1)-release (aarch64-raspi3b+-linux-gnu)
* Origin: Little Mikey's CanadARM - Ladysmith BC, Canada
SEEN-BY: 153/7001 154/10 20 30 40 700 227/400 340/800 3634/12 116/116 123/25
SEEN-BY: 123/150 755 135/300 153/7715 261/38 3634/15 27 50 123/50 3634/0 18/0
SEEN-BY: 123/0 1/120
@PATH: 153/7001 154/10 3634/12
@MSGID: 2:280/464.113 5caa1be7
@REPLY: 1:153/7001.2989 5caa174f
Hallo Maurice!
This line should be unwrapped and is 178 characters long
Yes it is. The path I see is as follows; "PATH: 153/7001 154/10 280/464". I assume it will be the same for mark except without 280/464.
Het leven is goed,131
Maurice
... Huil niet om mij, ik heb vi.
--- GNU bash, version 5.0.3(1)-release (x86_64-pc-linux-gnu)
* Origin: Little Mikey's EuroPoint - Ladysmith BC, Canada (2:280/464.113) SEEN-BY: 1/19 15/0 16/0 19/36 34/999 90/1 104/57 116/18 120/544 123/130
SEEN-BY: 123/140 153/7715 154/10 203/0 218/700 220/60 221/0 222/2 229/426 SEEN-BY: 230/150 152 240/1120 2100 5138 5832 5853 250/1 261/38 100 1466 SEEN-BY: 266/512 267/155 275/100 280/464 5003 5006 282/1031 1056 291/1 111 SEEN-BY: 310/31 320/119 219 340/400 342/13 396/45 423/120 712/848 770/1 SEEN-BY: 801/161 189 2320/105 2454/119 3634/12 5020/715 1042 116/116123/25
SEEN-BY: 123/150 755 135/300 3634/15 27 50 123/50 3634/0 18/0 123/0 1/120 @PATH: 280/464 240/5832 320/219 261/38 3634/12
Would you like to inspect those pkt and confirm for me?
i would like to see them, if i may, please... please zip them and drop
them in my inbound or send them to my wkitty42 account on gmail...
757pkts.zip is in your inbound. :)
a bunch there I am uncertain of but I still see both 770/1
and 153/250 in
and 153/250 in
we need to find out what software this one is running... if they are behind,
they need to update or drop back... we're already aware of one package that ha
problems with the seenbys in its latest alpha/beta/whateveritscalled and the suspicion is they are running that package, too...
yup, arrived here in good shape...
quoting it, of course, reflows it...
the problem is confirmed... one of the PKTs has ^M characters which
should not be there...
got tossed here. What is different in your reply is the extra nodes
in the path lines (two of them now) as follows; "PATH: 153/7001 154/10 203/0 221/1 640/1384 633/280 229/426 393/68 770/1" and "PATH: 153/250
633/280 runs MBSE
I haven't linked to Paul's system
the problem is confirmed... one of the PKTs has ^M characters which
should not be there...
That sounds like a problem Telegard had for a long time...something
having to do with soft CRs and different codepages.
That was a very long time ago now though.
alt-161, 0xA1 in the CP437 table?
alt-161, 0xA1 in the CP437 table?
Are you sure you're not thinking about c1 control codes that range from 0x80 to 0x9f?
http://fileformats.archiveteam.org/wiki/FidoNet_message_packet
not sure how that will come out because it is being interpreted
as a two byte character here :(
tohttp://fileformats.archiveteam.org/wiki/FidoNet_message_packet
I recall reading that and at the time finding absolutely zero references
back that up. I just tried again with no success. I am not sure where that idea comes from
and the closest I could find is the well documented c1 control codes.
It wouldn't surprise me if there was some propietary usage for 0x8d as
a soft line break but finding a reference to back it up is a bit of a challenge if not indeed impossible.
and the closest I could find is the well documented c1 control codes.
It wouldn't surprise me if there was some propietary usage for 0x8d
as a soft line break but finding a reference to back it up is a bit
of a challenge if not indeed impossible.
i'm not sure but it should be documented somewhere in the FTSC documents...
what idea? using that character as a soft-cr in fidonet?
i'm not sure but it should be documented somewhere in the FTSC
documents
what idea? using that character as a soft-cr in fidonet?
Yes. Are you aware of any FTN approved software that actually used that character as a soft line feed?
i'm not sure but it should be documented somewhere in the FTSC
documents
fts-0001.016 states, and I quote;
So called 'soft' carriage returns, 8DH, may mark a previous
processor's automatic line wrap, and should be ignored.
Beware that they may be followed by linefeeds, or may not.
It doesn't say anywhere that applications that use 0x8d as a control code are FTN compliant or even compatible.
I'd guess by the above quote that they aren't given the 'should be ignored' part.
yes, as i've noted in this thread previously
so someone using notepad as their editor is breaking FTN
standards?
I've never noticed any issues with MBSE ... not to say there aren't
any. I managed to compile a 64 bit version way back when MBSE was new
on the scene but never actually used it.
If there are issues, let me know. I am back running MBSE and am
on the development team.
yes, as i've noted in this thread previously
I must have missed that but now that you bring it up I will start
paying attention to it. Usually when I see 8 bit characters I tend to think of them as printable such as your cp437 example of 0x8d and not control codes. It is easy enough to scan for.
so someone using notepad as their editor is breaking FTN
standards?
That isn't what I meant.
All I meant is that 0x8d must not be an approved control code given
that if exists in a message it should be ignored.
However the mention of it must have meant that there was software that produced 0x8d as soft line feeds or soft carriage returns despite
there being no indication of what software that was and still might
be.
The only reference I can find pertains to c1 codes and IBM,
specifically 0x85 as a replacement for \r\n which are liberally used
in MS and DOS-think software to terminate lines. I am betting notepad
is one of them that uses \r\n rather than 0x85 ... or 0x8d for that matter.
If there are issues, let me know. I am back running MBSE and am on
the development team.
Will do except from this angle it looks like you're using golded. ;-)
i was being facetious
so that leaves BBS software and users' readers
in fido's heyday were professional programmers
i was going to write more and a little better but my meds are
kinda kicking in ATM..
others of his may be written via the BBS interface or, if he is
so inclined, even via QWK/QWKE or Bluewave...
0x8d 0x00ec #LATIN SMALL LETTER I WITH GRAVE
I managed to compile a 64 bit version way back when MBSE was new
on the scene but never actually used it.
I haven't linked to Paul's system
this I cannot say with absolute certainty that it is 770/1 ... or
153/250 for that matter. I am guessing there are nodes better
@PATH: 153/7001 757 250 770/1 280/464 221/1 640/1384 633/280
1.0.7.x compiles fin on 64bit systems. This vm is running debian
9 64bit.
You need to track down what software 153/250 is running.
Intresting path your message took.
Understood. In my case there is no BBS to telnet into although I have been ssh'ing to other machines (three in total here) to post and/or
reply from them. In all three cases vim is the editor of choice.
I usually don't do much surfing but every now and then I like to check things out, such as in the case of the "Features" page of MBSE. Good information is always a plus.
Sounds like a plan. :-)
If you're ever interested, MBSE does allow SSH connections,
you can use SSH to check on things this side of the pond
though MBSE is set up to use joe for its external editor.
Right now we are focusing on fixing major bugs
I am trying to teach myself C through this process.
Would you like me to test that?
Errrr ... I am on the same side of the pond as you. We just have a continent between us.
Not a problem. I've used joe before. However if it were me who
decided the internal editor I would have gone with nano. Overall I
think nano is probably the easiest one for users to learn, and it can properly wordwrap for assorted display sizes. Also, also it can do
utf8 but I think joe might be able to do that as well. It has been
awhile since I've used joe.
Create an account
Quoting Maurice Kinal to Nancy Backus on 07-Apr-2019 00:25 <=-
Interestingly, in this packet I got this message twice... the
first time with the 2025 date in the header (see the quote header
above), and the second time with the actual date of 31Mar2019.
Interesting. I am still waiting for it to arrive at the Brain along
wirh a couple other test netmails, with or without 'actual' dates, whatever that really means. The so-called 'actual' date of that
message was 2525 and the 2025 was the product of the two digit year
that the FTSC is so fond of. Also noticed I am missing a couple other messages that have nothing to do with me ... or you for that matter.
(just a little late with working through the packets, as often
the case)
Me too but in my case I delayed replying to this message in case the original showed up as well as tweaking what is now the official
platform for messages following a specific path. Looks like I found a
job for the raspberry pi thingy.
I think your experiment might have messed up the message base
In fact there are 272 characters up to this character ->.
I can confirm that as I am looking at it from the pkt I recieved from this
path; "PATH: 280/464 154/10", which is the entire reason for CanadARM's existance.
Speaking of firsts, you weren't first. The first point here was either/or/both points off Janis and/or Carol back around the turn of the century, maybe sooner. When both were running the project was called "Das Both" but then the US Navy torpedoed one of them. :::sigh:::
I started feeding my first point node in 1989.
Quoting Maurice Kinal to Nancy Backus on 11-Apr-2019 04:05 <=-
I think your experiment might have messed up the message base
If that is true I will take the rap for it. Just to be on the safe
side I won't do it again, not that I was planning to.
i was being facetious
Stop it or you'll go blind.
usedin fido's heyday were professional programmers
Which is what led me to suspect there was once an editor that actually
0x8d and if so it would be docuamented somewhere. No such luck.
0x8d 0x00ec #LATIN SMALL LETTER I WITH GRAVE
That was it. You'd see that on every line of a message if you used Telegard's internal editor if softCRs were enabled.
maybe wordstar or similar from back in the CPM days...
Maurice Kinal wrote to Sean Dennis <=-
Will do except from this angle it looks like you're using golded. ;-)
Maurice Kinal wrote to mark lewis <=-
Looking forward to seeing more of that. I checked out https://www.mbse.eu/bbsing/mbsebbs/features/ and all the good stuff is there ... and then some.
I do that when I want to send out quick messages instead of
telneting into the system itself.
Andrew and I have set up mbsebbs.org though not much is there at
the moment.
One thing that we are planning on is setting up QWK networking
in MBSE and a QWK<->FTN gate system also.
Sysop: | Ruben Figueroa |
---|---|
Location: | Mesquite, Tx |
Users: | 3 |
Nodes: | 4 (0 / 4) |
Uptime: | 97:00:35 |
Calls: | 79 |
Files: | 53 |
Messages: | 73,865 |