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-11-09T05:31:00-08:00</updated>
  13.  <entry>
  14.    <updated>2024-11-09T05:31:00-08:00</updated>
  15.    <published>2024-11-09T05:31:00-08:00</published>
  16.    <link href="https://tantek.com/2024/314/t1/indiewebcamp-berlin-2024-day-1" rel="alternate" title="" type="text/html"/>
  17.    <id>https://tantek.com/2024/314/t1/indiewebcamp-berlin-2024-day-1</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">Day 1 of #<span class="p-category auto-tag">IndieWebCamp</span> #<span class="p-category auto-tag">Berlin</span> 2024<a id="t5Zw1_ref-1" href="#t5Zw1_note-1">¹</a> was very well attended!<br class="auto-break"/>* 20 participants, more than 3x the previous one in 2022, and second highest (2019 had 22).<br class="auto-break"/>* 18 introduced themselves<a id="t5Zw1_ref-2" href="#t5Zw1_note-2">²</a> and their personal sites or aspirations for one<br class="auto-break"/><br class="auto-break"/>Collectively we proposed and facilitated 11 breakout sessions<a id="t5Zw1_ref-3" href="#t5Zw1_note-3">³</a> on many timely #<span class="p-category auto-tag">indieweb</span> topics covering #<span class="p-category auto-tag">syndication</span>, #<span class="p-category auto-tag">inclusion</span>, #<span class="p-category auto-tag">longevity</span>, #<span class="p-category auto-tag">federation</span> / #<span class="p-category auto-tag">fediverse</span>, how to best use #<span class="p-category auto-tag">Mastodon</span> with your personal site, #<span class="p-category auto-tag">privacy</span> and #<span class="p-category auto-tag">security</span> concerns of being online, #<span class="p-category auto-tag">writing</span>, how can we design better user interfaces for text authoring, and personalized reading #<span class="p-category auto-tag">algorithms</span> for staying connected with friends.<br class="auto-break"/><br class="auto-break"/>Session titles (and hashtags)<br class="auto-break"/>* How to #<span class="p-category auto-tag">POSSE</span><br class="auto-break"/>* How to make the web queerer / stranger. #<span class="p-category auto-tag">queer</span><br class="auto-break"/>* Online presence after our #<span class="p-category auto-tag">death</span><br class="auto-break"/>* Threat modeling #<span class="p-category auto-tag">threatmodeling</span><br class="auto-break"/>* Non-technical collaboration on the internet. #<span class="p-category auto-tag">collab</span><br class="auto-break"/>* Locations and #<span class="p-category auto-tag">places</span> check-in<br class="auto-break"/>* Writing with images. #<span class="p-category auto-tag">imagewriting</span><br class="auto-break"/>* Text authoring UX. #<span class="p-category auto-tag">textUX</span><br class="auto-break"/>* #<span class="p-category auto-tag">SSR</span>, organizing CSS/JS<br class="auto-break"/>* Website design without being a designer. #<span class="p-category auto-tag">designfordummies</span><br class="auto-break"/>* Timeline algorithms. #<span class="p-category auto-tag">timelines</span><br class="auto-break"/><br class="auto-break"/>Etherpad notes from sessions have been archived to the wiki, with session recordings to follow!<br class="auto-break"/><br class="auto-break"/>Day 2 also had 20 in-person participants, the highest IndieWebCamp Berlin day 2 attendance ever! Most everyone from day 1 came back to hack, and three new people showed up. We also had several remote participants.<br class="auto-break"/><br class="auto-break"/><br class="auto-break"/>References<br class="auto-break"/>  <br class="auto-break"/><a id="t5Zw1_note-1" href="#t5Zw1_ref-1">¹</a> <a class="auto-link" href="https://indieweb.org/2024">https://indieweb.org/2024</a><br class="auto-break"/><a id="t5Zw1_note-2" href="#t5Zw1_ref-2">²</a> <a class="auto-link" href="https://indieweb.org/2024/Berlin/Intros">https://indieweb.org/2024/Berlin/Intros</a><br class="auto-break"/><a id="t5Zw1_note-3" href="#t5Zw1_ref-3">³</a> <a class="auto-link" href="https://indieweb.org/2024/Berlin/Schedule#Saturday">https://indieweb.org/2024/Berlin/Schedule#Saturday</a><br class="auto-break"/><br class="auto-break"/><br class="auto-break"/>This is post 28 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/306/t1/simple-embeds">https://tantek.com/2024/306/t1/simple-embeds</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-11-08T04:04:00-08:00</updated>
  28.    <published>2024-11-08T04:04:00-08:00</published>
  29.    <link href="https://tantek.com/2024/313/t1/reflecting-listening-thoughts" rel="alternate" title="" type="text/html"/>
  30.    <id>https://tantek.com/2024/313/t1/reflecting-listening-thoughts</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">Still reflecting and listening to how different folks are reacting after the US #<span class="p-category auto-tag">election</span> results. A few immediate thoughts:<br class="auto-break"/>* take care of yourselves, physically, emotionally, etc.<br class="auto-break"/>* lean into mutual care, check on those close to you<br class="auto-break"/>* (re)connect with community and especially those that reach out to you<br class="auto-break"/>* (re)consider privacy implications of your actions, IRL &amp; online, spending habits <br class="auto-break"/><br class="auto-break"/>Here in #<span class="p-category auto-tag">SanFrancisco</span> and #<span class="p-category auto-tag">California</span> we are seeing mostly positive local results<a id="t5Zv1_ref-1" href="#t5Zv1_note-1">¹</a> including a new mayor (who I happened to rank first for many reasons).<br class="auto-break"/><br class="auto-break"/>Lots to think about and do in the next couple of months.<br class="auto-break"/><br class="auto-break"/><a id="t5Zv1_note-1" href="#t5Zv1_ref-1">¹</a> <a class="auto-link" href="https://sfstandard.com/2024/11/05/san-francisco-election-results-november-2024/">https://sfstandard.com/2024/11/05/san-francisco-election-results-november-2024/</a></div>
  36.    </content>
  37.    <object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
  38.  </entry>
  39.  <entry>
  40.    <updated>2024-11-01T14:33:00-07:00</updated>
  41.    <published>2024-11-01T14:33:00-07:00</published>
  42.    <link href="https://tantek.com/2024/306/t1/simple-embeds" rel="alternate" title="" type="text/html"/>
  43.    <id>https://tantek.com/2024/306/t1/simple-embeds</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">Last week at a #<span class="p-category auto-tag">HomebrewWebsiteClub</span> session<a id="t5Zo1_ref-1" href="#t5Zo1_note-1">¹</a> I pointed out that I was working on implementing a “simple” way to support embeds of my notes, that is, make my short notes embeddable, like how people embed tweets or toots.<br class="auto-break"/><br class="auto-break"/>I noted that to keep it as simple as possible while being flexible to implementation changes, I planned to implement three things:<br class="auto-break"/><br class="auto-break"/>1. A separate “embed” version of my post permalinks, with just the entry information (no header, nav, search, sidebar, footer etc.), embeddable via copy/paste or an iframe.<br class="auto-break"/>2. A way to “Follow Your Nose” discover that separate embed version<br class="auto-break"/>3. A way to discover the original post from the embedded version<br class="auto-break"/><br class="auto-break"/>For (1) a minimal h-entry, with perhaps a little bit of inline CSS would suffice.<br class="auto-break"/><br class="auto-break"/>For (2) I proposed using “rel=embed” which I’ve subsequently written up briefly<a id="t5Zo1_ref-2" href="#t5Zo1_note-2">²</a>.<br class="auto-break"/><br class="auto-break"/>For (3) The obvious existing answer is rel=canonical link from the embed version to the canonical post permalink.<br class="auto-break"/><br class="auto-break"/><br class="auto-break"/>Soon thereafter, several folks in the #<span class="p-category auto-tag">IndieWeb</span> community went ahead and implemented such embeds for their own sites, and even the <a class="auto-link" href="https://libre.fm/">https://libre.fm/</a> open scrobbling service!<br class="auto-break"/><br class="auto-break"/><a class="auto-link" href="https://indieweb.org/embed#IndieWeb_Examples">https://indieweb.org/embed#IndieWeb_Examples</a><br class="auto-break"/><br class="auto-break"/>I have yet to implement it myself, and that’s fine. This is one of the things I appreciate about the community, we can share our plans and ideas for improving things on our own sites, and if someone else does it first, that's great! We celebrate it and explore the solution space together.<br class="auto-break"/><br class="auto-break"/>Got other ideas for simple embeds? Want to implement them on your own site?<br class="auto-break"/><br class="auto-break"/>Join us in the #<span class="p-category auto-tag">indiewebdev</span> chat: <a class="auto-link" href="https://chat.indieweb.org/dev">https://chat.indieweb.org/dev</a><br class="auto-break"/><br class="auto-break"/><br class="auto-break"/>UPDATE: What about oEmbed? tl;dr: oEmbed requires JS and backend code, more work and unsuitable for embeds from static site hosting (like GitHub pages). <br class="auto-break"/><br class="auto-break"/>A simple HTML method is accessible to many more independent publishers and easier to implement. More: <a class="auto-link" href="https://tantek.com/2024/306/t2">https://tantek.com/2024/306/t2</a><br class="auto-break"/><br class="auto-break"/><br class="auto-break"/>Glossary<br class="auto-break"/><br class="auto-break"/>embed<br class="auto-break"/>  <a class="auto-link" href="https://indieweb.org/embed">https://indieweb.org/embed</a><br class="auto-break"/>Follow Your Nose<br class="auto-break"/>  <a class="auto-link" href="https://indieweb.org/follow_your_nose">https://indieweb.org/follow_your_nose</a><br class="auto-break"/>h-entry<br class="auto-break"/>  <a class="auto-link" href="https://microformats.org/wiki/h-entry">https://microformats.org/wiki/h-entry</a><br class="auto-break"/>oEmbed<br class="auto-break"/>  <a class="auto-link" href="https://indieweb.org/oEmbed">https://indieweb.org/oEmbed</a><br class="auto-break"/>rel-canonical<br class="auto-break"/>  <a class="auto-link" href="https://indieweb.org/rel-canonical">https://indieweb.org/rel-canonical</a><br class="auto-break"/>static site hosting<br class="auto-break"/>  <a class="auto-link" href="https://indieweb.org/static_web_hosting">https://indieweb.org/static_web_hosting</a><br class="auto-break"/><br class="auto-break"/><br class="auto-break"/>References<br class="auto-break"/>  <br class="auto-break"/><a id="t5Zo1_note-1" href="#t5Zo1_ref-1">¹</a> <a class="auto-link" href="https://indieweb.org/events/2024-10-23-hwc-europe#embedding">https://indieweb.org/events/2024-10-23-hwc-europe#embedding</a><br class="auto-break"/><a id="t5Zo1_note-2" href="#t5Zo1_ref-2">²</a> <a class="auto-link" href="https://indieweb.org/rel-embed">https://indieweb.org/rel-embed</a><br class="auto-break"/><br class="auto-break"/><br class="auto-break"/>This is post 27 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/287/t1/fediverse-unfollow-bridgyfed-bug">https://tantek.com/2024/287/t1/fediverse-unfollow-bridgyfed-bug</a><br class="auto-break"/>→ <a class="auto-link" href="https://tantek.com/2024/314/t1/indiewebcamp-berlin-2024-day-1">https://tantek.com/2024/314/t1/indiewebcamp-berlin-2024-day-1</a></div>
  49.    </content>
  50.    <object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
  51.  </entry>
  52.  <entry>
  53.    <updated>2024-10-31T22:34:00-07:00</updated>
  54.    <published>2024-10-31T22:34:00-07:00</published>
  55.    <link href="https://tantek.com/2024/305/t1/beyond-tellerand-berlin" rel="alternate" title="" type="text/html"/>
  56.    <id>https://tantek.com/2024/305/t1/beyond-tellerand-berlin</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">European friends!<br class="auto-break"/><br class="auto-break"/>🗓 I am going to Beyond Tellerand (<a class="auto-link" href="https://mastodon.social/@btconf">@btconf@mastodon.social</a>) Berlin next week 7-8 November and you should too!<br class="auto-break"/><br class="auto-break"/>BTconf is the best independent web design, development, and inspiration conference in Europe.<br class="auto-break"/><br class="auto-break"/>Everything from the speakers to the talks to the side events are a labor of love by <a class="auto-link" href="https://MarcThiele.com">@MarcThiele.com</a> (<a class="auto-link" href="https://mastodon.social/@marcthiele">@marcthiele@mastodon.social</a>) and his crew, and it shows in the #<span class="p-category auto-tag">btconf</span> community he has gathered over the years.<br class="auto-break"/><br class="auto-break"/>If you’re in #<span class="p-category auto-tag">Berlin</span>, or can hop on a train and join us, you should.<br class="auto-break"/><br class="auto-break"/>🎟 Grab a ticket: <a class="auto-link" href="https://btco.nf/t">https://btco.nf/t</a><br class="auto-break"/><br class="auto-break"/>And while you’re there, consider joining us at #<span class="p-category auto-tag">IndieWebCamp</span> Berlin right afterwards on 9-10 November (complimentary camp tickets at the same link), for #<span class="p-category auto-tag">barcamp</span> style discussions sessions and an #<span class="p-category auto-tag">indieweb</span> Create Day, writing, styling, designing, coding, hacking on our personal sites for a better web for ourselves and everyone else.</div>
  62.    </content>
  63.    <object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
  64.  </entry>
  65.  <entry>
  66.    <updated>2024-10-13T16:58:00-07:00</updated>
  67.    <published>2024-10-13T16:58:00-07:00</published>
  68.    <link href="https://tantek.com/2024/287/t3/bing-use-case-calendar-month" rel="alternate" title="" type="text/html"/>
  69.    <id>https://tantek.com/2024/287/t3/bing-use-case-calendar-month</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">Bing use-case! AKA One Weird Trick Time And Date Sites Hate<br class="auto-break"/><br class="auto-break"/>In my prior post<a id="t5ZV3_ref-1" href="#t5ZV3_note-1">¹</a> I noted that I use 'b' as a Search Shortcut for #<span class="p-category auto-tag">Bing</span>. Here is why: <br class="auto-break"/><br class="auto-break"/>* quickly view a Gregorian calendar month display, with readable days, days of the week, and weekends &amp; holidays highlighted.<br class="auto-break"/><br class="auto-break"/>E.g. I type this into my Firefox address bar:<br class="auto-break"/><br class="auto-break"/>b dec 2024<br class="auto-break"/><br class="auto-break"/>then press return and immediately see:<br class="auto-break"/><br class="auto-break"/><a class="auto-link figure" href="https://www.bing.com/search?q=dec+2024"><img class="auto-embed" alt="Screenshot of a Firefox private browsing window searching Bing for dec 2024 and showing a big text display of the month of December 2024 with headings for the days of the week and weekends and holidays highlighted." src="https://indieweb.org/images/8/81/2024-10-13-bing-dec-2024.png"/></a><br class="auto-break"/>Only Microsoft Bing search supports this. <br class="auto-break"/><br class="auto-break"/>On other search engines (Duckduckgo, Google, Yahoo) all you get are links to random date time sites littered with ads, or blurry images of calendar months where the day numbers and holidays are too small to read.<br class="auto-break"/><br class="auto-break"/>This is something I have informally complained about to friends for years, that if you use Google Search for unit conversions, simple arithmetic, and even names of holidays, you get a nice large font “featured snippet” display of exactly your answer. But not something as simple as a month and year or even month with the implication that you want to see the current or next instance of that month. <br class="auto-break"/><br class="auto-break"/>How hard can that be to build? 12 names of months. 12 more 3-letter abbreviations. Multiplied by however number of languages supported. An intern could code that in under an hour. Someone has likely already written a regular expression for detecting this. (Aside: I tried year first, e.g. 2024 Dec, and hilariously enough that did not work to show the nice month display. So I suspect there is a minimal regular expression under the covers of this Bing feature.)<br class="auto-break"/><br class="auto-break"/>From having tried search engines for years, I was pretty convinced no one supported this.<br class="auto-break"/><br class="auto-break"/>Then on a whim I tried this in Bing recently (maybe I hadn’t before?) and to my pleasant surprise it worked.<br class="auto-break"/><br class="auto-break"/>There you have it, a use-case for Bing that only works in Bing, and reason enough to add a 'b' Search Shortcut in Firefox for Bing.<br class="auto-break"/><br class="auto-break"/>#<span class="p-category auto-tag">search</span> #<span class="p-category auto-tag">webSearch</span> #<span class="p-category auto-tag">SearchShortcut</span> #<span class="p-category auto-tag">Microsoft</span> #<span class="p-category auto-tag">BingTip</span> #<span class="p-category auto-tag">searchTip</span> #<span class="p-category auto-tag">calendar</span> #<span class="p-category auto-tag">month</span><br class="auto-break"/><br class="auto-break"/><a id="t5ZV3_note-1" href="#t5ZV3_ref-1">¹</a> <a class="auto-link" href="https://tantek.com/2024/287/t2/setup-search-shortcuts-firefox">https://tantek.com/2024/287/t2/setup-search-shortcuts-firefox</a></div>
  75.    </content>
  76.    <object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
  77.  </entry>
  78.  <entry>
  79.    <updated>2024-10-13T16:08:00-07:00</updated>
  80.    <published>2024-10-13T16:08:00-07:00</published>
  81.    <link href="https://tantek.com/2024/287/t2/setup-search-shortcuts-firefox" rel="alternate" title="" type="text/html"/>
  82.    <id>https://tantek.com/2024/287/t2/setup-search-shortcuts-firefox</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">You should setup Search Shortcuts in #<span class="p-category auto-tag">Firefox</span>, they have sped up my web browsing experience considerably.<br class="auto-break"/><br class="auto-break"/>James (<a class="auto-link" href="https://jamesg.blog">@jamesg.blog</a>) wrote up a great summary of how to do so and his experience:<br class="auto-break"/>* <a class="auto-link" href="https://jamesg.blog/2024/10/13/search-engine-shortcuts-firefox/">https://jamesg.blog/2024/10/13/search-engine-shortcuts-firefox/</a><br class="auto-break"/><br class="auto-break"/>I use DuckDuckGo as my default search engine, so here are the Search Shortcuts I have setup when I want to explicitly search/lookup something elsewhere, roughly ordered by my perceived frequency of use:<br class="auto-break"/><br class="auto-break"/>i - IndieWeb - <a class="auto-link" href="https://indieweb.org/">https://indieweb.org/</a><br class="auto-break"/>w - Wikipedia - <a class="auto-link" href="https://en.wikipedia.org/wiki/">https://en.wikipedia.org/wiki/</a><br class="auto-break"/>g - Google - <a class="auto-link" href="https://google.com/">https://google.com/</a><br class="auto-break"/>d - MDN Web Docs - <a class="auto-link" href="https://developer.mozilla.org/">https://developer.mozilla.org/</a><br class="auto-break"/>m - Google Maps - <a class="auto-link" href="https://maps.google.com/">https://maps.google.com/</a><br class="auto-break"/>b - Bing - <a class="auto-link" href="https://bing.com/">https://bing.com/</a><br class="auto-break"/>a - Amazon - <a class="auto-link" href="https://amazon.com/">https://amazon.com/</a><br class="auto-break"/>x - Twitter - <a class="auto-link" href="https://twitter.com/search">https://twitter.com/search</a><br class="auto-break"/><br class="auto-break"/>If you don’t see one of these search engines in your Firefox Settings: Search Shortcuts, you can visit its URL above and then follow the instructions in James’s blog post to add it to your browser’s list of search engines. Once added there, it will show up in the Search Shortcuts table and you can double-click it and add a one-letter (or more) shortcut as you wish!<br class="auto-break"/><br class="auto-break"/>What Search Shortcuts have you setup in your browser?<br class="auto-break"/><br class="auto-break"/>#<span class="p-category auto-tag">search</span> #<span class="p-category auto-tag">OpenSearch</span> #<span class="p-category auto-tag">webSearch</span> #<span class="p-category auto-tag">SearchShortcuts</span> #<span class="p-category auto-tag">browserTip</span> #<span class="p-category auto-tag">FirefoxTip</span> #<span class="p-category auto-tag">searchTip</span></div>
  88.    </content>
  89.    <object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
  90.  </entry>
  91.  <entry>
  92.    <updated>2024-10-13T13:37:00-07:00</updated>
  93.    <published>2024-10-13T13:37:00-07:00</published>
  94.    <link href="https://tantek.com/2024/287/t1/fediverse-unfollow-bridgyfed-bug" rel="alternate" title="" type="text/html"/>
  95.    <id>https://tantek.com/2024/287/t1/fediverse-unfollow-bridgyfed-bug</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">No I did not block you on the #<span class="p-category auto-tag">fediverse</span> / #<span class="p-category auto-tag">Mastodon</span> / #<span class="p-category auto-tag">Misskey</span> etc.<br class="auto-break"/><br class="auto-break"/>If you were following me <a class="auto-link" href="https://tantek.com">@tantek.com</a> on your client/server/instance of choice but noticed you were no longer doing so, that was due to a recent software bug in my fediverse provider which accidentally caused everyone’s #<span class="p-category auto-tag">ActivityPub</span> servers to unfollow me (bug details below).<br class="auto-break"/><br class="auto-break"/>No it’s absolutely not your fault, you did nothing wrong.<br class="auto-break"/><br class="auto-break"/>We need a variant of Hanlon’s Razor<a id="t5ZV1_ref-1" href="#t5ZV1_note-1">¹</a> like:<br class="auto-break"/><br class="auto-break"/>“Never attribute to malice that which is adequately explained by a software bug.”<br class="auto-break"/><br class="auto-break"/>Take another look at my posts if you want (directly on <a class="auto-link" href="https://tantek.com">@tantek.com</a> or try searching for that on your instance) and if you like what you see or find them otherwise informative and useful, feel free to refollow. If not, no worries!<br class="auto-break"/><br class="auto-break"/>Also no worries if you ever unfollow/refollow for any reason. I mean that. <br class="auto-break"/><br class="auto-break"/>I always assume people know best how to manage their online reader/reading experiences, everyone’s priorities and likes/dislikes change over time, and encourage everyone to make choices that are best for their mental health and overall joy online.<br class="auto-break"/><br class="auto-break"/>Bug details:<br class="auto-break"/><br class="auto-break"/>This was due to a #<span class="p-category auto-tag">BridgyFed</span> bug<a id="t5ZV1_ref-2" href="#t5ZV1_note-2">²</a> that deleted my profile (“ActivityPub actor”) from (nearly?) all instances, making everyone’s accounts automatically unfollow me, as well as remove any of my posts from your likes and reposts (boosts) collections. It also removed my posts from any of your replies to my posts, leaving your replies dangling without reply-contexts. Apologies!<br class="auto-break"/><br class="auto-break"/>The bug was introduced accidentally as part of another fix about a month ago<a id="t5ZV1_ref-3" href="#t5ZV1_note-3">³</a>, and was triggered within the following week<a id="t5ZV1_ref-4" href="#t5ZV1_note-4">⁴</a>.<br class="auto-break"/><br class="auto-break"/>Anyone following me before ~2024-09-22 was no longer following me. A few folks have noticed and refollowed. Any likes or reposts of my posts before that date were also undone (removed).<br class="auto-break"/><br class="auto-break"/>Ryan (<a class="auto-link" href="https://snarfed.org">@snarfed.org</a>) has been really good about giving folks a heads-up, and apologizing, and quickly doing what he can to fix things.<br class="auto-break"/><br class="auto-break"/>Bugs happen, yes even in production code, so please do not post/send any hate.<br class="auto-break"/><br class="auto-break"/>I’d rather be one of the folks helping with improving BridgyFed, and temporary setbacks like this are part of being an early / eager #<span class="p-category auto-tag">IndieWeb</span> adopter.<br class="auto-break"/><br class="auto-break"/>This bug has also revealed some potential weaknesses in other ActivityPub implementations. E.g. deleting an “actor” should be undoable, and undoing a delete should reconnect everything, from follows to likes &amp; reposts collections, to reply-contexts. Perhaps the ActivityPub specification could be updated with such guidance (if it hasn’t been already, I need to double-check).<br class="auto-break"/><br class="auto-break"/>To be clear, I’m still a big supporter of #<span class="p-category auto-tag">BridgyFed</span>, #<span class="p-category auto-tag">ActivityPub</span>, #<span class="p-category auto-tag">Webmention</span>, and everyone who chooses to implement these and other #<span class="p-category auto-tag">IndieWeb</span> related and adjacent protocols as best fits their products and services. <br class="auto-break"/><br class="auto-break"/>All of these are a part of our broader open #<span class="p-category auto-tag">socialWeb</span>, and making all these #<span class="p-category auto-tag">openStandards</span> work well together (including handling edge-cases and mistakes!) is essential for providing #<span class="p-category auto-tag">socialMedia</span> alternatives that put users first.<br class="auto-break"/><br class="auto-break"/>References:<br class="auto-break"/><br class="auto-break"/><a id="t5ZV1_note-1" href="#t5ZV1_ref-1">¹</a> <a class="auto-link" href="https://en.wikipedia.org/wiki/Hanlon%27s_razor">https://en.wikipedia.org/wiki/Hanlon%27s_razor</a><br class="auto-break"/><a id="t5ZV1_note-2" href="#t5ZV1_ref-2">²</a> <a class="auto-link" href="https://github.com/snarfed/bridgy-fed/issues/1379">https://github.com/snarfed/bridgy-fed/issues/1379</a><br class="auto-break"/><a id="t5ZV1_note-3" href="#t5ZV1_ref-3">³</a> <a class="auto-link" href="https://github.com/snarfed/bridgy-fed/commit/4df76d0db7b87cabbd714039546c05b3221169be">https://github.com/snarfed/bridgy-fed/commit/4df76d0db7b87cabbd714039546c05b3221169be</a><br class="auto-break"/><a id="t5ZV1_note-4" href="#t5ZV1_ref-4">⁴</a> <a class="auto-link" href="https://chat.indieweb.org/dev/2024-09-22#t1727028174623700">https://chat.indieweb.org/dev/2024-09-22#t1727028174623700</a><br class="auto-break"/><br class="auto-break"/>This is post 26 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/285/t1/io-domain-suggested-steps">https://tantek.com/2024/285/t1/io-domain-suggested-steps</a><br class="auto-break"/>→ <a class="auto-link" href="https://tantek.com/2024/306/t1/simple-embeds">https://tantek.com/2024/306/t1/simple-embeds</a></div>
  101.    </content>
  102.    <object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
  103.  </entry>
  104.  <entry>
  105.    <updated>2024-10-11T14:22:00-07:00</updated>
  106.    <published>2024-10-11T14:22:00-07:00</published>
  107.    <link href="https://tantek.com/2024/285/t1/io-domain-suggested-steps" rel="alternate" title="" type="text/html"/>
  108.    <id>https://tantek.com/2024/285/t1/io-domain-suggested-steps</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">⚠️ .io domain<a id="t5ZT1_ref-1" href="#t5ZT1_note-1">¹</a> likely being phased-out<a id="t5ZT1_ref-2" href="#t5ZT1_note-2">²</a> — seven suggested steps<br class="auto-break"/><br class="auto-break"/>Good article in The Verge summarizing recent .io related events, see that for more context if this is news to you:<br class="auto-break"/>* <a class="auto-link" href="https://www.theverge.com/2024/10/8/24265441/uk-treaty-end-io-domain-chagos-islands">https://www.theverge.com/2024/10/8/24265441/uk-treaty-end-io-domain-chagos-islands</a><br class="auto-break"/><br class="auto-break"/>It looks likely .io (and .io domains) will go away in the next few years (as .cs and .yu did<a id="t5ZT1_ref-3" href="#t5ZT1_note-3">³</a>), so here are my suggested steps to take depending on your usage of .io domains:<br class="auto-break"/><br class="auto-break"/>1. Avoid buying new .io domains (or making plans with existing ones; sell if you can)<br class="auto-break"/>2. If you currently run a .io service<a id="t5ZT1_ref-4" href="#t5ZT1_note-4">⁴</a> (for a company or community), make and publicize a transition plan (like a new domain, redirection, orderly shutdown plan for redirects)<br class="auto-break"/>3. If you have a personal site on a .io domain<a id="t5ZT1_ref-5" href="#t5ZT1_note-5">⁵</a> or subdomain, make your own transition plan, and perhaps post about how others should link to your posts<br class="auto-break"/>4. If you are using someone else’s .io domain to publish (like #<span class="p-category auto-tag">GitHubPages</span><a id="t5ZT1_ref-6" href="#t5ZT1_note-6">⁶</a>), make a transition plan to publish elsewhere and leave a forwarding note and link behind<br class="auto-break"/>5. If you use a .io domain as your Web sign-in login on any sites, switch them to another non-io personal domain<br class="auto-break"/>6. Similarly if your site accepts #<span class="p-category auto-tag">WebSignIn</span> logins (via #<span class="p-category auto-tag">IndieAuth</span>, #<span class="p-category auto-tag">RelMeAuth</span>, or even #<span class="p-category auto-tag">OpenID</span>), consider discouraging any new sign-ups from .io domains, and warning any existing users with .io domains to switch per # 5<br class="auto-break"/>7. If you have posts (or a whole #<span class="p-category auto-tag">indieweb</span> site) with links to .io sites or pages (like those in 2-4 above), make a plan for editing those links to point to an alternative or an archival copy (like on the Internet Archive) <br class="auto-break"/><br class="auto-break"/>And of course, post about your #<span class="p-category auto-tag">dotIO</span> plans.<br class="auto-break"/><br class="auto-break"/>Glossary<br class="auto-break"/><br class="auto-break"/>Domain<br class="auto-break"/> <a class="auto-link" href="https://indieweb.org/domain">https://indieweb.org/domain</a><br class="auto-break"/>IndieAuth<br class="auto-break"/> <a class="auto-link" href="https://indieweb.org/IndieAuth">https://indieweb.org/IndieAuth</a><br class="auto-break"/>Internet Archive<br class="auto-break"/> <a class="auto-link" href="https://web.archive.org/">https://web.archive.org/</a><br class="auto-break"/>OpenID<br class="auto-break"/> <a class="auto-link" href="https://indieweb.org/OpenID">https://indieweb.org/OpenID</a><br class="auto-break"/>Redirect <br class="auto-break"/> <a class="auto-link" href="https://indieweb.org/redirect">https://indieweb.org/redirect</a><br class="auto-break"/>RelMeAuth<br class="auto-break"/> <a class="auto-link" href="https://indieweb.org/RelMeAuth">https://indieweb.org/RelMeAuth</a><br class="auto-break"/>Web sign-in<br class="auto-break"/> <a class="auto-link" href="https://indieweb.org/Web_sign-in">https://indieweb.org/Web_sign-in</a><br class="auto-break"/><br class="auto-break"/><br class="auto-break"/>References: <br class="auto-break"/><br class="auto-break"/><a id="t5ZT1_note-1" href="#t5ZT1_ref-1">¹</a> <a class="auto-link" href="https://indieweb.org/.io">https://indieweb.org/.io</a><br class="auto-break"/><a id="t5ZT1_note-2" href="#t5ZT1_ref-2">²</a> <a class="auto-link" href="https://en.wikipedia.org/wiki/.io#Phasing_Out">https://en.wikipedia.org/wiki/.io#Phasing_Out</a><br class="auto-break"/><a id="t5ZT1_note-3" href="#t5ZT1_ref-3">³</a> <a class="auto-link" href="https://en.wikipedia.org/wiki/.cs">https://en.wikipedia.org/wiki/.cs</a><br class="auto-break"/><a id="t5ZT1_note-4" href="#t5ZT1_ref-4">⁴</a> E.g. <a class="auto-link" href="https://indieweb.org/webmention.io">https://indieweb.org/webmention.io</a> or <a class="auto-link" href="https://indieweb.org/granary.io">https://indieweb.org/granary.io</a><br class="auto-break"/><a id="t5ZT1_note-5" href="#t5ZT1_ref-5">⁵</a> E.g. <a class="auto-link" href="https://indieweb.org/werd.io">https://indieweb.org/werd.io</a><br class="auto-break"/><a id="t5ZT1_note-6" href="#t5ZT1_ref-6">⁶</a> <a class="auto-link" href="https://indieweb.org/github.io">https://indieweb.org/github.io</a><br class="auto-break"/><br class="auto-break"/>This is post 25 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/283/t1/metaphors-constructive-cooperative-joyful">https://tantek.com/2024/283/t1/metaphors-constructive-cooperative-joyful</a><br class="auto-break"/>→ <a class="auto-link" href="https://tantek.com/2024/287/t1/fediverse-unfollow-bridgyfed-bug">https://tantek.com/2024/287/t1/fediverse-unfollow-bridgyfed-bug</a></div>
  114.    </content>
  115.    <object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
  116.  </entry>
  117.  <entry>
  118.    <updated>2024-10-09T12:06:00-07:00</updated>
  119.    <published>2024-10-09T12:06:00-07:00</published>
  120.    <link href="https://tantek.com/2024/283/t1/metaphors-constructive-cooperative-joyful" rel="alternate" title="" type="text/html"/>
  121.    <id>https://tantek.com/2024/283/t1/metaphors-constructive-cooperative-joyful</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">I have put a lot of thought into deliberately shifting<a id="t5ZR1_ref-1" href="#t5ZR1_note-1">¹</a> metaphors<a id="t5ZR1_ref-2" href="#t5ZR1_note-2">²</a>, often in the context of the #<span class="p-category auto-tag">indieweb</span><a id="t5ZR1_ref-3" href="#t5ZR1_note-3">³</a>. One goal is to replace use of violent or divisive metaphors with actively constructive, cooperative, or joyful alternatives, like:<br class="auto-break"/><br class="auto-break"/>* gardening/farming e.g. digital garden<a id="t5ZR1_ref-4" href="#t5ZR1_note-4">⁴</a><br class="auto-break"/>* biology/ecology/nature e.g. digital ecosystem<a id="t5ZR1_ref-5" href="#t5ZR1_note-5">⁵</a><br class="auto-break"/>* cooking/baking e.g. eat your own cooking<a id="t5ZR1_ref-6" href="#t5ZR1_note-6">⁶</a><br class="auto-break"/>* toolmaking, clothing making, other useful crafts e.g. sew what you want<a id="t5ZR1_ref-7" href="#t5ZR1_note-7">⁷</a><br class="auto-break"/>* music, dancing, painting, and other expressive crafts e.g. remixing<a id="t5ZR1_ref-8" href="#t5ZR1_note-8">⁸</a><br class="auto-break"/>* travel, navigation, maps e.g. information superhighway<a id="t5ZR1_ref-9" href="#t5ZR1_note-9">⁹</a><br class="auto-break"/>* games, sports, running, e.g. surfing the net<a id="t5ZR1_ref-10" href="#t5ZR1_note-10">¹⁰</a><br class="auto-break"/><br class="auto-break"/>Some of these areas are well developed (sports metaphors), others are obvious or emergent from various IndieWeb efforts like our principles<a id="t5ZR1_ref-11" href="#t5ZR1_note-11">¹¹</a>, and others could use brainstorming and experimentation.<br class="auto-break"/><br class="auto-break"/>Thoughts and words, whether spoken or written, influence each other in reinforcement feedback loops. Consciously choosing one can impact the other and vice versa.<br class="auto-break"/><br class="auto-break"/>Especially in messages to others or our even future selves, words and metaphors communicate and reinforce our values and thus merit care in their invention<a id="t5ZR1_ref-12" href="#t5ZR1_note-12">¹²</a> and usage.<br class="auto-break"/><br class="auto-break"/>What are metaphors you have found constructive, cooperative, or joyful?<br class="auto-break"/><br class="auto-break"/>References:<br class="auto-break"/><br class="auto-break"/><a id="t5ZR1_note-1" href="#t5ZR1_ref-1">¹</a> <a class="auto-link" href="https://tantek.com/2023/132/t1/agenda-gardening-metaphors">https://tantek.com/2023/132/t1/agenda-gardening-metaphors</a><br class="auto-break"/><a id="t5ZR1_note-2" href="#t5ZR1_ref-2">²</a> <a class="auto-link" href="https://tantek.com/2023/023/t3/">https://tantek.com/2023/023/t3/</a><br class="auto-break"/><a id="t5ZR1_note-3" href="#t5ZR1_ref-3">³</a> <a class="auto-link" href="https://tantek.com/2023/022/t1/indieweb-eat-what-you-cook">https://tantek.com/2023/022/t1/indieweb-eat-what-you-cook</a><br class="auto-break"/><a id="t5ZR1_note-4" href="#t5ZR1_ref-4">⁴</a> <a class="auto-link" href="https://indieweb.org/digital_garden">https://indieweb.org/digital_garden</a><br class="auto-break"/><a id="t5ZR1_note-5" href="#t5ZR1_ref-5">⁵</a> <a class="auto-link" href="https://en.wikipedia.org/wiki/Digital_ecosystem">https://en.wikipedia.org/wiki/Digital_ecosystem</a><br class="auto-break"/><a id="t5ZR1_note-6" href="#t5ZR1_ref-6">⁶</a> <a class="auto-link" href="https://indieweb.org/cook_what_you_want">https://indieweb.org/cook_what_you_want</a><br class="auto-break"/><a id="t5ZR1_note-7" href="#t5ZR1_ref-7">⁷</a> <a class="auto-link" href="https://indieweb.org/events/2020-08-19-hwc-west-coast#sewing">https://indieweb.org/events/2020-08-19-hwc-west-coast#sewing</a><br class="auto-break"/><a id="t5ZR1_note-8" href="#t5ZR1_ref-8">⁸</a> <a class="auto-link" href="https://en.wikipedia.org/wiki/Remix_culture#Analog_era">https://en.wikipedia.org/wiki/Remix_culture#Analog_era</a><br class="auto-break"/><a id="t5ZR1_note-9" href="#t5ZR1_ref-9">⁹</a> <a class="auto-link" href="https://en.wikipedia.org/wiki/Information_superhighway">https://en.wikipedia.org/wiki/Information_superhighway</a><br class="auto-break"/><a id="t5ZR1_note-10" href="#t5ZR1_ref-10">¹⁰</a> <a class="auto-link" href="https://en.wikipedia.org/wiki/Internet_metaphors#Functional_metaphors">https://en.wikipedia.org/wiki/Internet_metaphors#Functional_metaphors</a><br class="auto-break"/><a id="t5ZR1_note-11" href="#t5ZR1_ref-11">¹¹</a> <a class="auto-link" href="https://indieweb.org/principles">https://indieweb.org/principles</a><br class="auto-break"/><a id="t5ZR1_note-12" href="#t5ZR1_ref-12">¹²</a> <a class="auto-link" href="https://tantek.com/2024/180/b1/responsible-inventing">https://tantek.com/2024/180/b1/responsible-inventing</a><br class="auto-break"/><br class="auto-break"/><br class="auto-break"/>This is post 24 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/277/t2/october-blogtober-indieweb">https://tantek.com/2024/277/t2/october-blogtober-indieweb</a><br class="auto-break"/>→ <a class="auto-link" href="https://tantek.com/2024/285/t1/io-domain-suggested-steps">https://tantek.com/2024/285/t1/io-domain-suggested-steps</a></div>
  127.    </content>
  128.    <object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
  129.  </entry>
  130. </feed>
  131.  

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

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