IndieWeb post types
This content type is full of IndieWeb post types, which are all content types which allow me to take greater ownership of my own data. These are likely unrelated to my blog posts. You can find a better breakdown by actual post kind below:
I have this happen to me a lot when I'm trying to get to bed, it's so annoying 🙄
So my angle on this is to have a client that is completely auto-populating. It's not necessarily something that will be useful for everyone, I admit (and is a slightly different interaction model than we usually use).
But I think it'd be quite nice to be able to point a Micropub client to a Micropub server, and have it render an editor for all the given post-types, with all the given properties, instead of needing to build the client with some awareness of what is required.
I feel personally attacked by this tweet. I don't know how I'm going to continue to grow my wardrobe in a post-COVID world
https://twitter.com/ParissAthena/status/1281958370598178818
My fiancé’s entire wardrobe is all tech “swag” that you get from conferences and joining new communities lol
Pariss Athena⚡️Black Tech Pipeline Founder (@ParissAthena)Sat, 11 Jul 2020 14:27 UTC
I'm not sure if this was an issue on my side, or on Bridgy's, but when I tried to publish a reply to a GitHub issue, the syndicated comment originally had a >
, not a >
indicating a blockquote, which meant I needed to manually edit the comment on GitHub to make it render nicer.
Isn't this covered under the following section URL Canonicalization?
As such, if a URL with no path component is ever encountered, it MUST be treated as if it had the path /.
I will be attending ONLINE: Homebrew Website Club: Nottingham on
I will be attending ONLINE: Homebrew Website Club: Nottingham on
I will be attending ONLINE: Homebrew Website Club: Nottingham on
I will be attending ONLINE: Homebrew Website Club: Nottingham on
I've not looked at how many other Micropub servers operate, but isn't it quite common to have certain fields as required? I.e. I'm writing this comment on Micropublish and it requires in-reply-to
and content
for a reply type.