Why do we refuse to receive anything but a romp through somebody (or some folks') greatest hits for our #SuperBowl halftime entertainment.

8 mile beetches!!!

Plus whoever this dude is.

Tonight's #SuperBowl halftime show presented by … ☾𐂂's high school hip hop friends.

Okay … NFT squad … what are we doing with them? Are we collecting baseball cards … or displaying them in some shape or form? Officially querying for opinion as to what you'd do were you sitting on my gallery.

By the number of y'all gettin' your accounts suspended, I see Jack has put exactly as much effort into sorting out the abuse of his reporting system for propagandic purposes as I expected him to. Stellar work Jack. ┌П┐(ಠ_ಠ)

Do other nations bring their militaries into their national sports championships?

The team that will win tonight's #SuperBowl will be the one carrying three #GeorgiaBulldogs on its roster … and you can take that to the bank.

.@IamGMJohnson's description of a second adolescence is an interesting point of insight.

Cool beans … I also have no idea how long it's been since I checked Tumblr (and Twitter has me clocked at 8,400 tweets).

.@alanritchson, love you in Titans … but Reacher is the role you were made for bud … have some happy as episode seven starts rollin' in the ☾𐂂 household.

I mean … I bundled all my plugins into my theme and I suppose I could parameterize everything theme-related and register it, but I'm guessing I wouldn't be able to version my personal configuration files via GitHub repository any longer and apply them on top of the theme … so I'm pretty sure it wouldn't be worth the effort. The problem here really seems to be that everything is a Hugo theme by nature, the distinction between components is being arbitrarily layered on top. There is no reason, for instance, that a single Hugo generated Micro.blog site cannot apply multiple theme components (which in fact they do, we call them plugins). There is no reason the order of application could not be configurable. The illusion of structure works to simplify some aspects (like plugin configuration preservation) … this is far outweighed, however, by the limitations it imposes (like what those plugins can actually do or just how configurable they actually are). The answer to this continues to be the rebranding of the custom theme into what it oughta be, the root site configuration. It preloads with the blank theme. Users can add anything they can now to a custom theme … and these files should override installed plugins/themes. File naming should be deliberate as a general rule amongst plugin and theme developers so as not to incur naming collisions. In this way you can build your site up piecemeal while maintaing the last word as to what the final parameter values (or the templates themselves) should be. And, yes. This Micro.blog site configuration should be loadable from a repository so that everyone can enjoy version control over changes to their own site. cc @manton @sod @pimoore @whoeverelse

I'll take gaslighting-a$$hats-seeing-the-face-of-which-reminds-me-there-is-still-an-art-concept-concerning-a-train-some-track-a-bridge-out-ahead-and-a-smorgasbord-of-f$&king-warning-signs-that-needs-out-of-my-head for a thousand, Alex (may you rest in peace).

Here's a tip, if your psychiatrist wants you screened for autism to rule out savant syndrome (upon seeing what your random choice to jump into digital art has yielded), don't attempt to work that sh$t into casual conversation. You sound like an a$$hole every time.

F$&k yeah

If Grogu is showing up in chain mail Imma lose it.

Okay … whatever. So I guess the Micro.blog READMEs have their own page now.

What f$&king YAML? Hugo, you're such a d$ck.

Episode two of #JackReacher … points earned for the Frankenstein's monster reference … have some happy.