Replies

@Miraz

  • where are you? On the couch, Jönköping, Sweden
  • date? 27 January 2022
  • sunrise? 08:16
  • sunset? 16:17
  • day length? 8 hours 1 minute

@odd Oh, I’m glad you’re having fun with it. 😊 Let me know if that weird behavior comes back.

@odd Hei! Thanks for checking out my plug-in. 🥰 I used my browser (and curl from the terminal) and successfully fetched both /surprise-me and /surprise-me/ on your domain. I tried my best to recreate this on my test blog without success.

Could there have been a temporary glitch?

@vincent 😮 Are peeled/scraped keys a thing now? The left command key on my previous MacBook Air looked exactly like yours. I’ve never had that problem before.

@val Hey, thanks, what an honor to be compared with Jonna. I wish I had half her talent when it comes to ice photography. 😊

I’m more of a summer person, but I envy the kind of winters she gets up there. Living way more in the southern parts of Sweden, I have to settle for the small amount of snow and frozen lakes we get.

@pratik Yeah, support for old posts is already in the plug-in. As long as you link to an older post that actually has an entry on the Micro.blog timeline, the link should show up and take the visitor to the timeline when clicked.

@pratik No, it’s just a design decision I made during development, for two reasons. First, it was quicker to implement. 😊 Quicker is always better for me when working for free. Less time spent on free labor means I can spend more time doing paid labor, more food on the table, etc.

Second, I want to discourage people from putting the link on archive pages as that will unnecessarily load the Micro.blog servers. Every link needs a request to find out the conversation URL. A list page with 10 posts will make 10 requests to the servers.

I have an idea how to implement this in another way, to get support for having links to conversations on list pages. I might get around to that in the future.

@pratik Yes, Reply by email will work, but unfortunately not Conversation on Micro.blog. Those links will just take the visitor to your profile on Micro.blog (not the actual conversation).

@pratik I’m neither a user nor the designer of the theme you’re using, so I’m afraid I don’t know all the differences. But a quick glance at your blog hints at posts having a prominent date at the top, compared to ordinary pages like About.

In your case, index.html is the template for the homepage. There’s a particular lookup order when it comes to templates in Hugo. So, if you should happen to remove index.html, _default/list.html would take its place and be used for the homepage instead.

@pratik Is none of them showing? If so, that’s something for @manton to look into. Otherwise, it might be that I answered @amit‘s post in one case, mentioning you. Maybe that kind of reply won’t show up in Mentions?

@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.

@pratik Hehe, I think we wrote to each other simultaneously. 😊 Moving the snippets as I described above should solve all your problems.

@pratik Yepp, @amit is totally correct. Moving the code snippets for the plug-ins to layouts/post/single.html will probably work a lot better. 😊

@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.

@ohBananaJoe 😂 I will let my girlfriend know you prefer her shot; that will make her happy.

@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:

Screenshot of two checkboxes. Show title in subject line is checked. Show body in subject line is not checked.

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.

@maique @muan I enjoy washing by hand from time to time as well. I do love the machine, though. The thing is, here in Sweden, the electricity market is insane right now. So I have to start the washing program in the middle of the night to get decent rates. 😅

Chart showing price changes for electricity over 24 hours. It’s high for most of the day, cheaper at night. The average being 153 öre.

@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.

@pimoore Wow! 🤩 Great work with the updates for both Tufte and Hitchens. Thanks for adding support for my plug-ins.

@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.

@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:

Screenshot of plug-in card with additional links: Source Code and User Guide.

@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, 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

@pat Oh, I’m so happy my mention lead to the discovery of @pimoore’s port. 😊 I very much look forward to the compilation of mods. Thanks again for creating Hitchens and sharing it with everyone as free software.

@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. 😊

@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.

Sitemap for dahlstrand.net