<img class="fas fa-book"></img> "After Authenticity"
<img class="fas fa-book"></img> "IndieAuth for WordPress"
<img class="fas fa-book"></img> "Going From Reading To Notes"
<img class="fas fa-book"></img> "Different Kinds of Ties Between Notes"
2018-04-11
Digging into how withknown creates RSS feeds, I can see two things.
One is that for a status post, which has no title, `<title>` is a truncated version of the post content, although the level of truncation seems to vary. Not sure why.
The other is that even status posts, with a truncated `<title>`, have a full `<description>` that includes `p-name` and `e-content` and even `entry-content`.
But micro.blog does not seem to read `<description>` at least not when it is coming from my withknown RSS feed.
Puzzling.
Is there, anywhere, a definitive guide to ...
Is there, anywhere, a definitive guide to how micro.blog truncates posts it receives via RSS?
Strange question, I know, but ... Is ...
Strange question, I know, but ... Is there any way I can restrict access to a post in WP without having to make people jump through **any** hoops to see it?
There are lots of solutions that allow only registered users to see a specific post. What I want ideally is a link I can give people that will work for them and not for anyone else. A page hidden from anyone who does not have that link.
The idea is to give email subscribers and other supporters access either exclusively or well in advance of the general public.
Just read a horrible coinage: autonomobile. Cars ...
Just read a horrible coinage: autonomobile. Cars were never automobile without a driver. We are still waiting for a truly automobile means of transport.
Maybe next time.
