Showing posts with label Technology. Show all posts
Showing posts with label Technology. Show all posts

Wednesday, September 16, 2026

Prelude to Salem Church

The first Battle of Salem Church is in the books after a short/sharp fight on Monday.  How did Sedgwick fare?  That is a tale for another time.
Sedgwick on the attack!
Today's post is but a brief update to the Blog List to test that I can follow up with another successful post after having changed my url from "http" to "https".  While my url had been "http" since inception, the HTTPS Redirect toggle ensured that my "http" was redirected to "https".  Since the populated "Original feed" url in Feedburner is a fixed entity, that redirect may not be honored.  
Heavy fighting at Perry Farm.
To guarantee that you pick up your own blog in Blog List and that others can find you after using the Feedburner bypass, the Blog List entry in the gadget must match the "Original feed" path in Configure Proxy page.  If your Original feed path shows "http" then the Blog List entry must reference "http" as well and vice versa.  This works similarly for following other blogs in the gadget.  Your url entry in the Blog List gadget must match the author of the other blog's url if that author is using the Feedburner bypass.  If another's recent post is not appearing in your Blog List and that person has used the Feedburner bypass, try editing that Blog List entry by changing either "http" to "https" or from "https" to "http".

Clear as mud?

Let's see if PWJ still updates after switching to "https".  Yep!  Looks good in my Blogroll.  How about in yours?

Sunday, September 13, 2026

Bring In The Cache Buster!

By now, we are all familiar with the issue.  Blogger's Blogroll gadget refuses to reliably pick up and publish the latest post.  I first encountered this issue back in May when I posted a short update at PWJ: Testing.  In May, this was an occasional issue with variable lags but not too long.  There were a few workarounds that seemed to lessen the burden and at least one of these techniques worked, most times, to force a repolling of Blogger's Blogroll gadget.

That situation has changed to a worse case as witnessed by blogs now seeing multi-day delays in the most recent post appearing in Blogroll.  Very frustrating.  None of the temporary "methods" I used in the past to jog the gadget into action seemed to work.  Blogger's Community has seen a growing number of complaints that I first referenced in response to a comment in PWJ: Fourteen Years of Marching Through History.  That reference pointed to New posts not showing on Reading List.  This issue holds for the Blogroll gadget as well.  One respondent laid blame on pasting formatted text into a blog post for this failure to update.  A more likely explanation is that the Reading List or Blogroll displays a cached or stale feed rather than the feed from the most recent post.  The latter explanation seems the most reasonable conclusion since current posts still appear in the daily Feedspot Today email and Feedly Reading List remains current.       

Responses in the community note, above, suggest clearing the cache.  Now, “Clearing the cache” can mean two different things, and it is important not to confuse them.  The response suggests clearing your browser cache.  Clearing the browser cache or viewing the blogsite in a private/incognito window is a good way to make sure you are seeing the current version of your own blog.  This is useful for validating whether a change made to the Blogroll gadget has appeared publicly without cache contamination by your local browser.

In the current state of affairs, Blogger’s feed cache is, again, the more likely culprit.  Blogger keeps its own cached copy of the feeds used by the Blogroll gadget.  
Blogroll gadget sometimes holds on to an old copy of a blog’s feed.  Therefore, the gadget does not always notice a new post promptly even though the post was published correctly.  This condition is reinforced by seeing that many Wordpress blogs continue to show recent updates.  What we really need to do is bring out the heavy equipment and bust through the Blogroll cache that is holding back more recent posts.

One workaround is to use Google's own Feedburner's version of the blog’s feed.  Feedburner acts as a middleman.  It takes a fresh copy of the blog’s feed and provides a different feed address for the Blogroll to read.  That is why the Feedburner approach can be useful.  On the Feedburner page, your blog should be listed under "Your feeds."  Clicking on the three dots next your feed brings up a dropdown with "Refresh feed."  This choice forces Feedburner to fetch the current feed again.  If your Blogroll points to the Feedburner URL, it may retrieve the refreshed Feedburner version rather than relying on Blogger’s stale copy of the ordinary blog feed.  Now to be clear, PWJ still references the ordinary blog feed url in Blogroll.  That is, 

http://palousewargamingjournal.blogspot.com/feeds/posts/default

An alternative option that works for some is

http://palousewargamingjournal.blogspot.com/?alt=rss

