@pratik Okay, then you should remove it from layouts/_default/single.html. That’s a default, more general template that applies to ordinary pages. Your pages won’t show up on the timeline, so having a Conversation on Micro.blog link in that template makes less sense.
Replies
@pratik Hehe, I think we wrote to each other simultaneously. 😊 Moving the snippets as I described above should solve all your problems.
@pratik Yeah, the documentation lags behind here. Sorry about that. The plug-in shows a fallback when things go wrong, taking the visitor to your profile on Micro.blog.
You can change both the URL and text for this fallback link from the settings. Or you can choose to not have a fallback link. In that case, when something goes wrong, there will be no link at all.
So, what can go wrong then? For example, if you, like me, have a self-hosted blog, there can be a delay between a new post being available on my site until it shows up in the timeline on Micro.blog. In that case, my plug-in won’t have anywhere to send the visitor, as there’s no related post on the timeline yet. So the fallback link will be shown instead. Or not, depending on your settings
@pratik I’m glad the plug-in works great, in most cases. 😊 Unfortunately, Conversation on Micro.blog is not designed for listing pages with multiple posts. I might add support in the future, but for now, it will only work in single post scenarios.
Regarding the duplicates: I don’t know what’s going on there. I’ll have to take a look and get back to you.
@maique Thanks! Well, you know, it was a high-risk, high-reward kind of project. 😂 The reward, in this case, was a picture of me looking stupid on ice.
@JohnPhilpin Was that a horrible album with a good making-of documentary? 😅
@ohBananaJoe 😂 I will let my girlfriend know you prefer her shot; that will make her happy.
@renevanbelzen Thanks for letting us follow along on your pixel journey. I hope the art ends up in a game for us to play! 😊
@jemostrom I’ve just piloted tiny quadcopters, but they sure are fun to play with. I look forward to your future videos.
@pimoore Yes, I’ve made the behavior configurable with two new settings. A combination like this mimics the behavior in Tufte:
Something weird is going on with the plug-in’s new version number in the directory (I’ve reported this to @manton), but you should be able to install anyway and test this out.
@pimoore Yeah, I like that idea a lot. In addition to making the feature optional, my plug-in has settings for link text and subject line. And, should I add features or fix bugs in the future, people can get them independently from which theme they are using.
@timapple Well, no ice is 100 % safe, so I think your attitude is very reasonable. 😊 That said, it might look a bit scarier than it actually was. The risk was manageable: the water level is about knee-deep where I’m standing, dry land is 2–3 meters away, I had my girlfriend with me, and neighbors close by.
@amit This is so cool! Nicely ported.
@ChrisHannah Beautiful! I like how it radiates synthwave and vaporware vibes. 😎
@pimoore Wow! 🤩 Great work with the updates for both Tufte and Hitchens. Thanks for adding support for my plug-ins.
@tkoola Could it be this generative art project from 2008 (commissioned by Nokia)?
@help I love that status page. 🥰 But it’s a bit misleading as micro.blog/status is an almost empty page with just an emoji.
On my connection right now (slow fiber at a cabin in Sweden), the emoji page takes around 0.5 seconds to load. www.manton.org, in comparison, at 4.5 MB loads in about 2.3 seconds. This page, hosted elsewhere, weighing in at 8.3 MB, takes 0.8 seconds to load.
Average measurements in Safari Web Inspector with cache disabled. Not too scientific, but at least it gives a hint.
@amit @manton @pimoore I don’t know if it’s easy or not, but I do like the idea. 😊 It’s a common pattern to use files like README.md, CHANGELOG.md, and INSTALL.md and show them in user-facing directories. Nova Extensions is one example, Atom Packages another.
@manton @pimoore Love this! Another thing I’ve noticed for my plug-ins is that people miss there’s documentation available over at GitHub. Which I don’t blame them for. 😊
What if developers could add additional links below the plug-in description? Like “installation instructions”, “documentation”, or “support”. Something like this:
@colinwalker Looks like there are a lot of web3 folks signing that web0 manifesto. 😅
@skoobz Me too, so dumb.
@ohBananaJoe @Gaby Yeah, I think you’re out of luck with Windows. Maybe another human in your vicinity owns an iPhone you could pair the AirPods to until the latest firmware is installed? 😊
@artkavanagh Yeah, maybe that’s what’s happening. Weird that we don’t get any error messages. I think @manton has to get involved here. 😊
@artkavanagh Yeah, there might be something going on there. A full rebuild takes a while and usually ends with a line like this:
2022-01-20 12:59:52: Publish: Done for artkavanagh
@artkavanagh After clicking the rebuild button, do you get any errors in the log below?
@artkavanagh Have you tried forcing a total rebuild? That may get you unstuck. 😊
@rom Woohoo! 🎉 I’m glad it worked out.
@toddgrotenhuis Thanks for your feedback, much appreciated, and you’re totally right. Many plug-ins just add extra metadata or new pages to a blog. My own Surprise me! plug-in is one example. These plug-ins “just work” because they don’t need to change the blog’s templates.
Conversation on Micro.blog and Reply by email are different because modifications to the theme are necessary. I could provide a modified template with the plug-in, but that would overwrite any other customizations already done to that theme. That’s probably not what people want.
I would love to have hints and reminders – like you’re suggesting. And maybe there’s more we can do to make the installation process more manageable. I will give it some more thought. 😊
@matti Thanks, we are talking about the same issue. Feels good to not be alone. 😊
@rom Yeah, I don’t want to put words in @manton’s mouth, but I think we should look at plug-in-based themes as “still in beta”. 😊 Customizing does not work the same as with “classic themes”. Yet.
But it is possible to modify templates in plug-in-based themes. In more than one way, actually. For example, you can go to Design → Edit Custom Themes and click on the theme in question. From there, you can edit any template you want (or create new ones).
Another approach is to create a new plug-in and, from there, create a new template that overrides the template in the original theme plug-in. Finally, a third way is to duplicate the original theme and make your changes there.
They all feel a bit “hacky”, and I hope there will be a more straightforward, official way to customize plug-in-based themes in the future.
@bjhess Hmm, you’re right; there’s a risk for confusion the way it’s written. Thanks, I’ll try to make the instructions more straightforward.
@JohnPhilpin A cool thing, if you decide with Hitchens, is that it comes with built-in support for Conversation on Micro.blog. So you just have to install my plug-in, and the link will magically appear for every post. No custom theming is needed.
PS. @rom, see the other thread for help with plug-in installation.
@rom Wow, thanks for trying out my plug-ins. 🥰 There’s no easy way for plug-in developers to automatically inject links or make other changes, as every theme is unique. I would have to develop and maintain patched templates for every single Micro.blog theme out there.
In theory, theme developers could deliver their themes with built-in support for my plug-ins. And that’s actually a thing now, @pimoore’s Hitchens theme is the first that comes with built-in support for Conversation on Micro.blog.
For other themes, though, an installation step is needed for the links to show up. In the directory, below the plug-in’s description, there’s a link to the documentation on GitHub. Or just follow these links to the documentation for Conversation on Micro.blog and Reply by email.
@bjhess First of all, thanks for checking out my plug-in. 😊 The link won’t appear automatically, unfortunately. Below the plug-in’s description in the directory, there’s a link to the installation instructions. In short, a little code snippet needs to be injected in your template where you want the link to show up. Let me know if the documentation can be approved upon.
@maique Beautiful! 🤩
@Moondeer You could have the RSS file on your blog just output the link instead of the extra markup. That way, it would look better on the Micro.blog timeline and services you choose to cross-post to. But, still, have that cardy look on your blog.
@otaviocc The good news is that Hugo has built-in support for highlighting using shortcodes. Works on all Micro.blog blogs – both current and “next-gen”. 😊
On the latest version of Hugo (activated by going to Design → Hugo version), you will get highlighting for fenced code blocks (using backticks) as well.
@toddgrotenhuis Thank you for trying it out. 🥰
@pimoore That will definitely lower the bar to get started with some of the most popular plug-ins. And the option for a custom theme is still there for the crowd who wants that. Lovely!
@timapple Nice! You could have both. 😊 In that case, you might want to change the wording inside the link to “Reply on Micro.blog” or similar.
@Miraz That’s such a clever one-liner. To everyone following along at home: keep copies of your originals as this is a destructive action.
@pimoore Woohoo! 🚀
@Moondeer Well done! 🎉