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
→ 🔮
* 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
→ 🔮
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
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
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
→ 🔮
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
→ 🔮
It's moving day for the cats! They are still suspicious but they like hanging out with us on the bed.
Can't believe we already found somewhere we should have added an outlet. So instead I drilled through the cabinets to run an extension cord from the one outlet we *did* put inside the cabinets, and now there's power for the shredder.
Got the new litter boxes all ready for the cats to move in!
ok, got the TV box mounted behind the TV, it only sticks out like 3 inches and still looks pretty good on the wall with no cables visible
did you know you can just buy cup rinsers for your house??
we also moved the couch in today!
It's kitchen organizing day!
I got the Frame TV hung on the wall, next up is to hide the box behind the TV.
If I had really planned ahead I would have put a panel in the wall so the box could live inside the wall and the TV would be flush, but I wasn't actually sure about the Frame TV when we had to make that call.
Normally it wouldn't be a huge deal to retrofit it, but this is a shear wall so there's actually plywood behind the drywall which makes the whole thing a lot more complicated. Plus there's also a million power and network cables inside the wall already so I'm not even sure there is room for a panel anyway.
If I had really planned ahead I would have put a panel in the wall so the box could live inside the wall and the TV would be flush, but I wasn't actually sure about the Frame TV when we had to make that call.
Normally it wouldn't be a huge deal to retrofit it, but this is a shear wall so there's actually plywood behind the drywall which makes the whole thing a lot more complicated. Plus there's also a million power and network cables inside the wall already so I'm not even sure there is room for a panel anyway.
