Testing to make sure I’ll be able to use the micro.blog tools when they start supporting posting to blogs. I can post here using Quill, so micropub is working, but running the test suit at micropub.rocks produces only failures.
I’ve been using micro.blog right along and have a good, basic understanding of what it can do, but I’m very much looking forward to the release of the book, which I expect to fill in any number of gaps.
This post exists purely for the purpose of unlocking the Halloween pin on micro.blog. I apologize for the bandwidth consumed. Oh, and here’s a picture of our Halloween weather:
This is a test to see if emojis show up in post titles and post content. (Emoji functionality seems quite flaky in comments.)
Some emojis: 🌸💃🧚♀️🧜♀️🌸
(Interesting. They’re there, at least in the preview, but they’re from a different character set than what I see when I paste an emoji from elsewhere. Here’s two I’m typing: 🦔❤️. Yeah: Again not what I see when I pick an emoji via the native special character typing on the Mac; the native Mac hedgehog is facing left rather than forward, and the heart has some fancy tonal shading.)
Here’s a great summary of all the things I never quit using: a personal website, #RSS, blogroll, etc. Now augmented with indieweb stuff like webmention, micro.blog, etc.
I mentioned a few days ago that I’d got my microblogging working about the way I wanted. There was one exception to that: my “images” workflow.
There’s pretty good “media library” functionality built into WordPress, but I’ve always found it a bit too blog-centric in how it works to be a good general solution to images hosting.
Lychee works great, but it took me a while to sort out how to integrate images hosted there into my blog.
Here’s what I’ve ended up doing:
- Upload images to images.philipbrewer.net. The Lychee software lets me keep them private or make them public, and it lets me organize them into albums. It also produces an RSS feed of all my public photos.
- If I want to use one of my photos in a blog post, I select the photo in Lychee, click on the share button, and select “direct link” to get a link to a .jpg file. The default is the full-size image, but I can edit the link to get a link to a medium or small image if I prefer.
- In my blog post I insert the image as usual, except instead of selecting the image from my media library, I click “Insert from URL” and paste in the link I acquired in step two. If it’s the main image for the post I also paste it into the “use this image” field in Open Graph (a WordPress plugin I use to generate the metadata so that links shared in Twitter and Facebook use the image I want). If I want to, I can also specify the Lychee page for that image as the target URL if you click on the image.
Here, for example, is an image I took yesterday:
Pretty much everything works the way I want it to now. The images are hosted on images.philipbrewer.net, I have access to small, medium, and large versions of the images, and an easy-enough way to include them in a blog post.
Two things that could work better:
- A one-click way to get the link for the images pasted into all the right places in a new blog post, so I’m not having to go back and forth to make the image block, get one link, paste it (usually twice), then get the second link, and paste that one.
- A one-click way to get a srcset, so that my pages can be more automatically made responsive.
Still, after a bunch of posts where I was testing things out, in which things didn’t work quite they way I wanted them to, I’ve now got things just about set.
Often—I’d say usually—when I craft something to post to social media I end up disappointed eventually. In particular, when I want to refer back to it and find that it’s lost in the depths of Facebook or twitter and I can’t find it, or can’t refer to it in the way I want to.
I think I’ve got this problem solved now, via micro.blog, which is social media done correctly.
Use micro.blog like this: Have your own blog that generates an RSS feed. Sign up for a micro.blog, and configure it to watch that feed. It will build a twitter-like timeline out of your blog posts. There’s a clever detail about how it does so: Your regular posts will just be posted with your post title and a link. But your short, status posts—your tweet-like posts—show up with the full content instead of just a title and a link. (You signal the difference to micro.blog by omitting a title on your status posts.)
I set up a micro.blog a couple of years ago (I was a backer on Kickstarter), and was very pleased with how it all worked, with the sole problem being that nobody reads my micro.blog feed. My frustration with that, however, has finally prompted me to do something that I’m always loath to do: Spend money.
I signed up to spend $2 a month to have micro.blog forward my feed on to twitter (and, of course, to support micro.blog). A link to this post will show up with the post title. My status posts are showing up as tweets, just like they’re supposed to.
Going forward I’ll still post to twitter, but generally just replies and retweets. With those exceptions, my plan is to publish all my content here and let micro.blog handle the rest.
Tiny little leafhopper on my thumb.