I worked for Columbia/HCA, now HealthCare of America, at the time and we started gearing up for Y2K in January, 1997.
Every system, every piece of hardware - both in the data centers and in the hospitals - had to be certified Y2K compliant in enough time to correct the issue. As I recall, we were trying to target being Y2K ready on January 1, 1999 but that date slipped.
A "Mission Control" was created at the Data Center and it was going to be activated on December 15, 1999, running 24 hours a day until all issues were resolved. Every IT staff member was going to rotate through Mission Control and every staffer was going to have to serve some third shifts too.
I left Columbia/HCA in June, 1999 after they wanted to move me into COBOL. I had no desire to do so and I took a programming position with the Tennessee Department of Transportation.
I remember my first day on the job when I asked my boss what our Y2K policy was. He shrugged and said "If it breaks, we'll fix it when we get back from New Year's".
I'd like to report as of June 21st at 4pm CDT, the site now works beautifully in my Linux Mint/Firefox system. I've made no changes other than a Firefox update was automatically installed so whatever you did - THANKS!
INIT: Loading index.js index.js:193:65
The resource at “https://www.google-analytics.com/analytics.js” was blocked because content blocking is enabled. 11
INIT: onYouTubeIframeAPIReady():creating player object index.js:193:65
$(this).data... help_overlay_manager.js:9:234
Object { helpOverlayManager: {…}, forceRight: true, forceBottom: true, overlayTarget: ".app", jsClass: "HelpOverlayManager" }
help_overlay_manager.js:9:265
INIT: jQuery(function ($) index.js:193:65
INIT: splash image loaded index.js:193:65
Failed to execute ‘postMessage’ on ‘DOMWindow’: The target origin provided (‘https://www.youtube.xn--com-to0a) does not match the recipient window’s origin (‘https://apolloinrealtime.xn--org-to0a). 11
processPaperData(): done ajax.js:43:9
Failed to execute ‘postMessage’ on ‘DOMWindow’: The target origin provided (‘https://www.youtube.xn--com-to0a) does not match the recipient window’s origin (‘https://apolloinrealtime.xn--org-to0a). 11
APPREADY: Ajax loaded: 1 index.js:193:65
whatever index.js:193:65
INIT: onYouTubeIframeAPIReady():creating player object index.js:193:65
setApplicationReadyPoller(): Checking if App Ready index.js:193:65
APPREADY: populatePhotoGallery(): 2 index.js:193:65
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://googleads.g.doubleclick.net/pagead/id. (Reason: CORS request did not succeed).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxK..... (Reason: CORS request did not succeed).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://fonts.gstatic.com/s/roboto/v18/KFOlCnqEu92Fr1MmEU9fB.... (Reason: CORS request did not succeed).
Loading failed for the <script> with source “https://www.google.com/js/bg/vVB4qXRsC37Dg1P6FS82ZMhKPNReNJh.... KfRygQcR5uk:1:1
The resource at “https://static.doubleclick.net/instream/ad_status.js” was blocked because content blocking is enabled. 11
setApplicationReadyPoller(): Checking if App Ready index.js:193:65
APPREADY: onPlayerReady: 3 index.js:193:65
APPREADY: onPlayerReady: 4 index.js:193:65
setApplicationReadyPoller(): Checking if App Ready index.js:193:65
APPREADY = 4! App Ready! index.js:193:65
window resize index.js:204:108
TypeError: paper.view is null navigator.js:7:37
window resize index.js:204:108
TypeError: paper.view is null navigator.js:7:37
window resize index.js:204:108
TypeError: paper.view is null navigator.js:7:37
window resize index.js:204:108
TypeError: paper.view is null navigator.js:7:37
I'm running Firefox 67.0.2 on Linux Mint 19 (fully patched) and the site does not work. It sit waiting for the interface to fully load and the Youtube video pane shows the "three dots" image when Youtube cannot reach the audio. Nothing else loads but I do see the individual audio channel links - none work.
I did try your Apollo17.org site and it works beautifully in the same Firefox browser. And if I run Google Chrome, your Apollo 11 site works perfectly. Just not in Firefox.
I am running similar extensions in both browsers and I did disable Ublock Origin in Firefox but that had no effect. Apollo17.org in Firefox works fine with Ublock Origin enabled and I also run Ublock Origin in Chrome.
I'm willing to help out with debugging if you like.
Every system, every piece of hardware - both in the data centers and in the hospitals - had to be certified Y2K compliant in enough time to correct the issue. As I recall, we were trying to target being Y2K ready on January 1, 1999 but that date slipped.
A "Mission Control" was created at the Data Center and it was going to be activated on December 15, 1999, running 24 hours a day until all issues were resolved. Every IT staff member was going to rotate through Mission Control and every staffer was going to have to serve some third shifts too.
I left Columbia/HCA in June, 1999 after they wanted to move me into COBOL. I had no desire to do so and I took a programming position with the Tennessee Department of Transportation.
I remember my first day on the job when I asked my boss what our Y2K policy was. He shrugged and said "If it breaks, we'll fix it when we get back from New Year's".
What a difference!!!