After publishing a new blog post, open Feedburner website and click on "Refresh Feed."  That click ought to set the refresh in motion.  The key to remember is that Blogger’s Blogroll can still have its own cache. Resetting Feedburner cannot force Blogger to clear that cache or trigger Blogroll to poll immediately.

Note Very Well!
Do not rely on Feedburner as though it is a guaranteed repair.  Feedburner does not give you control over Blogger’s internal Blogroll cache.  This technique is best viewed as a practical workaround and not as a definitive solution.  Blogger still needs to resolve this issue.  Good practice to back up before making changes like this and test results.  Of course, YMMV.

If you give this a try, report back with your results.  If I see recent blogs popping up in my Blogroll, I will bet that some of you gave this workaround a try.  This technique worked for allowing PWJ to appear in Blogroll with its current and timely post, but I make no guarantees that this maneuver will work for everyone.  Enter these waters at your own risk!

Thursday, August 27, 2026

Kiwix and Zimit!

 

Kiwix and Zimit?  What the heck are those?  Well, I have discovered these to be very useful tools first brought to my attention by Martin at The Waving Flag blog back in December 2025.

What are they, really?

Kiwix is the application used to read web content offline while Zimit is a tool used to create offline archives of websites for Kiwix to read.  Together, they provide a package for preserving and accessing useful online information without a need for having a live internet connection.  I use these tools as a way to archive the Palouse Wargaming Journal.

Zimit
Zimit is an automated website scraper and archiving tool.  Given a starting URL, it uses a browser-based crawler to visit pages, capture their HTML, stylesheets, scripts, images, fonts, and other resources, and follow additional links according to specified exploration rules.

After crawling, Zimit converts the captured material into a single ZIM file archive.  That archive can then be opened in Kiwix and browsed offline in a way that attempts to preserve the structure and appearance of the original site.  The process does more than simply save a page.  It preserves the links embedded within the "seed" URL to drill down into the structure of the actual website.  For me, Zimit is especially useful for creating a snapshot of reference sites.  I am likely not alone to discover a useful reference site only later to find that the website and all of its content have vanished.  

Kiwix
Kiwix is free, open-source software for browsing downloaded collections of websites offline.  This is especially associated with offline versions of Wikipedia, Wiktionary, Wikibooks, Project Gutenberg, TED content, medical references, educational materials, and other resources.  The Kiwix reader opens content packaged in ZIM files created by Zimit.  These archives can then be searched and browsed locally.

How They Work Together
Briefly, Zimit is the archiver or publisher, the ZIM file is the offline package, and Kiwix is the reader.

The basic workflow is:
  1. Choose a website.
  2. Use Zimit to crawl and package it into a ZIM file.
  3. Transfer or download the ZIM file.
  4. Open it in Kiwix.
  5. Browse the archived content without requiring internet access.
For example, the website illustrating the history of Sardinian/Piedmontese uniforms often cannot be displayed in my desktop browser.  The website can be displayed on tablet or phone but Windows refuses.  To prevent the loss of such an interesting and valuable resource, I created a ZIM file from Zimit to build an offline archive.  Then using Kiwix, that archive can be opened anytime and anywhere.  All of the tabs and hyperlinks work and there is no difference from browsing through the website with an internet connection.  Now, this website will always be available!
Reading ZIM file in Kiwix

I recommend it!


Maybe I will Zimit Kronoskaf's Project Seven Years War just for safe keeping?

Tuesday, August 11, 2026

Has AI Killed the Blogger Star?

Not that every wargaming blogger is a star, but the title of this post is a nod to The Buggles’ 1979 song, Video Killed the Radio Star.  Who, among us, still remembers the first time we saw this music video on MTV?  I knew right then that I wanted to subscribe to MTV.  Unfortunately, cable was not available in my area.  Much like MTV did for music, AI search is changing the landscape for bloggers.  Is this the next step in media evolution with no turning back?

Having experienced pageviews climbing to unbelievable heights of up to 100,000 views a day, and keyword searches dropping to near zero, something has definitely changed in the search environment.  In my own search for answers, the article,
 Search Engines Are Dead: How AI is taking Over the Internet, from March of 2026 popped up in the results.  Briefly, the article points out that AI is changing search, its process, and results.  One problem for bloggers wanting increased visibility to their writings is that AI search often does not convert search results into visits.  Directed traffic from search engines is falling by the wayside.  Today, readers must be given a reason to click through directly to a post.  While AI search may reduce clicks, your name, blog link, and unique perspective could still come through in the summaries and citations.  At least most AI summaries still provide citations of works used.  Reduced traffic often leads to reduced reader engagement.  Reductions in visits and engagement support the conclusion of many that blogging is a dying media art form.  Compounding this dilemma is the recent feature of seeing large delays in posts appearing in blogrolls.  If no one reads your contributions, is the effort worthwhile?  Of course, visits and reader engagement may not be a driving reason for why one blogs.

