Mar 06, 2026: this is gay

I'm starting to turn the chronicles gay, beginning with asking cipher (my robot programmer) to run through the code and audit the repo to better understand how to implement the ideas that follow.

Here's what happened next:

• RAINBOW_COLOURS was added to the library
• Implemented provider + hook, not wired
• ReleaseSection now accepts optional rainbowColour
• Chronicles wired
• Gay spread to multi-MDX section-list renderers
• Minor tcdb trade tweaks
• cipher triple checked we didn't miss a spot (we didn't)
• Audited & augmented tests
• Updated README.md and other documentation
• Fixed a build error
• Some props were still overriding the gay, gay takes precedence
• cipher quadruple checked......gay found

Basically, every hash tag you see at the end of each section will now take on random color of the rainbow every time a page is visited. Sometimes hash tags have a border, such as the one we are in now, sometimes the border is only a line separator between sections, and sometimes sections have no borders at all.

There's reasons for that which would take too long to explain, most of which would only make sense to me anyway, and I'm not quite sure whether or not the alter egos agree that the current implementation is good enough. Wait, what?

Let's get back to the gay of it all. If you aren't familiar with what a rainbow looks like, here's a reminder:

Oops, you are gay now. That rainbow was a coded message that makes you do some gay ass shit. Not only are the chronicles gay now, so are you. I told you this was gay before you even got here so I will be accepting no responsibility for the decisions that landed you here, covered in so much gay.

They turned you gay. ⬅️ double entendre

Focus. Continuing to how these chronicles got so gay......

First, let's talk about randomness. If you refresh this page a few times you will see that the border & hashtag color will change (most of the time) to a random color on our beautiful spectrum.

Next, let's talk about random structure. The first thing the new color scheme does is randomly generate as many colors as there are sections. If you check out yesterday's page, there are 4 sections, and the first thing that chronicle does is generate 4 of the 7 colors of the rainbow. Then, no matter which 4 colors are generated, it orders them in the sequence of a classic rainbow.

Because of this, the first hashtag on yesterday's page (no border: remember, reasons) is more likely than not to be red. If you refresh enough times though, it ain't.

Random structure.

Lastly, let's talk about any pages that have 7+ sections. If there are enough sections on a chronicle to use the full spectrum, the page will use the full rainbow in order, no matter how many sections may follow. Interestingly, there's only one chronicle that meets this criteria. It's super gay apparently.

Wanna see it? Jump Around the site.

If you were kind enough to click on that link, you are super gay now too. Dudes, you are really bad at falling for my woke agenda.

Or good at it.

Release shaolin 2.7.0 – 2026-03 planned: chronicles are gay is a minor one. 2.7.0. Let's interrogate the release structure for those new to the party:

[major].[minor].[patch]

Incrementing from a 2 to a 3 would require some sort of MAJOR change that is either large enough, or breaks some sort of backwards compatibility......which, the definition of this doesn't actually matter. This will always stay a 2. 2 is my favorite number, I have strong feelings about that, and because of those feelings - this will always stay a 2.

The end.

With this release we incremented from 6 to 7. 'Round these parts, a change in the MINOR number is quite MAJOR. There were 48 releases in 6 before we incremented to 7.

Why did we increment? This past week I made a few changes to the ReleaseSection component to help address an idea that began to sprawl. The idea was great (humble brag) and the exectution was scattershot. It's also possible the idea was scattershot (imposter syndrome) and the exectution was shit.

Point being, everything is leaps and bounds more efficient, scalable, and ready for what's next. Time to go from from 6 to 7.

There were 1319 commits leading up to this page and for the last 150(ish) days, I have added to this site 148(ish) of them. I'm currently on Take 2; Day 45 of my attempt to blog 365 days in a row. That's a level of dedication that I am proud of.

When the preceding number increments or resets, this number resets as well. This is the level that most things are released to and the day-to-day updates applied within shaolin scrolls live here.

Before we close up shop, let's take a look at some of the "bigger" things that have been added between 2.6.0 and 2.7.0.

• TCDb Trades (cardattack)
• Local Card Shops (cardattack)
• Volleyball Tournaments (unclejimmy)
• Call A Save Point (unclejimmy)
• Table Schemas (unclejimmy)

There's a little bit of something there for everyone. Or me at least, I suppose.

Click through to see what I've been up to lately. 😎

As we finally do close up shop, let's take a look at some of the engagement number over the past 30 days:

The nice thing about these numbers is that I didn't do any full, all channels, engagement farming. I might ping some groups or individuals here and there, but I didn't send messages out system wide.

With this minor release (2.7.0) though, I will go system wide and we'll check back next week to see what my full-network-clickbait-re-up can produce. Pandemic! I got that pandemic!

IYKYK

Iterate.