[Valid Atom 1.0] This is a valid Atom 1.0 feed.


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


  1. <?xml version="1.0" encoding="utf-8"?>
  2. <feed xmlns="" xml:lang="en-US">
  3.  <title>Tantek Çelik</title>
  4.  <link href="" rel="alternate" title="Tantek Çelik" type="text/html"/>
  5.  <link href="" rel="self"/>
  6.  <link rel="hub" href=""/>
  7.  <id></id>
  8.  <author>
  9.    <name>Tantek</name>
  10.    <uri></uri>
  11.  </author>
  12.  <updated>2023-11-22T19:02:00-08:00</updated>
  13.  <entry>
  14.    <updated>2023-10-31T12:16:00-07:00</updated>
  15.    <published>2023-10-31T12:16:00-07:00</published>
  16.    <link href="" rel="alternate" title="John Peart's post" type="text/html"/>
  17.    <id></id>
  18.    <title type="xhtml">
  19.      <div xmlns="" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
  20.    </title>
  21.    <content type="xhtml" xml:base="" xml:space="preserve">
  22.      <div xmlns="" xml:space="preserve">likes <a href="">John Peart's post</a></div>
  23.    </content>
  24.    <verb xmlns="">like</verb>
  25.    <object xmlns="">
  26.      <link href="" type="text/html" title="John Peart's post"/>
  27.    </object>
  28.  </entry>
  29.  <entry>
  30.    <updated>2023-10-29T08:18:00-07:00</updated>
  31.    <published>2023-10-29T08:18:00-07:00</published>
  32.    <link href="" rel="alternate" title="" type="text/html"/>
  33.    <id></id>
  34.    <title type="xhtml">
  35.      <div xmlns="" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
  36.    </title>
  37.    <content type="xhtml" xml:base="" xml:space="preserve">
  38.      <div xmlns="" xml:space="preserve">coding at #<span class="p-category auto-tag">IndieWebCamp</span> Nuremberg, completed the following projects:<br class="auto-break"/><br class="auto-break"/>0.0: fixed the <a class="auto-link" href=""></a> footer to drop #<span class="p-category auto-tag">Matrix</span> as an access option since their bridge is disabled (#IndieWeb IRC, Discord, and Slack still work great), and provided an explicit link/encouragement for filing issues<br class="auto-break"/><br class="auto-break"/>0.5: investigated IndieWeb wiki issues (mobile presentation), possible fixes, and documented them: <a class="auto-link" href=""></a><br class="auto-break"/><br class="auto-break"/>0.7: added HTML &lt;search&gt; element support to my home page and permalinks as nerdsniped by <a class="auto-link" href=""></a> (<a class="auto-link" href=""></a> <a class="auto-link h-cassis-username" href="">@adactio</a>); expanded to &lt;search role=search&gt; to also support folks using older browsers / screenreaders that only support #<span class="p-category auto-tag">ARIA</span> 1.1.<br class="auto-break"/><br class="auto-break"/>0.8: replaced my incorrect use of HTML attribute aria-hidden="true" (on my links to #<span class="p-category auto-tag">BridgyFed</span>) as pointed out by <a class="auto-link" href=""></a> (<a class="auto-link" href=""></a> <a class="auto-link h-cassis-username" href="">@jkphl</a>) and <a class="auto-link" href=""></a> (<a class="auto-link" href=""></a>), with hidden="from-humans". Since other values are allowed on the hidden attribute and treated as hidden="hidden", the "from-humans" value communicates a subtle semantic that the element is intended for consumption by robots &amp; crawlers, like #<span class="p-category auto-tag">Bridgy</span>.<br class="auto-break"/>0.8.1 Update: created a pull-request (<a class="auto-link" href=""></a>) to update the BridgyFed documentation markup examples to use the 'hidden' attribute accordingly as well. Update 2: it's been merged! e.g. <a class="auto-link" href=""></a><br class="auto-break"/><br class="auto-break"/>Time is up for today’s IndieWebCamp Create Day so my remaining projects will have to wait.</div>
  39.    </content>
  40.    <object-type xmlns="">note</object-type>
  41.  </entry>
  42.  <entry>
  43.    <updated>2023-10-27T16:23:00-07:00</updated>
  44.    <published>2023-10-27T16:23:00-07:00</published>
  45.    <link href="" rel="alternate" title="" type="text/html"/>
  46.    <id></id>
  47.    <title type="xhtml">
  48.      <div xmlns="" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
  49.    </title>
  50.    <content type="xhtml" xml:base="" xml:space="preserve">
  51.      <div xmlns="" xml:space="preserve">Inspiring mix of perspective expanding and personal talks at border:none (<a class="auto-link" href=""></a> <a class="auto-link h-cassis-username" href="">@border_none</a>) the past two days. Thanks speakers, volunteers, and especially organizers <a class="auto-link" href=""></a> (<a class="auto-link" href=""></a> <a class="auto-link h-cassis-username" href="">@marcthiele</a>) and <a class="auto-link" href=""></a> (<a class="auto-link" href=""></a> <a class="auto-link h-cassis-username" href="">@jkphl</a>).<br class="auto-break"/><br class="auto-break"/>Looking forward to the next two days at #<span class="p-category auto-tag">IndieWebCamp</span> Nürnberg <a class="auto-link" href=""></a> (<a class="auto-link" href=""></a> <a class="auto-link h-cassis-username" href="">@tollwerk</a>) of personal site demos, brainstorming sessions, and making, creating, &amp; hacking things from UX to protocols to improve &amp; interconnect our websites, with each other ( #<span class="p-category auto-tag">Webmention</span> ), #<span class="p-category auto-tag">fediverse</span> ( #<span class="p-category auto-tag">BridgyFed</span> &amp; #<span class="p-category auto-tag">ActivityPub</span> ), and others ( #<span class="p-category auto-tag">POSSE</span> #<span class="p-category auto-tag">backfeed</span> ).<br class="auto-break"/><br class="auto-break"/>Still a few spots if you’re in town or can hop on a train and join us Saturday &amp; Sunday!<br class="auto-break"/><br class="auto-break"/>🎟 Tickets: <a class="auto-link" href=""></a><br class="auto-break"/>🗓 Event: <a class="auto-link" href=""></a><br class="auto-break"/>ℹ️ More info: <a class="auto-link" href=""></a><br class="auto-break"/><br class="auto-break"/>#<span class="p-category auto-tag">bordernone</span> #<span class="p-category auto-tag">bono23</span> #<span class="p-category auto-tag">IndieWeb</span></div>
  52.    </content>
  53.    <object-type xmlns="">note</object-type>
  54.  </entry>
  55.  <entry>
  56.    <updated>2023-10-24T08:47:00-07:00</updated>
  57.    <published>2023-10-24T08:47:00-07:00</published>
  58.    <link href="" rel="alternate" title="David Pierce’s post" type="text/html"/>
  59.    <id></id>
  60.    <title type="xhtml">
  61.      <div xmlns="" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
  62.    </title>
  63.    <content type="xhtml" xml:base="" xml:space="preserve">
  64.      <div xmlns="" xml:space="preserve">likes <a href="">David Pierce’s post</a></div>
  65.    </content>
  66.    <verb xmlns="">like</verb>
  67.    <object xmlns="">
  68.      <link href="" type="text/html" title="David Pierce’s post"/>
  69.    </object>
  70.  </entry>
  71.  <entry>
  72.    <updated>2023-10-23T17:30:00-07:00</updated>
  73.    <published>2023-10-23T17:30:00-07:00</published>
  74.    <link href="" rel="alternate" title="" type="text/html"/>
  75.    <id></id>
  76.    <title type="xhtml">
  77.      <div xmlns="" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
  78.    </title>
  79.    <content type="xhtml" xml:base="" xml:space="preserve">
  80.      <div xmlns="" xml:space="preserve">Great article on #<span class="p-category auto-tag">POSSE</span> by <a class="auto-link" href=""></a> (<a class="auto-link" href=""></a> <a class="auto-link h-cassis-username" href="">@pierce</a>) <a class="auto-link h-cassis-username" href="">@Verge</a>:<br class="auto-break"/><br class="auto-break"/><a class="auto-link" href=""></a><br class="auto-break"/><br class="auto-break"/>Several key #<span class="p-category auto-tag">IndieWeb</span> POSSE practices explained:<br class="auto-break"/><br class="auto-break"/><br class="auto-break"/>First, post on your own site:<br class="auto-break"/><br class="auto-break"/> “In a POSSE world, everybody owns a domain name, and everybody has a blog. (… a place on the internet where you post your stuff and others consume it.)”<br class="auto-break"/> <br class="auto-break"/><br class="auto-break"/>Second, syndicate elsewhere, appropriately for each destination:<br class="auto-break"/><br class="auto-break"/> “Then, your long blog post might be broken into chunks and posted as a thread on X and Mastodon and Threads. The whole thing might go to your Medium page and your Tumblr and your LinkedIn profile, too. If you post a photo, it might go straight to Instagram, and a vertical video would whoosh straight to TikTok, Reels, and Shorts. Your post appears natively on all of those platforms,”<br class="auto-break"/><br class="auto-break"/>You can use Bridgy Publish (<a class="auto-link" href=""></a>) to POSSE to many destinations, and Bridgy Fed (<a class="auto-link" href=""></a>) to #<span class="p-category auto-tag">federate</span> to #<span class="p-category auto-tag">Mastodon</span> and other #<span class="p-category auto-tag">fediverse</span> destinations, directly from your site instead of posting a copy on yet another account on yet another server.<br class="auto-break"/><br class="auto-break"/><br class="auto-break"/>Third, and this is a key piece that distinguishes proper POSSE setups, with original post perma(short)links back to your posts on your domain:<br class="auto-break"/><br class="auto-break"/> “typically with some kind of link back to your blog.”<br class="auto-break"/> <br class="auto-break"/><br class="auto-break"/>All copies link to (your) home.<br class="auto-break"/><br class="auto-break"/> "And your blog becomes the hub for everything, your main home on the internet."<br class="auto-break"/> <br class="auto-break"/><br class="auto-break"/>You have power over your domain (name), not outside silos.<br class="auto-break"/><br class="auto-break"/><br class="auto-break"/>David embedded a screenshot of one of my posts, a reply post:<br class="auto-break"/><br class="auto-break"/><a class="auto-link figure" href=""><img class="auto-embed" alt="screenshot of Tantek replying to a tweet by Zeldman." src=""/></a><br class="auto-break"/>in which I posted a reply *on my own site*<a id="t5TZ1_ref-1" href="#t5TZ1_note-1">¹</a> to <a class="auto-link" href=""></a>’s tweet (itself a reply to a POSSE copy of one of my posts), and POSSEd my reply to Twitter so it would thread with his reply.<br class="auto-break"/><br class="auto-break"/>This illustrates another important detail of a proper POSSE setup:<br class="auto-break"/><br class="auto-break"/>Fourth, post *replies* and other responses from your own site, whether to other IndieWeb sites, or to others’s silo posts (tweets etc.).<br class="auto-break"/><br class="auto-break"/>Own your data means owning your replies as well.<br class="auto-break"/><br class="auto-break"/><br class="auto-break"/>David also noted several challenges and good questions about POSSE. Some of these have answers &amp; established practices, others are areas of exploration. E.g.<br class="auto-break"/><br class="auto-break"/> "The first is the social side of social media: what do you do with all the likes, replies, comments, and everything else that comes with your posts?"<br class="auto-break"/> <br class="auto-break"/>The short answer is #<span class="p-category auto-tag">backfeed:</span> <a class="auto-link" href=""></a><br class="auto-break"/><br class="auto-break"/>Backfeed is a concept I first wrote about as “reverse syndication”<a id="t5TZ1_ref-2" href="#t5TZ1_note-2">²</a>. <br class="auto-break"/><br class="auto-break"/>As you syndicate your posts out to #<span class="p-category auto-tag">socialMedia</span> silos, you reverse syndicate any responses there back to your original post. <br class="auto-break"/><br class="auto-break"/>Your site can do this with a service like #<span class="p-category auto-tag">Bridgy</span>, which uses the #<span class="p-category auto-tag">Webmention</span> standard to forward such silo responses back to your site, and #<span class="p-category auto-tag">BridgyFed</span> which does same for responses from Mastodon to your #<span class="p-category auto-tag">federated</span> posts.<br class="auto-break"/><br class="auto-break"/><br class="auto-break"/>David asked many other questions, which are deserving of their own posts to help answer, so I’ll leave you with just one more:<br class="auto-break"/><br class="auto-break"/> "The most immediate question, though, is simply how to build a POSSE system that works."<br class="auto-break"/><br class="auto-break"/>The short answer is: just start<a id="t5TZ1_ref-3" href="#t5TZ1_note-3">³</a>.<br class="auto-break"/><br class="auto-break"/>Even if you have to do it manually (until it hurts), even if you have to edit your posts on a static GitHub site (behind your domain name of course), and then copy &amp; paste to your silo(s) of choice, just start.<br class="auto-break"/><br class="auto-break"/>By practicing POSSE, even manually, you will learn what aspects of POSSE &amp; backfeed matter the most to you, what aspects actually involve reaching &amp; responding to friends and others you care about. <br class="auto-break"/><br class="auto-break"/>By doing so you will naturally focus on setting up &amp; making what you need, and you too can join the future of web publishing, today.<br class="auto-break"/><br class="auto-break"/>Questions? Join us in the chat: <a class="auto-link" href=""></a> (also on Discord, IRC, and Slack<a id="t5TZ1_ref-4" href="#t5TZ1_note-4">⁴</a>)<br class="auto-break"/><br class="auto-break"/><br class="auto-break"/>This is day 46 of #<span class="p-category auto-tag">100DaysOfIndieWeb</span>. #<span class="p-category auto-tag">100Days</span><br class="auto-break"/><br class="auto-break"/>← Day 45: <a class="auto-link" href=""></a><br class="auto-break"/>→ 🔮<br class="auto-break"/><br class="auto-break"/><br class="auto-break"/>Post glossary:<br class="auto-break"/><br class="auto-break"/>backfeed / reverse syndication<br class="auto-break"/>  <a class="auto-link" href=""></a><br class="auto-break"/>Bridgy <br class="auto-break"/>  <a class="auto-link" href=""></a><br class="auto-break"/>make what you need<br class="auto-break"/>  <a class="auto-link" href=""></a><br class="auto-break"/>manual (until it hurts)<br class="auto-break"/>  <a class="auto-link" href=""></a><br class="auto-break"/>original post link<br class="auto-break"/>  <a class="auto-link" href=""></a><br class="auto-break"/>own your data<br class="auto-break"/>  <a class="auto-link" href=""></a><br class="auto-break"/>own your replies<br class="auto-break"/>  <a class="auto-link" href=""></a><br class="auto-break"/>permalink <br class="auto-break"/>  <a class="auto-link" href=""></a><br class="auto-break"/>permashortlink<br class="auto-break"/>  <a class="auto-link" href=""></a><br class="auto-break"/>POSSE<br class="auto-break"/>  <a class="auto-link" href=""></a><br class="auto-break"/>silo<br class="auto-break"/>  <a class="auto-link" href=""></a><br class="auto-break"/>social media<br class="auto-break"/>  <a class="auto-link" href=""></a><br class="auto-break"/>static site<br class="auto-break"/>  <a class="auto-link" href=""></a><br class="auto-break"/>start<br class="auto-break"/>  <a class="auto-link" href=""></a><br class="auto-break"/>Webmention<br class="auto-break"/>  <a class="auto-link" href=""></a><br class="auto-break"/><br class="auto-break"/><br class="auto-break"/><a id="t5TZ1_note-1" href="#t5TZ1_ref-1">¹</a> <a class="auto-link" href=""></a><br class="auto-break"/><a id="t5TZ1_note-2" href="#t5TZ1_ref-2">²</a> <a class="auto-link" href=""></a><br class="auto-break"/><a id="t5TZ1_note-3" href="#t5TZ1_ref-3">³</a> <a class="auto-link" href=""></a><br class="auto-break"/><a id="t5TZ1_note-4" href="#t5TZ1_ref-4">⁴</a> <a class="auto-link" href=""></a></div>
  81.    </content>
  82.    <object-type xmlns="">note</object-type>
  83.  </entry>
  84.  <entry>
  85.    <updated>2023-10-16T18:16:00-07:00</updated>
  86.    <published>2023-10-16T18:16:00-07:00</published>
  87.    <link href="" rel="alternate" title="" type="text/html"/>
  88.    <id></id>
  89.    <title type="xhtml">
  90.      <div xmlns="" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
  91.    </title>
  92.    <content type="xhtml" xml:base="" xml:space="preserve">
  93.      <div xmlns="" xml:space="preserve">Implemented liking/favoriting of #<span class="p-category auto-tag">Mastodon</span> posts via Bridgy Fed on my site! (Actually of any post on any site that #<span class="p-category auto-tag">BridgyFed</span> can discover an #<span class="p-category auto-tag">ActivityPub</span> endpoint to send likes to.)<br class="auto-break"/><br class="auto-break"/>Tested it by liking <a class="auto-link" href=""></a> (<a class="auto-link" href=""></a> <a class="auto-link h-cassis-username" href="">@evanpro</a>)’s reply<a id="t5TS1_ref-1" href="#t5TS1_note-1">¹</a> confirming that he received a notification from my prior post<a id="t5TS1_ref-2" href="#t5TS1_note-2">²</a>. I sent a #<span class="p-category auto-tag">Webmention</span> from my like post<a id="t5TS1_ref-3" href="#t5TS1_note-3">³</a> to Bridgy Fed, and it #<span class="p-category auto-tag">federated</span> the like to Evan’s server, which subsequently showed up in the "favourites" list of Evan’s post:<br class="auto-break"/><br class="auto-break"/><a class="auto-link" href=""></a><br class="auto-break"/><br class="auto-break"/>Every step that connects heterogenous #<span class="p-category auto-tag">socialWeb</span> systems &amp; protocols feels like progress.<br class="auto-break"/><br class="auto-break"/>This is day 45 of #<span class="p-category auto-tag">100DaysOfIndieWeb</span>. #<span class="p-category auto-tag">100Days</span> #<span class="p-category auto-tag">IndieWeb</span> #<span class="p-category auto-tag">like</span> #<span class="p-category auto-tag">likes</span> #<span class="p-category auto-tag">fediverse</span> #<span class="p-category auto-tag">favorite</span> #<span class="p-category auto-tag">favourite</span> #<span class="p-category auto-tag">favourites</span><br class="auto-break"/><br class="auto-break"/>← Day 44: <a class="auto-link" href=""></a><br class="auto-break"/>→ Day 46: <a class="auto-link" href=""></a><br class="auto-break"/><br class="auto-break"/><a id="t5TS1_note-1" href="#t5TS1_ref-1">¹</a> <a class="auto-link" href=""></a><br class="auto-break"/><a id="t5TS1_note-2" href="#t5TS1_ref-2">²</a> <a class="auto-link" href=""></a><br class="auto-break"/><a id="t5TS1_note-3" href="#t5TS1_ref-3">³</a> <a class="auto-link" href=""></a></div>
  94.    </content>
  95.    <object-type xmlns="">note</object-type>
  96.  </entry>
  97.  <entry>
  98.    <updated>2023-10-16T13:03:00-07:00</updated>
  99.    <published>2023-10-16T13:03:00-07:00</published>
  100.    <link href="" rel="alternate" title="evan’s reply" type="text/html"/>
  101.    <id></id>
  102.    <title type="xhtml">
  103.      <div xmlns="" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
  104.    </title>
  105.    <content type="xhtml" xml:base="" xml:space="preserve">
  106.      <div xmlns="" xml:space="preserve">likes <a href="">evan’s reply</a></div>
  107.    </content>
  108.    <verb xmlns="">like</verb>
  109.    <object xmlns="">
  110.      <link href="" type="text/html" title="evan’s reply"/>
  111.    </object>
  112.  </entry>
  113.  <entry>
  114.    <updated>2023-10-14T19:37:00-07:00</updated>
  115.    <published>2023-10-14T19:37:00-07:00</published>
  116.    <link href="" rel="alternate" title="" type="text/html"/>
  117.    <id></id>
  118.    <title type="xhtml">
  119.      <div xmlns="" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
  120.    </title>
  121.    <content type="xhtml" xml:base="" xml:space="preserve">
  122.      <div xmlns="" xml:space="preserve">Bridgy Fed (#BridgyFed) recently added support for federating @-@-mentions to #<span class="p-category auto-tag">Mastodon:</span> <a class="auto-link" href=""></a><br class="auto-break"/><br class="auto-break"/>So here’s a test:<br class="auto-break"/><br class="auto-break"/>Happy birthday <a class="auto-link" href=""></a> (<a class="auto-link" href=""></a> <a class="auto-link h-cassis-username" href="">@evanpro</a>)!!!<br class="auto-break"/><br class="auto-break"/><br class="auto-break"/>Let’s see if Evan receives one or more notifications of these mentions, especially on cosocial, directly from my blog to his Mastodon account.<br class="auto-break"/><br class="auto-break"/><br class="auto-break"/>Previous related posts on how to @-mention across the #<span class="p-category auto-tag">IndieWeb</span>, #<span class="p-category auto-tag">fediverse</span>, and silos:<br class="auto-break"/>* <a class="auto-link" href=""></a><br class="auto-break"/>* <a class="auto-link" href=""></a><br class="auto-break"/>* <a class="auto-link" href=""></a><br class="auto-break"/>* <a class="auto-link" href=""></a><br class="auto-break"/>which is enough material on the subject to be worth a broader overall blog post on at-mentions, @-mentions, @-@-mentions, how to write them, how to send #<span class="p-category auto-tag">Webmentions</span> or #<span class="p-category auto-tag">federate</span> them, and perhaps how to recognize &amp; send notifications for them.</div>
  123.    </content>
  124.    <object-type xmlns="">note</object-type>
  125.  </entry>
  126.  <entry>
  127.    <updated>2023-10-04T23:55:00-07:00</updated>
  128.    <published>2023-10-04T23:55:00-07:00</published>
  129.    <link href="" rel="alternate" title="More Thoughtful Reading &amp; Writing on the Web" type="text/html"/>
  130.    <id></id>
  131.    <title type="xhtml">
  132.      <div xmlns="" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14">More Thoughtful Reading &amp; Writing on the Web</div>
  133.    </title>
  134.    <content type="xhtml" xml:base="" xml:space="preserve">
  135.      <div xmlns="" xml:space="preserve">
  136.        <div class="entry-content e-content">
  137. <p>
  138. <a class="h-card" href="">Ben Werdmuller</a>
  139. recently published an inspiring and thought-provoking blog post:
  140.  “<a href="">Subscribing to the blogs of people I follow on Mastodon</a>”.
  142. Beyond the insights and excellent developer how-to in his post, I believe it points to something larger: a fundamental thoughtfulness difference between writing rapid short-form posts (whether tweets or toots) and medium or longer form writing (on blogs or journals), and the impact of that difference on readers: that the act of reading more thoughtful writing nudges &amp; reinforces a reader into a more thoughtful state of mind.
  143. </p>
  144. <p>
  145. If you have not read
  146.  <a class="h-card" href="">Derek Powazek</a>’s watershed blog post
  147. “<a href="">The Argument Machine</a>”,
  148. I highly recommend you do so. In the nearly ten years since his post, Derek’s hypothesis of Twitter’s user interface design being the ultimate machine to create &amp; amplify disputes has been repeatedly demonstrated.
  149. </p>
  150. <p>
  151. Derek’s post predated Mastodon’s release by nearly three years. Ironically, by replicating much of Twitter’s user experience, Mastodon has in many ways also replicated its Argument Machine effects, except distributed across more servers.
  152. </p>
  153. <p>
  154. I’ve witnessed numerous otherwise rational, well-intentioned individuals write reactive posts on Mastodon, exactly what the Twitter-like interface encourages. Quick emotional responses rather than slower, more thoughtful posts and replies.
  155. </p>
  156. <p>
  157. I’ve seen the artificial urgency of tweets &amp; toots bleed over into emotional essays on public mailing lists. New participants join a list and immediately make entitled demands. Fearful bordering on paranoid assumptions are used to state assertions of “facts” without citations. Arguments are made that
  158.  <a href="">appeal to emotion</a>
  159.  (<i>argumentum ad passiones</i>)
  160. rather than reasoning from principles and shared values.
  161. </p>
  162. <p>
  163. Implicit in Ben’s post, “Subscribing to the <em>blogs</em> of <em>people</em>”
  164. (<em>emphasis</em> mine), is a preference for reading longer form writing, published on a site a human owns &amp; identifies with (a la
  165.  <a href="">#<span class="p-category">indieweb</span></a>),
  166. neither silo nor
  167.  <a href="">someone
  168.    else’s garage</a>.
  169. </p>
  170. <p>
  171. The combination of taking more time (as longer form writing encourages) and publishing on a domain associated with your name, your identity, enables &amp; incentivizes more thoughtful writing. More thoughtful writing elevates the reader to a more thoughtful state of mind.
  172. </p>
  173. <p>
  174. There is also a self-care aspect to this kind of deliberate shift. Ben wrote that he found himself “craving more nuance and depth” among “quick, in-the-now status updates”. I believe this points to a scarcity of thoughtfulness in such short form writings. Spending more time reading thoughtful posts not only alleviates such scarcity, it can also displace the artificial sense of urgency to respond when scrolling through soundbyte status updates.
  175. </p>
  176. <p>
  177. When I returned from
  178. <a href="">#<span class="p-category">W3CTPAC</span></a>,
  179. I made a list of all the thoughts, meetings, sessions that I wanted to write-up and publish as blog posts to capture my experiences, perspectives, and insights beyond any official minutes.
  180. </p>
  181. <p>
  182. Yet due to distractions such as catching up on short form posts, it took me over a week to write-up even a
  183.  <a href="">summary of my
  184.   <span class="p-category">TPAC</span> week</a>, nevermind the queue of per-topic notes I wanted to write-up. To even publish that I had to stop and cut-off reading short form posts, as well as ignoring (mostly postponing) numerous notifications.
  185. </p>
  186. <p>
  187. There’s a larger connection here between
  188.  <span class="p-category">thoughtful</span>
  189.  <span class="p-category">reading</span>,
  190. and finding, restoring, and rebuilding the ability to focus, a key to thoughtful
  191.  <span class="p-category">writing</span>.
  192. It requires not only reducing time spent on short form reading (and writing), but also reducing
  193.  <span class="p-category">notifications</span>,
  194. especially push notifications. That insight led me to wade into and garden the respective IndieWeb wiki pages for
  195. <a href="">notifications</a>,
  196. <a href="">push notifications</a>,
  197. and document a new page for
  198. <a href="">notification fatigue</a>.
  199. That broader topic of what do to about notifications is worth its own blog post (or a few), and a good place to end this post.
  200. </p>
  201. <p>
  202. Thanks again Ben for your blog post. May we spend more time reading &amp; writing such thoughtful posts.
  203. </p>
  204. </div>
  205.      </div>
  206.    </content>
  207.    <object-type xmlns="">article</object-type>
  208.  </entry>
  209.  <entry>
  210.    <updated>2023-09-24T18:33:00-07:00</updated>
  211.    <published>2023-09-24T18:33:00-07:00</published>
  212.    <link href="" rel="alternate" title="" type="text/html"/>
  213.    <id></id>
  214.    <title type="xhtml">
  215.      <div xmlns="" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
  216.    </title>
  217.    <content type="xhtml" xml:base="" xml:space="preserve">
  218.      <div xmlns="" xml:space="preserve">I recently wrote a high level summary blog post:<br class="auto-break"/><br class="auto-break"/>W3C Technical Plenary and Advisory Committee (TPAC) Meetings 2023<br class="auto-break"/><br class="auto-break"/><a class="auto-link" href=""></a><br class="auto-break"/><br class="auto-break"/>of my time at the #<span class="p-category auto-tag">W3C</span> (<a class="auto-link" href=""></a>, <a class="auto-link" href=""></a>, <a class="auto-link h-cassis-username" href="">@W3C</a>) #<span class="p-category auto-tag">TPAC</span> the week before.<br class="auto-break"/><br class="auto-break"/>Posting this note to explicitly #<span class="p-category auto-tag">hashtag</span> that article with topics mentioned therein:<br class="auto-break"/><br class="auto-break"/>#<span class="p-category auto-tag">Sevilla</span> #<span class="p-category auto-tag">Seville</span> #<span class="p-category auto-tag">Spain</span> #<span class="p-category auto-tag">WICG</span> #<span class="p-category auto-tag">SocialCG</span> #<span class="p-category auto-tag">SWICG</span> #<span class="p-category auto-tag">Fediverse</span> #<span class="p-category auto-tag">SocialWeb</span> #<span class="p-category auto-tag">sustainability</span> #<span class="p-category auto-tag">IndieWeb</span> #<span class="p-category auto-tag">ActivityPub</span><br class="auto-break"/><br class="auto-break"/>because I forgot to put explicit categories (p-category markup) in the article post.<br class="auto-break"/><br class="auto-break"/>Adding that markup after publishing, and then sending an ActivityPub update (via #<span class="p-category auto-tag">BridgyFed</span>) is apparently not enough for #<span class="p-category auto-tag">Mastodon</span> to notice that the Update has new tags to display and aggregate on tag pages. In my next #<span class="p-category auto-tag">w3cTPAC</span> article post I’ll be sure to include category markup before publishing and see if that works.<br class="auto-break"/><br class="auto-break"/>Post glossary:<br class="auto-break"/><br class="auto-break"/>article post<br class="auto-break"/>  <a class="auto-link" href=""></a><br class="auto-break"/>note post<br class="auto-break"/>  <a class="auto-link" href=""></a><br class="auto-break"/>p-category<br class="auto-break"/>  <a class="auto-link" href=""></a><br class="auto-break"/>tags<br class="auto-break"/>  <a class="auto-link" href=""></a></div>
  219.    </content>
  220.    <object-type xmlns="">note</object-type>
  221.  </entry>
  222.  <entry>
  223.    <updated>2023-09-19T19:58:00-07:00</updated>
  224.    <published>2023-09-19T19:58:00-07:00</published>
  225.    <link href="" rel="alternate" title="W3C Technical Plenary and Advisory Committee (TPAC) Meetings 2023" type="text/html"/>
  226.    <id></id>
  227.    <title type="xhtml">
  228.      <div xmlns="" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14">W3C Technical Plenary and Advisory Committee (TPAC) Meetings 2023</div>
  229.    </title>
  230.    <content type="xhtml" xml:base="" xml:space="preserve">
  231.      <div xmlns="" xml:space="preserve">
  232.        <div class="entry-content e-content">
  233. <aside><div class="aside">
  234. <h2>Second <abbr title="in real life">IRL</abbr> TPAC since 2019</h2>
  235. <p>As noted
  236.  <a href="">last
  237.    year</a>,
  238. the
  239.  <abbr title="World Wide Web Consortium">W3C</abbr>
  240. convened its annual
  241.  <abbr title="Technical Plenary and Advisory Committee">TPAC</abbr> meetings
  242. in-person from
  243.  <a href="">2001</a>-<a href="">2019</a>
  244. (<a href="">full list</a>).
  245. After a
  246.  <a href="">couple</a>
  247. of
  248.  <a href="">virtual</a>
  249. TPACs, last year
  250.  <span class="p-category">W3C</span>
  251. organized its  
  252.  <a href="">first officially <em>hybrid</em> TPAC</a>
  253. in Vancouver, British Columbia.
  254. I wrote
  255.  <a href="">one
  256.  blog post about one session</a>.
  257. Last week’s second hybrid
  258.  <span class="p-category">TPAC</span>,
  259. held in
  260.  <span class="p-category">Sevilla</span>,
  261.  <span class="p-category">Spain</span>,
  262. felt very different in a number of positive ways. This post is a summary of impressions and varied types of meetings I participated in, each of which merits its own post.
  263. </p>
  264. </div></aside>
  266. <p>
  267. This year’s W3C TPAC (Technical Plenary and Advisory Committee) meetings felt denser in many ways, packed tighter with more topics, and more active participants. There were so many specific things in specific meetings, new connections, victories, new challenges, that in addition to capturing summary notes, I'm considering writing blog posts about each meeting or session.
  268. </p>
  269. <p>
  270. Nearly all of them have public minutes that document both participants, and a good portion of what was discussed. I have my own notes, and combined with recollected details of what was minuted, I have my own observations to share. I encourage everyone who participated at TPAC (whether in-person or remote) to consider either writing a summary blog post about the experience, perhaps highlighting a few things that stood out, or if there were specific technical discussions that advanced something in a positive direction, or challenges blocking progress, those are worth their own blog posts as well.
  271. </p>
  272. <p class="h-event">
  273.  <a href="" class="p-name u-url">TPAC week 2023</a>
  274. took place from Monday
  275.  <time class="dt-start">2023-09-11</time>
  276.  through Friday
  277.  <time class="dt-end">2023-09-15</time>,
  278. in
  279.  <span class="p-location h-adr"><span class="p-locality">Sevilla</span>,
  280.    <span class="p-country-name">Spain</span></span>.
  281. </p>
  282. <p>
  283. Here is a summary outline of meetings, sessions, and discussions I participated in. Not listed: conversations at breakfasts, morning &amp; afternoon breaks, lunches, dinners, and of course hallways. Unlinked for now, each of these has a calendar event with description, minutes, almost all of which are public.
  284. </p>
  285. <ul>
  286. <li>Monday
  287. <ul><li><abbr class="p-category">WICG</abbr> (Web Incubator Community Group)</li>
  288. </ul></li>
  289. <li>Tuesday
  290. <ul><li>Social Web Incubator CG (community group), AKA
  291.      <abbr class="p-category">SocialCG</abbr> or
  292.      <abbr class="p-category">SWICG</abbr></li>
  293.    <li><abbr title="Decentrlized Identifiers Working Group">DID WG</abbr>
  294.          rechartering discussion</li>
  295.    <li><abbr title="Advisory Committee">AC</abbr> meeting</li>
  296.    <li>Vision <abbr title="task force">TF</abbr></li>
  297.    <li><span class="p-category">Fediverse</span> meetup</li>
  298. </ul></li>
  299. <li>Wednesday — Breakouts day!
  300. <ul><li>Chartering at W3C</li>
  301.    <li>Technical Roadmap at W3C</li>
  302.    <li><span class="p-category">SocialWeb</span> Test Suite Discussion</li>
  303.    <li>SocialWeb Data Portability Discussion</li>
  304.    <li>Introducing the Web
  305.      <span class="p-category">Sustainability</span>
  306.      Guidelines (WSGs)</li>
  307.    <li>Report to Members, Hearing from Members</li>
  308.    <li>Technical Plenary reception</li>
  309. </ul></li>
  310. <li>Thursday
  311. <ul><li><abbr title="Cascading Style Sheets Working Group">CSS WG</abbr>, briefly</li>
  312.    <li>Afternoon break:
  313.      <abbr title="Social Linked Data">Solid</abbr>
  314.      charter discussions, use-cases,
  315.      <span class="p-category">IndieWeb</span> Micropub,
  316.      <span class="p-category">ActivityPub</span></li>
  317. </ul></li>
  318. <li>Friday
  319. <ul><li>Social CG planning</li>
  320.    <li>Departing conversations &amp; reflections</li>
  321. </ul></li>
  322. </ul>
  323. <p>
  324. Those are the sessions &amp; discussions that I found in my notes.
  325. I also met a lot of new people during meetings, meals, and discussions at breaks.
  326. As I write up my notes on specific sessions and their minutes (and hyperlink the above list items), I expect to recall more context and details. If you were at TPAC in
  327.  <span class="p-category">Seville</span>,
  328. I encourage you to write-up your experiences as well, while the thoughts, feelings, and insights are fresh in your mind. By documenting &amp; publishing our collective experiences (using the
  329.  <a href="">#<span class="p-category">w3cTPAC</span></a>
  330. hashtag) we can build upon them together. <a href="" hidden="from-humans"> </a>
  331. </p>
  332. </div>
  333.      </div>
  334.    </content>
  335.    <object-type xmlns="">article</object-type>
  336.  </entry>
  337. </feed>

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

  1. Download the "valid Atom 1.0" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

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

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda