Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2024-09-02 22:32-0700",
    "url": "https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed",
    "category": [
        "Mastodon",
        "fediverse",
        "indieweb",
        "ActivityPub",
        "100PostsOfIndieWeb",
        "100Posts"
    ],
    "content": {
        "text": "Adventures in IndieWeb / ActivityPub (AP) bridging:\n\nWhile in general my posts are being successfully federated by https://fed.brid.gy/ (#BridgyFed), my most recent three posts, and two more earlier this year, were delivered successfully to multiple #Mastodon instances AP inboxes (returned 202), however the posts do not show up if you look-up my profile on those instances (and thus followers never saw them).\n\nThese most recent posts:\n* https://tantek.com/2024/245/t1/read-write-suggest-edit-web\n* https://tantek.com/2024/242/t1/indiewebcamp-portland\n* https://tantek.com/2024/238/t3/indiewebcamp-auto-linking\nand these earlier this year:\n* https://tantek.com/2024/173/t1/years-posse-microformats-adoption\n* https://tantek.com/2024/044/t1/twenty-years-microformats\n\nwere all delivered to over 300 instances, which returned \"202\" codes, however none of them show up in profile views on those instances, e.g.\n* https://indieweb.social/@tantek.com@tantek.com\n* https://mastodon.social/@tantek.com@tantek.com\n* https://social.coop/@tantek.com@tantek.com\n* https://w3c.social/@tantek.com@tantek.com\n(My most recent post on all of these is the same 2024-08-25 post starting with \u201cAll setup here at IndieWebCamp Portland!\u201d)\n\nWhy would a Mastodon instance respond with a 202 to an AP inbox delivery and then not show that post on the local profile view?\n\nGitHub tracking bug in case you can help narrow/track this down or have \n* https://github.com/snarfed/bridgy-fed/issues/884\n\nLet\u2019s see if this post makes it to your Mastodon (or other #fediverse) reader/client.\n\n#indieweb #ActivityPub \n\nThis is post 21 of #100PostsOfIndieWeb. #100Posts\n\n\u2190 https://tantek.com/2024/245/t1/read-write-suggest-edit-web\n\u2192 \ud83d\udd2e",
        "html": "Adventures in IndieWeb / ActivityPub (AP) bridging:<br /><br />While in general my posts are being successfully federated by <a href=\"https://fed.brid.gy/\">https://fed.brid.gy/</a> (#BridgyFed), my most recent three posts, and two more earlier this year, were delivered successfully to multiple #<span class=\"p-category\">Mastodon</span> instances AP inboxes (returned 202), however the posts do not show up if you look-up my profile on those instances (and thus followers never saw them).<br /><br />These most recent posts:<br />* <a href=\"https://tantek.com/2024/245/t1/read-write-suggest-edit-web\">https://tantek.com/2024/245/t1/read-write-suggest-edit-web</a><br />* <a href=\"https://tantek.com/2024/242/t1/indiewebcamp-portland\">https://tantek.com/2024/242/t1/indiewebcamp-portland</a><br />* <a href=\"https://tantek.com/2024/238/t3/indiewebcamp-auto-linking\">https://tantek.com/2024/238/t3/indiewebcamp-auto-linking</a><br />and these earlier this year:<br />* <a href=\"https://tantek.com/2024/173/t1/years-posse-microformats-adoption\">https://tantek.com/2024/173/t1/years-posse-microformats-adoption</a><br />* <a href=\"https://tantek.com/2024/044/t1/twenty-years-microformats\">https://tantek.com/2024/044/t1/twenty-years-microformats</a><br /><br />were all delivered to over 300 instances, which returned \"202\" codes, however none of them show up in profile views on those instances, e.g.<br />* <a href=\"https://indieweb.social/@tantek.com@tantek.com\">https://indieweb.social/@tantek.com@tantek.com</a><br />* <a href=\"https://mastodon.social/@tantek.com@tantek.com\">https://mastodon.social/@tantek.com@tantek.com</a><br />* <a href=\"https://social.coop/@tantek.com@tantek.com\">https://social.coop/@tantek.com@tantek.com</a><br />* <a href=\"https://w3c.social/@tantek.com@tantek.com\">https://w3c.social/@tantek.com@tantek.com</a><br />(My most recent post on all of these is the same 2024-08-25 post starting with \u201cAll setup here at IndieWebCamp Portland!\u201d)<br /><br />Why would a Mastodon instance respond with a 202 to an AP inbox delivery and then not show that post on the local profile view?<br /><br />GitHub tracking bug in case you can help narrow/track this down or have <br />* <a href=\"https://github.com/snarfed/bridgy-fed/issues/884\">https://github.com/snarfed/bridgy-fed/issues/884</a><br /><br />Let\u2019s see if this post makes it to your Mastodon (or other #<span class=\"p-category\">fediverse</span>) reader/client.<br /><br />#<span class=\"p-category\">indieweb</span> #<span class=\"p-category\">ActivityPub</span> <br /><br />This is post 21 of #<span class=\"p-category\">100PostsOfIndieWeb</span>. #<span class=\"p-category\">100Posts</span><br /><br />\u2190 <a href=\"https://tantek.com/2024/245/t1/read-write-suggest-edit-web\">https://tantek.com/2024/245/t1/read-write-suggest-edit-web</a><br />\u2192 \ud83d\udd2e"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "https://tantek.com/",
        "photo": "https://tantek.com/photo.jpg"
    },
    "post-type": "note",
    "_id": "42119534",
    "_source": "2460"
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2024-09-01 14:51-0700",
    "url": "https://tantek.com/2024/245/t1/read-write-suggest-edit-web",
    "category": [
        "IndieWebCamp",
        "Mastodon",
        "ActivityPub",
        "IndieWeb",
        "readWriteWeb",
        "editableWeb",
        "suggestEdit",
        "acceptEdit",
        "100PostsOfIndieWeb",
        "100Posts"
    ],
    "content": {
        "text": "\u270f\ufe0f I want the Read Write Suggest-Edit Accept-Edit Update Web.\n\nThe consumer Infinite Scroll Web leaves us feeling empty.\n\nToo few of us participate in the Read Write Web, whether with personal sites or Wikipedia.\n\nA week ago when we wrapped up #IndieWebCamp Portland and I was reading @KevinMarks.com (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) live-tooting of the demos\u00b9, I noticed a few errors, typos or miscaptures, and pointed them out in-person.\n\nKevin was able to quickly edit his toots and update them for anyone reading, thanks to #Mastodon\u2019s post editing feature and its support of #ActivityPub Updates. But this shouldn\u2019t require being in the same room, IRL or chat.\n\nWe should be able to suggest edits to each other\u2019s posts, as easily as we can reply and add a comment.\n\n13 years ago I wrote\u00b2:\n\n\u00a0\u201cThe Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.\u201d\n\nNow I want the Read Write Suggest-Edit Accept-Edit Update Web.\n\nThe \u21aa Reply button is fairly ubiquitous in modern post user interfaces (UIs).\n\nWhy not also a \u270f\ufe0f Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid \"performative\" suggested edits.\n\nIf the author\u2019s posts provide revision histories, when a suggested edit is accepted, a post\u2019s history could show the contributor of the edit.\n\nInstead of asking Kevin in-person, what if I could have posted special \"Suggested Edit\" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots?\n\nTo enable such UIs and interactions across servers and implementations, we may need a new type of response\u00b3, perhaps with a special property (or more) to convey the edits being suggested.\n\nThere is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #IndieWeb wiki:\n* https://indieweb.org/edit\n\nOur interaction after IndieWebCamp has inspired me to take another look at how can we design and prototype solutions to this problem.\n\nFor now, if you host your blog and posts as static files on GitHub (or equivalent), you could add a button like this to your posts alongside Like, Reply, Repost buttons:\n\n\u270f\ufe0f Suggest Edit\n\nand link it to an edit URL for the static file for the post.\n\nI don\u2019t use GitHub static files myself for posts, but here\u2019s an example of such an edit link for one of my projects:\n\nhttps://tantek.com/github/cassis/edit/main/README.md\n\nThis will start the process of creating a \u201cpull request\u201d, GitHub\u2019s jargon\u2074 for a \u201csuggested edit\u201d.\n\nAfter completing GitHub\u2019s ceremony of entering multiple text fields (summary & description), and multiple clicks to create said \u201cpull request\u201d, it\u2019ll be sent to the author to review. Presuming the author likes the suggested edit, they can perform the other half of GitHub\u2019s jargon-filled ceremonies to \u201cMerge\u201d or \u201cSquash & Merge\u201d, \u201cDelete fork\u201d, etc. to accept the edit.\n\nIt\u2019s an awkward interaction\u2075, however useful for at least prototyping a \u270f\ufe0f Suggest Edit button on sites that store their posts as files in GitHub. Certainly worthy of experimenting with and gathering experience to design and build even better interactions.\n\nWe can start with the shortest path to getting something working, then learn, iterate, improve, repeat.\n\n#readWriteWeb #editableWeb #suggestEdit #acceptEdit\n\nReferences:\n\n\u00b9 https://indieweb.social/@kevinmarks/113025295600067213\n\u00b2 https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11\n\u00b3 https://indieweb.org/responses\n\u2074 The phrase \u201cpull request\u201d was derived from the git command: \u201cgit request-pull\u201d according to https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/\n\u2075 \u201cedits\u201d in GitHub require taking far more steps, and navigating far more jargon, then say, Wikipedia pages, which come down to \u201cEdit\u201d and \u201cSave\u201d. We should aspire to Wikipedia\u2019s simplicity, not GitHub\u2019s ceremonies.\n\nThis is post 20 of #100PostsOfIndieWeb. #100Posts\n\n\u2190 https://tantek.com/2024/242/t1/indiewebcamp-portland\n\u2192 \ud83d\udd2e",
        "html": "\u270f\ufe0f I want the Read Write Suggest-Edit Accept-Edit Update Web.<br /><br />The consumer Infinite Scroll Web leaves us feeling empty.<br /><br />Too few of us participate in the Read Write Web, whether with personal sites or Wikipedia.<br /><br />A week ago when we wrapped up #<span class=\"p-category\">IndieWebCamp</span> Portland and I was reading <a href=\"https://KevinMarks.com\">@KevinMarks.com</a> (<a href=\"https://indieweb.social/@kevinmarks\">@kevinmarks@indieweb.social</a> <a href=\"https://xoxo.zone/@kevinmarks\">@kevinmarks@xoxo.zone</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/kevinmarks\">@kevinmarks</a>) live-tooting of the demos<a href=\"https://tantek.com/#t5Yn1_note-1\">\u00b9</a>, I noticed a few errors, typos or miscaptures, and pointed them out in-person.<br /><br />Kevin was able to quickly edit his toots and update them for anyone reading, thanks to #<span class=\"p-category\">Mastodon</span>\u2019s post editing feature and its support of #<span class=\"p-category\">ActivityPub</span> Updates. But this shouldn\u2019t require being in the same room, IRL or chat.<br /><br />We should be able to suggest edits to each other\u2019s posts, as easily as we can reply and add a comment.<br /><br />13 years ago I wrote<a href=\"https://tantek.com/#t5Yn1_note-2\">\u00b2</a>:<br /><br />\u00a0\u201cThe Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.\u201d<br /><br />Now I want the Read Write Suggest-Edit Accept-Edit Update Web.<br /><br />The \u21aa Reply button is fairly ubiquitous in modern post user interfaces (UIs).<br /><br />Why not also a \u270f\ufe0f Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid \"performative\" suggested edits.<br /><br />If the author\u2019s posts provide revision histories, when a suggested edit is accepted, a post\u2019s history could show the contributor of the edit.<br /><br />Instead of asking Kevin in-person, what if I could have posted special \"Suggested Edit\" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots?<br /><br />To enable such UIs and interactions across servers and implementations, we may need a new type of response<a href=\"https://tantek.com/#t5Yn1_note-3\">\u00b3</a>, perhaps with a special property (or more) to convey the edits being suggested.<br /><br />There is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #<span class=\"p-category\">IndieWeb</span> wiki:<br />* <a href=\"https://indieweb.org/edit\">https://indieweb.org/edit</a><br /><br />Our interaction after IndieWebCamp has inspired me to take another look at how can we design and prototype solutions to this problem.<br /><br />For now, if you host your blog and posts as static files on GitHub (or equivalent), you could add a button like this to your posts alongside Like, Reply, Repost buttons:<br /><br />\u270f\ufe0f Suggest Edit<br /><br />and link it to an edit URL for the static file for the post.<br /><br />I don\u2019t use GitHub static files myself for posts, but here\u2019s an example of such an edit link for one of my projects:<br /><br /><a href=\"https://tantek.com/github/cassis/edit/main/README.md\">https://tantek.com/github/cassis/edit/main/README.md</a><br /><br />This will start the process of creating a \u201cpull request\u201d, GitHub\u2019s jargon<a href=\"https://tantek.com/#t5Yn1_note-4\">\u2074</a> for a \u201csuggested edit\u201d.<br /><br />After completing GitHub\u2019s ceremony of entering multiple text fields (summary &amp; description), and multiple clicks to create said \u201cpull request\u201d, it\u2019ll be sent to the author to review. Presuming the author likes the suggested edit, they can perform the other half of GitHub\u2019s jargon-filled ceremonies to \u201cMerge\u201d or \u201cSquash &amp; Merge\u201d, \u201cDelete fork\u201d, etc. to accept the edit.<br /><br />It\u2019s an awkward interaction<a href=\"https://tantek.com/#t5Yn1_note-5\">\u2075</a>, however useful for at least prototyping a \u270f\ufe0f Suggest Edit button on sites that store their posts as files in GitHub. Certainly worthy of experimenting with and gathering experience to design and build even better interactions.<br /><br />We can start with the shortest path to getting something working, then learn, iterate, improve, repeat.<br /><br />#<span class=\"p-category\">readWriteWeb</span> #<span class=\"p-category\">editableWeb</span> #<span class=\"p-category\">suggestEdit</span> #<span class=\"p-category\">acceptEdit</span><br /><br />References:<br /><br /><a href=\"https://tantek.com/#t5Yn1_ref-1\">\u00b9</a> <a href=\"https://indieweb.social/@kevinmarks/113025295600067213\">https://indieweb.social/@kevinmarks/113025295600067213</a><br /><a href=\"https://tantek.com/#t5Yn1_ref-2\">\u00b2</a> <a href=\"https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11\">https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11</a><br /><a href=\"https://tantek.com/#t5Yn1_ref-3\">\u00b3</a> <a href=\"https://indieweb.org/responses\">https://indieweb.org/responses</a><br /><a href=\"https://tantek.com/#t5Yn1_ref-4\">\u2074</a> The phrase \u201cpull request\u201d was derived from the git command: \u201cgit request-pull\u201d according to <a href=\"https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/\">https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/</a><br /><a href=\"https://tantek.com/#t5Yn1_ref-5\">\u2075</a> \u201cedits\u201d in GitHub require taking far more steps, and navigating far more jargon, then say, Wikipedia pages, which come down to \u201cEdit\u201d and \u201cSave\u201d. We should aspire to Wikipedia\u2019s simplicity, not GitHub\u2019s ceremonies.<br /><br />This is post 20 of #<span class=\"p-category\">100PostsOfIndieWeb</span>. #<span class=\"p-category\">100Posts</span><br /><br />\u2190 <a href=\"https://tantek.com/2024/242/t1/indiewebcamp-portland\">https://tantek.com/2024/242/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": "42117830",
    "_source": "2460"
}

