I realize this first pix is distorted. This is an auto line wrap functionality kicking in because the image was 73 characters wide, and I failed to triple-check this image to ensure it wouldn't bump into any limits. I have accommodations for 73 character wide pix, just didn't catch this one. Many apologies for the brokenness. I am re-checking all remaining pix to catch this from recurring, and I might try to re-transmit this in a bit if there is enough time.
The stream has started. First test message and pix runs at 3:00 PM MST (about 30 minutes from now), additional pix every hour on the hour for the following 11 hours, and then the tracking begins!
-
Jordan Spencer Cunningham
On Wed, Dec 20, 2023, at 10:12 PM, Jordan Spencer Cunningham wrote:
It's time of year again for all good little boys and girls to follow Santa's journey around the globe using the pinnacle of technological innovation-- the teleprinter-- to do so.
For the uninitiated, this is an ITTY-like broadcast where reports of where Santa was sighted and the circumstances of that sighting are broadcast periodically as the reports are verified. Our eyewitness reports provide a unique, intimate tracking experience particularly enjoyed by kids aged one to 92.
The schedule will be as follows:
- December 23, 3:00 PM MST - A test message followed immediately by a Christmasy RTTY art (some pix will have overstrike) will be broadcast every hour on the hour for this and the following 11 hours, which should give all global time zones some chance to tune in before tracking starts
- December 24, 3:00 AM MST - Based on prior timetables, we expect Santa to begin his journey and the reports of sightings to start coming around this time
- We will track Santa for the following ~24 hours as reports of his whereabouts and descriptions of what he's doing keep coming in, with these brief messages likely rolling in roughly every 10 - 20 minutes dependent upon how the sightings go this year. You may consider keeping a good ol' fashioned globe or atlas handy to follow along.
Not to get into the weeds, but I have attempted supporting USOS (unshift on space) for the past couple of years, and while I thought it was working last year it ended up not, I am unable again to support it this year due to a bug I found in the implementation of USOS in the software I use to generate tones (fldigi) for which I can't compensate. Those who have USOS on receive enabled, if you can disable it, that's advisable, though if not, it should only be a minor inconvenience, manifesting mainly in timestamps not printing correctly. I'm considering rewriting the broadcasting scripts to wrap around minimodem instead of fldigi, which should give me total control over aspects like USOS and CRCRLF, among other benefits. A project for next year.
Merry Christmas, 73,
-
Jordan Spencer Cunningham
______________________________________________________________
GreenKeys mailing list