This is the 92 straight day that I have stopped here to drop a chronicle. That is now the official all time record for blog boi days in a row. Blog boi til I die or I brick my environment again.
Raistlin would be so proud. I mean, not really: he'd be sarcastic and in no way, shape, or form nice about it.
When I finish a trade with someone, like say
mastodonyesterday, I also include a link to the trade in my feedback comments. When I did that last night after deploying, I realized there was a bug.
Because of the relative popularity of the site, or at least the consistent
usage of the site, along with the database work mentioned above, I ran into the free limits on my Neon
database server. Rather than trying to skimp here or there, I just bit the
bullet, and started to pay for it. I only hit the cap late in the month so I
could have adjusted, and yet, paying for this is inevitable.
If you do the cost vs. how much time I spend here math, plus add in the mental health benefits of letting it all out maths, I end up with an equation that says it's doubtful there's a better bang for the buck in my life right now.
Plus, I randomly had some hits from Japan, Canada, and a brief, but significant run of hits from Singapore this week. I'll pay a few bucks a month to say hi to someone from Singapore for no good reason.
Whatever it was they were looking for, I hope they found it.
I've started to consistently hit my free database limits on
neon and they suspended me through the end of the month
today. We shan't accept this, and so I've upgraded to a paid account. It's a
pretty cheap rate based upon total monthly usage, so we'll see just how much
you end up costing me.
The Q&A session with cipher was successful. They helped me to make a decsion that was outside of the initial ask, and now we'll fold that decision point right into what's next.
AI guy is off finalizing the plans now.
Oh, that was quick, okay, get to work nerd bot, start coding.
scroll amendment · 2026-03-14PS......I'm using the newest release of the bot for the first time today and it's legit better. In easily recogizable ways.
A little bit more than two months ago, I noted there was a bug in my release ID generation process, and I just verified exactly what it is.
All of that to say, I confirmed my suspicions and the solution I had in mind then, is still the same solution I have in mind now. I wasn't waiting for this confirmation to take that path, I just haven't been motivated to do so as of yet.
I could easily fix it right now. I will not easily fix it right now. Release 142 is only whispers of a myth, entirely a legend.
Found it!
Before we get into the meat of it, I also slightly adjusted the column widths on tcdb trades so that the Partner name did not wrap on the full desktop app.
As part of today's release, which was mostly about some fun volleyball action, I optimized a few commands along the way. Primarily, to help me remember what to run. I turned these three commands I'm invoking:
tullyelly
npm run images:optimize "tcdb"
npm run images:animated "tcdb"
npm run gen:images-manifest
What I'm really here for (non-proud-dad side) is to build out some improvements to the tcdb infrastructure, starting with adding card totals to my tcdb-tradesroute. Depending on when you land on this page, and when you click that link, things will be more or less done. Godspeed.
TL;DR: I added 3 new columns to tcdb trades: sent, received, + total.
While as of this literal sentence, there is one example, the odds are good this will be an old idea by the time YOU see this.
I actually spent most of yesterday programming while today I wrote about what I did yesterday, except for the programming. Or something like that.
Anyhwo, because I hit up an antique shop for the first time since I started these chronicles, that meant I needed to extend ReleaseSection and add a new thing. That new thing took longer than I thought it would and I fell behind.
Yesterday I started arguing with cipher about the database structure it chose, and before I knew it, the day was gone. We are still arguing BTW. What you see is not what I want to see. I'd say we are off by roughly 36%.
But for real though, I updated my self care plan so if you saw the placeholder already, check it out again. It's too much.
TL;DR: I added a new thing I'm calling Secret Identity. How cool is that? lol
Basically, I created a link from hashtags to the user profiles of the individuals that have logged into the site and commented on chronicles. Good news, everyone that has commented so far has a dedicated hashtag.
Here's how we got there:
secret identity and tags added to database [WU-747]
added audit fields to auth.users and dojo.tags
refresh migration scripts
refractor v_blog_comment view
new secret identity view
new comment summary by secret identity
new tag comments endpoint
new client-side community thread
rechart added to repo, chart for squad created
add some zest to PersonTag [WU-749]
PersonTag is the primary way that tags are generated, and now they are
italicized, bolded, with a Great Lakes Blue font color thrown in
for good measure. Within those tags are a handful of individuals that have
logged in and posted comments on the site (in order of most to fewest):
It'll be hard to notice the difference on those pages if you clicked any of those links, but if you click on donnie and then scroll down until you see the comments he has posted, you will be caught up on the changes to the tags page. I'll improve the UI for this page at some point. MVP for now.
Additionally, check out squad to see the new chart I added to track who has commented the most. Scroll about half way down the page before you hit payday. Looks like this:
lulu and I agree that while
nikkigirl might be leading, she violated the spirit of the
competition, and that
lulu is the real leader. lulz
Last but not least - if you are logged in, rather than showing your first name in the header, and your full name in the comments, it will now display your Secret Identity in all cases. Some Secret Identies are more creative than others. 😏
Because of the work done in secret identity yesterday, specifically enhancing the database tooling around user comments, it allowed me to quickly turn around a profile page, of sorts, for all of my bestest pals (so far).
I also generated a cartoon character for everyone, click the links and have some fun:
That's a sneak peak at what my cartoon character looks like. Some of them I like better than others, lol. These are not a finished product.
I took a brief detour to fix a minor annoyance in the PersonTag component that drives most of the hashtag functionality and required the DOOM tag remain in ALL CAPS at all times. Rules are rules.
See the hashtag section at the bottom to live it along with me.
I also simplified how I can invoke the PersonTag component. It's now easer for me in ways that don't matter to you.
I'm back after I got bored with that cleanup task and returned back to this cleanup task and populated all of the available data elements needed for tcdb trades to maximize it's current potential.
I just asked chatgpt to build me the plan to reshape that very same tcdb trades app. While I wait for the bot to think, I'll hop back over to the cards referenced next.
Bot thought for 5 minutes, coded for 30 minutes, and then we went back and forth for a good hour before we settled on the look and feel of the trade detail page. See 946574 as an example.
It's now a creative mix of the database backend and the content that I generate daily in these chronicles. Same data, new idea, different context, and I kinda like how it turned out.
So noice in fact, that I'm going to add links to my trades content onto my TCDb profile page and increase my audience size.
Maybe.
To close the day's work, I used the same rusted red color from the details page, and tcdb itself, and applied that styling to both homies + tcdb trades.
Okay, not quite closed. I also added the tcdb trades route to the menu.
Besides being slightly more efficient on the front-end, it allows for all kinds of additional functionality to spring up off the back-end. The custom trophy that's added when the bois win a championship is one example.
1st Place
Plus, more database = more fun.
Halfway through writing about our glorious day, I realized that I needed to finish the overhaul of my optimus function, because the photos being in different spots (legacy vs new), worked everywhere except the image carousel. That meant a quick update to 1621 files.
Easy peasy, lemon squeezy. No more legacy media - cipher is fucking good.