Aaron Parecki aaronparecki.com

Thoguhts on the Resiliency of Web Projects

{
    "type": "entry",
    "published": "2024-08-31T18:36:50-07:00",
    "summary": "I just did a massive spring cleaning of one of my servers, trying to clean up what has become quite the mess of clutter. For every website on the server, I either:",
    "url": "https://aaronparecki.com/2024/08/31/9/too-many-projects",
    "category": [
        "indieweb",
        "clutter",
        "projects",
        "100daysofmusic",
        "biketheeclipse"
    ],
    "name": "Thoguhts on the Resiliency of Web Projects",
    "author": {
        "type": "card",
        "name": "Aaron Parecki",
        "url": "https://aaronparecki.com/",
        "photo": "https://aperture-media.p3k.io/aaronparecki.com/41061f9de825966faa22e9c42830e1d4a614a321213b4575b9488aa93f89817a.jpg"
    },
    "post-type": "article",
    "_id": "42100438",
    "_source": "16"
}

Marty McGuire martymcgui.re

Elizabeth Street Garden

{
    "type": "entry",
    "published": "2024-08-31T14:11:25-0400",
    "summary": "\ud83d\udccd Checked in at Elizabeth Street Garden, New York, NY.",
    "url": "https://martymcgui.re/2024/08/31/141125/",
    "photo": [
        "https://res.cloudinary.com/schmarty/image/fetch/w_960,c_fill/https://fastly.4sqi.net/img/general/original/62057__NSec6W8CHJaaA_q_QCvb7lIFxWWeVFdBEhkjHH9a78.jpg",
        "https://res.cloudinary.com/schmarty/image/fetch/w_960,c_fill/https://fastly.4sqi.net/img/general/original/62057_8UE3lLfOwwqa64x7MEpz5QW-4mKG-PIVQ-K7ViE_YHg.jpg",
        "https://res.cloudinary.com/schmarty/image/fetch/w_960,c_fill/https://fastly.4sqi.net/img/general/original/62057_gCPJg8Myca3rXF5MAs02gWMwiBSmVAtAdAQkbGgaCR4.jpg"
    ],
    "syndication": [
        "https://www.swarmapp.com/user/62057/checkin/66d35ccd25c39b75af261f6d"
    ],
    "content": {
        "text": "Enjoying endangered gardens",
        "html": "<a href=\"https://fastly.4sqi.net/img/general/original/62057__NSec6W8CHJaaA_q_QCvb7lIFxWWeVFdBEhkjHH9a78.jpg\"></a>\n\n      <a href=\"https://fastly.4sqi.net/img/general/original/62057_8UE3lLfOwwqa64x7MEpz5QW-4mKG-PIVQ-K7ViE_YHg.jpg\"></a>\n\n      <a href=\"https://fastly.4sqi.net/img/general/original/62057_gCPJg8Myca3rXF5MAs02gWMwiBSmVAtAdAQkbGgaCR4.jpg\"></a>\n\n  <p>Enjoying endangered gardens</p>"
    },
    "author": {
        "type": "card",
        "name": "Marty McGuire",
        "url": "https://martymcgui.re/",
        "photo": "https://martymcgui.re/images/logo.jpg"
    },
    "checkin": {
        "type": "card",
        "name": "Elizabeth Street Garden",
        "latitude": "40.722137737137",
        "longitude": "-73.994744314711",
        "locality": "New York",
        "region": "NY",
        "url": "https://foursquare.com/v/4a9032caf964a5207b1620e3"
    },
    "post-type": "checkin",
    "_id": "42098026",
    "_source": "175"
}

