Congratulations!

[Valid Atom 1.0] 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.

Source: http://tantek.com/log/posts.atom

  1. <?xml version="1.0" encoding="utf-8"?>
  2. <feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-US">
  3.  <title>Tantek Çelik</title>
  4.  <link href="https://tantek.com/" rel="alternate" title="Tantek Çelik" type="text/html"/>
  5.  <link href="https://tantek.com/updates.atom" rel="self"/>
  6.  <link rel="hub" href="https://pubsubhubbub.superfeedr.com/"/>
  7.  <id>https://tantek.com/updates.atom</id>
  8.  <author>
  9.    <name>Tantek</name>
  10.    <uri>https://tantek.com/</uri>
  11.  </author>
  12.  <updated>2024-09-03T23:11:00-07:00</updated>
  13.  <entry>
  14.    <updated>2024-09-03T23:11:00-07:00</updated>
  15.    <published>2024-09-03T23:11:00-07:00</published>
  16.    <link href="https://tantek.com/2024/247/t4/w3c-link-checker-before-federating" rel="alternate" title="" type="text/html"/>
  17.    <id>https://tantek.com/2024/247/t4/w3c-link-checker-before-federating</id>
  18.    <title type="xhtml">
  19.      <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"/>
  20.    </title>
  21.    <content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
  22.      <div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">Tip: use the W3C Link Checker and fix any errors before federating with Bridgy Fed.<br class="auto-break"/><br class="auto-break"/><a class="auto-link" href="https://validator.w3.org/checklink">https://validator.w3.org/checklink</a><br class="auto-break"/><br class="auto-break"/>If you are using Bridgy Fed to federate your posts from your personal site, I highly recommend you first run the W3C Link Checker on a post, and verify there are no “red” errors (or fix any you find), before pinging Bridgy Fed to federate the post.<br class="auto-break"/><br class="auto-break"/>The reason is that if your post contains broken links, especially broken https: links as part of an @-mention, a weird set of timeout interactions will occur between #<span class="p-category auto-tag">BridgyFed</span> and #<span class="p-category auto-tag">Mastodon</span> that will cause any Mastodon instances following your posts to drop your federated posts as if they had not been received. <br class="auto-break"/><br class="auto-break"/>Further, those instances will also ignore any UPDATES to that post.<br class="auto-break"/><br class="auto-break"/>More discussion here:<br class="auto-break"/>* <a class="auto-link" href="https://chat.indieweb.org/dev/2024-09-04#t1725421768496000">https://chat.indieweb.org/dev/2024-09-04#t1725421768496000</a><br class="auto-break"/>More bug details here:<br class="auto-break"/>* <a class="auto-link" href="https://github.com/snarfed/bridgy-fed/issues/884#issuecomment-2327861883">https://github.com/snarfed/bridgy-fed/issues/884#issuecomment-2327861883</a><br class="auto-break"/><br class="auto-break"/>#<span class="p-category auto-tag">IndieWeb</span> #<span class="p-category auto-tag">federate</span> #<span class="p-category auto-tag">fediverse</span> #<span class="p-category auto-tag">interoperability</span><br class="auto-break"/><br class="auto-break"/>This is post 22 of #<span class="p-category auto-tag">100PostsOfIndieWeb</span>. #<span class="p-category auto-tag">100Posts</span><br class="auto-break"/><br class="auto-break"/>← <a class="auto-link" href="https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed">https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed</a><br class="auto-break"/>→ 🔮</div>
  23.    </content>
  24.    <object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
  25.  </entry>
  26.  <entry>
  27.    <updated>2024-09-03T18:47:00-07:00</updated>
  28.    <published>2024-09-03T18:47:00-07:00</published>
  29.    <link href="https://tantek.com/2024/247/t2/twenty-years-microformats-shorter2" rel="alternate" title="" type="text/html"/>
  30.    <id>https://tantek.com/2024/247/t2/twenty-years-microformats-shorter2</id>
  31.    <title type="xhtml">
  32.      <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"/>
  33.    </title>
  34.    <content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
  35.      <div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">Twenty years ago this past February, Kevin Marks and I introduced #<span class="p-category auto-tag">microformats</span> in a conference presentation.<br class="auto-break"/><br class="auto-break"/>Full post: <a class="auto-link" href="https://tantek.com/2024/044/t1/twenty-years-microformats">https://tantek.com/2024/044/t1/twenty-years-microformats</a><br class="auto-break"/><br class="auto-break"/>Aside: This is an even shorter summary of that post from ~200 days ago, which #<span class="p-category auto-tag">Mastodon</span> readers never got due to a Mastodon #<span class="p-category auto-tag">federation</span> bug (details in <a class="auto-link" href="https://tantek.com/t5Yo1">https://tantek.com/t5Yo1</a>).<br class="auto-break"/><br class="auto-break"/>Since early 2023, here are the top three updates &amp; interesting developments in microformats:<br class="auto-break"/><br class="auto-break"/>1. Growing rel=me adoption for distributed verification (✅ in Mastodon etc.)<br class="auto-break"/> * Wikipedia, Threads, <a class="auto-link" href="http://omg.lol">omg.lol</a><br class="auto-break"/>2. Proposal to merge #<span class="p-category auto-tag">microformats2</span> h-review into h-entry, since in practice (e.g. on #<span class="p-category auto-tag">indieweb</span>) reviews are just entries with a bit more.<br class="auto-break"/>3. #<span class="p-category auto-tag">metaformats</span> adoptions, implementations, iteration</div>
  36.    </content>
  37.    <object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
  38.  </entry>
  39.  <entry>
  40.    <updated>2024-09-03T14:02:00-07:00</updated>
  41.    <published>2024-09-03T14:02:00-07:00</published>
  42.    <link href="https://tantek.com/2024/247/t1/twenty-years-microformats-summary" rel="alternate" title="" type="text/html"/>
  43.    <id>https://tantek.com/2024/247/t1/twenty-years-microformats-summary</id>
  44.    <title type="xhtml">
  45.      <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"/>
  46.    </title>
  47.    <content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
  48.      <div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">Twenty years ago this past February, <a class="auto-link" href="https://KevinMarks.com">@KevinMarks.com</a> (<a class="auto-link" href="https://xoxo.zone/@KevinMarks">@KevinMarks@xoxo.zone</a>) and I introduced #<span class="p-category auto-tag">microformats</span> in a conference presentation.<br class="auto-break"/><br class="auto-break"/>Full post: <a class="auto-link" href="https://tantek.com/2024/044/t1/twenty-years-microformats">https://tantek.com/2024/044/t1/twenty-years-microformats</a><br class="auto-break"/><br class="auto-break"/>Aside: This is a summary of a longer post from ~200 days ago<a id="t5Yp1_ref-1" href="#t5Yp1_note-1">¹</a>, which #<span class="p-category auto-tag">Mastodon</span> readers never got due to a Mastodon #<span class="p-category auto-tag">federation</span> bug (instances returned 202 for post inbox delivery, but did not show post to followers or on local profiles, details in <a class="auto-link" href="https://tantek.com/t5Yo1">https://tantek.com/t5Yo1</a>).<br class="auto-break"/><br class="auto-break"/>I wrote a retrospective last year: <a class="auto-link" href="https://tantek.com/2023/047/t1/nineteen-years-microformats">https://tantek.com/2023/047/t1/nineteen-years-microformats</a><br class="auto-break"/><br class="auto-break"/>Since then, here are the top three updates &amp; interesting developments in microformats:<br class="auto-break"/><br class="auto-break"/>1. Growing rel=me adoption for distributed verification (✅ in Mastodon etc.)<br class="auto-break"/> * Wikipedia, Threads, <a class="auto-link" href="http://omg.lol">omg.lol</a> support<br class="auto-break"/>2. A proposal to merge #<span class="p-category auto-tag">microformats2</span> h-review into h-entry, since reviews are in practice (e.g. on the #<span class="p-category auto-tag">indieweb</span>) always entries with a bit more information.<br class="auto-break"/>3. #<span class="p-category auto-tag">metaformats</span> adoptions, implementations, and iteration<br class="auto-break"/><br class="auto-break"/>More details: <br class="auto-break"/><a id="t5Yp1_note-1" href="#t5Yp1_ref-1">¹</a> <a class="auto-link" href="https://tantek.com/2024/044/t1/twenty-years-microformats">https://tantek.com/2024/044/t1/twenty-years-microformats</a></div>
  49.    </content>
  50.    <object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
  51.  </entry>
  52.  <entry>
  53.    <updated>2024-09-02T22:32:00-07:00</updated>
  54.    <published>2024-09-02T22:32:00-07:00</published>
  55.    <link href="https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed" rel="alternate" title="" type="text/html"/>
  56.    <id>https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed</id>
  57.    <title type="xhtml">
  58.      <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"/>
  59.    </title>
  60.    <content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
  61.      <div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">Adventures in IndieWeb / ActivityPub (AP) bridging:<br class="auto-break"/><br class="auto-break"/>While in general my posts are being successfully federated by <a class="auto-link" href="https://fed.brid.gy/">https://fed.brid.gy/</a> #<span class="p-category auto-tag">BridgyFed</span>, most of my recent posts, and two more earlier this year, were delivered successfully to multiple #<span class="p-category auto-tag">Mastodon</span> instances AP inboxes (returned 202), however the posts do not show up if you look-up my profile on those instances (and thus followers never saw them).<br class="auto-break"/><br class="auto-break"/>Update: workaround found: <a class="auto-link" href="https://tantek.com/2024/247/t4/w3c-link-checker-before-federating">https://tantek.com/2024/247/t4/w3c-link-checker-before-federating</a><br class="auto-break"/><br class="auto-break"/>These very recent posts:<br class="auto-break"/>* <a class="auto-link" href="https://tantek.com/2024/247/t2/twenty-years-microformats-shorter">https://tantek.com/2024/247/t2/twenty-years-microformats-shorter</a><br class="auto-break"/>* <a class="auto-link" href="https://tantek.com/2024/247/t1/twenty-years-microformats-summary">https://tantek.com/2024/247/t1/twenty-years-microformats-summary</a><br class="auto-break"/>* <a class="auto-link" href="https://tantek.com/2024/245/t1/read-write-suggest-edit-web">https://tantek.com/2024/245/t1/read-write-suggest-edit-web</a><br class="auto-break"/>* <a class="auto-link" href="https://tantek.com/2024/242/t1/indiewebcamp-portland">https://tantek.com/2024/242/t1/indiewebcamp-portland</a><br class="auto-break"/>* <a class="auto-link" href="https://tantek.com/2024/238/t3/indiewebcamp-auto-linking">https://tantek.com/2024/238/t3/indiewebcamp-auto-linking</a><br class="auto-break"/>and these earlier this year:<br class="auto-break"/>* <a class="auto-link" href="https://tantek.com/2024/173/t1/years-posse-microformats-adoption">https://tantek.com/2024/173/t1/years-posse-microformats-adoption</a><br class="auto-break"/>* <a class="auto-link" href="https://tantek.com/2024/044/t1/twenty-years-microformats">https://tantek.com/2024/044/t1/twenty-years-microformats</a><br class="auto-break"/><br class="auto-break"/>were all delivered to over 300 instances, which returned "202" codes, however none of them show up in profile views on those instances, e.g.<br class="auto-break"/>* <a class="auto-link" href="https://indieweb.social/@tantek.com@tantek.com">https://indieweb.social/@tantek.com@tantek.com</a><br class="auto-break"/>* <a class="auto-link" href="https://mastodon.social/@tantek.com@tantek.com">https://mastodon.social/@tantek.com@tantek.com</a><br class="auto-break"/>* <a class="auto-link" href="https://social.coop/@tantek.com@tantek.com">https://social.coop/@tantek.com@tantek.com</a><br class="auto-break"/>* <a class="auto-link" href="https://w3c.social/@tantek.com@tantek.com">https://w3c.social/@tantek.com@tantek.com</a><br class="auto-break"/>(My most recent post on all of these is the same 2024-08-25 post starting with “All setup here at IndieWebCamp Portland!”)<br class="auto-break"/><br class="auto-break"/>Why would a Mastodon instance respond with a 202 to an AP inbox delivery and then not show that post on the local profile view?<br class="auto-break"/><br class="auto-break"/>GitHub tracking bug in case you can help narrow/track this down or have <br class="auto-break"/>* <a class="auto-link" href="https://github.com/snarfed/bridgy-fed/issues/884">https://github.com/snarfed/bridgy-fed/issues/884</a><br class="auto-break"/><br class="auto-break"/>Let’s see if this post makes it to your Mastodon (or other #<span class="p-category auto-tag">fediverse</span>) reader/client.<br class="auto-break"/><br class="auto-break"/>Update: ironically this very post itself (with plenty of links, including links to my domain) showed up so I’m quite confused why Mastodon is dropping some posts and not others.<br class="auto-break"/><br class="auto-break"/>Update 2: it appears all the posts that Mastodon dropped on the floor have @-domain references, e.g. to @-KevinMarks-.-com (without the "-"s). When I changed that @-domain mention to just “Kevin Marks” in <a class="auto-link" href="https://tantek.com/2024/247/t2/twenty-years-microformats-shorter">https://tantek.com/2024/247/t2/twenty-years-microformats-shorter</a>, it got delivered and shown on Mastodon no problem, with a new slug of <a class="auto-link" href="https://tantek.com/2024/247/t2/twenty-years-microformats-shorter2">https://tantek.com/2024/247/t2/twenty-years-microformats-shorter2</a>. <br class="auto-break"/><br class="auto-break"/>Something about the ActivityStreams2 that BridgyFed is generating for hyperlinked @-domain mentions is causing Mastodon to choke and fail to show the post to followers and in a local profile.<br class="auto-break"/><br class="auto-break"/><br class="auto-break"/>#<span class="p-category auto-tag">indieweb</span> #<span class="p-category auto-tag">ActivityPub</span> <br class="auto-break"/><br class="auto-break"/>This is post 21 of #<span class="p-category auto-tag">100PostsOfIndieWeb</span>. #<span class="p-category auto-tag">100Posts</span><br class="auto-break"/><br class="auto-break"/>← <a class="auto-link" href="https://tantek.com/2024/245/t1/read-write-suggest-edit-web">https://tantek.com/2024/245/t1/read-write-suggest-edit-web</a><br class="auto-break"/>→ <a class="auto-link" href="https://tantek.com/2024/247/t4/w3c-link-checker-before-federating">https://tantek.com/2024/247/t4/w3c-link-checker-before-federating</a></div>
  62.    </content>
  63.    <object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
  64.  </entry>
  65.  <entry>
  66.    <updated>2024-09-01T14:51:00-07:00</updated>
  67.    <published>2024-09-01T14:51:00-07:00</published>
  68.    <link href="https://tantek.com/2024/245/t1/read-write-suggest-edit-update-web" rel="alternate" title="" type="text/html"/>
  69.    <id>https://tantek.com/2024/245/t1/read-write-suggest-edit-update-web</id>
  70.    <title type="xhtml">
  71.      <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"/>
  72.    </title>
  73.    <content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
  74.      <div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">✏️ I want the Read Write Suggest-Edit Accept-Edit Update Web.<br class="auto-break"/><br class="auto-break"/>The consumer Infinite Scroll Web leaves us feeling empty.<br class="auto-break"/><br class="auto-break"/>Too few of us participate in the Read Write Web, whether with personal sites or Wikipedia.<br class="auto-break"/><br class="auto-break"/>A week ago when we wrapped up #<span class="p-category auto-tag">IndieWebCamp</span> Portland and I was reading Kevin Marks (<a class="auto-link" href="https://indieweb.social/@kevinmarks">@kevinmarks@indieweb.social</a>) live-tooting of the demos<a id="t5Yn1_ref-1" href="#t5Yn1_note-1">¹</a>, I noticed a few errors, typos or miscaptures, and pointed them out in-person.<br class="auto-break"/><br class="auto-break"/>Kevin was able to quickly edit his toots and update them for anyone reading, thanks to #<span class="p-category auto-tag">Mastodon</span>’s post editing feature and its support of #<span class="p-category auto-tag">ActivityPub</span> Updates. But this shouldn’t require being in the same room, whether IRL or chat.<br class="auto-break"/><br class="auto-break"/>We should be able to suggest edits to each other’s posts, as easily as we can reply and add a comment.<br class="auto-break"/><br class="auto-break"/>13 years ago I wrote<a id="t5Yn1_ref-2" href="#t5Yn1_note-2">²</a>:<br class="auto-break"/><br class="auto-break"/> “The Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.”<br class="auto-break"/><br class="auto-break"/>Now I want the Read Write Suggest-Edit Accept-Edit Update Web.<br class="auto-break"/><br class="auto-break"/>The ↪ Reply button is fairly ubiquitous in modern post user interfaces (UIs).<br class="auto-break"/><br class="auto-break"/>Why not also a ✏️ Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid "performative" suggested edits.<br class="auto-break"/><br class="auto-break"/>If the author’s posts provide revision histories, when a suggested edit is accepted, a post’s history could show the contributor of the edit.<br class="auto-break"/><br class="auto-break"/>Instead of asking Kevin in-person, what if I could have posted special "Suggested Edit" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots?<br class="auto-break"/><br class="auto-break"/>To enable such UIs and interactions across servers and implementations, we may need a new type of response<a id="t5Yn1_ref-3" href="#t5Yn1_note-3">³</a>, perhaps with a special property (or more) to convey the edits being suggested.<br class="auto-break"/><br class="auto-break"/>There is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #<span class="p-category auto-tag">IndieWeb</span> wiki:<br class="auto-break"/>* <a class="auto-link" href="https://indieweb.org/edit">https://indieweb.org/edit</a><br class="auto-break"/><br class="auto-break"/>Our interaction after IndieWebCamp has inspired me to take another look at how can we design and prototype solutions to this problem.<br class="auto-break"/><br class="auto-break"/>For now, if you host your blog and posts as static files on GitHub (or equivalent), you could add a button like this to your posts alongside Like, Reply, Repost buttons:<br class="auto-break"/><br class="auto-break"/>✏️ Suggest Edit<br class="auto-break"/><br class="auto-break"/>and link it to an edit URL for the static file for the post.<br class="auto-break"/><br class="auto-break"/>I don’t use GitHub static files myself for posts, but here’s an example of such an edit link for one of my projects:<br class="auto-break"/><br class="auto-break"/><a class="auto-link" href="https://tantek.com/github/cassis/edit/main/README.md">https://tantek.com/github/cassis/edit/main/README.md</a><br class="auto-break"/><br class="auto-break"/>This will start the process of creating a “pull request”, GitHub’s jargon<a id="t5Yn1_ref-4" href="#t5Yn1_note-4">⁴</a> for a “suggested edit”.<br class="auto-break"/><br class="auto-break"/>After completing GitHub’s ceremony of entering multiple text fields (summary &amp; description), and multiple clicks to create said “pull request”, it’ll be sent to the author to review. Presuming the author likes the suggested edit, they can perform the other half of GitHub’s jargon-filled ceremonies to “Merge” or “Squash &amp; Merge”, “Delete fork”, etc. to accept the edit.<br class="auto-break"/><br class="auto-break"/>It’s an awkward interaction<a id="t5Yn1_ref-5" href="#t5Yn1_note-5">⁵</a>, however useful for at least prototyping a ✏️ Suggest Edit button on sites that store their posts as files in GitHub. Certainly worthy of experimenting with and gathering experience to design and build even better interactions.<br class="auto-break"/><br class="auto-break"/>We can start with the shortest path to getting something working, then learn, iterate, improve, repeat.<br class="auto-break"/><br class="auto-break"/>#<span class="p-category auto-tag">readWriteWeb</span> #<span class="p-category auto-tag">editableWeb</span> #<span class="p-category auto-tag">suggestEdit</span> #<span class="p-category auto-tag">acceptEdit</span><br class="auto-break"/><br class="auto-break"/>References:<br class="auto-break"/><br class="auto-break"/><a id="t5Yn1_note-1" href="#t5Yn1_ref-1">¹</a> <a class="auto-link" href="https://indieweb.social/@kevinmarks/113025295600067213">https://indieweb.social/@kevinmarks/113025295600067213</a><br class="auto-break"/><a id="t5Yn1_note-2" href="#t5Yn1_ref-2">²</a> <a class="auto-link" href="https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11">https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11</a><br class="auto-break"/><a id="t5Yn1_note-3" href="#t5Yn1_ref-3">³</a> <a class="auto-link" href="https://indieweb.org/responses">https://indieweb.org/responses</a><br class="auto-break"/><a id="t5Yn1_note-4" href="#t5Yn1_ref-4">⁴</a> The phrase “pull request” was derived from the git command: “git request-pull” according to <a class="auto-link" href="https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/">https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/</a><br class="auto-break"/><a id="t5Yn1_note-5" href="#t5Yn1_ref-5">⁵</a> “edits” in GitHub require taking far more steps, and navigating far more jargon, then say, Wikipedia pages, which come down to “Edit” and “Save”. We should aspire to Wikipedia’s simplicity, not GitHub’s ceremonies.<br class="auto-break"/><br class="auto-break"/>This is post 20 of #<span class="p-category auto-tag">100PostsOfIndieWeb</span>. #<span class="p-category auto-tag">100Posts</span><br class="auto-break"/><br class="auto-break"/>← <a class="auto-link" href="https://tantek.com/2024/242/t1/indiewebcamp-portland">https://tantek.com/2024/242/t1/indiewebcamp-portland</a><br class="auto-break"/>→ <a class="auto-link" href="https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed">https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed</a></div>
  75.    </content>
  76.    <object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
  77.  </entry>
  78.  <entry>
  79.    <updated>2024-08-29T21:09:00-07:00</updated>
  80.    <published>2024-08-29T21:09:00-07:00</published>
  81.    <link href="https://tantek.com/2024/242/t1/indiewebcamp-portland-10" rel="alternate" title="" type="text/html"/>
  82.    <id>https://tantek.com/2024/242/t1/indiewebcamp-portland-10</id>
  83.    <title type="xhtml">
  84.      <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"/>
  85.    </title>
  86.    <content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
  87.      <div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">Had a great time at IndieWebCamp Portland 2024 this past Sunday — our 10th IndieWebCamp in Portland!<br class="auto-break"/><br class="auto-break"/><a class="auto-link" href="https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k">https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k</a><br class="auto-break"/><br class="auto-break"/>Being a one day #<span class="p-category auto-tag">IndieWebCamp</span>, we focused more on making, hacking, and creating, than on formal discussion sessions.<br class="auto-break"/><br class="auto-break"/>Nearly everyone gave a brief personal site intro with a summary of how they use their #<span class="p-category auto-tag">IndieWeb</span> site and what they would like to add, remove, or improve.<br class="auto-break"/>* <a class="auto-link" href="https://indieweb.org/2024/Portland/Intros">https://indieweb.org/2024/Portland/Intros</a><br class="auto-break"/><br class="auto-break"/>There were lots of informal discussions, some in the main room, on the walk to and from lunch, over lunch in the nearby outdoor patio, or at tables inside the lobby of the Hotel Grand Stark.<br class="auto-break"/><br class="auto-break"/>We wrapped up with our usual Create Day<a id="t5Yj1_ref-1" href="#t5Yj1_note-1">¹</a> Demos session, live streamed for remote attendees to see as well. Lots of great demos of things people built, designed, removed, cleaned-up, documented, and blogged! Everyone still at the camp showed something on their personal site!<br class="auto-break"/>* <a class="auto-link" href="https://indieweb.org/2024/Portland/Demos">https://indieweb.org/2024/Portland/Demos</a><br class="auto-break"/><br class="auto-break"/>Group photo and lots more about IndieWebCamp Portland 2024 at the event’s wiki page:<br class="auto-break"/>* <a class="auto-link" href="https://indieweb.org/2024/Portland">https://indieweb.org/2024/Portland</a><br class="auto-break"/><br class="auto-break"/>Thanks to everyone who pitched in to help organize IndieWebCamp Portland 2024! Thanks especially to Marty McGuire (<a class="auto-link" href="https://martymcgui.re">@martymcgui.re</a>) for taking live notes during both the personal site intros and create day demos, to Kevin Marks (<a class="auto-link" href="https://indieweb.social/@kevinmarks">@kevinmarks@indieweb.social</a> <a class="auto-link" href="https://xoxo.zone/@kevinmarks">@kevinmarks@xoxo.zone</a> <a class="auto-link h-cassis-username" href="https://twitter.com/kevinmarks">@kevinmarks</a>) for the IndieWebCamp live-tooting, and Ryan Barrett (<a class="auto-link" href="https://snarfed.org">@snarfed.org</a>) for amazing breakfast pastries from Dos Hermanos.<br class="auto-break"/><br class="auto-break"/>The experience definitely raised our hopes and confidence for returning to Portland in 2025.<a id="t5Yj1_ref-2" href="#t5Yj1_note-2">²</a><br class="auto-break"/><br class="auto-break"/><br class="auto-break"/>References:<br class="auto-break"/><br class="auto-break"/><a id="t5Yj1_note-1" href="#t5Yj1_ref-1">¹</a> <a class="auto-link" href="https://indieweb.org/Create_Day">https://indieweb.org/Create_Day</a><br class="auto-break"/><a id="t5Yj1_note-2" href="#t5Yj1_ref-2">²</a> <a class="auto-link" href="https://indieweb.org/Planning#Portland">https://indieweb.org/Planning#Portland</a><br class="auto-break"/><br class="auto-break"/>This is post 19 of #<span class="p-category auto-tag">100PostsOfIndieWeb</span>. #<span class="p-category auto-tag">100Posts</span> #<span class="p-category auto-tag">2024_238</span><br class="auto-break"/><br class="auto-break"/>← <a class="auto-link" href="https://tantek.com/2024/238/t3/indiewebcamp-auto-linking">https://tantek.com/2024/238/t3/indiewebcamp-auto-linking</a><br class="auto-break"/>→ <a class="auto-link" href="https://tantek.com/2024/245/t1/read-write-suggest-edit-web">https://tantek.com/2024/245/t1/read-write-suggest-edit-web</a></div>
  88.    </content>
  89.    <object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
  90.  </entry>
  91.  <entry>
  92.    <updated>2024-08-25T16:00:00-07:00</updated>
  93.    <published>2024-08-25T16:00:00-07:00</published>
  94.    <link href="https://tantek.com/2024/238/t3/indiewebcamp-auto-link" rel="alternate" title="" type="text/html"/>
  95.    <id>https://tantek.com/2024/238/t3/indiewebcamp-auto-link</id>
  96.    <title type="xhtml">
  97.      <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"/>
  98.    </title>
  99.    <content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
  100.      <div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">Nice #<span class="p-category auto-tag">IndieWebCamp</span> discussion session with Kevin Marks (<a class="auto-link" href="https://indieweb.social/@kevinmarks">@kevinmarks@indieweb.social</a> <a class="auto-link" href="https://xoxo.zone/@kevinmarks">@kevinmarks@xoxo.zone</a> <a class="auto-link h-cassis-username" href="https://twitter.com/kevinmarks">@kevinmarks</a>) on the topic of auto-linking<a id="t5Yf3_ref-1" href="#t5Yf3_note-1">¹</a>.<br class="auto-break"/><br class="auto-break"/>I’ve implemented an auto_link function<a id="t5Yf3_ref-2" href="#t5Yf3_note-2">²</a> that handles quite a few use-cases of URLs (with or without http: or https:), @-name @-domain @-domain/path @-@-handles, hashtags(#), and footnotes(^).<br class="auto-break"/><br class="auto-break"/>Much of it is based on what I’ve seen work (or implemented) on sites and software, and some of it is based on logically extending how people are using text punctuation across various services.<br class="auto-break"/><br class="auto-break"/>It may be time for me to write-up an auto-link specification based on the algorithms I’ve come up with, implemented, and am using live on my site. All the algorithms work fully offline (none of them require querying a site for more info, whether well-known or otherwise), so they can be used in offline-first authoring/writing clients.<br class="auto-break"/><br class="auto-break"/>I have identified three logical chunks of auto-linking functionality, each of which has different constraints and potential needs for local to the linking context information (like hashtags need a default tagspace). Each would be a good section for a new specification. Each is used by this very post.<br class="auto-break"/><br class="auto-break"/>* URLs, @-s, and @-@-s<br class="auto-break"/>* # hashtags<br class="auto-break"/>* ^ footnotes<br class="auto-break"/><br class="auto-break"/>#<span class="p-category auto-tag">IndieWeb</span> #<span class="p-category auto-tag">autoLink</span> #<span class="p-category auto-tag">hashtag</span> #<span class="p-category auto-tag">hashtags</span> #<span class="p-category auto-tag">footnote</span> #<span class="p-category auto-tag">footnotes</span><br class="auto-break"/><br class="auto-break"/>Previously, previously, previously:<br class="auto-break"/><br class="auto-break"/>* <a class="auto-link" href="https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases">https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases</a><br class="auto-break"/>* <a class="auto-link" href="https://tantek.com/2023/100/t1/auto-linked-hashtags-federated">https://tantek.com/2023/100/t1/auto-linked-hashtags-federated</a><br class="auto-break"/>* <a class="auto-link" href="https://tantek.com/2023/043/t1/footnotes-unicode-links">https://tantek.com/2023/043/t1/footnotes-unicode-links</a><br class="auto-break"/>* <a class="auto-link" href="https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo">https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo</a><br class="auto-break"/><br class="auto-break"/><br class="auto-break"/>References:<br class="auto-break"/><br class="auto-break"/><a id="t5Yf3_note-1" href="#t5Yf3_ref-1">¹</a> <a class="auto-link" href="https://indieweb.org/autolink">https://indieweb.org/autolink</a><br class="auto-break"/><a id="t5Yf3_note-2" href="#t5Yf3_ref-2">²</a> <a class="auto-link" href="https://github.com/tantek/cassis/blob/main/cassis.js">https://github.com/tantek/cassis/blob/main/cassis.js</a><br class="auto-break"/><br class="auto-break"/><br class="auto-break"/>This is post 18 of #<span class="p-category auto-tag">100PostsOfIndieWeb</span>. #<span class="p-category auto-tag">100Posts</span><br class="auto-break"/><br class="auto-break"/>← <a class="auto-link" href="https://tantek.com/2024/238/t1/indiewebcamp-portland">https://tantek.com/2024/238/t1/indiewebcamp-portland</a><br class="auto-break"/>→ <a class="auto-link" href="https://tantek.com/2024/242/t1/indiewebcamp-portland">https://tantek.com/2024/242/t1/indiewebcamp-portland</a></div>
  101.    </content>
  102.    <object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
  103.  </entry>
  104.  <entry>
  105.    <updated>2024-08-25T10:18:00-07:00</updated>
  106.    <published>2024-08-25T10:18:00-07:00</published>
  107.    <link href="https://tantek.com/2024/238/t1/indiewebcamp-portland" rel="alternate" title="" type="text/html"/>
  108.    <id>https://tantek.com/2024/238/t1/indiewebcamp-portland</id>
  109.    <title type="xhtml">
  110.      <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"/>
  111.    </title>
  112.    <content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
  113.      <div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">All setup here at IndieWebCamp Portland!<br class="auto-break"/><br class="auto-break"/><a class="auto-link" href="https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k">https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k</a><br class="auto-break"/><br class="auto-break"/>Good crowd of participants from #<span class="p-category auto-tag">XOXO</span> #<span class="p-category auto-tag">XOXOConf</span> (<a class="auto-link" href="https://xoxofest.com">@xoxofest.com</a> <a class="auto-link" href="https://xoxo.zone/@xoxo">@xoxo@xoxo.zone</a> <a class="auto-link h-cassis-username" href="https://twitter.com/xoxo">@xoxo</a>) here to work on their personal website(s), domains, or other independent social media setups!<br class="auto-break"/><br class="auto-break"/>As encouraged by Andy Baio (<a class="auto-link" href="https://waxy.org">@waxy.org</a> <a class="auto-link" href="https://xoxo.zone/@andybaio">@andybaio@xoxo.zone</a> <a class="auto-link h-cassis-username" href="https://twitter.com/waxpancake">@waxpancake</a>)<br class="auto-break"/><br class="auto-break"/>“Every one of you should have a home on the web not controlled by a billionaire.”<br class="auto-break"/><br class="auto-break"/>If you’re in #<span class="p-category auto-tag">Portland</span> and want help, encouragement, or camaraderie in getting setup or doing more with your personal site, come on by! We’ll be having a mix of discussion sessions and create/hack sessions. <br class="auto-break"/><br class="auto-break"/>Personal site and hack demos at 16:00 PDT!<br class="auto-break"/><br class="auto-break"/>#<span class="p-category auto-tag">indieweb</span> #<span class="p-category auto-tag">fediverse</span> #<span class="p-category auto-tag">ActivityPub</span> #<span class="p-category auto-tag">decentralized</span> #<span class="p-category auto-tag">socialMedia</span><br class="auto-break"/><br class="auto-break"/>This is post 17 of #<span class="p-category auto-tag">100PostsOfIndieWeb</span>. #<span class="p-category auto-tag">100Posts</span><br class="auto-break"/><br class="auto-break"/>← <a class="auto-link" href="https://tantek.com/2024/237/t1/people-over-protocols-platforms">https://tantek.com/2024/237/t1/people-over-protocols-platforms</a><br class="auto-break"/>→ <a class="auto-link" href="https://tantek.com/2024/238/t3/indiewebcamp-auto-linking">https://tantek.com/2024/238/t3/indiewebcamp-auto-linking</a></div>
  114.    </content>
  115.    <object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
  116.  </entry>
  117.  <entry>
  118.    <updated>2024-08-24T16:56:00-07:00</updated>
  119.    <published>2024-08-24T16:56:00-07:00</published>
  120.    <link href="https://tantek.com/2024/237/t1/people-over-protocols-platforms" rel="alternate" title="" type="text/html"/>
  121.    <id>https://tantek.com/2024/237/t1/people-over-protocols-platforms</id>
  122.    <title type="xhtml">
  123.      <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"/>
  124.    </title>
  125.    <content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
  126.      <div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">People over protocols over platforms.<br class="auto-break"/><br class="auto-break"/><br class="auto-break"/>inspired by today’s #<span class="p-category auto-tag">indieweb</span> #<span class="p-category auto-tag">fediverse</span> #<span class="p-category auto-tag">ActivityPub</span> #<span class="p-category auto-tag">decentralized</span> #<span class="p-category auto-tag">socialMedia</span> lunch meetup at #<span class="p-category auto-tag">XOXO</span> #<span class="p-category auto-tag">XOXOConf</span> (<a class="auto-link" href="https://xoxo.zone/@xoxo">@xoxo@xoxo.zone</a>)<br class="auto-break"/><br class="auto-break"/>This is post 16 of #<span class="p-category auto-tag">100PostsOfIndieWeb</span>. #<span class="p-category auto-tag">100Posts</span><br class="auto-break"/><br class="auto-break"/>← <a class="auto-link" href="https://tantek.com/2024/173/t1/years-posse-microformats-adoption">https://tantek.com/2024/173/t1/years-posse-microformats-adoption</a><br class="auto-break"/>→ <a class="auto-link" href="https://tantek.com/2024/238/t1/indiewebcamp-portland">https://tantek.com/2024/238/t1/indiewebcamp-portland</a></div>
  127.    </content>
  128.    <object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
  129.  </entry>
  130.  <entry>
  131.    <updated>2024-08-04T19:09:00-07:00</updated>
  132.    <published>2024-08-04T19:09:00-07:00</published>
  133.    <link href="https://tantek.com/2024/217/t1/skyline-half-marathon-trail-race" rel="alternate" title="" type="text/html"/>
  134.    <id>https://tantek.com/2024/217/t1/skyline-half-marathon-trail-race</id>
  135.    <title type="xhtml">
  136.      <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"/>
  137.    </title>
  138.    <content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
  139.      <div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">finished the Skyline 21k (half marathon) trail race in 3:39:48! (official bib time)<br class="auto-break"/><br class="auto-break"/>Went out with the goal to have fun and try for sub-4, finished with smiles and a sub 3:40. <br class="auto-break"/><br class="auto-break"/>Superbly run event as always by <a class="auto-link" href="https://ScenaPerformance.com">@ScenaPerformance.com</a> (<a class="auto-link" href="https://instagram.com/scenaperformance">@instagram.com/scenaperformance</a>), race director Adam Ray, and all the great volunteers.<br class="auto-break"/><br class="auto-break"/>So many things went well. Race write-up to follow.<br class="auto-break"/><br class="auto-break"/>Previously:<br class="auto-break"/>* 2023: DNS Skyline 50k because of a bad fever from a blood bacteria infection caught in Wakefield MA (that’s whole other story, never going back there)<br class="auto-break"/>* 2022: 50k race PR at Skyline: <a class="auto-link" href="https://tantek.com/2022/289/t1/hot-skyline50k-ultra-finish">https://tantek.com/2022/289/t1/hot-skyline50k-ultra-finish</a><br class="auto-break"/><br class="auto-break"/>#<span class="p-category auto-tag">Skyline</span> #<span class="p-category auto-tag">21k</span> #<span class="p-category auto-tag">halfMarathon</span> #<span class="p-category auto-tag">trailRace</span> #<span class="p-category auto-tag">trailRun</span></div>
  140.    </content>
  141.    <object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
  142.  </entry>
  143.  <entry>
  144.    <updated>2024-08-03T22:29:00-07:00</updated>
  145.    <published>2024-08-03T22:29:00-07:00</published>
  146.    <link href="https://tantek.com/2024/216/t1/socialcg-telcon" rel="alternate" title="" type="text/html"/>
  147.    <id>https://tantek.com/2024/216/t1/socialcg-telcon</id>
  148.    <title type="xhtml">
  149.      <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"/>
  150.    </title>
  151.    <content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
  152.      <div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">Good W3C SocialCG telcon yesterday morning.<br class="auto-break"/><br class="auto-break"/>Minutes: <a class="auto-link" href="https://www.w3.org/wiki/SocialCG/2024-08-02">https://www.w3.org/wiki/SocialCG/2024-08-02</a><br class="auto-break"/><br class="auto-break"/>Appreciate working with <a class="auto-link" href="https://cosocial.ca/@evan">@evan@cosocial.ca</a> <a class="auto-link" href="https://mastodon.mit.edu/@dmitriz">@dmitriz@mastodon.mit.edu</a> <a class="auto-link" href="https://mastodon.social/@TallTed">@TallTed@mastodon.social</a> <a class="auto-link" href="https://snarfed.org">@snarfed.org</a> Lisa a <a class="auto-link" href="https://fosstodon.org/@AaronNGray">@AaronNGray@fosstodon.org</a> <a class="auto-link" href="https://mastodon.social/@bobwyman">@bobwyman@mastodon.social</a> <a class="auto-link" href="https://mastodon.social/@by_caballero">@by_caballero@mastodon.social</a> <a class="auto-link" href="https://j12t.social/@j12t">@j12t@j12t.social</a> <a class="auto-link" href="https://social.technoetic.com/@steve">@steve@social.technoetic.com</a> <a class="auto-link" href="https://hachyderm.io/@thisismissem">@thisismissem@hachyderm.io</a><br class="auto-break"/><br class="auto-break"/>#<span class="p-category auto-tag">W3C</span> #<span class="p-category auto-tag">SocialCG</span> #<span class="p-category auto-tag">20240802</span> #<span class="p-category auto-tag">2024_215</span> #<span class="p-category auto-tag">ActivityPub</span> #<span class="p-category auto-tag">ActivityStreams</span> #<span class="p-category auto-tag">relAuthor</span></div>
  153.    </content>
  154.    <object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
  155.  </entry>
  156. </feed>
  157.  

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:

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

Home · About · News · Docs · Terms

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