FEED Validator

for Atom and RSS and KML

Congratulations!

This is a valid Atom 1.0 feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

line 5, column 59: Self reference doesn't match document location [help]

  <link href="https://tantek.com/updates.atom" rel="self"/>
                                                           ^

line 16, column 119: The title attribute of link should not be blank (11 occurrences) [help]

... ="alternate" title="" type="text/html"/>
                                             ^

line 24, column 4: Use of unknown namespace: http://activitystrea.ms/spec/1.0/ (12 occurrences) [help]

    <object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
    ^

Source: http://tantek.com/updates.atom

<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-US">
<title>Tantek Çelik</title>
<link href="https://tantek.com/" rel="alternate" title="Tantek Çelik" type="text/html"/>
<link href="https://tantek.com/updates.atom" rel="self"/>
<link rel="hub" href="https://pubsubhubbub.superfeedr.com/"/>
<id>https://tantek.com/updates.atom</id>
<author>
<name>Tantek</name>
<uri>https://tantek.com/</uri>
</author>
<updated>2025-03-18T18:25:00-07:00</updated>
<entry>
<updated>2025-03-18T18:25:00-07:00</updated>
<published>2025-03-18T18:25:00-07:00</published>
<link href="https://tantek.com/2025/077/t1/what-are-words-for-blogging" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2025/077/t1/what-are-words-for-blogging</id>
<title type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
</title>
<content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">“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)</div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
</entry>
<entry>
<updated>2025-03-12T14:45:00-07:00</updated>
<published>2025-03-12T14:45:00-07:00</published>
<link href="https://tantek.com/2025/071/t2/w3c-authentic-web-technical-proposals" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2025/071/t2/w3c-authentic-web-technical-proposals</id>
<title type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
</title>
<content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">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</div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
</entry>
<entry>
<updated>2025-03-12T08:11:00-07:00</updated>
<published>2025-03-12T08:11:00-07:00</published>
<link href="https://tantek.com/2025/071/t1/w3c-authentic-web-workshop-flaws" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2025/071/t1/w3c-authentic-web-workshop-flaws</id>
<title type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
</title>
<content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">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></div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
</entry>
<entry>
<updated>2025-03-10T19:55:00-07:00</updated>
<published>2025-03-10T19:55:00-07:00</published>
<link href="https://tantek.com/2025/069/t1/ten-years-jsdr-javascript-required-didnt-read" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2025/069/t1/ten-years-jsdr-javascript-required-didnt-read</id>
<title type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
</title>
<content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">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.</div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
</entry>
<entry>
<updated>2025-02-24T16:10:00-08:00</updated>
<published>2025-02-24T16:10:00-08:00</published>
<link href="https://tantek.com/2025/055/t1/three-steps-indieweb-cybersecurity" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2025/055/t1/three-steps-indieweb-cybersecurity</id>
<title type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
</title>
<content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">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></div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
</entry>
<entry>
<updated>2025-02-21T13:37:00-08:00</updated>
<published>2025-02-21T13:37:00-08:00</published>
<link href="https://tantek.com/2025/052/b1/steps-indieweb-cybersecurity" rel="alternate" title="CSF_01: Three Steps for IndieWeb Cybersecurity" type="text/html"/>
<id>https://tantek.com/2025/052/b1/steps-indieweb-cybersecurity</id>
<title type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14">CSF_01: Three Steps for IndieWeb Cybersecurity</div>
</title>
<content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">
<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>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">article</object-type>
</entry>
<entry>
<updated>2025-02-03T12:10:00-08:00</updated>
<published>2025-02-03T12:10:00-08:00</published>
<link href="https://tantek.com/2025/034/t1/national-resilience-strategy" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2025/034/t1/national-resilience-strategy</id>
<title type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
</title>
<content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">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</div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
</entry>
<entry>
<updated>2025-01-20T14:04:00-08:00</updated>
<published>2025-01-20T14:04:00-08:00</published>
<link href="https://tantek.com/2025/020/t1/seek-2024-year-in-review" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2025/020/t1/seek-2024-year-in-review</id>
<title type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
</title>
<content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">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></div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
</entry>
<entry>
<updated>2025-01-15T18:03:00-08:00</updated>
<published>2025-01-15T18:03:00-08:00</published>
<link href="https://tantek.com/2025/015/t1/16-years-ago-new-calendar-simpler" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2025/015/t1/16-years-ago-new-calendar-simpler</id>
<title type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
</title>
<content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">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></div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
</entry>
<entry>
<updated>2025-01-12T21:23:00-08:00</updated>
<published>2025-01-12T21:23:00-08:00</published>
<link href="https://tantek.com/2025/012/t1/eight-years-webmention" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2025/012/t1/eight-years-webmention</id>
<title type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
</title>
<content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">🎉 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></div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
</entry>
<entry>
<updated>2025-01-11T23:23:00-08:00</updated>
<published>2025-01-11T23:23:00-08:00</published>
<link href="https://tantek.com/2025/011/t1/remembering-aaronsw-twelve-years" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2025/011/t1/remembering-aaronsw-twelve-years</id>
<title type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
</title>
<content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">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></div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
</entry>
<entry>
<updated>2025-01-05T10:23:00-08:00</updated>
<published>2025-01-05T10:23:00-08:00</published>
<link href="https://tantek.com/2025/005/t1/alan-watts-mystery-curiosity" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2025/005/t1/alan-watts-mystery-curiosity</id>
<title type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
</title>
<content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">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</div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
</entry>
</feed>

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

Download the "valid Atom 1.0" banner.
Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)
Add this HTML to your page (change the image src attribute if necessary):

<a href="http://www.feedvalidator.org/check.cgi?url=http%3A//tantek.com/updates.atom"><img src="valid-atom.png" alt="[Valid Atom 1.0]" title="Validate my Atom 1.0 feed" /></a>

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//tantek.com/updates.atom

Home · About · News · Docs · Terms