Replies
@toddgrotenhuis Yeah, I wish there was an easy way for me to do that automatically, but unfortunately, it’s very impractical. Every theme is unique, so I would have to develop and maintain patched templates for all the Micro.blog themes out there.
But, in theory, theme developers could deliver their themes with built-in support for my plug-in. I’ve actually pitched that idea to @pimoore. So we’ll see what happens. 😊
@pat Thanks, and no, I wouldn’t mind at all; it would be an honor. Thanks for sharing your theme with us.
@toddgrotenhuis Hey, thanks for letting me know. If you just changed from another theme to Hitchen, you have to redo the include the Conversation on Micro.blog link in your custom theme step from my installation instructions once again.
Every theme is different, and it’s up to you where you want to include the Conversation on Micro.blog link. That said, for Hitchen, layouts/partials/article.html is probably where you want to have the {{ partial "conversation-link.html" . }} snippet.
@manton The fix that came with that deployment was worth the hassle, though. Good work! 🎉 🐛
@pimoore It’s a lovely theme, and your port to Micro.blog is so well executed. Fabulous! 🎉
@jemostrom @odd Men vem är mest unik? 🤔
@HemisphericViews Regarding the vital conversation about W at the top of the episode, it’s actually called double-v (dubbel-v) here in Sweden. 👏
@Moondeer I probably lack too much context here, but judging by the comment at the bottom, you’re including stylesheets based on if a shortcode is used or not. Is that right? Could an alternative be to just always have the stylesheet? That way, you could just get rid of the entire if/else block.
@Moondeer Wow, that’s one impressive – and kind of intimidating – piece of code. 😅
@Moondeer I’m glad you found it helpful. 😊
@pratik Micro.blog’s hosting provider has reported networking issues on their side. So that might be why you’re experiencing slow load times.
@pimoore 🤩
@Moondeer It’s doable, and fetching is the easy part. “Parsing” is a bit ugly if it’s not XHTML. Here’s something to get you started:
> {{ with resources.GetRemote “https://example.com” }}
> {{ $meta := findRE “<meta.*?>” .Content }}
> {{ range $meta }}
> {{ . }}<br />
> {{ end }}
> {{ end }}
That will output every meta tag found at the provided URL. Sorry about the messed-up template. 😔
@skoobz Congratulations! 🍻
@jsonbecker Ah, I see. There’s a Wi-Fi trigger, but that might not be granular enough for your use case. Motions sensors are another alternative but at an additional cost. You’re right; Airport presence detection would be cool.
@canion I don’t know about blog-specific search engines, but there’s a handful of alternatives out there.
Have you checked out millionshort.com? Like the name hints at, it lets you filter away the top million websites from your search results. There’s also an option to hide e-commerce websites.
wiby.me is another one with a focus on independent and hobbyist websites.
@jsonbecker Oh, intriguing! What would the Airport have enabled that’s not possible to do without it?
@otaviocc Looks like lean and usable packages. And very readable code, even for a non-Swift developer like me. 😊
@renevanbelzen Oh, that’s living the dream right there. 😍 My favorite BASIC (not assembly) one-liner for the C64 is 10 PRINT CHR$(205.5+RND(1)); : GOTO 10. It’s one of few (the only?) one-liner that has an entire book dedicated to it.
@manton Yay! 🙌 I’ve exposed my plug-ins to the new Hugo version, and everything seems to chug along just fine. Thanks for enabling this.
@canion Yeah, I know! I should write a meal replacement plug-in next.
@canion Thanks for installing; looking good! 🤩 Oh, I would love doing this stuff all the time. It’s just that there’s this thing called food and some obligation for me to put that on a table? 😅 I’ve had some time off around the turn of the year, but now it’s back to doing work for clients again.
@Gaby Thank you for installing. 🥰 Heads up: there’s no support for having the conversation link on list pages (like the archive or home page). At least not yet. So, for now, you have to move the {{ partial "conversation-link.html" . }} snippet from layouts/_default/list.html to layouts/_default/single.html.
@vincent I’m glad you like them. 🙏 The temporary burst of productivity might have coincided with some time off around the holidays. 😉
To see this in action, visit my blog and tap Reply on Micro.blog to get back to the timeline. 😊
@ndreas Verkar funka. 😊
@Gaby Looking good, thanks for giving Surprise Me! a go. 🥰
@manton Woohoo! 🎉
@Moondeer Yeah, I stumbled upon your plug-in; it’s awesome and way more polished than my approach. Mine is mostly a proof of concept. Nevertheless, I thought it worthwhile to experiment with monkey patching the built-in highlight shortcode for two reasons.
First, it works without JavaScript, and second, Hugo template code “just works.” So no jumping through hoops is necessary.
But, with @manton rolling out changes today, my plug-in will probably soon be obsolete.
@matti @moondeer We could monkey patch the built-in highlight shortcode to play better with Micro.blog. As an interim solution until @manton updates Hugo to a newer version. I have a plug-in working with decent results on the default theme.
Feel free to install and play around with Highlight Monkey. 🙈

@canion Your question improved my documentation; there’s a Customize the look and feel section now. Thanks!
@canion Yes, absolutely. The first thing to try is wrapping the partial call inside a paragraph (p element). In this way:
> <p>{{ partial “reply-by-email.html” . }}</p>
That should result in the same amount of breathing space text paragraphs have between them. If that’s not enough, there’s also CSS for flexible styling. But give the above a try first, and let me know how it goes.
@ChrisHannah This resonates with me. I adore keeping a mix of new and seasoned technology around. My favorite version of Tetris is for Game Boy, so I will try keeping that old gray brick healthy until the end of time.
I also enjoy repurposing old gadgets. I have an old e-reader that I should breathe new life into. Put a good-looking frame around the e-ink screen and hack the device to show something useful. Maybe the current electricity price? That way, I can tell if it’s a good time or not to do laundry. 😅
My favorite old product, though, is a mechanical clock that once belonged to my grandpa. It ticks along tirelessly and has done so for the last 60 years.
My Game Boy turned 32 last year. I hope it’s still alive and well in 2049.

@manton Nice! A footer is an excellent place for a surprise. 😊 I clicked and just learned that you got rid of some HTML tables and implemented your design with hack-free CSS back in 2006. Good work, past Manton! 💪
@JohnPhilpin Oh, thank you for checking out! 😊
@manton Thanks! It definitely makes sharing plug-in easier.
@JohnPhilpin Congrats to 1,496 days on Micro.blog! 🥳
@jemostrom Tasty! 😋
Thanks, everyone, for checking it out. 🥰 @ericmwalk @canion @lmika @svenseebeck @crossingthethreshold
@JohnPhilpin You can at least figure out how long you’ve paid for Micro.blog at Account → View Subscriptions. If you, like me, tend to keep old emails around, you might be able to search for “Welcome to Micro.blog” and find out your registration date that way.
@pimoore Hmm, I tested with Tufte during development, and john.philpin.com/surprise-… looks okay. Can you tell me in which way it’s not working for you, @JohnPhilpin? Do you see any errors?
@g 🥰 Tack för att du testar. Såg att du redan hunnit installera på din blogg, och det verkar ju funka hur bra som helst.
Want to see it in action? Follow this link, and you should end up on a random blog post of mine: Oh! the suspense. 🎲
@manton Oh, that makes me happy. 😊 Poke me if you find something weird or buggy.
@maique Thank you for testing. Let me know if you find some pesky bugs. 🐛