{
"type": "entry",
"published": "2023-10-25T20:47:28-07:00",
"url": "https://nadreck.me/2023/10/the-handcrafted-artisanal-web/",
"category": [
"social-computing",
"isles-of-blogging",
"john-scalzi",
"ryan-broderick",
"social-media"
],
"name": "The Handcrafted Artisanal Web",
"content": {
"text": "John Scalzi talked a while back about How to Weave the Artisan Web:\n\n\n\n\n1.\u00a0Create/reactivate your own site, owned by you, to hold your own work.\u00a0\n\n\n\n2.\u00a0When you create that site, write or otherwise present work on your site at least once a week, every week.\n\n\n\n3.\u00a0Regularly visit the sites of other creators to read/see/experience the work they present there.\n\n\n\n4.\u00a0Promote/link the work of others, on your own site\u00a0and also\u00a0on your other social media channels where you have followers. Encourage your followers to explore more widely, beyond the algorithmic borders of \u201csocial media.\u201d\nJohn Scalzi\n\n\n\n\nI do agree with those suggestions, even if I\u2019m not always the best at doing them myself.\n\n\n\n Continue reading \u201cThe Handcrafted Artisanal Web\u201d",
"html": "<p>John Scalzi talked a while back about <a href=\"https://whatever.scalzi.com/2022/11/25/how-to-weave-the-artisan-web/\">How to Weave the Artisan Web</a>:</p>\n\n\n\n<blockquote>\n<p><strong>1.</strong>\u00a0Create/reactivate your own site, owned by you, to hold your own work.\u00a0</p>\n\n\n\n<p><strong>2.</strong>\u00a0When you create that site, write or otherwise present work on your site at least once a week, every week.</p>\n\n\n\n<p><strong>3.</strong>\u00a0Regularly visit the sites of other creators to read/see/experience the work they present there.</p>\n\n\n\n<p><strong>4.</strong>\u00a0Promote/link the work of others, on your own site\u00a0<em>and also</em>\u00a0on your other social media channels where you have followers. Encourage your followers to explore more widely, beyond the algorithmic borders of \u201csocial media.\u201d</p>\nJohn Scalzi\n</blockquote>\n\n\n\n<p>I do agree with those suggestions, even if I\u2019m not always the best at doing them myself.</p>\n\n\n\n <a href=\"https://nadreck.me/2023/10/the-handcrafted-artisanal-web/#more-11763\">Continue reading<span> \u201cThe Handcrafted Artisanal Web\u201d</span></a>"
},
"author": {
"type": "card",
"name": "Nadreck",
"url": "http://nadreck.me",
"photo": null
},
"post-type": "note",
"_id": "39276677",
"_source": "2935"
}
Several key points of POSSE explained in the article:
First, post on your own site:
“In a POSSE world, everybody owns a domain name, and everybody has a blog. (… a place on the internet where you post your stuff and others consume it.)”
Second, syndicate elsewhere, appropriately for each destination:
“Then, your long blog post might be broken into chunks and posted as a thread on X and Mastodon and Threads. The whole thing might go to your Medium page and your Tumblr and your LinkedIn profile, too. If you post a photo, it might go straight to Instagram, and a vertical video would whoosh straight to TikTok, Reels, and Shorts. Your post appears natively on all of those platforms,”
You can use Bridgy Publish (https://brid.gy/) to POSSE to many destinations, and Bridgy Fed (https://fed.brid.gy/) to #federate to #Mastodon and other #fediverse destinations, directly from your site instead of posting a copy on yet another account on yet another server.
Third, and this is a key piece that distinguishes proper POSSE setups, with original post perma(short)links back to your posts on your domain:
“typically with some kind of link back to your blog.”
All copies link to (your) home.
"And your blog becomes the hub for everything, your main home on the internet."
You have power over your domain (name), not outside silos.
David embedded a screenshot of one of my posts, a reply post:
in which I posted a reply *on my own site*¹ to @Zeldman.com’s tweet (itself a reply to a POSSE copy of one of my posts), and POSSEd my reply to Twitter so it would thread with his reply.
This illustrates another important detail of a proper POSSE setup:
Fourth, post *replies* and other responses from your own site, whether to other #IndieWeb sites, or to others’s silo posts (tweets etc.).
Own your data means owning your replies as well.
David also noted several challenges and good questions about POSSE. Some of these have answers & established practices, others are areas of exploration. E.g.
"The first is the social side of social media: what do you do with all the likes, replies, comments, and everything else that comes with your posts?"
Backfeed is a concept I first wrote about as “reverse syndication”².
As you syndicate your posts out to #socialMedia silos, you reverse syndicate any responses there back to your original post.
Your site can do this with a service like #Bridgy, which uses the #Webmention standard to forward such silo responses back to your site, and #BridgyFed which does same for responses from Mastodon to your #federated posts.
David asked many other questions, which are deserving of their own posts to help answer, so I’ll leave you with just one more:
"The most immediate question, though, is simply how to build a POSSE system that works."
Even if you have to do it manually (until it hurts), even if you have to edit your posts on a static GitHub site (behind your domain name of course), and then copy & paste to your silo(s) of choice, just start.
By practicing POSSE, even manually, you will learn what aspects of POSSE & backfeed matter the most to you, what aspects actually involve reaching & responding to friends and others you care about.
By doing so you will naturally focus on setting up & making what you need, and you too can join the future of web publishing, today.
{
"type": "entry",
"published": "2023-10-23 17:30-0700",
"url": "https://tantek.com/2023/296/t1/posse-syndicate-link-reply",
"category": [
"POSSE",
"federate",
"Mastodon",
"fediverse",
"IndieWeb",
"backfeed:",
"socialMedia",
"Bridgy",
"Webmention",
"BridgyFed",
"federated",
"100DaysOfIndieWeb",
"100Days"
],
"content": {
"text": "Great article on #POSSE by David Pierce (@davidpierce@mastodon.social @pierce) @Verge:\n\nhttps://www.theverge.com/2023/10/23/23928550/posse-posting-activitypub-standard-twitter-tumblr-mastodon\n\nSeveral key points of POSSE explained in the article:\n\n\nFirst, post on your own site:\n\n\u00a0\u201cIn a POSSE world, everybody owns a domain name, and everybody has a blog. (\u2026 a place on the internet where you post your stuff and others consume it.)\u201d\n\u00a0\n\nSecond, syndicate elsewhere, appropriately for each destination:\n\n\u00a0\u201cThen, your long blog post might be broken into chunks and posted as a thread on X and Mastodon and Threads. The whole thing might go to your Medium page and your Tumblr and your LinkedIn profile, too. If you post a photo, it might go straight to Instagram, and a vertical video would whoosh straight to TikTok, Reels, and Shorts. Your post appears natively on all of those platforms,\u201d\n\nYou can use Bridgy Publish (https://brid.gy/) to POSSE to many destinations, and Bridgy Fed (https://fed.brid.gy/) to #federate to #Mastodon and other #fediverse destinations, directly from your site instead of posting a copy on yet another account on yet another server.\n\n\nThird, and this is a key piece that distinguishes proper POSSE setups, with original post perma(short)links back to your posts on your domain:\n\n\u00a0\u201ctypically with some kind of link back to your blog.\u201d\n\u00a0\n\nAll copies link to (your) home.\n\n\u00a0\"And your blog becomes the hub for everything, your main home on the internet.\"\n\u00a0\n\nYou have power over your domain (name), not outside silos.\n\n\nDavid embedded a screenshot of one of my posts, a reply post:\n\n\nin which I posted a reply *on my own site*\u00b9 to @Zeldman.com\u2019s tweet (itself a reply to a POSSE copy of one of my posts), and POSSEd my reply to Twitter so it would thread with his reply.\n\nThis illustrates another important detail of a proper POSSE setup:\n\nFourth, post *replies* and other responses from your own site, whether to other #IndieWeb sites, or to others\u2019s silo posts (tweets etc.).\n\nOwn your data means owning your replies as well.\n\n\nDavid also noted several challenges and good questions about POSSE. Some of these have answers & established practices, others are areas of exploration. E.g.\n\n\u00a0\"The first is the social side of social media: what do you do with all the likes, replies, comments, and everything else that comes with your posts?\"\n\u00a0\nThe short answer is #backfeed: https://indieweb.org/backfeed\n\nBackfeed is a concept I first wrote about as \u201creverse syndication\u201d\u00b2. \n\nAs you syndicate your posts out to #socialMedia silos, you reverse syndicate any responses there back to your original post. \n\nYour site can do this with a service like #Bridgy, which uses the #Webmention standard to forward such silo responses back to your site, and #BridgyFed which does same for responses from Mastodon to your #federated posts.\n\n\nDavid asked many other questions, which are deserving of their own posts to help answer, so I\u2019ll leave you with just one more:\n\n\u00a0\"The most immediate question, though, is simply how to build a POSSE system that works.\"\n\nThe short answer is: just start\u00b3.\n\nEven if you have to do it manually (until it hurts), even if you have to edit your posts on a static GitHub site (behind your domain name of course), and then copy & paste to your silo(s) of choice, just start.\n\nBy practicing POSSE, even manually, you will learn what aspects of POSSE & backfeed matter the most to you, what aspects actually involve reaching & responding to friends and others you care about. \n\nBy doing so you will naturally focus on setting up & making what you need, and you too can join the future of web publishing, today.\n\nQuestions? Join us in the chat: https://chat.indieweb.org/ (also on Discord, IRC, and Slack\u2074)\n\n\nThis is day 46 of #100DaysOfIndieWeb. #100Days\n\n\u2190 Day 45: https://tantek.com/2023/289/t1/bridgyfed-webmention-like-fediverse\n\u2192 \ud83d\udd2e\n\n\nPost glossary:\n\nbackfeed / reverse syndication\n\u00a0 https://indieweb.org/backfeed\nBridgy \n\u00a0 https://brid.gy/\nmake what you need\n\u00a0 https://indieweb.org/make_what_you_need\nmanual (until it hurts)\n\u00a0 https://indieweb.org/manual_until_it_hurts\noriginal post link\n\u00a0 https://indieweb.org/original_post_link\nown your data\n\u00a0 https://indieweb.org/own_your_data\nown your replies\n\u00a0 https://indieweb.org/own_your_replies\npermalink \n\u00a0 https://indieweb.org/permalink\npermashortlink\n\u00a0 https://indieweb.org/permashortlink\nPOSSE\n\u00a0 https://indieweb.org/POSSE\nsilo\n\u00a0 https://indieweb.org/silo\nsocial media\n\u00a0 https://indieweb.org/social_media\nstatic site\n\u00a0 https://indieweb.org/static_site\nstart\n\u00a0 https://indieweb.org/start\nWebmention\n\u00a0 https://indieweb.org/Webmention\n\n\n\u00b9 https://tantek.com/2023/253/t2/\n\u00b2 https://tantek.com/2010/034/t2/diso-2-personal-domains-shortener-hatom-push-relmeauth\n\u00b3 https://tantek.com/2023/001/t1/own-your-notes\n\u2074 https://indieweb.org/discuss",
"html": "Great article on #<span class=\"p-category\">POSSE</span> by David Pierce (<a href=\"https://mastodon.social/@davidpierce\">@davidpierce@mastodon.social</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/pierce\">@pierce</a>) <a class=\"h-cassis-username\" href=\"https://twitter.com/Verge\">@Verge</a>:<br /><br /><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 /><br />Several key points of POSSE explained in the article:<br /><br /><br />First, post on your own site:<br /><br />\u00a0\u201cIn a POSSE world, everybody owns a domain name, and everybody has a blog. (\u2026 a place on the internet where you post your stuff and others consume it.)\u201d<br />\u00a0<br /><br />Second, syndicate elsewhere, appropriately for each destination:<br /><br />\u00a0\u201cThen, your long blog post might be broken into chunks and posted as a thread on X and Mastodon and Threads. The whole thing might go to your Medium page and your Tumblr and your LinkedIn profile, too. If you post a photo, it might go straight to Instagram, and a vertical video would whoosh straight to TikTok, Reels, and Shorts. Your post appears natively on all of those platforms,\u201d<br /><br />You can use Bridgy Publish (<a href=\"https://brid.gy/\">https://brid.gy/</a>) to POSSE to many destinations, and Bridgy Fed (<a href=\"https://fed.brid.gy/\">https://fed.brid.gy/</a>) to #<span class=\"p-category\">federate</span> to #<span class=\"p-category\">Mastodon</span> and other #<span class=\"p-category\">fediverse</span> destinations, directly from your site instead of posting a copy on yet another account on yet another server.<br /><br /><br />Third, and this is a key piece that distinguishes proper POSSE setups, with original post perma(short)links back to your posts on your domain:<br /><br />\u00a0\u201ctypically with some kind of link back to your blog.\u201d<br />\u00a0<br /><br />All copies link to (your) home.<br /><br />\u00a0\"And your blog becomes the hub for everything, your main home on the internet.\"<br />\u00a0<br /><br />You have power over your domain (name), not outside silos.<br /><br /><br />David embedded a screenshot of one of my posts, a reply post:<br /><br /><a href=\"https://tantek.com/2023/253/t2/\"><img alt=\"screenshot of Tantek replying to a tweet by Zeldman.\" src=\"https://duet-cdn.vox-cdn.com/thumbor/0x0:1758x1046/1920x1142/filters:focal(879x523:880x524):format(webp)/cdn.vox-cdn.com/uploads/chorus_asset/file/25024444/CleanShot_2023_10_23_at_09.36.40_2x.png\" /></a><br />in which I posted a reply *on my own site*<a href=\"https://tantek.com/#t5TZ1_note-1\">\u00b9</a> to <a href=\"https://Zeldman.com\">@Zeldman.com</a>\u2019s tweet (itself a reply to a POSSE copy of one of my posts), and POSSEd my reply to Twitter so it would thread with his reply.<br /><br />This illustrates another important detail of a proper POSSE setup:<br /><br />Fourth, post *replies* and other responses from your own site, whether to other #<span class=\"p-category\">IndieWeb</span> sites, or to others\u2019s silo posts (tweets etc.).<br /><br />Own your data means owning your replies as well.<br /><br /><br />David also noted several challenges and good questions about POSSE. Some of these have answers & established practices, others are areas of exploration. E.g.<br /><br />\u00a0\"The first is the social side of social media: what do you do with all the likes, replies, comments, and everything else that comes with your posts?\"<br />\u00a0<br />The short answer is #<span class=\"p-category\">backfeed:</span> <a href=\"https://indieweb.org/backfeed\">https://indieweb.org/backfeed</a><br /><br />Backfeed is a concept I first wrote about as \u201creverse syndication\u201d<a href=\"https://tantek.com/#t5TZ1_note-2\">\u00b2</a>. <br /><br />As you syndicate your posts out to #<span class=\"p-category\">socialMedia</span> silos, you reverse syndicate any responses there back to your original post. <br /><br />Your site can do this with a service like #<span class=\"p-category\">Bridgy</span>, which uses the #<span class=\"p-category\">Webmention</span> standard to forward such silo responses back to your site, and #<span class=\"p-category\">BridgyFed</span> which does same for responses from Mastodon to your #<span class=\"p-category\">federated</span> posts.<br /><br /><br />David asked many other questions, which are deserving of their own posts to help answer, so I\u2019ll leave you with just one more:<br /><br />\u00a0\"The most immediate question, though, is simply how to build a POSSE system that works.\"<br /><br />The short answer is: just start<a href=\"https://tantek.com/#t5TZ1_note-3\">\u00b3</a>.<br /><br />Even if you have to do it manually (until it hurts), even if you have to edit your posts on a static GitHub site (behind your domain name of course), and then copy & paste to your silo(s) of choice, just start.<br /><br />By practicing POSSE, even manually, you will learn what aspects of POSSE & backfeed matter the most to you, what aspects actually involve reaching & responding to friends and others you care about. <br /><br />By doing so you will naturally focus on setting up & making what you need, and you too can join the future of web publishing, today.<br /><br />Questions? Join us in the chat: <a href=\"https://chat.indieweb.org/\">https://chat.indieweb.org/</a> (also on Discord, IRC, and Slack<a href=\"https://tantek.com/#t5TZ1_note-4\">\u2074</a>)<br /><br /><br />This is day 46 of #<span class=\"p-category\">100DaysOfIndieWeb</span>. #<span class=\"p-category\">100Days</span><br /><br />\u2190 Day 45: <a href=\"https://tantek.com/2023/289/t1/bridgyfed-webmention-like-fediverse\">https://tantek.com/2023/289/t1/bridgyfed-webmention-like-fediverse</a><br />\u2192 \ud83d\udd2e<br /><br /><br />Post glossary:<br /><br />backfeed / reverse syndication<br />\u00a0 <a href=\"https://indieweb.org/backfeed\">https://indieweb.org/backfeed</a><br />Bridgy <br />\u00a0 <a href=\"https://brid.gy/\">https://brid.gy/</a><br />make what you need<br />\u00a0 <a href=\"https://indieweb.org/make_what_you_need\">https://indieweb.org/make_what_you_need</a><br />manual (until it hurts)<br />\u00a0 <a href=\"https://indieweb.org/manual_until_it_hurts\">https://indieweb.org/manual_until_it_hurts</a><br />original post link<br />\u00a0 <a href=\"https://indieweb.org/original_post_link\">https://indieweb.org/original_post_link</a><br />own your data<br />\u00a0 <a href=\"https://indieweb.org/own_your_data\">https://indieweb.org/own_your_data</a><br />own your replies<br />\u00a0 <a href=\"https://indieweb.org/own_your_replies\">https://indieweb.org/own_your_replies</a><br />permalink <br />\u00a0 <a href=\"https://indieweb.org/permalink\">https://indieweb.org/permalink</a><br />permashortlink<br />\u00a0 <a href=\"https://indieweb.org/permashortlink\">https://indieweb.org/permashortlink</a><br />POSSE<br />\u00a0 <a href=\"https://indieweb.org/POSSE\">https://indieweb.org/POSSE</a><br />silo<br />\u00a0 <a href=\"https://indieweb.org/silo\">https://indieweb.org/silo</a><br />social media<br />\u00a0 <a href=\"https://indieweb.org/social_media\">https://indieweb.org/social_media</a><br />static site<br />\u00a0 <a href=\"https://indieweb.org/static_site\">https://indieweb.org/static_site</a><br />start<br />\u00a0 <a href=\"https://indieweb.org/start\">https://indieweb.org/start</a><br />Webmention<br />\u00a0 <a href=\"https://indieweb.org/Webmention\">https://indieweb.org/Webmention</a><br /><br /><br /><a href=\"https://tantek.com/#t5TZ1_ref-1\">\u00b9</a> <a href=\"https://tantek.com/2023/253/t2/\">https://tantek.com/2023/253/t2/</a><br /><a href=\"https://tantek.com/#t5TZ1_ref-2\">\u00b2</a> <a href=\"https://tantek.com/2010/034/t2/diso-2-personal-domains-shortener-hatom-push-relmeauth\">https://tantek.com/2010/034/t2/diso-2-personal-domains-shortener-hatom-push-relmeauth</a><br /><a href=\"https://tantek.com/#t5TZ1_ref-3\">\u00b3</a> <a href=\"https://tantek.com/2023/001/t1/own-your-notes\">https://tantek.com/2023/001/t1/own-your-notes</a><br /><a href=\"https://tantek.com/#t5TZ1_ref-4\">\u2074</a> <a href=\"https://indieweb.org/discuss\">https://indieweb.org/discuss</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "39256829",
"_source": "2460"
}
The deadline to submit drafts ahead of the IETF meeting in November just passed, and I submitted my last one with 30 minutes to spare! Here are all the docs I'll be discussing:
{
"type": "entry",
"published": "2023-10-23T17:15:49-07:00",
"url": "https://aaronparecki.com/2023/10/23/9/oauth",
"category": [
"oauth",
"ietf"
],
"content": {
"text": "The deadline to submit drafts ahead of the IETF meeting in November just passed, and I submitted my last one with 30 minutes to spare! Here are all the docs I'll be discussing: \n\nhttps://www.ietf.org/archive/id/draft-ietf-oauth-browser-based-apps-15.html \n\nhttps://www.ietf.org/archive/id/draft-ietf-oauth-resource-metadata-01.html \n\nhttps://www.ietf.org/archive/id/draft-parecki-oauth-first-party-apps-00.html \n\nhttps://www.ietf.org/archive/id/draft-parecki-oauth-metadata-for-nested-flows-00.html",
"html": "The deadline to submit drafts ahead of the IETF meeting in November just passed, and I submitted my last one with 30 minutes to spare! Here are all the docs I'll be discussing: <br /><br /><a href=\"https://www.ietf.org/archive/id/draft-ietf-oauth-browser-based-apps-15.html\"><span>https://</span>www.ietf.org/archive/id/draft-ietf-oauth-browser-based-apps-15.html</a> <br /><br /><a href=\"https://www.ietf.org/archive/id/draft-ietf-oauth-resource-metadata-01.html\"><span>https://</span>www.ietf.org/archive/id/draft-ietf-oauth-resource-metadata-01.html</a> <br /><br /><a href=\"https://www.ietf.org/archive/id/draft-parecki-oauth-first-party-apps-00.html\"><span>https://</span>www.ietf.org/archive/id/draft-parecki-oauth-first-party-apps-00.html</a> <br /><br /><a href=\"https://www.ietf.org/archive/id/draft-parecki-oauth-metadata-for-nested-flows-00.html\"><span>https://</span>www.ietf.org/archive/id/draft-parecki-oauth-metadata-for-nested-flows-00.html</a>"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/41061f9de825966faa22e9c42830e1d4a614a321213b4575b9488aa93f89817a.jpg"
},
"post-type": "note",
"_id": "39256188",
"_source": "16"
}
I checked and was not surprised to learn that Anil and I are very close in age. We were kids when personal computers were new and we were probably both in middle or high school when the web was born. We seem to have similar perspectives on the why of the open web: why building a more open web is — in addition to being fun — an important public good.
Anil’s framing is very personal, though, and I found it very moving. The full talk is available on YouTube and feels like it deserves more than its current ~650 views.
{
"type": "entry",
"author": {
"name": null,
"url": "https://davepeck.org/micro/",
"photo": null
},
"url": "https://davepeck.org/2023/10/23/anil-dash-at-oh-the-humanity/",
"published": "2023-10-23T10:09:00-07:00",
"content": {
"html": "<p><a href=\"https://www.anildash.com/\">Anil Dash</a> gave a <a href=\"https://www.youtube.com/watch?v=x9wbRUW57sc\">delightful keynote address</a> at last week\u2019s <a href=\"https://oh.helsinkiruby.fi/\">Oh, the Humanity!</a> conference.</p>\n\n<p>I checked and was not surprised to learn that Anil and I are very close in age. We were kids when personal computers were new and we were probably both in middle or high school when the web was born. We seem to have similar perspectives on the <em>why</em> of the open web: <em>why</em> building a more open web is \u2014 in addition to being fun \u2014 an important public good.</p>\n\n<p>Anil\u2019s framing is very personal, though, and I found it very moving. The full talk is <a href=\"https://www.youtube.com/watch?v=x9wbRUW57sc\">available on YouTube</a> and feels like it deserves more than its current ~650 views.</p>",
"text": "Anil Dash gave a delightful keynote address at last week\u2019s Oh, the Humanity! conference.\n\nI checked and was not surprised to learn that Anil and I are very close in age. We were kids when personal computers were new and we were probably both in middle or high school when the web was born. We seem to have similar perspectives on the why of the open web: why building a more open web is \u2014 in addition to being fun \u2014 an important public good.\n\nAnil\u2019s framing is very personal, though, and I found it very moving. The full talk is available on YouTube and feels like it deserves more than its current ~650 views."
},
"post-type": "note",
"_id": "39254647",
"_source": "2781"
}
After a lot of discussion on the mailing list over the last few months, and after some excellent discussions at the OAuth Security Workshop, we've been working on revising the draft to provide clearer guidance and clearer discussion of the threats and consequences of the various architectural patterns in the draft.
{
"type": "entry",
"published": "2023-10-23T09:12:55-07:00",
"summary": "After a lot of discussion on the mailing list over the last few months, and after some excellent discussions at the OAuth Security Workshop, we've been working on revising the draft to provide clearer guidance and clearer discussion of the threats and consequences of the various architectural patterns in the draft.",
"url": "https://aaronparecki.com/2023/10/23/5/oauth-browser-based-apps-draft-15",
"category": [
"oauth",
"ietf"
],
"name": "OAuth for Browser-Based Apps Draft 15",
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/41061f9de825966faa22e9c42830e1d4a614a321213b4575b9488aa93f89817a.jpg"
},
"post-type": "article",
"_id": "39252934",
"_source": "16"
}
{
"type": "entry",
"published": "2023-10-22T19:24:12-07:00",
"url": "https://aaronparecki.com/2023/10/22/11/mics",
"category": [
"homeautomation"
],
"content": {
"text": "was it absolutely necessary to run cables for ceiling mics in 5 rooms? definitely not. but now I am all set up to film a reality show \ud83d\ude02",
"html": "was it absolutely necessary to run cables for ceiling mics in 5 rooms? definitely not. but now I am all set up to film a reality show <a href=\"https://aaronparecki.com/emoji/%F0%9F%98%82\">\ud83d\ude02</a>"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/84db372c0f0b26c38c2198e5bdb4c3e61438aad138710b886ba2b72963215ccf.jpg"
},
"post-type": "note",
"_id": "39247507",
"_source": "16"
}
{
"type": "entry",
"published": "2023-10-22T18:59:41-07:00",
"url": "https://beesbuzz.biz/blog/5784-I-did-the-thing",
"photo": [
"https://beesbuzz.biz/_async/.eJyLVkrOzytJzSvRT8rJT9f39HWPNzM2NtXLKkhNV9Ix1KlWyk2siC_PTCnJULIyMjHQAfMzUjPTM0qgAkWpxZlVqUpWSmmZOTlKOkpp-UW5iUBJpfLUpAKl2lgAPjwf3w.rn2M2f66Zj--GPOymxHDyf33qn8",
"https://beesbuzz.biz/_async/.eJyLVkrOzytJzSvRT8rJT9f39HWPNzM2MdTLKkhNV9Ix1KlWyk2siC_PTCnJULIyMjHQAfMzUjPTM0qgAkWpxZlVqUpWSmmZOTlKOkpp-UW5iUBJpfLUpAKl2lgAPVYf3A.m36eVod6AtUtIEkfAxHvx0CXD_Q"
],
"name": "I did the thing",
"content": {
"text": "The plan went pretty much according to keikaku1.\nI had difficulty finding the studs because there\u2019s some particleboard behind the drywall for some reason. Maybe some half-assed attempt at a moisture barrier or something? It was pretty obvious that it was there since it was visible through the light wiring hole. I ended up using some neodymium magnets to locate some drywall screws and then verified it by drilling pilot holes. I\u2019m not absolutely certain that they\u2019re screwed into studs but there\u2019s a lot more support than there was before, and those screws are at least held tight to the wall.On the left anchor I thought I\u2019d messed up and that there actually was a stud behind it, somehow, and I started to patch it up so that I could screw in a construction screw instead (which is why there\u2019s plaster on the left hole in the first picture), until I remembered, oh yeah, there\u2019s weird backing board behind some of the drywall. So I drilled a smaller pilot hole and, yep, it went through easily, so yeah, it needed an anchor after all. (I mean I already knew that based on what had happened previously, but, still.)Also I couldn\u2019t find the nice toggle anchors I\u2019d bought a couple years ago, so I ended up buying some similar ones at Home Depot. Which aren\u2019t nearly as nice. A couple of them ended up breaking off and falling into the wall, and they were just kinda not-great to work with in general. But they did their job, and everything\u2019s tightly screwed down.Leveling the cabinet was a pain in the ass. It\u2019d have been a lot easier if I had someone to help me but I was being stubborn about just getting this done.Also, I didn\u2019t need to do any painting, as all of the paint damage happened to be behind the cabinet. Nice.Hopefully this time it stays up for more than two years!\nAlso I decided to be fancy and whipped up a custom centering jig to draw the centerline for drilling the holes in the hardwood. It was absolutely overkill but it didn\u2019t take me long to do. I\u2019ll probably post it as a customizable object on thingiverse/printables or something.",
"html": "<p><a href=\"https://beesbuzz.biz/blog/6868-Bathroom-remodel-day-wait-what\">The plan</a> went pretty much according to keikaku<a href=\"https://beesbuzz.biz/blog/5784-I-did-the-thing#d_e5784_fn1\">1</a>.</p>\n<a href=\"https://beesbuzz.biz/blog/5784-I-did-the-thing\"></a><a href=\"https://beesbuzz.biz/blog/5784-I-did-the-thing\"></a><a href=\"https://beesbuzz.biz/blog/5784-I-did-the-thing\"></a><a href=\"https://beesbuzz.biz/blog/5784-I-did-the-thing\"></a><a href=\"https://beesbuzz.biz/blog/5784-I-did-the-thing\"></a><p>I had difficulty finding the studs because there\u2019s some particleboard behind the drywall for some reason. Maybe some half-assed attempt at a moisture barrier or something? It was pretty obvious that it was there since it was visible through the light wiring hole. I ended up using some neodymium magnets to locate some drywall screws and then verified it by drilling pilot holes. I\u2019m not absolutely certain that they\u2019re screwed into studs but there\u2019s a lot more support than there was before, and those screws are at least held tight to the wall.</p><p>On the left anchor I thought I\u2019d messed up and that there actually <em>was</em> a stud behind it, somehow, and I started to patch it up so that I could screw in a construction screw instead (which is why there\u2019s plaster on the left hole in the first picture), until I remembered, oh yeah, there\u2019s weird backing board behind some of the drywall. So I drilled a smaller pilot hole and, yep, it went through easily, so yeah, it needed an anchor after all. (I mean I already <em>knew</em> that based on what had happened previously, but, still.)</p><p>Also I couldn\u2019t find the nice toggle anchors I\u2019d bought a couple years ago, so I ended up buying some similar ones at Home Depot. Which aren\u2019t <em>nearly</em> as nice. A couple of them ended up breaking off and falling into the wall, and they were just kinda not-great to work with in general. But they did their job, and everything\u2019s tightly screwed down.</p><p>Leveling the cabinet was a pain in the ass. It\u2019d have been a lot easier if I had someone to help me but I was being stubborn about just getting this done.</p><p>Also, I didn\u2019t need to do any painting, as all of the paint damage happened to be behind the cabinet. Nice.</p><p>Hopefully this time it stays up for more than two years!</p>\n<a href=\"https://beesbuzz.biz/blog/5784-I-did-the-thing\"></a><p>Also I decided to be fancy and whipped up a custom centering jig to draw the centerline for drilling the holes in the hardwood. It was absolutely overkill but it didn\u2019t take me long to do. I\u2019ll probably post it as a customizable object on thingiverse/printables or something.</p>"
},
"author": {
"type": "card",
"name": "fluffy",
"url": "https://beesbuzz.biz/",
"photo": "https://beesbuzz.biz/static/headshot.jpg"
},
"post-type": "photo",
"_id": "39247424",
"_source": "2778"
}
{
"type": "entry",
"published": "2023-10-22T04:22:44-07:00",
"url": "https://aaronparecki.com/2023/10/22/1/",
"content": {
"text": "I woke up before taking a pizza out of the oven in a dream and now that's going to be bugging me all day"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/41061f9de825966faa22e9c42830e1d4a614a321213b4575b9488aa93f89817a.jpg"
},
"post-type": "note",
"_id": "39242984",
"_source": "16"
}
{
"type": "entry",
"published": "2023-10-20T00:31:28-07:00",
"url": "https://beesbuzz.biz/blog/12349-Bandcrash-early-alpha-beta-whatever-released",
"name": "Bandcrash early alpha/beta/whatever released",
"content": {
"text": "So hey, the Bandcrash GUI is finally, finally in a working state! You can now use it to easily encode a bunch of wav files into mp3/ogg/flac and make a web preview, and optionally upload it all to itch.io automagically!Also, I\u2019ve released prebuilt macOS and Windows binaries over on itch.io. I\u2019ll probably do a Linux version as well at some point, although Linux users are likely much better-equipped to just build-and-install it themselves.To that end, I used it to upload one of my older albums to itch, and I gotta say, having a GUI to set it up is actually a lot nicer than doing it all from the CLI with hand-written JSON files? Weird.There\u2019s still a lot left to do on it but what is there right now is Good Enough for now.That said, I\u2019m hopeful that bandcamp remains viable for the long term, but now it\u2019s a lot less necessary to worry about a single platform like that.",
"html": "<p>So hey, the <a href=\"https://github.com/fluffy-critter/bandcrash\">Bandcrash</a> GUI is finally, finally in a working state! You can now use it to easily encode a bunch of wav files into mp3/ogg/flac and make a web preview, and optionally upload it all to itch.io automagically!</p><p>Also, I\u2019ve released prebuilt macOS and Windows binaries <a href=\"https://fluffy.itch.io/bandcrash\">over on itch.io</a>. I\u2019ll probably do a Linux version as well at some point, although Linux users are likely much better-equipped to just build-and-install it themselves.</p><p>To that end, I used it to upload <a href=\"https://fluffy.itch.io/foodsexsleep\">one of my older albums</a> to itch, and I gotta say, having a GUI to set it up is actually a lot nicer than doing it all from the CLI with hand-written JSON files? Weird.</p><p>There\u2019s still <a href=\"https://github.com/fluffy-critter/bandcrash\">a lot left to do on it</a> but what is there right now is Good Enough for now.</p><p>That said, I\u2019m hopeful that bandcamp remains viable for the long term, but now it\u2019s a lot less necessary to worry about a single platform like that.</p>"
},
"author": {
"type": "card",
"name": "fluffy",
"url": "https://beesbuzz.biz/",
"photo": "https://beesbuzz.biz/static/headshot.jpg"
},
"post-type": "article",
"_id": "39225778",
"_source": "2778"
}
{
"type": "entry",
"published": "2023-10-17T16:56:30-07:00",
"url": "https://nadreck.me/2023/10/october-in-new-england/",
"category": [
"life",
"travel"
],
"name": "October in New England",
"content": {
"text": "Here we are, halfway through October. It\u2019s been a bit over a month since my last post. In that time, we spent more time in Peterborough, New York City, Newport (Vermont), and Holderness. We socialized, we saw friends, saw family, had a good time. It\u2019s starting to get cooler out, and we\u2019re currently far enough north that the leaves have begun dropping in earnest.\n\n\n\nContinue reading \u201cOctober in New England\u201d",
"html": "<p>Here we are, halfway through October. It\u2019s been a bit over a month since my last post. In that time, we spent more time in Peterborough, New York City, Newport (Vermont), and Holderness. We socialized, we saw friends, saw family, had a good time. It\u2019s starting to get cooler out, and we\u2019re currently far enough north that the leaves have begun dropping in earnest.</p>\n\n\n\n<img width=\"1024\" height=\"768\" src=\"https://nadreck.me/backend/wp-content/uploads/2023/10/2023-10-09-22.16.53-1024x768.jpg\" alt=\"\" /><img width=\"1024\" height=\"768\" src=\"https://nadreck.me/backend/wp-content/uploads/2023/10/2023-10-09-22.16.53-1024x768.jpg\" alt=\"\" /><a href=\"https://nadreck.me/2023/10/october-in-new-england/#more-11756\">Continue reading<span> \u201cOctober in New England\u201d</span></a>"
},
"author": {
"type": "card",
"name": "Nadreck",
"url": "http://nadreck.me",
"photo": null
},
"post-type": "note",
"_id": "39203260",
"_source": "2935"
}
Implemented liking/favoriting of #Mastodon posts via Bridgy Fed on my site! (Actually of any post on any site that #BridgyFed can discover an #ActivityPub endpoint to send likes to.)
Tested it by liking @evanp.me (@evan@cosocial.ca@evanpro)’s reply¹ confirming that he received a notification from my prior post². I sent a #Webmention from my like post³ to Bridgy Fed, and it #federated the like to Evan’s server, which subsequently showed up in the "favourites" list of Evan’s post:
{
"type": "entry",
"published": "2023-10-16 18:16-0700",
"url": "https://tantek.com/2023/289/t1/bridgyfed-webmention-like-fediverse",
"category": [
"Mastodon",
"BridgyFed",
"ActivityPub",
"Webmention",
"federated",
"socialWeb",
"100DaysOfIndieWeb",
"100Days",
"IndieWeb",
"like",
"likes",
"fediverse",
"favorite",
"favourite",
"favourites"
],
"content": {
"text": "Implemented liking/favoriting of #Mastodon posts via Bridgy Fed on my site! (Actually of any post on any site that #BridgyFed can discover an #ActivityPub endpoint to send likes to.)\n\nTested it by liking @evanp.me (@evan@cosocial.ca @evanpro)\u2019s reply\u00b9 confirming that he received a notification from my prior post\u00b2. I sent a #Webmention from my like post\u00b3 to Bridgy Fed, and it #federated the like to Evan\u2019s server, which subsequently showed up in the \"favourites\" list of Evan\u2019s post:\n\nhttps://cosocial.ca/@evan/111237962392745000/favourites\n\nEvery step that connects heterogenous #socialWeb systems & protocols feels like progress.\n\nThis is day 45 of #100DaysOfIndieWeb. #100Days #IndieWeb #like #likes #fediverse #favorite #favourite #favourites\n\n\u2190 Day 44: https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me\n\u2192 \ud83d\udd2e\n\n\u00b9 https://cosocial.ca/@evan/111237962392745000\n\u00b2 https://tantek.com/2023/287/t1/federating-mentions\n\u00b3 https://tantek.com/2023/289/f1",
"html": "Implemented liking/favoriting of #<span class=\"p-category\">Mastodon</span> posts via Bridgy Fed on my site! (Actually of any post on any site that #<span class=\"p-category\">BridgyFed</span> can discover an #<span class=\"p-category\">ActivityPub</span> endpoint to send likes to.)<br /><br />Tested it by liking <a href=\"https://evanp.me\">@evanp.me</a> (<a href=\"https://cosocial.ca/@evan\">@evan@cosocial.ca</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/evanpro\">@evanpro</a>)\u2019s reply<a href=\"https://tantek.com/#t5TS1_note-1\">\u00b9</a> confirming that he received a notification from my prior post<a href=\"https://tantek.com/#t5TS1_note-2\">\u00b2</a>. I sent a #<span class=\"p-category\">Webmention</span> from my like post<a href=\"https://tantek.com/#t5TS1_note-3\">\u00b3</a> to Bridgy Fed, and it #<span class=\"p-category\">federated</span> the like to Evan\u2019s server, which subsequently showed up in the \"favourites\" list of Evan\u2019s post:<br /><br /><a href=\"https://cosocial.ca/@evan/111237962392745000/favourites\">https://cosocial.ca/@evan/111237962392745000/favourites</a><br /><br />Every step that connects heterogenous #<span class=\"p-category\">socialWeb</span> systems & protocols feels like progress.<br /><br />This is day 45 of #<span class=\"p-category\">100DaysOfIndieWeb</span>. #<span class=\"p-category\">100Days</span> #<span class=\"p-category\">IndieWeb</span> #<span class=\"p-category\">like</span> #<span class=\"p-category\">likes</span> #<span class=\"p-category\">fediverse</span> #<span class=\"p-category\">favorite</span> #<span class=\"p-category\">favourite</span> #<span class=\"p-category\">favourites</span><br /><br />\u2190 Day 44: <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 />\u2192 \ud83d\udd2e<br /><br /><a href=\"https://tantek.com/#t5TS1_ref-1\">\u00b9</a> <a href=\"https://cosocial.ca/@evan/111237962392745000\">https://cosocial.ca/@evan/111237962392745000</a><br /><a href=\"https://tantek.com/#t5TS1_ref-2\">\u00b2</a> <a href=\"https://tantek.com/2023/287/t1/federating-mentions\">https://tantek.com/2023/287/t1/federating-mentions</a><br /><a href=\"https://tantek.com/#t5TS1_ref-3\">\u00b3</a> <a href=\"https://tantek.com/2023/289/f1\">https://tantek.com/2023/289/f1</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "39194453",
"_source": "2460"
}
:format(webp)/cdn.vox-cdn.com/uploads/chorus_asset/file/25024444/CleanShot_2023_10_23_at_09.36.40_2x.png)
