CINXE.COM

<!DOCTYPE html> <html lang="en-US"> <head> <meta charset="UTF-8"/> <title lang="tr" style="text-transform:uppercase">Tantek Çelik</title> <meta name="viewport" content="width=device-width, initial-scale=1.0"/> <link rel="icon" href="logo.jpg"/> <link rel="apple-touch-icon-precomposed" href="logo.jpg"/> <meta name="mobile-web-app-capable" content="yes"/> <link rel="webmention" href="https://webmention.io/tantek.com/webmention"/> <link rel="hub" href="https://pubsubhubbub.superfeedr.com/"/> <link rel="openid.delegate" href="https://tantek.com/"/> <link rel="openid.server" href="https://indieauth.com/openid"/> <link rel="authorization_endpoint" href="https://indieauth.com/auth"/> <link rel="token_endpoint" href="https://tokens.indieauth.com/token"/> <link rel="microsub" href="https://aperture.p3k.io/microsub/277"/> <link rel="alternate" type="text/mf2+html" href="#updates"/> <link rel="alternate" type="application/atom+xml" href="updates.atom"/> <link rel="serviceworker" href="serviceworker.js"/> <link rel="me" href="https://fed.brid.gy/r/https://tantek.com/"/> <link rel="me" href="https://xoxo.zone/@t"/> <link rel="author canonical self" href="https://tantek.com/"/> <link rel="author" type="application/activity+json" href="https://tantek.com/@tantek.com"> <style> */ /* HTML5+CSS work in progress. Copy paste AT YOUR OWN RISK! */ @import "2023/simple.css"; h2 { font-size:1em; } body { margin:auto; padding:1.6em; max-width:940px; } iframe { max-width:100%; } abbr { text-decoration:none } .header { border-bottom:solid 1px #666; margin-top:0; margin-bottom:1em; } .header h1 { margin:0; padding:5px 0 0; font-size:3em; line-height:1.3; font-weight:bold; white-space:nowrap; } .header h2 { font-size:1.5em; font-weight:normal; line-height:1em; min-width:20em; min-height:3em; margin:0; } .aside dt, .aside dd {margin:0;padding:0} .aside dt { margin-top:.77em; color:#666; } .aside dd { color:#000} .aside img { max-width:100% } form.search { clear: right; text-align: right; margin-bottom: 1em; white-space: nowrap; font-size: 1.3em; } .stream>ol { margin:0; padding:0; } /* div.stream li.h-entry .figure { margin:0 -1em; } */ span.see-more { display:inline; } .interact img, .p-org.h-card img, .p-category.h-card img { height:1.4em; vertical-align:-.3em } @media screen and (min-width:40em) { /* progressive enhance wider screens */ span.see-more { display:none; } body { padding:2em; } .header { height:90px; margin-top:1.3em } form.search { margin-top: -3.9em; width: 34%; float: right; } .stream { clear:left; float:left; width:62%; margin-right:4%; } .stream>ol { margin-right:3em; } .hentry ol, .hentry ul { margin-left:30px; } .aside { float:left; width:33%; } .footer .section { float:left; width:30%; margin-right:3%; } div.stream li.h-entry .figure { margin:0; } .aside .recent-photos { margin-left:0; margin-right:0; } .aside .recent-photos h2 { margin-left:0; } } /* end wider screen enhancements */ .photo { width:73px; float:left; margin:0 20px 0 0; } form.search input[type=search] { width:62%; } form.search input, form.search button { font-size:1em; height:1.7em; -moz-box-sizing: border-box; box-sizing: border-box; margin:0; vertical-align:bottom; } .stream>ol { list-style:none; } .aside h2,.footer h2 { font-size: 1.3em; text-transform:uppercase; line-height:1.25; margin:0 0 1em; } .aside .section { margin-top:2em; } .aside .section.hello { margin-top:0; } .aside .section h2 { margin-bottom:0.5em; } .aside p,.aside li,.aside dl,.footer p,.footer li { font-size:1.3em; line-height:1.54; margin:0; color: #AAA; /* #666; */ list-style:none; } /*.hello p { color:#000; }*/ .elsewhere img { vertical-align:bottom; padding-bottom:.2em; } .aside h2 { font-size:1.5em; line-height:1.43; font-weight:bold; } .aside .recent-photos { margin-left:-1.5em; margin-right:-1.5em; padding:0; } .aside .recent-photos h2 { margin-left:1em; } div.footer { margin-left:1em; clear:both; margin-top:1em; padding-top:5em; } .footer address { white-space:nowrap; } .footer p { margin-top:1em; } .footer .section li { list-style:disc inside; } address { font-style:normal; text-align:center; clear:both; margin:1em 5%; padding:3em; } ul.nav,.nav li,ul.offsite { list-style:none; } ul.nav { float:right; margin-right: 5%; } ul.offsite,.offsite li,.nav li { list-style:inline; display:inline; } #a:link { color: #D0D044; /* color:#2240C0;*/ } #a:link:hover { color:#F0F088; /* color:#22B040;*/ } #a:visited { color:#66D; } #a:visited:hover { color:#99F; /* color:#88D0F0;*/ /* color:#118020; */ } /* events */ #events li.vevent { list-style:none;margin-top:1em; } #events abbr.location { display:block; text-align:center; text-transform:uppercase; font-weight:bold; font-size:2em; word-spacing:-.1em; font-size:1.5em; } #events li.vevent a { display:block; width:167px; text-align:center; color:inherit; border:2px solid; padding:2px 1px 0 1px; } #events li.vevent object,.vevent img { max-width:160px } #events li.vevent .with { display:block } .subhead { display:block } .html5 { display:block; padding-top:3px; color:#3C790A; font-family: Helvetica, sans-serif; font-weight: 900; font-size: 27px; line-height:.7em; } .html5 span { display:block; font-size:66%; line-height:1em; text-transform:capitalize; } #events .vevent a:visited:hover { color:#66F; } #events .vevent a:link:hover { color:#33F; } input,button { font-size:1em; } button { margin: 0 0.5em 0 0; padding:0 0.5em; } kbd { color: #000 } /* </style> </head> <body class="h-card vcard"> <header><div class="header"> <img class="photo u-photo" src="photo.jpg" alt=""/><a class="u-url u-uid" rel="author" href="/"></a> <div class="hgroup" style="margin-bottom:-1em"> <h1 class="p-name fn" lang="tr">Tantek Çelik</h1> <h2 class="p-role role"> inventor, connector, writer, runner, scientist, <a href="#hello">more</a>. </h2> </div> <a href="//tantek.com/contact"><abbr title="Message Tantek">💬</abbr></a> <a rel="payment" href="//tantek.com/tip/1" title="Tip: Did you read something of value here and want to encourage more posts like that? Feel free to tip a small amount and mention which topics you enjoyed! (Just please avoid specific products or services. Thanks! -t)">👏 </a> <search role="search"><form class="search" action="https://duckduckgo.com/html/" method="get"><div> <input type="hidden" name="type" value="list"/> <input type="search" value="site:tantek.com " name="q" style="max-width:10.5em"/> <button type="submit">Search</button> </div></form></search> </div></header>  <div class="h-feed section stream" id="updates"> <div class="pinned"></div> <ol> <li class="h-entry hentry as-note"> “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”<a id="t5b51_ref-1" href="#t5b51_note-1">¹</a> 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”<a id="t5b51_ref-2" href="#t5b51_note-2">²</a>) * <a class="auto-link" href="https://tantek.com/w/InboxZero">https://tantek.com/w/InboxZero</a> (2009-01-29 <a class="auto-link" href="https://tantek.com/twttr/status/1160324190">https://tantek.com/twttr/status/1160324190</a>) This is post 10 of #100PostsOfIndieWeb. #100Posts ← <a class="auto-link" href="https://tantek.com/2025/055/t1/three-steps-indieweb-cybersecurity">https://tantek.com/2025/055/t1/three-steps-indieweb-cybersecurity</a> → 🔮 Glossary blog   <a class="auto-link" href="https://indieweb.org/blog">https://indieweb.org/blog</a> blogging   <a class="auto-link" href="https://indieweb.org/blogging">https://indieweb.org/blogging</a> permalink   <a class="auto-link" href="https://indieweb.org/permalink">https://indieweb.org/permalink</a> why blog   <a class="auto-link" href="https://indieweb.org/why_post">https://indieweb.org/why_post</a> References <a id="t5b51_note-1" href="#t5b51_ref-1">¹</a> <a class="auto-link" href="https://libre.fm/artist/Missing+Persons/track/Words">https://libre.fm/artist/Missing+Persons/track/Words</a> (YouTube link inside) <a id="t5b51_note-2" href="#t5b51_ref-2">²</a> <a class="auto-link" href="https://libre.fm/artist/The+Fixx/track/Saved+by+Zero">https://libre.fm/artist/The+Fixx/track/Saved+by+Zero</a> (YouTube link inside) <a href="/2025/077/t1/what-are-words-for-blogging" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="18:25-0700">18:25</time> on <time class="value">2025-03-18</time></a> </li> <li class="h-entry hentry as-note"> ❤️ to <a href="https://github.com/w3c/AB-public/issues/211#issuecomment-2725722320" class="u-in-reply-to h-cite">a comment on issue 211 of GitHub project “AB-public”</a> <a href="/2025/073/t1/" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="14:07-0700">14:07</time> on <time class="value">2025-03-14</time></a> </li> <li class="h-entry hentry as-note"> ↳ In reply to <a href="https://bsky.app/profile/did:plc:pgjpl4opnmqxxpb74n4vuabv/post/3lk3zexogbc2l" class="u-in-reply-to h-cite">bsky.app’s post</a> Thanks <a class="auto-link" href="https://zeldman.com">@zeldman.com</a> (<a class="auto-link" href="https://zeldman.bsky.social">@zeldman.bsky.social</a> <a class="auto-link" href="https://front-end.social/@zeldman">@zeldman@front-end.social</a> <a class="auto-link h-cassis-username" href="https://twitter.com/zeldman">@zeldman</a>) 🙏🏻 Appreciate your kind words, and same appreciation of your decades of dedicated work & words right back at you. I feel we’re all doing what we can to keep at least parts of the web a positive place to connect and collaborate. #indieweb These recent words of yours (tweeted 2024-11-26) struck a chord that resonated: “Our euphoria during the first 25 years of web design turns out to have significantly overestimated human intelligence, compassion, and decency.” Here’s to decades more work & words, perhaps with some acceptance of your observation, and shifting our designs to meet people where they are, enabling and encouraging them to be and do better. <a href="/2025/071/t3/thanks-doing-what-we-can" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="17:18-0700">17:18</time> on <time class="value">2025-03-12</time></a> </li> <li class="h-entry hentry as-note"> Something I wrote in the W3C Authentic Web Mini Workshop’s Zoom chat: Another implicit assumption (flaw) that is often a part of "purely technical solutions" is the neglect or ignorance (innocent naïveté) of existing technical solutions. A technical proposal should not be praised for what it claims to solve. A technical proposal must be evaluated by what marginal difference or advantage does it provide over existing technologies. Any technical proposal that ignores prior technologies is itself doomed to be ignored by the next technical proposal. In addition to the slide presentations (links to come) in the mini workshop and Zoom verbal discussion which was minuted (link to come), there was a lot of very interesting discussion in the Zoom chat, which was not minuted. Sometimes such quick back & forth can help inspire summarizing of points which one had not previously written down. I was encouraged by a fellow workshop participant to blog this one so here it is! #W3C #credweb #credibleWeb #authenticWeb #technology #technical #proposal #technicalProposal #history <a href="/2025/071/t2/w3c-authentic-web-technical-proposals" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="14:45-0700">14:45</time> on <time class="value">2025-03-12</time></a> </li> <li class="h-entry hentry as-note"> I just participated in the first W3C Authentic Web Mini Workshop<a id="t5az1_ref-1" href="#t5az1_note-1">¹</a> hosted by the Credible Web Community Group<a id="t5az1_ref-2" href="#t5az1_note-2">²</a> (of which I’m a longtime member) and up front I noted that our very discussion itself needed to be careful about its own credibility, extra critical of any technologies discussed or assertions made, and initially identified two flaws to avoid on a meta level, having seen them occur many times in technical or standards discussions: 1. Politician’s Syllogism — "Something must be done about this problem. Here is something, let's do it!" 2. Solutions Looking For Problems — "I am interested in how tech X can solve problem Y" After some back and forth and arguments in the Zoom chat, I observed participants questioning speakers of arguments rather than the arguments themselves, so I had to identify a third fallacy to avoid: 3. Ad Hominem — while obvious examples are name-calling (which is usually against codes of conduct), less obvious examples (witnessed in the meeting) include questioning a speaker’s education (or lack thereof) like what they have or have not read, or would benefit from reading. I am blogging these here both as a reminder (should you choose to participate in such discussions), and as a resource to cite in future discussions. We need to all develop expertise in recognizing these logical and methodological flaws & fallacies, and call them out when we see them, especially when used against others. We need to promptly prune these flawed methods of discussion, so we can focus on actual productive, relevant, and yes, credible discussions. #W3C #credweb #credibleWeb #authenticWeb #flaw #fallacy #fallacies #logicalFallacy #logicalFallacies Glossary Ad Hominem   attacking an attribute of the person making an argument rather than the argument itself   <a class="auto-link" href="https://en.wikipedia.org/wiki/Ad_hominem">https://en.wikipedia.org/wiki/Ad_hominem</a> Politician's syllogism   <a class="auto-link" href="https://en.wikipedia.org/wiki/Politician%27s_syllogism">https://en.wikipedia.org/wiki/Politician%27s_syllogism</a> Solutions Looking For Problems (related: #solutionism, #solutioneering)   Promoting a technology that either has not identified a real problem for it to solve, or actively pitching a specific technology to any problem that seems related. Wikipedia has no page on this but has two related pages:   * <a class="auto-link" href="https://en.wikipedia.org/wiki/Law_of_the_instrument">https://en.wikipedia.org/wiki/Law_of_the_instrument</a>   * <a class="auto-link" href="https://en.wikipedia.org/wiki/Technological_fix">https://en.wikipedia.org/wiki/Technological_fix</a>   Wikipedia does have an essay on this specific to Wikipedia:   * <a class="auto-link" href="https://en.wikipedia.org/wiki/Wikipedia:Solutions_looking_for_a_problem">https://en.wikipedia.org/wiki/Wikipedia:Solutions_looking_for_a_problem</a>   Stack Exchange has a thread on "solution in search of a problem":   * <a class="auto-link" href="https://english.stackexchange.com/questions/250320/a-word-that-means-a-solution-in-search-of-a-problem">https://english.stackexchange.com/questions/250320/a-word-that-means-a-solution-in-search-of-a-problem</a>   Forbes has an illustrative anecdote:     * <a class="auto-link" href="https://www.forbes.com/sites/stephanieburns/2019/05/28/solution-looking-for-a-problem/">https://www.forbes.com/sites/stephanieburns/2019/05/28/solution-looking-for-a-problem/</a> References <a id="t5az1_note-1" href="#t5az1_ref-1">¹</a> <a class="auto-link" href="https://www.w3.org/events/workshops/2025/authentic-web-workshop/">https://www.w3.org/events/workshops/2025/authentic-web-workshop/</a> <a id="t5az1_note-2" href="#t5az1_ref-2">²</a> <a class="auto-link" href="https://credweb.org/">https://credweb.org/</a> and <a class="auto-link" href="https://www.w3.org/community/credibility/">https://www.w3.org/community/credibility/</a> Previously in 2019 I participated <a class="auto-link" href="https://misinfocon.com">@misinfocon.com</a> #MisinfoCon: * <a class="auto-link" href="https://tantek.com/2019/296/t1/london-misinfocon-discuss-spectrum-recency">https://tantek.com/2019/296/t1/london-misinfocon-discuss-spectrum-recency</a> * <a class="auto-link" href="https://tantek.com/2019/296/t2/misinfocon-roundtable-spectrums-misinformation">https://tantek.com/2019/296/t2/misinfocon-roundtable-spectrums-misinformation</a> <a href="/2025/071/t1/w3c-authentic-web-workshop-flaws" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="08:11-0700">08:11</time> on <time class="value">2025-03-12</time></a> </li> <li class="h-entry hentry as-note"> Ten years ago today I coined the shorthand “js;dr” for “JavaScript required; Didn’t Read” * <a class="auto-link" href="https://tantek.com/2015/069/t1/js-dr-javascript-required-dead">https://tantek.com/2015/069/t1/js-dr-javascript-required-dead</a> in reference to (primarily content) pages that were empty (or nearly so) without scripts. Since then js;dr found its way into a book: Page 88 of “Inclusive Design Patterns” by <a class="auto-link" href="https://heydonworks.com">@heydonworks.com</a> (<a class="auto-link" href="https://front-end.social/@heydon">@heydon@front-end.social</a>) <a class="auto-link figure" href="https://web.archive.org/web/20190405121431/https://twitter.com/jkphl/status/792452368562618369"><img class="auto-embed" alt="Cropped photo of part of page 88 of Inclusive Design Patterns at an angle" src="https://web.archive.org/web/20190405121448im_/https://pbs.twimg.com/media/Cv9bNjYW8AAHOac.jpg"/></a> and stickers! <a class="auto-link figure" href="https://kvalhe.im/@andrew/103211689652698610"><img class="auto-embed" alt="A hand holding about a dozen stickers with the “js;dr” in black on white text die-cut around the edges of the lettering" src="https://andrew.kvalhe.im/+gcs1iho7eqcknyiqxtjm5qadxi366ewu?x=.jpg"/></a> At the time I made the claim that: “in 10 years nothing you built today that depends on JS for the content will be available, visible, or archived anywhere on the web.” I’ve seen and documented many such sites, built with a hard dependency on scripting, that end up dead and unarchived. Many of these have been documented on the IndieWeb’s js;dr page: * <a class="auto-link" href="https://indieweb.org/js;dr">https://indieweb.org/js;dr</a> I have to ask though: does anyone remember building a site 10 years ago (Internet Archive citation) with a Javascript library/framework dependency to display content, that still works today? E.g. using one of the popular libraries/frameworks used to build such sites back then like AngularJS (discontinued 2022), Backbone.js, Ember.js, or even React which was still quite new at the time. The one almost exception I found was Facebook, e.g. this Smashing Magazine post on Facebook barely renders some content and all commentary is missing, in the earliest (2019) version saved on the Internet Archive: * <a class="auto-link" href="https://web.archive.org/web/20191123225253/https://www.facebook.com/smashmag/posts/10153198367332490">https://web.archive.org/web/20191123225253/https://www.facebook.com/smashmag/posts/10153198367332490</a> You can extract the direct Facebook link if you want to try viewing it in the present. Regarding those libraries/frameworks themselves, I wrote: “All your fancy front-end-JS-required frameworks are dead to history, a mere evolutionary blip in web app development practices. Perhaps they provided interesting ephemeral prototypes, nothing more.” Of all those listed above, only React has grown since, likely at the expense of the others. However instead of fewer such libraries and frameworks today, it seems we have many more (though it feels like their average hypespan is getting shorter with each iteration). Since I wrote “js;dr”, the web has only become more fragile, with ever more dependencies on scripting just to display text content. The irony here is that Javascript, like XML, has draconian parsing rules. One syntax error and the whole script is thrown out. This means it’s far too easy for any such JS-dependent site to break, in one or more browsers, whenever browsers change, or Javascript changes, or both. You wouldn’t build a site today (or 20 years ago) that depends on fragile draconian XML parsing, so why build a site that depends on fragile draconian Javascript parsing? I’ll repeat my claim from ten years ago, slightly amended, and shortened: In 5 years nothing you (personally, not a publicly traded company) build today that depends on Javascript in the browser to display content will be available, visible, or archived anywhere on the web. There’s a lot more to unpack about what we’ve collectively lost in the past ten years of fragile scripting-dependent site-deaths, and why web developers are choosing to build more fragile websites than they did 10 or certainly 20 years ago. For now I’ll leave you with a few positive encouragements: Practice Progressive Enhancement. Build first and foremost with forgiving technologies, declarative technologies, and forward and backward compatible coding techniques. All content should be readable without scripting. Links, buttons, text fields, and any other interactive HTML elements should all work without scripting. Scripts are great for providing an enhanced user experience, or additional functionality such as offline support. Then make sure to test your pages and sites without scripts, to make sure they still work. If it's worth building on the web, it's worth building it robustly, and building it to last. <a href="/2025/069/t1/ten-years-jsdr-javascript-required-didnt-read" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="19:55-0700">19:55</time> on <time class="value">2025-03-10</time></a> </li> <li class="h-entry hentry as-note"> 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: <a class="auto-link" href="https://tantek.com/2025/052/b1/steps-indieweb-cybersecurity">https://tantek.com/2025/052/b1/steps-indieweb-cybersecurity</a> Next time: entropy is your friend in security. If you want my #Cybersecurity Friday posts as soon as I publish them, follow my site <a class="auto-link" href="https://tantek.com/">https://tantek.com/</a> 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: * <a class="auto-link" href="https://planet.mozilla.org/">https://planet.mozilla.org/</a> 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 ← <a class="auto-link" href="https://tantek.com/2025/020/t1/seek-2024-year-in-review">https://tantek.com/2025/020/t1/seek-2024-year-in-review</a> → 🔮 Glossary article post   <a class="auto-link" href="https://indieweb.org/article">https://indieweb.org/article</a> Atom   <a class="auto-link" href="https://indieweb.org/Atom">https://indieweb.org/Atom</a> content delivery network   <a class="auto-link" href="https://indieweb.org/content_delivery_network">https://indieweb.org/content_delivery_network</a> cybersecurity   <a class="auto-link" href="https://en.wikipedia.org/wiki/cybersecurity">https://en.wikipedia.org/wiki/cybersecurity</a> DNS   <a class="auto-link" href="https://indieweb.org/DNS">https://indieweb.org/DNS</a> domain registrar   <a class="auto-link" href="https://indieweb.org/domain_registrar">https://indieweb.org/domain_registrar</a> entropy   <a class="auto-link" href="https://en.wikipedia.org/wiki/Entropy_(information_theory)">https://en.wikipedia.org/wiki/Entropy_(information_theory)</a> feed reader   <a class="auto-link" href="https://indieweb.org/feed_reader">https://indieweb.org/feed_reader</a> h-feed   <a class="auto-link" href="https://indieweb.org/h-feed">https://indieweb.org/h-feed</a> MFA / 2FA   <a class="auto-link" href="https://indieweb.org/multi-factor_authentication">https://indieweb.org/multi-factor_authentication</a> sometimes called Two Factor Authentication or Second Factor Authentication mobile number for MFA   <a class="auto-link" href="https://indieweb.org/SMS#Criticism">https://indieweb.org/SMS#Criticism</a> note post   <a class="auto-link" href="https://indieweb.org/note">https://indieweb.org/note</a> social reader   <a class="auto-link" href="https://indieweb.org/social_reader">https://indieweb.org/social_reader</a> web host   <a class="auto-link" href="https://indieweb.org/web_hosting">https://indieweb.org/web_hosting</a> <a href="/2025/055/t1/three-steps-indieweb-cybersecurity" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="16:10-0800">16:10</time> on <time class="value">2025-02-24</time></a> </li> <li class="h-entry hentry as-article"> <div class="article"> <a href="/2025/052/b1/steps-indieweb-cybersecurity" rel="bookmark" class="u-url u-uid"><h1 class="entry-title p-name"> CSF_01: Three Steps for IndieWeb Cybersecurity </h1></a><div class="entry-content e-content"> Welcome to my first Cybersecurity Friday (<abbr>CSF</abbr>) post. Almost exactly one week ago I experienced (and had to fight & recover from) a cybersecurity incident. While that’s a much longer story, this post series is focused on sharing tips and incident learnings from an <a href="https://indieweb.social/tags/indieweb" class="hashtag"> #indieweb</a>-centric perspective. <h2>Steps for Cybersecurity</h2> Here are the top three steps in order of importance, that you should take <abbr title="as soon as possible">ASAP</abbr> to secure your online presence. <ol> <li> Email MFA/2FA. Add multi-factor authentication (<abbr>MFA</abbr>) using an actual Authenticator application to all places where you store or check email. Some services call this second factor or two factor authentication (<abbr>2FA</abbr>). While checking your email security settings, verify recovery settings: Do not cross-link your emails as recovery methods for each other, and do not use a mobile/cell number for recovery at all. </li> <li> Domain Registrar MFA. Add MFA to your Domain Registrar(s) if you have any. Optionally disable password reset emails if possible (some registrars may allow this). </li> <li> Web Host MFA. Add MFA to your web hosting service(s) if you have any. This includes both website hosting and any content delivery network (<abbr>CDN</abbr>) services you are using for your domains. </li> </ol> Do not use a mobile number for MFA, nor a physical/hardware key if you travel internationally. There are very good reasons to avoid doing so. I’ll blog the reasons in another post. Those are my top three recommended cybersecurity steps for protecting your internet presence. That’s it for this week. These are the bare minimum steps to take. There are many more steps you can take to strengthen your personal cybersecurity. I will leave you with this for now: Entropy is your friend in security. <h2>Glossary</h2> Glossary for various terms, phrases, and further reading on each. <dl> <dt>content delivery network</dt> <dd><a href="https://indieweb.org/content_delivery_network">https://indieweb.org/content_delivery_network</a></dd> <dt>cybersecurity</dt> <dd><a href="https://en.wikipedia.org/wiki/cybersecurity">https://en.wikipedia.org/wiki/cybersecurity</a></dd> <dt>domain registrar</dt> <dd><a href="https://indieweb.org/domain_registrar">https://indieweb.org/domain_registrar</a></dd> <dt>email recovery</dt> <dd>A method for recovering a service account password via the email account associated with that account. See also: <a href="https://en.wikipedia.org/wiki/Password_notification_email">https://en.wikipedia.org/wiki/Password_notification_email</a> </dd> <dt>entropy</dt> <dd><a href="https://en.wikipedia.org/wiki/Entropy_(information_theory)">https://en.wikipedia.org/wiki/Entropy_(information_theory)</a></dd> <dt> <abbr>MFA</abbr> / <abbr>2FA</abbr> </dt> <dd> <a href="https://indieweb.org/multi-factor_authentication">https://indieweb.org/multi-factor_authentication</a> sometimes called Two Factor Authentication or Second Factor Authentication </dd> <dt>mobile number for MFA</dt> <dd><a href="https://indieweb.org/SMS#Criticism">https://indieweb.org/SMS#Criticism</a></dd> <dt>web host</dt> <dd><a href="https://indieweb.org/web_hosting">https://indieweb.org/web_hosting</a></dd> </dl> Syndicated to: <a class="u-syndication" href="https://news.indieweb.org/en">IndieNews</a> </div> </div> <a href="/2025/052/b1/steps-indieweb-cybersecurity" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="13:37-0800">13:37</time> on <time class="value">2025-02-21</time></a> </li> <li class="h-entry hentry as-note"> Some solid #ResilienceStrategy advice in here: <a class="auto-link" href="https://bidenwhitehouse.archives.gov/wp-content/uploads/2025/01/National-Resilience-Strategy.pdf">https://bidenwhitehouse.archives.gov/wp-content/uploads/2025/01/National-Resilience-Strategy.pdf</a> (20 page PDF, a well-written quick read or skim) January 2025 "National Resilience Strategy:  A Vision for a More Resilient Nation" While explicitly a #NationalResilienceStrategy, it has a lot of sound guidance for understanding, analyzing, and developing a resilience strategy at all levels, for yourself and your home, with your neighbors and relationships, to civic resilience, and beyond. Here is an overview of the sections, to get an idea (if you avoid PDFs), and to help with discovery across various services: * The Need for Collective Action toward National Resilience * Defining Resilience   * Adaptive   * Protective   * Collaborative   * Fair and Just   * Human-Centered   * Interdependent   * Sustainable and Durable * Understanding the Resilience Landscape * Strategic Approach to Build Attributes of a Resilient Nation * Throughlines of a Resilient Nation   * Cross-system and cross-sector use of resources   * Resilience manifests in adaptive capacity and communities   * Layered resilience   * Cascading reliance   * Environmental hazards, including climate change   * Technology innovation and digital transformation   * Cyber infrastructure   * Iterative continuous feedback loops   * Supply chains   * Robust safety nets * Resilience Pillars   * Pillar I: Governance Systems   * Pillar II: Social and Community Systems   * Pillar III: Economic Systems   * Pillar IV: Infrastructure Systems * Conclusion And yes the text contents of the PDF include the terms #diversity #diverse #equity #equitable #inclusivity #inclusive, in many contexts (including and beyond the ones that may come to mind). Related: <a class="auto-link" href="https://tantek.com/2025/011/t1/remembering-aaronsw-twelve-years">https://tantek.com/2025/011/t1/remembering-aaronsw-twelve-years</a> Previously, previously: * <a class="auto-link" href="https://tantek.com/2024/336/t1/disruptions-how-to-prepare">https://tantek.com/2024/336/t1/disruptions-how-to-prepare</a> * <a class="auto-link" href="https://tantek.com/2024/313/t1/reflecting-listening-thoughts">https://tantek.com/2024/313/t1/reflecting-listening-thoughts</a> #NationalResilience #Resilience #Strategy #Biden #BidenWhitehouse <a href="/2025/034/t1/national-resilience-strategy" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="12:10-0800">12:10</time> on <time class="value">2025-02-03</time></a> </li> <li class="h-entry hentry as-note"> ↳ In reply to <a href="https://github.com/mozilla/standards-positions/issues/27" class="u-in-reply-to h-cite">issue 27 of GitHub project “standards-positions”</a> Note that since this issue was opened, the spec was adopted by the Web Apps WG, and published as a W3C Recommendation as of 2023-05-30: * <a class="auto-link" href="https://www.w3.org/TR/2023/REC-web-share-20230530/">https://www.w3.org/TR/2023/REC-web-share-20230530/</a> Updated latest editor’s draft AKA * Specification or proposal URL: <a class="auto-link" href="https://w3c.github.io/web-share/">https://w3c.github.io/web-share/</a> Dropping label "position:positive" until we resolve the conflicts between negative, neutral, and positive historical comments upthread, to avoid miscommunicating our position (which is semi-orthogonal to any implementation status — see individual bugs cited above for that). <a href="/2025/028/t2/" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="04:42-0800">04:42</time> on <time class="value">2025-01-28</time></a> </li> <li class="h-entry hentry as-note"> ↳ In reply to <a href="https://github.com/mozilla/standards-positions/issues/27" class="u-in-reply-to h-cite">issue 27 of GitHub project “standards-positions”</a> Re-opening this due to unresolved comments (mix of negative, neutral, positive), and substantial new information about the UI that current implementations are presenting as of 2025. Previously, previously, previously: * 2018-01-10 <a class="auto-link" href="https://github.com/mozilla/standards-positions/issues/27#issuecomment-356793352">https://github.com/mozilla/standards-positions/issues/27#issuecomment-356793352</a> “harmful” * 2018-01-10 <a class="auto-link" href="https://github.com/mozilla/standards-positions/issues/27#issuecomment-356784523">https://github.com/mozilla/standards-positions/issues/27#issuecomment-356784523</a> “pour more fuel on the centralization” * 2017-12-18 <a class="auto-link" href="https://github.com/mozilla/standards-positions/issues/27#issuecomment-352661649">https://github.com/mozilla/standards-positions/issues/27#issuecomment-352661649</a> “lowers friction purely for content silos … bad for the web.” And a minor unaddressed concern from Martin: * 2018-11-08 <a class="auto-link" href="https://github.com/mozilla/standards-positions/issues/27#issuecomment-437243973">https://github.com/mozilla/standards-positions/issues/27#issuecomment-437243973</a> “Giving sites the ability to share something else reduces the incentive to set window.location to something usable” Since those concerns were written (validated by screenshots at the time showing centralized content / social media silos in browser UI), it appears browsers (perhaps OS updates) no longer show such silos in browser UI for “share” (as of 2025). Need updated screenshots. <a href="/2025/028/t1/" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="04:21-0800">04:21</time> on <time class="value">2025-01-28</time></a> </li> <li class="h-entry hentry as-note"> 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 (<a class="auto-link" href="https://www.inaturalist.org/pages/seek_app">https://www.inaturalist.org/pages/seek_app</a>), 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 ← <a class="auto-link" href="https://tantek.com/2025/012/t1/eight-years-webmention">https://tantek.com/2025/012/t1/eight-years-webmention</a> → <a class="auto-link" href="https://tantek.com/2025/055/t1/three-steps-indieweb-cybersecurity">https://tantek.com/2025/055/t1/three-steps-indieweb-cybersecurity</a> Glossary: login wall   <a class="auto-link" href="https://indieweb.org/login_wall">https://indieweb.org/login_wall</a> offline first   <a class="auto-link" href="https://indieweb.org/offline_first">https://indieweb.org/offline_first</a> <a href="/2025/020/t1/seek-2024-year-in-review" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="14:04-0800">14:04</time> on <time class="value">2025-01-20</time></a> </li> <li class="h-entry hentry as-note"> 16 years ago today I wrote up and posted a proposal for a new calendar: <a class="auto-link" href="http://newcal.org">newcal.org</a> Having long been frustrated by unnecessary unevenness and other quirks of the Gregorian calendar, I designed and wrote up a more ordered, mathematically simpler, and more continuously consistent calendar. Building up from the atomic calendar unit of a 'day': * five day weeks * six week (30 day) months * two month (60 day) + a sync day bims<a id="t5a31_ref-1" href="#t5a31_note-1">¹</a> * six bim years (minus a day for non-leap-years) After giving it an obvious name, “New Calendar”, and somehow getting a short speakable .org domain (<a class="auto-link" href="http://newcal.org">newcal.org</a>), I wrote code to do all the calendar computations and conversions. The simpler calendar computations made me realize I had invented something that would help solve a completely different problem I was working on: an efficient date-based storage format for my new blog. It‘s rare that an invention, or reinvention of something inelegant, actually serves a useful purpose. This was one of those rare exceptions. I also taught myself and have kept practicing the use of ISO 8601 Ordinal dates for my own personal calendaring, which literally gave me a new perspective of time. A much smoother and more linear progression of time across the duration of a year. Previously: <a class="auto-link" href="https://tantek.com/2019/015/t1/10-years-ago-today-new-calendar">https://tantek.com/2019/015/t1/10-years-ago-today-new-calendar</a> <a id="t5a31_note-1" href="#t5a31_ref-1">¹</a> <a class="auto-link" href="https://tantek.com/2015/228/t3/bim-definition">https://tantek.com/2015/228/t3/bim-definition</a> <a id="t5a31_note-2" href="#t5a31_ref-2">²</a> <a class="auto-link" href="https://en.wikipedia.org/wiki/ISO_8601#Ordinal_dates">https://en.wikipedia.org/wiki/ISO_8601#Ordinal_dates</a> <a href="/2025/015/t1/16-years-ago-new-calendar-simpler" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="18:03-0800">18:03</time> on <time class="value">2025-01-15</time></a> </li> <li class="h-entry hentry as-note"> 🎉 Eight years ago today, the #IndieWeb Webmention protocol was published as a W3C REC <a class="auto-link" href="https://www.w3.org/TR/webmention/">https://www.w3.org/TR/webmention/</a> 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, have 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<a id="t5a01_ref-1" href="#t5a01_note-1">¹</a> 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. Fortunately there is a CSS property, 'unicode-bidi', that can be used to directionally 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; } Previously: <a class="auto-link" href="https://tantek.com/2023/012/t1/six-years-webmention-w3c">https://tantek.com/2023/012/t1/six-years-webmention-w3c</a> This is post 7 of #100PostsOfIndieWeb. #100Posts #socialWeb #openSocialWeb ← <a class="auto-link" href="https://tantek.com/2025/004/t1/micro-one-onramp-open-social-web">https://tantek.com/2025/004/t1/micro-one-onramp-open-social-web</a> → <a class="auto-link" href="https://tantek.com/2025/020/t1/seek-2024-year-in-review">https://tantek.com/2025/020/t1/seek-2024-year-in-review</a> Glossary HTML class name   <a class="auto-link" href="https://tantek.com/2012/353/b1/why-html-classes-css-class-selectors">https://tantek.com/2012/353/b1/why-html-classes-css-class-selectors</a> IndieWeb chat   <a class="auto-link" href="https://indieweb.org/discuss">https://indieweb.org/discuss</a> pixelate   <a class="auto-link" href="https://indieweb.org/pixelated">https://indieweb.org/pixelated</a> small pieces, loosely joined   <a class="auto-link" href="https://www.smallpieces.com/">https://www.smallpieces.com/</a> Unicode directional formatting characters   <a class="auto-link" href="https://en.wikipedia.org/wiki/Bidirectional_text#Explicit_formatting">https://en.wikipedia.org/wiki/Bidirectional_text#Explicit_formatting</a> unicode-bidi CSS property   <a class="auto-link" href="https://developer.mozilla.org/en-US/docs/Web/CSS/unicode-bidi">https://developer.mozilla.org/en-US/docs/Web/CSS/unicode-bidi</a>   References <a id="t5a01_note-1" href="#t5a01_ref-1">¹</a> <a class="auto-link" href="https://chat.indieweb.org/dev/2025-01-05#t1736092889120900">https://chat.indieweb.org/dev/2025-01-05#t1736092889120900</a> <a href="/2025/012/t1/eight-years-webmention" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="21:23-0800">21:23</time> on <time class="value">2025-01-12</time></a> </li> <li class="h-entry hentry as-note"> remembering losing #aaronsw twelve years ago today, and drawing connections with: * Lawrence Lessig’s <a class="auto-link" href="https://lessig.tumblr.com/post/56888930628/on-the-emptiness-in-the-concept-of-neutrality">https://lessig.tumblr.com/post/56888930628/on-the-emptiness-in-the-concept-of-neutrality</a> * Ben Werdmüller’s <a class="auto-link" href="https://werd.io/2025/building-an-open-web-that-protects-us-from-harm">https://werd.io/2025/building-an-open-web-that-protects-us-from-harm</a> Two points of connection: 1. Neutrality in ethical or policy matters is insufficient, empty, and cowardly. Especially when you know better, neutrality in action is not ethical, it is negligent and wrong, like a lie of omission. “Allyship demands more than neutrality — it demands action.” — <a class="auto-link" href="https://werd.io">@werd.io</a> (<a class="auto-link" href="https://werd.social/@ben">@ben@werd.social</a>) “… there are obviously plenty of contexts in which to be ‘neutral’ is simply to be wrong. ” <a class="auto-link" href="https://lessig.org">@lessig.org</a> (<a class="auto-link" href="https://lessig.tumblr.com">@lessig.tumblr.com</a> <a class="auto-link" href="https://mastodon.world/@lessig">@lessig@mastodon.world</a> <a class="auto-link h-cassis-username" href="https://twitter.com/lessig">@lessig</a>) 2. Building community for collective action is required for resilient resistance Aaron helped inspire and drive numerous acts of resistance against foes better funded and connected, many acts which succeeded to some degree or completely such as preventing the passage of SOPA.<a id="t5_z1_ref-1" href="#t5_z1_note-1">¹</a> Similarly he built community for collective action, such as co-founding the Progressive Change Campaign Committee and the Demand Progress political advocacy group<a id="t5_z1_ref-2" href="#t5_z1_note-2">²</a> which remain active to this day. One of the best ways to honor Aaron’s memory is to build on the good examples he set that succeeded and continue to succeed. The only neutrality that Aaron supported was net neutrality, prioritizing those that use the internet over those that build & serve it, a priority of constituencies strongly aligned with the W3C’s official Ethical Web Principles.<a id="t5_z1_ref-3" href="#t5_z1_note-3">³</a> If you too reject neutrality and instead embrace allyship & action, some of those actions will require resisting the status quo with the intent of changing it. If resistance with the goal of actual change is your primary objective (rather than recognition), build community to bring about that change, resist collectively not alone, both in the near term, and sustainably into the future. Still miss you Aaron. Previously: * <a class="auto-link" href="https://tantek.com/2024/013/t1/remembering-aaronsw-eleven-years">https://tantek.com/2024/013/t1/remembering-aaronsw-eleven-years</a> (links to prior posts) <a id="t5_z1_note-1" href="#t5_z1_ref-1">¹</a> <a class="auto-link" href="https://en.wikipedia.org/wiki/Aaron_Swartz#Opposition_to_the_Stop_Online_Piracy_Act_(SOPA)">https://en.wikipedia.org/wiki/Aaron_Swartz#Opposition_to_the_Stop_Online_Piracy_Act_(SOPA)</a> <a id="t5_z1_note-2" href="#t5_z1_ref-2">²</a> <a class="auto-link" href="https://en.wikipedia.org/wiki/Aaron_Swartz#Progressive_Change_Campaign_Committee">https://en.wikipedia.org/wiki/Aaron_Swartz#Progressive_Change_Campaign_Committee</a> <a id="t5_z1_note-3" href="#t5_z1_ref-3">³</a> <a class="auto-link" href="https://www.w3.org/TR/ethical-web-principles/#noharm">https://www.w3.org/TR/ethical-web-principles/#noharm</a> <a href="/2025/011/t1/remembering-aaronsw-twelve-years" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="23:23-0800">23:23</time> on <time class="value">2025-01-11</time></a> </li> <li class="h-entry hentry as-note"> Alan Watts wrote in the “The World As Emptiness”: “So in the same way, the coming and going of things in the world is marvelous. They go. Where do they go? Don’t answer, because that would spoil the mystery.” I have to disagree with Watts here. Do ask and DO answer. Again and again. Embrace curiosity, explanation, understanding. Any mystery you can explain will reveal another mystery underneath. There is no spoiling the mystery, there is only the journey of one mystery after another. #meditationThoughts #Kula #meditation #liveMeditation #groupMeditation #AlanWatts #mystery <a href="/2025/005/t1/alan-watts-mystery-curiosity" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="10:23-0800">10:23</time> on <time class="value">2025-01-05</time></a> </li> <li class="h-entry hentry as-note"> The team <a class="auto-link" href="https://micro.blog">@micro.blog</a> have done it again. They soft-launched <a class="auto-link" href="https://micro.one">https://micro.one</a> yesterday<a id="t5_s1_ref-1" href="#t5_s1_note-1">¹</a>. 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<a id="t5_s1_ref-2" href="#t5_s1_note-2">²</a>. Stop posting in someone else’s garage<a id="t5_s1_ref-3" href="#t5_s1_note-3">³</a>. 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 <a class="auto-link" href="https://micro.one/about/pricing">https://micro.one/about/pricing</a> 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 <a class="auto-link" href="https://micro.one/about/indieweb">https://micro.one/about/indieweb</a> Did I mention the the superb <a class="auto-link" href="http://micro.blog">micro.blog</a> (and <a class="auto-link" href="http://micro.one">micro.one</a>) Community Guidelines? * <a class="auto-link" href="https://help.micro.blog/t/community-guidelines/39">https://help.micro.blog/t/community-guidelines/39</a> Well done <a class="auto-link" href="https://manton.org">@manton.org</a> and team. This is post 6 of #100PostsOfIndieWeb. #100Posts #ownYourIdentity #ownYourData #openSocialWeb ← <a class="auto-link" href="https://tantek.com/2025/003/t1/lastfm-year-in-review-playback24">https://tantek.com/2025/003/t1/lastfm-year-in-review-playback24</a> → <a class="auto-link" href="https://tantek.com/2025/012/t1/eight-years-webmention">https://tantek.com/2025/012/t1/eight-years-webmention</a> Glossary IndieAuth   <a class="auto-link" href="https://indieweb.org/IndieAuth">https://indieweb.org/IndieAuth</a> microformats   <a class="auto-link" href="https://microformats.org/wiki/microformats">https://microformats.org/wiki/microformats</a> Micropub   <a class="auto-link" href="https://indieweb.org/Micropub">https://indieweb.org/Micropub</a> Microsub   <a class="auto-link" href="https://indieweb.org/Microsub">https://indieweb.org/Microsub</a> Webmention   <a class="auto-link" href="https://indieweb.org/Webmention">https://indieweb.org/Webmention</a> References <a id="t5_s1_note-1" href="#t5_s1_ref-1">¹</a> <a class="auto-link" href="https://www.manton.org/2025/01/03/microone-was-effectively-a-softlaunch.html">https://www.manton.org/2025/01/03/microone-was-effectively-a-softlaunch.html</a> <a id="t5_s1_note-2" href="#t5_s1_ref-2">²</a> <a class="auto-link" href="https://tantek.com/2025/001/t1/15-years-notes-my-site-first">https://tantek.com/2025/001/t1/15-years-notes-my-site-first</a> <a id="t5_s1_note-3" href="#t5_s1_ref-3">³</a> <a class="auto-link" href="https://tantek.com/2023/022/t2/own-your-notes-domain-migration">https://tantek.com/2023/022/t2/own-your-notes-domain-migration</a> <a href="/2025/004/t1/micro-one-onramp-open-social-web" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="20:48-0800">20:48</time> on <time class="value">2025-01-04</time></a> </li> <li class="h-entry hentry as-note"> Yesterday <a class="auto-link" href="https://last.fm/">https://last.fm/</a> (<a class="auto-link h-cassis-username" href="https://twitter.com/lastfm">@lastfm</a>) 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.<a id="t5_r1_ref-1" href="#t5_r1_note-1">¹</a> They’re also available on the web, without requiring a native mobile app to view. Mine is here: <a class="auto-link" href="https://www.last.fm/user/tantekc/listening-report/year">https://www.last.fm/user/tantekc/listening-report/year</a> You can find yours (if you’re a <a class="auto-link" href="http://last.fm">last.fm</a> user) by going here: * <a class="auto-link" href="https://www.last.fm/user/_/listening-report/year">https://www.last.fm/user/_/listening-report/year</a> 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 ← <a class="auto-link" href="https://tantek.com/2025/002/t1/indieweb-third-place-community">https://tantek.com/2025/002/t1/indieweb-third-place-community</a> → <a class="auto-link" href="https://tantek.com/2025/004/t1/micro-one-onramp-open-social-web">https://tantek.com/2025/004/t1/micro-one-onramp-open-social-web</a> Glossary: scrobble   <a class="auto-link" href="https://indieweb.org/scrobble">https://indieweb.org/scrobble</a> year in review   <a class="auto-link" href="https://indieweb.org/year_in_review">https://indieweb.org/year_in_review</a> <a id="t5_r1_note-1" href="#t5_r1_ref-1">¹</a> <a class="auto-link" href="https://tantek.com/2025/001/t2/first-new-year-review-prior">https://tantek.com/2025/001/t2/first-new-year-review-prior</a> <a href="/2025/003/t1/lastfm-year-in-review-playback24" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="22:00-0800">22:00</time> on <time class="value">2025-01-03</time></a> </li> <li class="h-entry hentry as-note"> 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 <a class="auto-link" href="https://indieweb.org/">https://indieweb.org/</a> as well as the heterogeneous chat <a class="auto-link" href="https://chat.indieweb.org/">https://chat.indieweb.org/</a>. We also have many services run by individuals (or small teams) in the community, for the benefit of the community, like: * <a class="auto-link" href="https://snarfed.org">@snarfed.org</a>’s <a class="auto-link" href="https://brid.gy/">https://brid.gy/</a> and <a class="auto-link" href="https://fed.brid.gy/">https://fed.brid.gy/</a> * <a class="auto-link" href="https://aaronparecki.com">@aaronparecki.com</a>’s <a class="auto-link" href="https://webmention.io/">https://webmention.io/</a> and many others * <a class="auto-link" href="https://martymcgui.re">@martymcgui.re</a>’s <a class="auto-link" href="https://xn--sr8hvo.ws/">https://xn--sr8hvo.ws/</a> (IndieWeb Webring) * <a class="auto-link" href="https://gregorlove.com">@gregorlove.com</a>’s <a class="auto-link" href="https://indiebookclub.biz/">https://indiebookclub.biz/</a> * <a class="auto-link" href="https://mat.tl">@mat.tl</a>’s <a class="auto-link" href="https://libre.fm/">https://libre.fm/</a> 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 ← <a class="auto-link" href="https://tantek.com/2025/001/t3/strava-year-in-sport-how-to-get-info-save">https://tantek.com/2025/001/t3/strava-year-in-sport-how-to-get-info-save</a> → <a class="auto-link" href="https://tantek.com/2025/003/t1/lastfm-year-in-review-playback24">https://tantek.com/2025/003/t1/lastfm-year-in-review-playback24</a> <a href="/2025/002/t1/indieweb-third-place-community" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="23:54-0800">23:54</time> on <time class="value">2025-01-02</time></a> </li> <li class="h-entry hentry as-note"> 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<a id="t5_p3_ref-1" href="#t5_p3_note-1">¹</a> 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!<a id="t5_p3_ref-2" href="#t5_p3_note-2">²</a>) 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 of your sports. 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 * other aspects of your activities (if you have the info)   * ⛰ mountains summited (new, per sport, and/or total different and overall)   * 🏔 snow-peaks summited (new, per sport, total different and overall)   * 🌋 calderas summited (new, per sport, total different and overall)   * personal leaderboards for your summited mountains     * top 5 most summited (per mountain)     * top 5 highest elevation mountains summited   * number of different cities, states, countries (new, per sport, total)   * 🏁 number of races you ran, biked etc. (and finished, if not the same)   * 🗓 total days raced (if different from number of races, per sport, total)   * 🪧 total distance you raced (per sport, total)   * 🆙 total elevation you raced (per sport, total)   * ⏱ total time spent racing (per sport, total)   * ⛰ mountains summited in races (new, per sport, total)   * 🏔 snow-peaks summited in races (new, per sport, total)   * 🌋 calderas summited (new, per sport, total different and overall) * 🏅🏆 number of (or full set of) awards or trophies you earned at races * 🖼 photo of all your medals and/or trophies if any * 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<a id="t5_p3_ref-3" href="#t5_p3_note-3">³</a> 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 ← <a class="auto-link" href="https://tantek.com/2025/001/t2/first-new-year-review-prior">https://tantek.com/2025/001/t2/first-new-year-review-prior</a> → <a class="auto-link" href="https://tantek.com/2025/002/t1/indieweb-third-place-community">https://tantek.com/2025/002/t1/indieweb-third-place-community</a> Glossary: hashtag   <a class="auto-link" href="https://indieweb.org/hashtag">https://indieweb.org/hashtag</a> own your data   <a class="auto-link" href="https://indieweb.org/own_your_data">https://indieweb.org/own_your_data</a> <a id="t5_p3_note-1" href="#t5_p3_ref-1">¹</a> <a class="auto-link" href="https://tantek.com/2025/001/t2/first-new-year-review-prior">https://tantek.com/2025/001/t2/first-new-year-review-prior</a> <a id="t5_p3_note-2" href="#t5_p3_ref-2">²</a> <a class="auto-link" href="https://support.strava.com/hc/en-us/articles/22067973274509-Your-Year-in-Sport#h_01HH5VW132BPDTEZJZDHBGJ6KM">https://support.strava.com/hc/en-us/articles/22067973274509-Your-Year-in-Sport#h_01HH5VW132BPDTEZJZDHBGJ6KM</a> <a id="t5_p3_note-3" href="#t5_p3_ref-3">³</a> <a class="auto-link" href="https://indieweb.org/year_in_review">https://indieweb.org/year_in_review</a> <a href="/2025/001/t3/strava-year-in-sport-how-to-get-info-save" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="17:04-0800">17:04</time> on <time class="value">2025-01-01</time></a> </li> <li class="h-entry hentry as-note"> The first of a new year seems like a good day to assemble, aggregate, summarize and publish various year in review posts for the prior year. When various online services create a year in review for you many weeks before the end of the year (whether #Spotify #Wrapped or #Strava #YearInSport), it seems they are short-changing you. No one asks for an 11 months in review (except HR departments, which is a different problem). So why do people accept only an ~11 months summary when services provide such a premature “year” in review? When people say things like “Make every day count” do they not also believe you should “Count every day”? In this case, 2024 had 366 days. You should count every one of them, and every thing from every one of them. Rather than “sharing” a premature year in review, request your “year in review” today on the 1st of the year from various services, extract the data you want, fill in any gaps, and post your year in reviews on your own site<a id="t5_p2_ref-1" href="#t5_p2_note-1">¹</a>. #yearInReview #ownYourYearInReview This is post 2 of #100PostsOfIndieWeb. #100Posts ← <a class="auto-link" href="https://tantek.com/2025/001/t1/15-years-notes-my-site-first">https://tantek.com/2025/001/t1/15-years-notes-my-site-first</a> → <a class="auto-link" href="https://tantek.com/2025/001/t3/strava-year-in-sport-how-to-get-info-save">https://tantek.com/2025/001/t3/strava-year-in-sport-how-to-get-info-save</a> Glossary: year in review   <a class="auto-link" href="https://indieweb.org/year_in_review">https://indieweb.org/year_in_review</a>   <a id="t5_p2_note-1" href="#t5_p2_ref-1">¹</a> <a class="auto-link" href="https://indieweb.org/year_in_review#IndieWeb_Examples">https://indieweb.org/year_in_review#IndieWeb_Examples</a> <a href="/2025/001/t2/first-new-year-review-prior" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="16:30-0800">16:30</time> on <time class="value">2025-01-01</time></a> </li> <li class="h-entry hentry as-note"> Welcome to 2025! 15 years ago today I began posting notes on my own #indieweb site first, and only later on #socialMedia: <a class="auto-link" href="https://tantek.com/2010/001/t1/declaring-independence-building-it">https://tantek.com/2010/001/t1/declaring-independence-building-it</a> 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<a id="t5_p1_ref-1" href="#t5_p1_note-1">¹</a> to post into. Companies, servers, services, disappear all the time, taking all their posts and permalinks with them to graveyard 404<a id="t5_p1_ref-2" href="#t5_p1_note-2">²</a>. 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: <a class="auto-link" href="https://chat.indieweb.org/">https://chat.indieweb.org/</a> #ownYourContent #ownYourData Once again I am restarting a #100PostsOfIndieWeb #100Posts project for the year. This is post 1. Previously, previously, previously: * <a class="auto-link" href="https://tantek.com/2024/001/t1/restarting-100days-indieweb-gift-calendar">https://tantek.com/2024/001/t1/restarting-100days-indieweb-gift-calendar</a> * <a class="auto-link" href="https://tantek.com/2023/001/t1/own-your-notes">https://tantek.com/2023/001/t1/own-your-notes</a> * <a class="auto-link" href="https://tantek.com/2022/001/t1/12-years-notes-my-site">https://tantek.com/2022/001/t1/12-years-notes-my-site</a> * <a class="auto-link" href="https://tantek.com/2020/001/t1/10-years-notes-my-site">https://tantek.com/2020/001/t1/10-years-notes-my-site</a> * <a class="auto-link" href="https://tantek.com/2015/002/t1/notes-replies-faves-before-twitter-ownyourdata">https://tantek.com/2015/002/t1/notes-replies-faves-before-twitter-ownyourdata</a> ← ✨ → <a class="auto-link" href="https://tantek.com/2025/001/t2/first-new-year-review-prior">https://tantek.com/2025/001/t2/first-new-year-review-prior</a> Glossary: IndieWeb   <a class="auto-link" href="https://indieweb.org/">https://indieweb.org/</a> longevity   <a class="auto-link" href="https://indieweb.org/longevity">https://indieweb.org/longevity</a> post   <a class="auto-link" href="https://indieweb.org/post">https://indieweb.org/post</a> permalink   <a class="auto-link" href="https://indieweb.org/permalink">https://indieweb.org/permalink</a> personal domain name   <a class="auto-link" href="https://indieweb.org/personal-domain">https://indieweb.org/personal-domain</a> POSSE   <a class="auto-link" href="https://indieweb.org/POSSE">https://indieweb.org/POSSE</a> syndicate   <a class="auto-link" href="https://indieweb.org/syndicate">https://indieweb.org/syndicate</a> <a id="t5_p1_note-1" href="#t5_p1_ref-1">¹</a> <a class="auto-link" href="https://tantek.com/2023/022/t2/own-your-notes-domain-migration">https://tantek.com/2023/022/t2/own-your-notes-domain-migration</a> <a id="t5_p1_note-2" href="#t5_p1_ref-2">²</a> <a class="auto-link" href="https://indieweb.org/site-deaths">https://indieweb.org/site-deaths</a> <a href="/2025/001/t1/15-years-notes-my-site-first" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="16:18-0800">16:18</time> on <time class="value">2025-01-01</time></a> </li> <li class="h-entry hentry as-note"> Last 2024 #donation request: please #donate to any/all tonight! I donated to these, pick ones that resonate with you: <a class="auto-link h-cassis-username" href="https://twitter.com/ACLU">@ACLU</a> <a class="auto-link h-cassis-username" href="https://twitter.com/NAACP">@NAACP</a> <a class="auto-link h-cassis-username" href="https://twitter.com/InternetArchive">@InternetArchive</a> <a class="auto-link h-cassis-username" href="https://twitter.com/Wikipedia">@Wikipedia</a> <a class="auto-link h-cassis-username" href="https://twitter.com/PPact">@PPact</a> <a class="auto-link h-cassis-username" href="https://twitter.com/Mozilla">@Mozilla</a>** <a class="auto-link h-cassis-username" href="https://twitter.com/EFF">@EFF</a> <a class="auto-link h-cassis-username" href="https://twitter.com/CalAcademy">@CalAcademy</a> <a class="auto-link h-cassis-username" href="https://twitter.com/deYoungMuseum">@deYoungMuseum</a> <a class="auto-link h-cassis-username" href="https://twitter.com/Exploratorium">@Exploratorium</a> <a class="auto-link h-cassis-username" href="https://twitter.com/MontereyAq">@MontereyAq</a> <a class="auto-link h-cassis-username" href="https://twitter.com/SFMOMA">@SFMOMA</a> <a class="auto-link h-cassis-username" href="https://twitter.com/SFParksAlliance">@SFParksAlliance</a> **Disclosure: I work for <a class="auto-link h-cassis-username" href="https://twitter.com/Mozilla">@Mozilla</a>, on & with open web standards & communities <a class="auto-link h-cassis-username" href="https://twitter.com/indiewebcamp">@indiewebcamp</a> <a class="auto-link h-cassis-username" href="https://twitter.com/microformats">@microformats</a> <a class="auto-link h-cassis-username" href="https://twitter.com/W3C">@W3C</a> <a class="auto-link h-cassis-username" href="https://twitter.com/WHATWG">@WHATWG</a> supported by <a class="auto-link h-cassis-username" href="https://twitter.com/Firefox">@Firefox</a> to provide a more human-centric, private, and secure web for all users. Previously: <a class="auto-link" href="https://tantek.com/2019/365/t1/today-donate-renew-arts-science">https://tantek.com/2019/365/t1/today-donate-renew-arts-science</a> <a href="/2024/366/t2/last-donation-please-donate-tonight" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="19:50-0800">19:50</time> on <time class="value">2024-12-31</time></a> </li> <li class="h-entry hentry as-note"> 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: <a class="auto-link" href="https://theatermitu.org">@theatermitu.org</a> (<a class="auto-link h-cassis-username" href="https://twitter.com/theatermitu">@theatermitu</a> <a class="auto-link" href="https://instagram.com/theatermitu">@instagram.com/theatermitu</a>) Theater Mitu is an independent theater arts organization, space, and community that supports numerous artists, shows, and incubates and produces new work! Donation link: <a class="auto-link" href="https://secure.givelively.org/donate/theater-mitu/the-decade-ahead-10-more-years-of-mitu-in-brooklyn">https://secure.givelively.org/donate/theater-mitu/the-decade-ahead-10-more-years-of-mitu-in-brooklyn</a> #TheaterMitu #NewYork #NYC #Brooklyn <a href="/2024/366/t1/last-day-year-donate-worthy-theatermitu" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="12:04-0800">12:04</time> on <time class="value">2024-12-31</time></a> </li> <li class="h-entry hentry as-note"> finished the #InsideTrail Woodside Ramble 35k #trailRace in 7:42:58! 21+ miles for the 21st. Happy Winter Solstice! One last dance for 2024. Drove down 101 and saw the orange sunrise between the East Bay mountains and stormy cloud cover. Made it to Huddart Park, parked, got my bib, pinned it to to my shorts, left my drop bag on a picnic table, and lined up to start just in time. It was overcast and as we made our way up the hill, the drizzle then rain and wind began. The deep forest protected us from most of it. The recent storms had downed a large tree which blocked part of the original course. The organizers had to re-route the 35k course (and the 55k) into a series of loops. This was my first 3 loops race! It was harder than expected (the course changes added lots more vert) but I finished healthy, no pain, no soreness, so I'll take it, along with my second DLF trophy. I’m starting a collection. Started the year with a rainy 30k race (Redtail Ridge<a id="t5_d1_ref-1" href="#t5_d1_note-1">¹</a>), finished the year with a rainy 35k (with ~60% more vert! nearly 4400'). Seven races in 2024 ✅ Good notes to end on for this year’s trail racing season. #35k #WoodsideRamble #Ramble24 #trailRun #trailRunner #runner #trailRunning #running <a id="t5_d1_note-1" href="#t5_d1_ref-1">¹</a> <a class="auto-link" href="https://tantek.com/2024/051/t1/finished-redtail-ridge-30k">https://tantek.com/2024/051/t1/finished-redtail-ridge-30k</a> <a href="/2024/356/t1/finished-woodside-ramble-35k" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="23:36-0800">23:36</time> on <time class="value">2024-12-21</time></a> </li> <li class="h-entry hentry as-note"> signed up for <a class="auto-link" href="https://brokenarrowskyrace.com">@brokenarrowskyrace.com</a> (<a class="auto-link h-cassis-username" href="https://twitter.com/BrokenArrowCA">@BrokenArrowCA</a>) 23k #skyRace on 2025-06-22!<a id="t5_S1_ref-1" href="#t5_S1_note-1">¹</a> This will be my third #BrokenArrow race. Goals: finish strong, beat last year’s time. The race sold out within 10-15minutes of opening this morning. Here’s how it went for me: 09:00 Pacific time registration opened (I had two laptops ready, reloading every second) 09:06 I completed registering but it redirected me to the home page (not a confirmation). I thought it had canceled my registration, so I kept trying. The #UltraSignup site flow was sufficiently broken that I didn't know I had successfully registered. ~9:15 I was able to check my online UltraSignup profile and see the 09:06 registration. 09:25 Received email confirmation of registration. You can still register for the 23k waitlist: <a class="auto-link" href="https://ultrasignup.com/register.aspx?did=117118">https://ultrasignup.com/register.aspx?did=117118</a> More Broken Arrow races and distances (e.g. 46k, VK, 18k, 11k) registrations are opening the rest of this week, every morning December 10-13. See the <a class="auto-link" href="https://www.brokenarrowskyrace.com/">https://www.brokenarrowskyrace.com/</a> website for details for each. Previously, previously: * <a class="auto-link" href="https://tantek.com/2024/176/t1/finished-broken-arrow-skyrace-23k">https://tantek.com/2024/176/t1/finished-broken-arrow-skyrace-23k</a> * <a class="auto-link" href="https://tantek.com/2023/178/t1/june-trailrunner-ultrarunner">https://tantek.com/2023/178/t1/june-trailrunner-ultrarunner</a> <a id="t5_S1_note-1" href="#t5_S1_ref-1">¹</a> <a class="auto-link" href="https://www.brokenarrowskyrace.com/23k">https://www.brokenarrowskyrace.com/23k</a> #23k #trailRace #RingDasBell <a href="/2024/344/t1/signed-up-broken-arrow-skyrace-23k" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="10:41-0800">10:41</time> on <time class="value">2024-12-09</time></a> </li> <li class="h-entry hentry as-note"> This is a summary curation of prior posts of mine on why post, what to post, and how to post, as well as some bits I wrote on the #IndieWeb wiki. 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. If you have a blog and ever feel stuck about why you should post, what to post next, or how to write your post, hopefully this post will help get you unstuck. These reasons, topics, and techniques help me create, expand, edit, publish, and update more posts, sooner. Choose the ones that resonate for you, ignore the rest, and publish what else works for you on your personal site! Why Post There is a whole wiki page on the topic: * <a class="auto-link" href="https://indieweb.org/why_post">https://indieweb.org/why_post</a> — which could use some gardening Here are a few specific reasons why you should post: * 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<a id="t5_K1_ref-1" href="#t5_K1_note-1">¹</a>, then you already have reason enough to post. So post on your own site first, and optionally syndicate<a id="t5_K1_ref-2" href="#t5_K1_note-2">²</a> to that silo, only if you have friends who still use it to read posts. * Search everything you write. Do you post long comments or issues on GitHub? Do you post on public mailing lists? Post such things to your own site, so you can more easily search everything you’ve written on a topic. Then post a copy to those external destinations. * All the reasons to own your data: <a class="auto-link" href="https://indieweb.org/own_your_data">https://indieweb.org/own_your_data</a> What to Post There are so many things to post about! This is obviously highly personal. Here are a few that I use myself: * Post positive things promptly: <a class="auto-link" href="https://tantek.com/2018/357/t3">https://tantek.com/2018/357/t3</a>   * … from that day first: <a class="auto-link" href="https://tantek.com/2018/364/t1">https://tantek.com/2018/364/t1</a>   * … in time order: <a class="auto-link" href="https://tantek.com/2018/364/t5">https://tantek.com/2018/364/t5</a> * Make and share lists. People like lists * Post to learn in public, and pass on what you learn How to Post I have spent a lot of time thinking about, trying, and iterating on different methods and techniques for starting, expanding, completing, publishing, and updating posts. These are a few of the techniques I use: * Use a local text editor * Capture first, edit & publish later: <a class="auto-link" href="https://tantek.com/2023/365/t1/">https://tantek.com/2023/365/t1/</a> * Do something positive (in-person), then post about it: <a class="auto-link" href="https://tantek.com/2018/002/t1">https://tantek.com/2018/002/t1</a> * 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 posts, 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 sections: Previously, Post Glossary, References, Additional Reading * Check your references Each of these points could be its own blog post. There are many more whys, whats, and hows. See more on these pages on the IndieWeb community site: * <a class="auto-link" href="https://indieweb.org/why_post">https://indieweb.org/why_post</a> * <a class="auto-link" href="https://indieweb.org/what_to_post">https://indieweb.org/what_to_post</a> * <a class="auto-link" href="https://indieweb.org/how_to_post">https://indieweb.org/how_to_post</a> Add your own to each, and/or help organize them! Glossary mailing list   <a class="auto-link" href="https://indieweb.org/mailing_list">https://indieweb.org/mailing_list</a> own your data   <a class="auto-link" href="https://indieweb.org/own_your_data">https://indieweb.org/own_your_data</a> post footer   <a class="auto-link" href="https://indieweb.org/posts#Footer_sections">https://indieweb.org/posts#Footer_sections</a> silo   <a class="auto-link" href="https://indieweb.org/silo">https://indieweb.org/silo</a> social media   <a class="auto-link" href="https://indieweb.org/social_media">https://indieweb.org/social_media</a> References <a id="t5_K1_note-1" href="#t5_K1_ref-1">¹</a> <a class="auto-link" href="https://tantek.com/2023/001/t1/own-your-notes">https://tantek.com/2023/001/t1/own-your-notes</a> <a id="t5_K1_note-2" href="#t5_K1_ref-2">²</a> <a class="auto-link" href="https://indieweb.org/POSSE">https://indieweb.org/POSSE</a> This is post 29 of #100PostsOfIndieWeb. #100Posts ← <a class="auto-link" href="https://tantek.com/2024/306/t1/simple-embeds">https://tantek.com/2024/306/t1/simple-embeds</a> → 🔮 <a href="/2024/337/t1/why-what-how-to-post" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="21:11-0800">21:11</time> on <time class="value">2024-12-02</time></a> </li> <li class="h-entry hentry as-note"> ~3 weeks ago I posted some thoughts<a id="t5_J1_ref-1" href="#t5_J1_note-1">¹</a> about the US #election. Upon more reflection, more thoughts and some updates. ~50 days until many #changes that will harm many, disrupt many more. Some changes and impacts will be immediate, some in days to weeks, mostly predictable, and some in months or longer, less predictable the further out. It will be a lot like 8 years ago, except accelerated in time and severity, more well planned and executed, and quickly becoming hard to predict. How to prepare for a mix of seemingly unpreventable disruptions and unpredictability? resilience, redundancies, redirects, and resistance. The next 50 days are the calm before a four year storm, if not longer. Perhaps there will be a respite in two years (midterms), perhaps even worth pursuing, yet not something to depend on. For now, the following come to mind as immediately useful, actionable, and necessary, as a ways to act that are sustainable, and build upon each other: 1. make changes slowly, gradually, incrementally 2. take extra care of yourself, physical health, mental health 3. strengthen connections that matter, close friends, family, neighbors, not social media One goal of these is to build stronger personal foundations from which to take larger actions. Lastly, it is easy to get discouraged after disappointing outcomes. Easy to feel powerless. There are things we can all do, individually or collectively, perhaps locally, and there are many things that are difficult or impossible. It’s a spectrum of difficulty, not a dichotomy. Better to focus on approachable actions and goals rather than seeking perfection, the enemy of the good.<a id="t5_J1_ref-2" href="#t5_J1_note-2">²</a> Surround yourself with those that encourage and celebrate your actions and successes, and spend less time with those who speak fatalism (all outcomes are inevitable), defeatism (all actions are ineffective), or nihilism (nothing matters). Small successes build momentum and upon each other into larger successes. More to follow. <a id="t5_J1_note-1" href="#t5_J1_ref-1">¹</a> <a class="auto-link" href="https://tantek.com/2024/313/t1/reflecting-listening-thoughts">https://tantek.com/2024/313/t1/reflecting-listening-thoughts</a> <a id="t5_J1_note-2" href="#t5_J1_ref-2">²</a> <a class="auto-link" href="https://en.wikipedia.org/wiki/Perfect_is_the_enemy_of_good">https://en.wikipedia.org/wiki/Perfect_is_the_enemy_of_good</a> <a href="/2024/336/t1/disruptions-how-to-prepare" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="19:46-0800">19:46</time> on <time class="value">2024-12-01</time></a> </li> <li class="h-entry hentry as-note"> ran the Spartan Turkey Trot #5k #race in 44:34 <a class="auto-link h-cassis-username" href="https://twitter.com/SpartanTurkey5k">@SpartanTurkey5k</a>! 2min/mi+ faster average pace than 2023’s #turkeyTrot walk / slow jog of 47:37 on a shortened course (2.86mi). Arrived early for a warm-up and it was the coldest it’s been in years (30-something F). Alternated run/walk sessions for ~20min then jogged back to the track start area where they had moved the start since last year. Used the bathroom, and kept warming up with back/forth strides then high knees while waiting with the fam in wave 3. Ran out at a moderate pace dodging walkers and strollers. Once we were on the street the cold air really hit my lungs. Listened to music nearly the whole time. Mile 2 was my slowest but still kept it under 15min/mi (my goal pace). Ran much more than walked in the last mile, and had enough left in the tank to push a little harder the last quarter mile to the finish where I hit my highest heartrate of the race. Pretty happy with a sub-45 in sub-40F temperatures, and a solid improvement after last year’s walk/jog which itself was only ~3 months after recovering from a cardio-destroying illness. Considering what to race next, thinking a trail race in December. See also: <a class="auto-link" href="https://www.spartanturkeytrot.com/">https://www.spartanturkeytrot.com/</a> #turkeyTrot2024 Previously: * <a class="auto-link" href="https://tantek.com/2022/329/t1/spartan-turkey-trot-5k">https://tantek.com/2022/329/t1/spartan-turkey-trot-5k</a> <a href="/2024/333/t1/spartan-turkey-trot-5k" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="18:24-0800">18:24</time> on <time class="value">2024-11-28</time></a> </li> <li class="h-entry hentry as-note"> Day 1 of #IndieWebCamp #Berlin 2024<a id="t5Zw1_ref-1" href="#t5Zw1_note-1">¹</a> was very well attended! * 20 participants, more than 3x the previous one in 2022, and third highest (2018 ~30; 2019 ~22). * 18 introduced themselves<a id="t5Zw1_ref-2" href="#t5Zw1_note-2">²</a> and their personal sites or aspirations for one Collectively we proposed and facilitated 11 breakout sessions<a id="t5Zw1_ref-3" href="#t5Zw1_note-3">³</a> 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   <a id="t5Zw1_note-1" href="#t5Zw1_ref-1">¹</a> <a class="auto-link" href="https://indieweb.org/2024">https://indieweb.org/2024</a> <a id="t5Zw1_note-2" href="#t5Zw1_ref-2">²</a> <a class="auto-link" href="https://indieweb.org/2024/Berlin/Intros">https://indieweb.org/2024/Berlin/Intros</a> <a id="t5Zw1_note-3" href="#t5Zw1_ref-3">³</a> <a class="auto-link" href="https://indieweb.org/2024/Berlin/Schedule#Saturday">https://indieweb.org/2024/Berlin/Schedule#Saturday</a> This is post 28 of #100PostsOfIndieWeb. #100Posts ← <a class="auto-link" href="https://tantek.com/2024/306/t1/simple-embeds">https://tantek.com/2024/306/t1/simple-embeds</a> → <a class="auto-link" href="https://tantek.com/2024/337/t1/why-what-how-to-post">https://tantek.com/2024/337/t1/why-what-how-to-post</a> <a href="/2024/314/t1/indiewebcamp-berlin-2024-day-1" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="05:31-0800">05:31</time> on <time class="value">2024-11-09</time></a> </li> <li class="h-entry hentry as-note"> Still reflecting and listening to how different folks are reacting after the US #election results. A few immediate thoughts: * take care of yourselves, physically, emotionally, etc. * lean into mutual care, check on those close to you * (re)connect with community and especially those that reach out to you * (re)consider privacy implications of your actions, IRL & online, spending habits Here in #SanFrancisco and #California we are seeing mostly positive local results<a id="t5Zv1_ref-1" href="#t5Zv1_note-1">¹</a> including a new mayor (who I happened to rank first for many reasons). Lots to think about and do in the next couple of months. <a id="t5Zv1_note-1" href="#t5Zv1_ref-1">¹</a> <a class="auto-link" href="https://sfstandard.com/2024/11/05/san-francisco-election-results-november-2024/">https://sfstandard.com/2024/11/05/san-francisco-election-results-november-2024/</a> <a href="/2024/313/t1/reflecting-listening-thoughts" class="dt-published published dt-updated updated u-url u-uid"><time class="value" datetime="04:04-0800">04:04</time> on <time class="value">2024-11-08</time></a> </li> </ol> </div> <aside><div class="aside" id="contact"> <div class="p-note note"> <div class="section hello" id="hello"> <h2>Hello</h2> Hi. I work on web standards and the IndieWeb. I like to run trails, practice yoga, go bouldering, code & design my website, and write when I can. My pronouns are <a class="p-pronoun h-pronoun">he</a>/<a class="p-pronoun h-pronoun">him</a>. <a href="?" rel="nofollow" title="Choose default theme">🏠</a> <a href="?skin=vtx" rel="nofollow" title="Choose Terminal theme">📺</a> <a href="?skin=trn" rel="nofollow" title="Choose TRON:Legacy theme">🥏</a> </div> <div class="section interact"> <ul> <li><a href="//tantek.com/contact">💬 Contact</a></li> <li><a href="//tantek.com/tip/1" title="Did you read something of value here and want to encourage more posts like that? Feel free to tip a small amount and mention which topics you enjoyed! (Just please avoid specific products or services. Thanks! -t)">👏 Tip</a></li> </ul> </div> <div class="section information"> <ul> <li> <a href="https://indieweb.org/founders">Founder</a> at <a href="https://indieweb.org/" class="p-org org h-card">IndieWeb</a> </li> <li> <a href="http://microformats.org/about/people">Founder</a> at <a href="http://microformats.org/" class="p-org org h-card">microformats.org</a> </li> <li> <a class="p-role" href="https://wiki.mozilla.org/Standards">Web Standards Lead</a> at <a href="https://mozilla.org/" class="p-org org h-card">Mozilla</a> </li> <li> <a href="https://www.w3.org/Consortium/membership-faq#ACRep"><abbr title="W3C Advisory Committee">AC</abbr></a> <a href="https://www.w3.org/2002/ab/"><abbr title="W3C Advisory Board">AB</abbr></a> & <a class="p-role" href="https://www.w3.org/Style/CSS/members"><abbr title="W3C Cascading Style Sheets Working Group">CSS WG</abbr></a> member at <a href="https://www.w3.org/" class="p-org org h-card">W3C</a> </li> <li>BSCS & MSCS <a href="https://stanford.edu/" class="p-category category h-card">Stanford University</a> </li> </ul> </div> </div> <div class="section elsewhere"> <h2 id="follow">Follow</h2> <ul class="facets"> <li><indie-action do="follow" with="https://tantek.com/"><a href="https://tantek.com/" rel="canonical" title="follow tantek.com in your favorite Social Reader"><abbr title="world wide web">🌐</abbr> <kbd>tantek.com</kbd></a></indie-action></li> <li><form style="margin:0.2em 0 1em; color:#000" method="post" action="https://fed.brid.gy/remote-follow"> <label for="follow-address"><abbr title="at-at">🐘</abbr> Follow <kbd title="copy my at-at address to follow from Mastodon">@tantek.com@tantek.com</kbd>: enter your @-@ fediverse address:</label> <input id="follow-address" name="address" type="text" required="required" placeholder="@you@instance.social" title="Type your @-@ address" size="23" value=""> <input name="domain" type="hidden" value="tantek.com"> <input name="protocol" type="hidden" value="web"> <button type="submit">Follow</button> </form></li> <li> <a rel="me" class="u-url url" href="https://micro.blog/t" title="follow me on micro.blog"><svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" viewBox="0 0 480 480" focusable="false" aria-hidden="true"> <defs> <linearGradient id="a" x1="50%" x2="50%" y1="0" y2="78%"> <stop offset="0%" stop-color="#fb0"></stop> <stop offset="100%" stop-color="#f80"></stop> </linearGradient> <linearGradient id="b" x1="50%" x2="50%" y1="0" y2="100%"> <stop offset="0%" stop-color="#ffc"></stop> <stop offset="100%" stop-color="#ff6"></stop> </linearGradient> </defs> <path fill="url(#a)" d="M427 354c31-37 53-84 53-135C480 98 371 0 240 0 108 0 0 98 0 219s108 219 240 219c28 0 57-5 84-14 3-1 7 0 9 2 20 27 51 46 85 54l5-2v-6a93 93 0 0 1 4-118z"></path> <path fill="url(#b)" d="M352 194l-61 46 22 72c1 3 0 6-3 8h-8l-63-43-63 43h-8c-3-2-4-5-3-8l22-72-61-46c-3-2-4-5-3-8 1-2 4-4 7-4l77-2 25-71c1-3 4-5 7-5s6 2 7 5l25 71 77 2c3 0 6 2 7 4 1 3 0 6-3 8z"></path> </svg> micro.blog @t</a> </li> <li><a rel="me" class="u-url url" href="https://www.threads.net/@tantek" title="Threads account that I‘m experimenting with">@ Threads @tantek</a></li> <li><a rel="me" class="u-url url" href="https://instagram.com/tantek/" title="Instagram account where I cross-post my photos"><img src="images/instagram-16x16.png" alt=""/> Instagram @tantek</a></li> <li><a rel="me" class="u-url url" href="https://www.flickr.com/people/tantek/" title="photos on Flickr"><img src="images/flickr-16x16.png" alt=""/> Flickr</a></li> </ul> </div>  <div id="recent-articles" class="section recent-articles h-feed"> <h2 class="p-name">Recent Articles</h2> <ul> <li class="h-entry"><a href="/2025/052/b1/steps-indieweb-cybersecurity">CSF_01: Three Steps for IndieWeb Cybersecurity</a></li> <li class="h-entry"><a href="/2024/213/b1/choosing-tools">Choosing Tools</a></li> <li class="h-entry"><a href="/2024/180/b1/responsible-inventing">Responsible Inventing</a></li> </ul> </div>  <div id="recent-photos" class="section recent-photos h-feed"> <h2 class="p-name">Recent Photos</h2> <ul> <li class="h-entry" style="display:inline;margin:0;padding:0"><a href="/2022/289/t1/hot-skyline50k-ultra-finish"><img style="max-width:32%;width:7em;height:7em;object-fit:cover;margin-bottom:0.2em" src="https://fastly.4sqi.net/img/general/width960/476_tjk6ja88e3mjglC50lmeeMAwpr4Pozk_yVhAIuNgq3E.jpg" alt="Tantek running with a focused look in a 2020 MUC50 cap, black singlet & shorts, on a dirt trail with grass, bushes, & trees on both sides, and two runners out of focus ~20 meters behind him."/></a></li> <li class="h-entry" style="display:inline;margin:0;padding:0"><a href="/2021/221/t1/finished-rodeovalley-trailrace"><img style="max-width:32%;width:7em;height:7em;object-fit:cover;margin-bottom:0.2em" src="https://fastly.4sqi.net/img/general/width960/476_9_gqB6h_tK8iyjBEb886XpboOcF8bsEgT_wl76vckqI.jpg" alt="Fogged-in view of a lush green hillside, narrow singletrack trail cutting up from the right and approaching the center, with Tantek power hiking uphill, grinning, water bottle in right hand, holding his side with his left."/></a></li> <li class="h-entry" style="display:inline;margin:0;padding:0"><a href="/2021/218/t1/running-rodeovalley"><img style="max-width:32%;width:7em;height:7em;object-fit:cover;margin-bottom:0.2em" src="https://fastly.4sqi.net/img/general/width960/476_gChM9nrNNko-1aMouw-x74imp7kzUzJKLomkEQ4u8qQ.jpg" alt="White yoga mat on a hardwood floor with running shoes, clothes, gear, fuel laid out in an orderly fashion."/></a></li> <li class="h-entry" style="display:inline;margin:0;padding:0"><a href="/2021/019/t1/marin-trailrun"><img style="max-width:32%;width:7em;height:7em;object-fit:cover;margin-bottom:0.2em" src="https://fastly.4sqi.net/img/general/width960/476_nJH-uVKVhefvOPmfi3mPSlI9MqpeN6WLmS6EbWdKNC0.jpg" alt="Tantek running downhill on a trail with mountains, hills, and an ocean shore in the distant background, under a sunny blue sky."/></a></li> <li class="h-entry" style="display:inline;margin:0;padding:0"><a href="/2021/017/t3/seven-years-ago-npsf-hills"><img style="max-width:32%;width:7em;height:7em;object-fit:cover;margin-bottom:0.2em" src="https://fastly.4sqi.net/img/general/width960/476_fkcHgLiQBPvCLZJHKYdX7CaTedWH8UbLwL1AQuOZV9A.jpg" alt="View of sunset-lit downtown San Francisco in the distance as viewed from Twin Peaks, with the hairpin turn below, and immediately below the green hill slope of Twin Peaks summit."/></a></li> <li class="h-entry" style="display:inline;margin:0;padding:0"><a href="/2021/017/t2/january"><img style="max-width:32%;width:7em;height:7em;object-fit:cover;margin-bottom:0.2em" src="https://fastly.4sqi.net/img/general/width960/476_M152uOnalZ6QfPsz9YMHd2sNPt-U7s2Twx2Lj26gryA.jpg" alt="January of 2021 month calendar built from LEGO bricks, on a hexagonal white on gray blanket background."/></a></li> <li class="h-entry" style="display:inline;margin:0;padding:0"><a href="/2020/364/t1/last-track"><img style="max-width:32%;width:7em;height:7em;object-fit:cover;margin-bottom:0.2em" src="https://fastly.4sqi.net/img/general/width960/476_77tgUdgL2xYzHOEFYLIf1-kATkEom1PWrqzIEja6Bww.jpg" alt="Multicolored heart painting with a few sequine pieces, outlined in pink with bits of turquoise, paint dripping downward, on a piece of plywood at a construction site, signed KATE_TOVA."/></a></li> <li class="h-entry" style="display:inline;margin:0;padding:0"><a href="/2020/359/t1/tam-summit"><img style="max-width:32%;width:7em;height:7em;object-fit:cover;margin-bottom:0.2em" src="https://fastly.4sqi.net/img/general/width960/476_OguOnR4ZRWSfkf4xrKwqIhVCw6Fmp8zJZT1reWJclls.jpg" alt="Tantek wearing a buff taking a selfie at the Mill Valley Depot with Nick, Paddy, Olivia, and Emma safely distanced in the background."/></a></li> <li class="h-entry" style="display:inline;margin:0;padding:0"><a href="/2020/356/t1/december-winter-solstice"><img style="max-width:32%;width:7em;height:7em;object-fit:cover;margin-bottom:0.2em" src="https://fastly.4sqi.net/img/general/width960/476_crDev05xDJVnmxPsasFbdxMvdxDA1tuItOUPEaTVogA.jpg" alt="December of 2020 month calendar built from LEGO bricks, on an hardwood floor background."/></a></li> <li class="h-entry" style="display:inline;margin:0;padding:0"><a href="/2020/153/t1/justice-for-george"><img style="max-width:32%;width:7em;height:7em;object-fit:cover;margin-bottom:0.2em" src="https://fastly.4sqi.net/img/general/width960/476_wiYEJTxjdxLl_vZFlLefP9O8b-Jv9R12Q92ANKZXhSA.jpg" alt="Stencil street art of George Floyd on a red wall with the word JUSTICE above his head, and FOR GEORGE below."/></a></li> <li class="h-entry" style="display:inline;margin:0;padding:0"><a href="/2020/137/t3/sf-distancing-day-twelve"><img style="max-width:32%;width:7em;height:7em;object-fit:cover;margin-bottom:0.2em" src="https://fastly.4sqi.net/img/general/width960/476_SpwXl5ANk0Pyg5xBFSovR5qUkMoaEE_6uak0acFKU8w.jpg" alt="Intersection of Frederick and Ashbury streets at night, looking westward, everything is dark except for streetlamps, lights outside a boarded up Ashbury Market, and a second floor corner apartment on the other side, above a lit bus stop for the number 6 outbound bus."/></a></li> <li class="h-entry" style="display:inline;margin:0;padding:0"><a href="/2020/130/t1/ahmaudarbery-blacklivesmatter"><img style="max-width:32%;width:7em;height:7em;object-fit:cover;margin-bottom:0.2em" src="https://fastly.4sqi.net/img/general/width960/476_RLIxPGQ2v_yOJcsVnDalcK2pZETJNnYbZSr1I4VhrBc.jpg" alt="Strava map showing a roundtrip running route in red from Haight Ashbury to near a hairpin turn on Twin Peaks and back."/></a></li> </ul> </div> <div class="section elsewhere"> <h2 id="elsewhere">Elsewhere</h2> <ul class="facets"> <li><a rel="me" class="u-url url" href="https://github.com/tantek" title="open source on Github"><img src="images/github-16x16.png" alt=""/> Github @tantek</a></li>  <li><a href="https://www.imdb.com/name/nm8414793" title="film appearance(s)on IMDB"><img src="images/imdb-16x16.png" alt=""/> IMDB</a></li> <li><a rel="me" class="u-url url" href="https://indieweb.org/User:Tantek.com" title="contributions to IndieWeb wiki"><img src="images/wikipedia-16x16.png" alt=""/> IndieWeb User:Tantek.com</a></li> <li><a rel="me" class="u-url url" href="https://en.wikipedia.org/wiki/User:Tantek" title="contributions to Wikipedia"><img src="images/wikipedia-16x16.png" alt=""/> Wikipedia User:Tantek</a></li> </ul> </div>  <div class="section"> <h2>Buy my book!</h2> <a href="//tantek.com/html5now"><img src="images/html5nowdvd.jpg" alt="HTML5 Now!"/></a> A step-by-step tutorial for getting started with HTML5 today. Includes reference guide and DVD with 2.5 hours of video plus 100 page searchable full-color PDF eBook. <a href="//tantek.com/html5now">Buy at Amazon.com</a> </div> </div></aside> <footer><div class="footer"> <div class="section"> <h2>Launched & Live</h2> <ul> <li> <a href="//tantek.com/html5now">HTML5 Now! book & DVD</a> - quickly learn how to write HTML5, from documents to video and vector graphics.</li> <li> <a href="https://asin.cc" title="Amazon product link shortener">ASIN.cc</a> - a handy URL shortener for books and Amazon products</li> <li> <a href="https://h2vx.com/" title="hCard to vCard, hCalendar to iCalendar conversion services">H2VX</a> - add hCard contacts and hCalendar events from web pages to your address book and calendar programs</li> <li class="h-card"> <a class="p-name u-url" href="http://microformats.org/wiki">microformats.org</a> - the fastest way to publish your web page contents as data APIs and look better in search engines </li> </ul> </div> <div class="section"> <h2>Currently Working On</h2> <ul> <li> <a href="https://wiki.mozilla.org/Tantek-Mozilla-projects">Mozilla projects</a> - open standards: <a class="p-category category" href="http://microformats.org/wiki/microformats2">microformats2</a> (e.g. <a class="p-category category" href="http://microformats.org/wiki/h-card">h-card</a>, <a class="p-category category" href="http://microformats.org/wiki/h-cite">h-cite</a>, <a class="p-category category" href="http://microformats.org/wiki/h-entry">h-entry</a>, & <a class="p-category category" href="http://microformats.org/wiki/h-event">h-event</a>), some HTML5 & CSS3, growing the <a class="p-category category p-org org h-org" href="https://indieweb.org/">IndieWeb</a> & <a href="https://indieweb.org/events/next-hwc">Homebrew Website</a> communities.</li> <li> <a href="https://indieweb.org/">IndieWeb community</a> & <a href="https://events.indieweb.org/">events</a>, <a href="//tantek.com/2014/067/b1/building-blocks-people-focused-mobile-communication">people-focused mobile communication</a>, <a class="p-category category" href="https://indieweb.org/authorship">authorship</a>, <a class="p-category category" href="https://indieweb.org/POSSE">POSSE</a>, <a class="p-category category" href="https://indieweb.org/webactions">webactions</a>, and measuring progress with <a class="p-category category" href="https://indieweb.org/IndieMark">IndieMark</a>. </li> <li> <a class="p-category category" href="http://cassisproject.com" title="CASSIS language and library"><abbr title="Client And Server Scripting Implementation Subset for Javascript and PHP">CASSIS</abbr></a> (<a href="https://tantek.com/github/cassis/">on GitHub</a>) - a functional programming language and framework for code that natively executes in PHP and Javascript.</li>  <li> <a class="p-category category" href="https://indieweb.org/Falcon">Falcon</a> - personal website, blogging, and social web application. See <a href="https://indieweb.org/Falcon#Working_On">what I'm currently working on</a>. </li> <li> <a href="//tantek.com/w/Whistle">Whistle</a> - personal algorithmically reversible URL shortener.</li> </ul> </div> <div class="section h-feed" id="events"> <h2 class="p-name">Speaking & Events</h2> <ol> <li class="h-event vevent"> <time>2024-12-21</time> <a class="u-url url" href="https://insidetrail.com/calendar/woodside-ramble-trail-run/"><abbr class="p-name summary" title="35k Woodside Ramble trail race">Woodside Ramble 35k</abbr> <abbr class="p-location location" title="Huddart County Park, Woodside, California, USA">Woodside</abbr></a> </li> <li class="h-event vevent"> <time>2025-05-18</time> <a class="u-url url" href="https://www.baytobreakers.com/">Bay to Breakers 12k <abbr class="p-location location" title="San Francisco, California, USA">San Francisco</abbr></a> </li> <li class="h-event vevent"> <time>2025-06-22</time> <a class="u-url url" href="https://www.brokenarrowskyrace.com/23k"><abbr class="p-name summary" title="23K Broken Arrow Skyrace">BA 23k skyrace</abbr> <abbr class="p-location location" title="Palisades, Tahoe, California, USA">Palisades</abbr></a> </li> </ol>  <a href="webcal://dev.h2vx.com/ics/tantek.com">Subscribe to events</a> </div> <div class="favorite-quotes" id="favorite-quotes" style="padding-top:2em;clear:both"> <blockquote>There are two wolves and they are always fighting. One is darkness and despair, the other is light and hope. Which wolf wins? </blockquote> <blockquote>I get things are bad. But what are we doing to fix it? — Casey Newton (<a href="https://en.wikiquote.org/wiki/Tomorrowland_%28film%29#Casey_Newton">Tomorrowland, 2015</a>)</blockquote> </div> <address class="copyright">© <time>1996</time>-<time>2025</time> Tantek Çelik, All Rights Reserved. Icon photo by Rebecca Daniels. <a href="https://xn--sr8hvo.ws/📊/previous">←</a> Member of IndieWeb Webring 🕸💍 <a href="https://xn--sr8hvo.ws/📊/next">→</a> </address> <div class="disclaimer" id="disclaimer"> No large language models were used in the production of this site. (inspired by <a class="h-cite" href="https://www.rfc-editor.org/rfc/rfc9518.html#appendix-A-4" rel="inspiration"><abbr title="RFC 9518: Centralization, Decentralization, and Internet Standards">RFC 9518</abbr> Appendix A ¶ 4</a>) </div> </div></footer> <script src="cassis.js"></script> <script>/**/ var es = document.getElementById("link"); if (es) { es.onclick = function() { var e = targetelement(); e.focus(); e.select(); }; } /**/</script> <script>{var s=navigator.serviceWorker;if(s){s.register('/serviceworker.js');}}</script> </body> </html>