fluffy beesbuzz.biz

Show went well

{
    "type": "entry",
    "published": "2024-08-30T21:43:25-07:00",
    "url": "https://beesbuzz.biz/blog/10305-Show-went-well",
    "name": "Show went well",
    "author": {
        "type": "card",
        "name": "fluffy",
        "url": "https://beesbuzz.biz/",
        "photo": "https://beesbuzz.biz/static/headshot.jpg"
    },
    "post-type": "article",
    "_id": "42091914",
    "_source": "2778"
}

Aaron Parecki aaronparecki.com

{
    "type": "entry",
    "published": "2024-08-30T18:47:44-07:00",
    "url": "https://aaronparecki.com/2024/08/30/16/bluescsi",
    "category": [
        "macintosh",
        "bluescsi"
    ],
    "photo": [
        "https://aperture-media.p3k.io/aaronparecki.com/e5e60d9b809fb0c3492a302f0947e03a58d67f06ff80aece407652f2119dc3f7.jpg"
    ],
    "content": {
        "text": "well well well... what have we here! Just did some surgery on this Mac SE and replaced the hard drive with a BlueSCSI and it's alive! \n\nNow I just have to upgrade this to 4mb RAM and then we'll be in business!",
        "html": "well well well... what have we here! Just did some surgery on this Mac SE and replaced the hard drive with a BlueSCSI and it's alive! <br /><br />Now I just have to upgrade this to 4mb RAM and then we'll be in business!"
    },
    "author": {
        "type": "card",
        "name": "Aaron Parecki",
        "url": "https://aaronparecki.com/",
        "photo": "https://aperture-media.p3k.io/aaronparecki.com/41061f9de825966faa22e9c42830e1d4a614a321213b4575b9488aa93f89817a.jpg"
    },
    "post-type": "photo",
    "_id": "42091128",
    "_source": "16"
}

