Beyond aggregated and summarized stats, in 2025 I met a few amazing people (you know who you are), and started a few projects. Most of these projects started with an idea, or recognizing a problem, that inspired invention.

Sometimes the ideas came from observations, shared, questioned, distilled into insights, and sometimes new creations.

During one such conversation over coffee last year, James (https://jamesg.blog/) and I noticed that our Spotify “daylist” list names were often quite entertaining, despite their brevity.

We mused whether it was worth keeping track of the particularly fun or interesting names, even knowing they were automatically generated.

In September 2025, James created a page on his site, a simple HTML list of a few of his fun daylists names, and shared it:
* https://jamesg.blog/daylists

With a single real world #indieweb example, it was enough to stub a wiki page:
* https://indieweb.org/daylists

A little over two months later, during the weekend of 2025 IndieWeb Black Friday Create Day: Build Don’t Buy, I followed James’s example and built my own daylists page with a similar list of names of daylists, adding the datetimes when I had taken screenshots of my daylists.

* https://tantek.com/daylists

Realizing it was a page of items listed in reverse chronological order with datetime stamps, it made sense to mark it up as an h-feed so a social reader could theoretically subscribe to it. The list items had the minimum viable information for h-entry markup: content and a datetime. Minimal information meant only minimal markup was necessary: one nested HTML time element, and a couple of class names.

The list item of just the daylist name I started with:

<!-- a daylist item -->
<li>
  cyberpunk synthwave wednesday early morning
</li>
<!-- -->

The name’s coarse textual day and time of day was a handy bit of text to markup with the time element with a numerical date-time for parsers. That plus two h-entry class names:

<!-- minimal h-entry markup for a daylist item -->
<li class="h-entry">
  cyberpunk synthwave
  <time class="dt-published" datetime="2025-10-15 07:59">wednesday early morning</time>
</li>
<!-- -->

As linked on my daylists page, that plus a little h-feed wrapper is enough to make a web feed that a social reader like Monocle can parse and display:
* https://monocle.p3k.io/preview?url=https%3A%2F%2Ftantek.com%2Fdaylists

Minimal incremental markup added to an existing human readable HTML page.

No separate feed file needed. No XML, XSLT, or JavaScript either.

The HTML is the feed.

A feed that social readers, like Monocle, or Artemis (that James wrote) can directly follow.

Full circle.

And the year before that, James blogged about how publishing an h-feed is also a more efficient, and easier to maintain, method of supporting other formats:
* https://jamesg.blog/2024/06/06/publish-h-feed

This is post 6 of #100PostsOfIndieWeb. #100Posts #yearInReview #webFeed #microformats #microformats2 #hFeed #hEntry #socialReader #socialWeb

← https://tantek.com/2026/005/t1/year-movies-in-theaters
→ 🔮


Glossary:

Artemis
  https://indieweb.org/Artemis
daylists
  https://indieweb.org/daylists
h-entry
  https://indieweb.org/h-entry
h-feed
  https://indieweb.org/h-feed
IndieWeb Black Friday Create Day
  https://indieweb.org/events/2025-black-friday-create-day
Monocle
  https://indieweb.org/Monocle
social reader
  https://indieweb.org/social_reader
time element
  https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/time

pwr

Paced web reader (pwr) - an esoteric feed reader and workflow for keeping up to date online.

#webfeed, #software