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 and Bridgy) 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:
Bridgy
https://brid.gy/ and https://fed.brid.gy/ for direct federation instead of POSSE
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": "http://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 and Bridgy) 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\nBridgy\n\u00a0 https://brid.gy/ and https://fed.brid.gy/ for direct federation instead of POSSE\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> and Bridgy) 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=\"http://tantek.com/#t5Xa1_note-1\">\u00b9</a> <br />* #<span class=\"p-category\">Letterboxd</span> user profile website field<a href=\"http://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 />Bridgy<br />\u00a0 <a href=\"https://brid.gy/\">https://brid.gy/</a> and <a href=\"https://fed.brid.gy/\">https://fed.brid.gy/</a> for direct federation instead of POSSE<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=\"http://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=\"http://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://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "note",
"_id": "42130411",
"_source": "1",
"_is_read": false
}
today is a back-up day, because i said so.
make your back-up!
#indieweb #indiedev #BackupDay #programming
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://ohai.social/@3AM/113077354588812965",
"content": {
"html": "<p>today is a back-up day, because i said so. <br />make your back-up! <img alt=\":bonk:\" height=\"16\" src=\"https://files.mastodon.social/cache/custom_emojis/images/000/548/550/original/a1e65d2db77909b2.png\" title=\":bonk:\" width=\"16\" /></p><p><a href=\"https://ohai.social/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://ohai.social/tags/indiedev\">#<span>indiedev</span></a> <a href=\"https://ohai.social/tags/BackupDay\">#<span>BackupDay</span></a> <a href=\"https://ohai.social/tags/programming\">#<span>programming</span></a></p>",
"text": "today is a back-up day, because i said so. \nmake your back-up! \n\n#indieweb #indiedev #BackupDay #programming"
},
"published": "2024-09-04T04:18:21+00:00",
"post-type": "note",
"_id": "42130121",
"_source": "8007",
"_is_read": false
}
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 and Bridgy) 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:
Bridgy
https://brid.gy/ and https://fed.brid.gy/ for direct federation instead of POSSE
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",
"author": {
"name": "#indieweb",
"url": "https://indieweb.social/tags/indieweb",
"photo": null
},
"url": "https://fed.brid.gy/r/https://tantek.com/2024/173/t1/years-posse-microformats-beyond",
"content": {
"html": "<p>Happy 12 years of <a href=\"https://indieweb.org/POSSE\">https://indieweb.org/POSSE</a> <a href=\"https://indieweb.social/tags/POSSE\">#<span class=\"p-category\">POSSE</span></a> and<br />19 years of <a href=\"https://microformats.org/\">https://microformats.org/</a> <a href=\"https://indieweb.social/tags/microformats\">#<span class=\"p-category\">microformats</span></a>! (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 <a href=\"https://indieweb.social/tags/IndieWeb\">#<span class=\"p-category\">IndieWeb</span></a> 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> and Bridgy) 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 <a href=\"https://indieweb.social/tags/microformats2\">#<span class=\"p-category\">microformats2</span></a> 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 <a href=\"https://indieweb.social/tags/Webmention\">#<span class=\"p-category\">Webmention</span></a>.<br /><br />Beyond the IndieWeb, the rel=me microformat, AKA <a href=\"https://indieweb.social/tags/relMe\">#<span class=\"p-category\">relMe</span></a>, continues to be adopted by services to support <a href=\"https://indieweb.social/tags/distributed\">#<span class=\"p-category\">distributed</span></a> <a href=\"https://indieweb.social/tags/verification\">#<span class=\"p-category\">verification</span></a>, such as these in the past year: <br /><br />* Meta Platforms <a href=\"https://indieweb.social/tags/Threads\">#<span class=\"p-category\">Threads</span></a> user profile \"Link\" field<a href=\"https://tantek.com/2024/173/t1/years-posse-microformats-beyond#t5Xa1_note-1\">\u00b9</a> <br />* <a href=\"https://indieweb.social/tags/Letterboxd\">#<span class=\"p-category\">Letterboxd</span></a> user profile website field<a href=\"https://tantek.com/2024/173/t1/years-posse-microformats-beyond#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 <a href=\"https://indieweb.social/tags/100PostsOfIndieWeb\">#<span class=\"p-category\">100PostsOfIndieWeb</span></a>. <a href=\"https://indieweb.social/tags/100Posts\">#<span class=\"p-category\">100Posts</span></a><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 />Bridgy<br />\u00a0 <a href=\"https://brid.gy/\">https://brid.gy/</a> and <a href=\"https://fed.brid.gy/\">https://fed.brid.gy/</a> for direct federation instead of POSSE<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/2024/173/t1/years-posse-microformats-beyond#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/2024/173/t1/years-posse-microformats-beyond#t5Xa1_ref-2\">\u00b2</a> <a href=\"https://indieweb.org/rel-me#Letterboxd\">https://indieweb.org/rel-me#Letterboxd</a></p>\n<a class=\"u-mention\" href=\"https://TheVerge.com\"></a>\n<a class=\"u-mention\" href=\"https://craphound.com\"></a>\n<a class=\"u-mention\" href=\"https://hachyderm.io/@molly0xfff\"></a>\n<a class=\"u-mention\" href=\"https://indieweb.social/@web3isgreat\"></a>\n<a class=\"u-mention\" href=\"https://mamot.fr/@doctorow\"></a>\n<a class=\"u-mention\" href=\"https://mas.to/@pierce\"></a>\n<a class=\"u-mention\" href=\"https://mastodon.social/@verge\"></a>\n<a class=\"u-mention\" href=\"https://mollywhite.net\"></a>\n<a class=\"u-mention\" href=\"https://pluralistic.net\"></a>\n<a class=\"u-mention\" href=\"https://web3isgoinggreat.com\"></a>",
"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 and Bridgy) 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\nBridgy\n\u00a0 https://brid.gy/ and https://fed.brid.gy/ for direct federation instead of POSSE\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"
},
"published": "2024-06-22T05:02:00+00:00",
"post-type": "note",
"_id": "42130122",
"_source": "8007",
"_is_read": false
}
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": "http://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://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "note",
"_id": "42129731",
"_source": "1",
"_is_read": false
}
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": "http://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=\"http://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=\"http://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://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "note",
"_id": "42129732",
"_source": "1",
"_is_read": false
}
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",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://fed.brid.gy/r/https://tantek.com/2024/247/t2/twenty-years-microformats-shorter2",
"content": {
"html": "<p>Twenty years ago this past February, Kevin Marks and I introduced <a href=\"https://indieweb.social/tags/microformats\">#<span class=\"p-category\">microformats</span></a> 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 <a href=\"https://indieweb.social/tags/Mastodon\">#<span class=\"p-category\">Mastodon</span></a> readers never got due to a Mastodon <a href=\"https://indieweb.social/tags/federation\">#<span class=\"p-category\">federation</span></a> 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 <a href=\"https://indieweb.social/tags/microformats2\">#<span class=\"p-category\">microformats2</span></a> h-review into h-entry, since in practice (e.g. on <a href=\"https://indieweb.social/tags/indieweb\">#<span class=\"p-category\">indieweb</span></a>) reviews are just entries with a bit more.<br />3. <a href=\"https://indieweb.social/tags/metaformats\">#<span class=\"p-category\">metaformats</span></a> adoptions, implementations, iteration</p>",
"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"
},
"published": "2024-09-04T01:47:00+00:00",
"post-type": "note",
"_id": "42129532",
"_source": "8007",
"_is_read": false
}
{
"type": "entry",
"published": "2024-09-03 22:14:00",
"url": "https://marksuth.dev/posts/2024/09/indieweb-movie-club-august-2024-round-up-the-matrix",
"category": [
"Article"
],
"name": "IndieWeb Movie Club August 2024 Round Up (The Matrix)",
"content": {
"text": "August saw the inaugural month for the IndieWeb Movie Club, a film themed blog carnival, for which the reaction from the community has been great and will hopefully continue for ...",
"html": "<p>August saw the inaugural month for the <a href=\"https://indieweb.org/indieweb-movie-club\">IndieWeb Movie Club</a>, a film themed blog carnival, for which the reaction from the community has been great and will hopefully continue for ...</p>"
},
"author": {
"type": "card",
"name": "Mark Sutherland",
"url": "https://marksuth.dev/",
"photo": "https://marksuth.dev/images/avatar.jpg"
},
"post-type": "article",
"_id": "42127931",
"_source": "6127",
"_is_read": false
}
**Growing up with Sci-Fi in the ’70s**
Science fiction played a large part in my youth, this is a story about some of the shows that influenced me during the 1970's.
https://barrd.net/growing-up-with-sci-fi-in-the-70s/
#SciFi #indieWeb
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://indieweb.social/@barrd/113074522148771373",
"content": {
"html": "<p>**Growing up with Sci-Fi in the \u201970s**</p><p>Science fiction played a large part in my youth, this is a story about some of the shows that influenced me during the 1970's.</p><p><a href=\"https://barrd.net/growing-up-with-sci-fi-in-the-70s/\"><span>https://</span><span>barrd.net/growing-up-with-sci-</span><span>fi-in-the-70s/</span></a></p><p><a href=\"https://indieweb.social/tags/SciFi\">#<span>SciFi</span></a> <a href=\"https://indieweb.social/tags/indieWeb\">#<span>indieWeb</span></a></p>",
"text": "**Growing up with Sci-Fi in the \u201970s**\n\nScience fiction played a large part in my youth, this is a story about some of the shows that influenced me during the 1970's.\n\nhttps://barrd.net/growing-up-with-sci-fi-in-the-70s/\n\n#SciFi #indieWeb"
},
"published": "2024-09-03T16:18:01+00:00",
"post-type": "note",
"_id": "42126754",
"_source": "8007",
"_is_read": false
}
What make interesting rules for a minimalistic blog design?
So far: no div, no class, < 100 lines of CSS
#html #css #indieweb #smolweb
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://rrier.fr/@pc/statuses/01J6WJ5RZHMCPA2FCB4MA24TJZ",
"content": {
"html": "<p>What make interesting rules for a minimalistic blog design?<br />So far: no div, no class, < 100 lines of CSS</p><p><a href=\"https://rrier.fr/tags/html\">#<span>html</span></a> <a href=\"https://rrier.fr/tags/css\">#<span>css</span></a> <a href=\"https://rrier.fr/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://rrier.fr/tags/smolweb\">#<span>smolweb</span></a></p>",
"text": "What make interesting rules for a minimalistic blog design?\nSo far: no div, no class, < 100 lines of CSS\n\n#html #css #indieweb #smolweb"
},
"published": "2024-09-03T18:25:57+00:00",
"post-type": "note",
"_id": "42126154",
"_source": "8007",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://tweesecake.social/@weirdwriter/113074506413130323",
"content": {
"html": "<p>Trunk Writing <a href=\"https://robertkingett.com/posts/6625/\"><span>https://</span><span>robertkingett.com/posts/6625/</span><span></span></a> <a href=\"https://tweesecake.social/tags/NoPayWall\">#<span>NoPayWall</span></a> <a href=\"https://tweesecake.social/tags/IndieWeb\">#<span>IndieWeb</span></a> <a href=\"https://tweesecake.social/tags/Blog\">#<span>Blog</span></a> <a href=\"https://tweesecake.social/tags/Blogs\">#<span>Blogs</span></a></p>",
"text": "Trunk Writing https://robertkingett.com/posts/6625/ #NoPayWall #IndieWeb #Blog #Blogs"
},
"published": "2024-09-03T16:14:01+00:00",
"post-type": "note",
"_id": "42124643",
"_source": "8007",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://stefanbohacek.online/@stefan/113074481539559618",
"content": {
"html": "<p>Small Web September looks like a fun event!</p><p><a href=\"https://smallweb.dreamwidth.org/2335.html\"><span>https://</span><span>smallweb.dreamwidth.org/2335.h</span><span>tml</span></a></p><p>Via <span class=\"h-card\"><a class=\"u-url\" href=\"https://blorbo.social/@LeGaosaure\">@<span>LeGaosaure</span></a></span></p><p><a href=\"https://stefanbohacek.online/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://stefanbohacek.online/tags/SmallWeb\">#<span>SmallWeb</span></a> <a href=\"https://stefanbohacek.online/tags/SmallWebSeptember\">#<span>SmallWebSeptember</span></a> <a href=\"https://stefanbohacek.online/tags/PersonalWebsite\">#<span>PersonalWebsite</span></a></p>\n<a class=\"u-mention\" href=\"https://blorbo.social/@LeGaosaure\"></a>",
"text": "Small Web September looks like a fun event!\n\nhttps://smallweb.dreamwidth.org/2335.html\n\nVia @LeGaosaure\n\n#indieweb #SmallWeb #SmallWebSeptember #PersonalWebsite"
},
"published": "2024-09-03T16:07:42+00:00",
"post-type": "note",
"_id": "42124644",
"_source": "8007",
"_is_read": false
}
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",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://fed.brid.gy/r/https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed",
"content": {
"html": "<p>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> <a href=\"https://indieweb.social/tags/BridgyFed\">#<span class=\"p-category\">BridgyFed</span></a>, my most recent three posts, and two more earlier this year, were delivered successfully to multiple <a href=\"https://indieweb.social/tags/Mastodon\">#<span class=\"p-category\">Mastodon</span></a> 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 <a href=\"https://indieweb.social/tags/fediverse\">#<span class=\"p-category\">fediverse</span></a>) reader/client.<br /><br /><a href=\"https://indieweb.social/tags/indieweb\">#<span class=\"p-category\">indieweb</span></a> <a href=\"https://indieweb.social/tags/ActivityPub\">#<span class=\"p-category\">ActivityPub</span></a> <br /><br />This is post 21 of <a href=\"https://indieweb.social/tags/100PostsOfIndieWeb\">#<span class=\"p-category\">100PostsOfIndieWeb</span></a>. <a href=\"https://indieweb.social/tags/100Posts\">#<span class=\"p-category\">100Posts</span></a><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</p>",
"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"
},
"published": "2024-09-03T05:32:00+00:00",
"post-type": "note",
"_id": "42124137",
"_source": "8007",
"_is_read": false
}
"Use WordPress if you want. Use Blogger. Hell, use Frontpage 98 if you want. Or learn some HTML and CSS and type it all up in notepad.exe. Or just HTML, don't even bother with the CSS. Just make it yours."
IndieWeb vs. indie web https://fyr.io/post/indieweb_vs_indie_web
#blogging #PersonalWebsites #blogs #IndieWeb #WebDev #WebDesign #HTML #CSS #SmallWeb #SmolWeb #WordPress
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://c.im/@jake4480/113073736246721459",
"content": {
"html": "<p>\"Use WordPress if you want. Use Blogger. Hell, use Frontpage 98 if you want. Or learn some HTML and CSS and type it all up in notepad.exe. Or just HTML, don't even bother with the CSS. Just make it yours.\"</p><p>IndieWeb vs. indie web <a href=\"https://fyr.io/post/indieweb_vs_indie_web\"><span>https://</span><span>fyr.io/post/indieweb_vs_indie_</span><span>web</span></a></p><p><a href=\"https://c.im/tags/blogging\">#<span>blogging</span></a> <a href=\"https://c.im/tags/PersonalWebsites\">#<span>PersonalWebsites</span></a> <a href=\"https://c.im/tags/blogs\">#<span>blogs</span></a> <a href=\"https://c.im/tags/IndieWeb\">#<span>IndieWeb</span></a> <a href=\"https://c.im/tags/WebDev\">#<span>WebDev</span></a> <a href=\"https://c.im/tags/WebDesign\">#<span>WebDesign</span></a> <a href=\"https://c.im/tags/HTML\">#<span>HTML</span></a> <a href=\"https://c.im/tags/CSS\">#<span>CSS</span></a> <a href=\"https://c.im/tags/SmallWeb\">#<span>SmallWeb</span></a> <a href=\"https://c.im/tags/SmolWeb\">#<span>SmolWeb</span></a> <a href=\"https://c.im/tags/WordPress\">#<span>WordPress</span></a></p>",
"text": "\"Use WordPress if you want. Use Blogger. Hell, use Frontpage 98 if you want. Or learn some HTML and CSS and type it all up in notepad.exe. Or just HTML, don't even bother with the CSS. Just make it yours.\"\n\nIndieWeb vs. indie web https://fyr.io/post/indieweb_vs_indie_web\n\n#blogging #PersonalWebsites #blogs #IndieWeb #WebDev #WebDesign #HTML #CSS #SmallWeb #SmolWeb #WordPress"
},
"published": "2024-09-03T12:58:09+00:00",
"post-type": "note",
"_id": "42122945",
"_source": "8007",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://mastodon.social/@inautilo/113073685134759278",
"content": {
"html": "<p><a href=\"https://mastodon.social/tags/Business\">#<span>Business</span></a> <a href=\"https://mastodon.social/tags/Misconceptions\">#<span>Misconceptions</span></a><br />IndieWeb vs. indie web \u00b7 \u201cIt\u2019s unfortunate that the IndieWeb has that name.\u201d <a href=\"https://ilo.im/15zz1z\"><span>https://</span><span>ilo.im/15zz1z</span><span></span></a></p><p>_____<br /><a href=\"https://mastodon.social/tags/Terminology\">#<span>Terminology</span></a> <a href=\"https://mastodon.social/tags/HumanWeb\">#<span>HumanWeb</span></a> <a href=\"https://mastodon.social/tags/IndieWeb\">#<span>IndieWeb</span></a> <a href=\"https://mastodon.social/tags/SmallWeb\">#<span>SmallWeb</span></a> <a href=\"https://mastodon.social/tags/SlowWeb\">#<span>SlowWeb</span></a> <a href=\"https://mastodon.social/tags/OpenStandards\">#<span>OpenStandards</span></a> <a href=\"https://mastodon.social/tags/Website\">#<span>Website</span></a> <a href=\"https://mastodon.social/tags/Blog\">#<span>Blog</span></a> <a href=\"https://mastodon.social/tags/Development\">#<span>Development</span></a> <a href=\"https://mastodon.social/tags/WebDev\">#<span>WebDev</span></a></p>",
"text": "#Business #Misconceptions\nIndieWeb vs. indie web \u00b7 \u201cIt\u2019s unfortunate that the IndieWeb has that name.\u201d https://ilo.im/15zz1z\n\n_____\n#Terminology #HumanWeb #IndieWeb #SmallWeb #SlowWeb #OpenStandards #Website #Blog #Development #WebDev"
},
"published": "2024-09-03T12:45:09+00:00",
"post-type": "note",
"_id": "42122946",
"_source": "8007",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://mstdn.social/@the_cheis/113073668220500837",
"content": {
"html": "<p>Nuevo post:</p><p>On A Day Like Today (1998), de Bryan Adams</p><p><a href=\"https://mstdn.social/tags/musica\">#<span>musica</span></a> <a href=\"https://mstdn.social/tags/rock\">#<span>rock</span></a> <a href=\"https://mstdn.social/tags/poprock\">#<span>poprock</span></a> <a href=\"https://mstdn.social/tags/softrock\">#<span>softrock</span></a> <a href=\"https://mstdn.social/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://mstdn.social/tags/blog\">#<span>blog</span></a> <a href=\"https://mstdn.social/tags/enmiblog\">#<span>enmiblog</span></a></p><p><a href=\"https://thecheis.com/2024/09/03/on-a-day-like-today-1998-de-bryan-adams/\"><span>https://</span><span>thecheis.com/2024/09/03/on-a-d</span><span>ay-like-today-1998-de-bryan-adams/</span></a></p>",
"text": "Nuevo post:\n\nOn A Day Like Today (1998), de Bryan Adams\n\n#musica #rock #poprock #softrock #indieweb #blog #enmiblog\n\nhttps://thecheis.com/2024/09/03/on-a-day-like-today-1998-de-bryan-adams/"
},
"published": "2024-09-03T12:40:51+00:00",
"post-type": "note",
"_id": "42122947",
"_source": "8007",
"_is_read": false
}
Search the git history for all commits that have added or removed a string or regex pattern across all branches:
https://rm-o.dev/til/find-all-commits-that-added-or-removed-a-string/
#git #indieweb #til #blog
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://mastodon.social/@rodmoi/113073651602850657",
"content": {
"html": "<p>Search the git history for all commits that have added or removed a string or regex pattern across all branches:</p><p><a href=\"https://rm-o.dev/til/find-all-commits-that-added-or-removed-a-string/\"><span>https://</span><span>rm-o.dev/til/find-all-commits-</span><span>that-added-or-removed-a-string/</span></a></p><p><a href=\"https://mastodon.social/tags/git\">#<span>git</span></a> <a href=\"https://mastodon.social/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://mastodon.social/tags/til\">#<span>til</span></a> <a href=\"https://mastodon.social/tags/blog\">#<span>blog</span></a></p>",
"text": "Search the git history for all commits that have added or removed a string or regex pattern across all branches:\n\nhttps://rm-o.dev/til/find-all-commits-that-added-or-removed-a-string/\n\n#git #indieweb #til #blog"
},
"published": "2024-09-03T12:36:38+00:00",
"post-type": "note",
"_id": "42122948",
"_source": "8007",
"_is_read": false
}
I'm not a big lover of horror films, although I have seen a couple. However, none have left me feeling more horrified than David Lynch's Mulholland Drive, notably the diner scene at Winkie's. For me, this is the most terrifying sequence in cinema history.
https://rm-o.dev/notes/winkies/
#blog #note #indieweb #davidlynch #cinema
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://mastodon.social/@rodmoi/113073607589569922",
"content": {
"html": "<p>I'm not a big lover of horror films, although I have seen a couple. However, none have left me feeling more horrified than David Lynch's Mulholland Drive, notably the diner scene at Winkie's. For me, this is the most terrifying sequence in cinema history. </p><p><a href=\"https://rm-o.dev/notes/winkies/\"><span>https://</span><span>rm-o.dev/notes/winkies/</span><span></span></a></p><p><a href=\"https://mastodon.social/tags/blog\">#<span>blog</span></a> <a href=\"https://mastodon.social/tags/note\">#<span>note</span></a> <a href=\"https://mastodon.social/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://mastodon.social/tags/davidlynch\">#<span>davidlynch</span></a> <a href=\"https://mastodon.social/tags/cinema\">#<span>cinema</span></a></p>",
"text": "I'm not a big lover of horror films, although I have seen a couple. However, none have left me feeling more horrified than David Lynch's Mulholland Drive, notably the diner scene at Winkie's. For me, this is the most terrifying sequence in cinema history. \n\nhttps://rm-o.dev/notes/winkies/\n\n#blog #note #indieweb #davidlynch #cinema"
},
"published": "2024-09-03T12:25:26+00:00",
"post-type": "note",
"_id": "42122324",
"_source": "8007",
"_is_read": false
}
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": "http://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://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "note",
"_id": "42121555",
"_source": "1",
"_is_read": false
}
✏️ 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": "http://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=\"http://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=\"http://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=\"http://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=\"http://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=\"http://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=\"http://tantek.com/#t5Yn1_ref-1\">\u00b9</a> <a href=\"https://indieweb.social/@kevinmarks/113025295600067213\">https://indieweb.social/@kevinmarks/113025295600067213</a><br /><a href=\"http://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=\"http://tantek.com/#t5Yn1_ref-3\">\u00b3</a> <a href=\"https://indieweb.org/responses\">https://indieweb.org/responses</a><br /><a href=\"http://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=\"http://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://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "note",
"_id": "42119247",
"_source": "1",
"_is_read": false
}
After 12 years offline, my blog is back!
Converted HTMLs I had saved to markdown. It's as if nothing happened.
#indieweb
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://rrier.fr/@pc/statuses/01J6TPW4DRG4F3E2WH7MVCKP7K",
"content": {
"html": "<p>After 12 years offline, <a href=\"https://nothing.pcarrier.com\">my blog</a> is back!</p><p>Converted HTMLs I had saved to markdown. It's as if nothing happened.</p><p><a href=\"https://rrier.fr/tags/indieweb\">#<span>indieweb</span></a></p>",
"text": "After 12 years offline, my blog is back!\n\nConverted HTMLs I had saved to markdown. It's as if nothing happened.\n\n#indieweb"
},
"published": "2024-09-03T01:09:35+00:00",
"post-type": "note",
"_id": "42118291",
"_source": "8007",
"_is_read": false
}