Marty McGuire martymcgui.re

{
    "type": "entry",
    "published": "2024-08-30T17:05:04-0400",
    "url": "https://martymcgui.re/2024/08/30/170504/",
    "content": {
        "text": "Thanks to Matthew for reading my post on recent IndieWeb discourse and adding a new section with his responses and notifying me about it via email.\nThere are certainly a number of things in Matthew\u2019s response that tempt me to respond, but I\u2019d like to focus on this:\n\nI am, nevertheless, a little annoyed by the exhortation to \u201ctalk with us\u201d. What does it look like I\u2019m doing over here, anyway? Oh, no, it\u2019s not good enough to post one\u2019s opinion on the web. I\u2019m supposed to use one of the IndieWeb\u2019s chats, either IRC, Slack, or Discord. [\u2026] I am already talking with you. I\u2019m doing it here, on my own website for all to see, in the best IndieWeb tradition. And you are talking to me if you quote me on your own website or email me.\n\nI don\u2019t consider my post a reply to Matthew\u2019s post. I do not see his post as an invitation to conversation. I read it as a \u201ctake\u201d - an opinion piece intended to make the reader feel a certain way and then close the topic, complete with clickbait headline.\nI shouldn\u2019t have to point out that bloggers-blogging-at-bloggers has a long history of unproductive conversation. Reducing the impact of unproductive conversations is part is why there\u2019s not an IndieWeb mailing list. It\u2019s easy in these formats to go hard on the abstract, and to spend time constructing arguments instead of asking questions.\nThat\u2019s not to say that posts can\u2019t inspire change. In the past day or so indieweb.org/discuss has been updated to mention right in the opening sentence that the IRC, web, Slack, and Discord chats are all bridged. Discussions have also kicked up (not for the first time) around making the homepage more welcoming, focusing on principles first, etc.\nThose changes are being decided in the real-time chat, where you can meet and talk with the individuals (all volunteers!) who make up the IndieWeb community. I reckon it beats trying to reverse-engineer that community from a wiki.",
        "html": "<p>Thanks to <a href=\"https://starbreaker.org/\">Matthew</a> for reading my <a href=\"https://martymcgui.re/2024/08/29/141602/\">post on recent IndieWeb discourse</a> and adding <a href=\"https://starbreaker.org/blog/tech/has-indieweb-become-irrelevant/index.html#update-2024-08-30\">a new section with his responses</a> and notifying me about it via email.</p>\n<p>There are certainly a number of things in Matthew\u2019s response that tempt me to respond, but I\u2019d like to focus on this:</p>\n<blockquote>\n<p>I am, nevertheless, a little annoyed by the exhortation to \u201ctalk with us\u201d. What does it look like I\u2019m doing over here, anyway? Oh, no, it\u2019s not good enough to post one\u2019s opinion on the web. I\u2019m supposed to use one of the IndieWeb\u2019s chats, either IRC, Slack, or Discord. [\u2026] I am already talking with you. I\u2019m doing it here, on my own website for all to see, in the best IndieWeb tradition. And you are talking to me if you quote me on your own website or email me.</p>\n</blockquote>\n<p>I don\u2019t consider my post a <em>reply</em> to Matthew\u2019s post. I do not see his post as an invitation to conversation. I read it as a \u201ctake\u201d - an opinion piece intended to make the reader feel a certain way and then close the topic, complete with <a href=\"https://en.wikipedia.org/wiki/Betteridge's_law_of_headlines\">clickbait headline</a>.</p>\n<p>I shouldn\u2019t have to point out that bloggers-blogging-at-bloggers has a long history of <a href=\"https://en.wikipedia.org/wiki/Flaming_(Internet)#Flame_war\">unproductive conversation</a>. Reducing the impact of unproductive conversations is part is <a href=\"https://indieweb.org/FAQ#Is_there_an_IndieWeb_mailing_list\">why there\u2019s not an IndieWeb mailing list</a>. It\u2019s easy in these formats to go hard on the abstract, and to spend time constructing arguments instead of asking questions.</p>\n<p>That\u2019s not to say that posts can\u2019t <em>inspire</em> change. In the past day or so <a href=\"https://indieweb.org/discuss\">indieweb.org/discuss</a> has been updated to mention right in the opening sentence that the IRC, web, Slack, and Discord chats are all bridged. Discussions have also kicked up (<a href=\"https://indieweb.org/site-homepage\">not for the first time</a>) around making the homepage more welcoming, focusing on principles first, etc.</p>\n<p>Those changes are being decided in the <a href=\"https://indieweb.org/discuss\">real-time chat</a>, where you can meet and talk with the individuals (all volunteers!) who make up the IndieWeb community. I reckon it beats trying to reverse-engineer that community from a wiki.</p>"
    },
    "author": {
        "type": "card",
        "name": "Marty McGuire",
        "url": "https://martymcgui.re/",
        "photo": "https://martymcgui.re/images/logo.jpg"
    },
    "post-type": "note",
    "_id": "42090265",
    "_source": "175"
}

