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.”
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
Mike Hoye, writing on Mastodon:
People go to Stack Overflow because the docs and error messages are garbage. TLDR exists because the docs and error messages are garbage. People ask ChatGPT for help because the docs and error messages are garbage. We are going to lose a generation of competence and turn programming into call-and-response glyph-engine supplicancy because we let a personality cult that formed around the PDP-11 in the 1970s convince us that it was pure and good that docs and error messages are garbage.
Mike takes a look at what can go wrong when writing a one-line “Hello World” program in C. It’s dark — an example of the violence that developers inflict on one other.
It’s not just error messages and documentation. Today’s tools and frameworks overflow with violence; violence is so omnipresent that we’re inured to it, typically choosing to cast blame anywhere but where we should. All developers suffer for it; new developers suffer disproportionately more.