For the Micro.blog-heads, once I'm done pushing the boundaries of what a plugin can do, I'll start taking requests. You can see what all I'm playing around with here

Hey … Apple engineers … feels like keeping which messages I've f$&king checked in sync between the phone … and the watch … isn't all that big of an ask.

Updated the lightbox plugin's README with the whole dynamically generated Javascript spiel: moondeer.blog/2021/10/3...

.@mantion … So, parameterizing the plugin-lightbox options (via data files, see this post) totally worked. lightbox.js is now a template file that gets built along with the rest of the site. The walls of possibility for Micro.blog plugins just expanded outward by a sh$t ton.

Now I get to reduce the sh$te out of those stylesheets by introducing variables, partials, and mixins. woot.

Boom, @manton, and just like that … all my custom theme's stylesheets are now built from Sass files located in the theme's assets/sass directory.

And I've just figured out how to get Micro.blog's Hugo flavor to process Sass files.

Interesting that switching on Cloudflare's developer mode breaks Twitter card image fetching. I think it has to do with wonky SSL that proxying through Cloudflare fixes.

A plugin for Micro.blog that injects structured data for blog posts via a JSON-LD script tag. This is what search engines use to decorate their results. Confirmation that the structured data is accessible can be had by using Google’s rich results test. It's code lives here.

Read More

Murphy's been #AirDryin' since she got outta the shower.

#Tuckered

#Survivor 41 has got some interesting strategic complexity.

'I think I showered yesterday' isn't really a thought you wanna have come out in your inner monologue #ADHD

A guide to navigating the non-obvious nature of the process for providing the data my plugins want … and that you want to give them.

Read More

Totally sitting on an art concept for AG Garland, been waiting for my programming fever to pass. Here's a hint: the overall theme is accountability.

Today's random rabbit hole was finally cracking the creation of custom file formats under the Micro.blog flavor of the Hugo templating engine. Ended up updating plugin-favicon.

Everyone feels trauma … that b$tch is indiscriminate. Kyle feels it. The families of those he killed feel it. The g0dd@mn trick would be to merge the dual-f$&king-reality bubbles so that we might make strides towards the f$&king prevention of trauma (or at least its mitigation).

Whole lotta what-exactly-are-we-doing-here.

F$&k it … the CSS sh$t show surrounding the new post category breadcrumb list can wait until tomorrow.

Updated this one: plugin-favicons

All that time fussing with aliases, turns out you can just straight up set the category page's URL in the front matter:

---
title: "Perspectives"
description: "Essays off the beaten path, mostly political in nature at the moment."
url: /perspectives/
menu:
  main:
    name: "Perspectives"
    title: "Perspectives"
    identifier: "perspectives"
    url: "/perspectives/"
    weight: 10
---

*Essays off the beaten path.*

Recreated @manton's Conversation.js output. Not sure why yet.

<div id="conversation-output"></div>
<script type="text/javascript">

fetch('https://micro.blog/conversation.js?url={{ .Permalink }}&format=jsonfeed')
  .then(response => response.json())
  .then(data => {
    loadResponse(data);
  });
  
  function loadResponse(response) {
    let output = document.getElementById("conversation-output");
    if (response.title == "Conversation") {      
      let posts = response.items.map(entry => loadEntry(entry));
      posts.forEach(post => output.appendChild(post));
    } else {
      output.remove();
    }
  }
  
  function loadEntry(entry) {
    let date = new Date(entry.date_published);
    let post = document.createElement("DIV");
    post.setAttribute("class", "microblog_post");
    post.innerHTML = `
  <div class="microblog_user">
    <img class="microblog_avatar" src="${entry.author.avatar}" width="20" height="20" style="max-width: 20px;" />
    <span class="microblog_fullname">${entry.author.name}</span>
  </div>
  <div class="microblog_text">${entry.content_html}</div>
  <div class="microblog_time">
    <a href="${entry.url}>${date.toDateString()}</a>
  </div>`;
   return post
  }

</script>

Ignore this one.

Micro.blog moondeer.blog

webmention.rocks/test/1 webmention.rocks/test/2 webmention.rocks/test/3 webmention.rocks/test/4 webmention.rocks/test/5 webmention.rocks/test/6 webmention.rocks/test/7 webmention.rocks/test/8 webmention.rocks/test/9 webmention.rocks/test/10 webmention.rocks/test/11 webmention.rocks/test/12 webmention.rocks/test/13 webmention.rocks/test/14 webmention.rocks/test/15 webmention.rocks/test/16 webmention.rocks/test/17 webmention.rocks/test/18 webmention.rocks/test/19 webmention.rocks/test/20 webmention.rocks/test/21 webmention.rocks/test/22 webmention.rocks/test/23/page

For those wondering why House Republicans wouldn't vote an infrastructure bill they helped write: moondeer.blog/2021/10/0...

Pffftttt