Jonathan LaCour cleverdevil.io/profile/cleverdevil

🇺🇸 New Hat #WhiteDudesForHarris

{
    "type": "entry",
    "published": "2024-08-30T21:39:35+00:00",
    "url": "https://cleverdevil.io/2024/-new-hat-whitedudesforharris",
    "photo": [
        "https://cleverdevil.io/file/fca0c7a4b0370207cbf02062a32d56cd/thumb.jpg"
    ],
    "syndication": [
        "https://cleverdevil.club/@jonathan/113053137467476067",
        "https://bsky.app/profile/cleverdevil.io/post/3l2xpqundmj2w"
    ],
    "name": "\ud83c\uddfa\ud83c\uddf8 New Hat #WhiteDudesForHarris",
    "author": {
        "type": "card",
        "name": "Jonathan LaCour",
        "url": "https://cleverdevil.io/profile/cleverdevil",
        "photo": "https://cleverdevil.io/file/e37c3982acf4f0a8421d085b9971cd71/thumb.jpg"
    },
    "post-type": "photo",
    "_id": "42090218",
    "_source": "10"
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2024-08-29 21:09-0700",
    "url": "https://tantek.com/2024/242/t1/indiewebcamp-portland",
    "category": [
        "IndieWebCamp",
        "IndieWeb",
        "100PostsOfIndieWeb",
        "100Posts",
        "2024_238"
    ],
    "content": {
        "text": "Had a great time at IndieWebCamp Portland 2024 this past Sunday \u2014 our 10th IndieWebCamp in Portland!\n\nhttps://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k\n\nBeing a one day #IndieWebCamp, we focused more on making, hacking, and creating, than on formal discussion sessions.\n\nNearly everyone gave a brief personal site intro with a summary of how they use their #IndieWeb site and what they would like to add, remove, or improve.\n* https://indieweb.org/2024/Portland/Intros\n\nThere were lots of informal discussions, some in the main room, on the walk to and from lunch, over lunch in the nearby outdoor patio, or at tables inside the lobby of the Hotel Grand Stark.\n\nWe wrapped up with our usual Create Day\u00b9 Demos session, live streamed for remote attendees to see as well. Lots of great demos of things people built, designed, removed, cleaned-up, documented, and blogged! Everyone still at the camp showed something on their personal site!\n* https://indieweb.org/2024/Portland/Demos\n\nGroup photo and lots more about IndieWebCamp Portland 2024 at the event\u2019s wiki page:\n* https://indieweb.org/2024/Portland\n\n\nThanks to everyone who pitched in to help organize IndieWebCamp Portland 2024! Thanks especially to Marty McGuire (@martymcgui.re) for taking live notes during both the personal site intros and create day demos, to @KevinMarks.com (@kevinmarks@xoxo.zone @kevinmarks @kevinmarks@indieweb.social) for the IndieWebCamp live-tooting, and Ryan Barrett (@snarfed.org) for amazing breakfast pastries from Dos Hermanos.\n\nThe experience definitely raised our hopes and confidence for returning to Portland in 2025.\u00b2\n\n\nReferences:\n\u00b9 https://indieweb.org/Create_Day\n\u00b2 https://indieweb.org/Planning#Portland\n\nThis is post 19 of #100PostsOfIndieWeb. #100Posts #2024_238\n\n\u2190 https://tantek.com/2024/238/t3/indiewebcamp-auto-linking\n\u2192 \ud83d\udd2e",
        "html": "Had a great time at IndieWebCamp Portland 2024 this past Sunday \u2014 our 10th IndieWebCamp in 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 />Being a one day #<span class=\"p-category\">IndieWebCamp</span>, we focused more on making, hacking, and creating, than on formal discussion sessions.<br /><br />Nearly everyone gave a brief personal site intro with a summary of how they use their #<span class=\"p-category\">IndieWeb</span> site and what they would like to add, remove, or improve.<br />* <a href=\"https://indieweb.org/2024/Portland/Intros\">https://indieweb.org/2024/Portland/Intros</a><br /><br />There were lots of informal discussions, some in the main room, on the walk to and from lunch, over lunch in the nearby outdoor patio, or at tables inside the lobby of the Hotel Grand Stark.<br /><br />We wrapped up with our usual Create Day<a href=\"https://tantek.com/#t5Yj1_note-1\">\u00b9</a> Demos session, live streamed for remote attendees to see as well. Lots of great demos of things people built, designed, removed, cleaned-up, documented, and blogged! Everyone still at the camp showed something on their personal site!<br />* <a href=\"https://indieweb.org/2024/Portland/Demos\">https://indieweb.org/2024/Portland/Demos</a><br /><br />Group photo and lots more about IndieWebCamp Portland 2024 at the event\u2019s wiki page:<br />* <a href=\"https://indieweb.org/2024/Portland\">https://indieweb.org/2024/Portland</a><br /><br /><br />Thanks to everyone who pitched in to help organize IndieWebCamp Portland 2024! Thanks especially to Marty McGuire (<a href=\"https://martymcgui.re\">@martymcgui.re</a>) for taking live notes during both the personal site intros and create day demos, to <a href=\"https://KevinMarks.com\">@KevinMarks.com</a> (<a href=\"https://xoxo.zone/@kevinmarks\">@kevinmarks@xoxo.zone</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/kevinmarks\">@kevinmarks</a> <a href=\"https://indieweb.social/@kevinmarks\">@kevinmarks@indieweb.social</a>) for the IndieWebCamp live-tooting, and Ryan Barrett (<a href=\"https://snarfed.org\">@snarfed.org</a>) for amazing breakfast pastries from Dos Hermanos.<br /><br />The experience definitely raised our hopes and confidence for returning to Portland in 2025.<a href=\"https://tantek.com/#t5Yj1_note-2\">\u00b2</a><br /><br /><br />References:<br /><a href=\"https://tantek.com/#t5Yj1_ref-1\">\u00b9</a> <a href=\"https://indieweb.org/Create_Day\">https://indieweb.org/Create_Day</a><br /><a href=\"https://tantek.com/#t5Yj1_ref-2\">\u00b2</a> <a href=\"https://indieweb.org/Planning#Portland\">https://indieweb.org/Planning#Portland</a><br /><br />This is post 19 of #<span class=\"p-category\">100PostsOfIndieWeb</span>. #<span class=\"p-category\">100Posts</span> #<span class=\"p-category\">2024_238</span><br /><br />\u2190 <a href=\"https://tantek.com/2024/238/t3/indiewebcamp-auto-linking\">https://tantek.com/2024/238/t3/indiewebcamp-auto-linking</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": "42081829",
    "_source": "2460"
}

Marty McGuire martymcgui.re

{
    "type": "entry",
    "published": "2024-08-29T15:35:57-0400",
    "url": "https://martymcgui.re/2024/08/29/153557/",
    "syndication": [
        "https://fed.brid.gy/"
    ],
    "content": {
        "text": "Sharing for my fedi-peeps. That\u2019s a term, right?\nHas the IndieWeb become discourse, again?\nhttps://martymcgui.re/2024/08/29/141602/",
        "html": "<p>Sharing for my fedi-peeps. That\u2019s a term, right?</p>\n<p>Has the IndieWeb become discourse, again?\n<a href=\"https://martymcgui.re/2024/08/29/141602/\">https://martymcgui.re/2024/08/29/141602/</a></p>"
    },
    "author": {
        "type": "card",
        "name": "Marty McGuire",
        "url": "https://martymcgui.re/",
        "photo": "https://martymcgui.re/images/logo.jpg"
    },
    "post-type": "note",
    "_id": "42079767",
    "_source": "175"
}

Marty McGuire martymcgui.re

Has the IndieWeb become discourse again?

{
    "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"
}

fluffy beesbuzz.biz

TODO

{
    "type": "entry",
    "published": "2024-08-29T13:31:20-07:00",
    "url": "https://beesbuzz.biz/blog/15202-TODO",
    "name": "TODO",
    "author": {
        "type": "card",
        "name": "fluffy",
        "url": "https://beesbuzz.biz/",
        "photo": "https://beesbuzz.biz/static/headshot.jpg"
    },
    "post-type": "article",
    "_id": "42078550",
    "_source": "2778"
}

fluffy beesbuzz.biz

Bandcrash updated

{
    "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"
}

Marty McGuire martymcgui.re

{
    "type": "entry",
    "published": "2024-08-28T12:39:52-0400",
    "url": "https://martymcgui.re/2024/08/28/123952/",
    "category": [
        "Caturday"
    ],
    "video": [
        "https://res.cloudinary.com/schmarty/video/upload/vc_h264/mmmgre/e8/4d/db/05/6c06f5834013751d834b7fa9699a7d8b7dcd93c215510d6843340bab.mov"
    ],
    "content": {
        "text": "Are you safely stowed away during eternal Caturday?",
        "html": "<p>Are you safely stowed away during eternal Caturday?</p>"
    },
    "author": {
        "type": "card",
        "name": "Marty McGuire",
        "url": "https://martymcgui.re/",
        "photo": "https://martymcgui.re/images/logo.jpg"
    },
    "post-type": "video",
    "_id": "42067006",
    "_source": "175"
}

Marty McGuire martymcgui.re

{
    "type": "entry",
    "published": "2024-08-27T10:21:18-0400",
    "url": "https://martymcgui.re/2024/08/27/102118/",
    "category": [
        "Caturday"
    ],
    "video": [
        "https://res.cloudinary.com/schmarty/video/upload/vc_h264/mmmgre/88/fc/9b/80/3d81c6debe27d946e4b3814363d6e83cbe3aa525fe6bb67c2991e9b2.mov"
    ],
    "content": {
        "text": "Are you giving it your all during eternal Caturday?",
        "html": "<p>Are you giving it your all during eternal Caturday?</p>"
    },
    "author": {
        "type": "card",
        "name": "Marty McGuire",
        "url": "https://martymcgui.re/",
        "photo": "https://martymcgui.re/images/logo.jpg"
    },
    "post-type": "video",
    "_id": "42054864",
    "_source": "175"
}

Marty McGuire martymcgui.re

Study Hall

{
    "type": "entry",
    "published": "2024-08-25T17:46:49-0700",
    "summary": "\ud83d\udccd Checked in at Study Hall, Portland, OR.",
    "url": "https://martymcgui.re/2024/08/25/204649/",
    "syndication": [
        "https://www.swarmapp.com/user/62057/checkin/66cbd0799b82b01d883b7c40"
    ],
    "author": {
        "type": "card",
        "name": "Marty McGuire",
        "url": "https://martymcgui.re/",
        "photo": "https://martymcgui.re/images/logo.jpg"
    },
    "checkin": {
        "type": "card",
        "name": "Study Hall",
        "latitude": "45.51906",
        "longitude": "-122.660927",
        "locality": "Portland",
        "region": "OR",
        "url": "https://foursquare.com/v/66cb54ba4e5df94392ac317a"
    },
    "post-type": "checkin",
    "_id": "42037508",
    "_source": "175"
}

Tantek Çelik tantek.com

{
    "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"
}

Tantek Çelik tantek.com

{
    "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"
}

fluffy beesbuzz.biz

Upcoming VRChat performances

{
    "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"
}

Marty McGuire martymcgui.re

🔐🕸️💍 Restored sign-in options for an IndieWeb webring

{
    "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 &lt;a rel=\"me\" ... &gt;). 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"
}