User Interface to Indicate Posting Activity by Chris AldrichChris Aldrich (Boffo Socko)

Today I saw a note that led me to the Internet Archive which I know has recently had a redesign. I’m not sure if the functionality I saw was part of this redesign, but it’s pretty awesome. I’m not sure quite what to call this sort of circular bar chart given what it does, but circular widthmap seems vaguely appropriate.

Instead of using color gradations to indicate a relative number of posts, the UI is measuring things via width in ever increasing concentric circles. The innermost circle indicates the root domain and successive levels out add additional paths from my site. Because I’m using dated archive paths, there’s a level of circle by year (2019, 2018, 2017, etc.) then another level outside that by months (April 2019, March 2019, etc.), and finally the outermost circle which indicates individual posts. As a result, the width of a particular year or month indicates relatively how active that time frame was on my website (or at least how active thinks it was based on its robot crawler.)

I enjoyed the idea of these heatmaps and charting. I added the sparkline graph last week after I saw them on Chris’s website. I may create a separate web site page to keep these. I don’t know how useful they are, but they are just cool. I would also love a way to display some of the JetPack graphs.

These are the yearly JetPack stats from 2010, the year Automattic first offered the, to 2019.

2013 was the best year for this website.

But I get more “responses” that I did in earlier years. I suspect more of these are from semantic responses on other platforms, Facebook, Twitter, Instagram since. It’s, and the time I started using some of the IndieWeb software.

Below is the Internet Archive graph for 2018, compared to 2012. Traffic has fallen off.

2013 Internet Archive Circular Widthmaps
2018 Internet Archive Circular Widthmaps

Reply to Blog Engines and Indieweb Controlling Upstream by Brad Enslen by Chris AldrichChris Aldrich (Boffo Socko)

I’m aware of the disruption of the Gutenberg Editor within WordPress v5.0 and how it applies to those using IndieWeb technology on WordPress. I’m sure it will eventually get sorted out in a reasonable fashion. Sadly, throwing out the baby out with the bathwater as it comes to WordPress and IndieWeb may not be the best solution for many people and may actually be a painful detriment to several hundreds.

I don’t have much to add to the discussion but wanted to voice my dissatisfaction with Gutenberg and how it disrupts my recently discovered IndieWeb power (Webmentions). I considered switching to Jekyll, Hugo or Grav but ran into challenges migrating over 15 years of content and several thousand posts.