Wednesday, July 11, 2018
Breakfast at home with Patrick: two eggs scrambled, hash browns with green onions, brioche toast with butter, chocolate mint tea. Walked and rode Muni to UCSF Laurel Heights. Gave Julia M an update on the QBC hero work. Orgchart work: OSACA, OEIS. Announced the availability of tabbed interfaces to five of our web editors. UFD email list work: alumni and donors import. UCSF shuttle from Laurel Heights to Mt. Zion. Walked to lunch at The Grove on Fillmore: veggie chili with sour cream and shredded cheese, water: $10 after a small tip. The chili was spicier than I had hoped, but I was able to tolerate it. Afterwards I bought some spices at Spice Ace. UCSF shuttle from Mt. Zion to Laurel Heights. UFD work: web futzing with Joe's image at the top, html email build. Walked and rode Muni home. Dinner at home with Patrick: Good Eggs vietnamese-style noodle salad with tofu and herbs, Just Green green tea. Dessert: one small scoop of Smitten peaches and bourbon ice cream in a cloud of whipped cream from a can. After dinner we watched Ant-Man and the Wasp easter eggs on YouTube. I also resolved a problem with the YouTube app on our Roku television being extremely slow by removing power from the television, waiting 15 seconds, then restoring power and restarting. Recharge Medical web work: remove a job posting. I notice today that Bluehost probably appears to be implementing Let's Encrypt. First I noticed that .well-known/acme-challenge appeared in the root of one of my sites. Then after searching Google and discovering that this is related to Let's Encrypt I tried visiting my same site but with https instead of http, and it worked as expected. I find in their documentation that Bluehost calls their feature "AutoSSL"—auto because the SSL certs automatically renew, presumably every 90 days. After about 30 minutes in online chat with Bluehost Support I confirm that AutoSSL is enabled for all my add-on domains in addition to my primary domain, AutoSSL rollout began in June 2018, AutoSSL rollout is continuing now, and they do not know when the rollout will be complete. So far I'm pretty impressed with their implementation. I only wish I had had advance notice that this was coming. For the past several months I had been thinking that I needed to change web hosting providers. If I had completed a webhost migration last week, I'd be pretty pissed. On my end AutoSSL is enabled for everything and I only need to force https and then resolve mixed content issues. This should be pretty easy, but I'll leave this for another day. When the Bluehost Support chat ended, I expected to be able to email myself a copy of the chat transcript, but that feature was not offered and I lost all the details that I had hoped to have been able to keep. Also, although the support person seemed knowledgeable, the chat took twice as long as I had expected. Good answers will come, but you have to be more patient than you think. Upon rating, they asked two questions, neither of which was related to service speed. To bed late.