Plutonic Rainbows

Lightbox2

I resolved a functionality issue with Lightbox2, where image links were opening in separate pages instead of displaying in the intended lightbox overlay. The problem was traced to build_blog.py, where HTML sanitization was stripping out the essential data-lightbox and data-title attributes required by Lightbox2. To fix this, I updated the ALLOWED_ATTRIBUTES configuration to preserve these specific attributes while retaining the overall security of the HTML sanitization. I then updated all relevant documentation files — CHANGELOG.md, CLAUDE.md, and ISSUES_AND_IMPROVEMENTS.md — to reflect this improvement in version 1.6.0, and committed and pushed the changes to the remote repository with a detailed commit message explaining the technical solution.

Blog Updates

I need to undertake extensive work on this blog over the coming weeks. There are numerous issues to address, including structural improvements and the removal of existing redundancies.

Critical Issues

I have successfully addressed all critical issues identified in the redundancy analysis for the blog project. The most significant improvement was cleaning up the massive log files that were consuming 164MB of storage – the build.log (28MB) and deploy.log (136MB) have been cleared down to minimal placeholder files of 44 bytes each.

To prevent this issue from recurring, I updated the .gitignore file to use a comprehensive *.log pattern instead of the previous specific deploy.log entry, ensuring all future log files will be excluded from version control.

Upon investigation, the reported orphaned pagination files (index2.html through index103.html) were found to not actually exist – the build system is correctly generating index.html for the first page and page2.html, page3.html, etc., for subsequent pages as intended.

These changes provide immediate benefits including substantial storage savings, cleaner repository structure, improved deployment efficiency, and prevention of future log file bloat in the codebase.

Bill Upcoming

My Claude Max bill is due in two days. Based on ccusage, I would have spent $174 over the past five days using API calls alone. So, for now at least, it seems to offer pretty good value.

Yolo Mode

After spending countless hours trying to get Claude to respect my permission settings, I was beginning to feel frustrated and stuck. Every time I tried to make progress, I was interrupted by the same repetitive and intrusive menu prompts asking for permission yet again. It felt like a never-ending loop. Eventually, while browsing Reddit in search of answers, I stumbled upon a post that appeared to offer a solution. According to the post, the key was to use a specific command-line flag: claude --dangerously-skip-permissions. I gave it a try, and to my relief, it worked. This single command effectively bypassed the constant permission requests, allowing Claude to run smoothly without the interruptions that had been slowing everything down.