Watched 1946: The Mistranslation That Shifted Culture, a documentary about how the word “homosexual” didn’t appear in the Bible until 1946. It was really good, as expected. I hope when it gets wider release it will encourage more Christians to re-evaluate how we treat LGBTQ people.
“In the teachings of Jesus, he never made any qualifications about ‘God loves you if...’ Nothing is ever mentioned about sexual orientation. And God doesn’t ask. That part is just irrelevant. We’re people. We’re children of God.”
—
Kathy Baldock plays a big part in this documentary. For a deeper dive, I recommend her 2-part video, “Unclobbering the Tangled Mess.”
Reducing Native Comment Spam
I made some improvements to native comments on my site today. I have had Akismet running for several years now and it’s worked well at preventing about 98% of spam comments. A few would still get through each week. They were never displayed publicly, but I would still need to go through the moderation queue to delete them.
About six months ago I decided to start reporting those false negatives to Akismet since their API supports that. I hoped it would help improve their algorithm and fewer spam comments would slip through. I haven’t kept any stats, but it doesn’t feel like the number slipping through has decreased, unfortunately.
I noticed a good portion of these spam comments were to old URLs, like this one from 2011 about fixing a commenting issue. (Ironic?) I figured closing the comment form after one year would be a good way to reduce a lot of spam. I doubt many humans intend to leave a comment on that post here in 2024. There may be some rare cases where an actual human wants to comment on an older post, so I decided to still allow comments if you are signed in. Last year, I introduced a passwordless sign-in system, so I was able to use that as-is and display a message directing people there.
Old posts will still accept Webmentions, of course. There is always the contact page, too. Here is the message that is displayed on old posts when you’re not signed in:
This is an older post, so the public comment form is now closed. You can still use the form above to send me the link of your reply or sign in with your email to leave a comment. You can always send me a message, too.
Looking forward to reading/hearing this one! She's one of my favorites.
Do you play any cool action music when you run the montage command?
It might be too late for this one, but it might be worth pressuring them to do better in the future, a la publichealthpledge.com @phpledge@floss.social
Happy Christmas from the beach! I made the difficult, last-minute decision not to travel this holiday due to the high COVID transmission levels currently (see pmc19.com/data). Decided to make the best of the day with some beach time, though!
1. My mug at the beach 😎
2. I met a guy who had set up this rainbow-colored Christmas tree. He said it had sort of become a tradition since the pandemic. Love it!
3. Others enjoying the lovely day
4. After walking for a while, I sat down to write and read some. This seagull pal (seapal?) chilled about 10 feet from me for a while.
I know this is a difficult time for a lot of people. I hope you got to experience some moments of joy today, though. 💛
A good article with a lot of resources linked: The Pandemic Isn’t Over: The rich know it. You should, too.
“Without accurate data on current cases, transmission rates, hospitalizations, and deaths, we have no way of knowing the full scope of the current crisis. Our house is on fire; alarms removed, the public sleeps.”
@elijah.neumann Vaccines are an important layer of protection. They’re good at reducing hospitalization and death, but not as good at preventing transmission. Their efficacy wanes after several months, too. Even if they were better at preventing transmission, only 18% of US adults are up to date on the vaccine. Respirators are another important layer of protection and are effective at reducing transmission.
I’d like to encourage you to reflect on your last sentence. Disabled and immunocompromised people deserve to share in moments of joy like anyone else, without risking their health further. I believe we should take steps to make events like this accessible and wearing masks is a simple step towards that.
Time has been flying and I hadn’t really listened to Christmas music yet. Starting out with the obvious choice, A Charlie Brown Christmas. I’m still not really in the holiday spirit, but it’s cozy music.
So, in my interpretation, @gRegorLove is issuing a token to my user...wpdev.gwg.us, but in his, he's issuing a token to his user that I'm allowed to use. I'm assuming his conception is based on his being the owner of the resource.
In my interpretation, when I grant a token to a client like indiebookclub, I’m issuing the token to that client and the token has my information in it. Similarly, with Ticketing, I’m granting a token to an individual site and the token has my information in it. In both cases the token is used to access something on my site.
I’m open to do this differently, but currently I don’t understand why it would be different. The issuer, subject, and resource seem to communicate all the information about who the token is for and how to use it.
A highlight from IndieWebCamp San Diego:
Them: “you can scroll if you want to”
Me: “you can leave your friends behind”
Some more context: this is specifically for Ticketing. I’m testing from staging.gregorlove.com and sending tickets to wpdev.gwg.us.
In my mind, sending a ticket to someone is analogous to an IndieAuth Client redeeming an authorization_code — both an authorization_code and a ticket are redeemed for an access token. As a result, my implementation for generating the access token hasn’t changed for the Ticketing flow so far. My access token response includes a me property of staging.gregorlove.com.
David’s implementation is apparently expecting that me property to be wpdev.gwg.us so he can identify which user the token can be used on behalf of (thinking specifically of multi-user environments like WordPress).
It feels odd to me to return someone else’s URL in the me property. It seems like the initial subject sent with the ticket should be verified by the recipient and used to determine the user on the site before redeeming the ticket. If a valid user isn’t identified, it should return an error instead of trying to redeem the ticket.
I think the main use for the me property in the Ticketing flow, so far, is as a reminder which site the access token can be used for. It might be displayed in an admin interface, for example.
@jayliflani Live indeed! That’s literally why I’m suggesting it. Wearing a mask is an incredibly simple way to protect each other from a virus that is disabling and killing so many people. We can share in moments of joy together and keep each other safe at the same time. 💛
We're heading into another big COVID surge this winter so I hope you'll consider requiring masks for an accessible event 💛
Overheard in San Diego: “I’m reasonably sure my nephew isn’t going to fire a missile at the plane.”
Feeling overwhelmed and like some things are just meaningless, but I got a short little walk in for my stupid mental health. The sun felt good at least.
Oof, sorry to hear. :/ I've seen some research that the JN.1 variant is showing peak symptoms a few days later in the infection. No idea how/if that interacts with Paxlovid treatment. Rest well!