{
"type": "entry",
"published": "2024-08-29T14:16:02-0400",
"url": "https://martymcgui.re/2024/08/29/141602/",
"category": [
"IndieWeb",
"discourse"
],
"syndication": [
"https://news.indieweb.org/en/"
],
"name": "Has the IndieWeb become discourse again?",
"content": {
"text": "I recently read Has the IndieWeb Become Irrelevant from starbreaker.org.\nThe post does a great job linking to and summarizing a spate of posts that I\nwill call \u201cpeople being mad at the IndieWeb\u201d, while also being one of these posts.\nThese posts accuse \u201cthe IndieWeb\u201d of being elitist, exclusionary,\noverengineered, complicit, and unnecessary, among many other things.\nThere are some common threads I noticed among these posts:\nNone of them mention micro.blog!\nThey seem to attack a \u201cstraw person\u201d version of the IndieWeb, where one is\nexpected to read, follow, and implement over a decade of experimentation on the web.\nMicro.blog is real\nFolks that would like to try a turnkey website hosting service, where:\nyou bring your own domain (or register a new one!)\nyou can leave and take your content with you whenever you want\nrequires no coding (and no plugins to configure, and no \u201cfiles and folders\u201d)\noffers mobile and desktop apps that let you post (and read) the kinds of content you want\nsupports IndieWeb building blocks to let you follow and interact with other\npeople via your own websites\nI don\u2019t see eye-to-eye with its creator Manton Reese about everything, but\nmicro.blog is a great example of a real world service that makes use of IndieWeb\nbuilding blocks in ways that customers benefit from without having to build\nanything!\nThe rest is wiki\nI think many of other complaints, from being \u201coverengineered\u201d to (paraphased)\n\u201cPOSSE makes IndieWeb complicit with the corporate web\u201d, come from misconstruing\nthe IndieWeb wiki at indieweb.org as the entirety of\n\u201cbeing IndieWeb\u201d.\nWhen I discovered indieweb.org (in maybe 2015?) I was intrigued and nearly\ninstantly overwhelemed. Trying to absorb all the concepts there would\nbe nearly impossible. Understanding and implementing all the techniques there is\nactually impossible.\nThat\u2019s because indieweb.org is not a presciption or a cookbook or\nan exercise plan. It doesn\u2019t tell you how to \u201cbe IndieWeb\u201d. It\u2019s a collective\nmemory of experiments, some successful and some not, from a group of\nexperimenters that has changed greatly over time.\nFor example, I find that criticisms like \u201cf*ck the corporate web and f*ck\nIndieWeb for interoperating with the corporate web\u201d don\u2019t really hold up when\na lot of that stuff doesn\u2019t even work anymore.\nOn corporate complicity\nAutomatic POSSE, syndicating posts from your own\nsite out to your profiles on social silos, only ever barely (and briefly)\nworked for Instagram, was turned off for Facebook a few years ago, and was all\nbut destroyed for Twitter shortly after its last acquisition. backfeed -\npulling comments and likes from these platforms to display on your own site -\nhas similarly been blocked by technical measures.\nThese were experiments that worked for a time. People used them for a time. That\ntime has passed and the people have moved on.\nSome folks have replaced their Twitter usage with something like Mastodon, or\nBlue Sky, or Threads, and amazing people like Ryan have\nstepped up to help experiment with bridging personal sites and federated services.\nThere is no \u201cthe way\u201d, only \u201cyour way\u201d\nPeople don\u2019t have to move on for purely technical reasons. Even before\nTwitter closed their APIs, many in the IndieWeb community were shuttering their\nTwitter accounts and removing posts. They moved on from Twitter, despite all\nthose documented pages on the IndieWeb wiki, because they didn\u2019t want to use\nthe web this way anymore.\nAnd to me, this is actually what \u201cbeing IndieWeb\u201d or \u201cdoing IndieWeb\u201d is\nabout: using the web in ways that fit your wants and needs, being mindful of\nwhen (and to whom) you give up control over your stuff and your connections.\nFiguring out how you want to use the web is a daunting task, to say the least!\nThe IndieWeb wiki is full of interesting examples and ideas - but as a logbook\nof ways of using the web, it can be inscrutable. It was never intended that\nevery way of using the web would be suitable for everyone. A collective memory\nis extremely hard to keep up-to-date and to signpost for navigation. Trying to\nrely on the wiki alone is a recipe for frustration.\nI freely admit that the community has fallen into some serious prescriptive\ntraps over time. Like with tools like indiewebify.me\nthat offer a checklist of implementation details, without accompanying reasons\nwhy you might want these features.\nThis isn\u2019t the first time this has happened, by any means, and it won\u2019t be the\nlast, but the criticisms of these tools and models do make their way back into\nthe collective memory. (see: generations\nand IndieMark)\nTalk with us\nThat\u2019s why the IndieWeb chat exists. It\u2019s a\nplace where real actual people, who are working to use the web in ways that\nsuit them, are ready to help in whatever ways we can. We love to share what is\n(and is not) working for us, what we\u2019re trying, and so on. More importantly, we\nwant to help you find ways of using the web that work for you.",
"html": "<p>I recently read <a href=\"https://starbreaker.org/blog/tech/has-indieweb-become-irrelevant/\">Has the IndieWeb Become Irrelevant</a> from <a href=\"https://starbreaker.org/\">starbreaker.org</a>.</p>\n<p>The post does a great job linking to and summarizing a spate of posts that I\nwill call \u201cpeople being mad at the IndieWeb\u201d, while also <em>being</em> one of these posts.</p>\n<p>These posts accuse \u201cthe IndieWeb\u201d of being elitist, exclusionary,\noverengineered, complicit, and unnecessary, among many other things.</p>\n<p>There are some common threads I noticed among these posts:</p>\n<ul><li>None of them mention <a href=\"https://micro.blog/\">micro.blog</a>!</li>\n<li>They seem to attack a \u201cstraw person\u201d version of the IndieWeb, where one is\nexpected to read, follow, and implement over a decade of experimentation on the web.</li>\n</ul><h2>Micro.blog is real</h2>\n<p>Folks that would like to try a turnkey website hosting service, where:</p>\n<ul><li>you bring your own domain (or register a new one!)</li>\n<li>you can leave and take your content with you whenever you want</li>\n<li>requires no coding (and no plugins to configure, and no \u201cfiles and folders\u201d)</li>\n<li>offers mobile and desktop apps that let you post (and read) the kinds of content you want</li>\n<li>supports IndieWeb building blocks to let you follow and interact with other\npeople via your own websites</li>\n</ul><p>I don\u2019t see eye-to-eye with its creator Manton Reese about everything, but\nmicro.blog is a great example of a real world service that makes use of IndieWeb\nbuilding blocks in ways that customers benefit from without having to build\nanything!</p>\n<h2>The rest is wiki</h2>\n<p>I think many of other complaints, from being \u201coverengineered\u201d to (paraphased)\n\u201cPOSSE makes IndieWeb complicit with the corporate web\u201d, come from misconstruing\nthe <a href=\"https://indieweb.org/\"><em>IndieWeb wiki</em> at indieweb.org</a> as the entirety of\n\u201cbeing IndieWeb\u201d.</p>\n<p>When I discovered indieweb.org (in maybe 2015?) I was intrigued and nearly\ninstantly overwhelemed. Trying to absorb all the concepts there would\nbe nearly impossible. Understanding and implementing all the techniques there is\n<em>actually</em> impossible.</p>\n<p>That\u2019s because indieweb.org is not a presciption or a cookbook or\nan exercise plan. It doesn\u2019t tell you how to \u201cbe IndieWeb\u201d. It\u2019s a <em>collective\nmemory</em> of experiments, some successful and some not, from a group of\nexperimenters that has changed greatly over time.</p>\n<p>For example, I find that criticisms like \u201cf*ck the corporate web and f*ck\nIndieWeb for interoperating with the corporate web\u201d don\u2019t really hold up when\n<em>a lot of that stuff doesn\u2019t even work anymore</em>.</p>\n<h3>On corporate complicity</h3>\n<p>Automatic <a href=\"https://indieweb.org/POSSE\">POSSE</a>, syndicating posts from your own\nsite out to your profiles on social silos, only ever barely (and briefly)\nworked for Instagram, was turned off for Facebook a few years ago, and was all\nbut destroyed for Twitter shortly after its last acquisition. <a href=\"https://indieweb.org/backfeed\">backfeed</a> -\npulling comments and likes from these platforms to display on your own site -\nhas similarly been blocked by technical measures.</p>\n<p>These were experiments that worked for a time. People used them for a time. That\ntime has passed and the people have moved on.</p>\n<p>Some folks have replaced their Twitter usage with something like Mastodon, or\nBlue Sky, or Threads, and amazing people like <a href=\"https://snarfed.org/\">Ryan</a> have\nstepped up to help experiment with <a href=\"https://fed.brid.gy/\">bridging personal sites and federated services</a>.</p>\n<h2>There is no \u201cthe way\u201d, only \u201cyour way\u201d</h2>\n<p>People don\u2019t have to move on for purely technical reasons. Even before\nTwitter closed their APIs, many in the IndieWeb community were shuttering their\nTwitter accounts and removing posts. They moved on from Twitter, despite all\nthose documented pages on the IndieWeb wiki, because <em>they didn\u2019t want to use\nthe web this way anymore</em>.</p>\n<p>And to me, this is <em>actually</em> what \u201cbeing IndieWeb\u201d or \u201cdoing IndieWeb\u201d is\nabout: using the web in ways that fit your wants and needs, being mindful of\nwhen (and to whom) you give up control over your stuff and your connections.</p>\n<p>Figuring out how <em>you</em> want to use the web is a daunting task, to say the least!\nThe IndieWeb wiki is full of interesting examples and ideas - but as a logbook\nof ways of using the web, it can be inscrutable. It was never intended that\nevery way of using the web would be suitable for everyone. A collective memory\nis extremely hard to keep up-to-date and to signpost for navigation. Trying to\nrely on the wiki alone is a recipe for frustration.</p>\n<p>I freely admit that the community has fallen into some serious prescriptive\ntraps over time. Like with tools like <a href=\"https://indiewebify.me/\">indiewebify.me</a>\nthat offer a checklist of implementation details, without accompanying reasons\n<em>why</em> you might want these features.</p>\n<p>This isn\u2019t the first time this has happened, by any means, and it won\u2019t be the\nlast, but the criticisms of these tools and models do make their way back into\nthe collective memory. (see: <a href=\"https://indieweb.org/generations\">generations</a>\nand <a href=\"https://indieweb.org/IndieMark\">IndieMark</a>)</p>\n<h2>Talk with us</h2>\n<p>That\u2019s why the <a href=\"https://indieweb.org/discuss\">IndieWeb chat</a> exists. It\u2019s a\nplace where real actual people, who are working to use the web in ways that\nsuit them, are ready to help in whatever ways we can. We love to share what is\n(and is not) working for us, what we\u2019re trying, and so on. More importantly, we\nwant to help <em>you</em> find ways of using the web that work for you.</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "article",
"_id": "42079768",
"_source": "175"
}
{
"type": "entry",
"published": "2024-08-29T01:07:43-07:00",
"url": "https://beesbuzz.biz/blog/6564-Bandcrash-updated",
"name": "Bandcrash updated",
"content": {
"text": "Well, this is silly: I just discovered that Bandcrash doesn\u2019t properly escape HTML entities in the web preview player. Or rather, it didn\u2019t. It does now, as of v0.7.9.",
"html": "<p>Well, this is silly: I just discovered that <a href=\"https://fluffy.itch.io/bandcrash\">Bandcrash</a> doesn\u2019t properly escape HTML entities in the web preview player. Or rather, it didn\u2019t. It does now, as of v0.7.9.</p>"
},
"author": {
"type": "card",
"name": "fluffy",
"url": "https://beesbuzz.biz/",
"photo": "https://beesbuzz.biz/static/headshot.jpg"
},
"post-type": "article",
"_id": "42072587",
"_source": "2778"
}
I’ve implemented an auto_link function² that handles quite a few use-cases of URLs (with or without http: or https:), @-name @-domain @-domain/path @-@-handles, hashtags(#), and footnotes(^).
Much of it is based on what I’ve seen work (or implemented) on sites and software, and some of it is based on logically extending how people are using text punctuation across various services.
It may be time for me to write-up an auto-link specification based on the algorithms I’ve come up with, implemented, and am using live on my site. All the algorithms work fully offline (none of them require querying a site for more info, whether well-known or otherwise), so they can be used in offline-first authoring/writing clients.
I have identified three logical chunks of auto-linking functionality, each of which has different constraints and potential needs for local to the linking context information (like hashtags need a default tagspace). Each would be a good section for a new specification. Each is used by this very post.
{
"type": "entry",
"published": "2024-08-25 16:00-0700",
"url": "https://tantek.com/2024/238/t3/indiewebcamp-auto-linking",
"category": [
"IndieWebCamp",
"IndieWeb",
"autoLink",
"hashtag",
"hashtags",
"footnote",
"footnotes",
"100PostsOfIndieWeb",
"100Posts"
],
"content": {
"text": "Nice #IndieWebCamp discussion session with @KevinMarks.com (@kevinmarks@xoxo.com @kevinmarks) on the topic of auto-linking\u00b9.\n\nI\u2019ve implemented an auto_link function\u00b2 that handles quite a few use-cases of URLs (with or without http: or https:), @-name @-domain @-domain/path @-@-handles, hashtags(#), and footnotes(^).\n\nMuch of it is based on what I\u2019ve seen work (or implemented) on sites and software, and some of it is based on logically extending how people are using text punctuation across various services.\n\nIt may be time for me to write-up an auto-link specification based on the algorithms I\u2019ve come up with, implemented, and am using live on my site. All the algorithms work fully offline (none of them require querying a site for more info, whether well-known or otherwise), so they can be used in offline-first authoring/writing clients.\n\nI have identified three logical chunks of auto-linking functionality, each of which has different constraints and potential needs for local to the linking context information (like hashtags need a default tagspace). Each would be a good section for a new specification. Each is used by this very post.\n\n* URLs, @-s, and @-@-s\n* # hashtags\n* ^ footnotes\n\n#IndieWeb #autoLink #hashtag #hashtags #footnote #footnotes\n\nPreviously, previously, previously:\n* https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases\n* https://tantek.com/2023/100/t1/auto-linked-hashtags-federated\n* https://tantek.com/2023/043/t1/footnotes-unicode-links\n* https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo\n\nReferences:\n\u00b9 https://indieweb.org/autolink\n\u00b2 https://github.com/tantek/cassis/blob/main/cassis.js\n\nThis is post 18 of #100PostsOfIndieWeb. #100Posts\n\n\u2190 https://tantek.com/2024/238/t1/indiewebcamp-portland\n\u2192 \ud83d\udd2e",
"html": "Nice #<span class=\"p-category\">IndieWebCamp</span> discussion session with <a href=\"https://KevinMarks.com\">@KevinMarks.com</a> (<a href=\"https://xoxo.com/@kevinmarks\">@kevinmarks@xoxo.com</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/kevinmarks\">@kevinmarks</a>) on the topic of auto-linking<a href=\"https://tantek.com/#t5Yf3_note-1\">\u00b9</a>.<br /><br />I\u2019ve implemented an auto_link function<a href=\"https://tantek.com/#t5Yf3_note-2\">\u00b2</a> that handles quite a few use-cases of URLs (with or without http: or https:), @-name @-domain @-domain/path @-@-handles, hashtags(#), and footnotes(^).<br /><br />Much of it is based on what I\u2019ve seen work (or implemented) on sites and software, and some of it is based on logically extending how people are using text punctuation across various services.<br /><br />It may be time for me to write-up an auto-link specification based on the algorithms I\u2019ve come up with, implemented, and am using live on my site. All the algorithms work fully offline (none of them require querying a site for more info, whether well-known or otherwise), so they can be used in offline-first authoring/writing clients.<br /><br />I have identified three logical chunks of auto-linking functionality, each of which has different constraints and potential needs for local to the linking context information (like hashtags need a default tagspace). Each would be a good section for a new specification. Each is used by this very post.<br /><br />* URLs, @-s, and @-@-s<br />* # hashtags<br />* ^ footnotes<br /><br />#<span class=\"p-category\">IndieWeb</span> #<span class=\"p-category\">autoLink</span> #<span class=\"p-category\">hashtag</span> #<span class=\"p-category\">hashtags</span> #<span class=\"p-category\">footnote</span> #<span class=\"p-category\">footnotes</span><br /><br />Previously, previously, previously:<br />* <a href=\"https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases\">https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases</a><br />* <a href=\"https://tantek.com/2023/100/t1/auto-linked-hashtags-federated\">https://tantek.com/2023/100/t1/auto-linked-hashtags-federated</a><br />* <a href=\"https://tantek.com/2023/043/t1/footnotes-unicode-links\">https://tantek.com/2023/043/t1/footnotes-unicode-links</a><br />* <a 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 /><br />References:<br /><a href=\"https://tantek.com/#t5Yf3_ref-1\">\u00b9</a> <a href=\"https://indieweb.org/autolink\">https://indieweb.org/autolink</a><br /><a href=\"https://tantek.com/#t5Yf3_ref-2\">\u00b2</a> <a href=\"https://github.com/tantek/cassis/blob/main/cassis.js\">https://github.com/tantek/cassis/blob/main/cassis.js</a><br /><br />This is post 18 of #<span class=\"p-category\">100PostsOfIndieWeb</span>. #<span class=\"p-category\">100Posts</span><br /><br />\u2190 <a href=\"https://tantek.com/2024/238/t1/indiewebcamp-portland\">https://tantek.com/2024/238/t1/indiewebcamp-portland</a><br />\u2192 \ud83d\udd2e"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "42036989",
"_source": "2460"
}
Good crowd of participants from #XOXO #XOXOConf (@xoxofest.com@xoxo@xoxo.zone@xoxo) here to work on their personal website(s), domains, or other independent social media setups!
“Every one of you should have a home on the web not controlled by a billionaire.”
If you’re in #Portland and want help, encouragement, or camaraderie in getting setup or doing more with your personal site, come on by! We’ll be having a mix of discussion sessions and create/hack sessions.
{
"type": "entry",
"published": "2024-08-25 10:18-0700",
"url": "https://tantek.com/2024/238/t1/indiewebcamp-portland",
"category": [
"XOXO",
"XOXOConf",
"Portland",
"indieweb",
"fediverse",
"ActivityPub",
"decentralized",
"socialMedia",
"100PostsOfIndieWeb",
"100Posts"
],
"content": {
"text": "All setup here at IndieWebCamp Portland!\n\nhttps://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k\n\nGood crowd of participants from #XOXO #XOXOConf (@xoxofest.com @xoxo@xoxo.zone @xoxo) here to work on their personal website(s), domains, or other independent social media setups!\n\nAs encouraged by Andy Baio (@waxy.org @andybaio@xoxo.zone @waxpancake)\n\n\u201cEvery one of you should have a home on the web not controlled by a billionaire.\u201d\n\nIf you\u2019re in #Portland and want help, encouragement, or camaraderie in getting setup or doing more with your personal site, come on by! We\u2019ll be having a mix of discussion sessions and create/hack sessions. \n\nPersonal site and hack demos at 16:00 PDT!\n\n#indieweb #fediverse #ActivityPub #decentralized #socialMedia\n\nThis is post 17 of #100PostsOfIndieWeb. #100Posts\n\n\u2190 https://tantek.com/2024/237/t1/people-over-protocols-platforms\n\u2192 https://tantek.com/2024/238/t3/indiewebcamp-auto-linking",
"html": "All setup here at IndieWebCamp Portland!<br /><br /><a href=\"https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k\">https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k</a><br /><br />Good crowd of participants from #<span class=\"p-category\">XOXO</span> #<span class=\"p-category\">XOXOConf</span> (<a href=\"https://xoxofest.com\">@xoxofest.com</a> <a href=\"https://xoxo.zone/@xoxo\">@xoxo@xoxo.zone</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/xoxo\">@xoxo</a>) here to work on their personal website(s), domains, or other independent social media setups!<br /><br />As encouraged by Andy Baio (<a href=\"https://waxy.org\">@waxy.org</a> <a href=\"https://xoxo.zone/@andybaio\">@andybaio@xoxo.zone</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/waxpancake\">@waxpancake</a>)<br /><br />\u201cEvery one of you should have a home on the web not controlled by a billionaire.\u201d<br /><br />If you\u2019re in #<span class=\"p-category\">Portland</span> and want help, encouragement, or camaraderie in getting setup or doing more with your personal site, come on by! We\u2019ll be having a mix of discussion sessions and create/hack sessions. <br /><br />Personal site and hack demos at 16:00 PDT!<br /><br />#<span class=\"p-category\">indieweb</span> #<span class=\"p-category\">fediverse</span> #<span class=\"p-category\">ActivityPub</span> #<span class=\"p-category\">decentralized</span> #<span class=\"p-category\">socialMedia</span><br /><br />This is post 17 of #<span class=\"p-category\">100PostsOfIndieWeb</span>. #<span class=\"p-category\">100Posts</span><br /><br />\u2190 <a href=\"https://tantek.com/2024/237/t1/people-over-protocols-platforms\">https://tantek.com/2024/237/t1/people-over-protocols-platforms</a><br />\u2192 <a href=\"https://tantek.com/2024/238/t3/indiewebcamp-auto-linking\">https://tantek.com/2024/238/t3/indiewebcamp-auto-linking</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "42036991",
"_source": "2460"
}
{
"type": "entry",
"published": "2024-08-25T15:33:27-07:00",
"url": "https://beesbuzz.biz/blog/4415-Upcoming-VRChat-performances",
"name": "Upcoming VRChat performances",
"content": {
"text": "I have two upcoming VRChat performances happening.\nOn Wednesday, August 28, at 7 PM PDT, I will be performing a song off my upcoming album Transitions at the Trans Academy\u2019s \u201cMoonlit Academy\u201d concert series. Join the Trans Academy group for access to the instance.\nOn Friday, August 30, at 3 PM PDT, I will be playing a full set of my songs in-world. This will also be streamed to my owncast instance for folks who are unable to join in VR (and I\u2019ll hopefully record it for YouTube as well), but for the best experience, join my VRChat group for the easiest instance access.\nI hope to see you there!",
"html": "<p>I have two upcoming VRChat performances happening.</p>\n<ol><li>On Wednesday, August 28, at <a href=\"https://time.is/compare/0700pm_28_Aug_2024_in_Seattle?Sockpuppet_@_Moonlit_Academy\">7 PM PDT</a>, I will be performing a song off my upcoming album Transitions at the Trans Academy\u2019s \u201cMoonlit Academy\u201d concert series. Join the <a href=\"https://vrc.group/TRANS7885\">Trans Academy group</a> for access to the instance.</li>\n<li>On Friday, August 30, at <a href=\"https://time.is/compare/0300pm_30_Aug_2024_in_Seattle?Sockpuppet_@_VRChat\">3 PM PDT</a>, I will be playing a full set of my songs in-world. This will also be streamed to <a href=\"https://live.sockpuppet.us/\">my owncast instance</a> for folks who are unable to join in VR (and I\u2019ll hopefully record it for YouTube as well), but for the best experience, join <a href=\"https://vrc.group/PLAID.8330\">my VRChat group</a> for the easiest instance access.</li>\n</ol><p>I hope to see you there!</p>"
},
"author": {
"type": "card",
"name": "fluffy",
"url": "https://beesbuzz.biz/",
"photo": "https://beesbuzz.biz/static/headshot.jpg"
},
"post-type": "article",
"_id": "42036721",
"_source": "2778"
}
{
"type": "entry",
"published": "2024-08-25T16:32:50-0400",
"url": "https://martymcgui.re/2024/08/25/restored-sign-in-options-for-an-indieweb-webring/",
"category": [
"\ud83d\udd78\ufe0f\ud83d\udc8d",
"webring",
"indieweb",
"update",
"IndieAuth",
"RelMeAuth"
],
"name": "\ud83d\udd10\ud83d\udd78\ufe0f\ud83d\udc8d Restored sign-in options for an IndieWeb webring",
"content": {
"text": "Are you a member of the \ud83d\udd78\ufe0f\ud83d\udc8d IndieWeb Webring? Or have you wanted to be, but you couldn't sign in because it strictly required IndieAuth for sign-in?\nI was recently gently reminded that the IndieWeb webring at one time allowed you to verify your identity using an alternative sign-in mechanism. For instance, by making bi-directional links between your home page and your GitHub account, you can delegate the step of \"proving\" that you are the person in control of your homepage to GitHub, and let them worry about storing and checking usernames and passwords.\nThis concept is called RelMeAuth (because it works by embedding links in your homepage let look like <a rel=\"me\" ... >). The original version of the webring would first check to see if your site specifies its own IndieAuth provider and, if not, would fall back to using Aaron Parecki's indielogin.com, which handles checking for these rel=\"me\" links to supported sites. It also supports sending codes to your email, if you prefer!\nSo it used to work?\nYeah! I, uh, broke it when I moved the site over to PHP some time ago.\nBut it works now?\nIt should! If your homepage has no IndieAuth server specified, but has rel=\"me\" links to your GitHub or an email \"mailto:\" link, you should be able to sign in to the webring using those methods!\nIt was broken for how long?\n\ud83d\ude05 it was fixed within a day of someone telling me it was broken!\nPlease don't share any links to code-\nHere are the updates I added today to enable indielogin.com support. Some of it is a little hacky until indielogin.com is updated to allow the full client_id URL for the webring, but it works OK!\nSigh, ok.\nOkay that's it, for now! Thanks for reading, imaginary interlocutor! As always, feel free to reply to this post on your own site, or feel free to drop me a line in the #indieweb chat (I\u2019m schmarty there)!",
"html": "<p>Are you a member of the <a href=\"https://xn--sr8hvo.ws/\">\ud83d\udd78\ufe0f\ud83d\udc8d IndieWeb Webring</a>? Or have you wanted to be, but you couldn't sign in because it strictly required <a href=\"https://indieweb.org/IndieAuth\">IndieAuth</a> for sign-in?</p>\n<p>I was recently gently reminded that the IndieWeb webring <i>at one time</i> allowed you to verify your identity using an alternative sign-in mechanism. For instance, by making bi-directional links between your home page and your GitHub account, you can delegate the step of \"proving\" that you are the person in control of your homepage to GitHub, and let them worry about storing and checking usernames and passwords.</p>\n<p>This concept is called <a href=\"https://indieweb.org/RelMeAuth\">RelMeAuth</a> (because it works by embedding links in your homepage let look like <a rel=\"me\" ... >). The original version of the webring would first check to see if your site specifies its own IndieAuth provider and, if not, would fall back to using <a href=\"https://aaronparecki.com/\">Aaron Parecki</a>'s <a href=\"https://indielogin.com/\">indielogin.com</a>, which handles checking for these rel=\"me\" links to supported sites. It also supports sending codes to your email, if you prefer!</p>\n<h2>So it used to work?</h2>\n<p>Yeah! I, uh, broke it when I moved the site over to PHP <i>some time ago</i>.</p>\n<h2>But it works now?</h2>\n<p>It should! If your homepage has no IndieAuth server specified, but has rel=\"me\" links to your GitHub or an email \"mailto:\" link, you should be able to sign in to the webring using those methods!</p>\n<h2>It was broken for how long?</h2>\n<p>\ud83d\ude05 it was fixed within a day of someone telling me it was broken!</p>\n<h2>Please don't share any links to code-</h2>\n<p>Here are <a href=\"https://git.schmarty.net/schmarty/gem-diamond/commit/44883aa0c1478696901d1ad457cd5e59e0943171\">the updates I added today to enable indielogin.com support</a>. Some of it is a little hacky until indielogin.com is updated to allow the full client_id URL for the webring, but it works OK!</p>\n<h2>Sigh, ok.</h2>\n<p>Okay that's it, for now! Thanks for reading, imaginary interlocutor! As always, feel free to <a href=\"https://indieweb.org/reply\">reply</a> to this post on your own site, or feel free to drop me a line in the <a href=\"https://chat.indieweb.org/\">#indieweb chat</a> (I\u2019m <code>schmarty</code> there)!</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "article",
"_id": "42035691",
"_source": "175"
}