micromicro.cc

Extract microformats2-encoded data from a webpage.

Search Results

Found the following microformats2-encoded data for https://tantek.com/:

Items

Summary of microformats2-encoded items published by https://tantek.com/ presented as tabular data.
h-card 8
h-cassis-username 6
h-cite 16
h-entry 46
h-event 3
h-feed 4
h-org 2
h-pronoun 2

Relationships

Summary of microformats2-encoded relationships published by https://tantek.com/ presented as tabular data.
alternate 2
apple-touch-icon-precomposed 1
author 1
authorization_endpoint 1
bookmark 1
canonical 1
hub 1
icon 1
me 7
microsub 1
nofollow 3
openid.delegate 1
openid.server 1
payment 1
self 1
serviceworker 1
token_endpoint 1
webmention 1

JSON Data

{
  "items": [
    {
      "type": [
        "h-card"
      ],
      "properties": {
        "photo": [
          {
            "value": "https://tantek.com/photo.jpg",
            "alt": ""
          }
        ],
        "url": [
          "https://tantek.com/",
          "https://micro.blog/t",
          "https://instagram.com/tantek/",
          "https://twitter.com/intent/user?screen_name=t",
          "https://github.com/tantek",
          "https://indieweb.org/User:Tantek.com",
          "https://en.wikipedia.org/wiki/User:Tantek"
        ],
        "uid": [
          "https://tantek.com/"
        ],
        "name": [
          "Tantek Çelik"
        ],
        "role": [
          "inventor, \nconnector, \nwriter, \nrunner, \nscientist, more.",
          "Web Standards Lead",
          "CSS WG"
        ],
        "category": [
          "inventor",
          "connector",
          "writer",
          "runner",
          "scientist",
          {
            "type": [
              "h-card"
            ],
            "properties": {
              "name": [
                "Stanford University"
              ],
              "url": [
                "https://stanford.edu/"
              ]
            },
            "value": "Stanford University"
          },
          "microformats2",
          "h-card",
          "h-cite",
          "h-entry",
          "h-event",
          "HTML5",
          "CSS3",
          {
            "type": [
              "h-org"
            ],
            "properties": {
              "name": [
                "IndieWeb"
              ],
              "url": [
                "https://indieweb.org/"
              ]
            },
            "value": "IndieWeb"
          },
          "authorship",
          "POSSE",
          "post type discovery",
          "webactions",
          "IndieMark",
          "CASSIS",
          "Falcon"
        ],
        "note": [
          "Hello\nHi. I work on web standards and the indie web. I run trails at sunrise, practice yoga movement & philosophy, code & design my website, and write when I can. \nMy pronouns are \nhe/him.\n🏠 \n📺 \n🔵\n\n\n\n\n💬 Contact\n👏 Tip\n\n\n\n\n\n\nFounder at IndieWeb\n\n\nFounder at microformats.org\n\n\nWeb Standards Lead at Mozilla\n\n\nAC AB & CSS WG member at W3C\n\nBSCS & MSCS Stanford University"
        ],
        "pronouns": [
          "he/him"
        ],
        "pronoun": [
          {
            "type": [
              "h-pronoun"
            ],
            "properties": {
              "name": [
                "he"
              ],
              "url": [
                "https://pronoun.is/he"
              ]
            },
            "value": "he"
          },
          {
            "type": [
              "h-pronoun"
            ],
            "properties": {
              "name": [
                "him"
              ],
              "url": [
                "https://pronoun.is/he/him"
              ]
            },
            "value": "him"
          }
        ],
        "org": [
          {
            "type": [
              "h-card"
            ],
            "properties": {
              "name": [
                "IndieWeb"
              ],
              "url": [
                "https://indieweb.org/"
              ]
            },
            "value": "IndieWeb"
          },
          {
            "type": [
              "h-card"
            ],
            "properties": {
              "name": [
                "microformats.org"
              ],
              "url": [
                "http://microformats.org/"
              ]
            },
            "value": "microformats.org"
          },
          {
            "type": [
              "h-card"
            ],
            "properties": {
              "name": [
                "Mozilla"
              ],
              "url": [
                "https://mozilla.org/"
              ]
            },
            "value": "Mozilla"
          },
          {
            "type": [
              "h-card"
            ],
            "properties": {
              "name": [
                "W3C"
              ],
              "url": [
                "https://www.w3.org/"
              ]
            },
            "value": "W3C"
          },
          {
            "type": [
              "h-org"
            ],
            "properties": {
              "name": [
                "IndieWeb"
              ],
              "url": [
                "https://indieweb.org/"
              ]
            },
            "value": "IndieWeb"
          }
        ]
      },
      "children": [
        {
          "type": [
            "h-feed"
          ],
          "properties": {
          },
          "id": "updates",
          "children": [
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "Is the #IndieWeb just blogs/blogging?What if I told you the \"indie web\"^1 is older than \"blog\" or \"weblog\"^2?The IndieWeb, as it says on the homepage^3, also goes beyond blogging^4.And those are just the terms.It should come as no surprise that conceptually:personal sites in general, predated personal sites with reverse-chronologically-ordered dated entries.Good concepts, even if forgotten, tend to be rediscovered & reinvented over time.When I first used the phrase \"indie web\" (two words) in 2010^5, I used it descriptively, an informal shorthand for the \"independent web\". I didn’t find out about the 1997^1 use of the phrase until many years later.I saw & was a fan of the 2001 launch of the \"Independents Day\" site & its manifesto^6 (at independentsday(.)org, since offline) that asked “if you create^7 your own site”, to join them. That encouragement stuck with me, and was a source of inspiration nine years later.In my presentation^8 at the 2010 Federated Social Web Summit^9, I referenced the \"indie web\" again, and afterwards I proposed to @aaronparecki.com that we start something focused on explicit principles & practices.^10 After subsequent chats & discussions, we settled on the term “IndieWeb” (one word). We started with three essential principles/practices, in today’s terms: “create”, “use what you make”, and “own your data”, which the community eventually expanded into 11 principles^11.This brings us back to the original question, is the #IndieWeb just blogs/blogging?In short no. Seemingly paradoxically, blogging is neither required nor sufficient to “be” IndieWeb as we use the term today.Are IndieWeb sites blogs?Some (perhaps even most) of them are. However, there are plenty of personal sites that are just a homepage^12, or a handful of static pages like a portfolio^13.Are blogs IndieWeb sites?Some of them are, if they are personal blogs, or other forms of independent sites, like small organizations with their own blogs, on their own domains. However the concept of the IndieWeb goes far beyond blogging, or any jargon like decentralization or federation.^4The aforementioned principles^11 provide a good foundation for the IndieWeb, and a good contrast from the prevailing project-centric attitudes of the day. The practices described inside each principle, such as owning your data meaning owning your notes^14 as well, start to hint at what it means to do & be IndieWeb today.If you have a blog on your own domain, and yet you post notes as tweets or toots on someone else’s domain, are you “doing” IndieWeb?Such a split practice could be considered a mid-to-late 2000s approach to the “indie web”, but certainly not the 2023 IndieWeb. Since 2010, the IndieWeb evolved & extended far beyond blogs, into many kinds of posts^15 typical in social media (but lacking in blogs), and site-to-site social web interactions^16, like replies that looked like actual comments, rather than awkwardly displayed blog trackbacks/pingbacks.Either way, if you have your own site (whether a blog or not) and create with it, like the 2001 Independents Day encouragement, come join us^17, and we’ll help you get setup to do so much more.This is day 25 of #100DaysOfIndieWeb #100Days← Day 24: https://tantek.com/2023/027/t5/contrast-domain-chat-name→ 🔮^1 1997-02-01 https://web.archive.org/web/20010805195949/http://www.uzine.net/article63.html^2 https://en.wikipedia.org/wiki/Blog#History^3 https://indieweb.org/#Beyond_Blogging_and_Decentralization^4 https://indieweb.org/different^5 http://tantek.com/2010/123/t2/blogger-turned-off-ftp-what-indie-web-diso (https://twitter.com/t/status/13329370781)^6 https://indieweb.org/Independents_Day^7 https://indieweb.org/creator^8 https://web.archive.org/web/20100723133231/http://federatedsocialweb.net/wiki/2010-199-tantek-fsws-talk^9 https://indieweb.org/Federated_Social_Web_Summit#Portland_2010^10 https://indieweb.org/founders#IndieWeb_movement_and_terminology^11 https://indieweb.org/principles^12 https://indieweb.org/homepage^13 https://indieweb.org/portfolio^14 https://tantek.com/2023/001/t1/own-your-notes^15 https://indieweb.org/posts#Types_of_Posts^16 https://indieweb.org/responses^17 https://chat.indieweb.org/"
                ],
                "content": [
                  {
                    "html": "Is the #<span class=\"p-category auto-tag\">IndieWeb</span> just blogs/blogging?<br class=\"auto-break\"><br class=\"auto-break\">What if I told you the \"indie web\"^1 is older than \"blog\" or \"weblog\"^2?<br class=\"auto-break\"><br class=\"auto-break\">The IndieWeb, as it says on the homepage^3, also goes beyond blogging^4.<br class=\"auto-break\"><br class=\"auto-break\">And those are just the terms.<br class=\"auto-break\"><br class=\"auto-break\">It should come as no surprise that conceptually:<br class=\"auto-break\"><br class=\"auto-break\">personal sites in general, predated <br class=\"auto-break\">personal sites with reverse-chronologically-ordered dated entries.<br class=\"auto-break\"><br class=\"auto-break\">Good concepts, even if forgotten, tend to be rediscovered &amp; reinvented over time.<br class=\"auto-break\"><br class=\"auto-break\">When I first used the phrase \"indie web\" (two words) in 2010^5, I used it descriptively, an informal shorthand for the \"independent web\". I didn’t find out about the 1997^1 use of the phrase until many years later.<br class=\"auto-break\"><br class=\"auto-break\">I saw &amp; was a fan of the 2001 launch of the \"Independents Day\" site &amp; its manifesto^6 (at independentsday(.)org, since offline) that asked “if you create^7 your own site”, to join them. That encouragement stuck with me, and was a source of inspiration nine years later.<br class=\"auto-break\"><br class=\"auto-break\">In my presentation^8 at the 2010 Federated Social Web Summit^9, I referenced the \"indie web\" again, and afterwards I proposed to <a class=\"auto-link\" href=\"https://aaronparecki.com/\">@aaronparecki.com</a> that we start something focused on explicit principles &amp; practices.^10 <br class=\"auto-break\"><br class=\"auto-break\">After subsequent chats &amp; discussions, we settled on the term “IndieWeb” (one word). We started with three essential principles/practices, in today’s terms: “create”, “use what you make”, and “own your data”, which the community eventually expanded into 11 principles^11.<br class=\"auto-break\"><br class=\"auto-break\">This brings us back to the original question, is the #<span class=\"p-category auto-tag\">IndieWeb</span> just blogs/blogging?<br class=\"auto-break\"><br class=\"auto-break\">In short no. Seemingly paradoxically, blogging is neither required nor sufficient to “be” IndieWeb as we use the term today.<br class=\"auto-break\"><br class=\"auto-break\">Are IndieWeb sites blogs?<br class=\"auto-break\"><br class=\"auto-break\">Some (perhaps even most) of them are. However, there are plenty of personal sites that are just a homepage^12, or a handful of static pages like a portfolio^13.<br class=\"auto-break\"><br class=\"auto-break\">Are blogs IndieWeb sites?<br class=\"auto-break\"><br class=\"auto-break\">Some of them are, if they are personal blogs, or other forms of independent sites, like small organizations with their own blogs, on their own domains. However the concept of the IndieWeb goes far beyond blogging, or any jargon like decentralization or federation.^4<br class=\"auto-break\"><br class=\"auto-break\">The aforementioned principles^11 provide a good foundation for the IndieWeb, and a good contrast from the prevailing project-centric attitudes of the day. The practices described inside each principle, such as owning your data meaning owning your notes^14 as well, start to hint at what it means to do &amp; be IndieWeb today.<br class=\"auto-break\"><br class=\"auto-break\">If you have a blog on your own domain, and yet you post notes as tweets or toots on someone else’s domain, are you “doing” IndieWeb?<br class=\"auto-break\"><br class=\"auto-break\">Such a split practice could be considered a mid-to-late 2000s approach to the “indie web”, but certainly not the 2023 IndieWeb. Since 2010, the IndieWeb evolved &amp; extended far beyond blogs, into many kinds of posts^15 typical in social media (but lacking in blogs), and site-to-site social web interactions^16, like replies that looked like actual comments, rather than awkwardly displayed blog trackbacks/pingbacks.<br class=\"auto-break\"><br class=\"auto-break\">Either way, if you have your own site (whether a blog or not) and create with it, like the 2001 Independents Day encouragement, come join us^17, and we’ll help you get setup to do so much more.<br class=\"auto-break\"><br class=\"auto-break\"><br class=\"auto-break\">This is day 25 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 24: <a class=\"auto-link\" href=\"https://tantek.com/2023/027/t5/contrast-domain-chat-name\">https://tantek.com/2023/027/t5/contrast-domain-chat-name</a><br class=\"auto-break\">→ 🔮<br class=\"auto-break\"><br class=\"auto-break\"><br class=\"auto-break\">^1 1997-02-01 <a class=\"auto-link\" href=\"https://web.archive.org/web/20010805195949/http://www.uzine.net/article63.html\">https://web.archive.org/web/20010805195949/http://www.uzine.net/article63.html</a><br class=\"auto-break\">^2 <a class=\"auto-link\" href=\"https://en.wikipedia.org/wiki/Blog#History\">https://en.wikipedia.org/wiki/Blog#History</a><br class=\"auto-break\">^3 <a class=\"auto-link\" href=\"https://indieweb.org/#Beyond_Blogging_and_Decentralization\">https://indieweb.org/#Beyond_Blogging_and_Decentralization</a><br class=\"auto-break\">^4 <a class=\"auto-link\" href=\"https://indieweb.org/different\">https://indieweb.org/different</a><br class=\"auto-break\">^5 <a class=\"auto-link\" href=\"http://tantek.com/2010/123/t2/blogger-turned-off-ftp-what-indie-web-diso\">http://tantek.com/2010/123/t2/blogger-turned-off-ftp-what-indie-web-diso</a> (<a class=\"auto-link\" href=\"https://twitter.com/t/status/13329370781\">https://twitter.com/t/status/13329370781</a>)<br class=\"auto-break\">^6 <a class=\"auto-link\" href=\"https://indieweb.org/Independents_Day\">https://indieweb.org/Independents_Day</a><br class=\"auto-break\">^7 <a class=\"auto-link\" href=\"https://indieweb.org/creator\">https://indieweb.org/creator</a><br class=\"auto-break\">^8 <a class=\"auto-link\" href=\"https://web.archive.org/web/20100723133231/http://federatedsocialweb.net/wiki/2010-199-tantek-fsws-talk\">https://web.archive.org/web/20100723133231/http://federatedsocialweb.net/wiki/2010-199-tantek-fsws-talk</a><br class=\"auto-break\">^9 <a class=\"auto-link\" href=\"https://indieweb.org/Federated_Social_Web_Summit#Portland_2010\">https://indieweb.org/Federated_Social_Web_Summit#Portland_2010</a><br class=\"auto-break\">^10 <a class=\"auto-link\" href=\"https://indieweb.org/founders#IndieWeb_movement_and_terminology\">https://indieweb.org/founders#IndieWeb_movement_and_terminology</a><br class=\"auto-break\">^11 <a class=\"auto-link\" href=\"https://indieweb.org/principles\">https://indieweb.org/principles</a><br class=\"auto-break\">^12 <a class=\"auto-link\" href=\"https://indieweb.org/homepage\">https://indieweb.org/homepage</a><br class=\"auto-break\">^13 <a class=\"auto-link\" href=\"https://indieweb.org/portfolio\">https://indieweb.org/portfolio</a><br class=\"auto-break\">^14 <a class=\"auto-link\" href=\"https://tantek.com/2023/001/t1/own-your-notes\">https://tantek.com/2023/001/t1/own-your-notes</a><br class=\"auto-break\">^15 <a class=\"auto-link\" href=\"https://indieweb.org/posts#Types_of_Posts\">https://indieweb.org/posts#Types_of_Posts</a><br class=\"auto-break\">^16 <a class=\"auto-link\" href=\"https://indieweb.org/responses\">https://indieweb.org/responses</a><br class=\"auto-break\">^17 <a class=\"auto-link\" href=\"https://chat.indieweb.org/\">https://chat.indieweb.org/</a>",
                    "value": "Is the #IndieWeb just blogs/blogging?What if I told you the \"indie web\"^1 is older than \"blog\" or \"weblog\"^2?The IndieWeb, as it says on the homepage^3, also goes beyond blogging^4.And those are just the terms.It should come as no surprise that conceptually:personal sites in general, predated personal sites with reverse-chronologically-ordered dated entries.Good concepts, even if forgotten, tend to be rediscovered & reinvented over time.When I first used the phrase \"indie web\" (two words) in 2010^5, I used it descriptively, an informal shorthand for the \"independent web\". I didn’t find out about the 1997^1 use of the phrase until many years later.I saw & was a fan of the 2001 launch of the \"Independents Day\" site & its manifesto^6 (at independentsday(.)org, since offline) that asked “if you create^7 your own site”, to join them. That encouragement stuck with me, and was a source of inspiration nine years later.In my presentation^8 at the 2010 Federated Social Web Summit^9, I referenced the \"indie web\" again, and afterwards I proposed to @aaronparecki.com that we start something focused on explicit principles & practices.^10 After subsequent chats & discussions, we settled on the term “IndieWeb” (one word). We started with three essential principles/practices, in today’s terms: “create”, “use what you make”, and “own your data”, which the community eventually expanded into 11 principles^11.This brings us back to the original question, is the #IndieWeb just blogs/blogging?In short no. Seemingly paradoxically, blogging is neither required nor sufficient to “be” IndieWeb as we use the term today.Are IndieWeb sites blogs?Some (perhaps even most) of them are. However, there are plenty of personal sites that are just a homepage^12, or a handful of static pages like a portfolio^13.Are blogs IndieWeb sites?Some of them are, if they are personal blogs, or other forms of independent sites, like small organizations with their own blogs, on their own domains. However the concept of the IndieWeb goes far beyond blogging, or any jargon like decentralization or federation.^4The aforementioned principles^11 provide a good foundation for the IndieWeb, and a good contrast from the prevailing project-centric attitudes of the day. The practices described inside each principle, such as owning your data meaning owning your notes^14 as well, start to hint at what it means to do & be IndieWeb today.If you have a blog on your own domain, and yet you post notes as tweets or toots on someone else’s domain, are you “doing” IndieWeb?Such a split practice could be considered a mid-to-late 2000s approach to the “indie web”, but certainly not the 2023 IndieWeb. Since 2010, the IndieWeb evolved & extended far beyond blogs, into many kinds of posts^15 typical in social media (but lacking in blogs), and site-to-site social web interactions^16, like replies that looked like actual comments, rather than awkwardly displayed blog trackbacks/pingbacks.Either way, if you have your own site (whether a blog or not) and create with it, like the 2001 Independents Day encouragement, come join us^17, and we’ll help you get setup to do so much more.This is day 25 of #100DaysOfIndieWeb #100Days← Day 24: https://tantek.com/2023/027/t5/contrast-domain-chat-name→ 🔮^1 1997-02-01 https://web.archive.org/web/20010805195949/http://www.uzine.net/article63.html^2 https://en.wikipedia.org/wiki/Blog#History^3 https://indieweb.org/#Beyond_Blogging_and_Decentralization^4 https://indieweb.org/different^5 http://tantek.com/2010/123/t2/blogger-turned-off-ftp-what-indie-web-diso (https://twitter.com/t/status/13329370781)^6 https://indieweb.org/Independents_Day^7 https://indieweb.org/creator^8 https://web.archive.org/web/20100723133231/http://federatedsocialweb.net/wiki/2010-199-tantek-fsws-talk^9 https://indieweb.org/Federated_Social_Web_Summit#Portland_2010^10 https://indieweb.org/founders#IndieWeb_movement_and_terminology^11 https://indieweb.org/principles^12 https://indieweb.org/homepage^13 https://indieweb.org/portfolio^14 https://tantek.com/2023/001/t1/own-your-notes^15 https://indieweb.org/posts#Types_of_Posts^16 https://indieweb.org/responses^17 https://chat.indieweb.org/"
                  }
                ],
                "category": [
                  "IndieWeb",
                  "IndieWeb",
                  "100DaysOfIndieWeb",
                  "100Days"
                ],
                "published": [
                  "20:42 on 2023-01-29"
                ],
                "updated": [
                  "20:42 on 2023-01-29"
                ],
                "url": [
                  "https://tantek.com/2023/029/t1/indieweb-beyond-blogging"
                ],
                "uid": [
                  "https://tantek.com/2023/029/t1/indieweb-beyond-blogging"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "Another interesting contrast^1 in the #IndieWeb community is that most of us have both:* a domain name^2 — for posting our content, replies, likes etc.* a chat-name^3 — for chatting in our discussion channels^4Ideally, we would have a discussion system that “just” used our domain names as identities (IndieAuth^5 for Web sign-in^6) to chat with each other, but no such system exists (yet).No we’re not going to all setup XMPP servers on our domains and attempt to hook them all up. Nearly no one wants to pay that admintax^7. Nor would XMPP let us “just” use our domain names. Like email, XMPP requires a separate “username”. Sure we could fake it like Bridgy Fed does for us with 'domain @ domain', but why would we work harder for a worse UX?So instead of making things more complex than domains, we took the opposite approach, and based our chat on IRC, and our chat-names on plain nicknames.Using a chat system like IRC lowered the barrier to participation in the IndieWeb community, so you could for example, ask about how to pick a domain name^2 instead of being stuck in an actual catch-22^1 of needing a domain name just to ask about a domain name.By putting our chat archives on the web^8, we were able to reduce our chat system requirements, provide a simple minimal web app for brief chats, and bridge our IRC channels with multiple other chat systems, like Slack, Matrix, and even Discord^9. This has the significant advantage of much greater chat client choice for community members.However, we did realize that our statements in the chat archives^8 could be more closely tied to our domain identities, including our personal icons^10. Rather than a complex system or new protocol, we just put our flat list of nicknames in templates with images & domains on the wiki^11.Thus our chat archives, despite being based on IRC, show icons for people, and link their chat nicknames to their personal domain names, again striking a pragmatic balance.^1The flexibility of using a wiki template allowed us to add personal time zones as well, to enable things like asking in chat, “what time is it for tantek”. This works well enough, except does not account for cross-time-zone travel, though you could update your chat-name entry if you wanted to while traveling.Having all our chat-names in a single list^11 on a page like that revealed another interesting aspect: we have folks across all the timezones in the US & Europe, some in the Middle East, Australia, and most of Asia as well.As a result, the IndieWeb chat channels have people awake and often discussing various topics 24 hours a day.Drop by^8 and say hi, and be sure to have a look at our Code of Conduct.^12This is day 24 of #100DaysOfIndieWeb #100Days← Day 23: https://tantek.com/2023/027/t4/five-years-websub→ Day 25: https://tantek.com/2023/029/t1/indieweb-beyond-blogging^1 https://tantek.com/2023/026/t1/indieweb-priorities-balance^2 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb^3 https://indieweb.org/chat-names^4 https://indieweb.org/discuss^5 https://indieweb.org/IndieAuth^6 https://indieweb.org/Web_sign-in^7 https://indieweb.org/admintax^8 https://chat.indieweb.org/^9 https://indieweb.org/discuss#Join_Discussions^10 https://indieweb.org/icon^11 https://indieweb.org/chat-names#Nicknames^12 https://indieweb.org/code-of-conduct"
                ],
                "content": [
                  {
                    "html": "Another interesting contrast^1 in the #<span class=\"p-category auto-tag\">IndieWeb</span> community is that most of us have both:<br class=\"auto-break\">* a domain name^2 — for posting our content, replies, likes etc.<br class=\"auto-break\">* a chat-name^3 — for chatting in our discussion channels^4<br class=\"auto-break\"><br class=\"auto-break\">Ideally, we would have a discussion system that “just” used our domain names as identities (IndieAuth^5 for Web sign-in^6) to chat with each other, but no such system exists (yet).<br class=\"auto-break\"><br class=\"auto-break\">No we’re not going to all setup XMPP servers on our domains and attempt to hook them all up. Nearly no one wants to pay that admintax^7. Nor would XMPP let us “just” use our domain names. Like email, XMPP requires a separate “username”. Sure we could fake it like Bridgy Fed does for us with 'domain @ domain', but why would we work harder for a worse UX?<br class=\"auto-break\"><br class=\"auto-break\">So instead of making things more complex than domains, we took the opposite approach, and based our chat on IRC, and our chat-names on plain nicknames.<br class=\"auto-break\"><br class=\"auto-break\">Using a chat system like IRC lowered the barrier to participation in the IndieWeb community, so you could for example, ask about how to pick a domain name^2 instead of being stuck in an actual catch-22^1 of needing a domain name just to ask about a domain name.<br class=\"auto-break\"><br class=\"auto-break\">By putting our chat archives on the web^8, we were able to reduce our chat system requirements, provide a simple minimal web app for brief chats, and bridge our IRC channels with multiple other chat systems, like Slack, Matrix, and even Discord^9. This has the significant advantage of much greater chat client choice for community members.<br class=\"auto-break\"><br class=\"auto-break\">However, we did realize that our statements in the chat archives^8 could be more closely tied to our domain identities, including our personal icons^10. Rather than a complex system or new protocol, we just put our flat list of nicknames in templates with images &amp; domains on the wiki^11.<br class=\"auto-break\"><br class=\"auto-break\">Thus our chat archives, despite being based on IRC, show icons for people, and link their chat nicknames to their personal domain names, again striking a pragmatic balance.^1<br class=\"auto-break\"><br class=\"auto-break\">The flexibility of using a wiki template allowed us to add personal time zones as well, to enable things like asking in chat, “what time is it for tantek”. This works well enough, except does not account for cross-time-zone travel, though you could update your chat-name entry if you wanted to while traveling.<br class=\"auto-break\"><br class=\"auto-break\">Having all our chat-names in a single list^11 on a page like that revealed another interesting aspect: we have folks across all the timezones in the US &amp; Europe, some in the Middle East, Australia, and most of Asia as well.<br class=\"auto-break\"><br class=\"auto-break\">As a result, the IndieWeb chat channels have people awake and often discussing various topics 24 hours a day.<br class=\"auto-break\"><br class=\"auto-break\">Drop by^8 and say hi, and be sure to have a look at our Code of Conduct.^12<br class=\"auto-break\"><br class=\"auto-break\"><br class=\"auto-break\">This is day 24 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 23: <a class=\"auto-link\" href=\"https://tantek.com/2023/027/t4/five-years-websub\">https://tantek.com/2023/027/t4/five-years-websub</a><br class=\"auto-break\">→ Day 25: <a class=\"auto-link\" href=\"https://tantek.com/2023/029/t1/indieweb-beyond-blogging\">https://tantek.com/2023/029/t1/indieweb-beyond-blogging</a><br class=\"auto-break\"><br class=\"auto-break\"><br class=\"auto-break\">^1 <a class=\"auto-link\" href=\"https://tantek.com/2023/026/t1/indieweb-priorities-balance\">https://tantek.com/2023/026/t1/indieweb-priorities-balance</a><br class=\"auto-break\">^2 <a class=\"auto-link\" href=\"https://tantek.com/2023/004/t1/choosing-domain-name-indieweb\">https://tantek.com/2023/004/t1/choosing-domain-name-indieweb</a><br class=\"auto-break\">^3 <a class=\"auto-link\" href=\"https://indieweb.org/chat-names\">https://indieweb.org/chat-names</a><br class=\"auto-break\">^4 <a class=\"auto-link\" href=\"https://indieweb.org/discuss\">https://indieweb.org/discuss</a><br class=\"auto-break\">^5 <a class=\"auto-link\" href=\"https://indieweb.org/IndieAuth\">https://indieweb.org/IndieAuth</a><br class=\"auto-break\">^6 <a class=\"auto-link\" href=\"https://indieweb.org/Web_sign-in\">https://indieweb.org/Web_sign-in</a><br class=\"auto-break\">^7 <a class=\"auto-link\" href=\"https://indieweb.org/admintax\">https://indieweb.org/admintax</a><br class=\"auto-break\">^8 <a class=\"auto-link\" href=\"https://chat.indieweb.org/\">https://chat.indieweb.org/</a><br class=\"auto-break\">^9 <a class=\"auto-link\" href=\"https://indieweb.org/discuss#Join_Discussions\">https://indieweb.org/discuss#Join_Discussions</a><br class=\"auto-break\">^10 <a class=\"auto-link\" href=\"https://indieweb.org/icon\">https://indieweb.org/icon</a><br class=\"auto-break\">^11 <a class=\"auto-link\" href=\"https://indieweb.org/chat-names#Nicknames\">https://indieweb.org/chat-names#Nicknames</a><br class=\"auto-break\">^12 <a class=\"auto-link\" href=\"https://indieweb.org/code-of-conduct\">https://indieweb.org/code-of-conduct</a>",
                    "value": "Another interesting contrast^1 in the #IndieWeb community is that most of us have both:* a domain name^2 — for posting our content, replies, likes etc.* a chat-name^3 — for chatting in our discussion channels^4Ideally, we would have a discussion system that “just” used our domain names as identities (IndieAuth^5 for Web sign-in^6) to chat with each other, but no such system exists (yet).No we’re not going to all setup XMPP servers on our domains and attempt to hook them all up. Nearly no one wants to pay that admintax^7. Nor would XMPP let us “just” use our domain names. Like email, XMPP requires a separate “username”. Sure we could fake it like Bridgy Fed does for us with 'domain @ domain', but why would we work harder for a worse UX?So instead of making things more complex than domains, we took the opposite approach, and based our chat on IRC, and our chat-names on plain nicknames.Using a chat system like IRC lowered the barrier to participation in the IndieWeb community, so you could for example, ask about how to pick a domain name^2 instead of being stuck in an actual catch-22^1 of needing a domain name just to ask about a domain name.By putting our chat archives on the web^8, we were able to reduce our chat system requirements, provide a simple minimal web app for brief chats, and bridge our IRC channels with multiple other chat systems, like Slack, Matrix, and even Discord^9. This has the significant advantage of much greater chat client choice for community members.However, we did realize that our statements in the chat archives^8 could be more closely tied to our domain identities, including our personal icons^10. Rather than a complex system or new protocol, we just put our flat list of nicknames in templates with images & domains on the wiki^11.Thus our chat archives, despite being based on IRC, show icons for people, and link their chat nicknames to their personal domain names, again striking a pragmatic balance.^1The flexibility of using a wiki template allowed us to add personal time zones as well, to enable things like asking in chat, “what time is it for tantek”. This works well enough, except does not account for cross-time-zone travel, though you could update your chat-name entry if you wanted to while traveling.Having all our chat-names in a single list^11 on a page like that revealed another interesting aspect: we have folks across all the timezones in the US & Europe, some in the Middle East, Australia, and most of Asia as well.As a result, the IndieWeb chat channels have people awake and often discussing various topics 24 hours a day.Drop by^8 and say hi, and be sure to have a look at our Code of Conduct.^12This is day 24 of #100DaysOfIndieWeb #100Days← Day 23: https://tantek.com/2023/027/t4/five-years-websub→ Day 25: https://tantek.com/2023/029/t1/indieweb-beyond-blogging^1 https://tantek.com/2023/026/t1/indieweb-priorities-balance^2 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb^3 https://indieweb.org/chat-names^4 https://indieweb.org/discuss^5 https://indieweb.org/IndieAuth^6 https://indieweb.org/Web_sign-in^7 https://indieweb.org/admintax^8 https://chat.indieweb.org/^9 https://indieweb.org/discuss#Join_Discussions^10 https://indieweb.org/icon^11 https://indieweb.org/chat-names#Nicknames^12 https://indieweb.org/code-of-conduct"
                  }
                ],
                "category": [
                  "IndieWeb",
                  "100DaysOfIndieWeb",
                  "100Days"
                ],
                "published": [
                  "23:11 on 2023-01-27"
                ],
                "updated": [
                  "23:11 on 2023-01-27"
                ],
                "url": [
                  "https://tantek.com/2023/027/t5/contrast-domain-chat-name"
                ],
                "uid": [
                  "https://tantek.com/2023/027/t5/contrast-domain-chat-name"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "Five years ago (Monday the 23rd) the @W3C Social Web Working Group published the WebSub Recommendation^1The test suites https://websub.rocks/ for Publishers, Subscribers, and Hubs are still up & running, as are the vast majority of implementations documented in the implementation report.My site supports the publishing side of WebSub via the Superfeedr Hub^2 and there are many more supporting sites^3.Beyond publishing blog posts and realtime updates in social readers^4, there are additional WebSub use-cases such as real time #IndieWeb search^5 results, like Technorati except opt-in via WebSub subscriptions, and without any polling.Such diverse use-cases are one of the benefits of building-block^6 standards^7 like WebSub.If you create a new WebSub implementation, be sure to test it with the test suite^8 and add your results to the WebSub Implementation Reports repo^9.Got questions about WebSub? Ask in https://chat.indieweb.org/devThis is day 23 of #100DaysOfIndieWeb #100Days← Day 22: https://tantek.com/2023/026/t1/indieweb-priorities-balance→ Day 24: https://tantek.com/2023/027/t5/contrast-domain-chat-name^1 https://www.w3.org/TR/2018/REC-websub-20180123/^2 https://pubsubhubbub.superfeedr.com/^3 https://indieweb.org/WebSub#IndieWeb_Examples^4 https://indieweb.org/social_reader^5 https://indieweb.org/IndieWeb_Search^6 https://indieweb.org/building-blocks^7 https://spec.indieweb.org/^8 https://websub.rocks/^9 https://websub.net/implementation-reports"
                ],
                "content": [
                  {
                    "html": "Five years ago (Monday the 23rd) the <a class=\"auto-link h-cassis-username\" href=\"https://twitter.com/W3C\">@W3C</a> Social Web Working Group published the WebSub Recommendation^1<br class=\"auto-break\"><br class=\"auto-break\">The test suites <a class=\"auto-link\" href=\"https://websub.rocks/\">https://websub.rocks/</a> for Publishers, Subscribers, and Hubs are still up &amp; running, as are the vast majority of implementations documented in the implementation report.<br class=\"auto-break\"><br class=\"auto-break\">My site supports the publishing side of WebSub via the Superfeedr Hub^2 and there are many more supporting sites^3.<br class=\"auto-break\"><br class=\"auto-break\">Beyond publishing blog posts and realtime updates in social readers^4, there are additional WebSub use-cases such as real time #<span class=\"p-category auto-tag\">IndieWeb</span> search^5 results, like Technorati except opt-in via WebSub subscriptions, and without any polling.<br class=\"auto-break\"><br class=\"auto-break\">Such diverse use-cases are one of the benefits of building-block^6 standards^7 like WebSub.<br class=\"auto-break\"><br class=\"auto-break\">If you create a new WebSub implementation, be sure to test it with the test suite^8 and add your results to the WebSub Implementation Reports repo^9.<br class=\"auto-break\"><br class=\"auto-break\">Got questions about WebSub? Ask in <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\">This is day 23 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 22: <a class=\"auto-link\" href=\"https://tantek.com/2023/026/t1/indieweb-priorities-balance\">https://tantek.com/2023/026/t1/indieweb-priorities-balance</a><br class=\"auto-break\">→ Day 24: <a class=\"auto-link\" href=\"https://tantek.com/2023/027/t5/contrast-domain-chat-name\">https://tantek.com/2023/027/t5/contrast-domain-chat-name</a><br class=\"auto-break\"><br class=\"auto-break\"><br class=\"auto-break\">^1 <a class=\"auto-link\" href=\"https://www.w3.org/TR/2018/REC-websub-20180123/\">https://www.w3.org/TR/2018/REC-websub-20180123/</a><br class=\"auto-break\">^2 <a class=\"auto-link\" href=\"https://pubsubhubbub.superfeedr.com/\">https://pubsubhubbub.superfeedr.com/</a><br class=\"auto-break\">^3 <a class=\"auto-link\" href=\"https://indieweb.org/WebSub#IndieWeb_Examples\">https://indieweb.org/WebSub#IndieWeb_Examples</a><br class=\"auto-break\">^4 <a class=\"auto-link\" href=\"https://indieweb.org/social_reader\">https://indieweb.org/social_reader</a><br class=\"auto-break\">^5 <a class=\"auto-link\" href=\"https://indieweb.org/IndieWeb_Search\">https://indieweb.org/IndieWeb_Search</a><br class=\"auto-break\">^6 <a class=\"auto-link\" href=\"https://indieweb.org/building-blocks\">https://indieweb.org/building-blocks</a><br class=\"auto-break\">^7 <a class=\"auto-link\" href=\"https://spec.indieweb.org/\">https://spec.indieweb.org/</a><br class=\"auto-break\">^8 <a class=\"auto-link\" href=\"https://websub.rocks/\">https://websub.rocks/</a><br class=\"auto-break\">^9 <a class=\"auto-link\" href=\"https://websub.net/implementation-reports\">https://websub.net/implementation-reports</a>",
                    "value": "Five years ago (Monday the 23rd) the @W3C Social Web Working Group published the WebSub Recommendation^1The test suites https://websub.rocks/ for Publishers, Subscribers, and Hubs are still up & running, as are the vast majority of implementations documented in the implementation report.My site supports the publishing side of WebSub via the Superfeedr Hub^2 and there are many more supporting sites^3.Beyond publishing blog posts and realtime updates in social readers^4, there are additional WebSub use-cases such as real time #IndieWeb search^5 results, like Technorati except opt-in via WebSub subscriptions, and without any polling.Such diverse use-cases are one of the benefits of building-block^6 standards^7 like WebSub.If you create a new WebSub implementation, be sure to test it with the test suite^8 and add your results to the WebSub Implementation Reports repo^9.Got questions about WebSub? Ask in https://chat.indieweb.org/devThis is day 23 of #100DaysOfIndieWeb #100Days← Day 22: https://tantek.com/2023/026/t1/indieweb-priorities-balance→ Day 24: https://tantek.com/2023/027/t5/contrast-domain-chat-name^1 https://www.w3.org/TR/2018/REC-websub-20180123/^2 https://pubsubhubbub.superfeedr.com/^3 https://indieweb.org/WebSub#IndieWeb_Examples^4 https://indieweb.org/social_reader^5 https://indieweb.org/IndieWeb_Search^6 https://indieweb.org/building-blocks^7 https://spec.indieweb.org/^8 https://websub.rocks/^9 https://websub.net/implementation-reports"
                  }
                ],
                "category": [
                  "IndieWeb",
                  "100DaysOfIndieWeb",
                  "100Days"
                ],
                "published": [
                  "19:51 on 2023-01-27"
                ],
                "updated": [
                  "19:51 on 2023-01-27"
                ],
                "url": [
                  "https://tantek.com/2023/027/t4/five-years-websub"
                ],
                "uid": [
                  "https://tantek.com/2023/027/t4/five-years-websub"
                ]
              },
              "children": [
                {
                  "type": [
                    "h-cassis-username"
                  ],
                  "properties": {
                    "name": [
                      "@W3C"
                    ],
                    "url": [
                      "https://twitter.com/W3C"
                    ]
                  }
                }
              ]
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "in-reply-to": [
                  {
                    "type": [
                      "h-cite"
                    ],
                    "properties": {
                      "name": [
                        "bw3.dev’s post"
                      ],
                      "url": [
                        "https://bw3.dev/o/29Dfx"
                      ]
                    },
                    "value": "https://bw3.dev/o/29Dfx"
                  }
                ],
                "name": [
                  "https://bw3.dev/ (@0x3b0b) your reply mostly worked as intended! I checked my webmention.io:* 2 replies via Bridgy Fed and Bridgy (backfeed from Twitter), and * 1 mention directly from your original post permalink.Your #IndieWeb reply does have a u-in-reply-to link to a fed-brid-gy/r/ prefixed URL of my permalink, however the u-in-reply-to link directly to my site is linked to my previous post (look for \"2023/018/t1\" in your reply content’s markup) instead of the intended post! Try updating that direct link to use the correct URL (my original post at top of thread), add some link text to it, and resend a webmention.It’s ok to have multiple visible reply links (e.g. this reply has them, to your post & POSSE tweet reply, at the top.).Lastly, when you link directly from IndieWeb site to IndieWeb site with your reply, there’s no need to also link via Bridgy Fed. The direct Webmention is sufficient."
                ],
                "content": [
                  {
                    "html": "<a class=\"auto-link\" href=\"https://bw3.dev/\">https://bw3.dev/</a> (<a class=\"auto-link h-cassis-username\" href=\"https://twitter.com/0x3b0b\">@0x3b0b</a>) your reply mostly worked as intended! <br class=\"auto-break\">I checked my <a class=\"auto-link\" href=\"http://webmention.io/\">webmention.io</a>:<br class=\"auto-break\">* 2 replies via Bridgy Fed and Bridgy (backfeed from Twitter), and <br class=\"auto-break\">* 1 mention directly from your original post permalink.<br class=\"auto-break\"><br class=\"auto-break\">Your #<span class=\"p-category auto-tag\">IndieWeb</span> reply does have a u-in-reply-to link to a fed-brid-gy/r/ prefixed URL of my permalink, however the u-in-reply-to link directly to my site is linked to my previous post (look for \"2023/018/t1\" in your reply content’s markup) instead of the intended post! <br class=\"auto-break\"><br class=\"auto-break\">Try updating that direct link to use the correct URL (my original post at top of thread), add some link text to it, and resend a webmention.<br class=\"auto-break\"><br class=\"auto-break\">It’s ok to have multiple visible reply links (e.g. this reply has them, to your post &amp; POSSE tweet reply, at the top.).<br class=\"auto-break\"><br class=\"auto-break\">Lastly, when you link directly from IndieWeb site to IndieWeb site with your reply, there’s no need to also link via Bridgy Fed. The direct Webmention is sufficient.",
                    "value": "https://bw3.dev/ (@0x3b0b) your reply mostly worked as intended! I checked my webmention.io:* 2 replies via Bridgy Fed and Bridgy (backfeed from Twitter), and * 1 mention directly from your original post permalink.Your #IndieWeb reply does have a u-in-reply-to link to a fed-brid-gy/r/ prefixed URL of my permalink, however the u-in-reply-to link directly to my site is linked to my previous post (look for \"2023/018/t1\" in your reply content’s markup) instead of the intended post! Try updating that direct link to use the correct URL (my original post at top of thread), add some link text to it, and resend a webmention.It’s ok to have multiple visible reply links (e.g. this reply has them, to your post & POSSE tweet reply, at the top.).Lastly, when you link directly from IndieWeb site to IndieWeb site with your reply, there’s no need to also link via Bridgy Fed. The direct Webmention is sufficient."
                  }
                ],
                "category": [
                  "IndieWeb"
                ],
                "published": [
                  "18:43 on 2023-01-27"
                ],
                "updated": [
                  "18:43 on 2023-01-27"
                ],
                "url": [
                  "https://tantek.com/2023/027/t3/"
                ],
                "uid": [
                  "https://tantek.com/2023/027/t3/"
                ]
              },
              "children": [
                {
                  "type": [
                    "h-cassis-username"
                  ],
                  "properties": {
                    "name": [
                      "@0x3b0b"
                    ],
                    "url": [
                      "https://twitter.com/0x3b0b"
                    ]
                  }
                }
              ]
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "in-reply-to": [
                  {
                    "type": [
                      "h-cite"
                    ],
                    "properties": {
                      "name": [
                        "hachyderm.io user liztai’s post"
                      ],
                      "url": [
                        "https://hachyderm.io/@liztai/109764216636698618"
                      ]
                    },
                    "value": "https://hachyderm.io/@liztai/109764216636698618"
                  }
                ],
                "name": [
                  "@elizabethtai.com (@[email protected]) there are a bunch of current #webrings examples listed here: https://indieweb.org/webring#ExamplesI’m on the #IndieWebRing: https://indieweb.org/indiewebring Links to previous/next sites in the #webring are in the footer of my tantek.com home page."
                ],
                "content": [
                  {
                    "html": "<a class=\"auto-link\" href=\"https://elizabethtai.com/\">@elizabethtai.com</a> (<a class=\"auto-link\" href=\"https://hachyderm.io/@liztai\">@[email protected]</a>) there are a bunch of current #<span class=\"p-category auto-tag\">webrings</span> examples listed here: <a class=\"auto-link\" href=\"https://indieweb.org/webring#Examples\">https://indieweb.org/webring#Examples</a><br class=\"auto-break\"><br class=\"auto-break\">I’m on the #<span class=\"p-category auto-tag\">IndieWebRing:</span> <a class=\"auto-link\" href=\"https://indieweb.org/indiewebring\">https://indieweb.org/indiewebring</a> <br class=\"auto-break\"><br class=\"auto-break\">Links to previous/next sites in the #<span class=\"p-category auto-tag\">webring</span> are in the footer of my <a class=\"auto-link\" href=\"http://tantek.com/\">tantek.com</a> home page.",
                    "value": "@elizabethtai.com (@[email protected]) there are a bunch of current #webrings examples listed here: https://indieweb.org/webring#ExamplesI’m on the #IndieWebRing: https://indieweb.org/indiewebring Links to previous/next sites in the #webring are in the footer of my tantek.com home page."
                  }
                ],
                "category": [
                  "webrings",
                  "IndieWebRing:",
                  "webring"
                ],
                "published": [
                  "17:53 on 2023-01-27"
                ],
                "updated": [
                  "17:53 on 2023-01-27"
                ],
                "url": [
                  "https://tantek.com/2023/027/t2/"
                ],
                "uid": [
                  "https://tantek.com/2023/027/t2/"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "in-reply-to": [
                  {
                    "type": [
                      "h-cite"
                    ],
                    "properties": {
                      "name": [
                        "mastodon.social user voxpelli’s post"
                      ],
                      "url": [
                        "https://mastodon.social/@voxpelli/109763757536163279"
                      ]
                    },
                    "value": "https://mastodon.social/@voxpelli/109763757536163279"
                  }
                ],
                "name": [
                  "@kodfabrik.se (@[email protected]) thanks for the kind words!It’s not without its trade-offs. Long term it seems correct to prioritize a simpler, consistent, continuous identity & permalinks, while incrementally adding interaction features as needed. For now, browsing & Bridgy Fed notifications instead of following feels freeing."
                ],
                "content": [
                  {
                    "html": "<a class=\"auto-link\" href=\"https://kodfabrik.se/\">@kodfabrik.se</a> (<a class=\"auto-link\" href=\"https://mastodon.social/@voxpelli\">@[email protected]</a>) thanks for the kind words!<br class=\"auto-break\">It’s not without its trade-offs. Long term it seems correct to prioritize a simpler, consistent, continuous identity &amp; permalinks, while incrementally adding interaction features as needed. For now, browsing &amp; Bridgy Fed notifications instead of following feels freeing.",
                    "value": "@kodfabrik.se (@[email protected]) thanks for the kind words!It’s not without its trade-offs. Long term it seems correct to prioritize a simpler, consistent, continuous identity & permalinks, while incrementally adding interaction features as needed. For now, browsing & Bridgy Fed notifications instead of following feels freeing."
                  }
                ],
                "published": [
                  "17:18 on 2023-01-27"
                ],
                "updated": [
                  "17:18 on 2023-01-27"
                ],
                "url": [
                  "https://tantek.com/2023/027/t1/"
                ],
                "uid": [
                  "https://tantek.com/2023/027/t1/"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "There are many opposing forces in the #IndieWeb that can seem like catch-22s, yet help clarify priorities, and balance present pragmatism & future optimism.* Indie, yet often on corporate infrastructure* Independent, yet dependent on community * Own your content^1, yet share publicly, perhaps CC0^2* Control of your design^3, yet lack of control elsewhere^4* UX freedom & creativity, yet guidance toward common patterns for usability* Decentralized, yet DNS* Make what you need^5, yet open source^6 for others* Plurality^7 of projects, yet conforming to standards^8* Build it yourself, yet use services, software, & libraries built by othersThese are a few off the top of my head and implied by the IndieWeb wiki home page^9 and principles^10.Rather than contradictions, these tensions are a source of inquiry, questions, and conversations.Each could be expanded into their own discussion or exploration.Each of them is an axis of sorts, with different “right” answers for different people, depending on what they want, and how much time or other resources they have.Each makes the most sense when explored in the context of a focus on solving real user needs to participate directly on today’s web.Each is also a trap for abstract logic, theoretical purity, or dogmatic absolutism, especially when detached from real world goals, constraints, and efforts.This is day 22 of #100DaysOfIndieWeb #100Days, written after a break. Many double days ahead.← Day 21: https://tantek.com/2023/022/t2/own-your-notes-domain-migration→ Day 23: https://tantek.com/2023/027/t4/five-years-websub^1 https://tantek.com/2023/001/t1/own-your-notes^2 https://indieweb.org/IndieWeb:Copyrights^3 https://indieweb.org/design^4 https://indieweb.org/display-guidelines^5 https://indieweb.org/make_what_you_need^6 https://indieweb.org/open_source^7 https://indieweb.org/plurality^8 https://spec.indieweb.org/^9 https://indieweb.org/^10 https://indieweb.org/principles"
                ],
                "content": [
                  {
                    "html": "There are many opposing forces in the #<span class=\"p-category auto-tag\">IndieWeb</span> that can seem like catch-22s, yet help clarify priorities, and balance present pragmatism &amp; future optimism.<br class=\"auto-break\"><br class=\"auto-break\">* Indie, yet often on corporate infrastructure<br class=\"auto-break\">* Independent, yet dependent on community <br class=\"auto-break\">* Own your content^1, yet share publicly, perhaps CC0^2<br class=\"auto-break\">* Control of your design^3, yet lack of control elsewhere^4<br class=\"auto-break\">* UX freedom &amp; creativity, yet guidance toward common patterns for usability<br class=\"auto-break\">* Decentralized, yet DNS<br class=\"auto-break\">* Make what you need^5, yet open source^6 for others<br class=\"auto-break\">* Plurality^7 of projects, yet conforming to standards^8<br class=\"auto-break\">* Build it yourself, yet use services, software, &amp; libraries built by others<br class=\"auto-break\"><br class=\"auto-break\">These are a few off the top of my head and implied by the IndieWeb wiki home page^9 and principles^10.<br class=\"auto-break\"><br class=\"auto-break\">Rather than contradictions, these tensions are a source of inquiry, questions, and conversations.<br class=\"auto-break\"><br class=\"auto-break\">Each could be expanded into their own discussion or exploration.<br class=\"auto-break\"><br class=\"auto-break\">Each of them is an axis of sorts, with different “right” answers for different people, depending on what they want, and how much time or other resources they have.<br class=\"auto-break\"><br class=\"auto-break\">Each makes the most sense when explored in the context of a focus on solving real user needs to participate directly on today’s web.<br class=\"auto-break\"><br class=\"auto-break\">Each is also a trap for abstract logic, theoretical purity, or dogmatic absolutism, especially when detached from real world goals, constraints, and efforts.<br class=\"auto-break\"><br class=\"auto-break\"><br class=\"auto-break\">This is day 22 of #<span class=\"p-category auto-tag\">100DaysOfIndieWeb</span> #<span class=\"p-category auto-tag\">100Days</span>, written after a break. Many double days ahead.<br class=\"auto-break\"><br class=\"auto-break\">← Day 21: <a class=\"auto-link\" href=\"https://tantek.com/2023/022/t2/own-your-notes-domain-migration\">https://tantek.com/2023/022/t2/own-your-notes-domain-migration</a><br class=\"auto-break\">→ Day 23: <a class=\"auto-link\" href=\"https://tantek.com/2023/027/t4/five-years-websub\">https://tantek.com/2023/027/t4/five-years-websub</a><br class=\"auto-break\"><br class=\"auto-break\"><br class=\"auto-break\">^1 <a class=\"auto-link\" href=\"https://tantek.com/2023/001/t1/own-your-notes\">https://tantek.com/2023/001/t1/own-your-notes</a><br class=\"auto-break\">^2 <a class=\"auto-link\" href=\"https://indieweb.org/IndieWeb:Copyrights\">https://indieweb.org/IndieWeb:Copyrights</a><br class=\"auto-break\">^3 <a class=\"auto-link\" href=\"https://indieweb.org/design\">https://indieweb.org/design</a><br class=\"auto-break\">^4 <a class=\"auto-link\" href=\"https://indieweb.org/display-guidelines\">https://indieweb.org/display-guidelines</a><br class=\"auto-break\">^5 <a class=\"auto-link\" href=\"https://indieweb.org/make_what_you_need\">https://indieweb.org/make_what_you_need</a><br class=\"auto-break\">^6 <a class=\"auto-link\" href=\"https://indieweb.org/open_source\">https://indieweb.org/open_source</a><br class=\"auto-break\">^7 <a class=\"auto-link\" href=\"https://indieweb.org/plurality\">https://indieweb.org/plurality</a><br class=\"auto-break\">^8 <a class=\"auto-link\" href=\"https://spec.indieweb.org/\">https://spec.indieweb.org/</a><br class=\"auto-break\">^9 <a class=\"auto-link\" href=\"https://indieweb.org/\">https://indieweb.org/</a><br class=\"auto-break\">^10 <a class=\"auto-link\" href=\"https://indieweb.org/principles\">https://indieweb.org/principles</a>",
                    "value": "There are many opposing forces in the #IndieWeb that can seem like catch-22s, yet help clarify priorities, and balance present pragmatism & future optimism.* Indie, yet often on corporate infrastructure* Independent, yet dependent on community * Own your content^1, yet share publicly, perhaps CC0^2* Control of your design^3, yet lack of control elsewhere^4* UX freedom & creativity, yet guidance toward common patterns for usability* Decentralized, yet DNS* Make what you need^5, yet open source^6 for others* Plurality^7 of projects, yet conforming to standards^8* Build it yourself, yet use services, software, & libraries built by othersThese are a few off the top of my head and implied by the IndieWeb wiki home page^9 and principles^10.Rather than contradictions, these tensions are a source of inquiry, questions, and conversations.Each could be expanded into their own discussion or exploration.Each of them is an axis of sorts, with different “right” answers for different people, depending on what they want, and how much time or other resources they have.Each makes the most sense when explored in the context of a focus on solving real user needs to participate directly on today’s web.Each is also a trap for abstract logic, theoretical purity, or dogmatic absolutism, especially when detached from real world goals, constraints, and efforts.This is day 22 of #100DaysOfIndieWeb #100Days, written after a break. Many double days ahead.← Day 21: https://tantek.com/2023/022/t2/own-your-notes-domain-migration→ Day 23: https://tantek.com/2023/027/t4/five-years-websub^1 https://tantek.com/2023/001/t1/own-your-notes^2 https://indieweb.org/IndieWeb:Copyrights^3 https://indieweb.org/design^4 https://indieweb.org/display-guidelines^5 https://indieweb.org/make_what_you_need^6 https://indieweb.org/open_source^7 https://indieweb.org/plurality^8 https://spec.indieweb.org/^9 https://indieweb.org/^10 https://indieweb.org/principles"
                  }
                ],
                "category": [
                  "IndieWeb",
                  "100DaysOfIndieWeb",
                  "100Days"
                ],
                "published": [
                  "23:22 on 2023-01-26"
                ],
                "updated": [
                  "23:22 on 2023-01-26"
                ],
                "url": [
                  "https://tantek.com/2023/026/t1/indieweb-priorities-balance"
                ],
                "uid": [
                  "https://tantek.com/2023/026/t1/indieweb-priorities-balance"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "in-reply-to": [
                  {
                    "type": [
                      "h-cite"
                    ],
                    "properties": {
                      "name": [
                        "ohai.social user AnokheeTara’s post"
                      ],
                      "url": [
                        "https://ohai.social/@AnokheeTara/109736149516623200"
                      ]
                    },
                    "value": "https://ohai.social/@AnokheeTara/109736149516623200"
                  }
                ],
                "name": [
                  "@[email protected] indeed “drinking our own champagne” / “drinking your own champagne” was one of the proposed alternatives when the community was renaming “selfdogfooding”, though it had some downsides:https://indieweb.org/selfdogfood#drinking_our_own_champagneI like your points about emphasizing where something is amazing, and encouraging more fun and celebration. More positive metaphors!“taste your own cooking” is an excellent encouragement and variant of “eat what you cook” — I added it to the wiki (and quoted you if you don’t mind!) https://indieweb.org/eat_what_you_cook#Variants"
                ],
                "content": [
                  {
                    "html": "<a class=\"auto-link\" href=\"https://ohai.social/@AnokheeTara\">@[email protected]</a> indeed “drinking our own champagne” / “drinking your own champagne” was one of the proposed alternatives when the community was renaming “selfdogfooding”, though it had some downsides:<br class=\"auto-break\"><br class=\"auto-break\"><a class=\"auto-link\" href=\"https://indieweb.org/selfdogfood#drinking_our_own_champagne\">https://indieweb.org/selfdogfood#drinking_our_own_champagne</a><br class=\"auto-break\"><br class=\"auto-break\">I like your points about emphasizing where something is amazing, and encouraging more fun and celebration. More positive metaphors!<br class=\"auto-break\"><br class=\"auto-break\">“taste your own cooking” is an excellent encouragement and variant of “eat what you cook” — I added it to the wiki (and quoted you if you don’t mind!) <a class=\"auto-link\" href=\"https://indieweb.org/eat_what_you_cook#Variants\">https://indieweb.org/eat_what_you_cook#Variants</a>",
                    "value": "@[email protected] indeed “drinking our own champagne” / “drinking your own champagne” was one of the proposed alternatives when the community was renaming “selfdogfooding”, though it had some downsides:https://indieweb.org/selfdogfood#drinking_our_own_champagneI like your points about emphasizing where something is amazing, and encouraging more fun and celebration. More positive metaphors!“taste your own cooking” is an excellent encouragement and variant of “eat what you cook” — I added it to the wiki (and quoted you if you don’t mind!) https://indieweb.org/eat_what_you_cook#Variants"
                  }
                ],
                "published": [
                  "16:55 on 2023-01-23"
                ],
                "updated": [
                  "16:55 on 2023-01-23"
                ],
                "url": [
                  "https://tantek.com/2023/023/t3/"
                ],
                "uid": [
                  "https://tantek.com/2023/023/t3/"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "in-reply-to": [
                  {
                    "type": [
                      "h-cite"
                    ],
                    "properties": {
                      "name": [
                        "hachyderm.io user liztai’s post"
                      ],
                      "url": [
                        "https://hachyderm.io/@liztai/109741112012908197"
                      ]
                    },
                    "value": "https://hachyderm.io/@liztai/109741112012908197"
                  }
                ],
                "name": [
                  "@elizabethtai.com (@[email protected]) either is an excellent and challenging #100Days project.Join us in the #IndieWeb chat https://chat.indieweb.org/ for tips and help with figuring out the domain thing!"
                ],
                "content": [
                  {
                    "html": "<a class=\"auto-link\" href=\"https://elizabethtai.com/\">@elizabethtai.com</a> (<a class=\"auto-link\" href=\"https://hachyderm.io/@liztai\">@[email protected]</a>) either is an excellent and challenging #<span class=\"p-category auto-tag\">100Days</span> project.<br class=\"auto-break\"><br class=\"auto-break\">Join us in the #<span class=\"p-category auto-tag\">IndieWeb</span> chat <a class=\"auto-link\" href=\"https://chat.indieweb.org/\">https://chat.indieweb.org/</a> for tips and help with figuring out the domain thing!",
                    "value": "@elizabethtai.com (@[email protected]) either is an excellent and challenging #100Days project.Join us in the #IndieWeb chat https://chat.indieweb.org/ for tips and help with figuring out the domain thing!"
                  }
                ],
                "category": [
                  "100Days",
                  "IndieWeb"
                ],
                "published": [
                  "15:40 on 2023-01-23"
                ],
                "updated": [
                  "15:40 on 2023-01-23"
                ],
                "url": [
                  "https://tantek.com/2023/023/t2/"
                ],
                "uid": [
                  "https://tantek.com/2023/023/t2/"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "in-reply-to": [
                  {
                    "type": [
                      "h-cite"
                    ],
                    "properties": {
                      "name": [
                        "hachyderm.io user liztai’s post"
                      ],
                      "url": [
                        "https://hachyderm.io/@liztai/109735803056081113"
                      ]
                    },
                    "value": "https://hachyderm.io/@liztai/109735803056081113"
                  }
                ],
                "name": [
                  "@elizabethtai.com (@[email protected] @liztai) Welcome and good luck with shifting to your domain name!By “post 1 post a day in the #Indieweb way” it sounds like you’ve started a 100 days of blogging project (which is great!) rather than posting about IndieWeb topics in particular.Also great if you do plan to specifically write about your #IndieWeb adventures (that’s more the intent of #100DaysOfIndieWeb), like choosing/setting up your domain, your personal publishing flow, how you are publishing on your own site and distributing your posts on Mastodon etc.Whichever you choose, use your primary domain @elizabethtai.com to sign-in to the IndieWeb wiki and add yourself to the respective subsection here:https://indieweb.org/100_days#2023"
                ],
                "content": [
                  {
                    "html": "<a class=\"auto-link\" href=\"https://elizabethtai.com/\">@elizabethtai.com</a> (<a class=\"auto-link\" href=\"https://hachyderm.io/@liztai\">@[email protected]</a> <a class=\"auto-link h-cassis-username\" href=\"https://twitter.com/liztai\">@liztai</a>) Welcome and good luck with shifting to your domain name!<br class=\"auto-break\"><br class=\"auto-break\">By “post 1 post a day in the #<span class=\"p-category auto-tag\">Indieweb</span> way” it sounds like you’ve started a 100 days of blogging project (which is great!) rather than posting about IndieWeb topics in particular.<br class=\"auto-break\"><br class=\"auto-break\">Also great if you do plan to specifically write about your #<span class=\"p-category auto-tag\">IndieWeb</span> adventures (that’s more the intent of #<span class=\"p-category auto-tag\">100DaysOfIndieWeb</span>), like choosing/setting up your domain, your personal publishing flow, how you are publishing on your own site and distributing your posts on Mastodon etc.<br class=\"auto-break\"><br class=\"auto-break\">Whichever you choose, use your primary domain <a class=\"auto-link\" href=\"https://elizabethtai.com/\">@elizabethtai.com</a> to sign-in to the IndieWeb wiki and add yourself to the respective subsection here:<br class=\"auto-break\"><br class=\"auto-break\"><a class=\"auto-link\" href=\"https://indieweb.org/100_days#2023\">https://indieweb.org/100_days#2023</a>",
                    "value": "@elizabethtai.com (@[email protected] @liztai) Welcome and good luck with shifting to your domain name!By “post 1 post a day in the #Indieweb way” it sounds like you’ve started a 100 days of blogging project (which is great!) rather than posting about IndieWeb topics in particular.Also great if you do plan to specifically write about your #IndieWeb adventures (that’s more the intent of #100DaysOfIndieWeb), like choosing/setting up your domain, your personal publishing flow, how you are publishing on your own site and distributing your posts on Mastodon etc.Whichever you choose, use your primary domain @elizabethtai.com to sign-in to the IndieWeb wiki and add yourself to the respective subsection here:https://indieweb.org/100_days#2023"
                  }
                ],
                "category": [
                  "Indieweb",
                  "IndieWeb",
                  "100DaysOfIndieWeb"
                ],
                "published": [
                  "15:19 on 2023-01-23"
                ],
                "updated": [
                  "15:19 on 2023-01-23"
                ],
                "url": [
                  "https://tantek.com/2023/023/t1/"
                ],
                "uid": [
                  "https://tantek.com/2023/023/t1/"
                ]
              },
              "children": [
                {
                  "type": [
                    "h-cassis-username"
                  ],
                  "properties": {
                    "name": [
                      "@liztai"
                    ],
                    "url": [
                      "https://twitter.com/liztai"
                    ]
                  }
                }
              ]
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "3 weeks since the 1st, since asking you to own your notes^1Still tweeting in Big Chad’s garage or tooting in little Chad’s garage next door?^2 What’s the delay?Choosing a domain name?^3Or a service or other path?^4Or #TwitterMigration to #Mastodon?Two #IndieWeb alternatives to owning your notes (https://micro.blog/ or https://fed.brid.gy/, either with your own domain) both support migrating your followers from Mastodon.For example, I migrated my experimental @[email protected] Mastodon account to my own site^5, @tantek.com, thanks to the migration support in Bridgy Fed.If you’re not sure where you’d like to migrate, you can try https://micro.blog/ for 30 days to see if it works for you.If you’re a #webDev or otherwise like to tinker, it’s well worth the time to setup your own website with an SSG or CMS^6 or your own code, and grow it incrementally as you post and have time to do so.Either way, drop by https://chat.indieweb.org/ and ask any questions you have. There’s a whole community that wants you to succeed, that wants to help you own your notes.This is day 21 of #100DaysOfIndieWeb #100Days, written the night after. ← Day 20: https://tantek.com/2023/022/t1/indieweb-eat-what-you-cook→ Day 22: https://tantek.com/2023/026/t1/indieweb-priorities-balance^1 https://tantek.com/2023/001/t1/own-your-notes^2 https://xkcd.com/1150/^3 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb^4 https://tantek.com/2023/003/t1/indieweb-path-chosen-why^5 https://tantek.com/2022/358/t3/^6 https://indieweb.org/CMS"
                ],
                "content": [
                  {
                    "html": "3 weeks since the 1st, since asking you to own your notes^1<br class=\"auto-break\"><br class=\"auto-break\">Still tweeting in Big Chad’s garage or tooting in little Chad’s garage next door?^2 What’s the delay?<br class=\"auto-break\"><br class=\"auto-break\">Choosing a domain name?^3<br class=\"auto-break\">Or a service or other path?^4<br class=\"auto-break\">Or #<span class=\"p-category auto-tag\">TwitterMigration</span> to #<span class=\"p-category auto-tag\">Mastodon</span>?<br class=\"auto-break\"><br class=\"auto-break\">Two #<span class=\"p-category auto-tag\">IndieWeb</span> alternatives to owning your notes (<a class=\"auto-link\" href=\"https://micro.blog/\">https://micro.blog/</a> or <a class=\"auto-link\" href=\"https://fed.brid.gy/\">https://fed.brid.gy/</a>, either with your own domain) both support migrating your followers from Mastodon.<br class=\"auto-break\"><br class=\"auto-break\">For example, I migrated my experimental <a class=\"auto-link\" href=\"https://xoxo.zone/@t\">@[email protected]</a> Mastodon account to my own site^5, <a class=\"auto-link\" href=\"https://tantek.com/\">@tantek.com</a>, thanks to the migration support in Bridgy Fed.<br class=\"auto-break\"><br class=\"auto-break\">If you’re not sure where you’d like to migrate, you can try <a class=\"auto-link\" href=\"https://micro.blog/\">https://micro.blog/</a> for 30 days to see if it works for you.<br class=\"auto-break\"><br class=\"auto-break\">If you’re a #<span class=\"p-category auto-tag\">webDev</span> or otherwise like to tinker, it’s well worth the time to setup your own website with an SSG or CMS^6 or your own code, and grow it incrementally as you post and have time to do so.<br class=\"auto-break\"><br class=\"auto-break\">Either way, drop by <a class=\"auto-link\" href=\"https://chat.indieweb.org/\">https://chat.indieweb.org/</a> and ask any questions you have. <br class=\"auto-break\"><br class=\"auto-break\">There’s a whole community that wants you to succeed, that wants to help you own your notes.<br class=\"auto-break\"><br class=\"auto-break\"><br class=\"auto-break\">This is day 21 of #<span class=\"p-category auto-tag\">100DaysOfIndieWeb</span> #<span class=\"p-category auto-tag\">100Days</span>, written the night after. <br class=\"auto-break\"><br class=\"auto-break\">← Day 20: <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\">→ Day 22: <a class=\"auto-link\" href=\"https://tantek.com/2023/026/t1/indieweb-priorities-balance\">https://tantek.com/2023/026/t1/indieweb-priorities-balance</a><br class=\"auto-break\"><br class=\"auto-break\"><br class=\"auto-break\">^1 <a class=\"auto-link\" href=\"https://tantek.com/2023/001/t1/own-your-notes\">https://tantek.com/2023/001/t1/own-your-notes</a><br class=\"auto-break\">^2 <a class=\"auto-link\" href=\"https://xkcd.com/1150/\">https://xkcd.com/1150/</a><br class=\"auto-break\">^3 <a class=\"auto-link\" href=\"https://tantek.com/2023/004/t1/choosing-domain-name-indieweb\">https://tantek.com/2023/004/t1/choosing-domain-name-indieweb</a><br class=\"auto-break\">^4 <a class=\"auto-link\" href=\"https://tantek.com/2023/003/t1/indieweb-path-chosen-why\">https://tantek.com/2023/003/t1/indieweb-path-chosen-why</a><br class=\"auto-break\">^5 <a class=\"auto-link\" href=\"https://tantek.com/2022/358/t3/\">https://tantek.com/2022/358/t3/</a><br class=\"auto-break\">^6 <a class=\"auto-link\" href=\"https://indieweb.org/CMS\">https://indieweb.org/CMS</a>",
                    "value": "3 weeks since the 1st, since asking you to own your notes^1Still tweeting in Big Chad’s garage or tooting in little Chad’s garage next door?^2 What’s the delay?Choosing a domain name?^3Or a service or other path?^4Or #TwitterMigration to #Mastodon?Two #IndieWeb alternatives to owning your notes (https://micro.blog/ or https://fed.brid.gy/, either with your own domain) both support migrating your followers from Mastodon.For example, I migrated my experimental @[email protected] Mastodon account to my own site^5, @tantek.com, thanks to the migration support in Bridgy Fed.If you’re not sure where you’d like to migrate, you can try https://micro.blog/ for 30 days to see if it works for you.If you’re a #webDev or otherwise like to tinker, it’s well worth the time to setup your own website with an SSG or CMS^6 or your own code, and grow it incrementally as you post and have time to do so.Either way, drop by https://chat.indieweb.org/ and ask any questions you have. There’s a whole community that wants you to succeed, that wants to help you own your notes.This is day 21 of #100DaysOfIndieWeb #100Days, written the night after. ← Day 20: https://tantek.com/2023/022/t1/indieweb-eat-what-you-cook→ Day 22: https://tantek.com/2023/026/t1/indieweb-priorities-balance^1 https://tantek.com/2023/001/t1/own-your-notes^2 https://xkcd.com/1150/^3 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb^4 https://tantek.com/2023/003/t1/indieweb-path-chosen-why^5 https://tantek.com/2022/358/t3/^6 https://indieweb.org/CMS"
                  }
                ],
                "category": [
                  "TwitterMigration",
                  "Mastodon",
                  "IndieWeb",
                  "webDev",
                  "100DaysOfIndieWeb",
                  "100Days"
                ],
                "published": [
                  "23:49 on 2023-01-22"
                ],
                "updated": [
                  "23:49 on 2023-01-22"
                ],
                "url": [
                  "https://tantek.com/2023/022/t2/own-your-notes-domain-migration"
                ],
                "uid": [
                  "https://tantek.com/2023/022/t2/own-your-notes-domain-migration"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "One of our #IndieWeb principles is Use What You Make^1.  Photo of basil, tomatoes, uncooked spaghetti on a rustic table with white text on top: Slow Social. Try eating what you cook on your own website. Rely less on the unhealthy fast food of corporate social media. We use the metaphor Eat What You Cook^2 to more broadly relate to creators^3 of all kinds, the chefs & cooks of the IndieWeb.Cooks often taste their dishes while cooking, and modify them accordingly. Some even prepare entire dishes or meals to try themselves first, before preparing them for others.On the IndieWeb, some of us do the same by first testing our own code changes in production^4 on our personal sites, before publishing them more widely. Sometimes we let our changes simmer on our own sites for a while, before serving our code for others to consume.I myself have been most recently testing in production my at-mention auto-linking updates^5 on my site for over a week now. They seem to be working well, and I haven’t noticed any errors or regressions, so I’ll likely roll at least some of those changes into the CASSIS GitHub repo soon.While testing in production may be a reasonable & good practice for personal sites, it’s often a bad idea for corporate or critical web sites or services, and there’s no shortage of such examples.I have been wanting to write about our IndieWeb “test in production” practices for a while, and finally created a separate page on the IndieWeb wiki accordingly^4, organizing content from other pages, and adding examples beyond the IndieWeb as well.Do you write code for your website that you test there in production before sharing it more broadly on GitHub etc.? Add yourself to the examples section^6Thanks to Chris Aldrich (https://boffosocko.com/) for the eating what you cook banner image.This is day 20 of #100DaysOfIndieWeb #100Days, written two days after. I have some double days ahead of me.← Day 19: https://tantek.com/2023/020/t2/bridgy-fed-follow-form→ Day 21: https://tantek.com/2023/022/t2/own-your-notes-domain-migration^1 https://indieweb.org/use_what_you_make^2 https://indieweb.org/eat_what_you_cook, much more palatable than prior \"selfdogfood\" or \"dogfood\" metaphors from other open source related communities.^3 https://indieweb.org/creator^4 https://indieweb.org/test_in_production^5 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention^6 https://indieweb.org/test_in_production#IndieWeb_Examples"
                ],
                "content": [
                  {
                    "html": "One of our #<span class=\"p-category auto-tag\">IndieWeb</span> principles is Use What You Make^1. <a class=\"auto-link figure\" href=\"https://indieweb.org/eat_what_you_cook\"><img class=\"auto-embed u-photo\" alt=\"Photo of basil, tomatoes, uncooked spaghetti on a rustic table with white text on top: Slow Social. Try eating what you cook on your own website. Rely less on the unhealthy fast food of corporate social media.\" src=\"https://indieweb.org/images/8/8e/slow-social.png\"></a>We use the metaphor Eat What You Cook^2 to more broadly relate to creators^3 of all kinds, the chefs &amp; cooks of the IndieWeb.<br class=\"auto-break\"><br class=\"auto-break\">Cooks often taste their dishes while cooking, and modify them accordingly. Some even prepare entire dishes or meals to try themselves first, before preparing them for others.<br class=\"auto-break\"><br class=\"auto-break\">On the IndieWeb, some of us do the same by first testing our own code changes in production^4 on our personal sites, before publishing them more widely. Sometimes we let our changes simmer on our own sites for a while, before serving our code for others to consume.<br class=\"auto-break\"><br class=\"auto-break\">I myself have been most recently testing in production my at-mention auto-linking updates^5 on my site for over a week now. They seem to be working well, and I haven’t noticed any errors or regressions, so I’ll likely roll at least some of those changes into the CASSIS GitHub repo soon.<br class=\"auto-break\"><br class=\"auto-break\">While testing in production may be a reasonable &amp; good practice for personal sites, it’s often a bad idea for corporate or critical web sites or services, and there’s no shortage of such examples.<br class=\"auto-break\"><br class=\"auto-break\">I have been wanting to write about our IndieWeb “test in production” practices for a while, and finally created a separate page on the IndieWeb wiki accordingly^4, organizing content from other pages, and adding examples beyond the IndieWeb as well.<br class=\"auto-break\"><br class=\"auto-break\">Do you write code for your website that you test there in production before sharing it more broadly on GitHub etc.? Add yourself to the examples section^6<br class=\"auto-break\"><br class=\"auto-break\">Thanks to Chris Aldrich (<a class=\"auto-link\" href=\"https://boffosocko.com/\">https://boffosocko.com/</a>) for the eating what you cook banner image.<br class=\"auto-break\"><br class=\"auto-break\">This is day 20 of #<span class=\"p-category auto-tag\">100DaysOfIndieWeb</span> #<span class=\"p-category auto-tag\">100Days</span>, written two days after. I have some double days ahead of me.<br class=\"auto-break\"><br class=\"auto-break\">← Day 19: <a class=\"auto-link\" href=\"https://tantek.com/2023/020/t2/bridgy-fed-follow-form\">https://tantek.com/2023/020/t2/bridgy-fed-follow-form</a><br class=\"auto-break\">→ Day 21: <a class=\"auto-link\" href=\"https://tantek.com/2023/022/t2/own-your-notes-domain-migration\">https://tantek.com/2023/022/t2/own-your-notes-domain-migration</a><br class=\"auto-break\"><br class=\"auto-break\"><br class=\"auto-break\">^1 <a class=\"auto-link\" href=\"https://indieweb.org/use_what_you_make\">https://indieweb.org/use_what_you_make</a><br class=\"auto-break\">^2 <a class=\"auto-link\" href=\"https://indieweb.org/eat_what_you_cook\">https://indieweb.org/eat_what_you_cook</a>, much more palatable than prior \"selfdogfood\" or \"dogfood\" metaphors from other open source related communities.<br class=\"auto-break\">^3 <a class=\"auto-link\" href=\"https://indieweb.org/creator\">https://indieweb.org/creator</a><br class=\"auto-break\">^4 <a class=\"auto-link\" href=\"https://indieweb.org/test_in_production\">https://indieweb.org/test_in_production</a><br class=\"auto-break\">^5 <a class=\"auto-link\" href=\"https://tantek.com/2023/011/t1/indieweb-evolving-at-mention\">https://tantek.com/2023/011/t1/indieweb-evolving-at-mention</a><br class=\"auto-break\">^6 <a class=\"auto-link\" href=\"https://indieweb.org/test_in_production#IndieWeb_Examples\">https://indieweb.org/test_in_production#IndieWeb_Examples</a>",
                    "value": "One of our #IndieWeb principles is Use What You Make^1.  Photo of basil, tomatoes, uncooked spaghetti on a rustic table with white text on top: Slow Social. Try eating what you cook on your own website. Rely less on the unhealthy fast food of corporate social media. We use the metaphor Eat What You Cook^2 to more broadly relate to creators^3 of all kinds, the chefs & cooks of the IndieWeb.Cooks often taste their dishes while cooking, and modify them accordingly. Some even prepare entire dishes or meals to try themselves first, before preparing them for others.On the IndieWeb, some of us do the same by first testing our own code changes in production^4 on our personal sites, before publishing them more widely. Sometimes we let our changes simmer on our own sites for a while, before serving our code for others to consume.I myself have been most recently testing in production my at-mention auto-linking updates^5 on my site for over a week now. They seem to be working well, and I haven’t noticed any errors or regressions, so I’ll likely roll at least some of those changes into the CASSIS GitHub repo soon.While testing in production may be a reasonable & good practice for personal sites, it’s often a bad idea for corporate or critical web sites or services, and there’s no shortage of such examples.I have been wanting to write about our IndieWeb “test in production” practices for a while, and finally created a separate page on the IndieWeb wiki accordingly^4, organizing content from other pages, and adding examples beyond the IndieWeb as well.Do you write code for your website that you test there in production before sharing it more broadly on GitHub etc.? Add yourself to the examples section^6Thanks to Chris Aldrich (https://boffosocko.com/) for the eating what you cook banner image.This is day 20 of #100DaysOfIndieWeb #100Days, written two days after. I have some double days ahead of me.← Day 19: https://tantek.com/2023/020/t2/bridgy-fed-follow-form→ Day 21: https://tantek.com/2023/022/t2/own-your-notes-domain-migration^1 https://indieweb.org/use_what_you_make^2 https://indieweb.org/eat_what_you_cook, much more palatable than prior \"selfdogfood\" or \"dogfood\" metaphors from other open source related communities.^3 https://indieweb.org/creator^4 https://indieweb.org/test_in_production^5 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention^6 https://indieweb.org/test_in_production#IndieWeb_Examples"
                  }
                ],
                "category": [
                  "IndieWeb",
                  "100DaysOfIndieWeb",
                  "100Days"
                ],
                "photo": [
                  {
                    "value": "https://indieweb.org/images/8/8e/slow-social.png",
                    "alt": "Photo of basil, tomatoes, uncooked spaghetti on a rustic table with white text on top: Slow Social. Try eating what you cook on your own website. Rely less on the unhealthy fast food of corporate social media."
                  }
                ],
                "published": [
                  "16:11 on 2023-01-22"
                ],
                "updated": [
                  "16:11 on 2023-01-22"
                ],
                "url": [
                  "https://tantek.com/2023/022/t1/indieweb-eat-what-you-cook"
                ],
                "uid": [
                  "https://tantek.com/2023/022/t1/indieweb-eat-what-you-cook"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "When you setup your site with Bridgy Fed^1, it creates a dashboard with a form for others to follow you site. E.g. mine: https://fed.brid.gy/user/tantek.comCopying that Follow form to your site sets up cross-instance following directly from your #IndieWeb site!Starting with the Follow form markup on the dashboard, copy it and make any necessary changes for its HTML & CSS to fit in with your own, e.g.<form method=\"post\" action=\"https://fed.brid.gy/remote-follow\"> <label for=\"follow-address\">🐘 Follow   <kbd>@[email protected]</kbd>:<br />   enter your @[email protected] fediverse address:</label> <input id=\"follow-address\" name=\"address\" type=\"text\" required=\"required\"        placeholder=\"@[email protected]\" alt=\"fediverse address\" value=\"\" /> <input name=\"domain\" type=\"hidden\" value=\"tantek.com\" /> <button type=\"submit\">Follow</button></form>After adding the Follow form to my site, I added more instructions and screenshots to the IndieWeb wiki to hopefuly enable more developers to setup Follow buttons:* https://indieweb.org/Bridgy_Fed#How_to_add_a_follow_formSee that section for a sample rendering of the form, and what happens when someone else clicks the Follow button on your site while they’re logged into a Mastodon instance.They get prompted to FOLLOW you, and when they click that button, they get a follow confirmation.A functioning cross-instance “Follow” button is one step closer to a universal cross-site “Follow button”.This is day 19 of #100DaysOfIndieWeb #100Days, written the night after.← Day 18: https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo→ Day 20: https://tantek.com/2023/022/t1/indieweb-eat-what-you-cook^1 https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed"
                ],
                "content": [
                  {
                    "html": "When you setup your site with Bridgy Fed^1, it creates a dashboard with a form for others to follow you site. E.g. mine: <a class=\"auto-link\" href=\"https://fed.brid.gy/user/tantek.com\">https://fed.brid.gy/user/tantek.com</a><br class=\"auto-break\"><br class=\"auto-break\">Copying that Follow form to your site sets up cross-instance following directly from your #<span class=\"p-category auto-tag\">IndieWeb</span> site!<br class=\"auto-break\"><br class=\"auto-break\">Starting with the Follow form markup on the dashboard, copy it and make any necessary changes for its HTML &amp; CSS to fit in with your own, e.g.<br class=\"auto-break\"><br class=\"auto-break\">&lt;form method=\"post\" action=\"https://fed.brid.gy/remote-follow\"&gt;<br class=\"auto-break\"> &lt;label for=\"follow-address\"&gt;🐘 Follow <br class=\"auto-break\">  &lt;kbd&gt;@[email protected]&lt;/kbd&gt;:&lt;br /&gt; <br class=\"auto-break\">  enter your @[email protected] fediverse address:&lt;/label&gt;<br class=\"auto-break\"> &lt;input id=\"follow-address\" name=\"address\" type=\"text\" required=\"required\"<br class=\"auto-break\">        placeholder=\"@[email protected]\" alt=\"fediverse address\" value=\"\" /&gt;<br class=\"auto-break\"> &lt;input name=\"domain\" type=\"hidden\" value=\"tantek.com\" /&gt;<br class=\"auto-break\"> &lt;button type=\"submit\"&gt;Follow&lt;/button&gt;<br class=\"auto-break\">&lt;/form&gt;<br class=\"auto-break\"><br class=\"auto-break\">After adding the Follow form to my site, I added more instructions and screenshots to the IndieWeb wiki to hopefuly enable more developers to setup Follow buttons:<br class=\"auto-break\">* <a class=\"auto-link\" href=\"https://indieweb.org/Bridgy_Fed#How_to_add_a_follow_form\">https://indieweb.org/Bridgy_Fed#How_to_add_a_follow_form</a><br class=\"auto-break\"><br class=\"auto-break\">See that section for a sample rendering of the form, and what happens when someone else clicks the Follow button on your site while they’re logged into a Mastodon instance.<br class=\"auto-break\"><br class=\"auto-break\">They get prompted to FOLLOW you, and when they click that button, they get a follow confirmation.<br class=\"auto-break\"><br class=\"auto-break\">A functioning cross-instance “Follow” button is one step closer to a universal cross-site “Follow button”.<br class=\"auto-break\"><br class=\"auto-break\"><br class=\"auto-break\">This is day 19 of #<span class=\"p-category auto-tag\">100DaysOfIndieWeb</span> #<span class=\"p-category auto-tag\">100Days</span>, written the night after.<br class=\"auto-break\"><br class=\"auto-break\">← Day 18: <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\">→ Day 20: <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\"><br class=\"auto-break\"><br class=\"auto-break\">^1 <a class=\"auto-link\" href=\"https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed\">https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed</a>",
                    "value": "When you setup your site with Bridgy Fed^1, it creates a dashboard with a form for others to follow you site. E.g. mine: https://fed.brid.gy/user/tantek.comCopying that Follow form to your site sets up cross-instance following directly from your #IndieWeb site!Starting with the Follow form markup on the dashboard, copy it and make any necessary changes for its HTML & CSS to fit in with your own, e.g.<form method=\"post\" action=\"https://fed.brid.gy/remote-follow\"> <label for=\"follow-address\">🐘 Follow   <kbd>@[email protected]</kbd>:<br />   enter your @[email protected] fediverse address:</label> <input id=\"follow-address\" name=\"address\" type=\"text\" required=\"required\"        placeholder=\"@[email protected]\" alt=\"fediverse address\" value=\"\" /> <input name=\"domain\" type=\"hidden\" value=\"tantek.com\" /> <button type=\"submit\">Follow</button></form>After adding the Follow form to my site, I added more instructions and screenshots to the IndieWeb wiki to hopefuly enable more developers to setup Follow buttons:* https://indieweb.org/Bridgy_Fed#How_to_add_a_follow_formSee that section for a sample rendering of the form, and what happens when someone else clicks the Follow button on your site while they’re logged into a Mastodon instance.They get prompted to FOLLOW you, and when they click that button, they get a follow confirmation.A functioning cross-instance “Follow” button is one step closer to a universal cross-site “Follow button”.This is day 19 of #100DaysOfIndieWeb #100Days, written the night after.← Day 18: https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo→ Day 20: https://tantek.com/2023/022/t1/indieweb-eat-what-you-cook^1 https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed"
                  }
                ],
                "category": [
                  "IndieWeb",
                  "100DaysOfIndieWeb",
                  "100Days"
                ],
                "published": [
                  "23:54 on 2023-01-20"
                ],
                "updated": [
                  "23:54 on 2023-01-20"
                ],
                "url": [
                  "https://tantek.com/2023/020/t2/bridgy-fed-follow-form"
                ],
                "uid": [
                  "https://tantek.com/2023/020/t2/bridgy-fed-follow-form"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "in-reply-to": [
                  {
                    "type": [
                      "h-cite"
                    ],
                    "properties": {
                      "name": [
                        "hachyderm.io user liztai’s post"
                      ],
                      "url": [
                        "https://hachyderm.io/@liztai/109724842728667366"
                      ]
                    },
                    "value": "https://hachyderm.io/@liztai/109724842728667366"
                  }
                ],
                "name": [
                  "@elizabethtai.com (@[email protected]) Thanks! It took us a while to come up with #POSSE too! Both the concept and name.Roughly conceptually described in a 2010-05-26 interview^1: 1. Publish on your own site, own your URLs, your permalinks, and 2. Syndicate out to other sites. Your text updates to Twitter, your checkins to Foursquare, your photos to Flickr etc.A few months later in a whiteboard architecture diagram^2.Then *two years* after that @willnorris.com (@[email protected]) and I finally came up with the name/acronym POSSE!^3^1 https://web.archive.org/web/20130312135439/http://www.monkinetic.com/2010/05/26/tantek-celik-diso-20-brass-tacks^2 https://www.flickr.com/photos/tantek/5301870765/^3 http://tantek.com/2012/173/t1/posse-core-indieweb-approach"
                ],
                "content": [
                  {
                    "html": "<a class=\"auto-link\" href=\"https://elizabethtai.com/\">@elizabethtai.com</a> (<a class=\"auto-link\" href=\"https://hachyderm.io/@liztai\">@[email protected]</a>) Thanks! It took us a while to come up with #<span class=\"p-category auto-tag\">POSSE</span> too! Both the concept and name.<br class=\"auto-break\"><br class=\"auto-break\">Roughly conceptually described in a 2010-05-26 interview^1:<br class=\"auto-break\"><br class=\"auto-break\"> 1. Publish on your own site, own your URLs, your permalinks, and<br class=\"auto-break\"> 2. Syndicate out to other sites. Your text updates to Twitter, your checkins to Foursquare, your photos to Flickr etc.<br class=\"auto-break\"><br class=\"auto-break\">A few months later in a whiteboard architecture diagram^2.<br class=\"auto-break\"><br class=\"auto-break\">Then *two years* after that <a class=\"auto-link\" href=\"https://willnorris.com/\">@willnorris.com</a> (<a class=\"auto-link\" href=\"https://willnorris.com/@will\">@[email protected]</a>) and I finally came up with the name/acronym POSSE!^3<br class=\"auto-break\"><br class=\"auto-break\">^1 <a class=\"auto-link\" href=\"https://web.archive.org/web/20130312135439/http://www.monkinetic.com/2010/05/26/tantek-celik-diso-20-brass-tacks\">https://web.archive.org/web/20130312135439/http://www.monkinetic.com/2010/05/26/tantek-celik-diso-20-brass-tacks</a><br class=\"auto-break\">^2 <a class=\"auto-link\" href=\"https://www.flickr.com/photos/tantek/5301870765/\">https://www.flickr.com/photos/tantek/5301870765/</a><br class=\"auto-break\">^3 <a class=\"auto-link\" href=\"http://tantek.com/2012/173/t1/posse-core-indieweb-approach\">http://tantek.com/2012/173/t1/posse-core-indieweb-approach</a>",
                    "value": "@elizabethtai.com (@[email protected]) Thanks! It took us a while to come up with #POSSE too! Both the concept and name.Roughly conceptually described in a 2010-05-26 interview^1: 1. Publish on your own site, own your URLs, your permalinks, and 2. Syndicate out to other sites. Your text updates to Twitter, your checkins to Foursquare, your photos to Flickr etc.A few months later in a whiteboard architecture diagram^2.Then *two years* after that @willnorris.com (@[email protected]) and I finally came up with the name/acronym POSSE!^3^1 https://web.archive.org/web/20130312135439/http://www.monkinetic.com/2010/05/26/tantek-celik-diso-20-brass-tacks^2 https://www.flickr.com/photos/tantek/5301870765/^3 http://tantek.com/2012/173/t1/posse-core-indieweb-approach"
                  }
                ],
                "category": [
                  "POSSE"
                ],
                "published": [
                  "23:30 on 2023-01-20"
                ],
                "updated": [
                  "23:30 on 2023-01-20"
                ],
                "url": [
                  "https://tantek.com/2023/020/t1/"
                ],
                "uid": [
                  "https://tantek.com/2023/020/t1/"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "Instead of posting on a personal #IndieWeb site (& POSSE copies), some post primarily to a #fediverse instance and syndicate to Twitter, or vice-versa. How to reply^1 to such posts, e.g.:Reply to a toot (& POSSE tweet): https://tantek.com/2023/019/t4* @[email protected] (Twitter @-name)This is a variant of case (2) in https://tantek.com/2023/018/t1/elevate-indieweb-above-silo.We can update the directive and two questions & answers in that prior post accordingly:* Elevate #IndieWeb domains above @[email protected] addresses, and those above any silo identities1. Do they have an #IndieWeb domain? Then @-domain mention them^2, like you are speaking to them at their domain identity. This will notify them there, or at least reinforce their domain’s importance.2. Was their post only published on a #fediverse instance (and/or silo), or was it POSSEd to a fediverse instance (and/or silo) and do you plan to federate (and/or POSSE) your reply^3?Then use their @[email protected] address or silo @-name, or @[email protected] (silo @-name) for both, or (@[email protected], silo @-name) parenthetically following their @-domain if (1). This will notify them on that instance (or silo), and may help thread your POSSE reply.When posting a reply, you (or your CMS automatically) should explicitly link with u-in-reply-to markup^4 to the post your are replying to, and any of its syndicated copy permalinks on destinations you plan to POSSE your reply (see also multi-reply^5). This is day 18 of #100DaysOfIndieWeb #100Days, written the day after.← Day 17: https://tantek.com/2023/018/t1/elevate-indieweb-above-silo→ Day 19: https://tantek.com/2023/020/t2/bridgy-fed-follow-form^1 https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post^2 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention^3 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute^4 https://indieweb.org/in-reply-to^5 https://indieweb.org/multiple-reply"
                ],
                "content": [
                  {
                    "html": "Instead of posting on a personal #<span class=\"p-category auto-tag\">IndieWeb</span> site (&amp; POSSE copies), some post primarily to a #<span class=\"p-category auto-tag\">fediverse</span> instance and syndicate to Twitter, or vice-versa. How to reply^1 to such posts, e.g.:<br class=\"auto-break\"><br class=\"auto-break\">Reply to a toot (&amp; POSSE tweet): <a class=\"auto-link\" href=\"https://tantek.com/2023/019/t4\">https://tantek.com/2023/019/t4</a><br class=\"auto-break\">* @[email protected] (Twitter @-name)<br class=\"auto-break\"><br class=\"auto-break\">This is a variant of case (2) in <a class=\"auto-link\" href=\"https://tantek.com/2023/018/t1/elevate-indieweb-above-silo\">https://tantek.com/2023/018/t1/elevate-indieweb-above-silo</a>.<br class=\"auto-break\"><br class=\"auto-break\">We can update the directive and two questions &amp; answers in that prior post accordingly:<br class=\"auto-break\"><br class=\"auto-break\">* Elevate #<span class=\"p-category auto-tag\">IndieWeb</span> domains above @[email protected] addresses, and those above any silo identities<br class=\"auto-break\"><br class=\"auto-break\">1. Do they have an #<span class=\"p-category auto-tag\">IndieWeb</span> domain? Then @-domain mention them^2, like you are speaking to them at their domain identity. This will notify them there, or at least reinforce their domain’s importance.<br class=\"auto-break\"><br class=\"auto-break\">2. Was their post only published on a #<span class=\"p-category auto-tag\">fediverse</span> instance (and/or silo), or was it POSSEd to a fediverse instance (and/or silo) and do you plan to federate (and/or POSSE) your reply^3?<br class=\"auto-break\">Then use their @[email protected] address or silo @-name, or @[email protected] (silo @-name) for both, or (@[email protected], silo @-name) parenthetically following their @-domain if (1). This will notify them on that instance (or silo), and may help thread your POSSE reply.<br class=\"auto-break\"><br class=\"auto-break\">When posting a reply, you (or your CMS automatically) should explicitly link with u-in-reply-to markup^4 to the post your are replying to, and any of its syndicated copy permalinks on destinations you plan to POSSE your reply (see also multi-reply^5).<br class=\"auto-break\"> <br class=\"auto-break\"><br class=\"auto-break\">This is day 18 of #<span class=\"p-category auto-tag\">100DaysOfIndieWeb</span> #<span class=\"p-category auto-tag\">100Days</span>, written the day after.<br class=\"auto-break\"><br class=\"auto-break\">← Day 17: <a class=\"auto-link\" href=\"https://tantek.com/2023/018/t1/elevate-indieweb-above-silo\">https://tantek.com/2023/018/t1/elevate-indieweb-above-silo</a><br class=\"auto-break\">→ Day 19: <a class=\"auto-link\" href=\"https://tantek.com/2023/020/t2/bridgy-fed-follow-form\">https://tantek.com/2023/020/t2/bridgy-fed-follow-form</a><br class=\"auto-break\"><br class=\"auto-break\"><br class=\"auto-break\">^1 <a class=\"auto-link\" href=\"https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post\">https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post</a><br class=\"auto-break\">^2 <a class=\"auto-link\" href=\"https://tantek.com/2023/011/t1/indieweb-evolving-at-mention\">https://tantek.com/2023/011/t1/indieweb-evolving-at-mention</a><br class=\"auto-break\">^3 <a class=\"auto-link\" href=\"https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute\">https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute</a><br class=\"auto-break\">^4 <a class=\"auto-link\" href=\"https://indieweb.org/in-reply-to\">https://indieweb.org/in-reply-to</a><br class=\"auto-break\">^5 <a class=\"auto-link\" href=\"https://indieweb.org/multiple-reply\">https://indieweb.org/multiple-reply</a>",
                    "value": "Instead of posting on a personal #IndieWeb site (& POSSE copies), some post primarily to a #fediverse instance and syndicate to Twitter, or vice-versa. How to reply^1 to such posts, e.g.:Reply to a toot (& POSSE tweet): https://tantek.com/2023/019/t4* @[email protected] (Twitter @-name)This is a variant of case (2) in https://tantek.com/2023/018/t1/elevate-indieweb-above-silo.We can update the directive and two questions & answers in that prior post accordingly:* Elevate #IndieWeb domains above @[email protected] addresses, and those above any silo identities1. Do they have an #IndieWeb domain? Then @-domain mention them^2, like you are speaking to them at their domain identity. This will notify them there, or at least reinforce their domain’s importance.2. Was their post only published on a #fediverse instance (and/or silo), or was it POSSEd to a fediverse instance (and/or silo) and do you plan to federate (and/or POSSE) your reply^3?Then use their @[email protected] address or silo @-name, or @[email protected] (silo @-name) for both, or (@[email protected], silo @-name) parenthetically following their @-domain if (1). This will notify them on that instance (or silo), and may help thread your POSSE reply.When posting a reply, you (or your CMS automatically) should explicitly link with u-in-reply-to markup^4 to the post your are replying to, and any of its syndicated copy permalinks on destinations you plan to POSSE your reply (see also multi-reply^5). This is day 18 of #100DaysOfIndieWeb #100Days, written the day after.← Day 17: https://tantek.com/2023/018/t1/elevate-indieweb-above-silo→ Day 19: https://tantek.com/2023/020/t2/bridgy-fed-follow-form^1 https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post^2 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention^3 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute^4 https://indieweb.org/in-reply-to^5 https://indieweb.org/multiple-reply"
                  }
                ],
                "category": [
                  "IndieWeb",
                  "fediverse",
                  "IndieWeb",
                  "IndieWeb",
                  "fediverse",
                  "100DaysOfIndieWeb",
                  "100Days"
                ],
                "published": [
                  "18:05 on 2023-01-19"
                ],
                "updated": [
                  "18:05 on 2023-01-19"
                ],
                "url": [
                  "https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo"
                ],
                "uid": [
                  "https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "in-reply-to": [
                  {
                    "type": [
                      "h-cite"
                    ],
                    "properties": {
                      "name": [
                        "w3c.social user w3cdevs’s post"
                      ],
                      "url": [
                        "https://w3c.social/@w3cdevs/109705685724161500"
                      ]
                    },
                    "value": "https://w3c.social/@w3cdevs/109705685724161500"
                  }
                ],
                "name": [
                  "Thanks @[email protected] (@w3cdevs) & @[email protected], good to be back on the @W3CAB.As W3C Developers noted, we have a lot Priority Projects work to do. I have rejoined the Vision project: https://www.w3.org/wiki/AB/2023_Priorities#Vision.2FPrinciples, with gratitude to @cwilso.com (@[email protected]) for his editing & stewardship, and am looking forward to helping support his leadership & initiative on that project."
                ],
                "content": [
                  {
                    "html": "Thanks <a class=\"auto-link\" href=\"https://w3c.social/@w3cdevs\">@[email protected]</a> (<a class=\"auto-link h-cassis-username\" href=\"https://twitter.com/w3cdevs\">@w3cdevs</a>) &amp; <a class=\"auto-link\" href=\"https://w3c.social/@w3c\">@[email protected]</a>, good to be back on the <a class=\"auto-link h-cassis-username\" href=\"https://twitter.com/W3CAB\">@W3CAB</a>.<br class=\"auto-break\"><br class=\"auto-break\">As W3C Developers noted, we have a lot Priority Projects work to do. I have rejoined the Vision project: <a class=\"auto-link\" href=\"https://www.w3.org/wiki/AB/2023_Priorities#Vision.2FPrinciples\">https://www.w3.org/wiki/AB/2023_Priorities#Vision.2FPrinciples</a>, with gratitude to <a class=\"auto-link\" href=\"https://cwilso.com/\">@cwilso.com</a> (<a class=\"auto-link\" href=\"https://mastodon.social/@cdub\">@[email protected]</a>) for his editing &amp; stewardship, and am looking forward to helping support his leadership &amp; initiative on that project.",
                    "value": "Thanks @[email protected] (@w3cdevs) & @[email protected], good to be back on the @W3CAB.As W3C Developers noted, we have a lot Priority Projects work to do. I have rejoined the Vision project: https://www.w3.org/wiki/AB/2023_Priorities#Vision.2FPrinciples, with gratitude to @cwilso.com (@[email protected]) for his editing & stewardship, and am looking forward to helping support his leadership & initiative on that project."
                  }
                ],
                "published": [
                  "16:47 on 2023-01-19"
                ],
                "updated": [
                  "16:47 on 2023-01-19"
                ],
                "url": [
                  "https://tantek.com/2023/019/t4/"
                ],
                "uid": [
                  "https://tantek.com/2023/019/t4/"
                ]
              },
              "children": [
                {
                  "type": [
                    "h-cassis-username"
                  ],
                  "properties": {
                    "name": [
                      "@w3cdevs"
                    ],
                    "url": [
                      "https://twitter.com/w3cdevs"
                    ]
                  }
                },
                {
                  "type": [
                    "h-cassis-username"
                  ],
                  "properties": {
                    "name": [
                      "@W3CAB"
                    ],
                    "url": [
                      "https://twitter.com/W3CAB"
                    ]
                  }
                }
              ]
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "in-reply-to": [
                  {
                    "type": [
                      "h-cite"
                    ],
                    "properties": {
                      "name": [
                        "devdilettante.com user roland’s post"
                      ],
                      "url": [
                        "https://devdilettante.com/@roland/109711180771305151"
                      ]
                    },
                    "value": "https://devdilettante.com/@roland/109711180771305151"
                  }
                ],
                "name": [
                  "rolandtanglao.com (@[email protected]) thanks for the kind words and yes I was at W3C TPAC in Vancouver, would have been nice to chat!You’re right, neither ActivityPub, Webmention, nor h-entry for that matter have any explicit length limits.You can run “an experimental 10,000 character limit AP implementation” on your existing site rolandtanglao.com with a few webdev steps:Setup Bridgy Fed support on your site: * https://fed.brid.gy/docs#setup (SSL, /.well-known/ server redirects, homepage h-card)Add h-entry + h-card markup to your post template:* https://fed.brid.gy/docs#how-postThen send Bridgy Fed a Webmention when you publish a post.Presto, you’re running an AP implementation without a character limit!Happy to help with any of those steps. Drop by https://chat.indieweb.org/dev!"
                ],
                "content": [
                  {
                    "html": "<a class=\"auto-link\" href=\"http://rolandtanglao.com/\">rolandtanglao.com</a> (<a class=\"auto-link\" href=\"https://devdilettante.com/@roland\">@[email protected]</a>) thanks for the kind words and yes I was at W3C TPAC in Vancouver, would have been nice to chat!<br class=\"auto-break\"><br class=\"auto-break\">You’re right, neither ActivityPub, Webmention, nor h-entry for that matter have any explicit length limits.<br class=\"auto-break\"><br class=\"auto-break\">You can run “an experimental 10,000 character limit AP implementation” on your existing site <a class=\"auto-link\" href=\"http://rolandtanglao.com/\">rolandtanglao.com</a> with a few webdev steps:<br class=\"auto-break\"><br class=\"auto-break\">Setup Bridgy Fed support on your site: <br class=\"auto-break\">* <a class=\"auto-link\" href=\"https://fed.brid.gy/docs#setup\">https://fed.brid.gy/docs#setup</a> (SSL, /.well-known/ server redirects, homepage h-card)<br class=\"auto-break\"><br class=\"auto-break\">Add h-entry + h-card markup to your post template:<br class=\"auto-break\">* <a class=\"auto-link\" href=\"https://fed.brid.gy/docs#how-post\">https://fed.brid.gy/docs#how-post</a><br class=\"auto-break\"><br class=\"auto-break\">Then send Bridgy Fed a Webmention when you publish a post.<br class=\"auto-break\"><br class=\"auto-break\">Presto, you’re running an AP implementation without a character limit!<br class=\"auto-break\"><br class=\"auto-break\">Happy to help with any of those steps. Drop by <a class=\"auto-link\" href=\"https://chat.indieweb.org/dev\">https://chat.indieweb.org/dev</a>!",
                    "value": "rolandtanglao.com (@[email protected]) thanks for the kind words and yes I was at W3C TPAC in Vancouver, would have been nice to chat!You’re right, neither ActivityPub, Webmention, nor h-entry for that matter have any explicit length limits.You can run “an experimental 10,000 character limit AP implementation” on your existing site rolandtanglao.com with a few webdev steps:Setup Bridgy Fed support on your site: * https://fed.brid.gy/docs#setup (SSL, /.well-known/ server redirects, homepage h-card)Add h-entry + h-card markup to your post template:* https://fed.brid.gy/docs#how-postThen send Bridgy Fed a Webmention when you publish a post.Presto, you’re running an AP implementation without a character limit!Happy to help with any of those steps. Drop by https://chat.indieweb.org/dev!"
                  }
                ],
                "published": [
                  "15:50 on 2023-01-19"
                ],
                "updated": [
                  "15:50 on 2023-01-19"
                ],
                "url": [
                  "https://tantek.com/2023/019/t3/"
                ],
                "uid": [
                  "https://tantek.com/2023/019/t3/"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "in-reply-to": [
                  {
                    "type": [
                      "h-cite"
                    ],
                    "properties": {
                      "name": [
                        "mastodon.cloud user swart’s post"
                      ],
                      "url": [
                        "https://mastodon.cloud/@swart/109708132345593328"
                      ]
                    },
                    "value": "https://mastodon.cloud/@swart/109708132345593328"
                  }
                ],
                "name": [
                  "@[email protected] my #IndieWeb site https://tantek.com/, which runs its own software, doesn’t have any explicit length limit, nor does https://fed.brid.gy/, the service I use to federate to ActivityPub followers such as Mastodon instances.Both client & server as it were. I haven’t seen it cause any problems with other instances yet.For more about how an #IndieWeb setup works, and why, you might be interested in:* https://tantek.com/2023/005/t3/indieweb-simpler-approach"
                ],
                "content": [
                  {
                    "html": "<a class=\"auto-link\" href=\"https://mastodon.cloud/@swart\">@[email protected]</a> my #<span class=\"p-category auto-tag\">IndieWeb</span> site <a class=\"auto-link\" href=\"https://tantek.com/\">https://tantek.com/</a>, which runs its own software, doesn’t have any explicit length limit, nor does <a class=\"auto-link\" href=\"https://fed.brid.gy/\">https://fed.brid.gy/</a>, the service I use to federate to ActivityPub followers such as Mastodon instances.<br class=\"auto-break\"><br class=\"auto-break\">Both client &amp; server as it were. I haven’t seen it cause any problems with other instances yet.<br class=\"auto-break\"><br class=\"auto-break\">For more about how an #<span class=\"p-category auto-tag\">IndieWeb</span> setup works, and why, you might be interested in:<br class=\"auto-break\">* <a class=\"auto-link\" href=\"https://tantek.com/2023/005/t3/indieweb-simpler-approach\">https://tantek.com/2023/005/t3/indieweb-simpler-approach</a>",
                    "value": "@[email protected] my #IndieWeb site https://tantek.com/, which runs its own software, doesn’t have any explicit length limit, nor does https://fed.brid.gy/, the service I use to federate to ActivityPub followers such as Mastodon instances.Both client & server as it were. I haven’t seen it cause any problems with other instances yet.For more about how an #IndieWeb setup works, and why, you might be interested in:* https://tantek.com/2023/005/t3/indieweb-simpler-approach"
                  }
                ],
                "category": [
                  "IndieWeb",
                  "IndieWeb"
                ],
                "published": [
                  "15:50 on 2023-01-19"
                ],
                "updated": [
                  "15:50 on 2023-01-19"
                ],
                "url": [
                  "https://tantek.com/2023/019/t2/"
                ],
                "uid": [
                  "https://tantek.com/2023/019/t2/"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "in-reply-to": [
                  {
                    "type": [
                      "h-cite"
                    ],
                    "properties": {
                      "name": [
                        "GitHub project “bridgy”"
                      ],
                      "url": [
                        "https://github.com/snarfed/bridgy/issues"
                      ]
                    },
                    "value": "https://github.com/snarfed/bridgy/issues"
                  }
                ],
                "url": [
                  "https://tantek.com/2023/019/b1/bridgy-publish-support-gitlab",
                  "https://tantek.com/2023/019/b1/bridgy-publish-support-gitlab"
                ],
                "uid": [
                  "https://tantek.com/2023/019/b1/bridgy-publish-support-gitlab",
                  "https://tantek.com/2023/019/b1/bridgy-publish-support-gitlab"
                ],
                "name": [
                  "Bridgy Publish feature request: Support posting to GitLab sites"
                ],
                "content": [
                  {
                    "html": "<p>\nIt would be great if there was a way to post issues &amp; comments for GitLab repos, on a personal site, and have Bridgy Publish syndicate them to the actual GitLab repos.\ne.g. feature requests to Pleroma:\n</p>\n<ul>\n<li><a href=\"https://git.pleroma.social/pleroma/pleroma/-/issues\">https://git.pleroma.social/pleroma/pleroma/-/issues</a></li>\n</ul>\n<p>\nSuch as:\n</p>\n<ul>\n<li>Implement IndieAuth support (both sign-in with IndiAuth, and use of a Pleroma profile as an IndieAuth identity to sign-in elsewhere)</li>\n<li>Implement Micropub server support</li>\n<li>Implement Webmention support, sending &amp; receiving</li>\n</ul>",
                    "value": "It would be great if there was a way to post issues & comments for GitLab repos, on a personal site, and have Bridgy Publish syndicate them to the actual GitLab repos.\ne.g. feature requests to Pleroma:\n\n\nhttps://git.pleroma.social/pleroma/pleroma/-/issues\n\n\nSuch as:\n\n\nImplement IndieAuth support (both sign-in with IndiAuth, and use of a Pleroma profile as an IndieAuth identity to sign-in elsewhere)\nImplement Micropub server support\nImplement Webmention support, sending & receiving"
                  }
                ],
                "published": [
                  "14:40 on 2023-01-19"
                ],
                "updated": [
                  "14:40 on 2023-01-19"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "in-reply-to": [
                  {
                    "type": [
                      "h-cite"
                    ],
                    "properties": {
                      "name": [
                        "novakeith.net’s post"
                      ],
                      "url": [
                        "https://novakeith.net/2023/01/15/100-days-at-least-100/"
                      ]
                    },
                    "value": "https://novakeith.net/2023/01/15/100-days-at-least-100/"
                  }
                ],
                "name": [
                  "@novakeith.net (@[email protected]) welcome to #100DaysOfIndieWeb! There’s a few of us doing this:* https://indieweb.org/100_days#2023Feel free to add yourself to the ”100 Days of IndieWeb” section if you like, or to a new subhead for #AtLeast100!"
                ],
                "content": [
                  {
                    "html": "<a class=\"auto-link\" href=\"https://novakeith.net/\">@novakeith.net</a> (<a class=\"auto-link\" href=\"https://dartboard.social/@knova\">@[email protected]</a>) welcome to #<span class=\"p-category auto-tag\">100DaysOfIndieWeb</span>! <br class=\"auto-break\"><br class=\"auto-break\">There’s a few of us doing this:<br class=\"auto-break\">* <a class=\"auto-link\" href=\"https://indieweb.org/100_days#2023\">https://indieweb.org/100_days#2023</a><br class=\"auto-break\">Feel free to add yourself to the ”100 Days of IndieWeb” section if you like, or to a new subhead for #<span class=\"p-category auto-tag\">AtLeast100</span>!",
                    "value": "@novakeith.net (@[email protected]) welcome to #100DaysOfIndieWeb! There’s a few of us doing this:* https://indieweb.org/100_days#2023Feel free to add yourself to the ”100 Days of IndieWeb” section if you like, or to a new subhead for #AtLeast100!"
                  }
                ],
                "category": [
                  "100DaysOfIndieWeb",
                  "AtLeast100"
                ],
                "published": [
                  "13:37 on 2023-01-19"
                ],
                "updated": [
                  "13:37 on 2023-01-19"
                ],
                "url": [
                  "https://tantek.com/2023/019/t1/"
                ],
                "uid": [
                  "https://tantek.com/2023/019/t1/"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "The answer to “How should you @-mention someone you are replying to?”^1 can depend on many factors or a few. Context matters somewhat, sometimes.We can simplify it to 2 questions, based on 1 directive:* Elevate #IndieWeb domains, above any silo or @[email protected] identitiesTwo questions and answers: 1. Do they have an #IndieWeb domain? Then @-domain mention them^2, like you are speaking to them at their domain identity. This will notify them there, or at least reinforce their domain’s importance.2. Was their post only published on a silo (or #fediverse instance), or was it POSSEd to a silo (or fediverse instance) and you plan to POSSE (or federate) your reply^3? Then use their silo @-name (or @[email protected] address), in parentheses if (1). This will notify them on that silo (or instance), and may help thread your POSSE reply.Examples:If the author has their own domain:Reply to an IndieWeb post (& POSSE toot): https://tantek.com/2023/008/t1/* @-domain (@[email protected])Reply to an IndieWeb post (& POSSE tweet): https://tantek.com/2023/016/t1/* @-domain [that matches their Twitter @-name]Reply to a toot: https://tantek.com/2023/008/t4/* @-domain (@[email protected])Reply to a tweet: https://tantek.com/2023/002/t2/* @-domain (Twitter @-name)If the author does not have their own domain:Reply to a toot: https://tantek.com/2023/002/t4/* @[email protected] to a tweet: none since this series, though it would be of the form:* Twitter @-nameThis is day 17 of #100DaysOfIndieWeb #100Days, again finished the next day.← Day 16: https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post→ Day 18: https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo^1 https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post^2 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention^3 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute"
                ],
                "content": [
                  {
                    "html": "The answer to “How should you @-mention someone you are replying to?”^1 can depend on many factors or a few. Context matters somewhat, sometimes.<br class=\"auto-break\"><br class=\"auto-break\">We can simplify it to 2 questions, based on 1 directive:<br class=\"auto-break\"><br class=\"auto-break\">* Elevate #<span class=\"p-category auto-tag\">IndieWeb</span> domains, above any silo or @[email protected] identities<br class=\"auto-break\"><br class=\"auto-break\">Two questions and answers: <br class=\"auto-break\"><br class=\"auto-break\">1. Do they have an #<span class=\"p-category auto-tag\">IndieWeb</span> domain? Then @-domain mention them^2, like you are speaking to them at their domain identity. This will notify them there, or at least reinforce their domain’s importance.<br class=\"auto-break\"><br class=\"auto-break\">2. Was their post only published on a silo (or #<span class=\"p-category auto-tag\">fediverse</span> instance), or was it POSSEd to a silo (or fediverse instance) and you plan to POSSE (or federate) your reply^3? Then use their silo @-name (or @[email protected] address), in parentheses if (1). This will notify them on that silo (or instance), and may help thread your POSSE reply.<br class=\"auto-break\"><br class=\"auto-break\"><br class=\"auto-break\">Examples:<br class=\"auto-break\"><br class=\"auto-break\"><br class=\"auto-break\">If the author has their own domain:<br class=\"auto-break\"><br class=\"auto-break\">Reply to an IndieWeb post (&amp; POSSE toot): <a class=\"auto-link\" href=\"https://tantek.com/2023/008/t1/\">https://tantek.com/2023/008/t1/</a><br class=\"auto-break\">* @-domain (@[email protected])<br class=\"auto-break\"><br class=\"auto-break\">Reply to an IndieWeb post (&amp; POSSE tweet): <a class=\"auto-link\" href=\"https://tantek.com/2023/016/t1/\">https://tantek.com/2023/016/t1/</a><br class=\"auto-break\">* @-domain [that matches their Twitter @-name]<br class=\"auto-break\"><br class=\"auto-break\">Reply to a toot: <a class=\"auto-link\" href=\"https://tantek.com/2023/008/t4/\">https://tantek.com/2023/008/t4/</a><br class=\"auto-break\">* @-domain (@[email protected])<br class=\"auto-break\"><br class=\"auto-break\">Reply to a tweet: <a class=\"auto-link\" href=\"https://tantek.com/2023/002/t2/\">https://tantek.com/2023/002/t2/</a><br class=\"auto-break\">* @-domain (Twitter @-name)<br class=\"auto-break\"><br class=\"auto-break\"><br class=\"auto-break\">If the author does not have their own domain:<br class=\"auto-break\"><br class=\"auto-break\">Reply to a toot: <a class=\"auto-link\" href=\"https://tantek.com/2023/002/t4/\">https://tantek.com/2023/002/t4/</a><br class=\"auto-break\">* @[email protected]<br class=\"auto-break\"><br class=\"auto-break\">Reply to a tweet: none since this series, though it would be of the form:<br class=\"auto-break\">* Twitter @-name<br class=\"auto-break\"><br class=\"auto-break\"><br class=\"auto-break\">This is day 17 of #<span class=\"p-category auto-tag\">100DaysOfIndieWeb</span> #<span class=\"p-category auto-tag\">100Days</span>, again finished the next day.<br class=\"auto-break\"><br class=\"auto-break\">← Day 16: <a class=\"auto-link\" href=\"https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post\">https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post</a><br class=\"auto-break\">→ Day 18: <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\">^1 <a class=\"auto-link\" href=\"https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post\">https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post</a><br class=\"auto-break\">^2 <a class=\"auto-link\" href=\"https://tantek.com/2023/011/t1/indieweb-evolving-at-mention\">https://tantek.com/2023/011/t1/indieweb-evolving-at-mention</a><br class=\"auto-break\">^3 <a class=\"auto-link\" href=\"https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute\">https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute</a>",
                    "value": "The answer to “How should you @-mention someone you are replying to?”^1 can depend on many factors or a few. Context matters somewhat, sometimes.We can simplify it to 2 questions, based on 1 directive:* Elevate #IndieWeb domains, above any silo or @[email protected] identitiesTwo questions and answers: 1. Do they have an #IndieWeb domain? Then @-domain mention them^2, like you are speaking to them at their domain identity. This will notify them there, or at least reinforce their domain’s importance.2. Was their post only published on a silo (or #fediverse instance), or was it POSSEd to a silo (or fediverse instance) and you plan to POSSE (or federate) your reply^3? Then use their silo @-name (or @[email protected] address), in parentheses if (1). This will notify them on that silo (or instance), and may help thread your POSSE reply.Examples:If the author has their own domain:Reply to an IndieWeb post (& POSSE toot): https://tantek.com/2023/008/t1/* @-domain (@[email protected])Reply to an IndieWeb post (& POSSE tweet): https://tantek.com/2023/016/t1/* @-domain [that matches their Twitter @-name]Reply to a toot: https://tantek.com/2023/008/t4/* @-domain (@[email protected])Reply to a tweet: https://tantek.com/2023/002/t2/* @-domain (Twitter @-name)If the author does not have their own domain:Reply to a toot: https://tantek.com/2023/002/t4/* @[email protected] to a tweet: none since this series, though it would be of the form:* Twitter @-nameThis is day 17 of #100DaysOfIndieWeb #100Days, again finished the next day.← Day 16: https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post→ Day 18: https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo^1 https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post^2 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention^3 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute"
                  }
                ],
                "category": [
                  "IndieWeb",
                  "IndieWeb",
                  "fediverse",
                  "100DaysOfIndieWeb",
                  "100Days"
                ],
                "published": [
                  "23:11 on 2023-01-18"
                ],
                "updated": [
                  "23:11 on 2023-01-18"
                ],
                "url": [
                  "https://tantek.com/2023/018/t1/elevate-indieweb-above-silo"
                ],
                "uid": [
                  "https://tantek.com/2023/018/t1/elevate-indieweb-above-silo"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "Replying to people on the social web used to be “simple” before #socialMedia, when we used blogs. You would either write:1. a short reply — directly on someone’s blog post comment form, OR2. a longer reply — on your own blog, in-reply-to & linking to the other post and send a Pingback, expecting at least the other post’s author to see your reply, or you would also write a short comment in their blog post comment form with a brief summary & link to your longer reply postAside: web forums^1 at the time were proto-silos^2, and replies/threads were generally self-contained therein.Then social media exploded and eventually everybody was replying everywhere all at once.This was so burdensome that some even hired social media managers to perform the labor of how (and if) to reply on each silo, and attempt to keep up with every new silo that popped up.After a few years of this mid-to-late-2000s social web chaos, in the early 2010s many of us went back to option 2. above from the pre-social-media era, and as part of owning our data^3, started posting our replies in general on our own #IndieWeb sites:1. Regardless of brevity or length, we resumed posting peer-to-peer replies on our personal sites (now sent site-to-site with Webmentions^4), watched destinations retrieve & display our comments, and were pleased that our peer-to-peer comments looked like any other comments (except with permalinks back to our originals).2. We also started posting replies to tweets, GitHub issues^5, etc. on our own sites, and automatically POSSE-threading them into their sites of origin.3. When we wrote site-to-site replies where the original post had itself been syndicated to social media^6, we did both 1 & 2. This let readers follow the conversation in either place, providing an #IndieWeb record for if/when the social media thread was taken down, or disappeared along with another silo shutdown^7.Following this 1,2,3 approach helped conceptually simplify replying on the social web, and worked well except for a couple of interesting ongoing challenges:* What is the most efficient user interface path from viewing someone else’s post to writing a reply from your own site?* How should you @-mention someone you are replying to? (and how can our tools write or pre-fill that for us?)Regarding the latter, on day 14 I wrote a bit about how should we @-mention in general https://tantek.com/2023/014/t4/domain-first-federated-atmention though that was more of a general @-mention exploration. As a follow-up to day 14, it’s worth looking into @-reply mentions in particular, specifically for each of the above 1,2,3 contexts, analyzing examples of each, and looking for patterns of @-reply mentions best practices that we can document & recommend.This is day 16 of #100DaysOfIndieWeb #100Days, except I didn’t finish writing it (mostly) til the morning after, and editing later that afternoon.← Day 15: https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute→ Day 17: https://tantek.com/2023/018/t1/elevate-indieweb-above-silo^1 https://en.wikipedia.org/wiki/Internet_forum^2 https://indieweb.org/silo^3 https://indieweb.org/own_your_data^4 https://tantek.com/2023/012/t1/six-years-webmention-w3c^5 https://indieweb.org/GitHub#POSSE_to_GitHub^6 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute^7 https://indieweb.org/site-deaths"
                ],
                "content": [
                  {
                    "html": "Replying to people on the social web used to be “simple” before #<span class=\"p-category auto-tag\">socialMedia</span>, when we used blogs. You would either write:<br class=\"auto-break\"><br class=\"auto-break\">1. a short reply — directly on someone’s blog post comment form, OR<br class=\"auto-break\"><br class=\"auto-break\">2. a longer reply — on your own blog, in-reply-to &amp; linking to the other post and send a Pingback, expecting at least the other post’s author to see your reply, or you would also write a short comment in their blog post comment form with a brief summary &amp; link to your longer reply post<br class=\"auto-break\"><br class=\"auto-break\">Aside: web forums^1 at the time were proto-silos^2, and replies/threads were generally self-contained therein.<br class=\"auto-break\"><br class=\"auto-break\"><br class=\"auto-break\">Then social media exploded and eventually everybody was replying everywhere all at once.<br class=\"auto-break\"><br class=\"auto-break\">This was so burdensome that some even hired social media managers to perform the labor of how (and if) to reply on each silo, and attempt to keep up with every new silo that popped up.<br class=\"auto-break\"><br class=\"auto-break\"><br class=\"auto-break\">After a few years of this mid-to-late-2000s social web chaos, in the early 2010s many of us went back to option 2. above from the pre-social-media era, and as part of owning our data^3, started posting our replies in general on our own #<span class=\"p-category auto-tag\">IndieWeb</span> sites:<br class=\"auto-break\"><br class=\"auto-break\">1. Regardless of brevity or length, we resumed posting peer-to-peer replies on our personal sites (now sent site-to-site with Webmentions^4), watched destinations retrieve &amp; display our comments, and were pleased that our peer-to-peer comments looked like any other comments (except with permalinks back to our originals).<br class=\"auto-break\"><br class=\"auto-break\">2. We also started posting replies to tweets, GitHub issues^5, etc. on our own sites, and automatically POSSE-threading them into their sites of origin.<br class=\"auto-break\"><br class=\"auto-break\">3. When we wrote site-to-site replies where the original post had itself been syndicated to social media^6, we did both 1 &amp; 2. This let readers follow the conversation in either place, providing an #<span class=\"p-category auto-tag\">IndieWeb</span> record for if/when the social media thread was taken down, or disappeared along with another silo shutdown^7.<br class=\"auto-break\"><br class=\"auto-break\"><br class=\"auto-break\">Following this 1,2,3 approach helped conceptually simplify replying on the social web, and worked well except for a couple of interesting ongoing challenges:<br class=\"auto-break\"><br class=\"auto-break\">* What is the most efficient user interface path from viewing someone else’s post to writing a reply from your own site?<br class=\"auto-break\"><br class=\"auto-break\">* How should you @-mention someone you are replying to? (and how can our tools write or pre-fill that for us?)<br class=\"auto-break\"><br class=\"auto-break\">Regarding the latter, on day 14 I wrote a bit about how should we @-mention in general <a class=\"auto-link\" href=\"https://tantek.com/2023/014/t4/domain-first-federated-atmention\">https://tantek.com/2023/014/t4/domain-first-federated-atmention</a> though that was more of a general @-mention exploration. <br class=\"auto-break\"><br class=\"auto-break\">As a follow-up to day 14, it’s worth looking into @-reply mentions in particular, specifically for each of the above 1,2,3 contexts, analyzing examples of each, and looking for patterns of @-reply mentions best practices that we can document &amp; recommend.<br class=\"auto-break\"><br class=\"auto-break\">This is day 16 of #<span class=\"p-category auto-tag\">100DaysOfIndieWeb</span> #<span class=\"p-category auto-tag\">100Days</span>, except I didn’t finish writing it (mostly) til the morning after, and editing later that afternoon.<br class=\"auto-break\"><br class=\"auto-break\">← Day 15: <a class=\"auto-link\" href=\"https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute\">https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute</a><br class=\"auto-break\">→ Day 17: <a class=\"auto-link\" href=\"https://tantek.com/2023/018/t1/elevate-indieweb-above-silo\">https://tantek.com/2023/018/t1/elevate-indieweb-above-silo</a><br class=\"auto-break\"><br class=\"auto-break\"><br class=\"auto-break\">^1 <a class=\"auto-link\" href=\"https://en.wikipedia.org/wiki/Internet_forum\">https://en.wikipedia.org/wiki/Internet_forum</a><br class=\"auto-break\">^2 <a class=\"auto-link\" href=\"https://indieweb.org/silo\">https://indieweb.org/silo</a><br class=\"auto-break\">^3 <a class=\"auto-link\" href=\"https://indieweb.org/own_your_data\">https://indieweb.org/own_your_data</a><br class=\"auto-break\">^4 <a class=\"auto-link\" href=\"https://tantek.com/2023/012/t1/six-years-webmention-w3c\">https://tantek.com/2023/012/t1/six-years-webmention-w3c</a><br class=\"auto-break\">^5 <a class=\"auto-link\" href=\"https://indieweb.org/GitHub#POSSE_to_GitHub\">https://indieweb.org/GitHub#POSSE_to_GitHub</a><br class=\"auto-break\">^6 <a class=\"auto-link\" href=\"https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute\">https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute</a><br class=\"auto-break\">^7 <a class=\"auto-link\" href=\"https://indieweb.org/site-deaths\">https://indieweb.org/site-deaths</a>",
                    "value": "Replying to people on the social web used to be “simple” before #socialMedia, when we used blogs. You would either write:1. a short reply — directly on someone’s blog post comment form, OR2. a longer reply — on your own blog, in-reply-to & linking to the other post and send a Pingback, expecting at least the other post’s author to see your reply, or you would also write a short comment in their blog post comment form with a brief summary & link to your longer reply postAside: web forums^1 at the time were proto-silos^2, and replies/threads were generally self-contained therein.Then social media exploded and eventually everybody was replying everywhere all at once.This was so burdensome that some even hired social media managers to perform the labor of how (and if) to reply on each silo, and attempt to keep up with every new silo that popped up.After a few years of this mid-to-late-2000s social web chaos, in the early 2010s many of us went back to option 2. above from the pre-social-media era, and as part of owning our data^3, started posting our replies in general on our own #IndieWeb sites:1. Regardless of brevity or length, we resumed posting peer-to-peer replies on our personal sites (now sent site-to-site with Webmentions^4), watched destinations retrieve & display our comments, and were pleased that our peer-to-peer comments looked like any other comments (except with permalinks back to our originals).2. We also started posting replies to tweets, GitHub issues^5, etc. on our own sites, and automatically POSSE-threading them into their sites of origin.3. When we wrote site-to-site replies where the original post had itself been syndicated to social media^6, we did both 1 & 2. This let readers follow the conversation in either place, providing an #IndieWeb record for if/when the social media thread was taken down, or disappeared along with another silo shutdown^7.Following this 1,2,3 approach helped conceptually simplify replying on the social web, and worked well except for a couple of interesting ongoing challenges:* What is the most efficient user interface path from viewing someone else’s post to writing a reply from your own site?* How should you @-mention someone you are replying to? (and how can our tools write or pre-fill that for us?)Regarding the latter, on day 14 I wrote a bit about how should we @-mention in general https://tantek.com/2023/014/t4/domain-first-federated-atmention though that was more of a general @-mention exploration. As a follow-up to day 14, it’s worth looking into @-reply mentions in particular, specifically for each of the above 1,2,3 contexts, analyzing examples of each, and looking for patterns of @-reply mentions best practices that we can document & recommend.This is day 16 of #100DaysOfIndieWeb #100Days, except I didn’t finish writing it (mostly) til the morning after, and editing later that afternoon.← Day 15: https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute→ Day 17: https://tantek.com/2023/018/t1/elevate-indieweb-above-silo^1 https://en.wikipedia.org/wiki/Internet_forum^2 https://indieweb.org/silo^3 https://indieweb.org/own_your_data^4 https://tantek.com/2023/012/t1/six-years-webmention-w3c^5 https://indieweb.org/GitHub#POSSE_to_GitHub^6 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute^7 https://indieweb.org/site-deaths"
                  }
                ],
                "category": [
                  "socialMedia",
                  "IndieWeb",
                  "IndieWeb",
                  "100DaysOfIndieWeb",
                  "100Days"
                ],
                "published": [
                  "09:05 on 2023-01-17"
                ],
                "updated": [
                  "09:05 on 2023-01-17"
                ],
                "url": [
                  "https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post"
                ],
                "uid": [
                  "https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "in-reply-to": [
                  {
                    "type": [
                      "h-cite"
                    ],
                    "properties": {
                      "name": [
                        "dariusdunlap.com’s post"
                      ],
                      "url": [
                        "https://dariusdunlap.com/2023/01/take-control-of-your-online-life/"
                      ]
                    },
                    "value": "https://dariusdunlap.com/2023/01/take-control-of-your-online-life/"
                  }
                ],
                "name": [
                  "@dariusdunlap.com thanks for the kind words! Agreed that https://micro.blog/ is currently the best option for getting started with #IndieWeb / #fediverse, and for #TwitterMigration: https://indieweb.org/How_to_transition_from_Twitter"
                ],
                "content": [
                  {
                    "html": "<a class=\"auto-link\" href=\"https://dariusdunlap.com/\">@dariusdunlap.com</a> thanks for the kind words! Agreed that <a class=\"auto-link\" href=\"https://micro.blog/\">https://micro.blog/</a> is currently the best option for getting started with #<span class=\"p-category auto-tag\">IndieWeb</span> / #<span class=\"p-category auto-tag\">fediverse</span>, and for #<span class=\"p-category auto-tag\">TwitterMigration:</span> <a class=\"auto-link\" href=\"https://indieweb.org/How_to_transition_from_Twitter\">https://indieweb.org/How_to_transition_from_Twitter</a>",
                    "value": "@dariusdunlap.com thanks for the kind words! Agreed that https://micro.blog/ is currently the best option for getting started with #IndieWeb / #fediverse, and for #TwitterMigration: https://indieweb.org/How_to_transition_from_Twitter"
                  }
                ],
                "category": [
                  "IndieWeb",
                  "fediverse",
                  "TwitterMigration:"
                ],
                "published": [
                  "14:53 on 2023-01-16"
                ],
                "updated": [
                  "14:53 on 2023-01-16"
                ],
                "url": [
                  "https://tantek.com/2023/016/t1/"
                ],
                "uid": [
                  "https://tantek.com/2023/016/t1/"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "When you publish on your #IndieWeb site, you can decide afterwards where to distribute your content, and when. Figure out how you want to fit into the network of sites & instances. a png.  We call this POSSE — for Publish on your Own Site, then Syndicate Elsewhere.^1By prioritizing your own site, you decide whether (and when) you want to syndicate your posts (or a particular post) to a feed, to a fediverse, to a social media silo or silos, and/or to email like a newsletter.You can make it as simple or as detailed as you want. It’s up to you.Choose deliberately. Change your mind when things change. You can opt out of any destination, either by not opting-in, i.e. explicitly not sending your posts to them, or blocking them if necessary.Here are a few of the destination decisions I’ve made, and reasons why.You can delay sending a post to an RSS or Atom feed, say 10 minutes after the time of publication, to give yourself a chance to edit your post, fix typos or links, before a classic feed reader retrieves and perhaps caches your post.You can further delay sending to known uneditable destinations, like Twitter or email, to give yourself even longer to make further edits, corrections, updates, or improvements based on feedback to your original post.Some destination decisions may depend on the type of post.When you post a reply to someone else’s post, in addition to sending a webmention to that other post, it makes sense to also distribute it to where that other post was originally distributed, or a subset thereof, threading your POSSE reply with their original post POSSE copy.https://indieweb.org/reply#POSSE_a_replyFor example, if you reply to someone’s IndieWeb note, and they’ve POSSEd that note to Twitter, you should POSSE your reply to Twitter as well, threading it with their POSSE copy, if you’re still using Twitter that is. If they did not POSSE their original note to Twitter, there may be reasons to POSSE your reply to Twitter anyway, if your reply makes sense there on its own.https://indieweb.org/Twitter#POSSE_Replies_to_TwitterSome destinations have content limitations^2, and you may want to take that into consideration when authoring your content, or not.For example, you may want to more carefully copy-edit the first 256 (for now) characters of a note if you plan to POSSE to Twitter, so that the content that makes it through makes sense as an introduction, or a summary, or a hook, and perhaps has discovery features like hashtags. https://indieweb.org/Twitter#POSSE_Notes_to_TwitterYou can use that POSSE tweet text length limitation strategically, placing content after that 256 character cut-off that you may want to edit or expand in an update, or content Twitter may mess-up, like @-domain mentions I described yesterday (day 14).When you publish a multiphoto^3 post, if you’re POSSEing to Twitter, you may want to re-order your photos to choose which four photos show up in your POSSE tweet, e.g. if you happen to be using Bridgy Publish to cross-post your photos to Twitter. You can always re-order your original multiphoto post after POSSEing it. If you’re POSSEing photos to Instagram, since you can only do that manually, there’s no need to edit your original to fit Instagram’s 10-photo limitation, or 2200 characters caption limit, or 30 hashtags limit, or 20 person-tags limit.https://indieweb.org/multi-photo#How_to_POSSEOr you can reconsider what if anything you get from syndicating to Twitter or Instagram. Are people still seeing and interacting with your posts there? Are your friends?If & when social media algorithms deprioritize your original posts in favor of showing more ads, you can deprioritize posting to social media.If & when your friends quit social media silos^4, you can quit posting copies of your posts to those social media silos.You decide what content goes where, when, why, and can change your decisions any time you want.POSSEing to social media was always a stopgap. As social media silos self-destruct, you can stop syndicating to them.Thanks to Chris Aldrich (https://boffosocko.com/) for the banner image.This is day 15 of #100DaysOfIndieWeb #100Days.← Day 14: https://tantek.com/2023/014/t4/domain-first-federated-atmention→ Day 16: https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post^1 https://indieweb.org/POSSE^2 Day 5: https://tantek.com/2023/005/t3/indieweb-simpler-approach^3 https://indieweb.org/multi-photo^4 https://indieweb.org/silo-quits"
                ],
                "content": [
                  {
                    "html": "When you publish on your #<span class=\"p-category auto-tag\">IndieWeb</span> site, you can decide afterwards where to distribute your content, and when. Figure out how you want to fit into the network of sites &amp; instances.<br class=\"auto-break\"><a class=\"auto-link figure\" href=\"https://indieweb.org/POSSE\"><img class=\"auto-embed u-photo\" alt=\"a png. \" src=\"https://indieweb.org/images/6/6a/fit-into-the-network.png\"></a>We call this POSSE — for Publish on your Own Site, then Syndicate Elsewhere.^1<br class=\"auto-break\"><br class=\"auto-break\">By prioritizing your own site, you decide whether (and when) you want to syndicate your posts (or a particular post) to a feed, to a fediverse, to a social media silo or silos, and/or to email like a newsletter.<br class=\"auto-break\"><br class=\"auto-break\">You can make it as simple or as detailed as you want. It’s up to you.<br class=\"auto-break\"><br class=\"auto-break\">Choose deliberately. Change your mind when things change.<br class=\"auto-break\"> <br class=\"auto-break\">You can opt out of any destination, either by not opting-in, i.e. explicitly not sending your posts to them, or blocking them if necessary.<br class=\"auto-break\"><br class=\"auto-break\">Here are a few of the destination decisions I’ve made, and reasons why.<br class=\"auto-break\"><br class=\"auto-break\">You can delay sending a post to an RSS or Atom feed, say 10 minutes after the time of publication, to give yourself a chance to edit your post, fix typos or links, before a classic feed reader retrieves and perhaps caches your post.<br class=\"auto-break\"><br class=\"auto-break\">You can further delay sending to known uneditable destinations, like Twitter or email, to give yourself even longer to make further edits, corrections, updates, or improvements based on feedback to your original post.<br class=\"auto-break\"><br class=\"auto-break\">Some destination decisions may depend on the type of post.<br class=\"auto-break\"><br class=\"auto-break\">When you post a reply to someone else’s post, in addition to sending a webmention to that other post, it makes sense to also distribute it to where that other post was originally distributed, or a subset thereof, threading your POSSE reply with their original post POSSE copy.<br class=\"auto-break\"><br class=\"auto-break\"><a class=\"auto-link\" href=\"https://indieweb.org/reply#POSSE_a_reply\">https://indieweb.org/reply#POSSE_a_reply</a><br class=\"auto-break\"><br class=\"auto-break\">For example, if you reply to someone’s IndieWeb note, and they’ve POSSEd that note to Twitter, you should POSSE your reply to Twitter as well, threading it with their POSSE copy, if you’re still using Twitter that is. If they did not POSSE their original note to Twitter, there may be reasons to POSSE your reply to Twitter anyway, if your reply makes sense there on its own.<br class=\"auto-break\"><br class=\"auto-break\"><a class=\"auto-link\" href=\"https://indieweb.org/Twitter#POSSE_Replies_to_Twitter\">https://indieweb.org/Twitter#POSSE_Replies_to_Twitter</a><br class=\"auto-break\"><br class=\"auto-break\">Some destinations have content limitations^2, and you may want to take that into consideration when authoring your content, or not.<br class=\"auto-break\"><br class=\"auto-break\">For example, you may want to more carefully copy-edit the first 256 (for now) characters of a note if you plan to POSSE to Twitter, so that the content that makes it through makes sense as an introduction, or a summary, or a hook, and perhaps has discovery features like hashtags. <br class=\"auto-break\"><br class=\"auto-break\"><a class=\"auto-link\" href=\"https://indieweb.org/Twitter#POSSE_Notes_to_Twitter\">https://indieweb.org/Twitter#POSSE_Notes_to_Twitter</a><br class=\"auto-break\"><br class=\"auto-break\">You can use that POSSE tweet text length limitation strategically, placing content after that 256 character cut-off that you may want to edit or expand in an update, or content Twitter may mess-up, like @-domain mentions I described yesterday (day 14).<br class=\"auto-break\"><br class=\"auto-break\">When you publish a multiphoto^3 post, if you’re POSSEing to Twitter, you may want to re-order your photos to choose which four photos show up in your POSSE tweet, e.g. if you happen to be using Bridgy Publish to cross-post your photos to Twitter. You can always re-order your original multiphoto post after POSSEing it. <br class=\"auto-break\"><br class=\"auto-break\">If you’re POSSEing photos to Instagram, since you can only do that manually, there’s no need to edit your original to fit Instagram’s 10-photo limitation, or 2200 characters caption limit, or 30 hashtags limit, or 20 person-tags limit.<br class=\"auto-break\"><br class=\"auto-break\"><a class=\"auto-link\" href=\"https://indieweb.org/multi-photo#How_to_POSSE\">https://indieweb.org/multi-photo#How_to_POSSE</a><br class=\"auto-break\"><br class=\"auto-break\">Or you can reconsider what if anything you get from syndicating to Twitter or Instagram. <br class=\"auto-break\"><br class=\"auto-break\">Are people still seeing and interacting with your posts there? Are your friends?<br class=\"auto-break\"><br class=\"auto-break\">If &amp; when social media algorithms deprioritize your original posts in favor of showing more ads, you can deprioritize posting to social media.<br class=\"auto-break\"><br class=\"auto-break\">If &amp; when your friends quit social media silos^4, you can quit posting copies of your posts to those social media silos.<br class=\"auto-break\"><br class=\"auto-break\">You decide what content goes where, when, why, and can change your decisions any time you want.<br class=\"auto-break\"><br class=\"auto-break\">POSSEing to social media was always a stopgap. <br class=\"auto-break\"><br class=\"auto-break\">As social media silos self-destruct, you can stop syndicating to them.<br class=\"auto-break\"><br class=\"auto-break\">Thanks to Chris Aldrich (<a class=\"auto-link\" href=\"https://boffosocko.com/\">https://boffosocko.com/</a>) for the banner image.<br class=\"auto-break\"><br class=\"auto-break\">This is day 15 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 14: <a class=\"auto-link\" href=\"https://tantek.com/2023/014/t4/domain-first-federated-atmention\">https://tantek.com/2023/014/t4/domain-first-federated-atmention</a><br class=\"auto-break\">→ Day 16: <a class=\"auto-link\" href=\"https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post\">https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post</a><br class=\"auto-break\"><br class=\"auto-break\">^1 <a class=\"auto-link\" href=\"https://indieweb.org/POSSE\">https://indieweb.org/POSSE</a><br class=\"auto-break\">^2 Day 5: <a class=\"auto-link\" href=\"https://tantek.com/2023/005/t3/indieweb-simpler-approach\">https://tantek.com/2023/005/t3/indieweb-simpler-approach</a><br class=\"auto-break\">^3 <a class=\"auto-link\" href=\"https://indieweb.org/multi-photo\">https://indieweb.org/multi-photo</a><br class=\"auto-break\">^4 <a class=\"auto-link\" href=\"https://indieweb.org/silo-quits\">https://indieweb.org/silo-quits</a>",
                    "value": "When you publish on your #IndieWeb site, you can decide afterwards where to distribute your content, and when. Figure out how you want to fit into the network of sites & instances. a png.  We call this POSSE — for Publish on your Own Site, then Syndicate Elsewhere.^1By prioritizing your own site, you decide whether (and when) you want to syndicate your posts (or a particular post) to a feed, to a fediverse, to a social media silo or silos, and/or to email like a newsletter.You can make it as simple or as detailed as you want. It’s up to you.Choose deliberately. Change your mind when things change. You can opt out of any destination, either by not opting-in, i.e. explicitly not sending your posts to them, or blocking them if necessary.Here are a few of the destination decisions I’ve made, and reasons why.You can delay sending a post to an RSS or Atom feed, say 10 minutes after the time of publication, to give yourself a chance to edit your post, fix typos or links, before a classic feed reader retrieves and perhaps caches your post.You can further delay sending to known uneditable destinations, like Twitter or email, to give yourself even longer to make further edits, corrections, updates, or improvements based on feedback to your original post.Some destination decisions may depend on the type of post.When you post a reply to someone else’s post, in addition to sending a webmention to that other post, it makes sense to also distribute it to where that other post was originally distributed, or a subset thereof, threading your POSSE reply with their original post POSSE copy.https://indieweb.org/reply#POSSE_a_replyFor example, if you reply to someone’s IndieWeb note, and they’ve POSSEd that note to Twitter, you should POSSE your reply to Twitter as well, threading it with their POSSE copy, if you’re still using Twitter that is. If they did not POSSE their original note to Twitter, there may be reasons to POSSE your reply to Twitter anyway, if your reply makes sense there on its own.https://indieweb.org/Twitter#POSSE_Replies_to_TwitterSome destinations have content limitations^2, and you may want to take that into consideration when authoring your content, or not.For example, you may want to more carefully copy-edit the first 256 (for now) characters of a note if you plan to POSSE to Twitter, so that the content that makes it through makes sense as an introduction, or a summary, or a hook, and perhaps has discovery features like hashtags. https://indieweb.org/Twitter#POSSE_Notes_to_TwitterYou can use that POSSE tweet text length limitation strategically, placing content after that 256 character cut-off that you may want to edit or expand in an update, or content Twitter may mess-up, like @-domain mentions I described yesterday (day 14).When you publish a multiphoto^3 post, if you’re POSSEing to Twitter, you may want to re-order your photos to choose which four photos show up in your POSSE tweet, e.g. if you happen to be using Bridgy Publish to cross-post your photos to Twitter. You can always re-order your original multiphoto post after POSSEing it. If you’re POSSEing photos to Instagram, since you can only do that manually, there’s no need to edit your original to fit Instagram’s 10-photo limitation, or 2200 characters caption limit, or 30 hashtags limit, or 20 person-tags limit.https://indieweb.org/multi-photo#How_to_POSSEOr you can reconsider what if anything you get from syndicating to Twitter or Instagram. Are people still seeing and interacting with your posts there? Are your friends?If & when social media algorithms deprioritize your original posts in favor of showing more ads, you can deprioritize posting to social media.If & when your friends quit social media silos^4, you can quit posting copies of your posts to those social media silos.You decide what content goes where, when, why, and can change your decisions any time you want.POSSEing to social media was always a stopgap. As social media silos self-destruct, you can stop syndicating to them.Thanks to Chris Aldrich (https://boffosocko.com/) for the banner image.This is day 15 of #100DaysOfIndieWeb #100Days.← Day 14: https://tantek.com/2023/014/t4/domain-first-federated-atmention→ Day 16: https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post^1 https://indieweb.org/POSSE^2 Day 5: https://tantek.com/2023/005/t3/indieweb-simpler-approach^3 https://indieweb.org/multi-photo^4 https://indieweb.org/silo-quits"
                  }
                ],
                "category": [
                  "IndieWeb",
                  "100DaysOfIndieWeb",
                  "100Days"
                ],
                "photo": [
                  {
                    "value": "https://indieweb.org/images/6/6a/fit-into-the-network.png",
                    "alt": "a png."
                  }
                ],
                "published": [
                  "23:58 on 2023-01-15"
                ],
                "updated": [
                  "23:58 on 2023-01-15"
                ],
                "url": [
                  "https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute"
                ],
                "uid": [
                  "https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "Previously^1 I asked “How should we @ someone [on the #IndieWeb]?” & suggested we use @-domain. With some web spelunking, the earliest such use I found was 2013-03-26 (~10y ago!) by @eschnou.com, maybe^2 the first #siteToSite #federated #atMention! “And my first ever #indieweb pingback goes to @tantek.com, @aaronparecki.com and @waterpigs.co.uk ! Yes, I can now federate... well.. if I can manage to get it to interop :-)”Though the original post disappeared in a site update (and was unarchived), you can see it on the Internet Archive of @eschnou.com’s #IndieWeb tag page: https://web.archive.org/web/20130609045145/http://eschnou.com/tag/indieweb#2013Mar26At the time, Barnaby (@waterpigs.co.uk) did confirm receiving that @-mention on his site via Pingback (this was before Webmention was a thing^3): https://waterpigs.co.uk/notes/1199/ (https://twitter.com/BarnabyWalters/status/316664943820812289)@eschnou.com also asked in the IndieWeb chat if @aaronparecki.com had gotten his @-domain mention: https://chat.indieweb.org/2013-03-26#t1364333721000000 You can see at the bottom of that chat log that he did.I myself started using @-domain in my posts ~4 years later in a 2017 reply: https://tantek.com/2017/345/t1/aaronpk-paid-thanks (https://twitter.com/t/status/940382393097228288) though only when the same person controlled the domain and the Twitter @-name of the first part of the domain name before the \".\" (which was/is not many people. Workaround: use other @-domain mentions in posts after the POSSE tweet cut-off).I think that was my earliest use because two days after that post I added @-domain auto-linking to the https://tantek.com/github/cassis (@cassisjs) \"auto_link\" function https://github.com/tantek/cassis/commit/0e8e6270c0a3b600423c283f59b5d22c3648d59a (https://twitter.com/cassisjs/status/941107922318381057), likely having already tested it in production on my own site with that post.I’m still #testingInProduction the updates noted in ^3, notably \"https:\" for all @-mentions (@-name @-domain @[email protected]) and hope to merge them into the repo soon. Aside: both that and the #testInProduction hashtag have hilarious Twitter results^4.Does anyone know of any other auto-linkers that support linking @-domain in plain text to an https URL of that domain? Extra internet points if they also support @[email protected] auto-linking.This is day 14 of #100DaysOfIndieWeb #100Days.← Day 13: https://tantek.com/2023/013/t1/indieweb-home-internet→ Day 15: https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute^1 Day 11: https://tantek.com/2023/011/t1/indieweb-evolving-at-mention^2 I’m curious if StatusNet, OStatus, or OpenMicroBlogging had an explicit syntax for site-to-site @-mentions, whether any of them resembled @-domain, and is there evidence of their earliest @-mention usage (if any) still visible on the web (or Internet Archive) cc: @evanp.me (@[email protected])^3 Day 12: https://tantek.com/2023/012/t1/six-years-webmention-w3c^4 Navigating to Twitter hashtag results left as an exercise to the reader, to provide a deliberate soft barrier to a potential doomscrolling trap."
                ],
                "content": [
                  {
                    "html": "Previously^1 I asked “How should we @ someone [on the #<span class=\"p-category auto-tag\">IndieWeb</span>]?” &amp; suggested we use @-domain. With some web spelunking, the earliest such use I found was 2013-03-26 (~10y ago!) by <a class=\"auto-link\" href=\"https://eschnou.com/\">@eschnou.com</a>, maybe^2 the first #<span class=\"p-category auto-tag\">siteToSite</span> #<span class=\"p-category auto-tag\">federated</span> #<span class=\"p-category auto-tag\">atMention</span>!<br class=\"auto-break\"><br class=\"auto-break\"> “And my first ever #<span class=\"p-category auto-tag\">indieweb</span> pingback goes to <a class=\"auto-link\" href=\"https://tantek.com/\">@tantek.com</a>, <a class=\"auto-link\" href=\"https://aaronparecki.com/\">@aaronparecki.com</a> and <a class=\"auto-link\" href=\"https://waterpigs.co.uk/\">@waterpigs.co.uk</a> ! Yes, I can now federate... well.. if I can manage to get it to interop :-)”<br class=\"auto-break\"><br class=\"auto-break\">Though the original post disappeared in a site update (and was unarchived), you can see it on the Internet Archive of <a class=\"auto-link\" href=\"https://eschnou.com/\">@eschnou.com</a>’s #<span class=\"p-category auto-tag\">IndieWeb</span> tag page: <a class=\"auto-link\" href=\"https://web.archive.org/web/20130609045145/http://eschnou.com/tag/indieweb#2013Mar26\">https://web.archive.org/web/20130609045145/http://eschnou.com/tag/indieweb#2013Mar26</a><br class=\"auto-break\"><br class=\"auto-break\">At the time, Barnaby (<a class=\"auto-link\" href=\"https://waterpigs.co.uk/\">@waterpigs.co.uk</a>) did confirm receiving that @-mention on his site via Pingback (this was before Webmention was a thing^3): <a class=\"auto-link\" href=\"https://waterpigs.co.uk/notes/1199/\">https://waterpigs.co.uk/notes/1199/</a> (<a class=\"auto-link\" href=\"https://twitter.com/BarnabyWalters/status/316664943820812289\">https://twitter.com/BarnabyWalters/status/316664943820812289</a>)<br class=\"auto-break\"><br class=\"auto-break\"><a class=\"auto-link\" href=\"https://eschnou.com/\">@eschnou.com</a> also asked in the IndieWeb chat if <a class=\"auto-link\" href=\"https://aaronparecki.com/\">@aaronparecki.com</a> had gotten his @-domain mention: <a class=\"auto-link\" href=\"https://chat.indieweb.org/2013-03-26#t1364333721000000\">https://chat.indieweb.org/2013-03-26#t1364333721000000</a> <br class=\"auto-break\">You can see at the bottom of that chat log that he did.<br class=\"auto-break\"><br class=\"auto-break\">I myself started using @-domain in my posts ~4 years later in a 2017 reply: <a class=\"auto-link\" href=\"https://tantek.com/2017/345/t1/aaronpk-paid-thanks\">https://tantek.com/2017/345/t1/aaronpk-paid-thanks</a> (<a class=\"auto-link\" href=\"https://twitter.com/t/status/940382393097228288\">https://twitter.com/t/status/940382393097228288</a>) though only when the same person controlled the domain and the Twitter @-name of the first part of the domain name before the \".\" (which was/is not many people. Workaround: use other @-domain mentions in posts after the POSSE tweet cut-off).<br class=\"auto-break\"><br class=\"auto-break\">I think that was my earliest use because two days after that post I added @-domain auto-linking to the <a class=\"auto-link\" href=\"https://tantek.com/github/cassis\">https://tantek.com/github/cassis</a> (<a class=\"auto-link h-cassis-username\" href=\"https://twitter.com/cassisjs\">@cassisjs</a>) \"auto_link\" function <a class=\"auto-link\" href=\"https://github.com/tantek/cassis/commit/0e8e6270c0a3b600423c283f59b5d22c3648d59a\">https://github.com/tantek/cassis/commit/0e8e6270c0a3b600423c283f59b5d22c3648d59a</a> (<a class=\"auto-link\" href=\"https://twitter.com/cassisjs/status/941107922318381057\">https://twitter.com/cassisjs/status/941107922318381057</a>), likely having already tested it in production on my own site with that post.<br class=\"auto-break\"><br class=\"auto-break\">I’m still #<span class=\"p-category auto-tag\">testingInProduction</span> the updates noted in ^3, notably \"https:\" for all @-mentions (@-name @-domain @[email protected]) and hope to merge them into the repo soon. Aside: both that and the #<span class=\"p-category auto-tag\">testInProduction</span> hashtag have hilarious Twitter results^4.<br class=\"auto-break\"><br class=\"auto-break\">Does anyone know of any other auto-linkers that support linking @-domain in plain text to an https URL of that domain? Extra internet points if they also support @[email protected] auto-linking.<br class=\"auto-break\"><br class=\"auto-break\">This is day 14 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 13: <a class=\"auto-link\" href=\"https://tantek.com/2023/013/t1/indieweb-home-internet\">https://tantek.com/2023/013/t1/indieweb-home-internet</a><br class=\"auto-break\">→ Day 15: <a class=\"auto-link\" href=\"https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute\">https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute</a><br class=\"auto-break\"><br class=\"auto-break\">^1 Day 11: <a class=\"auto-link\" href=\"https://tantek.com/2023/011/t1/indieweb-evolving-at-mention\">https://tantek.com/2023/011/t1/indieweb-evolving-at-mention</a><br class=\"auto-break\">^2 I’m curious if StatusNet, OStatus, or OpenMicroBlogging had an explicit syntax for site-to-site @-mentions, whether any of them resembled @-domain, and is there evidence of their earliest @-mention usage (if any) still visible on the web (or Internet Archive) cc: <a class=\"auto-link\" href=\"https://evanp.me/\">@evanp.me</a> (<a class=\"auto-link\" href=\"https://prodromou.pub/@evan\">@[email protected]</a>)<br class=\"auto-break\">^3 Day 12: <a class=\"auto-link\" href=\"https://tantek.com/2023/012/t1/six-years-webmention-w3c\">https://tantek.com/2023/012/t1/six-years-webmention-w3c</a><br class=\"auto-break\">^4 Navigating to Twitter hashtag results left as an exercise to the reader, to provide a deliberate soft barrier to a potential doomscrolling trap.",
                    "value": "Previously^1 I asked “How should we @ someone [on the #IndieWeb]?” & suggested we use @-domain. With some web spelunking, the earliest such use I found was 2013-03-26 (~10y ago!) by @eschnou.com, maybe^2 the first #siteToSite #federated #atMention! “And my first ever #indieweb pingback goes to @tantek.com, @aaronparecki.com and @waterpigs.co.uk ! Yes, I can now federate... well.. if I can manage to get it to interop :-)”Though the original post disappeared in a site update (and was unarchived), you can see it on the Internet Archive of @eschnou.com’s #IndieWeb tag page: https://web.archive.org/web/20130609045145/http://eschnou.com/tag/indieweb#2013Mar26At the time, Barnaby (@waterpigs.co.uk) did confirm receiving that @-mention on his site via Pingback (this was before Webmention was a thing^3): https://waterpigs.co.uk/notes/1199/ (https://twitter.com/BarnabyWalters/status/316664943820812289)@eschnou.com also asked in the IndieWeb chat if @aaronparecki.com had gotten his @-domain mention: https://chat.indieweb.org/2013-03-26#t1364333721000000 You can see at the bottom of that chat log that he did.I myself started using @-domain in my posts ~4 years later in a 2017 reply: https://tantek.com/2017/345/t1/aaronpk-paid-thanks (https://twitter.com/t/status/940382393097228288) though only when the same person controlled the domain and the Twitter @-name of the first part of the domain name before the \".\" (which was/is not many people. Workaround: use other @-domain mentions in posts after the POSSE tweet cut-off).I think that was my earliest use because two days after that post I added @-domain auto-linking to the https://tantek.com/github/cassis (@cassisjs) \"auto_link\" function https://github.com/tantek/cassis/commit/0e8e6270c0a3b600423c283f59b5d22c3648d59a (https://twitter.com/cassisjs/status/941107922318381057), likely having already tested it in production on my own site with that post.I’m still #testingInProduction the updates noted in ^3, notably \"https:\" for all @-mentions (@-name @-domain @[email protected]) and hope to merge them into the repo soon. Aside: both that and the #testInProduction hashtag have hilarious Twitter results^4.Does anyone know of any other auto-linkers that support linking @-domain in plain text to an https URL of that domain? Extra internet points if they also support @[email protected] auto-linking.This is day 14 of #100DaysOfIndieWeb #100Days.← Day 13: https://tantek.com/2023/013/t1/indieweb-home-internet→ Day 15: https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute^1 Day 11: https://tantek.com/2023/011/t1/indieweb-evolving-at-mention^2 I’m curious if StatusNet, OStatus, or OpenMicroBlogging had an explicit syntax for site-to-site @-mentions, whether any of them resembled @-domain, and is there evidence of their earliest @-mention usage (if any) still visible on the web (or Internet Archive) cc: @evanp.me (@[email protected])^3 Day 12: https://tantek.com/2023/012/t1/six-years-webmention-w3c^4 Navigating to Twitter hashtag results left as an exercise to the reader, to provide a deliberate soft barrier to a potential doomscrolling trap."
                  }
                ],
                "category": [
                  "IndieWeb",
                  "siteToSite",
                  "federated",
                  "atMention",
                  "indieweb",
                  "IndieWeb",
                  "testingInProduction",
                  "testInProduction",
                  "100DaysOfIndieWeb",
                  "100Days"
                ],
                "published": [
                  "23:50 on 2023-01-14"
                ],
                "updated": [
                  "23:50 on 2023-01-14"
                ],
                "url": [
                  "https://tantek.com/2023/014/t4/domain-first-federated-atmention"
                ],
                "uid": [
                  "https://tantek.com/2023/014/t4/domain-first-federated-atmention"
                ]
              },
              "children": [
                {
                  "type": [
                    "h-cassis-username"
                  ],
                  "properties": {
                    "name": [
                      "@cassisjs"
                    ],
                    "url": [
                      "https://twitter.com/cassisjs"
                    ]
                  }
                }
              ]
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "👍"
                ],
                "content": [
                  {
                    "html": "👍",
                    "value": "👍"
                  }
                ],
                "in-reply-to": [
                  {
                    "type": [
                      "h-cite"
                    ],
                    "properties": {
                      "name": [
                        "a comment on issue 22213 of GitHub project “mastodon”"
                      ],
                      "url": [
                        "https://github.com/mastodon/mastodon/issues/22213#issuecomment-1382426972"
                      ]
                    },
                    "value": "https://github.com/mastodon/mastodon/issues/22213#issuecomment-1382426972"
                  }
                ],
                "published": [
                  "19:10 on 2023-01-14"
                ],
                "updated": [
                  "19:10 on 2023-01-14"
                ],
                "url": [
                  "https://tantek.com/2023/014/t3/"
                ],
                "uid": [
                  "https://tantek.com/2023/014/t3/"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "👍"
                ],
                "content": [
                  {
                    "html": "👍",
                    "value": "👍"
                  }
                ],
                "in-reply-to": [
                  {
                    "type": [
                      "h-cite"
                    ],
                    "properties": {
                      "name": [
                        "issue 22213 of GitHub project “mastodon”"
                      ],
                      "url": [
                        "https://github.com/mastodon/mastodon/issues/22213"
                      ]
                    },
                    "value": "https://github.com/mastodon/mastodon/issues/22213"
                  }
                ],
                "published": [
                  "19:07 on 2023-01-14"
                ],
                "updated": [
                  "19:07 on 2023-01-14"
                ],
                "url": [
                  "https://tantek.com/2023/014/t2/"
                ],
                "uid": [
                  "https://tantek.com/2023/014/t2/"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "likes martymcguire’s podcast"
                ],
                "summary": [
                  "likes martymcguire’s podcast"
                ],
                "like-of": [
                  "https://martymcgui.re/2023/01/14/123423/"
                ],
                "published": [
                  "18:42 on 2023-01-14"
                ],
                "updated": [
                  "18:42 on 2023-01-14"
                ],
                "url": [
                  "https://tantek.com/2023/014/f1"
                ],
                "uid": [
                  "https://tantek.com/2023/014/f1"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "in-reply-to": [
                  {
                    "type": [
                      "h-cite"
                    ],
                    "properties": {
                      "name": [
                        "pkm.social user daviddelven’s post"
                      ],
                      "url": [
                        "https://pkm.social/@daviddelven/109658104389145549"
                      ]
                    },
                    "value": "https://pkm.social/@daviddelven/109658104389145549"
                  }
                ],
                "name": [
                  "@[email protected] self-hosting^1 is plumbing^2, does not impact key user functionality, and thus not required for an #IndieWeb site.You can switch your site from self-hosted to service-hosted & back and it won’t affect your domain, permalinks, content, readers, peer-to-peer comments, or any other IndieWeb user features.Lastly, “self-hosting” means different things to different people. Some insist it means you have personal physical control of hardware, like a server in your home or garage, some are ok with a physical server in a personal colo cage under lock & key, or a shared colo cage, or a virtual “cloud” server without a physical location.Per the IndieWeb plurality^3 principle, people can use a self-hosted (under any of those definitions) site or a service-hosted site to publish & interact with each other.^1 https://indieweb.org/self_hosting^2 https://indieweb.org/plumbing^3 https://indieweb.org/plurality"
                ],
                "content": [
                  {
                    "html": "<a class=\"auto-link\" href=\"https://pkm.social/@daviddelven\">@[email protected]</a> self-hosting^1 is plumbing^2, does not impact key user functionality, and thus not required for an #<span class=\"p-category auto-tag\">IndieWeb</span> site.<br class=\"auto-break\"><br class=\"auto-break\">You can switch your site from self-hosted to service-hosted &amp; back and it won’t affect your domain, permalinks, content, readers, peer-to-peer comments, or any other IndieWeb user features.<br class=\"auto-break\"><br class=\"auto-break\">Lastly, “self-hosting” means different things to different people. Some insist it means you have personal physical control of hardware, like a server in your home or garage, some are ok with a physical server in a personal colo cage under lock &amp; key, or a shared colo cage, or a virtual “cloud” server without a physical location.<br class=\"auto-break\"><br class=\"auto-break\">Per the IndieWeb plurality^3 principle, people can use a self-hosted (under any of those definitions) site or a service-hosted site to publish &amp; interact with each other.<br class=\"auto-break\"><br class=\"auto-break\">^1 <a class=\"auto-link\" href=\"https://indieweb.org/self_hosting\">https://indieweb.org/self_hosting</a><br class=\"auto-break\">^2 <a class=\"auto-link\" href=\"https://indieweb.org/plumbing\">https://indieweb.org/plumbing</a><br class=\"auto-break\">^3 <a class=\"auto-link\" href=\"https://indieweb.org/plurality\">https://indieweb.org/plurality</a>",
                    "value": "@[email protected] self-hosting^1 is plumbing^2, does not impact key user functionality, and thus not required for an #IndieWeb site.You can switch your site from self-hosted to service-hosted & back and it won’t affect your domain, permalinks, content, readers, peer-to-peer comments, or any other IndieWeb user features.Lastly, “self-hosting” means different things to different people. Some insist it means you have personal physical control of hardware, like a server in your home or garage, some are ok with a physical server in a personal colo cage under lock & key, or a shared colo cage, or a virtual “cloud” server without a physical location.Per the IndieWeb plurality^3 principle, people can use a self-hosted (under any of those definitions) site or a service-hosted site to publish & interact with each other.^1 https://indieweb.org/self_hosting^2 https://indieweb.org/plumbing^3 https://indieweb.org/plurality"
                  }
                ],
                "category": [
                  "IndieWeb"
                ],
                "published": [
                  "17:06 on 2023-01-14"
                ],
                "updated": [
                  "17:06 on 2023-01-14"
                ],
                "url": [
                  "https://tantek.com/2023/014/t1/"
                ],
                "uid": [
                  "https://tantek.com/2023/014/t1/"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "Your #IndieWeb site can be the home you’ve always wanted on the internet. a png.  While posting on a personal site has many^1 advantages^2 over only posting to #socialMedia, maybe you already quit social media silos^3.There are lots of reasons to get a domain name^4 and setup your own homepage on the web.If you’re a web professional, a personal site with your name on it (perhaps also in its domain) can make it easier for potential employers to find you and read your description in your own words.If you’re a web developer, a personal home page is also an opportunity to demonstrate your craft.^5If you’re a writer, you can organize your words, essays, and longer form articles in a form that’s easier for readers to browse, and style them to both be easier to read, and express your style better than any silo.Similarly if you’re an artist, photographer, or any other kind of content creator.See https://indieweb.org/homepage for more reasons why, and what other kinds of things you can put on your home page.Thanks to Chris Aldrich (https://boffosocko.com/) for the banner image.This is day 13 of #100DaysOfIndieWeb #100Days.← Day 12: https://tantek.com/2023/012/t1/six-years-webmention-w3c→ Day 14: https://tantek.com/2023/014/t4/domain-first-federated-atmention^1 https://tantek.com/2023/001/t1/own-your-notes^2 https://tantek.com/2023/005/t3/indieweb-simpler-approach^3 https://indieweb.org/silo-quits^4 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb^5 https://indieweb.org/creator"
                ],
                "content": [
                  {
                    "html": "Your #<span class=\"p-category auto-tag\">IndieWeb</span> site can be the home you’ve always wanted on the internet.<br class=\"auto-break\"><a class=\"auto-link figure\" href=\"https://indieweb.org/homepage\"><img class=\"auto-embed u-photo\" alt=\"a png. \" src=\"https://indieweb.org/images/e/ee/the-home-youve-always-wanted.png\"></a><br class=\"auto-break\">While posting on a personal site has many^1 advantages^2 over only posting to #<span class=\"p-category auto-tag\">socialMedia</span>, maybe you already quit social media silos^3.<br class=\"auto-break\"><br class=\"auto-break\">There are lots of reasons to get a domain name^4 and setup your own homepage on the web.<br class=\"auto-break\"><br class=\"auto-break\">If you’re a web professional, a personal site with your name on it (perhaps also in its domain) can make it easier for potential employers to find you and read your description in your own words.<br class=\"auto-break\"><br class=\"auto-break\">If you’re a web developer, a personal home page is also an opportunity to demonstrate your craft.^5<br class=\"auto-break\"><br class=\"auto-break\">If you’re a writer, you can organize your words, essays, and longer form articles in a form that’s easier for readers to browse, and style them to both be easier to read, and express your style better than any silo.<br class=\"auto-break\"><br class=\"auto-break\">Similarly if you’re an artist, photographer, or any other kind of content creator.<br class=\"auto-break\"><br class=\"auto-break\">See <a class=\"auto-link\" href=\"https://indieweb.org/homepage\">https://indieweb.org/homepage</a> for more reasons why, and what other kinds of things you can put on your home page.<br class=\"auto-break\"><br class=\"auto-break\">Thanks to Chris Aldrich (<a class=\"auto-link\" href=\"https://boffosocko.com/\">https://boffosocko.com/</a>) for the banner image.<br class=\"auto-break\"><br class=\"auto-break\">This is day 13 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 12: <a class=\"auto-link\" href=\"https://tantek.com/2023/012/t1/six-years-webmention-w3c\">https://tantek.com/2023/012/t1/six-years-webmention-w3c</a><br class=\"auto-break\">→ Day 14: <a class=\"auto-link\" href=\"https://tantek.com/2023/014/t4/domain-first-federated-atmention\">https://tantek.com/2023/014/t4/domain-first-federated-atmention</a><br class=\"auto-break\"><br class=\"auto-break\">^1 <a class=\"auto-link\" href=\"https://tantek.com/2023/001/t1/own-your-notes\">https://tantek.com/2023/001/t1/own-your-notes</a><br class=\"auto-break\">^2 <a class=\"auto-link\" href=\"https://tantek.com/2023/005/t3/indieweb-simpler-approach\">https://tantek.com/2023/005/t3/indieweb-simpler-approach</a><br class=\"auto-break\">^3 <a class=\"auto-link\" href=\"https://indieweb.org/silo-quits\">https://indieweb.org/silo-quits</a><br class=\"auto-break\">^4 <a class=\"auto-link\" href=\"https://tantek.com/2023/004/t1/choosing-domain-name-indieweb\">https://tantek.com/2023/004/t1/choosing-domain-name-indieweb</a><br class=\"auto-break\">^5 <a class=\"auto-link\" href=\"https://indieweb.org/creator\">https://indieweb.org/creator</a>",
                    "value": "Your #IndieWeb site can be the home you’ve always wanted on the internet. a png.  While posting on a personal site has many^1 advantages^2 over only posting to #socialMedia, maybe you already quit social media silos^3.There are lots of reasons to get a domain name^4 and setup your own homepage on the web.If you’re a web professional, a personal site with your name on it (perhaps also in its domain) can make it easier for potential employers to find you and read your description in your own words.If you’re a web developer, a personal home page is also an opportunity to demonstrate your craft.^5If you’re a writer, you can organize your words, essays, and longer form articles in a form that’s easier for readers to browse, and style them to both be easier to read, and express your style better than any silo.Similarly if you’re an artist, photographer, or any other kind of content creator.See https://indieweb.org/homepage for more reasons why, and what other kinds of things you can put on your home page.Thanks to Chris Aldrich (https://boffosocko.com/) for the banner image.This is day 13 of #100DaysOfIndieWeb #100Days.← Day 12: https://tantek.com/2023/012/t1/six-years-webmention-w3c→ Day 14: https://tantek.com/2023/014/t4/domain-first-federated-atmention^1 https://tantek.com/2023/001/t1/own-your-notes^2 https://tantek.com/2023/005/t3/indieweb-simpler-approach^3 https://indieweb.org/silo-quits^4 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb^5 https://indieweb.org/creator"
                  }
                ],
                "category": [
                  "IndieWeb",
                  "socialMedia",
                  "100DaysOfIndieWeb",
                  "100Days"
                ],
                "photo": [
                  {
                    "value": "https://indieweb.org/images/e/ee/the-home-youve-always-wanted.png",
                    "alt": "a png."
                  }
                ],
                "published": [
                  "23:39 on 2023-01-13"
                ],
                "updated": [
                  "23:39 on 2023-01-13"
                ],
                "url": [
                  "https://tantek.com/2023/013/t1/indieweb-home-internet"
                ],
                "uid": [
                  "https://tantek.com/2023/013/t1/indieweb-home-internet"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "🎉 Six years ago today, the #IndieWeb Webmention protocol was published as a W3C REC https://www.w3.org/TR/webmention/A key social web building block, Webmention enabled peer-to-peer comments, likes, and other responses to be created, updated, and deleted across the web, by both dynamic & static websites.It was accompanied by a report of over a dozen implementations that demonstrated interoperability: https://webmention.net/implementation-reports/summary/ using an open test suite: https://webmention.rocks/ that is still up and running and used by developers today.Many many more implementations have been developed, open sourced, shipped, launched since. The specification itself has a webmention endpoint and accepts webmentions.Exactly a year before that, Webmention was published as a First Public Working Draft by the W3C Social Web Working Group: https://www.w3.org/TR/2016/WD-webmention-20160112/It took the best parts of the prior Pingback protocol, simplified it (ditched XML-RPC), made it more secure, separated presentation from plumbing, and added update & delete semantics. It was in many ways a model for how open web standards should be developed.See the wiki page for an overview and numerous screenshots of implementations: https://indieweb.org/WebmentionIf you want to implement Webmention yourself, there are now numerous developer resources to do so.Start here: https://indieweb.org/Webmention-developer and come say hi at the IndieWeb development chat channel: https://chat.indieweb.org/devPreviously, previously, previously: * https://tantek.com/2020/012/t1/happy-birthday-webmention* https://tantek.com/2018/012/t1/anniversary-million-webmentions* https://tantek.com/2017/012/t1/webmntion-first-w3c-recommendation-high-barThis is day 12 of #100DaysOfIndieWeb #100Days.← Day 11: https://tantek.com/2023/011/t1/indieweb-evolving-at-mention→ Day 13: https://tantek.com/2023/013/t1/indieweb-home-internet"
                ],
                "content": [
                  {
                    "html": "🎉 Six years ago today, the #<span class=\"p-category auto-tag\">IndieWeb</span> Webmention protocol was published as a W3C REC <a class=\"auto-link\" href=\"https://www.w3.org/TR/webmention/\">https://www.w3.org/TR/webmention/</a><br class=\"auto-break\"><br class=\"auto-break\">A key social web building block, Webmention enabled peer-to-peer comments, likes, and other responses to be created, updated, and deleted across the web, by both dynamic &amp; static websites.<br class=\"auto-break\"><br class=\"auto-break\">It was accompanied by a report of over a dozen implementations that demonstrated interoperability: <a class=\"auto-link\" href=\"https://webmention.net/implementation-reports/summary/\">https://webmention.net/implementation-reports/summary/</a> using an open test suite: <a class=\"auto-link\" href=\"https://webmention.rocks/\">https://webmention.rocks/</a> that is still up and running and used by developers today.<br class=\"auto-break\"><br class=\"auto-break\">Many many more implementations have been developed, open sourced, shipped, launched since. The specification itself has a webmention endpoint and accepts webmentions.<br class=\"auto-break\"><br class=\"auto-break\">Exactly a year before that, Webmention was published as a First Public Working Draft by the W3C Social Web Working Group: <a class=\"auto-link\" href=\"https://www.w3.org/TR/2016/WD-webmention-20160112/\">https://www.w3.org/TR/2016/WD-webmention-20160112/</a><br class=\"auto-break\"><br class=\"auto-break\">It took the best parts of the prior Pingback protocol, simplified it (ditched XML-RPC), made it more secure, separated presentation from plumbing, and added update &amp; delete semantics. <br class=\"auto-break\"><br class=\"auto-break\">It was in many ways a model for how open web standards should be developed.<br class=\"auto-break\"><br class=\"auto-break\">See the wiki page for an overview and numerous screenshots of implementations: <a class=\"auto-link\" href=\"https://indieweb.org/Webmention\">https://indieweb.org/Webmention</a><br class=\"auto-break\"><br class=\"auto-break\">If you want to implement Webmention yourself, there are now numerous developer resources to do so.<br class=\"auto-break\"><br class=\"auto-break\">Start here: <a class=\"auto-link\" href=\"https://indieweb.org/Webmention-developer\">https://indieweb.org/Webmention-developer</a> and come say hi at the IndieWeb development chat channel: <a class=\"auto-link\" href=\"https://chat.indieweb.org/dev\">https://chat.indieweb.org/dev</a><br class=\"auto-break\"><br class=\"auto-break\">Previously, previously, previously: <br class=\"auto-break\">* <a class=\"auto-link\" href=\"https://tantek.com/2020/012/t1/happy-birthday-webmention\">https://tantek.com/2020/012/t1/happy-birthday-webmention</a><br class=\"auto-break\">* <a class=\"auto-link\" href=\"https://tantek.com/2018/012/t1/anniversary-million-webmentions\">https://tantek.com/2018/012/t1/anniversary-million-webmentions</a><br class=\"auto-break\">* <a class=\"auto-link\" href=\"https://tantek.com/2017/012/t1/webmntion-first-w3c-recommendation-high-bar\">https://tantek.com/2017/012/t1/webmntion-first-w3c-recommendation-high-bar</a><br class=\"auto-break\"><br class=\"auto-break\">This is day 12 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 11: <a class=\"auto-link\" href=\"https://tantek.com/2023/011/t1/indieweb-evolving-at-mention\">https://tantek.com/2023/011/t1/indieweb-evolving-at-mention</a><br class=\"auto-break\">→ Day 13: <a class=\"auto-link\" href=\"https://tantek.com/2023/013/t1/indieweb-home-internet\">https://tantek.com/2023/013/t1/indieweb-home-internet</a>",
                    "value": "🎉 Six years ago today, the #IndieWeb Webmention protocol was published as a W3C REC https://www.w3.org/TR/webmention/A key social web building block, Webmention enabled peer-to-peer comments, likes, and other responses to be created, updated, and deleted across the web, by both dynamic & static websites.It was accompanied by a report of over a dozen implementations that demonstrated interoperability: https://webmention.net/implementation-reports/summary/ using an open test suite: https://webmention.rocks/ that is still up and running and used by developers today.Many many more implementations have been developed, open sourced, shipped, launched since. The specification itself has a webmention endpoint and accepts webmentions.Exactly a year before that, Webmention was published as a First Public Working Draft by the W3C Social Web Working Group: https://www.w3.org/TR/2016/WD-webmention-20160112/It took the best parts of the prior Pingback protocol, simplified it (ditched XML-RPC), made it more secure, separated presentation from plumbing, and added update & delete semantics. It was in many ways a model for how open web standards should be developed.See the wiki page for an overview and numerous screenshots of implementations: https://indieweb.org/WebmentionIf you want to implement Webmention yourself, there are now numerous developer resources to do so.Start here: https://indieweb.org/Webmention-developer and come say hi at the IndieWeb development chat channel: https://chat.indieweb.org/devPreviously, previously, previously: * https://tantek.com/2020/012/t1/happy-birthday-webmention* https://tantek.com/2018/012/t1/anniversary-million-webmentions* https://tantek.com/2017/012/t1/webmntion-first-w3c-recommendation-high-barThis is day 12 of #100DaysOfIndieWeb #100Days.← Day 11: https://tantek.com/2023/011/t1/indieweb-evolving-at-mention→ Day 13: https://tantek.com/2023/013/t1/indieweb-home-internet"
                  }
                ],
                "category": [
                  "IndieWeb",
                  "100DaysOfIndieWeb",
                  "100Days"
                ],
                "published": [
                  "23:45 on 2023-01-12"
                ],
                "updated": [
                  "23:45 on 2023-01-12"
                ],
                "url": [
                  "https://tantek.com/2023/012/t1/six-years-webmention-w3c"
                ],
                "uid": [
                  "https://tantek.com/2023/012/t1/six-years-webmention-w3c"
                ]
              }
            }
          ]
        },
        {
          "type": [
            "h-feed"
          ],
          "properties": {
            "name": [
              "Recent Articles"
            ]
          },
          "id": "recent-articles",
          "children": [
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "Running For The @W3C Advisory Board (@W3CAB) Special Election"
                ],
                "url": [
                  "https://tantek.com/2022/334/b1/running-for-w3c-advisory-board-special-election"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "W3C TPAC 2022 Sustainability Community Group Meeting"
                ],
                "url": [
                  "https://tantek.com/2022/267/b1/w3c-tpac-sustainability-cg-meeting"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "One Year Since The #IndieWeb Homebrew Website Club Met In Person And Other Last Times"
                ],
                "url": [
                  "https://tantek.com/2021/064/b1/one-year-since-homebrew-website-club"
                ]
              }
            }
          ]
        },
        {
          "type": [
            "h-feed"
          ],
          "properties": {
            "name": [
              "Recent Photos"
            ]
          },
          "id": "recent-photos",
          "children": [
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "Tantek running with a focused look in a 2020 MUC50 cap, black singlet & shorts, on a dirt trail with grass, bushes, & trees on both sides, and two runners out of focus ~20 meters behind him."
                ],
                "photo": [
                  {
                    "value": "https://fastly.4sqi.net/img/general/width960/476_tjk6ja88e3mjglC50lmeeMAwpr4Pozk_yVhAIuNgq3E.jpg",
                    "alt": "Tantek running with a focused look in a 2020 MUC50 cap, black singlet & shorts, on a dirt trail with grass, bushes, & trees on both sides, and two runners out of focus ~20 meters behind him."
                  }
                ],
                "url": [
                  "https://tantek.com/2022/289/t1/hot-skyline50k-ultra-finish"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "Fogged-in view of a lush green hillside, narrow singletrack trail cutting up from the right and approaching the center, with Tantek power hiking uphill, grinning, water bottle in right hand, holding his side with his left."
                ],
                "photo": [
                  {
                    "value": "https://fastly.4sqi.net/img/general/width960/476_9_gqB6h_tK8iyjBEb886XpboOcF8bsEgT_wl76vckqI.jpg",
                    "alt": "Fogged-in view of a lush green hillside, narrow singletrack trail cutting up from the right and approaching the center, with Tantek power hiking uphill, grinning, water bottle in right hand, holding his side with his left."
                  }
                ],
                "url": [
                  "https://tantek.com/2021/221/t1/finished-rodeovalley-trailrace"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "White yoga mat on a hardwood floor with running shoes, clothes, gear, fuel laid out in an orderly fashion."
                ],
                "photo": [
                  {
                    "value": "https://fastly.4sqi.net/img/general/width960/476_gChM9nrNNko-1aMouw-x74imp7kzUzJKLomkEQ4u8qQ.jpg",
                    "alt": "White yoga mat on a hardwood floor with running shoes, clothes, gear, fuel laid out in an orderly fashion."
                  }
                ],
                "url": [
                  "https://tantek.com/2021/218/t1/running-rodeovalley"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "Tantek running downhill on a trail with mountains, hills, and an ocean shore in the distant background, under a sunny blue sky."
                ],
                "photo": [
                  {
                    "value": "https://fastly.4sqi.net/img/general/width960/476_nJH-uVKVhefvOPmfi3mPSlI9MqpeN6WLmS6EbWdKNC0.jpg",
                    "alt": "Tantek running downhill on a trail with mountains, hills, and an ocean shore in the distant background, under a sunny blue sky."
                  }
                ],
                "url": [
                  "https://tantek.com/2021/019/t1/marin-trailrun"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "View of sunset-lit downtown San Francisco in the distance as viewed from Twin Peaks, with the hairpin turn below, and immediately below the green hill slope of Twin Peaks summit."
                ],
                "photo": [
                  {
                    "value": "https://fastly.4sqi.net/img/general/width960/476_fkcHgLiQBPvCLZJHKYdX7CaTedWH8UbLwL1AQuOZV9A.jpg",
                    "alt": "View of sunset-lit downtown San Francisco in the distance as viewed from Twin Peaks, with the hairpin turn below, and immediately below the green hill slope of Twin Peaks summit."
                  }
                ],
                "url": [
                  "https://tantek.com/2021/017/t3/seven-years-ago-npsf-hills"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "January of 2021 month calendar built from LEGO bricks, on a hexagonal white on gray blanket background."
                ],
                "photo": [
                  {
                    "value": "https://fastly.4sqi.net/img/general/width960/476_M152uOnalZ6QfPsz9YMHd2sNPt-U7s2Twx2Lj26gryA.jpg",
                    "alt": "January of 2021 month calendar built from LEGO bricks, on a hexagonal white on gray blanket background."
                  }
                ],
                "url": [
                  "https://tantek.com/2021/017/t2/january"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "Multicolored heart painting with a few sequine pieces, outlined in pink with bits of turquoise, paint dripping downward, on a piece of plywood at a construction site, signed KATE_TOVA."
                ],
                "photo": [
                  {
                    "value": "https://fastly.4sqi.net/img/general/width960/476_77tgUdgL2xYzHOEFYLIf1-kATkEom1PWrqzIEja6Bww.jpg",
                    "alt": "Multicolored heart painting with a few sequine pieces, outlined in pink with bits of turquoise, paint dripping downward, on a piece of plywood at a construction site, signed KATE_TOVA."
                  }
                ],
                "url": [
                  "https://tantek.com/2020/364/t1/last-track"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "Tantek wearing a buff taking a selfie at the Mill Valley Depot with Nick, Paddy, Olivia, and Emma safely distanced in the background."
                ],
                "photo": [
                  {
                    "value": "https://fastly.4sqi.net/img/general/width960/476_OguOnR4ZRWSfkf4xrKwqIhVCw6Fmp8zJZT1reWJclls.jpg",
                    "alt": "Tantek wearing a buff taking a selfie at the Mill Valley Depot with Nick, Paddy, Olivia, and Emma safely distanced in the background."
                  }
                ],
                "url": [
                  "https://tantek.com/2020/359/t1/tam-summit"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "December of 2020 month calendar built from LEGO bricks, on an hardwood floor background."
                ],
                "photo": [
                  {
                    "value": "https://fastly.4sqi.net/img/general/width960/476_crDev05xDJVnmxPsasFbdxMvdxDA1tuItOUPEaTVogA.jpg",
                    "alt": "December of 2020 month calendar built from LEGO bricks, on an hardwood floor background."
                  }
                ],
                "url": [
                  "https://tantek.com/2020/356/t1/december-winter-solstice"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "Stencil street art of George Floyd on a red wall with the word JUSTICE above his head, and FOR GEORGE below."
                ],
                "photo": [
                  {
                    "value": "https://fastly.4sqi.net/img/general/width960/476_wiYEJTxjdxLl_vZFlLefP9O8b-Jv9R12Q92ANKZXhSA.jpg",
                    "alt": "Stencil street art of George Floyd on a red wall with the word JUSTICE above his head, and FOR GEORGE below."
                  }
                ],
                "url": [
                  "https://tantek.com/2020/153/t1/justice-for-george"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "Intersection of Frederick and Ashbury streets at night, looking westward, everything is dark except for streetlamps, lights outside a boarded up Ashbury Market, and a second floor corner apartment on the other side, above a lit bus stop for the number 6 outbound bus."
                ],
                "photo": [
                  {
                    "value": "https://fastly.4sqi.net/img/general/width960/476_SpwXl5ANk0Pyg5xBFSovR5qUkMoaEE_6uak0acFKU8w.jpg",
                    "alt": "Intersection of Frederick and Ashbury streets at night, looking westward, everything is dark except for streetlamps, lights outside a boarded up Ashbury Market, and a second floor corner apartment on the other side, above a lit bus stop for the number 6 outbound bus."
                  }
                ],
                "url": [
                  "https://tantek.com/2020/137/t3/sf-distancing-day-twelve"
                ]
              }
            },
            {
              "type": [
                "h-entry"
              ],
              "properties": {
                "name": [
                  "Strava map showing a roundtrip running route in red from Haight Ashbury to near a hairpin turn on Twin Peaks and back."
                ],
                "photo": [
                  {
                    "value": "https://fastly.4sqi.net/img/general/width960/476_RLIxPGQ2v_yOJcsVnDalcK2pZETJNnYbZSr1I4VhrBc.jpg",
                    "alt": "Strava map showing a roundtrip running route in red from Haight Ashbury to near a hairpin turn on Twin Peaks and back."
                  }
                ],
                "url": [
                  "https://tantek.com/2020/130/t1/ahmaudarbery-blacklivesmatter"
                ]
              }
            }
          ]
        },
        {
          "type": [
            "h-card"
          ],
          "properties": {
            "name": [
              "microformats.org"
            ],
            "url": [
              "http://microformats.org/wiki",
              "https://twitter.com/microformats"
            ],
            "note": [
              "the fastest way to turn your web pages into simple APIs and simultaneously look better in search engines"
            ]
          }
        },
        {
          "type": [
            "h-feed"
          ],
          "properties": {
            "name": [
              "Speaking & Events"
            ]
          },
          "id": "events",
          "children": [
            {
              "type": [
                "h-event"
              ],
              "properties": {
                "start": [
                  "2022-08-07"
                ],
                "url": [
                  "https://scenaperformance.com/events/skyline-50k/"
                ],
                "name": [
                  "Scena Performance’s Skyeline 50km trail race"
                ],
                "location": [
                  "Lake Chabot Marina, Castro Valley, California, USA"
                ]
              }
            },
            {
              "type": [
                "h-event"
              ],
              "properties": {
                "start": [
                  "2022-08-16"
                ],
                "end": [
                  "2022-08-18"
                ],
                "url": [
                  "https://www.w3.org/wiki/AB/2022-08-BER"
                ],
                "name": [
                  "W3C Advisory Board"
                ],
                "location": [
                  "Berlin, Germany"
                ]
              }
            },
            {
              "type": [
                "h-event"
              ],
              "properties": {
                "start": [
                  "2022-09-12"
                ],
                "end": [
                  "2022-09-16"
                ],
                "url": [
                  "https://www.w3.org/wiki/TPAC/2022"
                ],
                "name": [
                  "W3C TPAC"
                ],
                "location": [
                  "Vancouver, Canada"
                ]
              }
            }
          ]
        },
        {
          "type": [
            "h-card"
          ],
          "properties": {
            "name": [
              "Rebecca Daniels"
            ]
          }
        }
      ]
    }
  ],
  "rels": {
    "self": [
      "https://tantek.com/"
    ],
    "icon": [
      "https://tantek.com/logo.jpg"
    ],
    "apple-touch-icon-precomposed": [
      "https://tantek.com/logo.jpg"
    ],
    "webmention": [
      "https://webmention.io/tantek.com/webmention"
    ],
    "hub": [
      "https://pubsubhubbub.superfeedr.com/"
    ],
    "openid.delegate": [
      "https://tantek.com/"
    ],
    "openid.server": [
      "https://indieauth.com/openid"
    ],
    "authorization_endpoint": [
      "https://indieauth.com/auth"
    ],
    "token_endpoint": [
      "https://tokens.indieauth.com/token"
    ],
    "microsub": [
      "https://aperture.p3k.io/microsub/277"
    ],
    "alternate": [
      "https://tantek.com/#updates",
      "https://tantek.com/updates.atom"
    ],
    "serviceworker": [
      "https://tantek.com/serviceworker.js"
    ],
    "author": [
      "https://tantek.com/"
    ],
    "payment": [
      "https://tantek.com/tip/1"
    ],
    "bookmark": [
      "https://tantek.com/2023/019/b1/bridgy-publish-support-gitlab"
    ],
    "nofollow": [
      "https://tantek.com/?",
      "https://tantek.com/?skin=vtx",
      "https://tantek.com/?skin=trn"
    ],
    "canonical": [
      "https://tantek.com/"
    ],
    "me": [
      "https://micro.blog/t",
      "https://xoxo.zone/@t",
      "https://instagram.com/tantek/",
      "https://twitter.com/intent/user?screen_name=t",
      "https://github.com/tantek",
      "https://indieweb.org/User:Tantek.com",
      "https://en.wikipedia.org/wiki/User:Tantek"
    ]
  },
  "rel-urls": {
    "https://tantek.com/": {
      "rels": [
        "self"
      ]
    },
    "https://tantek.com/logo.jpg": {
      "rels": [
        "icon"
      ]
    },
    "https://webmention.io/tantek.com/webmention": {
      "rels": [
        "webmention"
      ]
    },
    "https://pubsubhubbub.superfeedr.com/": {
      "rels": [
        "hub"
      ]
    },
    "https://indieauth.com/openid": {
      "rels": [
        "openid.server"
      ]
    },
    "https://indieauth.com/auth": {
      "rels": [
        "authorization_endpoint"
      ]
    },
    "https://tokens.indieauth.com/token": {
      "rels": [
        "token_endpoint"
      ]
    },
    "https://aperture.p3k.io/microsub/277": {
      "rels": [
        "microsub"
      ]
    },
    "https://tantek.com/#updates": {
      "rels": [
        "alternate"
      ],
      "type": "text/mf2+html"
    },
    "https://tantek.com/updates.atom": {
      "rels": [
        "alternate"
      ],
      "type": "application/atom+xml"
    },
    "https://tantek.com/serviceworker.js": {
      "rels": [
        "serviceworker"
      ]
    },
    "https://tantek.com/tip/1": {
      "rels": [
        "payment"
      ],
      "title": "Tip: Did you read something of value here and want to encourage more posts like that? Feel free to tip a small amount and mention which topics you enjoyed! (Just please avoid specific products or services. Thanks! -t)",
      "text": "👏 "
    },
    "https://tantek.com/2023/019/b1/bridgy-publish-support-gitlab": {
      "rels": [
        "bookmark"
      ],
      "text": "\nBridgy Publish feature request: Support posting to GitLab sites\n"
    },
    "https://tantek.com/?": {
      "rels": [
        "nofollow"
      ],
      "title": "Choose default theme",
      "text": "🏠"
    },
    "https://tantek.com/?skin=vtx": {
      "rels": [
        "nofollow"
      ],
      "title": "Choose Terminal theme",
      "text": "📺"
    },
    "https://tantek.com/?skin=trn": {
      "rels": [
        "nofollow"
      ],
      "title": "Choose TRON:Legacy theme",
      "text": "🔵"
    },
    "https://micro.blog/t": {
      "rels": [
        "me"
      ],
      "title": "follow me on micro.blog",
      "text": "\n  \n    \n      \n      \n    \n    \n      \n      \n    \n  \n  \n  \n micro.blog @t"
    },
    "https://xoxo.zone/@t": {
      "rels": [
        "me"
      ]
    },
    "https://instagram.com/tantek/": {
      "rels": [
        "me"
      ],
      "title": "Instagram account where I cross-post my photos",
      "text": " Instagram @tantek"
    },
    "https://twitter.com/intent/user?screen_name=t": {
      "rels": [
        "me"
      ],
      "title": "follow me on Twitter",
      "text": " Twitter @t"
    },
    "https://github.com/tantek": {
      "rels": [
        "me"
      ],
      "title": "open source on Github",
      "text": " Github @tantek"
    },
    "https://indieweb.org/User:Tantek.com": {
      "rels": [
        "me"
      ],
      "title": "contributions to IndieWeb wiki",
      "text": " IndieWeb User:Tantek.com"
    },
    "https://en.wikipedia.org/wiki/User:Tantek": {
      "rels": [
        "me"
      ],
      "title": "contributions to Wikipedia",
      "text": " Wikipedia User:Tantek"
    }
  }
}
microformats2-encoded data for https://tantek.com/ represented as JSON.

Command Line Interface

Use command line utilities like curl or Wget to directly query micromicro.cc.
curl --header 'Accept: application/json' --silent 'https://micromicro.cc/search?url=https://tantek.com/' wget --header 'Accept: application/json' --quiet -O - 'https://micromicro.cc/search?url=https://tantek.com/'