#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"
}
Twenty years ago this past February, @KevinMarks.com (@KevinMarks@xoxo.zone) and I introduced #microformats in a conference presentation.
Full post: https://tantek.com/2024/044/t1/twenty-years-microformats
Aside: This is a summary of a longer post from ~200 days ago¹, which #Mastodon readers never got due to a Mastodon #federation bug (instances returned 202 for post inbox delivery, but did not show post to followers or on local profiles, details in https://tantek.com/t5Yo1).
I wrote a retrospective last year: https://tantek.com/2023/047/t1/nineteen-years-microformats
Since then, 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 support
2. A proposal to merge #microformats2 h-review into h-entry, since reviews are in practice (e.g. on the #indieweb) always entries with a bit more information.
3. #metaformats adoptions, implementations, and iteration
More details:
¹ https://tantek.com/2024/044/t1/twenty-years-microformats
{
"type": "entry",
"published": "2024-09-03 14:02-0700",
"url": "https://tantek.com/2024/247/t1/twenty-years-microformats-summary",
"category": [
"microformats",
"Mastodon",
"federation",
"microformats2",
"indieweb",
"metaformats"
],
"content": {
"text": "Twenty years ago this past February, @KevinMarks.com (@KevinMarks@xoxo.zone) and I introduced #microformats in a conference presentation.\n\nFull post: https://tantek.com/2024/044/t1/twenty-years-microformats\n\nAside: This is a summary of a longer post from ~200 days ago\u00b9, which #Mastodon readers never got due to a Mastodon #federation bug (instances returned 202 for post inbox delivery, but did not show post to followers or on local profiles, details in https://tantek.com/t5Yo1).\n\nI wrote a retrospective last year: https://tantek.com/2023/047/t1/nineteen-years-microformats\n\nSince then, 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 support\n2. A proposal to merge #microformats2 h-review into h-entry, since reviews are in practice (e.g. on the #indieweb) always entries with a bit more information.\n3. #metaformats adoptions, implementations, and iteration\n\nMore details: \n\u00b9 https://tantek.com/2024/044/t1/twenty-years-microformats",
"html": "Twenty years ago this past February, <a href=\"https://KevinMarks.com\">@KevinMarks.com</a> (<a href=\"https://xoxo.zone/@KevinMarks\">@KevinMarks@xoxo.zone</a>) 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 a summary of a longer post from ~200 days ago<a href=\"https://tantek.com/#t5Yp1_note-1\">\u00b9</a>, which #<span class=\"p-category\">Mastodon</span> readers never got due to a Mastodon #<span class=\"p-category\">federation</span> bug (instances returned 202 for post inbox delivery, but did not show post to followers or on local profiles, details in <a href=\"https://tantek.com/t5Yo1\">https://tantek.com/t5Yo1</a>).<br /><br />I wrote a retrospective last year: <a href=\"https://tantek.com/2023/047/t1/nineteen-years-microformats\">https://tantek.com/2023/047/t1/nineteen-years-microformats</a><br /><br />Since then, 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> support<br />2. A proposal to merge #<span class=\"p-category\">microformats2</span> h-review into h-entry, since reviews are in practice (e.g. on the #<span class=\"p-category\">indieweb</span>) always entries with a bit more information.<br />3. #<span class=\"p-category\">metaformats</span> adoptions, implementations, and iteration<br /><br />More details: <br /><a href=\"https://tantek.com/#t5Yp1_ref-1\">\u00b9</a> <a href=\"https://tantek.com/2024/044/t1/twenty-years-microformats\">https://tantek.com/2024/044/t1/twenty-years-microformats</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "42129249",
"_source": "2460"
}
{
"type": "entry",
"author": {
"name": "Jared White",
"url": "https://jaredwhite.com/",
"photo": null
},
"url": "https://jaredwhite.com/articles/perfect-days-movie-review",
"published": "2024-09-03T09:24:16-07:00",
"content": {
"html": "<img alt=\"\" src=\"https://res.cloudinary.com/mariposta/image/upload/w_1200,c_limit,q_65/perfect-days.jpg\" /><h2>The strength of character needed to perform the best work you can, to care deeply about the welfare of others, to admire the beauty of Mother Earth, and to stay in tune with your hidden self\u2014finding that is true nobility.</h2>\n\n<p>Without a doubt I knew I would love this movie. (Hat tip to Thomas Flight\u2019s amazing video essay <a href=\"https://www.youtube.com/watch?v=BucSbzYXqKM\">Hollywood\u2019s Obsession with Ambition</a> which highlights this film as an example of the kind of story you rarely see told in mainstream cinema.)</p>\n\n<p>At first glance, you might approach <em>Perfect Days</em> expecting it to be a quaint little film about a simple man (of meager status in society) going about his simple day, and then all of a sudden something happens to puncture his comfortable routine and make him question the nature of his poor existence. And while there <em>is</em> an element of that trope to be found here, I genuinely don\u2019t think that\u2019s the point of the movie\u2014certainly not its central theme.</p>\n\n<p>Instead, what I think <em>Perfect Days</em> is about is this (and it\u2019s all but stated clearly by the protagonist, Hirayama, in an incredibly insightful conversation):</p>\n\n<p><strong>There are many worlds within our world</strong>, and the world in which the most celebrated among us are those who are gentle of spirit, quiet yet understanding, quickened with wisdom yet slow to teach, observant of small details, careful to do good work regardless of its appreciation by others, able to find worthwhile meaning and creative merit even in the mundane\u2026is not a world in sync with much of modern culture & civilization.</p>\n\n<p>Society celebrates the high earners, the outwardly \u201csuccessful\u201d, the movers & shakers who can make a splash, make a scene, make an obvious \u201cdent\u201d in the universe. Perhaps in certain cases, such lauding of lofty outcomes is indeed warranted. But I would argue\u2014and it seems this film does argue\u2014that finding fulfillment in the trappings of cosmopolitan relevance is certainly not a universal path\u2026and rewarding alternatives are routinely overlooked.</p>\n\n<h3>Two roads diverged, and Hirayama took the one less traveled by\u2026</h3>\n\n<p>(<em>Minor spoilers ahead.</em>)</p>\n\n<p>It\u2019s not spelled out in detail what occurred in the past, but it seems Hirayama\u2019s family had been well-to-do, yet he walked away under less-than-ideal circumstances\u2014while his sister remained \u201cin the fold\u201d. Was their father abusive? Or simply overbearing and demanding? Perhaps the family business was repugnant to Hirayama in some way? Whatever caused the rift, Hirayama became estranged and went off to forge his own destiny.</p>\n\n<p>A destiny, that is, revolving around <strong>cleaning some of Tokyo\u2019s finest toilets</strong>, taking pictures of trees, listening to cassette tapes of Van Morrison, and reading books for \u201cintellectuals\u201d before nodding off to sleep in his modest apartment.</p>\n\n<p>Now I realize that makes him sound quite \u201cboring\u201d and not at all worthy of being the star attraction of a motion picture, but hear me out. There\u2019s more to Hirayama than what he does, and that\u2019s kind of the point.</p>\n\n<p>He may be <em>invisible</em> to most others in society, yet the people who have taken the trouble to get to know him admire him. They recognize that he is a considerate person. A safe person. A <em>good</em> person. He works hard and gets the job done right. He\u2019s dependable. He has been through some stuff, certainly, but that didn\u2019t result in his becoming callous, cynical, or self-absorbed. He may not be a \u201cgentleman\u201d, but he\u2019s a <strong>gentle man</strong>.</p>\n\n<p>And it turns out these qualities are particularly important to the women who turn to Hirayama when shit happens in their lives.</p>\n\n<p>Aya\u2014who feels pressured by her boyfriend to take things to the next level and she\u2019s clearly not willing to go there. Yet she enjoys listening to Hirayama\u2019s music collection and plants a demure kiss on his cheek. <strong>He\u2019s safe, and she knows it</strong>.</p>\n\n<p>Niko\u2014the teenage niece he barely recognizes at first who turns towards him without hesitation as part of her first-ever \u201crunaway\u201d adventure. (Apparently things are not going well in the household of Hirayama\u2019s sister\u2026echoes of the past?) Far from seeming fazed by her uncle\u2019s simple existence as a toilet cleaner or his unfamiliar ancient technology (what\u2019s a cassette tape?!), she relishes it. To her, he seems more grounded, more reassuring, and more in-tune with some sort of inner peace she longs to cultivate. Outwardly he doesn\u2019t own much besides books, tapes, and plants, but spiritually <strong>he is rich\u2026while her own family is in essence poor</strong>.</p>\n\n<p>And \u201cMama\u201d\u2014the bar owner Hirayama is on friendly terms with\u2026and perhaps in time, more. Although she\u2019ll deny it with loud protestations, apparently he gets a bit more to drink and a bit more to eat than the other patrons of her establishment. And even though he appears to be nothing more than a friendly regular customer, Mama\u2019s ex-husband who is dying of cancer is somehow able to pick up on the fact that of anyone in the world he could implore to \u201ctake care of Mama for me\u201d, <strong>it\u2019s Hirayama</strong>. (Even though it\u2019s \u201cnot like that\u201d. Yeah Hirayama, sure. Right\u2026)</p>\n\n<p>In an era where the chronically online chatter over whether, as a woman, it\u2019s safer to hang out with a man or a bear\u2014in an era when \u201cincel\u201d culture has truly become a menace to our political discourse\u2014in an era when young men may find themselves falling down that rabbit hole of wondering what their place is in a world where women gain equality of status, means, and purpose\u2014a genuinely <em>decent</em> older man as depicted in the person of Hirayama doesn\u2019t just warm the heart\u2026it demonstrates that a human who operates from the vantage point of mindfulness, dedication, and true cultivation of spirit isn\u2019t just a figment of a bygone age but a <em>blueprint we are in desperate need of</em>.</p>\n\n<p>The overflowing of memes around Tim Walz and his \u201cbig dad energy\u201d is simply another variation on this theme: we can all stop pretending we don\u2019t know what \u201ctonic masculinity\u201d (I love this phrase!) looks like, because we do.</p>\n\n<p><strong>It looks, in a certain way, like Hirayama.</strong></p>\n\n<p>I don\u2019t believe this means we should all quit our high-paying corporate jobs and become toilet cleaners to find the path to ultimate fulfillment. That\u2019s not what <em>Perfect Days</em> is saying.</p>\n\n<p>It\u2019s saying, I believe, that the strength of character needed to perform the best work you can, to care deeply about the welfare of others, to admire the beauty of Mother Earth, and to stay in tune with your hidden self\u2014finding that is true nobility. And making the intention to cultivate that wisdom path is a most worthy goal, whether or not you happen to clean toilets or run for political office or write code or volunteer at the local non-profit or fly to the moon.</p>\n\n<h3>Finding joy amidst the banality</h3>\n\n<p>Hirayama isn\u2019t \u201chappy\u201d thoughout the whole film. In fact, he really ends up struggling due to some of the things which happen to him and finds it very difficult to regain his composure. And I was deeply moved by the final scene of the film\u2014I won\u2019t give it away, but let\u2019s just say it\u2019s a <em>tour de force</em> of subtle emotive acting.</p>\n\n<p>And that too is the point of <em>Perfect Days</em>. Mindfulness exercise and spiritual \u201cenlightenment\u201d (however you might chose to define that) isn\u2019t a magic bullet. <strong>Sometimes life just sucks</strong>, plain and simple. Inevitably you\u2019ll have bad days. Everything will leave a sour taste in your mouth.</p>\n\n<p>But those days do pass. The sun will rise as it always does. And if you take the time to stop and notice, you\u2019ll find the beauty again even in the mundane. <strong>You\u2019ll recognize the priceless value of a gentle spirit</strong>. And you\u2019ll revel in that indescribable feeling of <em>komorebi</em> once again.</p>\n\n\n\n<p><em>Perfect Days</em> was written by German film veteran Wim Wenders along with Takuma Takasaki. It stars acclaimed Japanese actor K\u014dji Yakusho as Hirayam and was directed by Wenders. It was nominated for an Academy Award in 2023 and is currently streaming on Hulu. Wenders was initially approached to create a documentary about the architectural significance of Tokyo\u2019s public toilets and instead crafted an intimate character study about \u201cfinding joy in our everyday banality\u201d (<a href=\"https://movieweb.com/wim-wenders-takuma-takasaki-perfect-days-interview/\">MovieWeb</a>).</p>\n\n\n\n <br /><p>\n \n <a href=\"https://jaredwhite.com/tag/mindfulness\">#mindfulness</a>\n \n <a href=\"https://jaredwhite.com/tag/spirituality\">#spirituality</a>\n \n <a href=\"https://jaredwhite.com/tag/movies\">#movies</a>\n \n </p>",
"text": "The strength of character needed to perform the best work you can, to care deeply about the welfare of others, to admire the beauty of Mother Earth, and to stay in tune with your hidden self\u2014finding that is true nobility.\n\nWithout a doubt I knew I would love this movie. (Hat tip to Thomas Flight\u2019s amazing video essay Hollywood\u2019s Obsession with Ambition which highlights this film as an example of the kind of story you rarely see told in mainstream cinema.)\n\nAt first glance, you might approach Perfect Days expecting it to be a quaint little film about a simple man (of meager status in society) going about his simple day, and then all of a sudden something happens to puncture his comfortable routine and make him question the nature of his poor existence. And while there is an element of that trope to be found here, I genuinely don\u2019t think that\u2019s the point of the movie\u2014certainly not its central theme.\n\nInstead, what I think Perfect Days is about is this (and it\u2019s all but stated clearly by the protagonist, Hirayama, in an incredibly insightful conversation):\n\nThere are many worlds within our world, and the world in which the most celebrated among us are those who are gentle of spirit, quiet yet understanding, quickened with wisdom yet slow to teach, observant of small details, careful to do good work regardless of its appreciation by others, able to find worthwhile meaning and creative merit even in the mundane\u2026is not a world in sync with much of modern culture & civilization.\n\nSociety celebrates the high earners, the outwardly \u201csuccessful\u201d, the movers & shakers who can make a splash, make a scene, make an obvious \u201cdent\u201d in the universe. Perhaps in certain cases, such lauding of lofty outcomes is indeed warranted. But I would argue\u2014and it seems this film does argue\u2014that finding fulfillment in the trappings of cosmopolitan relevance is certainly not a universal path\u2026and rewarding alternatives are routinely overlooked.\n\nTwo roads diverged, and Hirayama took the one less traveled by\u2026\n\n(Minor spoilers ahead.)\n\nIt\u2019s not spelled out in detail what occurred in the past, but it seems Hirayama\u2019s family had been well-to-do, yet he walked away under less-than-ideal circumstances\u2014while his sister remained \u201cin the fold\u201d. Was their father abusive? Or simply overbearing and demanding? Perhaps the family business was repugnant to Hirayama in some way? Whatever caused the rift, Hirayama became estranged and went off to forge his own destiny.\n\nA destiny, that is, revolving around cleaning some of Tokyo\u2019s finest toilets, taking pictures of trees, listening to cassette tapes of Van Morrison, and reading books for \u201cintellectuals\u201d before nodding off to sleep in his modest apartment.\n\nNow I realize that makes him sound quite \u201cboring\u201d and not at all worthy of being the star attraction of a motion picture, but hear me out. There\u2019s more to Hirayama than what he does, and that\u2019s kind of the point.\n\nHe may be invisible to most others in society, yet the people who have taken the trouble to get to know him admire him. They recognize that he is a considerate person. A safe person. A good person. He works hard and gets the job done right. He\u2019s dependable. He has been through some stuff, certainly, but that didn\u2019t result in his becoming callous, cynical, or self-absorbed. He may not be a \u201cgentleman\u201d, but he\u2019s a gentle man.\n\nAnd it turns out these qualities are particularly important to the women who turn to Hirayama when shit happens in their lives.\n\nAya\u2014who feels pressured by her boyfriend to take things to the next level and she\u2019s clearly not willing to go there. Yet she enjoys listening to Hirayama\u2019s music collection and plants a demure kiss on his cheek. He\u2019s safe, and she knows it.\n\nNiko\u2014the teenage niece he barely recognizes at first who turns towards him without hesitation as part of her first-ever \u201crunaway\u201d adventure. (Apparently things are not going well in the household of Hirayama\u2019s sister\u2026echoes of the past?) Far from seeming fazed by her uncle\u2019s simple existence as a toilet cleaner or his unfamiliar ancient technology (what\u2019s a cassette tape?!), she relishes it. To her, he seems more grounded, more reassuring, and more in-tune with some sort of inner peace she longs to cultivate. Outwardly he doesn\u2019t own much besides books, tapes, and plants, but spiritually he is rich\u2026while her own family is in essence poor.\n\nAnd \u201cMama\u201d\u2014the bar owner Hirayama is on friendly terms with\u2026and perhaps in time, more. Although she\u2019ll deny it with loud protestations, apparently he gets a bit more to drink and a bit more to eat than the other patrons of her establishment. And even though he appears to be nothing more than a friendly regular customer, Mama\u2019s ex-husband who is dying of cancer is somehow able to pick up on the fact that of anyone in the world he could implore to \u201ctake care of Mama for me\u201d, it\u2019s Hirayama. (Even though it\u2019s \u201cnot like that\u201d. Yeah Hirayama, sure. Right\u2026)\n\nIn an era where the chronically online chatter over whether, as a woman, it\u2019s safer to hang out with a man or a bear\u2014in an era when \u201cincel\u201d culture has truly become a menace to our political discourse\u2014in an era when young men may find themselves falling down that rabbit hole of wondering what their place is in a world where women gain equality of status, means, and purpose\u2014a genuinely decent older man as depicted in the person of Hirayama doesn\u2019t just warm the heart\u2026it demonstrates that a human who operates from the vantage point of mindfulness, dedication, and true cultivation of spirit isn\u2019t just a figment of a bygone age but a blueprint we are in desperate need of.\n\nThe overflowing of memes around Tim Walz and his \u201cbig dad energy\u201d is simply another variation on this theme: we can all stop pretending we don\u2019t know what \u201ctonic masculinity\u201d (I love this phrase!) looks like, because we do.\n\nIt looks, in a certain way, like Hirayama.\n\nI don\u2019t believe this means we should all quit our high-paying corporate jobs and become toilet cleaners to find the path to ultimate fulfillment. That\u2019s not what Perfect Days is saying.\n\nIt\u2019s saying, I believe, that the strength of character needed to perform the best work you can, to care deeply about the welfare of others, to admire the beauty of Mother Earth, and to stay in tune with your hidden self\u2014finding that is true nobility. And making the intention to cultivate that wisdom path is a most worthy goal, whether or not you happen to clean toilets or run for political office or write code or volunteer at the local non-profit or fly to the moon.\n\nFinding joy amidst the banality\n\nHirayama isn\u2019t \u201chappy\u201d thoughout the whole film. In fact, he really ends up struggling due to some of the things which happen to him and finds it very difficult to regain his composure. And I was deeply moved by the final scene of the film\u2014I won\u2019t give it away, but let\u2019s just say it\u2019s a tour de force of subtle emotive acting.\n\nAnd that too is the point of Perfect Days. Mindfulness exercise and spiritual \u201cenlightenment\u201d (however you might chose to define that) isn\u2019t a magic bullet. Sometimes life just sucks, plain and simple. Inevitably you\u2019ll have bad days. Everything will leave a sour taste in your mouth.\n\nBut those days do pass. The sun will rise as it always does. And if you take the time to stop and notice, you\u2019ll find the beauty again even in the mundane. You\u2019ll recognize the priceless value of a gentle spirit. And you\u2019ll revel in that indescribable feeling of komorebi once again.\n\n\n\nPerfect Days was written by German film veteran Wim Wenders along with Takuma Takasaki. It stars acclaimed Japanese actor K\u014dji Yakusho as Hirayam and was directed by Wenders. It was nominated for an Academy Award in 2023 and is currently streaming on Hulu. Wenders was initially approached to create a documentary about the architectural significance of Tokyo\u2019s public toilets and instead crafted an intimate character study about \u201cfinding joy in our everyday banality\u201d (MovieWeb).\n\n\n\n \n\n \n #mindfulness\n \n #spirituality\n \n #movies"
},
"name": "The Underestimation of a Gentle Spirit (Movie Review of Perfect Days)",
"post-type": "article",
"_id": "42125966",
"_source": "2783"
}
Adventures in IndieWeb / ActivityPub (AP) bridging:
While 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).
These most recent posts:
* https://tantek.com/2024/245/t1/read-write-suggest-edit-web
* https://tantek.com/2024/242/t1/indiewebcamp-portland
* https://tantek.com/2024/238/t3/indiewebcamp-auto-linking
and these earlier this year:
* https://tantek.com/2024/173/t1/years-posse-microformats-adoption
* https://tantek.com/2024/044/t1/twenty-years-microformats
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.
* https://indieweb.social/@tantek.com@tantek.com
* https://mastodon.social/@tantek.com@tantek.com
* https://social.coop/@tantek.com@tantek.com
* https://w3c.social/@tantek.com@tantek.com
(My most recent post on all of these is the same 2024-08-25 post starting with “All setup here at IndieWebCamp Portland!”)
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?
GitHub tracking bug in case you can help narrow/track this down or have
* https://github.com/snarfed/bridgy-fed/issues/884
Let’s see if this post makes it to your Mastodon (or other #fediverse) reader/client.
#indieweb #ActivityPub
This is post 21 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/245/t1/read-write-suggest-edit-web
→ 🔮
{
"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"
}
✏️ 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 @KevinMarks.com (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) 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, 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
→ 🔮
{
"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 & 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 \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"
}
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:
{
"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"
}
Enjoying endangered gardens
{
"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"
}
{
"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"
}
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!
Now I just have to upgrade this to 4mb RAM and then we'll be in business!
{
"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"
}
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.
There are certainly a number of things in Matthew’s response that tempt me to respond, but I’d like to focus on this:
I am, nevertheless, a little annoyed by the exhortation to “talk with us”. What does it look like I’m doing over here, anyway? Oh, no, it’s not good enough to post one’s opinion on the web. I’m supposed to use one of the IndieWeb’s chats, either IRC, Slack, or Discord. […] I am already talking with you. I’m 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.
I don’t consider my post a reply to Matthew’s post. I do not see his post as an invitation to conversation. I read it as a “take” - an opinion piece intended to make the reader feel a certain way and then close the topic, complete with clickbait headline.
I shouldn’t 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’s not an IndieWeb mailing list. It’s easy in these formats to go hard on the abstract, and to spend time constructing arguments instead of asking questions.
That’s not to say that posts can’t 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.
Those 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.
{
"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"
}
{
"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"
}
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 @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.
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
→ 🔮
{
"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"
}
Sharing for my fedi-peeps. That’s a term, right?
Has the IndieWeb become discourse, again?
https://martymcgui.re/2024/08/29/141602/
{
"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"
}