Ooh, it is delightful! Starting with the revived era (2005 series 1, Eccleston as the Doctor) is great and where I would usually recommend, but Tennant in series 2 is a huge fan favorite so you could jump in there too.
I really love the whole arc of series 1-4. Hope you enjoy it!
“We are never, ever, ever going swimming together”
This is a really empathetic and encouraging post urging event organizers to improve events with better Health and Safety policies: An event organizer’s duty of care: from Codes of Conduct to Health and Safety policies
Consider sharing it and the corresponding publichealthpledge.com with any events you might attend. Like @josh@josh.tel wrote, “Don’t let anyone convince you we can’t do better. We can, and will.”
I rarely dream in my sleep (or remember them at least) but when I do, of course it’s something absolutely unhinged like I’m hanging off the side of a big boat and my feet hit Taylor Swift as she was swimming in the water. At least I apologized to her.
Bookmarked: longcovidmoonshot.com
WHAT WE WANT:
- Invest in a moonshot for Long Covid – a commitment to invest at least $1B per year over the next 10 years into NIH research funding and clinical trials.
- Back the Long COVID Support Act (S. 2560), TREAT Long COVID Act (HR 3258), and Long COVID RECOVERY NOW Act (HR 1114).
Fix: Adobe Digital Editions Not Recognizing the Nook
This might only help two people out there, but I was one of them, so hey.
I ran into an issue where Adobe Digital Editions (ADE) software was not recognizing my Nook Glowlight 4 ebook reader. I’ve previously transferred several library ebooks using ADE, but this time I started getting the error “Loan token update failed” when I tried to open the book. I searched that error message and found this Overdrive help page.
That page explains how to reset the ADE authorization on the Nook by connecting with USB, deleting the Nook folder .adobe-digital-editions, then trying ADE again. The instructions seem to imply ADE will then automatically find the device and authorize it again. I was nervous so I backed up the folder before deleting it. Unfortunately, ADE stopped seeing the device entirely.
I tried several things including restoring that Nook folder and the two files in it (activation.xml, device.xml), rebooting the Nook, re-authorizing ADE on my computer, etc.
Finally, I was poking around the Nook settings and found it has its own section to enter your Adobe ID and password. I had forgotten about this, but it started to make sense: entering those probably creates the signed files in the .adobe-digital-editions folder. Then ADE uses that to recognize the device since both have the same Adobe ID.
So my recommended steps for the Nook Glowlight 4 would be:
- In ADE, go to Help > Authorization Information. The authorization window should pop up and show what Adobe ID you used to authorize the computer. If the option is grayed out, you’ll need to authorize the computer first.
- On the Nook, go to Settings > My Account > Adobe DRM Settings
- Make sure that the same Adobe ID from ADE is listed under Authorized Adobe IDs. If it isn’t, tap Add Adobe ID and enter the Adobe ID and password.
- Re-open ADE and it should display the Nook in the device list now
If ADE still does not recognize the device or if the Adobe ID already appears in the list in step 3, only then would I recommend trying Overdrive’s instructions to delete the folder (“Reset the ADE folder on your NOOK”). After deleting that folder, try my steps again to add back the Adobe ID.
Again, this is specific to the Nook Glowlight 4, but it might work with other versions. Note that transferring ebooks to the Nook Glowlight Plus has different directions. I don’t have any experience with that device, though.
Currently reading: The Fifth Season by (ISBN 9780316229302)
1. San Diego can have little a fall, as a treat.
2. They took an hour from us but at least I can still enjoy this.
★★★☆☆ Live Wire by
The plot was kind of average and the reveal at the end seemed far-fetched, but overall an enjoyable read. I picked this one up from a neighborhood Little Free Library because I had read one of Coben’s other books and enjoyed it. I didn’t realize it was part of a series, but it worked alright as a standalone read.
Finished reading: Live Wire by (ISBN 9780525952060)
Joe brought CSS Battle to my attention today. I enjoy CSS but most of my daily work with it is routine stuff like forms, nothing too fancy or creative. I decided to try it out and in true indieweb fashion, I wanted to post the results on my site.
The 2023-11-14 Daily Target seemed like a good chance to brush up on CSS Grid. I got my solution down to 342 characters when minified. I must say it hurt a little to remove the quotation marks on HTML attributes. :]
It looks like the daily target switches over at midnight UTC, so I was too late to submit this today. Still a fun exercise and looking forward to more.
Bookmarked: Making “Webmentions” look more conversational
I like this CSS image reset after watching Kevin Powell’s walkthrough.
Also intrigued by the post he linked, “The Ultimate Low-Quality Image Placeholder Technique.”
Not sure that can work directly with the GROUP_BY query, but I tried below with only SUM and IF. It will depend on how the "quantity" of each type works. Below assumes it's quantity=1 for each.
SELECT SUM(IF(advisory_type = 'SECURITY', 1, 0)) AS total_security ,SUM(IF(advisory_type = 'DEPRECATED', 1, 0)) AS total_deprecated FROM example_table WHERE -- conditions GROUP BY -- need to group by something here
I’ve implemented this: my ticket_endpoint will accept a (currently optional) iss parameter. If that’s included, the endpoint will check that the issuer URL advertises indieauth-metadata endpoint and is valid as described in the spec.
I think I like this solution to the privacy concern. It also avoids the overhead of advertising endpoints on multiple resource URLs. So I lean towards requiring the iss when sending a ticket. However, I’m not sure how many implementations might send an issuer URL that does not advertise the metadata endpoint.
I now have the building blocks for Ticketing for IndieAuth set up.
On my staging site, the metadata endpoint now advertises the ticket_endpoint. That endpoint is accepting POST requests with parameters: ticket, resource, and subject. If the request is valid, it will be stored and return HTTP 202 with the message “Accepted.” Tickets are not automatically redeemed yet.
In the IndieAuth module admin, I set up a page to issue a ticket by entering a URL for “Allow access to” (the resource) and “Send ticket to” (the subject). Submitting that form will check the subject URL for an indieauth-metadata endpoint that advertises a ticket_endpoint. If that is found successfully, a ticket is created and sent there.
Finally, I updated the token_endpoint to accept POST requests with grant_type=ticket and exchange the ticket for an access token.
Next I will be working on automatically redeeming received tickets for access tokens and setting up some private posts to work with granted access tokens.
I am currently using the same code that generates authorization codes to make the tickets. I think this should work fine because it already handles creating an opaque string that is valid for a short period of time (5 minutes). The module also ensures these can only be used once and logs key information for each request like client_id (source code). I need to run some tests to ensure tickets can’t be used as authorization codes and I might need to add some metadata to differentiate the two in the admin area.
Feel free to try to send a ticket to my staging site and ping me in IndieWeb dev chat. I can also send you a ticket if you’d like to try that out. I look forward to discussing this with other implementers!
The CDC’s HICPAC has proposed guidance that will weaken infection control in healthcare settings. They have a rather short period for written comments, “…opened November 1, 2023, and will close at 11:59 pm on November 6, 2023.” I presume that is Eastern timezone.
Below is the message I sent, including links to more information. Please take a moment and send an email yourself! hicpac@cdc.gov
Subject: Strengthen infection control guidance
To: CDC’s Healthcare Infection Control Practices Advisory Committee (HICPAC)
hicpac@cdc.gov
I am writing to join my voice with the National Nurses United (NNU), People’s CDC, and thousands of experts in public health — calling on HICPAC to strengthen the guidance on infection control and fully recognize the aerosol transmission of SARS-CoV-2. The proposed updates weaken the guidance and do not adequately follow the current science on transmission. This will put more healthcare workers and patients at risk.
I am also urging more openness and transparency in your processes. You should be seeking input from frontline workers and other experts in respiratory health. Draft guidance should be published along with the scientific evidence well in advance, with an ample time for the public to make written comments.
Thank you,
Gregor Morrill