Posts

Git is not suitable for managing versions of Excel and Word files

Related publicly shared ChatGPT (CG) chat:  Git handling .xlsx files The context is an Excel workbook having list of posts in a blog that is part of my Blogger Blog Post Size Utility Scripts project - Associated GitHub Public Repo and associated blog post . Given below is a summary provided by CG for above chat which has been slightly edited by me. Managing Excel and Word Files Inside a Git Repository — A Practical Exploration The author explored how Git handles Microsoft Excel ( .xlsx ) files inside a project repository that primarily contains PowerShell scripts and text files. Later the author asked for including Microsoft Word ( .docx ) files in this summary as the same applies to it too.  How Git Stores Excel and Word Files Git treats .xlsx and .docx files as binary blobs , not as structured documents. Unlike text files: Git cannot show meaningful line-by-line diffs. Git cannot intelligently merge concurrent changes. Each modification typically results in a new ...

Discussion and Analysis of Dark Reader Chrome extension test post with Gemini assitance

My recent blog post: Testing Dark Reader Chrome extension addition of darkreader CSS styles to HTML of blog post edited in Compose mode is discussed and analyzed with help of Gemini in this post. Related chat: Analyzing Blog Post Bloat and Content Given below is an edited version of related exchange with Gemini (Gem). I saved the contents of 'Edit HTML' view of above blog post in a file post-orig.html and uploaded it to Gemini. Me: 4 Mar. 2026: The uploaded file has a test blog post I created: Testing Dark Reader Chrome extension addition of darkreader CSS styles to HTML of blog post edited in Compose mode Please study the HTML in this file which has the test procedure as well as the data. Then give me your analysis and views. Gem: The HTML content in post-orig.html provides a clear technical demonstration of how the Dark Reader Chrome extension interacts with the Blogger Compose mode to inject permanent CSS bloat. Analysis of the Test Procedure The file documents a multi...

Testing Dark Reader Chrome extension's addition of darkreader CSS styles to HTML of blog post edited in Compose mode

Follow-up post:  Discussion and Analysis of Dark Reader Chrome extension test post with Gemini assitance ================================================================ Test to see if Compose adds darkreader CSS styles (e.g. --darkreader-inline-color) even when Dark Reader extension is enabled but is switched 'Off' temporarily in its UI. Identifying Blogger blog posts with size bloat This test confirms that adding text and a link in Compose when Dark Reader extn. is enabled but switched 'Off' does NOT add darkreader CSS styles to Blogger post. I used HTML view to check the generated HTML. Now I will switch 'On' Dark Reader extn. and repeat the same addition of text and a link in Compose mode. Test to see if Compose mode adds darkreader CSS styles when Dark Reader extension is enabled and is switched 'On'. Identifying Blogger blog posts with size bloat This test confirms that adding text and a link in Compose when Dark Reader extn. is enabled and switche...

Identifying Blogger blog posts with size bloat

Last updated on 4 Mar 2026 Quick Info Blogger Blog Post Size Utility Scripts GitHub Public Repo Details This post follows up my previous post:  Fixing Gemini chat to Blogger Compose post copy-paste causing 1.5 MB post size bloat due to unnecessary CSS . Gemini chat: Blogger Feed Request Issue This part of the chat happened over a few days from end February to early March 2026, and was interspersed with work related to above mentioned blog post creation. [In response to Gemini question: Are there any other posts you noticed in your feed that might still be carrying that Gemini/Dark Reader bloat?] Me: I am sure there are other posts too but the content copy-pasted from Gemini was limited and so I did not encounter this issue. I did notice that my incremental blog backup size had become much more than usual (into few MBs instead of being less than an MB). I need to first identify which are the specific posts which are big in size. Blogger dashboard is not showing it to me. S...

How to copy-paste Gemini Chats to Blogger posts without CSS bloat

Last updated on 5 Mar 2026 Summary Step   Action Tool 1 Copy Raw Markdown   Gemini Response Copy Button 2 Convert to HTML MarkdownToHTML.com 3 Escape Brackets Manual Edit (e.g.,  <  to  &lt; ) 4 Validate Syntax VS Code / Prettier 5 Publish Blogger (HTML View) Note that for user messages, Gemini Copy button seems to put only plain text (not markdown) on the clipboard. Plain text may be directly added to Compose window of Blogger which handles conversion to HTML, including conversion of line breaks in plain text. ========================================================== ========================================================== Details ...

Fixing Gemini/ChatGPT chat to Blogger Compose post copy-paste causing upto 1.5 MB post size bloat due to unnecessary CSS

Last updated on 4 Mar 2026 Summary The Problem: Copy-pasting content from Gemini Chat into the Blogger Compose view was injecting thousands of lines of hidden CSS and browser extension variables (like Dark Reader styles). This issue also impacted ChatGPT chats but with lesser size. The Impact: Single blog posts ballooned from a few kilobytes to upto  1.5 MB , causing the Blogger Feed to truncate results and breaking the BloggerFeedToBook incremental backup utility. The Solution: A 12-step sanitization process using PrettyHTML and VSCode to strip unnecessary tag attributes while preserving headers, bolding, and lists. This solution works for both Gemini and ChatGPT copy-paste CSS bloat issues. The steps in the process are given below in this Summary itself. The Result: Post sizes were reduced by 96% (from 1,491 KB down to ~50-60 KB) without losing any visible text or core formatting. 12-step Sanitization Process Copy HTML of original blog post using 'Edit HTML' ...

Started blogging about my serious and deliberate usage of AI tools - ChatGPT and Gemini - in April 2025; Limited serious use of CoPilot AI chat from May 2025

I was curious to know when I started blogging about my usage of AI tools. A couple of days back I searched on my active blogs and found that it was in April 2025 which is close to a year ago that I first started blogging about my usage of ChatGPT and Gemini which were the first AI tools that I used in a deliberate way. I think even before April 2025, I would have accepted some CoPilot code completion suggestions in VSCode and also perhaps tried out some chat messages with it related to some syntax errors. But those were not deliberate and sustained sessions. Also I would have tried out ChatGPT and Gemini prior to April 2025 but not to the extent that I wanted to mention that in my blogs. My first blog entry about CoPilot usage is in May 2025. Note that I have used CoPilot only in the context of software development work. I think I can conclude that it was from April 2025 or perhaps a month or two earlier, that I started seriously and deliberately using AI tools (for example, having a l...