home.social

#yearinreview — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #yearinreview, aggregated by home.social.

  1. Diarycast - Year In Review (2023) - The rollercoaster thrills and spills of 2023 at EOU Towers... #podcast #yearInReview - earth.org.uk/diarycast-2024012

  2. Diarycast - Year In Review (2023) - The rollercoaster thrills and spills of 2023 at EOU Towers... #podcast #yearInReview - earth.org.uk/diarycast-2024012

  3. What a ride! Dive into workadventure's 2023 Retrospective — a nostalgic, punchy look at the year's highlights, projects, and surprises. Perfect for lovers of creative online spaces. Relive the moments that shaped the year! #Retrospective #2023 #YearInReview #WorkAdventure #PeerTube #OpenVideo #IndieVideo #English
    video.fnordkollektiv.de/videos

  4. What's that? I've published a new article on my website?

    All other writing has been on hold until I finished it, but my data review of 2025 is finally done 😅 🎉

    I have absolutely no idea if it will be of interest to anyone else, but I love these posts. And this year's was using **even more** of my own, home-grown data, captured directly via the very site it now lives on 😁

    theadhocracy.co.uk/wrote/2025-

    #IndieWeb #YearInReview #DigitalHomesteading

  5. Diarycast - Year In Review (2023) - The rollercoaster thrills and spills of 2023 at EOU Towers... #podcast #yearInReview - earth.org.uk/diarycast-2024012

  6. Diarycast - Year In Review (2023) - The rollercoaster thrills and spills of 2023 at EOU Towers... #podcast #yearInReview - m.earth.org.uk/diarycast-20240

  7. Is it too late to publish #yearinreview posts? ...asking for a friend...

    It's a mix of highlights, side projects and the usual media listicle, enjoy ✌️

    janmonschke.com/weeknotes/2025

  8. For the year in review I want to highlight notable releases in several media and I’m starting with video games. I’m going divide the releases by season, starting in Winter and ending in Fall. So without further ado. Here are the notable video game releases of 2025: #gaming #YearInReview

  9. For the year in review I want to highlight notable releases in several media and I’m starting with video games.

    I’m going divide the releases by season, starting in Winter and ending in Fall.

    So without further ado. Here are the notable video game releases of 2025:
    #gaming #YearInReview

  10. Fall 2025 Games

    Continuing our year in review, the following are the notable video game releases of Fall 2025:

    List with games releasing Fall 2025, with art, title and release date.

    And with that we conclude notable video game releases in 2025 for my year in review.

    Did you get any games from this list?

  11. Summer 2025

    Continuing our year in review, the following are the notable video game releases of Summer 2025:

    List with games releasing Summer 2025, with art, title and release date.

    Did you get any games from this list?

  12. Spring 2025 Games

    Continuing our year in review, the following are the notable video game releases of Spring 2025:

    List with games releasing Spring 2025, with art, title and release date.

    Did you get any games from this list?

  13. Winter 2025 Games

    For the year in review I want to highlight notable releases in several media and I’m starting with video games.

    I’m going divide the releases by season, starting in Winter and ending in Fall.

    So without further ado. Here are the notable video game releases of Winter 2025:

    List with games releasing Winter 2025, with art, title and release date.

    Did you get any games from this list?

  14. Is it just me or does most of the apps out there suddenly now have some kind of automatic "year in review" thing? I guess its because gen AI makes it easy. On the other hand there can be a certain sense of dread about it as it just reminds the user how much the company is spying on them.

  15. My 2025 'Year in Review' blog post is now live! ✨ It was a year focused on deliberate, sustainable work while managing post-COVID recovery. I'm sharing insights on deep dives into APIs with `httr2`, the R Package Development Advent Calendar, and ongoing `ggseg` improvements. It’s all about creating durable outputs. Come read about my journey and what's next for 2026! What were your highlights? drmo.site/8NNsxa

  16. Diarycast - Year In Review (2023) - The rollercoaster thrills and spills of 2023 at EOU Towers... #podcast #yearInReview - earth.org.uk/diarycast-2024012

  17. Today Wikipedia turns 25! )

    Looks like i read wikis for over an hour per week, and that's just on one (of 2) of their apps (& not to mention browser search results: )

    A common use case is hearing someone famous' (fuzzily familiar) name then looking it up. Also used 2 research medical terms 4my Family.

    --

    My Wikipedia Year in Review
    Here's my Wikipedia #YearInReview. Created with (one of) the #Wikipedia #Android apps

    Https://www.wikimediafoundatio

    play.google.com/store/apps/det #WikipediaYearInReview

  18. 2025 #Nintendo #YearInReview is now out. I chose #TetrisEffect as my favorite game, as it has been since release, but spent more time playing #AnimalCrossing and #Kirby in the Forgotten Land.
    year-in-review.nintendo.com

  19. 2025 Best Editorial Cartoons from #ABlueView🧵1/4

    With all of Trump's bigly news this year, it's been hard to finish the Best of 2025 cartoon series I began after Xmas, but today I'll finish with my own political cartoons.

    I can't draw but after doing this for many years I ...

    #YearInReview #BestOfABlueView #BestOf2025 #BestEditorialCartoons

  20. Well, this was a fun #Nintendo #2025 #yearinreview to read.

    Well, the main highlights, anyways.

  21. Shout-outs to the kind folks who make this work possible by funding cargo-semver-checks 🙏

    #rust #rustlang #semver #yearinreview

  22. I also propose a change in how we measure success going forward.

    I hate gameable metrics. Let's build what's most valuable for the community, not what's easiest to quantify and brag about.

    Does this resonate? Let me know what you think!

    Bonus points if you also fund cargo-semver-checks, of course!

    #rust #rustlang #semver #yearinreview

  23. Here's everything you'll find in the post above!

    If you're a regular reader, some of these sections may be familiar. There are links so you can skip ahead!

    #rust #rustlang #semver #yearinreview

  24. cargo-semver-checks is growing faster than ever:
    - 7 new releases, from v0.39 to v0.45
    - 122 new lints, more than double last year's count
    - 4x reduction in lint execution time — some lints became up to 10x faster
    - across 26 (!!) rustdoc format versions

    Check out our "year in review" 👇
    predr.ag/blog/cargo-semver-che

    #rust #rustlang #semver #yearinreview

  25. Morning Folks. This morning, I dive down a bit of a guilty pleasure rabbit hole as I talk about the YouTube channels that were important to me in 2025. I watch a lot of YouTube, or more specifically, I have videos playing in the background while I do other things. These channels are ones that I rarely miss.

    aggronaut.com/2026/01/09/2025-

    #2025InReview #YearInReview #2025Review #YouTube

  26. It is finally time for me to talk about the #Games that were important to me as part of my #2025InReview series. I am pretty certain, though, that my list looks nothing like most of the best games lists, but these were games and game events that were important to me personally.

    aggronaut.com/2026/01/08/2025-

    #ARPG #MMO #MMORPG #VideoGames #2025 #2025Review #YearInReview #GamesOfTheYear

  27. Wikipedia “Edited” 2025 year in review, summarizing from Wikimedia XTools queries, and Wikipedia itself, curated manually for my personal site:

    * 7 articles created (new personal best), with several firsts for me. In creation order:
      * "Take California" (https://en.wikipedia.org/wiki/Take_California) — first music related
      * "West Coast Health Alliance" (https://en.wikipedia.org/wiki/West_Coast_Health_Alliance) — first health related
      * "Northeast Public Health Collaborative" (https://en.wikipedia.org/wiki/Northeast_Public_Health_Collaborative)
      * "RaptureTok" (https://en.wikipedia.org/wiki/RaptureTok) — first hashtag article
      * "Governors Public Health Alliance" (https://en.wikipedia.org/wiki/Governors_Public_Health_Alliance)
      * "Stephanie D'Agostini" (https://en.wikipedia.org/wiki/Stephanie_D%27Agostini) — first comedian
      * "Mic Drop Comedy" (https://en.wikipedia.org/wiki/Mic_Drop_Comedy) — first comedy club

    * 2 Category: articles created — first ever for me. In creation order:
      * https://en.wikipedia.org/wiki/Category:2025_establishments_in_Hawaii
      * https://en.wikipedia.org/wiki/Category:2025_establishments_in_Maryland

    * 28 redirects created: https://xtools.wmcloud.org/pages/en.wikipedia.org/Tantek/all/onlyredirects

    and

    * 1 image uploaded to Wikimedia Commons: https://commons.wikimedia.org/wiki/File:2025-12-11-stefdag.jpg?photo

    In total:

    * 272 edits (not counting User: page edits) across Wikipedia and Wikimedia commons
      * 229 main Wikipedia articles edits
      * 39 Talk: page edits
      * 2 Category: page edits (above-mentioned articles created)
      * 2 Wikipedia Commons edits
     
    * 329 edits and contributions counting User: page edits: https://xtools.wmcloud.org/globalcontribs/Tantek/all///2025-12-31T01:36:35Z?limit=330

    This is my first time posting a Wikipedia “Edited” year in review, despite having edited Wikipedia for 20+ years (https://tantek.com/2025/300/t20/wikipedia-editing-anniversary).

    While this #indieweb version of a year in review was fun to make and look back on, since all the data is public, there’s an opportunity here for a service (perhaps another XTool) or open source project to create such a summary for any Wikipedia editor.

    Beyond a nicer presentation than plain text lists and numbers, such a summary could include visuals like a graphs of some of these stats over time, like Wikipedia pages created or edits of various kinds each year.

    Until then, I encourage everyone editing Wikipedia to make their own “Edited” (I made that up, feel free to pick a better term) year in review and post it on your personal site! Feel free to re-use any of the design or separation of numbers that I chose, or make up your own.


    This is post 7 of #100PostsOfIndieWeb. #100Posts #yearInReview #Wikipedia #WikipediaEdited #Wikimedia #WikimediaCommons #XTools

    https://tantek.com/2026/006/t1/2025-people-projects-insights-creations
    → 🔮

  28. 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, 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 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

  29. 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

  30. 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

  31. 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, 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 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

  32. 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, 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 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

  33. My year in movies in theaters, using Fandango > My Orders > History, my Swarm Timeline, and personal recollection, to aggregate a few lists and stats:

    I saw 9 new movies in theaters in 2025, two of them multiple times (dates are first viewing)
    * 2025-02-20 👹 Captain America: Brave New World
    * 2025-05-22 ℹ️ Mission: Impossible - The Final Reckoning
    * 2025-07-20 🦸🏻‍♂️ Superman (2025)
    * 2025-07-26 ⓸ The Fantastic Four: First Steps (2025)
    * 2025-10-09 🔺 Tron: Ares
    * 2025-11-15 🏃🏻‍♂️ The Running Man (2025)
    * 2025-11-19 🧌 Predator: Badlands
    * 2025-12-03 🪄 Now You See Me: Now You Don’t
    * 2025-12-14 🧹 Wicked: For Good

    In these cities:
    * 11x San Francisco
    * Berlin
    * Boston
    * San Diego

    At the following movie theaters:
    * 6x AMC Metreon Dolby
    * 2x AMC Metreon IMAX
    * Zoo Palast
    * Alamo Drafthouse SF HDR BARCO
    * AMC Boston Common IMAX
    * Regal Stonestown Galleria ScreenX
    * Regal Stonestown Galleria
    * AMC Mission Valley 20

    In the following formats, in rough order of frequency then features/quality:
    * 5x Dolby
    * 2x IMAX
    * 2x Standard
    * 3D IMAX
    * 3D Dolby
    * HDR BARCO
    * ScreenX
    * Standard German dub

    The latter three were new formats for me this year: HDR BARCO, ScreenX, and Standard German dub.

    My preferred movie format is still Dolby, in particular in the Metreon Dolby theater. I’ve been other “Dolby” theaters (including other AMC Dolby) and none have measured up. Dolby theater audio quality is significantly better than any IMAX theater I have been in.

    3D IMAX can look amazing for the right film (e.g. Tron: Ares). In comparison, I was not impressed by 3D Dolby, or any other 3D projection+glasses technologies over the years.

    HDR BARCO was very high quality, however, having seen the same film (Tron: Ares, with lots of dark scenes) in both HDR BARCO and Metreon Dolby, I could not see a discernible difference in the visual quality. Perhaps the light pollution from the Alamo Drafthouse's under-table lights interfered with the quality of the HDR BARCO experience.

    I archived the page that Alamo Drafthouse had setup for the HDR BARCO Tron: Ares showing:
    * https://web.archive.org/web/20251011173709/https://drafthouse.com/sf/event/special-event-tron-ares-hdr-by-barco?cinemaId=0801&sessionId=74102
    Unclear why they took the page down.

    ScreenX was an entertaining gimmick for the landscapes of Predator: Badlands. I would consider seeing another suitable movie in the format.

    Watching a film dubbed in German was an interesting challenge that pushed and exceeded my German speech comprehension skills. I had to use contextual cues, on screen, sci-fi terminology, and the Fantastic Four subject matter to interpret much of it.

    I constructed these summary lists by hand, and having completed them, I think next time it might work better to incorporate the raw data into a table with various columns for date, time, film name, theater, auditorium, format, and perhaps more like seat number(s) and the set of us at the viewing. I would not include classic "IMDB" fields like genre, director, writer etc. because all of those are independent of the particular theater/viewing and can easily be looked up on Wikipedia. Duplicating that info in my own personal notes would merely add noise to the signal of each specific movie theater experience.

    I’m curious if anyone else has done something like this / is doing this to keep track of the movies they see in theaters, what info to capture about the viewing, what to note about the particular experience, and what to publish on their #indieweb site.

    This is post 5 of #100PostsOfIndieWeb. #100Posts #yearInReview #yearInMovies #yearInTheaters

    https://tantek.com/2026/004/t1/year-in-sport
    → 🔮

  34. My Year in Sport, using data from my Strava, Swarm, and personal notes & recollections, assembled into a simpler summary on my personal site.

    2025 activities according to Strava:
    🏃🏻‍♂️1354mi + 160,077' hiking+running
     👟 823mi + 119,453' running
      ⛰ 485mi trail running
      🛣 337mi road running
     🥾 526mi + 40,624' hiking
    🧘🏻‍♂️ 8h27m yoga
    💪🏻 some number of weight-lifting sessions (less than one a week)
    🚲 4.6mi + 413' bicycling — only one ride all year somehow(?)
    🪨 1 bouldering session (at Movement)

    Races:
    🏁 3 races, finished 2
    🌳 12k Bay to Breakers 1:55:31 https://tantek.com/t5c61
    ⛰ 50k Skyline: 9:34:51 https://tantek.com/t5dQ1

    2025 was a more difficult year than expected, in many ways, and it cut both the hours and frequencies of many physical activities.

    My hours and frequency of yoga, weight-lifting, bicycling, and bouldering all dropped from 2024 to 2025. My goals for 2026 are to find sustainable regular rhythms for each of those, either by myself or with friends.

    Despite that, I made several improvements in 2025 over 2024:
    * Overall: 160,077' climbed, +9.4k' over 150,676' in 2024
    * Running: 823mi + 119,453', +20mi +8.3k' over 803mi + 111,155' in 2024
    * Hiking: 526mi just barely (+6mi) over 520mi in 2024
    * Finished a 50k! First since mid-2023.

    I have a few running goals for 2026:
    * incrementally faster Bay to Breakers over 2025
    * Broken Arrow 23k Skyrace, finish and ideally beat my 2024 time (6h52m)
    * finish a 50k trail race, my fifth 50k

    I don't have specific metrics goals, like total distance, or feet climbed, or any specific race times (other than beating last year’s times). Those are all secondary to my goals.

    Based on how the past few years have gone, I believe these are reasonable goals, yet will take focus and hard work to achieve them.

    Lastly, this personalized, #indieweb “year in sport”, reflects much more of what matters to me than any summary from an online service. It’s not perfect and doesn’t need to be. It’s a start and I expect to iterate and improve it next year.

    This is post 4 of #100PostsOfIndieWeb. #100Posts #yearInReview #yearInSport

    https://tantek.com/2026/003/t1/seek-2025-year-in-review
    → 🔮


    Glossary:

    Year in Review:
      https://indieweb.org/year_in_review

  35. 2025 was big builds, long drives, questionable decisions, and a lot of nights under the stars.

    This isn’t just a highlight reel, it’s a look back at the wins, the struggles, and the lessons that shaped the year.

    Got a favourite moment or an idea for what comes next, let me know.

    And remember, look up, question everything. 🌌

    #AstroPuNk #Astronomy #YearInReview #2025Recap #Astrophotography #NightSky

    youtu.be/LoTxQbLSzU0