ttj - Tom Jones

To register a device for wifi on Princess ship, connect to wifi MedallionNet, and point. a browser at login.com. Background:  tardtards decided that wifi connection couldn't be done via wifi protocols, it had to be via a web page.  So were born "captive portal"s.  When web was plain-text, network provider's stack could easily man-in-the-middle user's web requests (assumption: user goes straight to web), and redirect to their captive schmortal page, and make them fill forms. Then the web went mostly-https, (SSL / TLS), meaning encrypted, so MITM shouldn't be possible, and the captive schmortal MITM attempts result in certificate errors.  User may choose "abandon ssl certificates", "do anyway" kind of things in browser.  But the client is now told, I think by a DHCP item, what URL to go to to do the captive schmortal.  This is somehow passed from the client's OS to the client's browser.  Sometimes a new browser window is launched, on ...

Crossing the Pacific westwards, the ship's time gets set back one hour at a time.  The ship's management arranges it so that at land stops, it is synchronised with the location.  Changes between one stop and the next are somewhat arbitrary, but the idea should be to keep changes smooth and have dawn and dusk at sensible wall times. I set around 5 clocks at each change. The Casio F-91W is the easiest.  I set the hour back using the three buttons on the watch.  The only annoyance is that I have to cycle +23 hours, as one can not decrement the hour directly.  It's not that annoying, and one knows it's going to work. For the Debian (Linux) laptop, I change the /etc/localtime symlink to point to location in /usr/share/zoneinfo/*/*, such as /usr/share/zoneinfo/America/Vancouver.  This is fine when there is a well-known city to select.  It sometimes involves research and experimentation to choose one with the correct (current) offset.  Once the symlink c...