📗 Want to read Says Who?: A Kinder, Funner Usage Guide for Everyone Who Cares about Words by Anne Curzan ISBN: 9780593444092
{
"type": "entry",
"published": "2024-09-07T14:26:50-0400",
"summary": "\ud83d\udcd7 Want to read Says Who?: A Kinder, Funner Usage Guide for Everyone Who Cares about Words by Anne Curzan ISBN: 9780593444092",
"url": "https://martymcgui.re/2024/09/07/142650/",
"category": [
"books"
],
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "note",
"_id": "42169023",
"_source": "175"
}
📗 Want to read Mobility by Lydia Kiesling ISBN: 9781638930563
{
"type": "entry",
"published": "2024-09-07T14:17:29-0400",
"summary": "\ud83d\udcd7 Want to read Mobility by Lydia Kiesling ISBN: 9781638930563",
"url": "https://martymcgui.re/2024/09/07/141729/",
"category": [
"books"
],
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "note",
"_id": "42169024",
"_source": "175"
}
📗 Want to read How We Show Up: Reclaiming Family, Friendship, and Community by Mia Birdsong ISBN: 9781580058070
{
"type": "entry",
"published": "2024-09-07T14:16:51-0400",
"summary": "\ud83d\udcd7 Want to read How We Show Up: Reclaiming Family, Friendship, and Community by Mia Birdsong ISBN: 9781580058070",
"url": "https://martymcgui.re/2024/09/07/141651/",
"category": [
"books"
],
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "note",
"_id": "42169025",
"_source": "175"
}
📗 Want to read Emergent Strategy: Shaping Change, Changing Worlds by Adrienne Maree Brown ISBN: 9781849352604
{
"type": "entry",
"published": "2024-09-07T14:16:08-0400",
"summary": "\ud83d\udcd7 Want to read Emergent Strategy: Shaping Change, Changing Worlds by Adrienne Maree Brown ISBN: 9781849352604",
"url": "https://martymcgui.re/2024/09/07/141608/",
"category": [
"books"
],
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "note",
"_id": "42169026",
"_source": "175"
}
{
"type": "entry",
"published": "2024-09-06T18:09:38-0400",
"summary": "\ud83d\udccd Checked in at Fourth Avenue Pub, Brooklyn, NY.",
"url": "https://martymcgui.re/2024/09/06/180938/",
"photo": [
"https://res.cloudinary.com/schmarty/image/fetch/w_960,c_fill/https://fastly.4sqi.net/img/general/original/62057_d0LslrAakrEPn6W-pljy9kZpXylYS1epe1-sCjkKR5g.jpg",
"https://res.cloudinary.com/schmarty/image/fetch/w_960,c_fill/https://fastly.4sqi.net/img/general/original/62057_FZa_wb4L9rjmmDySv98XCCDvhacPNkPqFBSSdEmiY5E.jpg",
"https://res.cloudinary.com/schmarty/image/fetch/w_960,c_fill/https://fastly.4sqi.net/img/general/original/62057_Av8SkYXPvz-S4JZy5lLO5icUvBgXF8qp-lEyNL3a2Ls.jpg"
],
"syndication": [
"https://www.swarmapp.com/user/62057/checkin/66db7da2fedc0219a07e784d"
],
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"checkin": {
"type": "card",
"name": "Fourth Avenue Pub",
"latitude": "40.682296530899",
"longitude": "-73.98002654314",
"locality": "Brooklyn",
"region": "NY",
"url": "https://foursquare.com/v/4587e9aef964a520cf3f1fe3"
},
"post-type": "checkin",
"_id": "42161667",
"_source": "175"
}
{
"type": "entry",
"author": {
"name": "Jared White",
"url": "https://jaredwhite.com/",
"photo": null
},
"url": "https://jaredwhite.com/links/20240906/recumbant-bicycles",
"published": "2024-09-06T09:46:35-07:00",
"content": {
"html": "<blockquote>\n <h2><a href=\"https://momentummag.com/best-reasons-benefits-recumbent-bicycles/\"></a></h2>\n\n <p>While traditional bicycles have been the staple for decades, there\u2019s a fascinating alternative that\u2019s been gaining traction in recent years \u2013 the recumbent bicycle. Whether you\u2019re a seasoned cyclist or someone looking to embark on a new biking adventure, recumbent bicycles offer an exciting departure from the ordinary. But why switch?</p>\n\n</blockquote>\n\n<p>One of the aspects of the \u201cnew age\u201d of <a href=\"https://jaredwhite.com/tag/micromobility\">#micromobility</a> I\u2019m so excited about is the experimentation around <strong>form factors</strong>. Yes, of course we\u2019ve been seeing many fascinating variations on e-scooters & e-bikes come out in recent years, but even the tried-and-true category of 100% human-powered vehicles has witnessed a recent surge of design variety and innovation.</p>\n\n<p>Watching what people ride here in <a href=\"https://jaredwhite.com/tag/portland\">#Portland</a> has been nothing short of fascinating. And if you get the chance to head out to some of the bike-oriented get-togethers in town, you\u2019ll see some <em>pret-tay, pret-tay, pret-tay</em> intriguing vechicles. <strong>I just love it</strong>. \u263a\ufe0f</p>",
"text": "While traditional bicycles have been the staple for decades, there\u2019s a fascinating alternative that\u2019s been gaining traction in recent years \u2013 the recumbent bicycle. Whether you\u2019re a seasoned cyclist or someone looking to embark on a new biking adventure, recumbent bicycles offer an exciting departure from the ordinary. But why switch?\n\n\n\nOne of the aspects of the \u201cnew age\u201d of #micromobility I\u2019m so excited about is the experimentation around form factors. Yes, of course we\u2019ve been seeing many fascinating variations on e-scooters & e-bikes come out in recent years, but even the tried-and-true category of 100% human-powered vehicles has witnessed a recent surge of design variety and innovation.\n\nWatching what people ride here in #Portland has been nothing short of fascinating. And if you get the chance to head out to some of the bike-oriented get-togethers in town, you\u2019ll see some pret-tay, pret-tay, pret-tay intriguing vechicles. I just love it. \u263a\ufe0f"
},
"name": "Link: The Recumbent Bicycle: Reasons to Buy",
"post-type": "article",
"_id": "42159409",
"_source": "2783"
}
Gotta enjoy outdoor sipping while it’s nice!
{
"type": "entry",
"published": "2024-09-04T20:12:27-0400",
"summary": "\ud83d\udccd Checked in at Bar Veloce, New York, NY.",
"url": "https://martymcgui.re/2024/09/04/201227/",
"photo": [
"https://res.cloudinary.com/schmarty/image/fetch/w_960,c_fill/https://fastly.4sqi.net/img/general/original/62057_BXBDH1S0OEVVFsZS6Fe9LxhuUQ12ULJtnUa18VFPP_c.jpg",
"https://res.cloudinary.com/schmarty/image/fetch/w_960,c_fill/https://fastly.4sqi.net/img/general/original/62057_inJiDWflkq155qJJnn7QesE24LuRmbkjoS9dEJvS6Ao.jpg"
],
"syndication": [
"https://www.swarmapp.com/user/62057/checkin/66d8f76beeaecf4dd2204c5d"
],
"content": {
"text": "Gotta enjoy outdoor sipping while it\u2019s nice!",
"html": "<a href=\"https://fastly.4sqi.net/img/general/original/62057_BXBDH1S0OEVVFsZS6Fe9LxhuUQ12ULJtnUa18VFPP_c.jpg\"></a>\n\n <a href=\"https://fastly.4sqi.net/img/general/original/62057_inJiDWflkq155qJJnn7QesE24LuRmbkjoS9dEJvS6Ao.jpg\"></a>\n\n <p>Gotta enjoy outdoor sipping while it\u2019s nice!</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"checkin": {
"type": "card",
"name": "Bar Veloce",
"latitude": "40.728154",
"longitude": "-74.001897",
"locality": "New York",
"region": "NY",
"url": "https://foursquare.com/v/4a70e5d0f964a520b8d81fe3"
},
"post-type": "checkin",
"_id": "42140546",
"_source": "175"
}
✏️ I want the Read Write Suggest-Edit Accept-Edit Update Web.
The consumer Infinite Scroll Web leaves us feeling empty.
Too few of us participate in the Read Write Web, whether with personal sites or Wikipedia.
A week ago when we wrapped up #IndieWebCamp Portland and I was reading Kevin Marks (@kevinmarks@indieweb.social) live-tooting of the demos¹, I noticed a few errors, typos or miscaptures, and pointed them out in-person.
Kevin was able to quickly edit his toots and update them for anyone reading, thanks to #Mastodon’s post editing feature and its support of #ActivityPub Updates. But this shouldn’t require being in the same room, whether IRL or chat.
We should be able to suggest edits to each other’s posts, as easily as we can reply and add a comment.
13 years ago I wrote²:
“The Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.”
Now I want the Read Write Suggest-Edit Accept-Edit Update Web.
The ↪ Reply button is fairly ubiquitous in modern post user interfaces (UIs).
Why not also a ✏️ Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid "performative" suggested edits.
If the author’s posts provide revision histories, when a suggested edit is accepted, a post’s history could show the contributor of the edit.
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?
To enable such UIs and interactions across servers and implementations, we may need a new type of response³, perhaps with a special property (or more) to convey the edits being suggested.
There is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #IndieWeb wiki:
* https://indieweb.org/edit
Our interaction after IndieWebCamp has inspired me to take another look at how can we design and prototype solutions to this problem.
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:
✏️ Suggest Edit
and link it to an edit URL for the static file for the post.
I don’t use GitHub static files myself for posts, but here’s an example of such an edit link for one of my projects:
https://tantek.com/github/cassis/edit/main/README.md
This will start the process of creating a “pull request”, GitHub’s jargon⁴ for a “suggested edit”.
After completing GitHub’s ceremony of entering multiple text fields (summary & description), and multiple clicks to create said “pull request”, it’ll be sent to the author to review. Presuming the author likes the suggested edit, they can perform the other half of GitHub’s jargon-filled ceremonies to “Merge” or “Squash & Merge”, “Delete fork”, etc. to accept the edit.
It’s an awkward interaction⁵, however useful for at least prototyping a ✏️ Suggest Edit button on sites that store their posts as files in GitHub. Certainly worthy of experimenting with and gathering experience to design and build even better interactions.
We can start with the shortest path to getting something working, then learn, iterate, improve, repeat.
#readWriteWeb #editableWeb #suggestEdit #acceptEdit
References:
¹ https://indieweb.social/@kevinmarks/113025295600067213
² https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11
³ https://indieweb.org/responses
⁴ The phrase “pull request” was derived from the git command: “git request-pull” according to https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/
⁵ “edits” in GitHub require taking far more steps, and navigating far more jargon, then say, Wikipedia pages, which come down to “Edit” and “Save”. We should aspire to Wikipedia’s simplicity, not GitHub’s ceremonies.
This is post 20 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/242/t1/indiewebcamp-portland
→ https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed
{
"type": "entry",
"published": "2024-09-01 14:51-0700",
"url": "https://tantek.com/2024/245/t1/read-write-suggest-edit-update-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 Kevin Marks (@kevinmarks@indieweb.social) 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, whether 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 https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed",
"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 Kevin Marks (<a href=\"https://indieweb.social/@kevinmarks\">@kevinmarks@indieweb.social</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, whether 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 & 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.<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 <a href=\"https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed\">https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "42140455",
"_source": "2460"
}
Had a great time at IndieWebCamp Portland 2024 this past Sunday — our 10th IndieWebCamp in Portland!
https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k
Being a one day #IndieWebCamp, we focused more on making, hacking, and creating, than on formal discussion sessions.
Nearly 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.
* https://indieweb.org/2024/Portland/Intros
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.
We wrapped up with our usual Create Day¹ 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!
* https://indieweb.org/2024/Portland/Demos
Group photo and lots more about IndieWebCamp Portland 2024 at the event’s wiki page:
* https://indieweb.org/2024/Portland
Thanks 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 Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) for the IndieWebCamp live-tooting, and Ryan Barrett (@snarfed.org) for amazing breakfast pastries from Dos Hermanos.
The experience definitely raised our hopes and confidence for returning to Portland in 2025.²
References:
¹ https://indieweb.org/Create_Day
² https://indieweb.org/Planning#Portland
This is post 19 of #100PostsOfIndieWeb. #100Posts #2024_238
← https://tantek.com/2024/238/t3/indiewebcamp-auto-linking
→ https://tantek.com/2024/245/t1/read-write-suggest-edit-web
{
"type": "entry",
"published": "2024-08-29 21:09-0700",
"url": "https://tantek.com/2024/242/t1/indiewebcamp-portland-10",
"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\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 Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) 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\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 https://tantek.com/2024/245/t1/read-write-suggest-edit-web",
"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 />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 Kevin Marks (<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>) 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 /><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 <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>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "42140456",
"_source": "2460"
}
Nice #IndieWebCamp discussion session with Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) on the topic of auto-linking¹.
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.
* URLs, @-s, and @-@-s
* # hashtags
* ^ footnotes
#IndieWeb #autoLink #hashtag #hashtags #footnote #footnotes
Previously, previously, previously:
* https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases
* https://tantek.com/2023/100/t1/auto-linked-hashtags-federated
* https://tantek.com/2023/043/t1/footnotes-unicode-links
* https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo
References:
¹ https://indieweb.org/autolink
² https://github.com/tantek/cassis/blob/main/cassis.js
This is post 18 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/238/t1/indiewebcamp-portland
→ https://tantek.com/2024/242/t1/indiewebcamp-portland
{
"type": "entry",
"published": "2024-08-25 16:00-0700",
"url": "https://tantek.com/2024/238/t3/indiewebcamp-auto-link",
"category": [
"IndieWebCamp",
"IndieWeb",
"autoLink",
"hashtag",
"hashtags",
"footnote",
"footnotes",
"100PostsOfIndieWeb",
"100Posts"
],
"content": {
"text": "Nice #IndieWebCamp discussion session with Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @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\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\n\nReferences:\n\n\u00b9 https://indieweb.org/autolink\n\u00b2 https://github.com/tantek/cassis/blob/main/cassis.js\n\n\nThis is post 18 of #100PostsOfIndieWeb. #100Posts\n\n\u2190 https://tantek.com/2024/238/t1/indiewebcamp-portland\n\u2192 https://tantek.com/2024/242/t1/indiewebcamp-portland",
"html": "Nice #<span class=\"p-category\">IndieWebCamp</span> discussion session with Kevin Marks (<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>) 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 /><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 /><br />References:<br /><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 /><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 <a href=\"https://tantek.com/2024/242/t1/indiewebcamp-portland\">https://tantek.com/2024/242/t1/indiewebcamp-portland</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "42140457",
"_source": "2460"
}
At Bar del Pla in Barcelona
{
"type": "entry",
"author": {
"name": null,
"url": "https://herestomwiththeweather.com/",
"photo": null
},
"url": "https://herestomwiththeweather.com/social/2024/09/04/75579/",
"published": "2024-09-04T20:59:39+00:00",
"content": {
"html": "<p>At Bar del Pla in Barcelona</p>",
"text": "At Bar del Pla in Barcelona"
},
"post-type": "note",
"_id": "42139228",
"_source": "246"
}
If this is hell, I don’t wanna go to heaven.
Happy Labor Day weekend y’all! 🥳
#Portland #OregonExplored
{
"type": "entry",
"author": {
"name": "Jared White",
"url": "https://jaredwhite.com/",
"photo": null
},
"url": "https://jaredwhite.com/pictures/20240830/if-this-is-hell-i-don-t-wanna-go-to-heaven",
"published": "2024-08-30T15:00:13-07:00",
"content": {
"html": "<img alt=\"\" src=\"https://pxscdn.com/public/m/_v2/4580/0e43b1202-69768b/6uL4kviBKFw8/eA0cFTaivFAH1q9ByUrwVLoDp9jPyRnCUJqqlOEC.jpg\" /><p>If this is hell, I don\u2019t wanna go to heaven.</p>\n\n<p>Happy Labor Day weekend y\u2019all! \ud83e\udd73</p>\n\n<p><a href=\"https://jaredwhite.com/tag/portland\">#Portland</a> <a href=\"https://jaredwhite.com/tag/oregonexplored\">#OregonExplored</a></p>",
"text": "If this is hell, I don\u2019t wanna go to heaven.\n\nHappy Labor Day weekend y\u2019all! \ud83e\udd73\n\n#Portland #OregonExplored"
},
"post-type": "note",
"_id": "42136888",
"_source": "2783"
}
#Portland is pleased to boast many fine murals, but this one is definitely my favorite. It’s always a good day when I get to ride past. 😍 #OregonExplored
Artist: Fin DAC
you can find many other fine works of his here
{
"type": "entry",
"author": {
"name": "Jared White",
"url": "https://jaredwhite.com/",
"photo": null
},
"url": "https://jaredwhite.com/pictures/20240824/portland-many-fine-murals",
"published": "2024-08-24T07:17:52-07:00",
"content": {
"html": "<img alt=\"\" src=\"https://pxscdn.com/public/m/_v2/4580/0e43b1202-69768b/5lhL5izycO5S/qcVUGiesfrhtSrFVnuyoFoLuStG4pmmYWLJk3SzI.jpg\" /><p><a href=\"https://jaredwhite.com/tag/portland\">#Portland</a> is pleased to boast many fine murals, but this one is definitely my favorite. It\u2019s always a good day when I get to ride past. \ud83d\ude0d <a href=\"https://jaredwhite.com/tag/oregonexplored\">#OregonExplored</a></p>\n\n<p>Artist: Fin DAC<br />you can find many other fine works of his <a href=\"https://www.streetartbio.com/artists/fin-dac/\">here</a></p>",
"text": "#Portland is pleased to boast many fine murals, but this one is definitely my favorite. It\u2019s always a good day when I get to ride past. \ud83d\ude0d #OregonExplored\n\nArtist: Fin DAC\nyou can find many other fine works of his here"
},
"post-type": "note",
"_id": "42136889",
"_source": "2783"
}
A view of South Waterfront and the Aerial Tram, looking east from the OHSU medical complex.
It was pretty hazy that day, but I still think this is one swell vista!
#Portland #OregonExplored #NikonZfc
{
"type": "entry",
"author": {
"name": "Jared White",
"url": "https://jaredwhite.com/",
"photo": null
},
"url": "https://jaredwhite.com/pictures/20240803/a-view-of-south-waterfront-and-the-aerial-tram-looking",
"published": "2024-08-03T07:50:30-07:00",
"content": {
"html": "<img alt=\"\" src=\"https://pxscdn.com/public/m/_v2/4580/0e43b1202-69768b/zMwc2kYkPQ52/m4F5B45UEm35pOD0rwMDm1DDkVytIARqCwodhDkg.jpg\" /><p>A view of South Waterfront and the Aerial Tram, looking east from the OHSU medical complex.</p>\n\n<p>It was pretty hazy that day, but I still think this is one swell vista!</p>\n\n<p><a href=\"https://jaredwhite.com/tag/portland\">#Portland</a> <a href=\"https://jaredwhite.com/tag/oregonexplored\">#OregonExplored</a> <a href=\"https://jaredwhite.com/tag/nikonzfc\">#NikonZfc</a></p>",
"text": "A view of South Waterfront and the Aerial Tram, looking east from the OHSU medical complex.\n\nIt was pretty hazy that day, but I still think this is one swell vista!\n\n#Portland #OregonExplored #NikonZfc"
},
"post-type": "note",
"_id": "42136890",
"_source": "2783"
}
Dayum, this DJ was on fire! 🔥
At the Pearl 4th of July festival in #Portland. #OregonExplored
{
"type": "entry",
"author": {
"name": "Jared White",
"url": "https://jaredwhite.com/",
"photo": null
},
"url": "https://jaredwhite.com/pictures/20240704/dayum-this-dj-was-on-fire",
"published": "2024-07-04T18:53:50-07:00",
"content": {
"html": "<img alt=\"\" src=\"https://pxscdn.com/public/m/_v2/4580/3781ba7d4-1bb9dc/8dOgr1ByLx5p/xV5u0sEtOU85A43LWYOQpxYsKpEuKVrPOMlcdJu8.jpg\" /><p>Dayum, this DJ was on fire! \ud83d\udd25</p>\n\n<p>At the Pearl 4th of July festival in <a href=\"https://jaredwhite.com/tag/portland\">#Portland</a>. <a href=\"https://jaredwhite.com/tag/oregonexplored\">#OregonExplored</a></p>",
"text": "Dayum, this DJ was on fire! \ud83d\udd25\n\nAt the Pearl 4th of July festival in #Portland. #OregonExplored"
},
"post-type": "note",
"_id": "42136891",
"_source": "2783"
}
This lavender field (I think that’s what it is? lol) at Elizabeth Caruthers Park in #Portland was simply stunning! 🤩 #OregonExplored #nofilter
{
"type": "entry",
"author": {
"name": "Jared White",
"url": "https://jaredwhite.com/",
"photo": null
},
"url": "https://jaredwhite.com/pictures/20240628/this-lavender-field-i-think-that-s-what-it-is-lol",
"published": "2024-06-28T18:07:54-07:00",
"content": {
"html": "<img alt=\"\" src=\"https://pxscdn.com/public/m/_v2/4580/530d83cd3-f15549/6iTa7CZNslZo/b544dQM8afUvqgjQd8a39hBax5qdIKbyZdQq3bcv.jpg\" /><p>This lavender field (I think that\u2019s what it is? lol) at Elizabeth Caruthers Park in <a href=\"https://jaredwhite.com/tag/portland\">#Portland</a> was simply stunning! \ud83e\udd29 <a href=\"https://jaredwhite.com/tag/oregonexplored\">#OregonExplored</a> <a href=\"https://jaredwhite.com/tag/nofilter\">#nofilter</a></p>",
"text": "This lavender field (I think that\u2019s what it is? lol) at Elizabeth Caruthers Park in #Portland was simply stunning! \ud83e\udd29 #OregonExplored #nofilter"
},
"post-type": "note",
"_id": "42136892",
"_source": "2783"
}
A view of #Portland, as seen from the Eastbank Esplanade. #OregonExplored
{
"type": "entry",
"author": {
"name": "Jared White",
"url": "https://jaredwhite.com/",
"photo": null
},
"url": "https://jaredwhite.com/pictures/20240623/a-view-of-portland-eastbank-esplanade",
"published": "2024-06-23T09:09:27-07:00",
"content": {
"html": "<img alt=\"\" src=\"https://pxscdn.com/public/m/_v2/4580/530d83cd3-f15549/9RvRMxSeQCMU/tlHC50XZUIaUv2w7ZJU2jfYYsrBDPCULo56u2jph.jpg\" /><p>A view of <a href=\"https://jaredwhite.com/tag/portland\">#Portland</a>, as seen from the Eastbank Esplanade. <a href=\"https://jaredwhite.com/tag/oregonexplored\">#OregonExplored</a></p>",
"text": "A view of #Portland, as seen from the Eastbank Esplanade. #OregonExplored"
},
"post-type": "note",
"_id": "42136893",
"_source": "2783"
}
Tip: use the W3C Link Checker and fix any errors before federating with Bridgy Fed.
https://validator.w3.org/checklink
If you are using Bridgy Fed to federate your posts from your personal site, I highly recommend you first run the W3C Link Checker on a post, and verify there are no “red” errors (or fix any you find), before pinging Bridgy Fed to federate the post.
The reason is that if your post contains broken links, especially broken https: links as part of an @-mention, a weird set of timeout interactions will occur between #BridgyFed and #Mastodon that will cause any Mastodon instances following your posts to drop your federated posts as if they had not been received.
Further, those instances will also ignore any UPDATES to that post.
More discussion here:
* https://chat.indieweb.org/dev/2024-09-04#t1725421768496000
More bug details here:
* https://github.com/snarfed/bridgy-fed/issues/884#issuecomment-2327861883
#IndieWeb #federate #fediverse #interoperability
This is post 22 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed
→ 🔮
{
"type": "entry",
"published": "2024-09-03 23:11-0700",
"url": "https://tantek.com/2024/247/t4/w3c-link-checker-before-federating",
"category": [
"BridgyFed",
"Mastodon",
"IndieWeb",
"federate",
"fediverse",
"interoperability",
"100PostsOfIndieWeb",
"100Posts"
],
"content": {
"text": "Tip: use the W3C Link Checker and fix any errors before federating with Bridgy Fed.\n\nhttps://validator.w3.org/checklink\n\nIf you are using Bridgy Fed to federate your posts from your personal site, I highly recommend you first run the W3C Link Checker on a post, and verify there are no \u201cred\u201d errors (or fix any you find), before pinging Bridgy Fed to federate the post.\n\nThe reason is that if your post contains broken links, especially broken https: links as part of an @-mention, a weird set of timeout interactions will occur between #BridgyFed and #Mastodon that will cause any Mastodon instances following your posts to drop your federated posts as if they had not been received. \n\nFurther, those instances will also ignore any UPDATES to that post.\n\nMore discussion here:\n* https://chat.indieweb.org/dev/2024-09-04#t1725421768496000\nMore bug details here:\n* https://github.com/snarfed/bridgy-fed/issues/884#issuecomment-2327861883\n\n#IndieWeb #federate #fediverse #interoperability\n\nThis is post 22 of #100PostsOfIndieWeb. #100Posts\n\n\u2190 https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed\n\u2192 \ud83d\udd2e",
"html": "Tip: use the W3C Link Checker and fix any errors before federating with Bridgy Fed.<br /><br /><a href=\"https://validator.w3.org/checklink\">https://validator.w3.org/checklink</a><br /><br />If you are using Bridgy Fed to federate your posts from your personal site, I highly recommend you first run the W3C Link Checker on a post, and verify there are no \u201cred\u201d errors (or fix any you find), before pinging Bridgy Fed to federate the post.<br /><br />The reason is that if your post contains broken links, especially broken https: links as part of an @-mention, a weird set of timeout interactions will occur between #<span class=\"p-category\">BridgyFed</span> and #<span class=\"p-category\">Mastodon</span> that will cause any Mastodon instances following your posts to drop your federated posts as if they had not been received. <br /><br />Further, those instances will also ignore any UPDATES to that post.<br /><br />More discussion here:<br />* <a href=\"https://chat.indieweb.org/dev/2024-09-04#t1725421768496000\">https://chat.indieweb.org/dev/2024-09-04#t1725421768496000</a><br />More bug details here:<br />* <a href=\"https://github.com/snarfed/bridgy-fed/issues/884#issuecomment-2327861883\">https://github.com/snarfed/bridgy-fed/issues/884#issuecomment-2327861883</a><br /><br />#<span class=\"p-category\">IndieWeb</span> #<span class=\"p-category\">federate</span> #<span class=\"p-category\">fediverse</span> #<span class=\"p-category\">interoperability</span><br /><br />This is post 22 of #<span class=\"p-category\">100PostsOfIndieWeb</span>. #<span class=\"p-category\">100Posts</span><br /><br />\u2190 <a href=\"https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed\">https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed</a><br />\u2192 \ud83d\udd2e"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "42130804",
"_source": "2460"
}
Happy 12 years of https://indieweb.org/POSSE #POSSE and
19 years of https://microformats.org/ #microformats! (as of yesterday, the 20th)
A few highlights from the past year:
POSSE (Publish on your Own Site, Syndicate Elsewhere) has grown steadily as a common practice in the #IndieWeb community, personal sites, CMSs (like Withknown, which itself reached 10 years in May!), and services (like https://micro.blog) for over a decade.
In its 12th year, POSSE broke through to broader technology press and adoption beyond the community. For example:
* David Pierce’s (@pierce@mas.to) excellent article @TheVerge.com (@verge@mastodon.social): “The poster’s guide to the internet of the future” (https://www.theverge.com/2023/10/23/23928550/posse-posting-activitypub-standard-twitter-tumblr-mastodon):
“Your post appears natively on all of those platforms, typically with some kind of link back to your blog. And your blog becomes the hub for everything, your main home on the internet.
Done right, POSSE is the best of all posting worlds.”
* David also recorded a 29 minute podcast on POSSE with some great interviews: https://podcasts.apple.com/us/podcast/the-posters-guide-to-the-new-internet/id430333725?i=1000632256014
* Cory Doctorow (@craphound.com @doctorow@mamot.fr) declared in his Pluralistic blog (@pluralistic.net) post: “Vice surrenders” (https://pluralistic.net/2024/02/24/anti-posse/):
“This is the moment for POSSE (Post Own Site, Share Everywhere [sic]), a strategy that sees social media as a strategy for bringing readers to channels that you control”
* And none other than Molly White (@mollywhite.net @molly0xfff@hachyderm.io) of @web3isgoinggreat.com (@web3isgreat@indieweb.social) built, deployed, and started actively using her own POSSE setup as described in her post titled “POSSE” (https://www.mollywhite.net/micro/entry/202403091817) to:
"… write posts in the microblog and automatically crosspost them to Twitter/Mastodon/Bluesky, while keeping the original post on my site."
Congrats Molly and well done!
In its 19th year, the microformats formal #microformats2 syntax and popular vocabularies h-card, h-entry, and h-feed, kept growing across IndieWeb (micro)blogging services and software like CMSs & SSGs both for publishing, and richer peer-to-peer social web interactions via #Webmention.
Beyond the IndieWeb, the rel=me microformat, AKA #relMe, continues to be adopted by services to support #distributed #verification, such as these in the past year:
* Meta Platforms #Threads user profile "Link" field¹
* #Letterboxd user profile website field²
For both POSSE and microformats, there is always more we can do to improve their techniques, technologies, and tools to help people own their content and identities online, while staying connected to friends across the web.
Got suggestions for this coming year? Join us in chat:
* https://chat.indieweb.org/dev
* https://chat.indieweb.org/microformats
for discussions about POSSE and microformats, respectively.
Previously: https://tantek.com/2023/171/t1/anniversaries-microformats-posse
This is post 15 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/151/t1/minimum-interesting-service-worker
→ https://tantek.com/2024/237/t1/people-over-protocols-platforms
Post glossary:
CMS
https://indieweb.org/CMS
h-card
https://microformats.org/wiki/h-card
h-entry
https://microformats.org/wiki/h-entry
h-feed
https://microformats.org/wiki/h-feed
microformats2 syntax
https://microformats.org/wiki/microformats2-parsing
rel-me
https://microformats.org/wiki/rel-me
SSG
https://indieweb.org/SSG
Webmention
https://indieweb.org/Webmention
Withknown
https://indieweb.org/Known
References:
¹ https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me
² https://indieweb.org/rel-me#Letterboxd
{
"type": "entry",
"published": "2024-06-21 22:02-0700",
"url": "https://tantek.com/2024/173/t1/years-posse-microformats-beyond",
"category": [
"POSSE",
"microformats",
"IndieWeb",
"microformats2",
"Webmention",
"relMe",
"distributed",
"verification",
"Threads",
"Letterboxd",
"100PostsOfIndieWeb",
"100Posts"
],
"content": {
"text": "Happy 12 years of https://indieweb.org/POSSE #POSSE and\n19 years of https://microformats.org/ #microformats! (as of yesterday, the 20th)\n\nA few highlights from the past year:\n\nPOSSE (Publish on your Own Site, Syndicate Elsewhere) has grown steadily as a common practice in the #IndieWeb community, personal sites, CMSs (like Withknown, which itself reached 10 years in May!), and services (like https://micro.blog) for over a decade.\n\nIn its 12th year, POSSE broke through to broader technology press and adoption beyond the community. For example:\n\n* David Pierce\u2019s (@pierce@mas.to) excellent article @TheVerge.com (@verge@mastodon.social): \u201cThe poster\u2019s guide to the internet of the future\u201d (https://www.theverge.com/2023/10/23/23928550/posse-posting-activitypub-standard-twitter-tumblr-mastodon):\n\u00a0 \u201cYour post appears natively on all of those platforms, typically with some kind of link back to your blog. And your blog becomes the hub for everything, your main home on the internet.\nDone right, POSSE is the best of all posting worlds.\u201d\n\n* David also recorded a 29 minute podcast on POSSE with some great interviews: https://podcasts.apple.com/us/podcast/the-posters-guide-to-the-new-internet/id430333725?i=1000632256014\n\n* Cory Doctorow (@craphound.com @doctorow@mamot.fr) declared in his Pluralistic blog (@pluralistic.net) post: \u201cVice surrenders\u201d (https://pluralistic.net/2024/02/24/anti-posse/):\n\u00a0 \u201cThis is the moment for POSSE (Post Own Site, Share Everywhere [sic]), a strategy that sees social media as a strategy for bringing readers to channels that you control\u201d \n\n* And none other than Molly White (@mollywhite.net @molly0xfff@hachyderm.io) of @web3isgoinggreat.com (@web3isgreat@indieweb.social) built, deployed, and started actively using her own POSSE setup as described in her post titled \u201cPOSSE\u201d (https://www.mollywhite.net/micro/entry/202403091817) to: \n\u00a0 \"\u2026 write posts in the microblog and automatically crosspost them to Twitter/Mastodon/Bluesky, while keeping the original post on my site.\"\n\u00a0 \nCongrats Molly and well done!\n\n\nIn its 19th year, the microformats formal #microformats2 syntax and popular vocabularies h-card, h-entry, and h-feed, kept growing across IndieWeb (micro)blogging services and software like CMSs & SSGs both for publishing, and richer peer-to-peer social web interactions via #Webmention.\n\nBeyond the IndieWeb, the rel=me microformat, AKA #relMe, continues to be adopted by services to support #distributed #verification, such as these in the past year: \n\n* Meta Platforms #Threads user profile \"Link\" field\u00b9 \n* #Letterboxd user profile website field\u00b2\n\n\nFor both POSSE and microformats, there is always more we can do to improve their techniques, technologies, and tools to help people own their content and identities online, while staying connected to friends across the web.\n\nGot suggestions for this coming year? Join us in chat:\n* https://chat.indieweb.org/dev\n* https://chat.indieweb.org/microformats\nfor discussions about POSSE and microformats, respectively.\n\n\nPreviously: https://tantek.com/2023/171/t1/anniversaries-microformats-posse\n\n\nThis is post 15 of #100PostsOfIndieWeb. #100Posts\n\n\u2190 https://tantek.com/2024/151/t1/minimum-interesting-service-worker\n\u2192 https://tantek.com/2024/237/t1/people-over-protocols-platforms\n\n\nPost glossary:\n\nCMS\n\u00a0 https://indieweb.org/CMS\nh-card\n\u00a0 https://microformats.org/wiki/h-card\nh-entry\n\u00a0 https://microformats.org/wiki/h-entry\nh-feed\n\u00a0 https://microformats.org/wiki/h-feed\nmicroformats2 syntax\n\u00a0 https://microformats.org/wiki/microformats2-parsing\nrel-me\n\u00a0 https://microformats.org/wiki/rel-me\nSSG\n\u00a0 https://indieweb.org/SSG\nWebmention\n\u00a0 https://indieweb.org/Webmention\nWithknown\n\u00a0 https://indieweb.org/Known\n\n\nReferences:\n\n\u00b9 https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me\n\u00b2 https://indieweb.org/rel-me#Letterboxd",
"html": "Happy 12 years of <a href=\"https://indieweb.org/POSSE\">https://indieweb.org/POSSE</a> #<span class=\"p-category\">POSSE</span> and<br />19 years of <a href=\"https://microformats.org/\">https://microformats.org/</a> #<span class=\"p-category\">microformats</span>! (as of yesterday, the 20th)<br /><br />A few highlights from the past year:<br /><br />POSSE (Publish on your Own Site, Syndicate Elsewhere) has grown steadily as a common practice in the #<span class=\"p-category\">IndieWeb</span> community, personal sites, CMSs (like Withknown, which itself reached 10 years in May!), and services (like <a href=\"https://micro.blog\">https://micro.blog</a>) for over a decade.<br /><br />In its 12th year, POSSE broke through to broader technology press and adoption beyond the community. For example:<br /><br />* David Pierce\u2019s (<a href=\"https://mas.to/@pierce\">@pierce@mas.to</a>) excellent article <a href=\"https://TheVerge.com\">@TheVerge.com</a> (<a href=\"https://mastodon.social/@verge\">@verge@mastodon.social</a>): \u201cThe poster\u2019s guide to the internet of the future\u201d (<a href=\"https://www.theverge.com/2023/10/23/23928550/posse-posting-activitypub-standard-twitter-tumblr-mastodon\">https://www.theverge.com/2023/10/23/23928550/posse-posting-activitypub-standard-twitter-tumblr-mastodon</a>):<br />\u00a0 \u201cYour post appears natively on all of those platforms, typically with some kind of link back to your blog. And your blog becomes the hub for everything, your main home on the internet.<br />Done right, POSSE is the best of all posting worlds.\u201d<br /><br />* David also recorded a 29 minute podcast on POSSE with some great interviews: <a href=\"https://podcasts.apple.com/us/podcast/the-posters-guide-to-the-new-internet/id430333725?i=1000632256014\">https://podcasts.apple.com/us/podcast/the-posters-guide-to-the-new-internet/id430333725?i=1000632256014</a><br /><br />* Cory Doctorow (<a href=\"https://craphound.com\">@craphound.com</a> <a href=\"https://mamot.fr/@doctorow\">@doctorow@mamot.fr</a>) declared in his Pluralistic blog (<a href=\"https://pluralistic.net\">@pluralistic.net</a>) post: \u201cVice surrenders\u201d (<a href=\"https://pluralistic.net/2024/02/24/anti-posse/\">https://pluralistic.net/2024/02/24/anti-posse/</a>):<br />\u00a0 \u201cThis is the moment for POSSE (Post Own Site, Share Everywhere [sic]), a strategy that sees social media as a strategy for bringing readers to channels that you control\u201d <br /><br />* And none other than Molly White (<a href=\"https://mollywhite.net\">@mollywhite.net</a> <a href=\"https://hachyderm.io/@molly0xfff\">@molly0xfff@hachyderm.io</a>) of <a href=\"https://web3isgoinggreat.com\">@web3isgoinggreat.com</a> (<a href=\"https://indieweb.social/@web3isgreat\">@web3isgreat@indieweb.social</a>) built, deployed, and started actively using her own POSSE setup as described in her post titled \u201cPOSSE\u201d (<a href=\"https://www.mollywhite.net/micro/entry/202403091817\">https://www.mollywhite.net/micro/entry/202403091817</a>) to: <br />\u00a0 \"\u2026 write posts in the microblog and automatically crosspost them to Twitter/Mastodon/Bluesky, while keeping the original post on my site.\"<br />\u00a0 <br />Congrats Molly and well done!<br /><br /><br />In its 19th year, the microformats formal #<span class=\"p-category\">microformats2</span> syntax and popular vocabularies h-card, h-entry, and h-feed, kept growing across IndieWeb (micro)blogging services and software like CMSs & SSGs both for publishing, and richer peer-to-peer social web interactions via #<span class=\"p-category\">Webmention</span>.<br /><br />Beyond the IndieWeb, the rel=me microformat, AKA #<span class=\"p-category\">relMe</span>, continues to be adopted by services to support #<span class=\"p-category\">distributed</span> #<span class=\"p-category\">verification</span>, such as these in the past year: <br /><br />* Meta Platforms #<span class=\"p-category\">Threads</span> user profile \"Link\" field<a href=\"https://tantek.com/#t5Xa1_note-1\">\u00b9</a> <br />* #<span class=\"p-category\">Letterboxd</span> user profile website field<a href=\"https://tantek.com/#t5Xa1_note-2\">\u00b2</a><br /><br /><br />For both POSSE and microformats, there is always more we can do to improve their techniques, technologies, and tools to help people own their content and identities online, while staying connected to friends across the web.<br /><br />Got suggestions for this coming year? Join us in chat:<br />* <a href=\"https://chat.indieweb.org/dev\">https://chat.indieweb.org/dev</a><br />* <a href=\"https://chat.indieweb.org/microformats\">https://chat.indieweb.org/microformats</a><br />for discussions about POSSE and microformats, respectively.<br /><br /><br />Previously: <a href=\"https://tantek.com/2023/171/t1/anniversaries-microformats-posse\">https://tantek.com/2023/171/t1/anniversaries-microformats-posse</a><br /><br /><br />This is post 15 of #<span class=\"p-category\">100PostsOfIndieWeb</span>. #<span class=\"p-category\">100Posts</span><br /><br />\u2190 <a href=\"https://tantek.com/2024/151/t1/minimum-interesting-service-worker\">https://tantek.com/2024/151/t1/minimum-interesting-service-worker</a><br />\u2192 <a href=\"https://tantek.com/2024/237/t1/people-over-protocols-platforms\">https://tantek.com/2024/237/t1/people-over-protocols-platforms</a><br /><br /><br />Post glossary:<br /><br />CMS<br />\u00a0 <a href=\"https://indieweb.org/CMS\">https://indieweb.org/CMS</a><br />h-card<br />\u00a0 <a href=\"https://microformats.org/wiki/h-card\">https://microformats.org/wiki/h-card</a><br />h-entry<br />\u00a0 <a href=\"https://microformats.org/wiki/h-entry\">https://microformats.org/wiki/h-entry</a><br />h-feed<br />\u00a0 <a href=\"https://microformats.org/wiki/h-feed\">https://microformats.org/wiki/h-feed</a><br />microformats2 syntax<br />\u00a0 <a href=\"https://microformats.org/wiki/microformats2-parsing\">https://microformats.org/wiki/microformats2-parsing</a><br />rel-me<br />\u00a0 <a href=\"https://microformats.org/wiki/rel-me\">https://microformats.org/wiki/rel-me</a><br />SSG<br />\u00a0 <a href=\"https://indieweb.org/SSG\">https://indieweb.org/SSG</a><br />Webmention<br />\u00a0 <a href=\"https://indieweb.org/Webmention\">https://indieweb.org/Webmention</a><br />Withknown<br />\u00a0 <a href=\"https://indieweb.org/Known\">https://indieweb.org/Known</a><br /><br /><br />References:<br /><br /><a href=\"https://tantek.com/#t5Xa1_ref-1\">\u00b9</a> <a href=\"https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me\">https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me</a><br /><a href=\"https://tantek.com/#t5Xa1_ref-2\">\u00b2</a> <a href=\"https://indieweb.org/rel-me#Letterboxd\">https://indieweb.org/rel-me#Letterboxd</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "42130096",
"_source": "2460"
}
Twenty years ago this past February, Kevin Marks and I introduced #microformats in a conference presentation.
Full post: https://tantek.com/2024/044/t1/twenty-years-microformats
Aside: This is an even shorter summary of that post from ~200 days ago, which #Mastodon readers never got due to a Mastodon #federation bug (details in https://tantek.com/t5Yo1).
Since early 2023, here are the top three updates & interesting developments in microformats:
1. Growing rel=me adoption for distributed verification (✅ in Mastodon etc.)
* Wikipedia, Threads, omg.lol
2. Proposal to merge #microformats2 h-review into h-entry, since in practice (e.g. on #indieweb) reviews are just entries with a bit more.
3. #metaformats adoptions, implementations, iteration
{
"type": "entry",
"published": "2024-09-03 18:47-0700",
"url": "https://tantek.com/2024/247/t2/twenty-years-microformats-shorter2",
"category": [
"microformats",
"Mastodon",
"federation",
"microformats2",
"indieweb",
"metaformats"
],
"content": {
"text": "Twenty years ago this past February, Kevin Marks and I introduced #microformats in a conference presentation.\n\nFull post: https://tantek.com/2024/044/t1/twenty-years-microformats\n\nAside: This is an even shorter summary of that post from ~200 days ago, which #Mastodon readers never got due to a Mastodon #federation bug (details in https://tantek.com/t5Yo1).\n\nSince early 2023, here are the top three updates & interesting developments in microformats:\n\n1. Growing rel=me adoption for distributed verification (\u2705 in Mastodon etc.)\n\u00a0* Wikipedia, Threads, omg.lol\n2. Proposal to merge #microformats2 h-review into h-entry, since in practice (e.g. on #indieweb) reviews are just entries with a bit more.\n3. #metaformats adoptions, implementations, iteration",
"html": "Twenty years ago this past February, Kevin Marks and I introduced #<span class=\"p-category\">microformats</span> in a conference presentation.<br /><br />Full post: <a href=\"https://tantek.com/2024/044/t1/twenty-years-microformats\">https://tantek.com/2024/044/t1/twenty-years-microformats</a><br /><br />Aside: This is an even shorter summary of that post from ~200 days ago, which #<span class=\"p-category\">Mastodon</span> readers never got due to a Mastodon #<span class=\"p-category\">federation</span> bug (details in <a href=\"https://tantek.com/t5Yo1\">https://tantek.com/t5Yo1</a>).<br /><br />Since early 2023, here are the top three updates & interesting developments in microformats:<br /><br />1. Growing rel=me adoption for distributed verification (\u2705 in Mastodon etc.)<br />\u00a0* Wikipedia, Threads, <a href=\"http://omg.lol\">omg.lol</a><br />2. Proposal to merge #<span class=\"p-category\">microformats2</span> h-review into h-entry, since in practice (e.g. on #<span class=\"p-category\">indieweb</span>) reviews are just entries with a bit more.<br />3. #<span class=\"p-category\">metaformats</span> adoptions, implementations, iteration"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "42129421",
"_source": "2460"
}