In today's rapidly evolving environment
, search engines increasingly try to answer questions without sending anyone back to the original sources.  Gathering and synthesizing the collective wisdom of the internet, AI generates summaries to answer the question posed.  Type in a wargaming question and the search result may now return a brief answer without requiring the researcher to visit a single blog site.  For people who have relied upon Google search engine to send strangers to their posts, this new state can be somewhat troubling.  Are wargame bloggers doomed by AI's interventions?  Lately, I have been thinking about the gloomy claim that AI may be killing blogging and, with it, the motivation to blog.

Wargaming blog
s are vulnerable to the rise of AI search because many of the most common topics are searchable in a way that suits AI.  Rules clarifications, historical overviews, army organization, paint choices, figure choices, and beginner advice are all useful, but they are also highly compressible into summaries.  If a post offers little more than the expected answer, then it can be flattened into a summary with almost no loss of content.  On the other hand, a blog post does not necessarily have to be merely an answer to a search.  It can be an argument, a battle account, a project record, a warning, an opinion, or simply an enjoyable report from somebody else’s tabletop.  Nobody really needs an AI summary of the fact that I painted another twelve figures.  Readers visiting the blog, however, may enjoy seeing how the figures came out once painted and based, learning which paint scheme was used, how this unit fits into the project plan, or reading why I abandoned the original basing plan halfway through.

By off
ering more than a simple answer to a query, wargaming blogs hold an advantage over AI.  Wargaming blogs are built on things that AI cannot (yet!) convincingly fake or manipulate at scale.  Some of the tasks that AI has yet to master include photographs of actual miniatures, handmade terrain, battle reports emphasizing different tactics and decision-making choices, and historical research as seen through the eyes of a particular hobbyist’s judgment.  A good wargaming blog does not solely rely on delivering information.  It also provides evidence of ongoing practice, planning, commitment, point of view, thoughtful commentary, persistence, and accomplishment.  That distinction matters.  Readers can find generic advice anywhere from search, but they come to a "real" hobbyist's blog for the thing that only a real, practicing wargamer can provide.  A practicing wargamer can offer a sense that the writer has actually moved figures across a table, given thought to the exercise, and, perhaps, learned something in the process.

The ris
k for the blogger is not that an AI system will suddenly make a reader lose interest in painted armies, historical scenarios, or reports from a remote game. The risk is more subtle.  Much more subtle.  AI is making it easier for readers to obtain a quick, generic answer without ever visiting the source that did the interesting (and often considerable) effort in the first place.  AI is killing "Lazy discoverability."

What i
s “Lazy discoverability?” It encompasses the habit of writing for search engines instead of writing for readers.  This technique produces posts that are technically discoverable but not especially memorable.  Bloggers may operate under the misguided assumption that one can put a reasonably competent post on the internet, include a few likely search terms, and expect search engines to do the rest.  Even before AI algorithms came to dominate search, that model was always rather fragile and suspect.  AI simply makes the weakness harder to ignore.

For hobby blogging, especially wargaming, lazy discoverability offers the possibility of entrapment because the work can become optimized toward being found instead of being worth reading.  AI search systems are very good at compressing those posts into a summary, which means the original blog gets less of the reward while the reader has less reason to click through.

A blog post ought to offer more than a summarized answer to a question.  Bloggers should emphasize depth and personal experience that no summary can replicate.  A good wargaming blog provides an archive of accumulated effort.  This is an asset and body of work that cannot be replaced by an AI summary.

If the wargaming blogger wants to avoid being crushed under the jackboot of the Machine, is there anything we can do to connect into this rapidly evolving situation?  The post linked to above offers some suggestions for adapting to AI.  I explore some of these options using my humble perspective of the PWJ and my nearly fourteen years of tapping out posts.  Where does PWJ succeed?  Where can improvements be made?  The answers may depend upon reader engagement!

AI has not killed the blogger star.  As with radio, there is still a place for blogging, at least for me, and I am no star.