One of the many great things about the Indieweb is that I can use my domain URL to log into and use different services. But now changing from http:
to https:
those services see that as a new URL.
Disabling the redirect in the .htaccess
file only works for the root. Once I try to authenticate with the WordPress element we’re right back to using the secure URL.
Most of this problem is of my own creation. I don’t run WordPress for my whole site. Only the /blog
part is WP as I wanted to retain a POSH homepage and be able to play around on the non-blog parts.
This means the URL I have to use is https://davidjohnmead.com/blog
. Not great as most things are geared around the root.
I think I’m just going to have to discard my old URL login and start anew with the secure one.
I see it fairly often. Is there any API in p3k to make these stories available in readers? Maybe we could build something interconnected, so every person’s story was available in an IndieWeb reader!
I think @indiewebcat needs to make @aaronpk to post more photos, since #cats are cute. #🐈
Okay, #damagereport!
The bug was, in essence, a hardcoded date for posts in the Micropub instance. It could’ve respected the date of sending if it was present, but it wasn’t.
That’s why it got the date from now_iso()
function, but the call was performed on launch instead of on post creation. It overwrote the same document over and over…
Thankfully, all my posts are saved in Git, so I’ve easily recovered my stuff. The feed now is in proper order.
Here’s the talk I gave recently about indie web building blocks.
There’s fifteen minutes of Q&A starting around the 35 minute mark. People asked some great questions!