Updates tagged with indieweb on stadeus!
: Happy Twin Peaks day to those who celebrate!In Agent Cooper’s first appearance in the show, he’s driving a car, right hand on the steering wheel, left hand holding a small black box (a microcassette recorder), that, if you don’t look too closely, could easily be mistaken for a regular sized black iPhone with a flush battery pack attached to its back.You may search the web for a screen capture or video if you like, or continue with this plain text description.He's keeping his eyes on the road, and dictating audio.“Diane, 11:30 a.m., February 24th. Entering the town of Twin Peaks.”In 1989 he’s dictating a log entry to his presumably human assistant, Diane, for her to transcribe after the fact.In 2026 (notwithstanding safety and legal concerns while driving) it’s not a stretch to say he could (would likely) be dictating to his (perhaps renamed) digital assistant, Diane, or at least a speech-to-text feature in a note-taking application that would automatically transcribe his words in real time.Those transcribed words could even be saved as a private post or draft, either locally on his device, or to his personal website, for him to review and clean-up if necessary before publishing to and notifying perhaps a limited audience.Imagine capturing your thoughts without having to look at a screen. No scrolling to first see what others have said. No attention-distracting alerts or admintax prompts to update an application. Capture your thoughts as they occur, and continue onward, focused on your current task or project, uninterrupted.Today’s technologies and standards should enable such an interaction, all the way through to storing your dictations in a location of your choice. I wonder if anyone has built this.This is post 8 of #100PostsOfIndieWeb. #100Posts #IndieWeb #TwinPeaksDay← https://tantek.com/2026/007/t3/wikipedia-edited-year-in-review→ 🔮
's status on Tuesday, 24-Feb-2026 22:14:00 EST
Happy Twin Peaks day to those who celebrate! In Agent Cooper’s first appearance in the show, he’s driving a car, right hand on the steering wheel, left hand holding a small black box (a microcassette recorder), that, if you don’t look too closely, could easily be mistaken for a regular sized black iPhone with a flush battery pack attached to its back. You may search the web for a screen capture or video if you like, or continue with this plain text description. He's keeping his eyes on the road, and dictating audio. “Diane, 11:30 a.m., February 24th. Entering the town of Twin Peaks.” In 1989 he’s dictating a log entry to his presumably human assistant, Diane, for her to transcribe after the fact. In 2026 (notwithstanding safety and legal concerns while driving) it’s not a stretch to say he could (would likely) be dictating to his (perhaps renamed) digital assistant, Diane, or at least a speech-to-text feature in a note-taking application that would automatically transcribe his words in real time. Those transcribed words could even be saved as a private post or draft, either locally on his device, or to his personal website, for him to review and clean-up if necessary before publishing to and notifying perhaps a limited audience. Imagine capturing your thoughts without having to look at a screen. No scrolling to first see what others have said. No attention-distracting alerts or admintax prompts to update an application. Capture your thoughts as they occur, and continue onward, focused on your current task or project, uninterrupted. Today’s technologies and standards should enable such an interaction, all the way through to storing your dictations in a location of your choice. I wonder if anyone has built this. This is post 8 of #100PostsOfIndieWeb. #100Posts #IndieWeb #TwinPeaksDay ← https://tantek.com/2026/007/t3/wikipedia-edited-year-in-review → 🔮
: 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/onlyredirectsand* 1 image uploaded to Wikimedia Commons: https://commons.wikimedia.org/wiki/File:2025-12-11-stefdag.jpg?photoIn 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=330This 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: https://xtools.wmcloud.org/) 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→ 🔮
's status on Thursday, 08-Jan-2026 02:57:00 EST
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: https://xtools.wmcloud.org/) 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, 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/daylistsWith a single real world #indieweb example, it was enough to stub a wiki page:* https://indieweb.org/daylistsA 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/daylistsRealizing 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 follow 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 --> cyberpunk synthwave wednesday early morning <-- -->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 --> cyberpunk synthwave wednesday early morning <-- -->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 read and display:* https://monocle.p3k.io/preview?url=https%3A%2F%2Ftantek.com%2FdaylistsMinimal incremental markup added to an existing HTML page. No separate feed file needed.The HTML is the feed.This is post 6 of #100PostsOfIndieWeb. #100Posts #yearInReview #webFeed← https://tantek.com/2026/005/t1/year-movies-in-theaters→ 🔮Glossary:daylists https://indieweb.org/daylistsh-entry https://microformats.org/wiki/h-entryh-feed https://microformats.org/wiki/h-feedIndieWeb Black Friday Create Day https://indieweb.org/events/2025-black-friday-create-dayMonocle https://indieweb.org/Monoclesocial reader https://indieweb.org/social_readertime element https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/time
's status on Wednesday, 07-Jan-2026 02:42:00 EST
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 follow 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 --> cyberpunk synthwave wednesday early morning <-- --> 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 --> cyberpunk synthwave wednesday early morning <-- --> 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 read and display: * https://monocle.p3k.io/preview?url=https%3A%2F%2Ftantek.com%2Fdaylists Minimal incremental markup added to an existing HTML page. No separate feed file needed. The HTML is the feed. This is post 6 of #100PostsOfIndieWeb. #100Posts #yearInReview #webFeed ← https://tantek.com/2026/005/t1/year-movies-in-theaters → 🔮 Glossary: daylists https://indieweb.org/daylists h-entry https://microformats.org/wiki/h-entry h-feed https://microformats.org/wiki/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 GoodIn these cities:* 11x San Francisco* Berlin* Boston* San DiegoAt 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 20In the following formats, in rough order of frequency then features/quality:* 5x 2D Dolby* 2x IMAX* 2x Standard* 3D IMAX* 3D Dolby* HDR BARCO* ScreenX* Standard German dubThe 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=74102Unclear 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→ 🔮
's status on Monday, 05-Jan-2026 21:52:00 EST
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 2D 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 → 🔮
: 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/t5dQ12025 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 50kI 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
's status on Monday, 05-Jan-2026 00:40:00 EST
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
: My Seek 2025 Year in Review:* 101 new species observed (down from 141 last year)Top three kinds: * 64 new plants (down from 79) * 14 new insects (down from 20) * 8 new fungi* 4 new challenge badges earned (down from 56)July, June, February were the months I observed the most new species.Last year: June, March, July.Seek also gave me a graph of observations per month, and also a map of where I made my discoveries.As noted last year: https://tantek.com/2025/020/t1/seek-2024-year-in-reviewSeek is a delightful free (like actually free, free of tracking, free of surveillance) native mobile application for identifying species.Made by the iNaturalist folks (https://www.inaturalist.org/pages/seek_app), Seek works:1. works without creating an account2. works completely offline to identify species3. adds new species to your local collection on your deviceThose first two capabilities (no login wall, offline first) are what we should aspire to when we build #indieweb apps or websites for ourselves and our friends.This is post 3 of #100PostsOfIndieWeb. #100Posts #yearInReview #iNaturalist #SeekApp← https://tantek.com/2026/002/t1/find-export-strava-year-in-sport→ 🔮Glossary:login wall https://indieweb.org/login_walloffline first https://indieweb.org/offline_first
's status on Sunday, 04-Jan-2026 02:49:00 EST
My Seek 2025 Year in Review: * 101 new species observed (down from 141 last year) Top three kinds: * 64 new plants (down from 79) * 14 new insects (down from 20) * 8 new fungi * 4 new challenge badges earned (down from 56) July, June, February were the months I observed the most new species. Last year: June, March, July. Seek also gave me a graph of observations per month, and also a map of where I made my discoveries. As noted last year: https://tantek.com/2025/020/t1/seek-2024-year-in-review Seek is a delightful free (like actually free, free of tracking, free of surveillance) native mobile application for identifying species. Made by the iNaturalist folks (https://www.inaturalist.org/pages/seek_app), Seek works: 1. works without creating an account 2. works completely offline to identify species 3. adds new species to your local collection on your device Those first two capabilities (no login wall, offline first) are what we should aspire to when we build #indieweb apps or websites for ourselves and our friends. This is post 3 of #100PostsOfIndieWeb. #100Posts #yearInReview #iNaturalist #SeekApp ← https://tantek.com/2026/002/t1/find-export-strava-year-in-sport → 🔮 Glossary: login wall https://indieweb.org/login_wall offline first https://indieweb.org/offline_first
: 2026 goals I’ve heard:* Dry January — avoid alcohol* Meatless January — avoid meatIf you have a personal website, how about also:* No Socials January — avoid #socialMedia silosNo posting on social media, just for a month (not counting DMs).Instead, since you have your own website, post there, and see how that feels.If you don’t have a personal website, make it your goal for the month to set one up. The #IndieWeb folks https://indieweb.org/ can help! Join https://chat.indieweb.org/Once again I am restarting a #100PostsOfIndieWeb #100Posts project for the year.This is post 1.Previously:* https://tantek.com/2025/001/t1/15-years-notes-my-site-first← ✨→ 🔮
's status on Friday, 02-Jan-2026 01:56:00 EST
2026 goals I’ve heard: * Dry January — avoid alcohol * Meatless January — avoid meat If you have a personal website, how about also: * No Socials January — avoid #socialMedia silos No posting on social media, just for a month (not counting DMs). Instead, since you have your own website, post there, and see how that feels. If you don’t have a personal website, make it your goal for the month to set one up. The #IndieWeb folks https://indieweb.org/ can help! Join https://chat.indieweb.org/ Once again I am restarting a #100PostsOfIndieWeb #100Posts project for the year. This is post 1. Previously: * https://tantek.com/2025/001/t1/15-years-notes-my-site-first ← ✨ → 🔮
: Important #indieweb lesson in #modular website setup this morning:Keep your DNS provider separate from your CDN separate from your webhost, so you can swap out any one of them as necessary, whether for economic or as it were today, reliability reasons. And make sure those services themselves don’t depend on each other.This is of course regarding the #Cloudflare #outage: * https://www.cloudflarestatus.com/incidents/8gmgl950y3h7* https://theguardian.com/technology/2025/nov/18/cloudflare-outage-causes-error-messages-across-the-internet* https://the-independent.com/tech/cloudflare-down-twitter-not-working-outage-b2867367.html* https://bbc.com/news/articles/c629pny4gl7o* https://independent.co.uk/bulletin/news/nj-transit-down-app-cloudfare-outage-b2867457.html#CloudflareOutage #NJTransit #ChatGPT #Shopify #Dropbox #Coinbase #Twitter/X #modularity #devopsThis is post 17 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2025/311/t2/indieweb-sessions-btconf-berlin→ 🔮
's status on Tuesday, 18-Nov-2025 09:51:00 EST
Important #indieweb lesson in #modular website setup this morning: Keep your DNS provider separate from your CDN separate from your webhost, so you can swap out any one of them as necessary, whether for economic or as it were today, reliability reasons. And make sure those services themselves don’t depend on each other. This is of course regarding the #Cloudflare #outage: * https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 * https://theguardian.com/technology/2025/nov/18/cloudflare-outage-causes-error-messages-across-the-internet * https://the-independent.com/tech/cloudflare-down-twitter-not-working-outage-b2867367.html * https://bbc.com/news/articles/c629pny4gl7o * https://independent.co.uk/bulletin/news/nj-transit-down-app-cloudfare-outage-b2867457.html #CloudflareOutage #NJTransit #ChatGPT #Shopify #Dropbox #Coinbase #Twitter/X #modularity #devops This is post 17 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2025/311/t2/indieweb-sessions-btconf-berlin → 🔮
: Great #indieweb sessions at #btconf #Berlin!Yesterday, Sacha Judd (@sachajudd.com) reminded us to “teach someone …. something about building for the web”, and to “take back control of your feeds, your attention, and … go exploring again”. She encouraged us to “build healthy online neighborhoods”. That’s a great metaphor and very complementary to rebuilding your own home(page) on the web with perhaps a digital garden as well!Today, Ana Rodrigues (@anarodrigu.es @ohhelloana.blog) connected the dots from Sacha’s reminders to encouraging everyone to join burgeoning healthy online neighborhoods like:* 32-Bit Cafe (@32bit.cafe and see their Discord & Discourse)* IndieWeb Community (@indieweb.org and see @chat.indieweb.org for Discord, IRC, Slack)Both are filled with online neighbors helping and teaching each other how to make what people want to express on and for their personal sites!Know of other healthy online neighborhoods? Let me know and I’ll add them to the IndieWeb communities page!Want to connect your online home with online neighbors?* Join the IndieWeb #webring: https://indieweb.org/IndieWeb_WebringPrefer events? Join a virtual Frontend Study Hall, Homebrew Website Club meetup, or the next #IndieWebCamp!Glossary and links:btconf (Beyond Tellerrand conference) Berlin 2025 https://beyondtellerrand.com/events/berlin-2025communities (IndieWeb) https://indieweb.org/communitiesdigital gardens https://indieweb.org/digital_gardenhome (page) on the web https://indieweb.org/homepageHomebrew Website Club (HWC) online and in-person: https://events.indieweb.org/tag/hwcFront End Study Hall (FrESH) https://indieweb.org/freshIndieWebCamps - in-person and hybrid! https://events.indieweb.org/tag/indiewebcampThis is post 16 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2025/311/t1/indiewebcamp-berlin-sessions-demos→ 🔮
's status on Friday, 07-Nov-2025 11:09:00 EST
Great #indieweb sessions at #btconf #Berlin! Yesterday, Sacha Judd (@sachajudd.com) reminded us to “teach someone …. something about building for the web”, and to “take back control of your feeds, your attention, and … go exploring again”. She encouraged us to “build healthy online neighborhoods”. That’s a great metaphor and very complementary to rebuilding your own home(page) on the web with perhaps a digital garden as well! Today, Ana Rodrigues (@anarodrigu.es @ohhelloana.blog) connected the dots from Sacha’s reminders to encouraging everyone to join burgeoning healthy online neighborhoods like: * 32-Bit Cafe (@32bit.cafe and see their Discord & Discourse) * IndieWeb Community (@indieweb.org and see @chat.indieweb.org for Discord, IRC, Slack) Both are filled with online neighbors helping and teaching each other how to make what people want to express on and for their personal sites! Know of other healthy online neighborhoods? Let me know and I’ll add them to the IndieWeb communities page! Want to connect your online home with online neighbors? * Join the IndieWeb #webring: https://indieweb.org/IndieWeb_Webring Prefer events? Join a virtual Frontend Study Hall, Homebrew Website Club meetup, or the next #IndieWebCamp! Glossary and links: btconf (Beyond Tellerrand conference) Berlin 2025 https://beyondtellerrand.com/events/berlin-2025 communities (IndieWeb) https://indieweb.org/communities digital gardens https://indieweb.org/digital_garden home (page) on the web https://indieweb.org/homepage Homebrew Website Club (HWC) online and in-person: https://events.indieweb.org/tag/hwc Front End Study Hall (FrESH) https://indieweb.org/fresh IndieWebCamps - in-person and hybrid! https://events.indieweb.org/tag/indiewebcamp This is post 16 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2025/311/t1/indiewebcamp-berlin-sessions-demos → 🔮
: IndieWebCamp Berlin was great! Participants facilitated inspiring sessions, and everyone made something on or for their personal site on our Create Day #Hackathon.Session notes are up from day 1, recordings to follow:* https://indieweb.org/2025/Berlin/ScheduleDemos notes also up, recording to follow:* https://indieweb.org/2025/Berlin/DemosWant to keep up with #IndieWebCamp #Berlin participants? Volunteer Daniel has updated the IndieWebCamp Berlin feed:* https://indieweb.org/2025/Berlin#Feeds_Lists_Starter_Packs_Oh_MyQuestions about sessions or demos? Ask in #IndieWeb chat!* https://chat.indieweb.org/This is post 15 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2025/304/t1/night-before-indiewebcamp-berlin→ 🔮
's status on Friday, 07-Nov-2025 05:55:00 EST
IndieWebCamp Berlin was great! Participants facilitated inspiring sessions, and everyone made something on or for their personal site on our Create Day #Hackathon. Session notes are up from day 1, recordings to follow: * https://indieweb.org/2025/Berlin/Schedule Demos notes also up, recording to follow: * https://indieweb.org/2025/Berlin/Demos Want to keep up with #IndieWebCamp #Berlin participants? Volunteer Daniel has updated the IndieWebCamp Berlin feed: * https://indieweb.org/2025/Berlin#Feeds_Lists_Starter_Packs_Oh_My Questions about sessions or demos? Ask in #IndieWeb chat! * https://chat.indieweb.org/ This is post 15 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2025/304/t1/night-before-indiewebcamp-berlin → 🔮
: 🎃 Night before IndieWebCamp Berlin! Participants are (hopefully, mostly) all tucked into their beds, dreaming of what wonderful things they can brainstorm for their personal sites Saturday, and #HackTheirPlanet on Sunday.Want to keep up with #IndieWebCamp #Berlin participants?Follow their feeds and a Bluesky starter pack (happy to include more for any other formats, protocols, or platforms)* https://indieweb.org/2025/Berlin#Feeds_Lists_Starter_Packs_Oh_MyWe’ll add more as folks sign-in at the camp!This is post 14 of #100PostsOfIndieWeb. #100Posts #IndieWeb #Blogtober #IndieWebMovieClub #HackThePlanet 📟← https://tantek.com/2025/303/t1/october-blogging-challenges→ 🔮
's status on Friday, 31-Oct-2025 18:14:00 EDT
🎃 Night before IndieWebCamp Berlin! Participants are (hopefully, mostly) all tucked into their beds, dreaming of what wonderful things they can brainstorm for their personal sites Saturday, and #HackTheirPlanet on Sunday. Want to keep up with #IndieWebCamp #Berlin participants? Follow their feeds and a Bluesky starter pack (happy to include more for any other formats, protocols, or platforms) * https://indieweb.org/2025/Berlin#Feeds_Lists_Starter_Packs_Oh_My We’ll add more as folks sign-in at the camp! This is post 14 of #100PostsOfIndieWeb. #100Posts #IndieWeb #Blogtober #IndieWebMovieClub #HackThePlanet 📟 ← https://tantek.com/2025/303/t1/october-blogging-challenges → 🔮
: October is almost over! For all us procrastinators, still time to write a post or two to participate in #October blogging challenges like:#Blogtober#IndieWebMovieClub on #Hackers#Inktober#Mathober#WeirdWebOctober+ coding challenges:#Hacktoberfest — https://blog.holopin.io/posts/hacktoberfest-2025Many more at:* https://indieweb.org/October* https://indieweb.org/blog_carnival🎃 And tomorrow is #Halloween so consider a holiday theme for your site as well! See #IndieWeb examples for inspiration:* https://indieweb.org/HalloweenLast but not least, perhaps we’ll see some of you at #IndieWebCamp Berlin this weekend!* https://indieweb.org/2025/BerlinThis is post 13 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2025/182/t1/movie-club-tomorrowland-submissions→ 🔮
's status on Thursday, 30-Oct-2025 19:27:00 EDT
October is almost over! For all us procrastinators, still time to write a post or two to participate in #October blogging challenges like: #Blogtober #IndieWebMovieClub on #Hackers #Inktober #Mathober #WeirdWebOctober + coding challenges: #Hacktoberfest — https://blog.holopin.io/posts/hacktoberfest-2025 Many more at: * https://indieweb.org/October * https://indieweb.org/blog_carnival 🎃 And tomorrow is #Halloween so consider a holiday theme for your site as well! See #IndieWeb examples for inspiration: * https://indieweb.org/Halloween Last but not least, perhaps we’ll see some of you at #IndieWebCamp Berlin this weekend! * https://indieweb.org/2025/Berlin This is post 13 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2025/182/t1/movie-club-tomorrowland-submissions → 🔮
: I really enjoyed the IndieWeb Movie Club May 2025 submissions about the film “Tomorrowland”. Ordered from earliest to most recent:* Paolo Feadin: https://www.feadin.eu/en/posts/tomorrowland* Thomas Vander Wal: https://vanderwal.net/random/entrysel.php?blog=2119* gRegor Morrill: https://gregorlove.com/2025/05/tomorrowland/* Benji: https://www.benji.dog/watched/1748757918-tomorrowland-2015/* James: https://jamesg.blog/2025/07/01/tomorrowland-indieweb-movie-clubAs promised in my welcome post, here are my past posts regarding or related to Tomorrowland the film, Before Tomorrowland the book, and the themes and messages therein:* https://tantek.com/2016/042/t1/the-problem-to-solve-negative-news* https://tantek.com/2016/145/b1/tomorrowland-misjudging-by-name-association* https://tantek.com/2016/150/b1/tomorrowland-change-perspective-flight-paris* https://tantek.com/2016/279/t2/finished-reading-before-tomorrowlandI rewatched the film in May, and had a mix of remembering my past impressions as well as forming new impressions in the context of 2025. A lot has changed in the past 10 years. Worth a separate blog post. Previously: https://tantek.com/2025/120/t1/indieweb-movie-club-tomorrowland#TomorrowlandFilm #BeforeTomorrowland #IndieWeb #IndieWebMovieClubThis is post 12 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2025/120/t1/indieweb-movie-club-tomorrowland→ 🔮
's status on Tuesday, 01-Jul-2025 20:41:00 EDT
I really enjoyed the IndieWeb Movie Club May 2025 submissions about the film “Tomorrowland”. Ordered from earliest to most recent: * Paolo Feadin: https://www.feadin.eu/en/posts/tomorrowland * Thomas Vander Wal: https://vanderwal.net/random/entrysel.php?blog=2119 * gRegor Morrill: https://gregorlove.com/2025/05/tomorrowland/ * Benji: https://www.benji.dog/watched/1748757918-tomorrowland-2015/ * James: https://jamesg.blog/2025/07/01/tomorrowland-indieweb-movie-club As promised in my welcome post, here are my past posts regarding or related to Tomorrowland the film, Before Tomorrowland the book, and the themes and messages therein: * https://tantek.com/2016/042/t1/the-problem-to-solve-negative-news * https://tantek.com/2016/145/b1/tomorrowland-misjudging-by-name-association * https://tantek.com/2016/150/b1/tomorrowland-change-perspective-flight-paris * https://tantek.com/2016/279/t2/finished-reading-before-tomorrowland I rewatched the film in May, and had a mix of remembering my past impressions as well as forming new impressions in the context of 2025. A lot has changed in the past 10 years. Worth a separate blog post. Previously: https://tantek.com/2025/120/t1/indieweb-movie-club-tomorrowland #TomorrowlandFilm #BeforeTomorrowland #IndieWeb #IndieWebMovieClub This is post 12 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2025/120/t1/indieweb-movie-club-tomorrowland → 🔮
: 🎂 Congrats @microformats.org on 20 years! #microformats20Even after 20 years, people keep discovering new ways of using #microformats:* @artlung.com: "WML, WAP, & Microformats Demo!" (https://lab.artlung.com/wml/faux)> Because WML elements may have the class attributeOriginally posted 2025-06-18: https://xoxo.zone/@artlung/114705990062730513That adds to the list of languages with working microformats examples:* HTML — modern, unversioned as well as every version since HTML4* HTML3 — see https://microformats.org/wiki/html3* SVG — see https://microformats.org/wiki/svg* XHTML — every version, 1.0, 1.1, 2.0and now also:* WML — https://microformats.org/wiki/wmlLiterally any HTML-like or XML-like language that has a space-separated class attribute can work with microformats.In constrast, every alternative to microformats (most now defunct) required adding new attributes, or worse, entirely new elements, which meant revising every language one at a time (or use of fragile XML Namespaces), resulting in supporting only 1-2 languages at most (HTML and XHTML) in practice, and nothing else.Re-using the "class" attribute based on the existing footpath that web designers made for encoding additional semantics into their HTML, and the similarly extensible "rel" attribute, was one of the best design decisions in any extension format ever.After 20 years, microformats continue to serve as another example of “loosely joined” approaches being more adaptable, reliable, resilient, and longer lasting than “tightly coupled”.More microformats 20th anniversary posts from the #indieweb personal sites (via https://stream.indieweb.org/)* @manton.org: "It’s the 20th anniversary of the launch of microforrmats.org!" (https://www.manton.org/2025/06/20/its-the-th-anniversary-of.html)* ... hashtag your post #microformats or #microformats20 and #federate (using #Mastodon or any compatible #fediverse server etc.) or webmention this post!#20thAnniversary #smallPieces #looselyJoinedPreviously, previously, previously:* https://tantek.com/2024/173/t1/years-posse-microformats-beyond* https://tantek.com/2023/171/t1/anniversaries-microformats-posse* https://tantek.com/2019/171/t1/happy-14th-microformats-org
's status on Friday, 20-Jun-2025 20:48:00 EDT
🎂 Congrats @microformats.org on 20 years! #microformats20 Even after 20 years, people keep discovering new ways of using #microformats: * @artlung.com: "WML, WAP, & Microformats Demo!" (https://lab.artlung.com/wml/faux) > Because WML elements may have the class attribute Originally posted 2025-06-18: https://xoxo.zone/@artlung/114705990062730513 That adds to the list of languages with working microformats examples: * HTML — modern, unversioned as well as every version since HTML4 * HTML3 — see https://microformats.org/wiki/html3 * SVG — see https://microformats.org/wiki/svg * XHTML — every version, 1.0, 1.1, 2.0 and now also: * WML — https://microformats.org/wiki/wml Literally any HTML-like or XML-like language that has a space-separated class attribute can work with microformats. In constrast, every alternative to microformats (most now defunct) required adding new attributes, or worse, entirely new elements, which meant revising every language one at a time (or use of fragile XML Namespaces), resulting in supporting only 1-2 languages at most (HTML and XHTML) in practice, and nothing else. Re-using the "class" attribute based on the existing footpath that web designers made for encoding additional semantics into their HTML, and the similarly extensible "rel" attribute, was one of the best design decisions in any extension format ever. After 20 years, microformats continue to serve as another example of “loosely joined” approaches being more adaptable, reliable, resilient, and longer lasting than “tightly coupled”. More microformats 20th anniversary posts from the #indieweb personal sites (via https://stream.indieweb.org/) * @manton.org: "It’s the 20th anniversary of the launch of microforrmats.org!" (https://www.manton.org/2025/06/20/its-the-th-anniversary-of.html) * ... hashtag your post #microformats or #microformats20 and #federate (using #Mastodon or any compatible #fediverse server etc.) or webmention this post! #20thAnniversary #smallPieces #looselyJoined Previously, previously, previously: * https://tantek.com/2024/173/t1/years-posse-microformats-beyond * https://tantek.com/2023/171/t1/anniversaries-microformats-posse * https://tantek.com/2019/171/t1/happy-14th-microformats-org
: Deliberate use of entropy, randomness, even changing routines can provide a layer of defense for cybersecurity. More Steps for Cybersecurity Here are three more steps (in addition to Three Steps for IndieWeb Cybersecurity) that you can take to add obstacles to any would be attackers, and further secure your online presence. Different email address for each account, AKA email masking. Use or create a different email alias for each service you sign-up for. With a single email inbox, like any username at Gmail, you can often append a plus sign (+) and a brief random string. If you use your own #indieweb domain for email addresses, pick a different name at that domain for each service, with a bit of entropy like a short number. Lastly, another option is to use an email masking service — try a web search for that phrase for options to check out. Each of these works to limit or at least slow down an attacker, because even if they gain control of one email alias or account, any “forgot password” (AKA password reset or account reset, or sometimes called recovery) attempts with that same email on other services won’t work, since each service only knows about an email address unique to it. Different password for each account. This is a well known security technique against credential stuffing attacks. I.e. if someone retrieves your username and password from a data breach, or guesses them, or tricks (phishes) you into entering them for one service, they may try to “stuff” those “credentials” into other services. Using different passwords for all online services you use can thwart that attack. Note however that different passwords with the same email address will not stop an account reset attack, which is why this tip is second to email masking. Use a password manager to autofill. All modern browsers and many operating systems have built-in password managers, most of which also offer free sync services across devices. There is also third party password manager software and third party password manager services which are designed to work across devices, browsers, and operating systems. Regardless of which option you choose, always using a password manager to autofill your login username (or email) and password can be a very effective method of reducing the chances of being phished. Password managers will not autofill forms on fake phishing domains that are pretending to be a legitimate service. Password managers can also help with keeping track of unique email addresses and passwords for each service. Most will also auto-generate long and random (high entropy) passwords for you. I’ll close with a reminder that Perfect is the enemy of good. This post has been a draft for a while so I decided to publish it as a summary, rather than continuing to iterate on it. I’m sure others have written much longer posts. Similarly, even if you cannot take all these actions immediately everywhere, you can benefit by incrementally taking some of these steps on some accounts. Prioritize important accounts and take steps to increase their security. Previous post in this series: CSF_01: Three Steps for IndieWeb Cybersecurity Glossary Glossary for some terms, phrases, and further reading on each. credential stuffing https://en.wikipedia.org/wiki/Credential_stuffing data breach https://en.wikipedia.org/wiki/Data_breach entropy https://en.wikipedia.org/wiki/Entropy_(information_theory) password manager https://en.wikipedia.org/wiki/Password_manager phish, phished, phishes, phishing https://en.wikipedia.org/wiki/Phishing Syndicated to: IndieNews
's status on Friday, 02-May-2025 19:45:00 EDT
Deliberate use of entropy, randomness, even changing routines can provide a layer of defense for cybersecurity. More Steps for Cybersecurity Here are three more steps (in addition to Three Steps for IndieWeb Cybersecurity) that you can take to add obstacles to any would be attackers, and further secure your online presence. Different email address for each account, AKA email masking. Use or create a different email alias for each service you sign-up for. With a single email inbox, like any username at Gmail, you can often append a plus sign (+) and a brief random string. If you use your own #indieweb domain for email addresses, pick a different name at that domain for each service, with a bit of entropy like a short number. Lastly, another option is to use an email masking service — try a web search for that phrase for options to check out. Each of these works to limit or at least slow down an attacker, because even if they gain control of one email alias or account, any “forgot password” (AKA password reset or account reset, or sometimes called recovery) attempts with that same email on other services won’t work, since each service only knows about an email address unique to it. Different password for each account. This is a well known security technique against credential stuffing attacks. I.e. if someone retrieves your username and password from a data breach, or guesses them, or tricks (phishes) you into entering them for one service, they may try to “stuff” those “credentials” into other services. Using different passwords for all online services you use can thwart that attack. Note however that different passwords with the same email address will not stop an account reset attack, which is why this tip is second to email masking. Use a password manager to autofill. All modern browsers and many operating systems have built-in password managers, most of which also offer free sync services across devices. There is also third party password manager software and third party password manager services which are designed to work across devices, browsers, and operating systems. Regardless of which option you choose, always using a password manager to autofill your login username (or email) and password can be a very effective method of reducing the chances of being phished. Password managers will not autofill forms on fake phishing domains that are pretending to be a legitimate service. Password managers can also help with keeping track of unique email addresses and passwords for each service. Most will also auto-generate long and random (high entropy) passwords for you. I’ll close with a reminder that Perfect is the enemy of good. This post has been a draft for a while so I decided to publish it as a summary, rather than continuing to iterate on it. I’m sure others have written much longer posts. Similarly, even if you cannot take all these actions immediately everywhere, you can benefit by incrementally taking some of these steps on some accounts. Prioritize important accounts and take steps to increase their security. Previous post in this series: CSF_01: Three Steps for IndieWeb Cybersecurity Glossary Glossary for some terms, phrases, and further reading on each. credential stuffing https://en.wikipedia.org/wiki/Credential_stuffing data breach https://en.wikipedia.org/wiki/Data_breach entropy https://en.wikipedia.org/wiki/Entropy_(information_theory) password manager https://en.wikipedia.org/wiki/Password_manager phish, phished, phishes, phishing https://en.wikipedia.org/wiki/Phishing Syndicated to: IndieNews
: Welcome to the May 2025 edition of IndieWeb Movie Club!As your host for this month¹, I invite you to (re)watch the film “Tomorrowland” (https://movies.disney.com/tomorrowland), with an optional prequel book reading assignment!“Before Tomorrowland” (https://books.disney.com/book/before-tomorrowland/) was released about a month before the film, so it’s fine to read before watching.#Tomorrowland is available in various physical media formats, and via streaming on DisneyPlus². 130 minutes, rated PG.This month is the 10th anniversary of Tomorrowland’s release.The world was quite different in 2015.I had my own impressions of Tomorrowland when I first heard about it and then watched it much later (which I won’t link to yet to avoid spoilers or biasing your opinions). The film made such a strong impression on me that I held a group film viewing and discussion party in 2015!I’m curious how both first time viewers in 2025 and folks watching a second (or more) time think of Tomorrowland.If you would like to participate in this month’s IndieWeb Movie Club:* optional: read the prequel book* watch the film* blog a read³ (for the book), watch⁴, review⁵, or even a simple note⁶ post of your impressions, or some or all the above and link to this postIf you want your post(s) to be included in the May 2025 IndieWeb Movie Club roundup, notify me with a Webmention⁷ from your post, or drop a link in the IndieWeb chat discussion channel⁸ and @-mention me.Since this is an IndieWeb community activity, please both follow the Code of Conduct⁹, and also keep your post within the same rating (PG) as the movie. I may curate the roundup accordingly.Happy reading, watching, and dreaming!#TomorrowlandFilm #BeforeTomorrowland #IndieWeb #IndieWebMovieClubThis is post 11 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2025/077/t1/what-are-words-for-blogging→ 🔮References:¹ https://indieweb.org/IndieWeb_Movie_Club#2025² https://www.disneyplus.com/en-gb/browse/entity-3355a91d-addb-4c66-91a6-136325e6ecf7³ https://indieweb.org/read⁴ https://indieweb.org/watch⁵ https://indieweb.org/review⁶ https://indieweb.org/note⁷ https://indieweb.org/Webmention⁸ https://indieweb.org/discuss#indieweb⁹ https://indieweb.org/code-of-conduct
's status on Wednesday, 30-Apr-2025 21:03:00 EDT
Welcome to the May 2025 edition of IndieWeb Movie Club! As your host for this month¹, I invite you to (re)watch the film “Tomorrowland” (https://movies.disney.com/tomorrowland), with an optional prequel book reading assignment! “Before Tomorrowland” (https://books.disney.com/book/before-tomorrowland/) was released about a month before the film, so it’s fine to read before watching. #Tomorrowland is available in various physical media formats, and via streaming on DisneyPlus². 130 minutes, rated PG. This month is the 10th anniversary of Tomorrowland’s release. The world was quite different in 2015. I had my own impressions of Tomorrowland when I first heard about it and then watched it much later (which I won’t link to yet to avoid spoilers or biasing your opinions). The film made such a strong impression on me that I held a group film viewing and discussion party in 2015! I’m curious how both first time viewers in 2025 and folks watching a second (or more) time think of Tomorrowland. If you would like to participate in this month’s IndieWeb Movie Club: * optional: read the prequel book * watch the film * blog a read³ (for the book), watch⁴, review⁵, or even a simple note⁶ post of your impressions, or some or all the above and link to this post If you want your post(s) to be included in the May 2025 IndieWeb Movie Club roundup, notify me with a Webmention⁷ from your post, or drop a link in the IndieWeb chat discussion channel⁸ and @-mention me. Since this is an IndieWeb community activity, please both follow the Code of Conduct⁹, and also keep your post within the same rating (PG) as the movie. I may curate the roundup accordingly. Happy reading, watching, and dreaming! #TomorrowlandFilm #BeforeTomorrowland #IndieWeb #IndieWebMovieClub This is post 11 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2025/077/t1/what-are-words-for-blogging → 🔮 References: ¹ https://indieweb.org/IndieWeb_Movie_Club#2025 ² https://www.disneyplus.com/en-gb/browse/entity-3355a91d-addb-4c66-91a6-136325e6ecf7 ³ https://indieweb.org/read ⁴ https://indieweb.org/watch ⁵ https://indieweb.org/review ⁶ https://indieweb.org/note ⁷ https://indieweb.org/Webmention ⁸ https://indieweb.org/discuss#indieweb ⁹ https://indieweb.org/code-of-conduct
: “Tell me, what are words for?” They are for blogging!Earlier today during an informal espresso live stream in the #indieweb cafe, Spotify was playing an auto-generated daylist, something like “romantic 80s tuesday morning”, and the 1982 song “Words”¹ by the band Missing Persons came on.When we heard this lyric:🎶 What are words for when no one listens? 🎶I remarked half-jokingly in response:Words are for blogging, whether anyone is listening, reading, or not.Another participant noted that blogging sometimes feels like screaming into the void.I noted it doesn’t matter if anyone is reading (or listening), it’s fine to blog for an audience of one, yourself, even just to have something to refer to or reference in the future.When I write a post it’s often directed at only a small number of people, who may be part of a larger conversation. The point of publishing it publicly is to assert a level of confidence and credibility by the act of “putting it on the permanent record” (since nearly everything blogged is promptly indexed and archived.) with a permalink.The lyrics have some quite prescient bits, like this:“No one notices, I think I'll dye my hair blue Media overload bombarding you with action It’s getting near impossible to cause distraction”Written and sung more than forty years ago. Long before the web (or #socialWeb) was a thing.Rewriting the lyrics as a parody could be a fun project, e.g.:🎶 What are blogs for when no one reads them? 🎶some existing lyrics barely need any edits, like:“It’s like the feeling at the end of the page When you realize you don't know what you just read”perhaps an exercise for the reader for now.Previously: “Inbox Zero” (parody of The Fixx “Saved by Zero”²)* https://tantek.com/w/InboxZero (2009-01-29 https://twitter.com/t/status/1160324190)This is post 10 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2025/055/t1/three-steps-indieweb-cybersecurity→ 🔮Glossaryblog https://indieweb.org/blogblogging https://indieweb.org/bloggingpermalink https://indieweb.org/permalinkwhy blog https://indieweb.org/why_postReferences¹ https://libre.fm/artist/Missing+Persons/track/Words (YouTube link inside)² https://libre.fm/artist/The+Fixx/track/Saved+by+Zero (YouTube link inside)
's status on Tuesday, 18-Mar-2025 21:25:00 EDT
“Tell me, what are words for?” They are for blogging! Earlier today during an informal espresso live stream in the #indieweb cafe, Spotify was playing an auto-generated daylist, something like “romantic 80s tuesday morning”, and the 1982 song “Words”¹ by the band Missing Persons came on. When we heard this lyric: 🎶 What are words for when no one listens? 🎶 I remarked half-jokingly in response: Words are for blogging, whether anyone is listening, reading, or not. Another participant noted that blogging sometimes feels like screaming into the void. I noted it doesn’t matter if anyone is reading (or listening), it’s fine to blog for an audience of one, yourself, even just to have something to refer to or reference in the future. When I write a post it’s often directed at only a small number of people, who may be part of a larger conversation. The point of publishing it publicly is to assert a level of confidence and credibility by the act of “putting it on the permanent record” (since nearly everything blogged is promptly indexed and archived.) with a permalink. The lyrics have some quite prescient bits, like this: “No one notices, I think I'll dye my hair blue Media overload bombarding you with action It’s getting near impossible to cause distraction” Written and sung more than forty years ago. Long before the web (or #socialWeb) was a thing. Rewriting the lyrics as a parody could be a fun project, e.g.: 🎶 What are blogs for when no one reads them? 🎶 some existing lyrics barely need any edits, like: “It’s like the feeling at the end of the page When you realize you don't know what you just read” perhaps an exercise for the reader for now. Previously: “Inbox Zero” (parody of The Fixx “Saved by Zero”²) * https://tantek.com/w/InboxZero (2009-01-29 https://twitter.com/t/status/1160324190) This is post 10 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2025/055/t1/three-steps-indieweb-cybersecurity → 🔮 Glossary blog https://indieweb.org/blog blogging https://indieweb.org/blogging permalink https://indieweb.org/permalink why blog https://indieweb.org/why_post References ¹ https://libre.fm/artist/Missing+Persons/track/Words (YouTube link inside) ² https://libre.fm/artist/The+Fixx/track/Saved+by+Zero (YouTube link inside)
: Last week I published my first Cybersecurity Friday post with three key steps for indieweb cybersecurity. In summary:1. Email MFA/2FA. Add multi-factor authentication (sometimes called two-factor authentication) to everywhere you store or check email. Do not use phone/cell numbers.2. Domain Registrar MFA. Add multi-factor authentication to your domain registrar account.3. Web Host MFA. Same for your web host and any intermediate name servers (DNS) or content delivery network (CDN) service accounts.Full post: https://tantek.com/2025/052/b1/steps-indieweb-cybersecurityNext time: entropy is your friend in security.If you want my #Cybersecurity Friday posts as soon as I publish them, follow my site https://tantek.com/ directly in your reader rather than using #socialMedia or #Mastodon or some other notes-centric #fediverse client.You can subscribe to my site directly with an h-feed supporting #indieweb Social Reader, or if you use a classic feed reader, it can auto-discover my Atom feed from my home page.You can also read my article blog posts and those from other Mozillians on the Mozilla Planet:* https://planet.mozilla.org/If you look closely you might even find my not-so-secret articles-only Atom feed linked there if you prefer.This is post 9 of #100PostsOfIndieWeb. #100Posts #cyber #security← https://tantek.com/2025/020/t1/seek-2024-year-in-review→ 🔮Glossaryarticle post https://indieweb.org/articleAtom https://indieweb.org/Atomcontent delivery network https://indieweb.org/content_delivery_networkcybersecurity https://en.wikipedia.org/wiki/cybersecurityDNS https://indieweb.org/DNSdomain registrar https://indieweb.org/domain_registrarentropy https://en.wikipedia.org/wiki/Entropy_(information_theory)feed reader https://indieweb.org/feed_readerh-feed https://indieweb.org/h-feedMFA / 2FA https://indieweb.org/multi-factor_authentication sometimes called Two Factor Authentication or Second Factor Authenticationmobile number for MFA https://indieweb.org/SMS#Criticismnote post https://indieweb.org/notesocial reader https://indieweb.org/social_readerweb host https://indieweb.org/web_hosting
's status on Monday, 24-Feb-2025 19:10:00 EST
Last week I published my first Cybersecurity Friday post with three key steps for indieweb cybersecurity. In summary: 1. Email MFA/2FA. Add multi-factor authentication (sometimes called two-factor authentication) to everywhere you store or check email. Do not use phone/cell numbers. 2. Domain Registrar MFA. Add multi-factor authentication to your domain registrar account. 3. Web Host MFA. Same for your web host and any intermediate name servers (DNS) or content delivery network (CDN) service accounts. Full post: https://tantek.com/2025/052/b1/steps-indieweb-cybersecurity Next time: entropy is your friend in security. If you want my #Cybersecurity Friday posts as soon as I publish them, follow my site https://tantek.com/ directly in your reader rather than using #socialMedia or #Mastodon or some other notes-centric #fediverse client. You can subscribe to my site directly with an h-feed supporting #indieweb Social Reader, or if you use a classic feed reader, it can auto-discover my Atom feed from my home page. You can also read my article blog posts and those from other Mozillians on the Mozilla Planet: * https://planet.mozilla.org/ If you look closely you might even find my not-so-secret articles-only Atom feed linked there if you prefer. This is post 9 of #100PostsOfIndieWeb. #100Posts #cyber #security ← https://tantek.com/2025/020/t1/seek-2024-year-in-review → 🔮 Glossary article post https://indieweb.org/article Atom https://indieweb.org/Atom content delivery network https://indieweb.org/content_delivery_network cybersecurity https://en.wikipedia.org/wiki/cybersecurity DNS https://indieweb.org/DNS domain registrar https://indieweb.org/domain_registrar entropy https://en.wikipedia.org/wiki/Entropy_(information_theory) feed reader https://indieweb.org/feed_reader h-feed https://indieweb.org/h-feed MFA / 2FA https://indieweb.org/multi-factor_authentication sometimes called Two Factor Authentication or Second Factor Authentication mobile number for MFA https://indieweb.org/SMS#Criticism note post https://indieweb.org/note social reader https://indieweb.org/social_reader web host https://indieweb.org/web_hosting
: My Seek 2024 Year in Review:* 141 new species observed, of those, the top three kinds: * 79 plants * 20 insects * 16 fungi* 56 challenge badges earnedJune was the month I observed the most new species in 2024, followed by March, and then July.Seek also gave me a graph of observations per month, and also a map of where I made my discoveries.Rather than posting screenshots of the Year in Review that Seek provided me in the app, I am posting the relevant content here in a post on my personal site, which I know I’ll be able to search and look up in the future.Seek is a delightful free (like actually free, free of tracking, free of surveillance) native mobile application for identifying species.Made by the iNaturalist folks (https://www.inaturalist.org/pages/seek_app), Seek works without creating an account, and is able to work completely offline to identify species out in the wild (and add them to your local collection).Seek awards you Species Badges when you discover a number of species of a particular grouping, as well as Challenge Badges when you complete one or more of their monthly challenges that they post.In some ways it’s like Pokemon Go, except based on finding and collecting observations of real living things.I have found it quite useful especially when traveling, and wondering is that plant (or animal) the same as one I’ve seen elsewhere, perhaps around home, or is it a slightly different species?I also really like the good example that Seek provides for how an app can be immediately useful without requiring extra labor (like creating an account, or logging on) on behalf of the person using it.Lastly, Seek is an excellent example of a truly offline capable app where nearly all of its functionality works just fine without a network connection.Both of these capabilities (offline first, no login wall) are what we should aspire to when we build #indieweb apps or websites for ourselves and our friends.This is post 8 of #100PostsOfIndieWeb. #100Posts #yearInReview #iNaturalist #SeekApp← https://tantek.com/2025/012/t1/eight-years-webmention→ 🔮Glossary:login wall https://indieweb.org/login_walloffline first https://indieweb.org/offline_first
's status on Monday, 20-Jan-2025 17:04:00 EST
My Seek 2024 Year in Review: * 141 new species observed, of those, the top three kinds: * 79 plants * 20 insects * 16 fungi * 56 challenge badges earned June was the month I observed the most new species in 2024, followed by March, and then July. Seek also gave me a graph of observations per month, and also a map of where I made my discoveries. Rather than posting screenshots of the Year in Review that Seek provided me in the app, I am posting the relevant content here in a post on my personal site, which I know I’ll be able to search and look up in the future. Seek is a delightful free (like actually free, free of tracking, free of surveillance) native mobile application for identifying species. Made by the iNaturalist folks (https://www.inaturalist.org/pages/seek_app), Seek works without creating an account, and is able to work completely offline to identify species out in the wild (and add them to your local collection). Seek awards you Species Badges when you discover a number of species of a particular grouping, as well as Challenge Badges when you complete one or more of their monthly challenges that they post. In some ways it’s like Pokemon Go, except based on finding and collecting observations of real living things. I have found it quite useful especially when traveling, and wondering is that plant (or animal) the same as one I’ve seen elsewhere, perhaps around home, or is it a slightly different species? I also really like the good example that Seek provides for how an app can be immediately useful without requiring extra labor (like creating an account, or logging on) on behalf of the person using it. Lastly, Seek is an excellent example of a truly offline capable app where nearly all of its functionality works just fine without a network connection. Both of these capabilities (offline first, no login wall) are what we should aspire to when we build #indieweb apps or websites for ourselves and our friends. This is post 8 of #100PostsOfIndieWeb. #100Posts #yearInReview #iNaturalist #SeekApp ← https://tantek.com/2025/012/t1/eight-years-webmention → 🔮 Glossary: login wall https://indieweb.org/login_wall offline first https://indieweb.org/offline_first
: 🎉 Eight years ago today, the #IndieWeb Webmention protocol was published as a W3C REC https://www.w3.org/TR/webmention/As a social web building block, #Webmention was designed to work with various other building blocks. Small pieces, loosely joined. Every year developers find new ways to work with Webmention, and new subtleties when combined with other building blocks.The primary uses of Webmention, peer-to-peer comments, likes, and other responses across web sites, has long presented an interesting challenge with the incorporation and display of external content originally from one site (the Webmention sender), on another site (the Webmention receiver).There are multiple considerations to keep in mind when displaying such external content.Two examples of external content are images (e.g. people’s icons or profile images from the author of a comment) and text (e.g. people’s names or the text of their comments).For external images, rather than displaying them in full fidelity, you may want to compress them into a smaller resolution for how your site displays the profile images of comment authors.If you accept Webmentions from arbitrary sources, there’s no telling what might show up in author images. You may want to pixelate images from unknown or novel sources into say 3x3 pixel grids of color (or grayscale) averages to make them uniquely identifiable while blurring any undesirable graphics beyond recognition.For external text, one thing we discovered in recent IndieWeb chat¹ is that someone’s comment (or in this case their name) can contain Unicode directional formatting characters, e.g. for displaying an Arabic or Hebrew name right-to-left. Text with such formatting characters can errantly impact the direction of adjacent text adjacent.Fortunately there is a CSS property, 'unicode-bidi', that can be used to isolate such external text. Thus when you embed text that was parsed from a received Webmention, possibly with formatting characters, you have to wrap it in an HTML element (a span will do if you have not already wrapped it) with that CSS property. E.g.:parsed text hereThough even better would be use of a generic HTML class name indicating the semantic:parsed text hereand then a CSS rule in your style sheet to add that property (and any others you want for external text).external-text { unicode-bidi: isolate; }This is post 7 of #100PostsOfIndieWeb. #100Posts #socialWeb #openSocialWeb← https://tantek.com/2025/004/t1/micro-one-onramp-open-social-web→ 🔮GlossaryHTML class name https://tantek.com/2012/353/b1/why-html-classes-css-class-selectorsIndieWeb chat https://indieweb.org/discusspixelate https://indieweb.org/pixelatedsmall pieces, loosely joined https://www.smallpieces.com/Unicode directional formatting characters https://en.wikipedia.org/wiki/Bidirectional_text#Explicit_formattingunicode-bidi CSS property https://developer.mozilla.org/en-US/docs/Web/CSS/unicode-bidi References¹ https://chat.indieweb.org/dev/2025-01-05#t1736092889120900
's status on Monday, 13-Jan-2025 00:23:00 EST
🎉 Eight years ago today, the #IndieWeb Webmention protocol was published as a W3C REC https://www.w3.org/TR/webmention/ As a social web building block, #Webmention was designed to work with various other building blocks. Small pieces, loosely joined. Every year developers find new ways to work with Webmention, and new subtleties when combined with other building blocks. The primary uses of Webmention, peer-to-peer comments, likes, and other responses across web sites, has long presented an interesting challenge with the incorporation and display of external content originally from one site (the Webmention sender), on another site (the Webmention receiver). There are multiple considerations to keep in mind when displaying such external content. Two examples of external content are images (e.g. people’s icons or profile images from the author of a comment) and text (e.g. people’s names or the text of their comments). For external images, rather than displaying them in full fidelity, you may want to compress them into a smaller resolution for how your site displays the profile images of comment authors. If you accept Webmentions from arbitrary sources, there’s no telling what might show up in author images. You may want to pixelate images from unknown or novel sources into say 3x3 pixel grids of color (or grayscale) averages to make them uniquely identifiable while blurring any undesirable graphics beyond recognition. For external text, one thing we discovered in recent IndieWeb chat¹ is that someone’s comment (or in this case their name) can contain Unicode directional formatting characters, e.g. for displaying an Arabic or Hebrew name right-to-left. Text with such formatting characters can errantly impact the direction of adjacent text adjacent. Fortunately there is a CSS property, 'unicode-bidi', that can be used to isolate such external text. Thus when you embed text that was parsed from a received Webmention, possibly with formatting characters, you have to wrap it in an HTML element (a span will do if you have not already wrapped it) with that CSS property. E.g.: parsed text here Though even better would be use of a generic HTML class name indicating the semantic: parsed text here and then a CSS rule in your style sheet to add that property (and any others you want for external text) .external-text { unicode-bidi: isolate; } This is post 7 of #100PostsOfIndieWeb. #100Posts #socialWeb #openSocialWeb ← https://tantek.com/2025/004/t1/micro-one-onramp-open-social-web → 🔮 Glossary HTML class name https://tantek.com/2012/353/b1/why-html-classes-css-class-selectors IndieWeb chat https://indieweb.org/discuss pixelate https://indieweb.org/pixelated small pieces, loosely joined https://www.smallpieces.com/ Unicode directional formatting characters https://en.wikipedia.org/wiki/Bidirectional_text#Explicit_formatting unicode-bidi CSS property https://developer.mozilla.org/en-US/docs/Web/CSS/unicode-bidi References ¹ https://chat.indieweb.org/dev/2025-01-05#t1736092889120900
: The team @micro.blog have done it again.They soft-launched https://micro.one yesterday¹.This may be the most accessible onramp to the open social web ever.Cost: $1 a month. Yes you read correctly.This is the simplest and cheapest (where you are the customer, not the product) way to own your identity and content online².Stop posting in someone else’s garage³.Time to export your Twitter, and migrate your Mastodon handle to your own home on the web.Of course you can bring your own domain name. Additionally:* blog posts, naturally, both articles and microblogging notes* photos* podcasting* custom themes* web-clients and native mobile posting clients* WordPress, Tumblr, Mastodon, Medium importMore details (and alternatives) at https://micro.one/about/pricingAnd yes, it interoperates with the open #socialWeb, including:* #ActivityPub support, #Mastodon and #fediverse compatibility* #IndieAuth to sign-in to third-party apps* #microformats support in all built-in themes* #Webmention for sending and receiving replies across websites* #Micropub standard posting API, supporting dozens of clients* #Microsub standard timeline API, supporting social readersMore #indieweb support details at https://micro.one/about/indiewebDid I mention the the superb micro.blog (and micro.one) Community Guidelines?* https://help.micro.blog/t/community-guidelines/39Well done @manton.org and team.This is post 6 of #100PostsOfIndieWeb. #100Posts #ownYourIdentity #ownYourData #openSocialWeb← https://tantek.com/2025/003/t1/lastfm-year-in-review-playback24→ 🔮GlossaryIndieAuth https://indieweb.org/IndieAuthmicroformats https://microformats.org/wiki/microformatsMicropub https://indieweb.org/MicropubMicrosub https://indieweb.org/MicrosubWebmention https://indieweb.org/Webmention¹ https://www.manton.org/2025/01/03/microone-was-effectively-a-softlaunch.html² https://tantek.com/2025/001/t1/15-years-notes-my-site-first³ https://tantek.com/2023/022/t2/own-your-notes-domain-migration
's status on Saturday, 04-Jan-2025 23:48:00 EST
The team @micro.blog have done it again. They soft-launched https://micro.one yesterday¹. This may be the most accessible onramp to the open social web ever. Cost: $1 a month. Yes you read correctly. This is the simplest and cheapest (where you are the customer, not the product) way to own your identity and content online². Stop posting in someone else’s garage³. Time to export your Twitter, and migrate your Mastodon handle to your own home on the web. Of course you can bring your own domain name. Additionally: * blog posts, naturally, both articles and microblogging notes * photos * podcasting * custom themes * web-clients and native mobile posting clients * WordPress, Tumblr, Mastodon, Medium import More details (and alternatives) at https://micro.one/about/pricing And yes, it interoperates with the open #socialWeb, including: * #ActivityPub support, #Mastodon and #fediverse compatibility * #IndieAuth to sign-in to third-party apps * #microformats support in all built-in themes * #Webmention for sending and receiving replies across websites * #Micropub standard posting API, supporting dozens of clients * #Microsub standard timeline API, supporting social readers More #indieweb support details at https://micro.one/about/indieweb Did I mention the the superb micro.blog (and micro.one) Community Guidelines? * https://help.micro.blog/t/community-guidelines/39 Well done @manton.org and team. This is post 6 of #100PostsOfIndieWeb. #100Posts #ownYourIdentity #ownYourData #openSocialWeb ← https://tantek.com/2025/003/t1/lastfm-year-in-review-playback24 → 🔮 Glossary IndieAuth https://indieweb.org/IndieAuth microformats https://microformats.org/wiki/microformats Micropub https://indieweb.org/Micropub Microsub https://indieweb.org/Microsub Webmention https://indieweb.org/Webmention ¹ https://www.manton.org/2025/01/03/microone-was-effectively-a-softlaunch.html ² https://tantek.com/2025/001/t1/15-years-notes-my-site-first ³ https://tantek.com/2023/022/t2/own-your-notes-domain-migration
: Yesterday https://last.fm/ (@lastfm) emailed their year in review reports, which they called #Playback24 and Last.Year.Kudos to them for waiting until the new year to do so, and breaking with the pattern of services prematurely posting year in review summaries.¹They’re also available on the web, without requiring a native mobile app to view.Mine is here: https://www.last.fm/user/tantekc/listening-report/yearYou can find yours (if you’re a last.fm user) by going here:* https://www.last.fm/user/_/listening-report/yearThe page title calls it your #YearInMusic, and the URL your #ListeningReport.It has many interesting elements, from various top listened lists (artist, album, track), to what percent of 2024 listens (which they call scrobbles) were new artists, albums, and tracks.Their “Top Tags” time chart is quite cool. Fascinating to see the differences in music listening over the seasons and the whole year.The report has many interactive features, so it will take me some time to figure out how to save, export, and/or republish my listening report on my personal #indieweb site.For now I used Firefox to save the page as an .html page to my laptop, and was quite impressed with how much of the information was available in that one file. Much more than #Spotify’s #Wrapped. That’s step 1. Step 2 is figuring out a good way to blog at least some of it.This is post 5 of #100PostsOfIndieWeb. #100Posts #LastFM #YearInReview← https://tantek.com/2025/002/t1/indieweb-third-place-community→ 🔮Glossary:scrobble https://indieweb.org/scrobbleyear in review https://indieweb.org/year_in_review¹ https://tantek.com/2025/001/t2/first-new-year-review-prior
's status on Saturday, 04-Jan-2025 01:00:00 EST
Yesterday https://last.fm/ (@lastfm) emailed their year in review reports, which they called #Playback24 and Last.Year. Kudos to them for waiting until the new year to do so, and breaking with the pattern of services prematurely posting year in review summaries.¹ They’re also available on the web, without requiring a native mobile app to view. Mine is here: https://www.last.fm/user/tantekc/listening-report/year You can find yours (if you’re a last.fm user) by going here: * https://www.last.fm/user/_/listening-report/year The page title calls it your #YearInMusic, and the URL your #ListeningReport. It has many interesting elements, from various top listened lists (artist, album, track), to what percent of 2024 listens (which they call scrobbles) were new artists, albums, and tracks. Their “Top Tags” time chart is quite cool. Fascinating to see the differences in music listening over the seasons and the whole year. The report has many interactive features, so it will take me some time to figure out how to save, export, and/or republish my listening report on my personal #indieweb site. For now I used Firefox to save the page as an .html page to my laptop, and was quite impressed with how much of the information was available in that one file. Much more than #Spotify’s #Wrapped. That’s step 1. Step 2 is figuring out a good way to blog at least some of it. This is post 5 of #100PostsOfIndieWeb. #100Posts #LastFM #YearInReview ← https://tantek.com/2025/002/t1/indieweb-third-place-community → 🔮 Glossary: scrobble https://indieweb.org/scrobble year in review https://indieweb.org/year_in_review ¹ https://tantek.com/2025/001/t2/first-new-year-review-prior
: The #indieweb is more than #independence. It’s also a web, of both personal sites and “third place” sites like aggregators, bridges, proxies, directories, indexes, and other community sites.Broadly speaking, such “third place” sites include places we collectively contribute to, and which license our contributions for free use by others. While open source projects come to mind, perhaps a more obvious example is Wikipedia.Similarly, the most obvious “third place” in the #IndieWeb community is our community site and wiki https://indieweb.org/ as well as the heterogeneous chat https://chat.indieweb.org/.We also have many services run by individuals (or small teams) in the community, for the benefit of the community, like:* @snarfed.org’s https://brid.gy/ and https://fed.brid.gy/* @aaronparecki.com’s https://webmention.io/ and many others* @martymcgui.re’s https://xn--sr8hvo.ws/ (IndieWeb Webring)* @gregorlove.com’s https://indiebookclub.biz/* @mat.tl’s https://libre.fm/and I’m sure many more I’m forgetting.All these services respect your data and your ownership of it. #ownYourDataAll these services are swappable. Many (most?) are open source and self-hostable in case you want to run your own personal instance or another shared instance.The web part of the indieweb complements, connects, and strengthens the indie part.This is post 4 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2025/001/t3/strava-year-in-sport-how-to-get-info-save→ 🔮
's status on Friday, 03-Jan-2025 02:54:00 EST
The #indieweb is more than #independence. It’s also a web, of both personal sites and “third place” sites like aggregators, bridges, proxies, directories, indexes, and other community sites. Broadly speaking, such “third place” sites include places we collectively contribute to, and which license our contributions for free use by others. While open source projects come to mind, perhaps a more obvious example is Wikipedia. Similarly, the most obvious “third place” in the #IndieWeb community is our community site and wiki https://indieweb.org/ as well as the heterogeneous chat https://chat.indieweb.org/. We also have many services run by individuals (or small teams) in the community, for the benefit of the community, like: * @snarfed.org’s https://brid.gy/ and https://fed.brid.gy/ * @aaronparecki.com’s https://webmention.io/ and many others * @martymcgui.re’s https://xn--sr8hvo.ws/ (IndieWeb Webring) * @gregorlove.com’s https://indiebookclub.biz/ * @mat.tl’s https://libre.fm/ and I’m sure many more I’m forgetting. All these services respect your data and your ownership of it. #ownYourData All these services are swappable. Many (most?) are open source and self-hostable in case you want to run your own personal instance or another shared instance. The web part of the indieweb complements, connects, and strengthens the indie part. This is post 4 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2025/001/t3/strava-year-in-sport-how-to-get-info-save → 🔮
: When we say #ownYourData we mean whatever data is important to you, like the data services aggregate about you and present back to you. Owning that data means extracting it into a form you can hang onto regardless of what the service does in the future (or disappears), and publishing whatever aspects of it you wish to, on your personal #indieweb site.Speaking of year in reviews¹ and #Strava Year in Sport in particular, here are my brief notes for how to get the info from it (before it disappears after the 6th!²) and save it locally so you can write and publish your own year in sport.How to find your Strava: Year in Sport 2024 For 2024, the Strava Year in Sport 2024 is only available on the native mobile app (iOS and presumably Android) and not accessible via the website. Prior years which were available on the website e.g. 2018(.)strava(.)com and 2017(.)strava(.)com are long gone.From the mobile app home screen, tap the "📋 You" button in the lower right corner.At the top you should see:"Play back your 2024" heading with an orange button:[ See your Year in Sport ]Tap that button.Saving Seven Summary SegmentsYou should immediately see an animation start playing, with seven "segments" (like Instagram stories) at the top, gradually filling-in as progress indicators one at a time. For each "segment" if you press the screenshot combination of buttons on your mobile (e.g. volume-up + power on iPhone 14), in addition to taking a screenshot it will put you in a "share" screen with one or more videos or still images to share in a carousel format. For each item in the carousel (if there is more than one)* tap the item in the carousel* tap the "[↑] More" button at the bottom.* scroll down the list of options up a bit* tap "Save Video [↓]" or "Save Image [↓]" option to store it locally on your mobile.The seventh "segment" is your overall summary, and shows all your sports combined.Save it (as an image as noted above), then* tap the "✏️ Customize" button* choose an individual sport (e.g. "👟 Run")* tap "Save changes"* save that image (as above)* tap customize again* choose the next sport (e.g. "🚲 Ride")* save changes again* save image againStrava seemingly only reports summaries of (up to?) two or your sports it appears. Those were Run (presumably all running, street and trail) and Ride for me.Cleanup Your ScreenshotsAfter having saved all the videos/images for each "segment", you can:* go back to your mobile’s top level Photos app/stream* delete the screenshotsYou should see all the videos/images you've saved. If anything is missing, go back to the previous steps and save them again, then remove any duplicates as necessary.Post Your Year In SportGo through your saved videos/images, and either post on your own site as-is, or use your mobile’s built-in image OCR to copy the text bits into a plain personal year in sport note summary post on your own site. Or some combination of both if you prefer.Add other summaries of your activities and sports as you see fit, like:* info on other sports (beyond running and biking), e.g. yoga, weight-lifting, bouldering etc. * total days active (of 366) * total distance (if applicable) * total elevation (if applicable) * total time* number of races you ran, biked etc. (and finished, if not the same)* number of miles (or km) you raced (per sport and/or total overall)* number of (or full set of) awards or trophies you earned at races* any other stats that you think of that seem interesting to youFor each of these annual numbers, you could also compute (optionally display) the percentage change from 2023, if you happen to have those numbers around.This is also a good reason to at least total up these numbers for 2024, whether you publish them or not, for figuring out the percentage change in 2025 next year.When you publish your own year in sport post, might as well re-use the existing #YearInSport hashtag too.I have already saved all the videos/images from my own Strava Year In Sport, and as I assemble the pieces into my own post, I’ll take more notes, and add to the IndieWeb year in review page³ accordingly.This post could also be improved with a few screenshots for a few of the steps above. I figured I’d publish my notes first to hopefully help some people sooner (since the Strava Year In Sport will disappear after January 6th as mentioned!). I might upload a few screenshots to the IndieWeb wiki later as well.#yearInReview #ownYourYearInReviewThis is post 3 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2025/001/t2/first-new-year-review-prior→ 🔮Glossary: hashtag https://indieweb.org/hashtagown your data https://indieweb.org/own_your_data¹ https://tantek.com/2025/001/t2/first-new-year-review-prior² https://support.strava.com/hc/en-us/articles/22067973274509-Your-Year-in-Sport#h_01HH5VW132BPDTEZJZDHBGJ6KM³ https://indieweb.org/year_in_review
's status on Wednesday, 01-Jan-2025 20:04:00 EST
When we say #ownYourData we mean whatever data is important to you, like the data services aggregate about you and present back to you. Owning that data means extracting it into a form you can hang onto regardless of what the service does in the future (or disappears), and publishing whatever aspects of it you wish to, on your personal #indieweb site. Speaking of year in reviews¹ and #Strava Year in Sport in particular, here are my brief notes for how to get the info from it (before it disappears after the 6th!²) and save it locally so you can write and publish your own year in sport. How to find your Strava: Year in Sport 2024 For 2024, the Strava Year in Sport 2024 is only available on the native mobile app (iOS and presumably Android) and not accessible via the website. Prior years which were available on the website e.g. 2018(.)strava(.)com and 2017(.)strava(.)com are long gone. From the mobile app home screen, tap the "📋 You" button in the lower right corner. At the top you should see: "Play back your 2024" heading with an orange button: [ See your Year in Sport ] Tap that button. Saving Seven Summary Segments You should immediately see an animation start playing, with seven "segments" (like Instagram stories) at the top, gradually filling-in as progress indicators one at a time. For each "segment" if you press the screenshot combination of buttons on your mobile (e.g. volume-up + power on iPhone 14), in addition to taking a screenshot it will put you in a "share" screen with one or more videos or still images to share in a carousel format. For each item in the carousel (if there is more than one) * tap the item in the carousel * tap the "[↑] More" button at the bottom. * scroll down the list of options up a bit * tap "Save Video [↓]" or "Save Image [↓]" option to store it locally on your mobile. The seventh "segment" is your overall summary, and shows all your sports combined. Save it (as an image as noted above), then * tap the "✏️ Customize" button * choose an individual sport (e.g. "👟 Run") * tap "Save changes" * save that image (as above) * tap customize again * choose the next sport (e.g. "🚲 Ride") * save changes again * save image again Strava seemingly only reports summaries of (up to?) two or your sports it appears. Those were Run (presumably all running, street and trail) and Ride for me. Cleanup Your Screenshots After having saved all the videos/images for each "segment", you can: * go back to your mobile’s top level Photos app/stream * delete the screenshots You should see all the videos/images you've saved. If anything is missing, go back to the previous steps and save them again, then remove any duplicates as necessary. Post Your Year In Sport Go through your saved videos/images, and either post on your own site as-is, or use your mobile’s built-in image OCR to copy the text bits into a plain personal year in sport note summary post on your own site. Or some combination of both if you prefer. Add other summaries of your activities and sports as you see fit, like: * info on other sports (beyond running and biking), e.g. yoga, weight-lifting, bouldering etc. * total days active (of 366) * total distance (if applicable) * total elevation (if applicable) * total time * number of races you ran, biked etc. (and finished, if not the same) * number of miles (or km) you raced (per sport and/or total overall) * number of (or full set of) awards or trophies you earned at races * any other stats that you think of that seem interesting to you For each of these annual numbers, you could also compute (optionally display) the percentage change from 2023, if you happen to have those numbers around. This is also a good reason to at least total up these numbers for 2024, whether you publish them or not, for figuring out the percentage change in 2025 next year. When you publish your own year in sport post, might as well re-use the existing #YearInSport hashtag too. I have already saved all the videos/images from my own Strava Year In Sport, and as I assemble the pieces into my own post, I’ll take more notes, and add to the IndieWeb year in review page³ accordingly. This post could also be improved with a few screenshots for a few of the steps above. I figured I’d publish my notes first to hopefully help some people sooner (since the Strava Year In Sport will disappear after January 6th as mentioned!). I might upload a few screenshots to the IndieWeb wiki later as well. #yearInReview #ownYourYearInReview This is post 3 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2025/001/t2/first-new-year-review-prior → 🔮 Glossary: hashtag https://indieweb.org/hashtag own your data https://indieweb.org/own_your_data ¹ https://tantek.com/2025/001/t2/first-new-year-review-prior ² https://support.strava.com/hc/en-us/articles/22067973274509-Your-Year-in-Sport#h_01HH5VW132BPDTEZJZDHBGJ6KM ³ https://indieweb.org/year_in_review
: Welcome to 2025!15 years ago today I began posting notes on my own #indieweb site first, and only later on #socialMedia: https://tantek.com/2010/001/t1/declaring-independence-building-itYou can too.I am once again encouraging you start the year with:1. Getting a personal domain name2. Posting on your own site first, then syndicating elsewhere: #POSSEIn 2025 there are even more neighborhoods with other people’s garages¹ to post into. Companies, servers, services, disappear all the time, taking all their posts and permalinks with them to graveyard 404².This is your annual reminder to embrace #independent ownership of your online self, your creations, and their #longevity:* Own your domain -> own your online identity* Own your permalinks -> own your postsWant help? Just ask: https://chat.indieweb.org/#ownYourContent #ownYourDataOnce again I am restarting a #100PostsOfIndieWeb #100Posts project for the year.This is post 1.Previously, previously, previously:* https://tantek.com/2024/001/t1/restarting-100days-indieweb-gift-calendar* https://tantek.com/2023/001/t1/own-your-notes* https://tantek.com/2022/001/t1/12-years-notes-my-site* https://tantek.com/2020/001/t1/10-years-notes-my-site* https://tantek.com/2015/002/t1/notes-replies-faves-before-twitter-ownyourdata← ✨→ https://tantek.com/2025/001/t2/first-new-year-review-priorGlossary:IndieWeb https://indieweb.org/longevity https://indieweb.org/longevitypost https://indieweb.org/postpermalink https://indieweb.org/permalinkpersonal domain name https://indieweb.org/personal-domainPOSSE https://indieweb.org/POSSEsyndicate https://indieweb.org/syndicate¹ https://tantek.com/2023/022/t2/own-your-notes-domain-migration² https://indieweb.org/site-deaths
's status on Wednesday, 01-Jan-2025 19:18:00 EST
Welcome to 2025! 15 years ago today I began posting notes on my own #indieweb site first, and only later on #socialMedia: https://tantek.com/2010/001/t1/declaring-independence-building-it You can too. I am once again encouraging you start the year with: 1. Getting a personal domain name 2. Posting on your own site first, then syndicating elsewhere: #POSSE In 2025 there are even more neighborhoods with other people’s garages¹ to post into. Companies, servers, services, disappear all the time, taking all their posts and permalinks with them to graveyard 404². This is your annual reminder to embrace #independent ownership of your online self, your creations, and their #longevity: * Own your domain -> own your online identity * Own your permalinks -> own your posts Want help? Just ask: https://chat.indieweb.org/ #ownYourContent #ownYourData Once again I am restarting a #100PostsOfIndieWeb #100Posts project for the year. This is post 1. Previously, previously, previously: * https://tantek.com/2024/001/t1/restarting-100days-indieweb-gift-calendar * https://tantek.com/2023/001/t1/own-your-notes * https://tantek.com/2022/001/t1/12-years-notes-my-site * https://tantek.com/2020/001/t1/10-years-notes-my-site * https://tantek.com/2015/002/t1/notes-replies-faves-before-twitter-ownyourdata ← ✨ → https://tantek.com/2025/001/t2/first-new-year-review-prior Glossary: IndieWeb https://indieweb.org/ longevity https://indieweb.org/longevity post https://indieweb.org/post permalink https://indieweb.org/permalink personal domain name https://indieweb.org/personal-domain POSSE https://indieweb.org/POSSE syndicate https://indieweb.org/syndicate ¹ https://tantek.com/2023/022/t2/own-your-notes-domain-migration ² https://indieweb.org/site-deaths
: Last day of the year and last chance to #donate to worthy causes for 2024!I post a lot about the #indieweb but I’m not asking you to donate to that.Starting this series of non-profit #donation posts with asking you to consider donating to the #independentArts.Choose an #arts organization local to you or one that friends or family are directly involved in.For example: @theatermitu.org (@theatermitu @instagram.com/theatermitu)Theater Mitu is an independent theater arts organization, space, and community that supports numerous artists, shows, and incubates and produces new work!Donation link: https://secure.givelively.org/donate/theater-mitu/the-decade-ahead-10-more-years-of-mitu-in-brooklyn#TheaterMitu #NewYork #NYC #Brooklyn
's status on Tuesday, 31-Dec-2024 15:04:00 EST
Last day of the year and last chance to #donate to worthy causes for 2024! I post a lot about the #indieweb but I’m not asking you to donate to that. Starting this series of non-profit #donation posts with asking you to consider donating to the #independentArts. Choose an #arts organization local to you or one that friends or family are directly involved in. For example: @theatermitu.org (@theatermitu @instagram.com/theatermitu) Theater Mitu is an independent theater arts organization, space, and community that supports numerous artists, shows, and incubates and produces new work! Donation link: https://secure.givelively.org/donate/theater-mitu/the-decade-ahead-10-more-years-of-mitu-in-brooklyn #TheaterMitu #NewYork #NYC #Brooklyn
: I have written several posts with tips for various aspects of blogging. This post curates those posts and bits from the #IndieWeb wiki into a linear progression, from why, to what, and how to post. This post assumes you already have a blog — if you don’t have one and wonder why you should, that’s a different blog post.Why PostThere is a whole wiki page on the topic:* https://indieweb.org/why_post — which could use some gardeningHere is a summary of reasons why to post:1. Wean yourself off social media. Post to your own site instead of social media. If you already post on social media, into someone else’s garage¹, then you already have reason enough to post. So post on your own site first, and optionally syndicate² to that silo, only if you have friends who still use it to read posts.2. What to Post* Post positive things promptly: https://tantek.com/2018/357/t3 * … from that day first: https://tantek.com/2018/364/t1 * … in time order: https://tantek.com/2018/364/t5* Make and share lists. People like listsHow to Post* Use a local text editor* Capture first, edit & publish later: https://tantek.com/2023/365/t1/* Do something positive (in-person), then post about it: https://tantek.com/2018/002/t1* Single topic post* Short and to the point. Edit and remove anything distracting from the main point.* Quotable post title* Summary opening paragraph* Put tangents aside* Quotable sentences and multi-sentence paragraphs* Subheadings help cluster related paragraphs* Use a footer for updates, terminology, previous writings, additional reading, and citations. * Move definitions, citations, etc. to the footer unless including them inline either provides little risk of distraction or significantly helps reading flow. * Use footer subsections: Previously, Post Glossary, References, Additional Reading* Check your referencesEach of these points could be its own blog post.Glossarysilo https://indieweb.org/silosocial media https://indieweb.org/social_mediaReferences¹ https://tantek.com/2023/001/t1/own-your-notes² https://indieweb.org/POSSEThis is post 29 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/306/t1/simple-embeds→ 🔮
's status on Tuesday, 03-Dec-2024 00:11:00 EST
I have written several posts with tips for various aspects of blogging. This post curates those posts and bits from the #IndieWeb wiki into a linear progression, from why, to what, and how to post. This post assumes you already have a blog — if you don’t have one and wonder why you should, that’s a different blog post. Why Post There is a whole wiki page on the topic: * https://indieweb.org/why_post — which could use some gardening Here is a summary of reasons why to post: 1. Wean yourself off social media. Post to your own site instead of social media. If you already post on social media, into someone else’s garage¹, then you already have reason enough to post. So post on your own site first, and optionally syndicate² to that silo, only if you have friends who still use it to read posts. 2. What to Post * Post positive things promptly: https://tantek.com/2018/357/t3 * … from that day first: https://tantek.com/2018/364/t1 * … in time order: https://tantek.com/2018/364/t5 * Make and share lists. People like lists How to Post * Use a local text editor * Capture first, edit & publish later: https://tantek.com/2023/365/t1/ * Do something positive (in-person), then post about it: https://tantek.com/2018/002/t1 * Single topic post * Short and to the point. Edit and remove anything distracting from the main point. * Quotable post title * Summary opening paragraph * Put tangents aside * Quotable sentences and multi-sentence paragraphs * Subheadings help cluster related paragraphs * Use a footer for updates, terminology, previous writings, additional reading, and citations. * Move definitions, citations, etc. to the footer unless including them inline either provides little risk of distraction or significantly helps reading flow. * Use footer subsections: Previously, Post Glossary, References, Additional Reading * Check your references Each of these points could be its own blog post. Glossary silo https://indieweb.org/silo social media https://indieweb.org/social_media References ¹ https://tantek.com/2023/001/t1/own-your-notes ² https://indieweb.org/POSSE This is post 29 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/306/t1/simple-embeds → 🔮
: Day 1 of #IndieWebCamp #Berlin 2024¹ was very well attended!* 20 participants, more than 3x the previous one in 2022, and second highest (2019 had 22).* 18 introduced themselves² and their personal sites or aspirations for oneCollectively we proposed and facilitated 11 breakout sessions³ on many timely #indieweb topics covering #syndication, #inclusion, #longevity, #federation / #fediverse, how to best use #Mastodon with your personal site, #privacy and #security concerns of being online, #writing, how can we design better user interfaces for text authoring, and personalized reading #algorithms for staying connected with friends.Session titles (and hashtags)* How to #POSSE* How to make the web queerer / stranger. #queer* Online presence after our #death* Threat modeling #threatmodeling* Non-technical collaboration on the internet. #collab* Locations and #places check-in* Writing with images. #imagewriting* Text authoring UX. #textUX* #SSR, organizing CSS/JS* Website design without being a designer. #designfordummies* Timeline algorithms. #timelinesEtherpad notes from sessions have been archived to the wiki, with session recordings to follow!Day 2 also had 20 in-person participants, the highest IndieWebCamp Berlin day 2 attendance ever! Most everyone from day 1 came back to hack, and three new people showed up. We also had several remote participants.References ¹ https://indieweb.org/2024² https://indieweb.org/2024/Berlin/Intros³ https://indieweb.org/2024/Berlin/Schedule#SaturdayThis is post 28 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/306/t1/simple-embeds→ 🔮
's status on Saturday, 09-Nov-2024 08:31:00 EST
Day 1 of #IndieWebCamp #Berlin 2024¹ was very well attended! * 20 participants, more than 3x the previous one in 2022, and second highest (2019 had 22). * 18 introduced themselves² and their personal sites or aspirations for one Collectively we proposed and facilitated 11 breakout sessions³ on many timely #indieweb topics covering #syndication, #inclusion, #longevity, #federation / #fediverse, how to best use #Mastodon with your personal site, #privacy and #security concerns of being online, #writing, how can we design better user interfaces for text authoring, and personalized reading #algorithms for staying connected with friends. Session titles (and hashtags) * How to #POSSE * How to make the web queerer / stranger. #queer * Online presence after our #death * Threat modeling #threatmodeling * Non-technical collaboration on the internet. #collab * Locations and #places check-in * Writing with images. #imagewriting * Text authoring UX. #textUX * #SSR, organizing CSS/JS * Website design without being a designer. #designfordummies * Timeline algorithms. #timelines Etherpad notes from sessions have been archived to the wiki, with session recordings to follow! Day 2 also had 20 in-person participants, the highest IndieWebCamp Berlin day 2 attendance ever! Most everyone from day 1 came back to hack, and three new people showed up. We also had several remote participants. References ¹ https://indieweb.org/2024 ² https://indieweb.org/2024/Berlin/Intros ³ https://indieweb.org/2024/Berlin/Schedule#Saturday This is post 28 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/306/t1/simple-embeds → 🔮
: Last week at a #HomebrewWebsiteClub session¹ I pointed out that I was working on implementing a “simple” way to support embeds of my notes, that is, make my short notes embeddable, like how people embed tweets or toots.I noted that to keep it as simple as possible while being flexible to implementation changes, I planned to implement three things:1. A separate “embed” version of my post permalinks, with just the entry information (no header, nav, search, sidebar, footer etc.), embeddable via copy/paste or an iframe.2. A way to “Follow Your Nose” discover that separate embed version3. A way to discover the original post from the embedded versionFor (1) a minimal h-entry, with perhaps a little bit of inline CSS would suffice.For (2) I proposed using “rel=embed” which I’ve subsequently written up briefly².For (3) The obvious existing answer is rel=canonical link from the embed version to the canonical post permalink.Soon thereafter, several folks in the #IndieWeb community went ahead and implemented such embeds for their own sites, and even the https://libre.fm/ open scrobbling service!https://indieweb.org/embed#IndieWeb_ExamplesI have yet to implement it myself, and that’s fine. This is one of the things I appreciate about the community, we can share our plans and ideas for improving things on our own sites, and if someone else does it first, that's great! We celebrate it and explore the solution space together.Got other ideas for simple embeds? Want to implement them on your own site?Join us in the #indiewebdev chat: https://chat.indieweb.org/devUPDATE: What about oEmbed? tl;dr: oEmbed requires JS and backend code, more work and unsuitable for embeds from static site hosting (like GitHub pages). A simple HTML method is accessible to many more independent publishers and easier to implement. More: https://tantek.com/2024/306/t2Glossaryembed https://indieweb.org/embedFollow Your Nose https://indieweb.org/follow_your_noseh-entry https://microformats.org/wiki/h-entryoEmbed https://indieweb.org/oEmbedrel-canonical https://indieweb.org/rel-canonicalstatic site hosting https://indieweb.org/static_web_hostingReferences ¹ https://indieweb.org/events/2024-10-23-hwc-europe#embedding² https://indieweb.org/rel-embedThis is post 27 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/287/t1/fediverse-unfollow-bridgyfed-bug→ 🔮
's status on Friday, 01-Nov-2024 17:33:00 EDT
Last week at a #HomebrewWebsiteClub session¹ I pointed out that I was working on implementing a “simple” way to support embeds of my notes, that is, make my short notes embeddable, like how people embed tweets or toots. I noted that to keep it as simple as possible while being flexible to implementation changes, I planned to implement three things: 1. A separate “embed” version of my post permalinks, with just the entry information (no header, nav, search, sidebar, footer etc.), embeddable via copy/paste or an iframe. 2. A way to “Follow Your Nose” discover that separate embed version 3. A way to discover the original post from the embedded version For (1) a minimal h-entry, with perhaps a little bit of inline CSS would suffice. For (2) I proposed using “rel=embed” which I’ve subsequently written up briefly². For (3) The obvious existing answer is rel=canonical link from the embed version to the canonical post permalink. Soon thereafter, several folks in the #IndieWeb community went ahead and implemented such embeds for their own sites, and even the https://libre.fm/ open scrobbling service! https://indieweb.org/embed#IndieWeb_Examples I have yet to implement it myself, and that’s fine. This is one of the things I appreciate about the community, we can share our plans and ideas for improving things on our own sites, and if someone else does it first, that's great! We celebrate it and explore the solution space together. Got other ideas for simple embeds? Want to implement them on your own site? Join us in the #indiewebdev chat: https://chat.indieweb.org/dev UPDATE: What about oEmbed? tl;dr: oEmbed requires JS and backend code, more work and unsuitable for embeds from static site hosting (like GitHub pages). A simple HTML method is accessible to many more independent publishers and easier to implement. More: https://tantek.com/2024/306/t2 Glossary embed https://indieweb.org/embed Follow Your Nose https://indieweb.org/follow_your_nose h-entry https://microformats.org/wiki/h-entry oEmbed https://indieweb.org/oEmbed rel-canonical https://indieweb.org/rel-canonical static site hosting https://indieweb.org/static_web_hosting References ¹ https://indieweb.org/events/2024-10-23-hwc-europe#embedding ² https://indieweb.org/rel-embed This is post 27 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/287/t1/fediverse-unfollow-bridgyfed-bug → 🔮
: European friends!🗓 I am going to Beyond Tellerand (@btconf@mastodon.social) Berlin next week 7-8 November and you should too!BTconf is the best independent web design, development, and inspiration conference in Europe.Everything from the speakers to the talks to the side events are a labor of love by @MarcThiele.com (@marcthiele@mastodon.social) and his crew, and it shows in the #btconf community he has gathered over the years.If you’re in #Berlin, or can hop on a train and join us, you should.🎟 Grab a ticket: https://btco.nf/tAnd while you’re there, consider joining us at #IndieWebCamp Berlin right afterwards on 9-10 November (complimentary camp tickets at the same link), for #barcamp style discussions sessions and an #indieweb Create Day, writing, styling, designing, coding, hacking on our personal sites for a better web for ourselves and everyone else.
's status on Friday, 01-Nov-2024 01:34:00 EDT
European friends! 🗓 I am going to Beyond Tellerand (@btconf@mastodon.social) Berlin next week 7-8 November and you should too! BTconf is the best independent web design, development, and inspiration conference in Europe. Everything from the speakers to the talks to the side events are a labor of love by @MarcThiele.com (@marcthiele@mastodon.social) and his crew, and it shows in the #btconf community he has gathered over the years. If you’re in #Berlin, or can hop on a train and join us, you should. 🎟 Grab a ticket: https://btco.nf/t And while you’re there, consider joining us at #IndieWebCamp Berlin right afterwards on 9-10 November (complimentary camp tickets at the same link), for #barcamp style discussions sessions and an #indieweb Create Day, writing, styling, designing, coding, hacking on our personal sites for a better web for ourselves and everyone else.
: No I did not block you on the #fediverse / #Mastodon / #Misskey etc.If you were following me @tantek.com on your client/server/instance of choice but noticed you were no longer doing so, that was due to a recent software bug in my fediverse provider which accidentally caused everyone’s #ActivityPub servers to unfollow me (bug details below).No it’s absolutely not your fault, you did nothing wrong.We need a variant of Hanlon’s Razor¹ like:“Never attribute to malice that which is adequately explained by a software bug.”Take another look at my posts if you want (directly on @tantek.com or try searching for that on your instance) and if you like what you see or find them otherwise informative and useful, feel free to refollow. If not, no worries!Also no worries if you ever unfollow/refollow for any reason. I mean that. I always assume people know best how to manage their online reader/reading experiences, everyone’s priorities and likes/dislikes change over time, and encourage everyone to make choices that are best for their mental health and overall joy online.Bug details:This was due to a #BridgyFed bug² that deleted my profile (“ActivityPub actor”) from (nearly?) all instances, making everyone’s accounts automatically unfollow me, as well as remove any of my posts from your likes and reposts (boosts) collections. It also removed my posts from any of your replies to my posts, leaving your replies dangling without reply-contexts. Apologies!The bug was introduced accidentally as part of another fix about a month ago³, and was triggered within the following week⁴.Anyone following me before ~2024-09-22 was no longer following me. A few folks have noticed and refollowed. Any likes or reposts of my posts before that date were also undone (removed).Ryan (@snarfed.org) has been really good about giving folks a heads-up, and apologizing, and quickly doing what he can to fix things.Bugs happen, yes even in production code, so please do not post/send any hate.I’d rather be one of the folks helping with improving BridgyFed, and temporary setbacks like this are part of being an early / eager #IndieWeb adopter.This bug has also revealed some potential weaknesses in other ActivityPub implementations. E.g. deleting an “actor” should be undoable, and undoing a delete should reconnect everything, from follows to likes & reposts collections, to reply-contexts. Perhaps the ActivityPub specification could be updated with such guidance (if it hasn’t been already, I need to double-check).To be clear, I’m still a big supporter of #BridgyFed, #ActivityPub, #Webmention, and everyone who chooses to implement these and other #IndieWeb related and adjacent protocols as best fits their products and services. All of these are a part of our broader open #socialWeb, and making all these #openStandards work well together (including handling edge-cases and mistakes!) is essential for providing #socialMedia alternatives that put users first.References:¹ https://en.wikipedia.org/wiki/Hanlon%27s_razor² https://github.com/snarfed/bridgy-fed/issues/1379³ https://github.com/snarfed/bridgy-fed/commit/4df76d0db7b87cabbd714039546c05b3221169be⁴ https://chat.indieweb.org/dev/2024-09-22#t1727028174623700This is post 26 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/285/t1/io-domain-suggested-steps→ 🔮
's status on Sunday, 13-Oct-2024 16:37:00 EDT
No I did not block you on the #fediverse / #Mastodon / #Misskey etc. If you were following me @tantek.com on your client/server/instance of choice but noticed you were no longer doing so, that was due to a recent software bug in my fediverse provider which accidentally caused everyone’s #ActivityPub servers to unfollow me (bug details below). No it’s absolutely not your fault, you did nothing wrong. We need a variant of Hanlon’s Razor¹ like: “Never attribute to malice that which is adequately explained by a software bug.” Take another look at my posts if you want (directly on @tantek.com or try searching for that on your instance) and if you like what you see or find them otherwise informative and useful, feel free to refollow. If not, no worries! Also no worries if you ever unfollow/refollow for any reason. I mean that. I always assume people know best how to manage their online reader/reading experiences, everyone’s priorities and likes/dislikes change over time, and encourage everyone to make choices that are best for their mental health and overall joy online. Bug details: This was due to a #BridgyFed bug² that deleted my profile (“ActivityPub actor”) from (nearly?) all instances, making everyone’s accounts automatically unfollow me, as well as remove any of my posts from your likes and reposts (boosts) collections. It also removed my posts from any of your replies to my posts, leaving your replies dangling without reply-contexts. Apologies! The bug was introduced accidentally as part of another fix about a month ago³, and was triggered within the following week⁴. Anyone following me before ~2024-09-22 was no longer following me. A few folks have noticed and refollowed. Any likes or reposts of my posts before that date were also undone (removed). Ryan (@snarfed.org) has been really good about giving folks a heads-up, and apologizing, and quickly doing what he can to fix things. Bugs happen, yes even in production code, so please do not post/send any hate. I’d rather be one of the folks helping with improving BridgyFed, and temporary setbacks like this are part of being an early / eager #IndieWeb adopter. This bug has also revealed some potential weaknesses in other ActivityPub implementations. E.g. deleting an “actor” should be undoable, and undoing a delete should reconnect everything, from follows to likes & reposts collections, to reply-contexts. Perhaps the ActivityPub specification could be updated with such guidance (if it hasn’t been already, I need to double-check). To be clear, I’m still a big supporter of #BridgyFed, #ActivityPub, #Webmention, and everyone who chooses to implement these and other #IndieWeb related and adjacent protocols as best fits their products and services. All of these are a part of our broader open #socialWeb, and making all these #openStandards work well together (including handling edge-cases and mistakes!) is essential for providing #socialMedia alternatives that put users first. References: ¹ https://en.wikipedia.org/wiki/Hanlon%27s_razor ² https://github.com/snarfed/bridgy-fed/issues/1379 ³ https://github.com/snarfed/bridgy-fed/commit/4df76d0db7b87cabbd714039546c05b3221169be ⁴ https://chat.indieweb.org/dev/2024-09-22#t1727028174623700 This is post 26 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/285/t1/io-domain-suggested-steps → 🔮
: Happy October!For some reason this month has a plethora of daily blogging or other creativity prompts. Here’s a list of the ones I found so far:* #Blogtober (consider this post my first for this, retroactively day 1)* Inktober — https://inktober.com/* LOLtober - https://weblog.anniegreens.lol/2024/10/loltober-2024* Looptober — https://looptober.com/* Mathober - https://mathober.com/* Viztober — https://www.instagram.com/evalottchen/p/DAiNm3ZtuTj/Having found so many for the month I created an “October” page on the #IndieWeb wiki to document them all (and in case folks find others to add):* https://indieweb.org/OctoberOctober is also a very popular month for seasonal blog styling:* https://indieweb.org/HalloweenDo you have a custom Halloween theme for your personal site? Add it to the wiki!This is post 23 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/247/t4/w3c-link-checker-before-federating→ 🔮
's status on Thursday, 03-Oct-2024 19:04:00 EDT
Happy October! For some reason this month has a plethora of daily blogging or other creativity prompts. Here’s a list of the ones I found so far: * #Blogtober (consider this post my first for this, retroactively day 1) * Inktober — https://inktober.com/ * LOLtober - https://weblog.anniegreens.lol/2024/10/loltober-2024 * Looptober — https://looptober.com/ * Mathober - https://mathober.com/ * Viztober — https://www.instagram.com/evalottchen/p/DAiNm3ZtuTj/ Having found so many for the month I created an “October” page on the #IndieWeb wiki to document them all (and in case folks find others to add): * https://indieweb.org/October October is also a very popular month for seasonal blog styling: * https://indieweb.org/Halloween Do you have a custom Halloween theme for your personal site? Add it to the wiki! This is post 23 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/247/t4/w3c-link-checker-before-federating → 🔮
: 20 years and two weeks ago, I came up with undohtml.css and unknowingly invented the mechanism of CSS Resets (AKA reboot or reset style sheets¹) which spawned numerous variants, many still in broad use on the web today.https://tantek.com/log/2004/09.html#d06t2354A one sentence problem description, and a short paragraph describing my problem-solving, actions, license, link to less than 300 bytes of code (not counting comments), and a few future thoughts.The rest of that blog post was about “debug scaffolding”, the part I thought was more interesting at the time.Eric Meyer (@meyerweb.com @meyerweb@mastodon.social) followed up ~10 days afterwards with his thinking and improvements:* https://meyerweb.com/eric/thoughts/2004/09/15/emreallyem-undoing-htmlcss/where he mentioned “resetting” in passing, but not actually calling it a "reset".~2.5 years later Eric published “Reset Styles” with further reasoning and improvements:* http://meyerweb.com/eric/thoughts/2007/04/12/reset-styles/describing them as: “reset” or “baseline” set of styles.Subsequently he iterated in several more blog posts:* http://meyerweb.com/eric/thoughts/2007/04/14/reworked-reset/* http://meyerweb.com/eric/thoughts/2007/04/18/reset-reasoning/ — this is Eric’s first post where he explicitly calls them “reset styles”, which I believe is the origin of the eventual phrase “CSS Reset” and “reset style sheets”* http://meyerweb.com/eric/thoughts/2007/05/01/reset-reloaded/ (yes a Matrix: Reloaded reference)~6 months later Eric published his evergreen resource “CSS Tools: Reset CSS”* https://meyerweb.com/eric/tools/css/reset/which, as you see within the URL: “css/reset”, is perhaps where the phrase “CSS Reset” comes from, and it’s also the label (link text) he gives that page in his UI about-page² and the first content link in his 404 page³.My technology invention takeaways from all this:1. if you find yourself repeatedly solving the same (especially annoying) problem, create a re-usable solution that works for you2. write up your problem statement / use-case in only one sentence3. publish your solution (on your personal site⁴), name it something short, with only a short paragraph description, and re-use/remix friendly license (like Creative Commons)And things not to worry about (that may get in your way to publishing):1. perfecting or making your solution “big enough” or “the right size”. does it solve your problem? then it’s already the right size.2. coming up with the perfect name. instead, name it what it does. someone might come up with a better name weeks, months, or years later. let them run with it!3. waiting to blog multiple things. I could have blogged undohtml.css by itself, probably should have, and instead lumped it into a blog post with another CSS thing I came up with.Further reading and resources for CSS Resets:* More history: https://css-tricks.com/reboot-resets-reasoning/* Large collection: https://perishablepress.com/a-killer-collection-of-global-css-reset-styles/References:¹ https://en.wikipedia.org/wiki/Reset_style_sheet² https://meyerweb.com/ui/about.html³ https://meyerweb.com/404⁴ https://indieweb.org/#undoHTML #undoHTMLCSS #reset #CSSreset #resetstyles #webdesign #technology #invention #indieweb
's status on Thursday, 19-Sep-2024 20:35:00 EDT
20 years and two weeks ago, I came up with undohtml.css and unknowingly invented the mechanism of CSS Resets (AKA reboot or reset style sheets¹) which spawned numerous variants, many still in broad use on the web today. https://tantek.com/log/2004/09.html#d06t2354 A one sentence problem description, and a short paragraph describing my problem-solving, actions, license, link to less than 300 bytes of code (not counting comments), and a few future thoughts. The rest of that blog post was about “debug scaffolding”, the part I thought was more interesting at the time. Eric Meyer (@meyerweb.com @meyerweb@mastodon.social) followed up ~10 days afterwards with his thinking and improvements: * https://meyerweb.com/eric/thoughts/2004/09/15/emreallyem-undoing-htmlcss/ where he mentioned “resetting” in passing, but not actually calling it a "reset". ~2.5 years later Eric published “Reset Styles” with further reasoning and improvements: * http://meyerweb.com/eric/thoughts/2007/04/12/reset-styles/ describing them as: “reset” or “baseline” set of styles. Subsequently he iterated in several more blog posts: * http://meyerweb.com/eric/thoughts/2007/04/14/reworked-reset/ * http://meyerweb.com/eric/thoughts/2007/04/18/reset-reasoning/ — this is Eric’s first post where he explicitly calls them “reset styles”, which I believe is the origin of the eventual phrase “CSS Reset” and “reset style sheets” * http://meyerweb.com/eric/thoughts/2007/05/01/reset-reloaded/ (yes a Matrix: Reloaded reference) ~6 months later Eric published his evergreen resource “CSS Tools: Reset CSS” * https://meyerweb.com/eric/tools/css/reset/ which, as you see within the URL: “css/reset”, is perhaps where the phrase “CSS Reset” comes from, and it’s also the label (link text) he gives that page in his UI about-page² and the first content link in his 404 page³. My technology invention takeaways from all this: 1. if you find yourself repeatedly solving the same (especially annoying) problem, create a re-usable solution that works for you 2. write up your problem statement / use-case in only one sentence 3. publish your solution (on your personal site⁴), name it something short, with only a short paragraph description, and re-use/remix friendly license (like Creative Commons) And things not to worry about (that may get in your way to publishing): 1. perfecting or making your solution “big enough” or “the right size”. does it solve your problem? then it’s already the right size. 2. coming up with the perfect name. instead, name it what it does. someone might come up with a better name weeks, months, or years later. let them run with it! 3. waiting to blog multiple things. I could have blogged undohtml.css by itself, probably should have, and instead lumped it into a blog post with another CSS thing I came up with. Further reading and resources for CSS Resets: * More history: https://css-tricks.com/reboot-resets-reasoning/ * Large collection: https://perishablepress.com/a-killer-collection-of-global-css-reset-styles/ References: ¹ https://en.wikipedia.org/wiki/Reset_style_sheet ² https://meyerweb.com/ui/about.html ³ https://meyerweb.com/404 ⁴ https://indieweb.org/ #undoHTML #undoHTMLCSS #reset #CSSreset #resetstyles #webdesign #technology #invention #indieweb
: Twenty years ago this past February, Kevin Marks and I introduced #microformats in a conference presentation.Full post: https://tantek.com/2024/044/t1/twenty-years-microformatsAside: This is an even shorter summary of that post from ~200 days ago, which #Mastodon readers never got due to a Mastodon #federation bug (details in https://tantek.com/t5Yo1).Since early 2023, here are the top three updates & interesting developments in microformats:1. Growing rel=me adoption for distributed verification (✅ in Mastodon etc.) * Wikipedia, Threads, omg.lol2. Proposal to merge #microformats2 h-review into h-entry, since in practice (e.g. on #indieweb) reviews are just entries with a bit more.3. #metaformats adoptions, implementations, iteration
's status on Tuesday, 03-Sep-2024 21:47:00 EDT
Twenty years ago this past February, Kevin Marks and I introduced #microformats in a conference presentation. Full post: https://tantek.com/2024/044/t1/twenty-years-microformats Aside: This is an even shorter summary of that post from ~200 days ago, which #Mastodon readers never got due to a Mastodon #federation bug (details in https://tantek.com/t5Yo1). Since early 2023, here are the top three updates & interesting developments in microformats: 1. Growing rel=me adoption for distributed verification (✅ in Mastodon etc.) * Wikipedia, Threads, omg.lol 2. Proposal to merge #microformats2 h-review into h-entry, since in practice (e.g. on #indieweb) reviews are just entries with a bit more. 3. #metaformats adoptions, implementations, iteration
: Twenty years ago this past February, @KevinMarks.com (@KevinMarks@xoxo.zone) and I introduced #microformats in a conference presentation.Full post: https://tantek.com/2024/044/t1/twenty-years-microformatsAside: This is a summary of a longer post from ~200 days ago¹, which #Mastodon readers never got due to a Mastodon #federation bug (instances returned 202 for post inbox delivery, but did not show post to followers or on local profiles, details in https://tantek.com/t5Yo1).I wrote a retrospective last year: https://tantek.com/2023/047/t1/nineteen-years-microformatsSince then, here are the top three updates & interesting developments in microformats:1. Growing rel=me adoption for distributed verification (✅ in Mastodon etc.) * Wikipedia, Threads, omg.lol support2. A proposal to merge #microformats2 h-review into h-entry, since reviews are in practice (e.g. on the #indieweb) always entries with a bit more information.3. #metaformats adoptions, implementations, and iterationMore details: ¹ https://tantek.com/2024/044/t1/twenty-years-microformats
's status on Tuesday, 03-Sep-2024 17:02:00 EDT
Twenty years ago this past February, @KevinMarks.com (@KevinMarks@xoxo.zone) and I introduced #microformats in a conference presentation. Full post: https://tantek.com/2024/044/t1/twenty-years-microformats Aside: This is a summary of a longer post from ~200 days ago¹, which #Mastodon readers never got due to a Mastodon #federation bug (instances returned 202 for post inbox delivery, but did not show post to followers or on local profiles, details in https://tantek.com/t5Yo1). I wrote a retrospective last year: https://tantek.com/2023/047/t1/nineteen-years-microformats Since then, here are the top three updates & interesting developments in microformats: 1. Growing rel=me adoption for distributed verification (✅ in Mastodon etc.) * Wikipedia, Threads, omg.lol support 2. A proposal to merge #microformats2 h-review into h-entry, since reviews are in practice (e.g. on the #indieweb) always entries with a bit more information. 3. #metaformats adoptions, implementations, and iteration More details: ¹ https://tantek.com/2024/044/t1/twenty-years-microformats
: ✏️ I want the Read Write Suggest-Edit Accept-Edit Update Web.The consumer Infinite Scroll Web leaves us feeling empty.Too few of us participate in the Read Write Web, whether with personal sites or Wikipedia.A week ago when we wrapped up #IndieWebCamp Portland and I was reading Kevin Marks (@kevinmarks@indieweb.social) live-tooting of the demos¹, I noticed a few errors, typos or miscaptures, and pointed them out in-person.Kevin was able to quickly edit his toots and update them for anyone reading, thanks to #Mastodon’s post editing feature and its support of #ActivityPub Updates. But this shouldn’t require being in the same room, whether IRL or chat.We should be able to suggest edits to each other’s posts, as easily as we can reply and add a comment.13 years ago I wrote²: “The Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.”Now I want the Read Write Suggest-Edit Accept-Edit Update Web.The ↪ Reply button is fairly ubiquitous in modern post user interfaces (UIs).Why not also a ✏️ Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid "performative" suggested edits.If the author’s posts provide revision histories, when a suggested edit is accepted, a post’s history could show the contributor of the edit.Instead of asking Kevin in-person, what if I could have posted special "Suggested Edit" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots?To enable such UIs and interactions across servers and implementations, we may need a new type of response³, perhaps with a special property (or more) to convey the edits being suggested.There is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #IndieWeb wiki:* https://indieweb.org/editOur interaction after IndieWebCamp has inspired me to take another look at how can we design and prototype solutions to this problem.For now, if you host your blog and posts as static files on GitHub (or equivalent), you could add a button like this to your posts alongside Like, Reply, Repost buttons:✏️ Suggest Editand link it to an edit URL for the static file for the post.I don’t use GitHub static files myself for posts, but here’s an example of such an edit link for one of my projects:https://tantek.com/github/cassis/edit/main/README.mdThis will start the process of creating a “pull request”, GitHub’s jargon⁴ for a “suggested edit”.After completing GitHub’s ceremony of entering multiple text fields (summary & description), and multiple clicks to create said “pull request”, it’ll be sent to the author to review. Presuming the author likes the suggested edit, they can perform the other half of GitHub’s jargon-filled ceremonies to “Merge” or “Squash & Merge”, “Delete fork”, etc. to accept the edit.It’s an awkward interaction⁵, however useful for at least prototyping a ✏️ Suggest Edit button on sites that store their posts as files in GitHub. Certainly worthy of experimenting with and gathering experience to design and build even better interactions.We can start with the shortest path to getting something working, then learn, iterate, improve, repeat.#readWriteWeb #editableWeb #suggestEdit #acceptEditReferences:¹ https://indieweb.social/@kevinmarks/113025295600067213² https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11³ https://indieweb.org/responses⁴ The phrase “pull request” was derived from the git command: “git request-pull” according to https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/⁵ “edits” in GitHub require taking far more steps, and navigating far more jargon, then say, Wikipedia pages, which come down to “Edit” and “Save”. We should aspire to Wikipedia’s simplicity, not GitHub’s ceremonies.This is post 20 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/242/t1/indiewebcamp-portland→ https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed
's status on Sunday, 01-Sep-2024 17:51:00 EDT
✏️ I want the Read Write Suggest-Edit Accept-Edit Update Web. The consumer Infinite Scroll Web leaves us feeling empty. Too few of us participate in the Read Write Web, whether with personal sites or Wikipedia. A week ago when we wrapped up #IndieWebCamp Portland and I was reading Kevin Marks (@kevinmarks@indieweb.social) live-tooting of the demos¹, I noticed a few errors, typos or miscaptures, and pointed them out in-person. Kevin was able to quickly edit his toots and update them for anyone reading, thanks to #Mastodon’s post editing feature and its support of #ActivityPub Updates. But this shouldn’t require being in the same room, whether IRL or chat. We should be able to suggest edits to each other’s posts, as easily as we can reply and add a comment. 13 years ago I wrote²: “The Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.” Now I want the Read Write Suggest-Edit Accept-Edit Update Web. The ↪ Reply button is fairly ubiquitous in modern post user interfaces (UIs). Why not also a ✏️ Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid "performative" suggested edits. If the author’s posts provide revision histories, when a suggested edit is accepted, a post’s history could show the contributor of the edit. Instead of asking Kevin in-person, what if I could have posted special "Suggested Edit" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots? To enable such UIs and interactions across servers and implementations, we may need a new type of response³, perhaps with a special property (or more) to convey the edits being suggested. There is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #IndieWeb wiki: * https://indieweb.org/edit Our interaction after IndieWebCamp has inspired me to take another look at how can we design and prototype solutions to this problem. For now, if you host your blog and posts as static files on GitHub (or equivalent), you could add a button like this to your posts alongside Like, Reply, Repost buttons: ✏️ Suggest Edit and link it to an edit URL for the static file for the post. I don’t use GitHub static files myself for posts, but here’s an example of such an edit link for one of my projects: https://tantek.com/github/cassis/edit/main/README.md This will start the process of creating a “pull request”, GitHub’s jargon⁴ for a “suggested edit”. After completing GitHub’s ceremony of entering multiple text fields (summary & description), and multiple clicks to create said “pull request”, it’ll be sent to the author to review. Presuming the author likes the suggested edit, they can perform the other half of GitHub’s jargon-filled ceremonies to “Merge” or “Squash & Merge”, “Delete fork”, etc. to accept the edit. It’s an awkward interaction⁵, however useful for at least prototyping a ✏️ Suggest Edit button on sites that store their posts as files in GitHub. Certainly worthy of experimenting with and gathering experience to design and build even better interactions. We can start with the shortest path to getting something working, then learn, iterate, improve, repeat. #readWriteWeb #editableWeb #suggestEdit #acceptEdit References: ¹ https://indieweb.social/@kevinmarks/113025295600067213 ² https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11 ³ https://indieweb.org/responses ⁴ The phrase “pull request” was derived from the git command: “git request-pull” according to https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/ ⁵ “edits” in GitHub require taking far more steps, and navigating far more jargon, then say, Wikipedia pages, which come down to “Edit” and “Save”. We should aspire to Wikipedia’s simplicity, not GitHub’s ceremonies. This is post 20 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/242/t1/indiewebcamp-portland → https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed
: ✏️ I want the Read Write Suggest-Edit Accept-Edit Update Web.The consumer Infinite Scroll Web leaves us feeling empty.Too few of us participate in the Read Write Web, whether with personal sites or Wikipedia.A week ago when we wrapped up #IndieWebCamp Portland and I was reading @KevinMarks.com (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) live-tooting of the demos¹, I noticed a few errors, typos or miscaptures, and pointed them out in-person.Kevin was able to quickly edit his toots and update them for anyone reading, thanks to #Mastodon’s post editing feature and its support of #ActivityPub Updates. But this shouldn’t require being in the same room, IRL or chat.We should be able to suggest edits to each other’s posts, as easily as we can reply and add a comment.13 years ago I wrote²: “The Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.”Now I want the Read Write Suggest-Edit Accept-Edit Update Web.The ↪ Reply button is fairly ubiquitous in modern post user interfaces (UIs).Why not also a ✏️ Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid "performative" suggested edits.If the author’s posts provide revision histories, when a suggested edit is accepted, a post’s history could show the contributor of the edit.Instead of asking Kevin in-person, what if I could have posted special "Suggested Edit" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots?To enable such UIs and interactions across servers and implementations, we may need a new type of response³, perhaps with a special property (or more) to convey the edits being suggested.There is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #IndieWeb wiki:* https://indieweb.org/editOur interaction after IndieWebCamp has inspired me to take another look at how can we design and prototype solutions to this problem.For now, if you host your blog and posts as static files on GitHub (or equivalent), you could add a button like this to your posts alongside Like, Reply, Repost buttons:✏️ Suggest Editand link it to an edit URL for the static file for the post.I don’t use GitHub static files myself for posts, but here’s an example of such an edit link for one of my projects:https://tantek.com/github/cassis/edit/main/README.mdThis will start the process of creating a “pull request”, GitHub’s jargon⁴ for a “suggested edit”.After completing GitHub’s ceremony of entering multiple text fields (summary & description), and multiple clicks to create said “pull request”, it’ll be sent to the author to review. Presuming the author likes the suggested edit, they can perform the other half of GitHub’s jargon-filled ceremonies to “Merge” or “Squash & Merge”, “Delete fork”, etc. to accept the edit.It’s an awkward interaction⁵, however useful for at least prototyping a ✏️ Suggest Edit button on sites that store their posts as files in GitHub. Certainly worthy of experimenting with and gathering experience to design and build even better interactions.We can start with the shortest path to getting something working, then learn, iterate, improve, repeat.#readWriteWeb #editableWeb #suggestEdit #acceptEditReferences:¹ https://indieweb.social/@kevinmarks/113025295600067213² https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11³ https://indieweb.org/responses⁴ The phrase “pull request” was derived from the git command: “git request-pull” according to https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/⁵ “edits” in GitHub require taking far more steps, and navigating far more jargon, then say, Wikipedia pages, which come down to “Edit” and “Save”. We should aspire to Wikipedia’s simplicity, not GitHub’s ceremonies.This is post 20 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/242/t1/indiewebcamp-portland→ 🔮
✏️ I want the Read Write Suggest-Edit Accept-Edit Update Web. The consumer Infinite Scroll Web leaves us feeling empty. Too few of us participate in the Read Write Web, whether with personal sites or Wikipedia. A week ago when we wrapped up #IndieWebCamp Portland and I was reading @KevinMarks.com (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) live-tooting of the demos¹, I noticed a few errors, typos or miscaptures, and pointed them out in-person. Kevin was able to quickly edit his toots and update them for anyone reading, thanks to #Mastodon’s post editing feature and its support of #ActivityPub Updates. But this shouldn’t require being in the same room, IRL or chat. We should be able to suggest edits to each other’s posts, as easily as we can reply and add a comment. 13 years ago I wrote²: “The Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.” Now I want the Read Write Suggest-Edit Accept-Edit Update Web. The ↪ Reply button is fairly ubiquitous in modern post user interfaces (UIs). Why not also a ✏️ Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid "performative" suggested edits. If the author’s posts provide revision histories, when a suggested edit is accepted, a post’s history could show the contributor of the edit. Instead of asking Kevin in-person, what if I could have posted special "Suggested Edit" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots? To enable such UIs and interactions across servers and implementations, we may need a new type of response³, perhaps with a special property (or more) to convey the edits being suggested. There is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #IndieWeb wiki: * https://indieweb.org/edit Our interaction after IndieWebCamp has inspired me to take another look at how can we design and prototype solutions to this problem. For now, if you host your blog and posts as static files on GitHub (or equivalent), you could add a button like this to your posts alongside Like, Reply, Repost buttons: ✏️ Suggest Edit and link it to an edit URL for the static file for the post. I don’t use GitHub static files myself for posts, but here’s an example of such an edit link for one of my projects: https://tantek.com/github/cassis/edit/main/README.md This will start the process of creating a “pull request”, GitHub’s jargon⁴ for a “suggested edit”. After completing GitHub’s ceremony of entering multiple text fields (summary & description), and multiple clicks to create said “pull request”, it’ll be sent to the author to review. Presuming the author likes the suggested edit, they can perform the other half of GitHub’s jargon-filled ceremonies to “Merge” or “Squash & Merge”, “Delete fork”, etc. to accept the edit. It’s an awkward interaction⁵, however useful for at least prototyping a ✏️ Suggest Edit button on sites that store their posts as files in GitHub. Certainly worthy of experimenting with and gathering experience to design and build even better interactions. We can start with the shortest path to getting something working, then learn, iterate, improve, repeat. #readWriteWeb #editableWeb #suggestEdit #acceptEdit References: ¹ https://indieweb.social/@kevinmarks/113025295600067213 ² https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11 ³ https://indieweb.org/responses ⁴ The phrase “pull request” was derived from the git command: “git request-pull” according to https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/ ⁵ “edits” in GitHub require taking far more steps, and navigating far more jargon, then say, Wikipedia pages, which come down to “Edit” and “Save”. We should aspire to Wikipedia’s simplicity, not GitHub’s ceremonies. This is post 20 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/242/t1/indiewebcamp-portland → 🔮
: Had a great time at IndieWebCamp Portland 2024 this past Sunday — our 10th IndieWebCamp in Portland!https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0kBeing a one day #IndieWebCamp, we focused more on making, hacking, and creating, than on formal discussion sessions.Nearly everyone gave a brief personal site intro with a summary of how they use their #IndieWeb site and what they would like to add, remove, or improve.* https://indieweb.org/2024/Portland/IntrosThere were lots of informal discussions, some in the main room, on the walk to and from lunch, over lunch in the nearby outdoor patio, or at tables inside the lobby of the Hotel Grand Stark.We wrapped up with our usual Create Day¹ Demos session, live streamed for remote attendees to see as well. Lots of great demos of things people built, designed, removed, cleaned-up, documented, and blogged! Everyone still at the camp showed something on their personal site!* https://indieweb.org/2024/Portland/DemosGroup photo and lots more about IndieWebCamp Portland 2024 at the event’s wiki page:* https://indieweb.org/2024/PortlandThanks to everyone who pitched in to help organize IndieWebCamp Portland 2024! Thanks especially to Marty McGuire (@martymcgui.re) for taking live notes during both the personal site intros and create day demos, to Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) for the IndieWebCamp live-tooting, and Ryan Barrett (@snarfed.org) for amazing breakfast pastries from Dos Hermanos.The experience definitely raised our hopes and confidence for returning to Portland in 2025.²References:¹ https://indieweb.org/Create_Day² https://indieweb.org/Planning#PortlandThis is post 19 of #100PostsOfIndieWeb. #100Posts #2024_238← https://tantek.com/2024/238/t3/indiewebcamp-auto-linking→ https://tantek.com/2024/245/t1/read-write-suggest-edit-web
's status on Friday, 30-Aug-2024 00:09:00 EDT
Had a great time at IndieWebCamp Portland 2024 this past Sunday — our 10th IndieWebCamp in Portland! https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k Being a one day #IndieWebCamp, we focused more on making, hacking, and creating, than on formal discussion sessions. Nearly everyone gave a brief personal site intro with a summary of how they use their #IndieWeb site and what they would like to add, remove, or improve. * https://indieweb.org/2024/Portland/Intros There were lots of informal discussions, some in the main room, on the walk to and from lunch, over lunch in the nearby outdoor patio, or at tables inside the lobby of the Hotel Grand Stark. We wrapped up with our usual Create Day¹ Demos session, live streamed for remote attendees to see as well. Lots of great demos of things people built, designed, removed, cleaned-up, documented, and blogged! Everyone still at the camp showed something on their personal site! * https://indieweb.org/2024/Portland/Demos Group photo and lots more about IndieWebCamp Portland 2024 at the event’s wiki page: * https://indieweb.org/2024/Portland Thanks to everyone who pitched in to help organize IndieWebCamp Portland 2024! Thanks especially to Marty McGuire (@martymcgui.re) for taking live notes during both the personal site intros and create day demos, to Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) for the IndieWebCamp live-tooting, and Ryan Barrett (@snarfed.org) for amazing breakfast pastries from Dos Hermanos. The experience definitely raised our hopes and confidence for returning to Portland in 2025.² References: ¹ https://indieweb.org/Create_Day ² https://indieweb.org/Planning#Portland This is post 19 of #100PostsOfIndieWeb. #100Posts #2024_238 ← https://tantek.com/2024/238/t3/indiewebcamp-auto-linking → https://tantek.com/2024/245/t1/read-write-suggest-edit-web
: Had a great time at IndieWebCamp Portland 2024 this past Sunday — our 10th IndieWebCamp in Portland!https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0kBeing a one day #IndieWebCamp, we focused more on making, hacking, and creating, than on formal discussion sessions.Nearly everyone gave a brief personal site intro with a summary of how they use their #IndieWeb site and what they would like to add, remove, or improve.* https://indieweb.org/2024/Portland/IntrosThere were lots of informal discussions, some in the main room, on the walk to and from lunch, over lunch in the nearby outdoor patio, or at tables inside the lobby of the Hotel Grand Stark.We wrapped up with our usual Create Day¹ Demos session, live streamed for remote attendees to see as well. Lots of great demos of things people built, designed, removed, cleaned-up, documented, and blogged! Everyone still at the camp showed something on their personal site!* https://indieweb.org/2024/Portland/DemosGroup photo and lots more about IndieWebCamp Portland 2024 at the event’s wiki page:* https://indieweb.org/2024/PortlandThanks to everyone who pitched in to help organize IndieWebCamp Portland 2024! Thanks especially to Marty McGuire (@martymcgui.re) for taking live notes during both the personal site intros and create day demos, to @KevinMarks.com (@kevinmarks@xoxo.zone @kevinmarks @kevinmarks@indieweb.social) for the IndieWebCamp live-tooting, and Ryan Barrett (@snarfed.org) for amazing breakfast pastries from Dos Hermanos.The experience definitely raised our hopes and confidence for returning to Portland in 2025.²References:¹ https://indieweb.org/Create_Day² https://indieweb.org/Planning#PortlandThis is post 19 of #100PostsOfIndieWeb. #100Posts #2024_238← https://tantek.com/2024/238/t3/indiewebcamp-auto-linking→ 🔮
Had a great time at IndieWebCamp Portland 2024 this past Sunday — our 10th IndieWebCamp in Portland! https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k Being a one day #IndieWebCamp, we focused more on making, hacking, and creating, than on formal discussion sessions. Nearly everyone gave a brief personal site intro with a summary of how they use their #IndieWeb site and what they would like to add, remove, or improve. * https://indieweb.org/2024/Portland/Intros There were lots of informal discussions, some in the main room, on the walk to and from lunch, over lunch in the nearby outdoor patio, or at tables inside the lobby of the Hotel Grand Stark. We wrapped up with our usual Create Day¹ Demos session, live streamed for remote attendees to see as well. Lots of great demos of things people built, designed, removed, cleaned-up, documented, and blogged! Everyone still at the camp showed something on their personal site! * https://indieweb.org/2024/Portland/Demos Group photo and lots more about IndieWebCamp Portland 2024 at the event’s wiki page: * https://indieweb.org/2024/Portland Thanks to everyone who pitched in to help organize IndieWebCamp Portland 2024! Thanks especially to Marty McGuire (@martymcgui.re) for taking live notes during both the personal site intros and create day demos, to @KevinMarks.com (@kevinmarks@xoxo.zone @kevinmarks @kevinmarks@indieweb.social) for the IndieWebCamp live-tooting, and Ryan Barrett (@snarfed.org) for amazing breakfast pastries from Dos Hermanos. The experience definitely raised our hopes and confidence for returning to Portland in 2025.² References: ¹ https://indieweb.org/Create_Day ² https://indieweb.org/Planning#Portland This is post 19 of #100PostsOfIndieWeb. #100Posts #2024_238 ← https://tantek.com/2024/238/t3/indiewebcamp-auto-linking → 🔮
: People over protocols over platforms.inspired by today’s #indieweb #fediverse #ActivityPub #decentralized #socialMedia lunch meetup at #XOXO #XOXOConf (@xoxo@xoxo.zone)This is post 16 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/173/t1/years-posse-microformats-adoption→ 🔮
's status on Saturday, 24-Aug-2024 19:56:00 EDT
People over protocols over platforms. inspired by today’s #indieweb #fediverse #ActivityPub #decentralized #socialMedia lunch meetup at #XOXO #XOXOConf (@xoxo@xoxo.zone) This is post 16 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/173/t1/years-posse-microformats-adoption → 🔮
: Happy 12 years of https://indieweb.org/POSSE #POSSE and19 years of https://microformats.org/ #microformats! (as of yesterday, the 20th)A few highlights from the past year:POSSE (Publish on your Own Site, Syndicate Elsewhere) has grown steadily as a common practice in the #IndieWeb community, personal sites, CMSs (like Withknown, which itself reached 10 years in May!), and services (like https://micro.blog) for over a decade.In its 12th year, POSSE broke through to broader technology press and adoption beyond the community. For example:* David Pierce’s (@pierce@mas.to) excellent article @TheVerge.com (@verge@mastodon.social): “The poster’s guide to the internet of the future” (https://www.theverge.com/2023/10/23/23928550/posse-posting-activitypub-standard-twitter-tumblr-mastodon): “Your post appears natively on all of those platforms, typically with some kind of link back to your blog. And your blog becomes the hub for everything, your main home on the internet.Done right, POSSE is the best of all posting worlds.”* David also recorded a 29 minute podcast on POSSE with some great interviews: https://podcasts.apple.com/us/podcast/the-posters-guide-to-the-new-internet/id430333725?i=1000632256014* Cory Doctorow (@craphound.com @doctorow@mamot.fr) declared in his Pluralistic blog (@pluralisticmamot.fr) post: “Vice surrenders” (https://pluralistic.net/2024/02/24/anti-posse/): “This is the moment for POSSE (Post Own Site, Share Everywhere [sic]), a strategy that sees social media as a strategy for bringing readers to channels that you control” * And none other than Molly White (@mollywhite.net @molly0xfff@hachyderm.io) of @web3isgoinggreat.com (@web3isgreat@indieweb.social) built, deployed, and started actively using her own POSSE setup as described in her post titled “POSSE” (https://www.mollywhite.net/micro/entry/202403091817) to: "… write posts in the microblog and automatically crosspost them to Twitter/Mastodon/Bluesky, while keeping the original post on my site." Congrats Molly and well done!In its 19th year, the microformats formal #microformats2 syntax and popular vocabularies h-card, h-entry, and h-feed, kept growing across IndieWeb (micro)blogging services and software like CMSs & SSGs both for publishing, and richer peer-to-peer social web interactions via #Webmention.Beyond the IndieWeb, the rel=me microformat, AKA #relMe, continues to be adopted by services to support #distributed #verification, such as these in the past year: * Meta Platforms #Threads user profile "Link" field¹ * #Letterboxd user profile website field²For both POSSE and microformats, there is always more we can do to improve their techniques, technologies, and tools to help people own their content and identities online, while staying connected to friends across the web.Got suggestions for this coming year? Join us in chat:* https://chat.indieweb.org/dev* https://chat.indieweb.org/microformatsfor discussions about POSSE and microformats, respectively.Previously: https://tantek.com/2023/171/t1/anniversaries-microformats-posseThis is post 15 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/151/t1/minimum-interesting-service-worker→ 🔮Post glossary:CMS https://indieweb.org/CMSh-card https://microformats.org/wiki/h-cardh-entry https://microformats.org/wiki/h-entryh-feed https://microformats.org/wiki/h-feedmicroformats2 syntax https://microformats.org/wiki/microformats2-parsingrel-me https://microformats.org/wiki/rel-meSSG https://indieweb.org/SSGWebmention https://indieweb.org/WebmentionWithknown https://indieweb.org/KnownReferences:¹ https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me² https://indieweb.org/rel-me#Letterboxd
's status on Saturday, 22-Jun-2024 01:02:00 EDT
Happy 12 years of https://indieweb.org/POSSE #POSSE and 19 years of https://microformats.org/ #microformats! (as of yesterday, the 20th) A few highlights from the past year: POSSE (Publish on your Own Site, Syndicate Elsewhere) has grown steadily as a common practice in the #IndieWeb community, personal sites, CMSs (like Withknown, which itself reached 10 years in May!), and services (like https://micro.blog) for over a decade. In its 12th year, POSSE broke through to broader technology press and adoption beyond the community. For example: * David Pierce’s (@pierce@mas.to) excellent article @TheVerge.com (@verge@mastodon.social): “The poster’s guide to the internet of the future” (https://www.theverge.com/2023/10/23/23928550/posse-posting-activitypub-standard-twitter-tumblr-mastodon): “Your post appears natively on all of those platforms, typically with some kind of link back to your blog. And your blog becomes the hub for everything, your main home on the internet. Done right, POSSE is the best of all posting worlds.” * David also recorded a 29 minute podcast on POSSE with some great interviews: https://podcasts.apple.com/us/podcast/the-posters-guide-to-the-new-internet/id430333725?i=1000632256014 * Cory Doctorow (@craphound.com @doctorow@mamot.fr) declared in his Pluralistic blog (@pluralisticmamot.fr) post: “Vice surrenders” (https://pluralistic.net/2024/02/24/anti-posse/): “This is the moment for POSSE (Post Own Site, Share Everywhere [sic]), a strategy that sees social media as a strategy for bringing readers to channels that you control” * And none other than Molly White (@mollywhite.net @molly0xfff@hachyderm.io) of @web3isgoinggreat.com (@web3isgreat@indieweb.social) built, deployed, and started actively using her own POSSE setup as described in her post titled “POSSE” (https://www.mollywhite.net/micro/entry/202403091817) to: "… write posts in the microblog and automatically crosspost them to Twitter/Mastodon/Bluesky, while keeping the original post on my site." Congrats Molly and well done! In its 19th year, the microformats formal #microformats2 syntax and popular vocabularies h-card, h-entry, and h-feed, kept growing across IndieWeb (micro)blogging services and software like CMSs & SSGs both for publishing, and richer peer-to-peer social web interactions via #Webmention. Beyond the IndieWeb, the rel=me microformat, AKA #relMe, continues to be adopted by services to support #distributed #verification, such as these in the past year: * Meta Platforms #Threads user profile "Link" field¹ * #Letterboxd user profile website field² For both POSSE and microformats, there is always more we can do to improve their techniques, technologies, and tools to help people own their content and identities online, while staying connected to friends across the web. Got suggestions for this coming year? Join us in chat: * https://chat.indieweb.org/dev * https://chat.indieweb.org/microformats for discussions about POSSE and microformats, respectively. Previously: https://tantek.com/2023/171/t1/anniversaries-microformats-posse This is post 15 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/151/t1/minimum-interesting-service-worker → 🔮 Post glossary: CMS https://indieweb.org/CMS h-card https://microformats.org/wiki/h-card h-entry https://microformats.org/wiki/h-entry h-feed https://microformats.org/wiki/h-feed microformats2 syntax https://microformats.org/wiki/microformats2-parsing rel-me https://microformats.org/wiki/rel-me SSG https://indieweb.org/SSG Webmention https://indieweb.org/Webmention Withknown https://indieweb.org/Known References: ¹ https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me ² https://indieweb.org/rel-me#Letterboxd
: Yesterday I proposed the idea of a “minimum interesting service worker” that could provide a link (or links) to archives or mirrors when your site was unavailable as one possible solution to the desire to make personal #indieweb sites more reliable by providing at least a user path to “soft repair” links to your site that may otherwise seem broken.Minimum because it only requires two files and one line of script in site footer template, and interesting because it provides both a novel user benefit and personal site publisher benefits.The idea occurred to me during an informal coffee chat over Zoom with a couple of other Indieweb community folks yesterday, and afterwards I braindumped a bit into the IndieWeb Developers Chat channel¹. Figured it was worth writing up rather than waiting to implement it.Basic idea:You have a service worker (and “offline” HTML page) on your personal site, installed from any page on your site, that all it does is cache the offline page, and on future requests to your site checks to see if the requested page is available, and if so serves it, otherwise it displays your offline page with a “site appears to be unreachable” message that a lot of service workers provide, AND provides an algorithmically constructed link to the page on an archive (e.g. Internet Archive) or static mirror of your site (typically at another domain).This is minimal because it requires only two files: your service worker (a JS file) and your offline page (a minimal self-contained static HTML file with inline CSS). Doable in <1k bytes of code, with no additional local caching or storage requirements, thus a negligible impact on site visitors (likely less than the cookies that major sites store).User benefit:If someone has ever visited your personal site, then in the future whenever they click a link to your pages or posts, if your site/domain is unavailable for any reason, then the reader would see a notice (from your offline page) and a link to view an archive/mirror copy instead, thus providing a one-click ability for the reader to “soft-repair” any otherwise apparently broken links to your site.Personal site publisher benefits:Having such a service worker that automatically provides your readers links to where they can view your content on an archive or mirror means you can go on vacation or otherwise step away from your personal site, knowing that if it does go down, (at least prior) site visitors will still have a way to click-through and view your published content.Additional enhancements:Ideally any archive or mirror copies would use rel=canonical to link back to the page on your domain, so any crawlers or search engines could automatically prefer your original page, or browsers could offer the user a choice to “View original”. You can do that by including a rel=canonical link in all your original pages, so when they are archived or mirrored, those copies automatically include a rel=canonical link back to your original page or post.The simplest implementation would be to ping the Internet Archive to save² your page or post upon publishing it. You could also add code to your site to explicitly generate a static mirror of your pages, perhaps with an SSG or crawler like Spiderpig, to a GitHub repo, which is then auto-served as GitHub static pages, perhaps on its own domain yet at the same paths as your original pages (to make it trivial to generate such mirror links automatically).If you’re using links to the Internet Archive, you can generate them automatically by prefixing your page URL with https://web.archive.org/web/*/ e.g. this post:https://web.archive.org/web/*/https://tantek.com/2024/151/t1/minimum-interesting-service-workerPossible generic library:It may be possible to write this minimum interesting service worker (e.g. misv.js) as a generic (rather than site-specific) service worker that literally anyone with a personal site could “install” as is (a JS file, an HTML file, and a one-line script tag in their site-wide footer) and it would figure everything out from the context it is running in, unchanged (zero configuration necessary).This is post 14 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/072/t1/created-at-indiewebcamp-brighton→ 🔮Post glossary:GitHub static pages https://indieweb.org/GitHub_PagesHTML https://indieweb.org/HTMLJS https://indieweb.org/jsrel-canonical https://indieweb.org/rel-canonicalservice worker https://indieweb.org/service_workerSpiderpig https://indieweb.org/SpiderpigSSG https://indieweb.org/SSG References:¹ https://chat.indieweb.org/dev/2024-05-29#t1717006352142600² https://indieweb.org/Internet_Archive#Trigger_an_Archive
's status on Thursday, 30-May-2024 14:21:00 EDT
Yesterday I proposed the idea of a “minimum interesting service worker” that could provide a link (or links) to archives or mirrors when your site was unavailable as one possible solution to the desire to make personal #indieweb sites more reliable by providing at least a user path to “soft repair” links to your site that may otherwise seem broken. Minimum because it only requires two files and one line of script in site footer template, and interesting because it provides both a novel user benefit and personal site publisher benefits. The idea occurred to me during an informal coffee chat over Zoom with a couple of other Indieweb community folks yesterday, and afterwards I braindumped a bit into the IndieWeb Developers Chat channel¹. Figured it was worth writing up rather than waiting to implement it. Basic idea: You have a service worker (and “offline” HTML page) on your personal site, installed from any page on your site, that all it does is cache the offline page, and on future requests to your site checks to see if the requested page is available, and if so serves it, otherwise it displays your offline page with a “site appears to be unreachable” message that a lot of service workers provide, AND provides an algorithmically constructed link to the page on an archive (e.g. Internet Archive) or static mirror of your site (typically at another domain). This is minimal because it requires only two files: your service worker (a JS file) and your offline page (a minimal self-contained static HTML file with inline CSS). Doable in <1k bytes of code, with no additional local caching or storage requirements, thus a negligible impact on site visitors (likely less than the cookies that major sites store). User benefit: If someone has ever visited your personal site, then in the future whenever they click a link to your pages or posts, if your site/domain is unavailable for any reason, then the reader would see a notice (from your offline page) and a link to view an archive/mirror copy instead, thus providing a one-click ability for the reader to “soft-repair” any otherwise apparently broken links to your site. Personal site publisher benefits: Having such a service worker that automatically provides your readers links to where they can view your content on an archive or mirror means you can go on vacation or otherwise step away from your personal site, knowing that if it does go down, (at least prior) site visitors will still have a way to click-through and view your published content. Additional enhancements: Ideally any archive or mirror copies would use rel=canonical to link back to the page on your domain, so any crawlers or search engines could automatically prefer your original page, or browsers could offer the user a choice to “View original”. You can do that by including a rel=canonical link in all your original pages, so when they are archived or mirrored, those copies automatically include a rel=canonical link back to your original page or post. The simplest implementation would be to ping the Internet Archive to save² your page or post upon publishing it. You could also add code to your site to explicitly generate a static mirror of your pages, perhaps with an SSG or crawler like Spiderpig, to a GitHub repo, which is then auto-served as GitHub static pages, perhaps on its own domain yet at the same paths as your original pages (to make it trivial to generate such mirror links automatically). If you’re using links to the Internet Archive, you can generate them automatically by prefixing your page URL with https://web.archive.org/web/*/ e.g. this post: https://web.archive.org/web/*/https://tantek.com/2024/151/t1/minimum-interesting-service-worker Possible generic library: It may be possible to write this minimum interesting service worker (e.g. misv.js) as a generic (rather than site-specific) service worker that literally anyone with a personal site could “install” as is (a JS file, an HTML file, and a one-line script tag in their site-wide footer) and it would figure everything out from the context it is running in, unchanged (zero configuration necessary). This is post 14 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/072/t1/created-at-indiewebcamp-brighton → 🔮 Post glossary: GitHub static pages https://indieweb.org/GitHub_Pages HTML https://indieweb.org/HTML JS https://indieweb.org/js rel-canonical https://indieweb.org/rel-canonical service worker https://indieweb.org/service_worker Spiderpig https://indieweb.org/Spiderpig SSG https://indieweb.org/SSG References: ¹ https://chat.indieweb.org/dev/2024-05-29#t1717006352142600 ² https://indieweb.org/Internet_Archive#Trigger_an_Archive
: The Library of Infinite Loan is a physical world practice I conceived of many many years ago¹, implemented in minimal prototype form 5+ years ago², shared a summary with the #IndieWeb community at least four years ago at the #IndieWebCamp Austin in 2020³ and last year in IndieWeb chat⁴, so it’s about time⁵ I wrote it down. Summary: lend a #book from your personal library⁶ to a friend, on the conditions that they do not donate sell or dispose of it, and instead when they are done with it they return it or lend it to someone else who agrees to these conditions.My goal was to create a book lending system that:* preserves books — effectively in a giant #distributed communal #library* makes lending easier fiscally, psychologically, emotionally for both parties* encourages direct person-to-person lending without intermediaries* grows a culture of non-zero-sum sharing, preservation, and longterm thinkingThe basic steps to create a Library of Infinite Loan:1. Create a separate space (like a particular bookshelf) for #books to infinite lend. A small shelf in a guest room or common space like a hallway works well.2. Move books there that you are ok lending out and never seeing again3. Label that space your “Library of Infinite Loan”, or invite guests to borrow from your “Library of Infinite Loan”4. When visitors ask what that means, explain the RulesRules for borrowing from a Library of Infinite Loan (“the Rules”)1. Keep it as long as you like2. Do not sell donate or otherwise dispose of it3. You may give it a. back to the person you borrowed from b. or back to its original purchaser if they wrote their name and web address inside c. or (lend it) to someone else who agrees to the RulesThere are several ways to extend / expand the Library of Infinite Loan:* custom book plate: design a custom book plate for yourself with room for your name (and web address) on it e.g. “From Tantek’s (@tantek.com) Library” (with space), print it on longterm adhesive paper, and place it inside new books you purchase. When you move a book to your Library of Infinite Loan, amend the book plate to say ”… Library of Infinite Loan” and attach a copy of the Rules. * add a “borrowers log” with blank lines for anyone you lend it to or they lend it to, transitively, to optionally add their name, web address, and a date of borrowing. Then amend the rules to allow returning a book to who you borrowed from or anyone in the borrower log or original purchaser.* more media: CDs, vinyl records, DVDs, LaserDiscs, VHS, cassette tapes, video game cartridges etc.* other things * large tools — which usually come in a box with instruction manual, so there’s a logical place to put an “owners plate”, “borrowers log”, and copy of the rules. * artwork — a great way to rotate art among a communityThis is what I remember off the top of my head and with a little web searching. I know I have a bunch more notes in various places of my thoughts (and conversations) over the years about a Library of Infinite Loan. As I find those notes, I’ll post them as well.#infiniteLoan #libraryOfInfiniteLoanReferences:¹ I’m looking through old personal logs for earliest mentions of “infinite loan”² In my 2019 personal log I found a note that I “moved some books as library of infinite loan to guest room” where I had previously setup a small bookshelf for such books.³ https://indieweb.org/2020/Austin/reading⁴ https://chat.indieweb.org/2023-10-01#t1696202307311300⁵ I was also inspired by sharing the idea again to a couple of friends in an espresso-making livestream this morning⁶ https://indieweb.org/personal_library
's status on Monday, 29-Apr-2024 21:53:00 EDT
The Library of Infinite Loan is a physical world practice I conceived of many many years ago¹, implemented in minimal prototype form 5+ years ago², shared a summary with the #IndieWeb community at least four years ago at the #IndieWebCamp Austin in 2020³ and last year in IndieWeb chat⁴, so it’s about time⁵ I wrote it down. Summary: lend a #book from your personal library⁶ to a friend, on the conditions that they do not donate sell or dispose of it, and instead when they are done with it they return it or lend it to someone else who agrees to these conditions. My goal was to create a book lending system that: * preserves books — effectively in a giant #distributed communal #library * makes lending easier fiscally, psychologically, emotionally for both parties * encourages direct person-to-person lending without intermediaries * grows a culture of non-zero-sum sharing, preservation, and longterm thinking The basic steps to create a Library of Infinite Loan: 1. Create a separate space (like a particular bookshelf) for #books to infinite lend. A small shelf in a guest room or common space like a hallway works well. 2. Move books there that you are ok lending out and never seeing again 3. Label that space your “Library of Infinite Loan”, or invite guests to borrow from your “Library of Infinite Loan” 4. When visitors ask what that means, explain the Rules Rules for borrowing from a Library of Infinite Loan (“the Rules”) 1. Keep it as long as you like 2. Do not sell donate or otherwise dispose of it 3. You may give it a. back to the person you borrowed from b. or back to its original purchaser if they wrote their name and web address inside c. or (lend it) to someone else who agrees to the Rules There are several ways to extend / expand the Library of Infinite Loan: * custom book plate: design a custom book plate for yourself with room for your name (and web address) on it e.g. “From Tantek’s (@tantek.com) Library” (with space), print it on longterm adhesive paper, and place it inside new books you purchase. When you move a book to your Library of Infinite Loan, amend the book plate to say ”… Library of Infinite Loan” and attach a copy of the Rules. * add a “borrowers log” with blank lines for anyone you lend it to or they lend it to, transitively, to optionally add their name, web address, and a date of borrowing. Then amend the rules to allow returning a book to who you borrowed from or anyone in the borrower log or original purchaser. * more media: CDs, vinyl records, DVDs, LaserDiscs, VHS, cassette tapes, video game cartridges etc. * other things * large tools — which usually come in a box with instruction manual, so there’s a logical place to put an “owners plate”, “borrowers log”, and copy of the rules. * artwork — a great way to rotate art among a community This is what I remember off the top of my head and with a little web searching. I know I have a bunch more notes in various places of my thoughts (and conversations) over the years about a Library of Infinite Loan. As I find those notes, I’ll post them as well. #infiniteLoan #libraryOfInfiniteLoan References: ¹ I’m looking through old personal logs for earliest mentions of “infinite loan” ² In my 2019 personal log I found a note that I “moved some books as library of infinite loan to guest room” where I had previously setup a small bookshelf for such books. ³ https://indieweb.org/2020/Austin/reading ⁴ https://chat.indieweb.org/2023-10-01#t1696202307311300 ⁵ I was also inspired by sharing the idea again to a couple of friends in an espresso-making livestream this morning ⁶ https://indieweb.org/personal_library
: Last week I participated @W3.org (@w3c@w3c.social) #W3CAC (W3C Advisory Committee¹), #W3CAB (W3C Advisory Board² @ab@w3c.social), and #W3CBoard³ meetings in Hiroshima, Japan.The W3C Process⁴ describes the twice a year AC (Advisory Committee) Meetings⁵. In addition to members of the AC (one primary and one alternate per W3C Member Organization), the meetings are open to the AB (Advisory Board), the Board of the W3C Corporation, the #w3cTAG (W3C Technical Architecture Group⁶ @tag@w3c.social), Working Group⁷ chairs, Chapter⁸ staff, and this time also a W3C Invited Expert designated observer⁹.The AC currently meets in the Spring on its own and a shorter meeting in the Fall as part of the annual #W3CTPAC (W3C Technical Plenary and Advisory Committee¹⁰ meetings). The existence, dates, and location of the event are public¹¹, however the agenda, minutes, and registrants are generally Member-confidential. Since those individual links have their own access controls, I collected them on a publicly-viewable wiki page for easier discovery & navigation (if you work for a W3C Member Organization¹²): * https://www.w3.org/wiki/AC/Meetings#2024_SpringMost of the W3C meeting materials and discussions were also W3C Member-confidential, however a several of the presentations are publicly viewable, and a few more may be shared publicly after the fact.Myself and others at #W3C who believe in pushing for more openness and transparency in standards work, even (or especially) governance of said work, will be doing our best to work with others at W3C to continue shifting our work accordingly.Aside: I started the #OpenAB project when I was first elected to the AB (Advisory Board) in 2013, documenting it on the publicly viewable W3C Wiki, and updated it with the help of others since: https://www.w3.org/wiki/AB#Open_ABLike most conferences, I got as much out of side conversations at breaks (AKA hallway track¹³) and meals as I did from scheduled talks and panels.For now, here are the events, slides, and videos which are publicly viewable that provide an interesting glimpse into some of the topics discussed:* 📄 report: https://www.w3.org/reports/ai-web-impact/* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/engaging-the-members/* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/exploration/* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/OHCHR.pdf* ▶️ video 5m42s: https://customer-0kix77mxh2zzzae0.cloudflarestream.com/9ad1e01b20d9b15d413f02c0ada3fe34/watch* ▶️ video 4m16s: https://customer-0kix77mxh2zzzae0.cloudflarestream.com/1bfde2bf614d7535b8a775217a949974/watch* 🗓 event: https://www.w3.org/events/meetings/13213a52-8159-4af8-b939-38c7880ba266/* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/lt-deepfake/* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/lt-accessing-llms-data/* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/pac-data-sovereignty/ (nice #IndieWeb mention)* 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/intro-content-credentials.pdf* 🖼 slides: https://w3c.github.io/adapt/presentations/ac2024/ Warning: the proposed use of .well-known therein is IMO a bad mistake. Unnecessary reinvention (most handled by existing rel values¹⁴), more complex to author (requires sidefiles¹⁵), harder to publish (requires site admin root access), likely to become inaccurate (Ruby’s postulate¹⁶), and fragile (site admins frequently break .well-known for individual pages). A full critique likely requires its own blog post.* 🗓 event: https://www.w3.org/events/meetings/df0b9dd8-2356-47ec-839d-eadc06da1ca1/I’ll update this list with additional resources as they are made publicly viewable.If you work for a W3C Member Organization you can view the full list of resources linked from the Member-confidential agenda: https://www.w3.org/2024/04/AC/ac-agenda.html#mondayReferences:¹ https://w3.org/wiki/AC² https://w3.org/wiki/AB³ https://w3.org/wiki/Board⁴ https://www.w3.org/Consortium/Process/⁵ https://www.w3.org/2023/Process-20231103/#ACMeetings⁶ https://w3.org/tag⁷ https://www.w3.org/groups/wg/⁸ https://chapters.w3.org/⁹ https://www.w3.org/invited-experts/#ac-observer¹⁰ https://www.w3.org/wiki/TPAC¹¹ https://www.w3.org/events/ac/2024/ac-2024/¹² https://www.w3.org/membership/list/¹³ https://en.wiktionary.org/wiki/hallway_track¹⁴ https://microformats.org/wiki/existing-rel-values¹⁵ https://indieweb.org/sidefile-antipattern¹⁶ https://intertwingly.net/slides/2004/devcon/68.html
's status on Sunday, 14-Apr-2024 21:41:00 EDT
Last week I participated @W3.org (@w3c@w3c.social) #W3CAC (W3C Advisory Committee¹), #W3CAB (W3C Advisory Board² @ab@w3c.social), and #W3CBoard³ meetings in Hiroshima, Japan. The W3C Process⁴ describes the twice a year AC (Advisory Committee) Meetings⁵. In addition to members of the AC (one primary and one alternate per W3C Member Organization), the meetings are open to the AB (Advisory Board), the Board of the W3C Corporation, the #w3cTAG (W3C Technical Architecture Group⁶ @tag@w3c.social), Working Group⁷ chairs, Chapter⁸ staff, and this time also a W3C Invited Expert designated observer⁹. The AC currently meets in the Spring on its own and a shorter meeting in the Fall as part of the annual #W3CTPAC (W3C Technical Plenary and Advisory Committee¹⁰ meetings). The existence, dates, and location of the event are public¹¹, however the agenda, minutes, and registrants are generally Member-confidential. Since those individual links have their own access controls, I collected them on a publicly-viewable wiki page for easier discovery & navigation (if you work for a W3C Member Organization¹²): * https://www.w3.org/wiki/AC/Meetings#2024_Spring Most of the W3C meeting materials and discussions were also W3C Member-confidential, however a several of the presentations are publicly viewable, and a few more may be shared publicly after the fact. Myself and others at #W3C who believe in pushing for more openness and transparency in standards work, even (or especially) governance of said work, will be doing our best to work with others at W3C to continue shifting our work accordingly. Aside: I started the #OpenAB project when I was first elected to the AB (Advisory Board) in 2013, documenting it on the publicly viewable W3C Wiki, and updated it with the help of others since: https://www.w3.org/wiki/AB#Open_AB Like most conferences, I got as much out of side conversations at breaks (AKA hallway track¹³) and meals as I did from scheduled talks and panels. For now, here are the events, slides, and videos which are publicly viewable that provide an interesting glimpse into some of the topics discussed: * 📄 report: https://www.w3.org/reports/ai-web-impact/ * 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/engaging-the-members/ * 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/exploration/ * 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/OHCHR.pdf * ▶️ video 5m42s: https://customer-0kix77mxh2zzzae0.cloudflarestream.com/9ad1e01b20d9b15d413f02c0ada3fe34/watch * ▶️ video 4m16s: https://customer-0kix77mxh2zzzae0.cloudflarestream.com/1bfde2bf614d7535b8a775217a949974/watch * 🗓 event: https://www.w3.org/events/meetings/13213a52-8159-4af8-b939-38c7880ba266/ * 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/lt-deepfake/ * 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/lt-accessing-llms-data/ * 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/pac-data-sovereignty/ (nice #IndieWeb mention) * 🖼 slides: https://www.w3.org/2024/Talks/ac-slides/intro-content-credentials.pdf * 🖼 slides: https://w3c.github.io/adapt/presentations/ac2024/ Warning: the proposed use of .well-known therein is IMO a bad mistake. Unnecessary reinvention (most handled by existing rel values¹⁴), more complex to author (requires sidefiles¹⁵), harder to publish (requires site admin root access), likely to become inaccurate (Ruby’s postulate¹⁶), and fragile (site admins frequently break .well-known for individual pages). A full critique likely requires its own blog post. * 🗓 event: https://www.w3.org/events/meetings/df0b9dd8-2356-47ec-839d-eadc06da1ca1/ I’ll update this list with additional resources as they are made publicly viewable. If you work for a W3C Member Organization you can view the full list of resources linked from the Member-confidential agenda: https://www.w3.org/2024/04/AC/ac-agenda.html#monday References: ¹ https://w3.org/wiki/AC ² https://w3.org/wiki/AB ³ https://w3.org/wiki/Board ⁴ https://www.w3.org/Consortium/Process/ ⁵ https://www.w3.org/2023/Process-20231103/#ACMeetings ⁶ https://w3.org/tag ⁷ https://www.w3.org/groups/wg/ ⁸ https://chapters.w3.org/ ⁹ https://www.w3.org/invited-experts/#ac-observer ¹⁰ https://www.w3.org/wiki/TPAC ¹¹ https://www.w3.org/events/ac/2024/ac-2024/ ¹² https://www.w3.org/membership/list/ ¹³ https://en.wiktionary.org/wiki/hallway_track ¹⁴ https://microformats.org/wiki/existing-rel-values ¹⁵ https://indieweb.org/sidefile-antipattern ¹⁶ https://intertwingly.net/slides/2004/devcon/68.html
: @indieweb.org/POSSE in effect!Well done @joanwestenberg@threads.net 🙌🏻#POSSE threads https://www.threads.net/@joanwestenberg/post/C43gPbVSzPI:“Me: You should publish on your own website first, then other platforms. Me: Publishes on my own website first, then other platforms. Galaxy brains: HOW IRONIC YOU PUBLISH ON OTHER PLATFORMS” #IndieWeb
's status on Sunday, 24-Mar-2024 17:50:00 EDT
@indieweb.org/POSSE in effect! Well done @joanwestenberg@threads.net 🙌🏻 #POSSE threads https://www.threads.net/@joanwestenberg/post/C43gPbVSzPI: “Me: You should publish on your own website first, then other platforms. Me: Publishes on my own website first, then other platforms. Galaxy brains: HOW IRONIC YOU PUBLISH ON OTHER PLATFORMS” #IndieWeb
: While an HTML style element for inline CSS needs nothing but simple start and end tags (as of HTML5 and later) a more robust style element requires a precise series of overlapping code comments.Here is the answer if you want a code snippet to copy & paste Here is why:1. Not all HTML processors are CSS processors. While all modern browsers know how to parse CSS in style elements inside HTML, it is still quite reasonable for people to build HTML processors that do not, and many exist. There are plenty of ways that errant or deliberately misplaced markup inside a style element, like in a CSS comment, that such processors will not see, that can break them and cause unexpected and different results in different processors.Thus it makes your HTML more parseable, by more processors, if you can hide the entirety of the style sheet inside the style elmenet from such processing. A CDATA section does exactly that: here to not close the element */body > p { margin:1em } /* CDATA allows an unescaped > child combinator */ 2. However CSS syntax does not recognize a CDATA directive (even as of the latest published CSS Syntax Module Level 3¹ or editor's draft² as of this writing). CSS parsers may very well treat a CDATA directive as a syntax error that invalidates the subsequent style rule.Thus we must hide the CDATA directive, its opening and closing markup, from CSS parsers. CSS code comments /* ... */ can do exactly that: here to not close the element */body > p { margin:1em } /* CDATA allows an unescaped > child combinator *//* */ 3. This is close but still exposes HTML processors that do not process CSS to a minimal bit of content, the CSS comment opener and closer that are outside the CDATA section:/* */This recently showed up in a draft of the This Week in The #IndieWeb newsletter³, because portions of it are automatically constructed by parsing the HTML of MediaWiki pages for content, and one of those used a MediaWiki template that included a minimal style element to style the marked up content inserted by the template. A draft of the newsletter was showing raw CSS, extracted as text from the style element by the CSS-unaware parser extracting content. I was able to hide nearly all of it using CSS comments around the CDATA section opener and closer. Except for that little bit of CSS comment noise outside the CDATA section: /* */Fortunately there is one more tool in our toolbox that we can use. Simple HTML/SGML comments are ignored at the start and end of style sheets⁴ (noted there as CDO-token⁵ and CDC-token⁶), and thus we can use those to hide the last two remaining CSS comment pieces that were leaking out, like this: and . Note that the portion of the HTML comment directives that are inside CSS comments are ignored by CSS processors, which is why this works for both processors that parse CSS and those that do not.This last addition produces our answer, with no fewer than three different comment mechanisms (CDATA, CSS, HTML/SGML), overlapping to hide each other from different processors: here to not close the element */body > p { margin:1em } /* CDATA allows an unescaped > child combinator *//* By replacing those informative style rules with a style rule to be deleted, we have recreated the code snippet to copy & paste from the top of the post: Q.E.D.Afterword:If you View Source on this original permalink or my home page you can see the more robust style element in a real world example, following the IndieWeb Use What You Make⁷ principle.#CSS #style #styleElement #styleSheet #HTML #HTML5 #CSSsyntax #codecommentsGlossary:CDATA https://en.wikipedia.org/wiki/CDATACSS — Cascading Style Sheets https://en.wikipedia.org/wiki/CSSHTML — HyperText Markup Language https://en.wikipedia.org/wiki/HTMLHTML5 https://en.wikipedia.org/wiki/HTML5IndieWeb Principles https://indieweb.org/principlesMediaWiki https://en.wikipedia.org/wiki/MediaWikioriginal permalink https://indieweb.org/original_permalinkQ.E.D. https://en.wikipedia.org/wiki/Q.E.D.References:¹ https://www.w3.org/TR/css-syntax-3/² https://drafts.csswg.org/css-syntax/³ https://indieweb.org/this-week-in-the-indieweb ⁴ https://www.w3.org/TR/css-syntax-3/#stylesheet-diagram⁵ https://www.w3.org/TR/css-syntax-3/#CDO-token-diagram⁶ https://www.w3.org/TR/css-syntax-3/#CDC-token-diagram⁷ https://indieweb.org/use_what_you_make
's status on Saturday, 16-Mar-2024 00:35:00 EDT
While an HTML style element for inline CSS needs nothing but simple start and end tags (as of HTML5 and later) a more robust style element requires a precise series of overlapping code comments. Here is the answer if you want a code snippet to copy & paste Here is why: 1. Not all HTML processors are CSS processors. While all modern browsers know how to parse CSS in style elements inside HTML, it is still quite reasonable for people to build HTML processors that do not, and many exist. There are plenty of ways that errant or deliberately misplaced markup inside a style element, like in a CSS comment, that such processors will not see, that can break them and cause unexpected and different results in different processors. Thus it makes your HTML more parseable, by more processors, if you can hide the entirety of the style sheet inside the style elmenet from such processing. A CDATA section does exactly that: here to not close the element */ body > p { margin:1em } /* CDATA allows an unescaped > child combinator */ 2. However CSS syntax does not recognize a CDATA directive (even as of the latest published CSS Syntax Module Level 3¹ or editor's draft² as of this writing). CSS parsers may very well treat a CDATA directive as a syntax error that invalidates the subsequent style rule. Thus we must hide the CDATA directive, its opening and closing markup, from CSS parsers. CSS code comments /* ... */ can do exactly that: here to not close the element */ body > p { margin:1em } /* CDATA allows an unescaped > child combinator */ /* */ 3. This is close but still exposes HTML processors that do not process CSS to a minimal bit of content, the CSS comment opener and closer that are outside the CDATA section: /* */ This recently showed up in a draft of the This Week in The #IndieWeb newsletter³, because portions of it are automatically constructed by parsing the HTML of MediaWiki pages for content, and one of those used a MediaWiki template that included a minimal style element to style the marked up content inserted by the template. A draft of the newsletter was showing raw CSS, extracted as text from the style element by the CSS-unaware parser extracting content. I was able to hide nearly all of it using CSS comments around the CDATA section opener and closer. Except for that little bit of CSS comment noise outside the CDATA section: /* */ Fortunately there is one more tool in our toolbox that we can use. Simple HTML/SGML comments are ignored at the start and end of style sheets⁴ (noted there as CDO-token⁵ and CDC-token⁶), and thus we can use those to hide the last two remaining CSS comment pieces that were leaking out, like this: and . Note that the portion of the HTML comment directives that are inside CSS comments are ignored by CSS processors, which is why this works for both processors that parse CSS and those that do not. This last addition produces our answer, with no fewer than three different comment mechanisms (CDATA, CSS, HTML/SGML), overlapping to hide each other from different processors: here to not close the element */ body > p { margin:1em } /* CDATA allows an unescaped > child combinator */ /* By replacing those informative style rules with a style rule to be deleted, we have recreated the code snippet to copy & paste from the top of the post: Q.E.D. Afterword: If you View Source on this original permalink or my home page you can see the more robust style element in a real world example, following the IndieWeb Use What You Make⁷ principle. #CSS #style #styleElement #styleSheet #HTML #HTML5 #CSSsyntax #codecomments Glossary: CDATA https://en.wikipedia.org/wiki/CDATA CSS — Cascading Style Sheets https://en.wikipedia.org/wiki/CSS HTML — HyperText Markup Language https://en.wikipedia.org/wiki/HTML HTML5 https://en.wikipedia.org/wiki/HTML5 IndieWeb Principles https://indieweb.org/principles MediaWiki https://en.wikipedia.org/wiki/MediaWiki original permalink https://indieweb.org/original_permalink Q.E.D. https://en.wikipedia.org/wiki/Q.E.D. References: ¹ https://www.w3.org/TR/css-syntax-3/ ² https://drafts.csswg.org/css-syntax/ ³ https://indieweb.org/this-week-in-the-indieweb ⁴ https://www.w3.org/TR/css-syntax-3/#stylesheet-diagram ⁵ https://www.w3.org/TR/css-syntax-3/#CDO-token-diagram ⁶ https://www.w3.org/TR/css-syntax-3/#CDC-token-diagram ⁷ https://indieweb.org/use_what_you_make
: What I created while remotely participating at #IndieWebCamp Brighton 2024: wiki-gardened day 1’s BarCamp sessions notes pages, and documented my @-mention @-@-mention autolinking coding improvements I built the Sunday before.Day 2 of IndieWebCamps is Create Day, where everyone is encouraged to create, make, or build something for their personal website, or the IndieWeb community, or both.At the start of day 2, everyone is encourage to pick things to make¹. What to make at an IndieWebCamp² can be anything from setting up your personal website, to writing a blog post, redesigning your styling, building new features, helping other participants, or contributing to shared IndieWeb community resources, whether code or content. Everyone is encouraged to at least pick something they consider easy, that they can do in less than an hour, then a more bold goal, and then perhaps a stretch goal, something challenging that may require collaboration, asking for help, or breaking into smaller steps.For my "easy" task, I built on what another remote participant, @gregorlove.com completed the night before. gRegor had archived all the IndieWebCamp Brighton Sessions Etherpads onto the wiki, linked from the Schedule page³. gRegor had noted that he didn’t have time to clean-up the pages, e.g. convert and fix Markdown links.I went through the 13 Session Notes archives and did the following:* converted Markdown links to MediaWiki links* converted indieweb.org (and some services) links to local wiki page links* fixed (some) typosWith some help from @alexsirac.com (@alexture@todo.eu), I figured out how to create a MediaWiki Contributions summary link of my edits:* https://indieweb.org/wiki/index.php?title=Special:Contributions&target=Tantek.com&namespace=all&start=2024-03-10&end=2024-03-10&offset=20240310143900&limit=25I point this out to provide an example of an IndieWeb Create Day project that is:* incremental on top of someone else’s work* community contribution rather a personal-focused project* editing and wiki-gardening as valid contributions, not just creating new contentI point this out to illustrate some of the IndieWeb community's recognitions & values in contrast to typical corporate cultures and incentive systems which often only reward:* new innovations (not incremental improvements)* solo (or maybe jointly in a small team) inventions, designs, specs, or implementations* something large, a new service or a big feature, not numerous small edits & fixesIn this regard, the IndieWeb community shares more in common with Wikipedia and similar collaborative communities (despite the #Indie in #IndieWeb), than any corporation.For my "more bold" goal, I wrote a medium-sized post about the auto-linking improvements I made the Sunday before the IndieWebCamp to my personal website with examples and brief descriptions of the coding changes & improvements.* https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-casesMy stretch goal was to write up a more complete auto-linking specification, based on the research I have done into @-mention @-@-mention user practices (on #Mastodon, other #ActivityPub or #fediverse implementations, and even across #socialMedia silos), as well as how implementations link URLs, domains, and paths.That stretch goal remains a goal, however I did collect a handful of prior posts on @-mentions which I plan to source for specifying auto-linking and @-mentioning:* https://tantek.com/2023/011/t1/indieweb-evolving-at-mention* https://tantek.com/2023/014/t4/domain-first-federated-atmention* https://tantek.com/2023/018/t1/elevate-indieweb-above-silo* https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo* https://tantek.com/2023/109/t2/years-ago-first-federated-indieweb-thread#autoLink #atDomain #atPath #atMention #atMentions #atat #atAtMentionI was one of a few remote participants in addition to ~18 in-person participants, the overwhelming majority of overall attendees, who demonstrated something at the end of IndieWebCamp Brighton 2024 day 2. See what everyone else made & demonstrated on Create Day:* https://indieweb.org/2024/Brighton/DemosThis is post 13 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases→ 🔮Glossary:Create Day https://indieweb.org/Create_DayIndieWebCamp Brighton 2024 https://indieweb.org/2024/BrightonReferences:¹ https://indieweb.org/IndieWebCamps/Attending#Day_Two² https://indieweb.org/what_to_make_at_IndieWebCamp³ https://indieweb.org/2024/Brighton/Schedule#Saturday
's status on Tuesday, 12-Mar-2024 22:19:00 EDT
What I created while remotely participating at #IndieWebCamp Brighton 2024: wiki-gardened day 1’s BarCamp sessions notes pages, and documented my @-mention @-@-mention autolinking coding improvements I built the Sunday before. Day 2 of IndieWebCamps is Create Day, where everyone is encouraged to create, make, or build something for their personal website, or the IndieWeb community, or both. At the start of day 2, everyone is encourage to pick things to make¹. What to make at an IndieWebCamp² can be anything from setting up your personal website, to writing a blog post, redesigning your styling, building new features, helping other participants, or contributing to shared IndieWeb community resources, whether code or content. Everyone is encouraged to at least pick something they consider easy, that they can do in less than an hour, then a more bold goal, and then perhaps a stretch goal, something challenging that may require collaboration, asking for help, or breaking into smaller steps. For my "easy" task, I built on what another remote participant, @gregorlove.com completed the night before. gRegor had archived all the IndieWebCamp Brighton Sessions Etherpads onto the wiki, linked from the Schedule page³. gRegor had noted that he didn’t have time to clean-up the pages, e.g. convert and fix Markdown links. I went through the 13 Session Notes archives and did the following: * converted Markdown links to MediaWiki links * converted indieweb.org (and some services) links to local wiki page links * fixed (some) typos With some help from @alexsirac.com (@alexture@todo.eu), I figured out how to create a MediaWiki Contributions summary link of my edits: * https://indieweb.org/wiki/index.php?title=Special:Contributions&target=Tantek.com&namespace=all&start=2024-03-10&end=2024-03-10&offset=20240310143900&limit=25 I point this out to provide an example of an IndieWeb Create Day project that is: * incremental on top of someone else’s work * community contribution rather a personal-focused project * editing and wiki-gardening as valid contributions, not just creating new content I point this out to illustrate some of the IndieWeb community's recognitions & values in contrast to typical corporate cultures and incentive systems which often only reward: * new innovations (not incremental improvements) * solo (or maybe jointly in a small team) inventions, designs, specs, or implementations * something large, a new service or a big feature, not numerous small edits & fixes In this regard, the IndieWeb community shares more in common with Wikipedia and similar collaborative communities (despite the #Indie in #IndieWeb), than any corporation. For my "more bold" goal, I wrote a medium-sized post about the auto-linking improvements I made the Sunday before the IndieWebCamp to my personal website with examples and brief descriptions of the coding changes & improvements. * https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases My stretch goal was to write up a more complete auto-linking specification, based on the research I have done into @-mention @-@-mention user practices (on #Mastodon, other #ActivityPub or #fediverse implementations, and even across #socialMedia silos), as well as how implementations link URLs, domains, and paths. That stretch goal remains a goal, however I did collect a handful of prior posts on @-mentions which I plan to source for specifying auto-linking and @-mentioning: * https://tantek.com/2023/011/t1/indieweb-evolving-at-mention * https://tantek.com/2023/014/t4/domain-first-federated-atmention * https://tantek.com/2023/018/t1/elevate-indieweb-above-silo * https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo * https://tantek.com/2023/109/t2/years-ago-first-federated-indieweb-thread #autoLink #atDomain #atPath #atMention #atMentions #atat #atAtMention I was one of a few remote participants in addition to ~18 in-person participants, the overwhelming majority of overall attendees, who demonstrated something at the end of IndieWebCamp Brighton 2024 day 2. See what everyone else made & demonstrated on Create Day: * https://indieweb.org/2024/Brighton/Demos This is post 13 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases → 🔮 Glossary: Create Day https://indieweb.org/Create_Day IndieWebCamp Brighton 2024 https://indieweb.org/2024/Brighton References: ¹ https://indieweb.org/IndieWebCamps/Attending#Day_Two ² https://indieweb.org/what_to_make_at_IndieWebCamp ³ https://indieweb.org/2024/Brighton/Schedule#Saturday
: New this week: the #IndieWeb community deployed a major modern update to the design, usability, and cross-device support of the https://indieweb.org/ home page and wiki in general! In brief:* Updated MediaWiki install, updated themes, better mobile device support* New default theme: Vector (2022), the same as English Wikipedia* Lots of CSS fixes for content, sidebars, etc.* Home page content simplification and more pleasing design updateLots more details on the 2024 homepage and design update project page:* https://indieweb.org/2024/homepageThis was a community effort, with many people pitching in with major & minor contributions, spending weeks, days, hours, or a few minutes here and there helping out. From server work, to PHP coding, to HTML+CSS (re)coding, to testing variants of MediaWiki themes, browsers, and devices.Huge thanks in particular to @PaulRobertLloyd.com for both driving this design update (e.g. said project page) and doing the heavy lifting of debugging, patching, and testing the latest MediaWiki Vector theme, documenting before & after screenshots, and @AaronParecki.com for all the server-side software updates, PHP/IndieAuth wrangling, and critical devops too.Go try the new https://indieweb.org/ on any browser, on any device, and share your experience!#IndieNewsThis is post 11 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/046/t1/the-ephemeral-web→ 🔮
's status on Friday, 16-Feb-2024 17:25:00 EST
New this week: the #IndieWeb community deployed a major modern update to the design, usability, and cross-device support of the https://indieweb.org/ home page and wiki in general! In brief: * Updated MediaWiki install, updated themes, better mobile device support * New default theme: Vector (2022), the same as English Wikipedia * Lots of CSS fixes for content, sidebars, etc. * Home page content simplification and more pleasing design update Lots more details on the 2024 homepage and design update project page: * https://indieweb.org/2024/homepage This was a community effort, with many people pitching in with major & minor contributions, spending weeks, days, hours, or a few minutes here and there helping out. From server work, to PHP coding, to HTML+CSS (re)coding, to testing variants of MediaWiki themes, browsers, and devices. Huge thanks in particular to @PaulRobertLloyd.com for both driving this design update (e.g. said project page) and doing the heavy lifting of debugging, patching, and testing the latest MediaWiki Vector theme, documenting before & after screenshots, and @AaronParecki.com for all the server-side software updates, PHP/IndieAuth wrangling, and critical devops too. Go try the new https://indieweb.org/ on any browser, on any device, and share your experience! #IndieNews This is post 11 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/046/t1/the-ephemeral-web → 🔮