#LittleMissRandom

And for the non-sporting types … today’s the day the jersey gets washed.

Well, sorry defense … we needed Daniels … and we were to romantic to play him

When you’ve blown through your daily 10,000 query limit set by Google when using their programmable search engine custom search API right on the brink of finalizing the parameterization of CSS variable values for your Micro.blog plugin (and finally being done with it):

#Caturday #BreakingBad

Animating via CSS transition and the manipulation of custom CSS variables (which will, of course, end up as plugin parameters) from Javascript. Bootstrap class name congestion can go ahead and f$&k off now.

BTW, the-fall-of-row + our-current-distribution-of-wealth = acceleration-towards-the-white-minority-nation. How you like them apples, @GOP?

#Unscripted

#HeavyIsTheSleepyHead

So I’ll definitely come back to touch up the bookshelf plugin after I’m done piddling with this site search plugin. It was the first plugin I did … so it’s missing all the best-practices I’ve been codifying as well as all the tricks I’ve learned along the way.

.@JohnPhilpin @pimoore @maique @artkavanagh @odd @agilelisa @frostedecho @tda

I suppose another good primer for my plugins would be a walkthrough explaining all the ways I subvert @manton’s web-client-interface-based Hugo configuration in order to grab control over more of the build process:

config directory allows for safe, opt-in overriding/supplementing of things like the main navigation menu, the site.Author values (which you can straight up make up your own if you remember to access them in all lowercase

data directory allows you to drop in files with configuration data that become more easily accessible than plugin parameter values and more safely accessed as Hugo automatically parses them appropriately where as the plugin parameter interface saves everything as a string value

That all sounds scary, but in the end, what it means is that all my (complex) plugins really ask of y’all is to fill out a config file like a form of parameter values … and by making them TOML files included in the plugin itself I get to set you up with a template where I can add comments exaining how each value is used.

The Micro.blog programmable search engine plugin is getting damn close to finished now.

When you learn new sh$t just to toot your own horn.

This is me playing #BrainWars … and I’ve just learned that what I’m doing … is making the Stroop Effect my b$tch.

Imma toss out the most unique aspect of my #DualADHDBrain in a second … y’all can see if you have any better luck trying to figure out what to do with it than I have the last 44 years I’m still not sure what you call this but I just learned what it is I’m doing.

When UR 44, U start working out w/ a personal trainer & on the way home U just miss out on the opportunity 2 record a white cute-a-f chihuahua N the car next 2 U howling along N the passenger seat 2 the sound of the siren belonging 2 the fire truck racing through the intersection

When you’re 44 and you start working out with a personal trainer.

Closing in on a custom site search Micro.blog plugin.

I thought reacquainting myself with Javascript would be more fun … it’s just bumming me out that I can’t use Swift. Swift really is stellar f$&king programming language.

Episode 5 of #TheShrinkNextDoor is hard to watch.

F$&k Mark … this is meta

Updated this one:

moondeer.blog/2021/11/0…

For the Micro.bloggers that are watching the plugin development … once I slow down a bit on innovation I plan to do some practical posts that are more like guides to how to use or implement this stuff. I tend to get caught up in all the things I think of next.

A storytime spaghetti reply thread experience

Read More

Now that I’ve rolled my own Twitter cards I oughta be able to recreate my storytime spaghetti reply threads … first attempt incoming.