@warner Thanks for checking out the plug-in! There’s no plan to turn Magic Preview into a full-blown text editor or Micro.blog client. It’s just a quick way to preview your next blog post and relies on your favorite app for the actual posting.
Regarding the macOS app and the new post window lurking behind the main window, that’s something @manton might want to tweak. Maybe the new post window should have focus and appear at the top when a user follows a microblog://post URL?
@vincent Haha, awesome, I’ve had the exact same itch. Thanks for scratching it for me! 😊
@kottkrig Yay! 🙌 Thanks for trying it out. Any and all feedback is welcome. One thing I’m still pondering is whether it feels natural to have a test-blog directory in one’s theme directory and run the tests from there (the way it works now) or if that’s too much hassle? I can see an alternative approach where the test suite is installed like a tool instead that runs from the terminal like micro-blog-test path/to/your/theme (similar to html-validate).
@Mtt There are some rudimentary instructions on how to get started on a Mac in the root of the project for theme developers feeling brave. 😊 Tiny passes all but three tests, great work! I’ve opened a pull request with the necessary changes to get to a 100%.
@alexink You don’t have to, but you can if you want. 😊
@gr36 @iPabloSB The changelog (commit history) is available for each theme over at GitHub. Here’s Cactus, for example. I’ve run a test suite on each theme that checks for:
For now, the test suite mostly runs on my machine and is not designed to be easy to use. But we might pack it up and release it for third-party theme developers to test their own themes. Of course, nothing is stopping you from doing that now, if you feel adventurous. 😊 But it’s not officially released yet and unsupported for now.
@cliffordbeshers Maybe Signal?
@KimberlyHirsh You might be experiencing the infamous Joy-Con drift issue. If that’s the case, Nintendo will probably repair the controller for free, even if it is out of warranty. This support page has troubleshooting tips and a link at the bottom for starting a repair.
@odd Lite sent, men gratulerer med dagen! 🇳🇴
@cleverdevil Was Link still alive when you woke up? 😄
@jtr Like @manton says, your changes should be preserved. But, you might not get all my updates, depending on which files are overridden in your custom theme. A lot of the changes I’ve made resolves around lauouts/index.html and layouts/post/single.html. If you’ve made changes to the same files, yours will take precedence, and you will have to manually merge in my changes (if you want them).
@ndreas Välkommen hem! En blev ju inte mindre sugen efter att ha läst din blogg. 😊 Ni verkar ha haft det riktigt gött.
@timapple Sounds like a 10 out of 10 day if you ask me. 😊
@jean Oh, wow, I totally approve of this tweak to the guidelines. 🥰 Alt-texts: The Ultimate Guide is another hands-on article that I like, with tips and tricks for writing great alt-texts. Thanks for doing this!
@ndreas Men va häftigt! Jag vill också ta mig till Island nån gång. Hoppas ni får en fin vistelse.
@mikehaynes Beautiful! 😍 Thanks for making it.
@Mtt Wow, nice! 🎉 Thanks for the built-in support for my plug-ins. 🥰
@BenSouthwood Hehe, I know that kind of struggle too.
@otaviocc Well, that sounds infinite more important than any Zelda game ever. I wish for a successful surgery and speedy recovery.
@cygnoir As the replies is first-party functionality, I would say this is a bug in the Bear theme. I’m currently doing some theme-related work for @manton and will take a look at this. So you can just sit back and relax, replies will be included in a future update to the Bear theme.
If you’re eager to get replies going, paste the following snippet where you want them to show up (probably right below my plug-in links):
> {{ if .Site.Params.include_conversation }}
> <script src=“https://micro.blog/conversation.js?url={{ .Permalink }}”></script>
> {{ end }}
@ndreas Glad valborg!
@cygnoir Hey, I’m glad you like my plug-ins. 😊 There are a few themes with built-in support but for most, you have to include the links yourself where you want them. A code snippet has to be pasted in using a custom theme.
The process is documented here for Reply by email and here for Conversation on Micro.blog. You have to be signed in to Micro.blog for those links to work.
Let me know if anything is unclear and we will figure it out together.
@warner @JohnPhilpin The future is here! 🔮 Magic Preview 0.5.0 has noindex set.
@warner @JohnPhilpin I will add a robots meta tag with noindex set in the future. Until then, just install your theme, Magic Preview, and the No robots plug-in on your test blog and you will get preview functionality while keeping it hidden from search engines.
@bjoreman The Whisper model is impressive! And I love the whisper.cpp project. I’m using it to transcribe Hej (resten av) internet! episodes. Also, thanks to the timecodes, I hacked together rudimentary interactive transcripts. (Try clicking/tapping on a single line and wait for the player to start.)
@Alligator I love that there’s some Swedish mixed in there. Kylskåpspoesi was popular when I was a kid. “du behöva chokladmjölk” and “killing mamma slowly” are my favorites. 😊
@sannalund My co-host is the best. 🥰 And that podcast studio is definitely a step up from the makeshift one we had at home.
@crossingthethreshold Hehe, no, you’re not just seeing things; it’s a bit elusive. I’ve set up the donate link to appear for around 7% of entries in the feeds so people won’t feel bombarded with it.
@JohnPhilpin I guess anything’s possible, but the Search Space index should just mirror the rest of your blog. In other words, if my plug-in says 30 posts and replies indexed, you should be able to count 30 posts and replies if you visit the archive and replies page.
So, if Search Space shows a number that feels off to you, something is probably up with the build process. Might be a good time to force a rebuild and see if that solves the problem.
@pratik @skoobz @otaviocc @JohnPhilpin @manton Oh, yeah, I think of Micro.blog as a feed reader. It’s just a bit limited, as you cant follow any RSS feed. At least not without hacks. Micro.blog expect one (sub-) domain = feed.
But you can reply to posts outside the Micro.blog community. There are millions of microblogs on Mastodon and the larger fediverse, and your replies will be sent to any blog with support for webmentions, micro or not.
@sannalund There’s a story there. Maybe he’s the culprit and simply trying to confuse us? 😱
@skoobz @otaviocc @JohnPhilpin @pratik @manton If I hack together support for replies in my experimental feeds, it won’t feel native to the feed reader. It also won’t work with other blogs (outside the Micro. blog universe) without alternative feeds.
A better solution is reply functionality natively built-in to feed readers. So:
Support developers that already offer this feature in their apps. Monocle and Together are two examples. And reach out to the developer of your favorite feed reader to ask for this feature.
@odd theme-color is just a suggestion to the browser. It might decide, for example, that the color you provide will make text hard to read in the user interface and choose another color. You can suggest a different color for Dark Mode like this:
> <meta name=“theme-color”
> content=”#ecd96f”
> media=”(prefers-color-scheme: light)”>
> <meta name=“theme-color”
> content=”#0b3e05”
> media=”(prefers-color-scheme: dark)”>
@V_ Ah, that makes a lot more sense. 😊
@joacim Mys! Här dracks det också gin och tonic igår. 😋 Grattis till (och grymt jobbat med) 300 avsnitt!
@V_ The second list contains totally different names, though? 😅
@workswellforme My interest is piqued! I will follow along closely. I have dabbled with electronic paper myself but never ended up with a finished project. Yet. 😊 Looking forward to your next update.
@moonmehta @pimoore Thanks, guys! Regarding Reply by email, @JohnPhilpin, today’s release was a bug fix for blogs still on Hugo 0.54.
@UndamnedOne Are you trying to do headings with the #? If so, add a space after the #.
@toddgrotenhuis This is now fixed in the latest version of my plug-in (1.2.1). I used some modern shenanigans in the templates that the old Hugo (0.54) didn’t like. Thanks again for the report, and sorry for the inconvenience.
@toddgrotenhuis Yep! Sorry about that, I’m looking into it.
@sannalund Oh, man, we really need to find a better spot for our router. 😂
@gr36 I had a similar thought the other day - maybe I deserve an OLED Switch to celebrate the next Zelda? 🤔 I don’t strictly need one, as my current Switch works just fine. That screen, though… 🤤
@DaveyCraney 🎉 Nicely done!
@manton What are your thoughts on enabling cross-origin requests for API endpoints? I’m prototyping a plug-in that makes use of this endpoint, but as the fetching is happening on the client side I hit a wall. 😢
@sannalund Me too! And this was good one. 😋