Microblog

Added Hugo version 0.117 as an option on the Design page for your blog.

I've been seeing differences between my current home setup and what's on Micro.blog and always attributed it to some difference in my environment and what is on the server. Some kind of secret sauce.

Unfortunately, it looks like something changed in the way that Hugo (or maybe goldmark) handles code blocks.

I’ve got it running on my test blog and have a post that I can refer to so that I can tweak the CSS to go with this newer version.

Table and Gist

Still, I’m excited because this release has a lot of cool things since the v.91 that I’ve been targeting. Such as…

92 Removes depreciated .Page methods

93
Markdown diagrams and code block render hooks

94
20% reduction in build time and memory usage

99
Error handling release

101
Gif image processing

103
Updates to 404 support

104
$image.Colors

107
Update to code highlighting

108
Change to the render hook so that you can have it make it so that stand alone images are placed in a

tag. When I look at my blog, I see that you have something there to handle this behavior.

You can checkout the release notes here: github.com/gohugoio/…

I’m self aware enough to know that some of what drives me to write on this blog is to communicate and share my thoughts and feelings on various things. Some would call it a little narcissistic.

That being said, I do come across things that I would like to share. For instance, I came across a post by my friend Adam on Mastodon and I want to put it on my blog. I sometimes wouldn’t know how I should go about doing that. Should I just put the link into Micro.blog? Apple Notes? What about a third party application?

I took a step back and remembered that I had put sometime into saving bookmarks into drafts¹.

I took a fair amount of time reading over the IndieWeb during the creation of the labarum theme but I’m still having trouble getting it absolutely “correct” because some of the examples that they point to for replies, likes, and articles are returning 404 pages.

Still, I’m pretty confident in the site as it stands and will continue to use the Microformats Parser as part of the process.

My current Web Capture Template will be the following until I get some time to rethink things.

# [[title]]

<blockquote>
[[selection_html]]

<footer>
<cite>
    <a class="u-in-reply-to" rel="in-reply-to" href="[[url]]">
        [[title]]
    </a>
</cite>
</footer>

</blockquote>

<p class="p-summary">Begin response here</p>

I’m planning on making it so that I can select some text and get the draft ready to send to my blog. Otherwise, I’d just send the link directly to someone² who is interested it.

I think the second hardest part was getting it to stop making the smart quotes.

We solved the “how” but now “what”

This will be an ongoing question. Everyone’s blog is a personal platform and when we put something on it, we are broadcasting a little bit of who we are.

With the recent turmoil of what used to be twitter and reddit, I feel that user created content needs more avenues for discovery.

People used to call it the social graph.

As my site is a node in the social graph, I’m going to post more stuff that interests me.

Sure, you are going to see repeats from other places, but that’s ok.

I was experimenting with webmentions a lot today. Still have a couple questions, but I think I’m done for the time being.

Webmention is one of the fundamental indieweb building blocks. It enables rich interactions between websites, like posting a comment or favorite on one site from another site.

I hope this works.

This is really the example that everyone links to.

Webmention is one of the fundamental indieweb building blocks. It enables rich interactions between websites, like posting a comment or favorite on one site from another site.

I’m hoping that this all works properly from the clipping to drafts to micro.blog.

I’m spending sometime with iA writer.

It’s definitely a nice interface for writing things.

I just wonder how I’m going to add the descriptions to the images.