coding at #IndieWebCamp Nuremberg, completed the following projects:
0.0: fixed the https://chat.indieweb.org/ footer to drop #Matrix as an access option since their bridge is disabled (#IndieWeb IRC, Discord, and Slack still work great), and provide an explicit link/encouragement for filing issues
0.7: add HTML <search> element support to my home page and permalinks as nerdsniped by @adactio.com (@adactio@mastodon.social@adactio); expanded to <search role=search> to also support folks using older browsers / screenreaders that only support #ARIA 1.1.
0.8: replaced my incorrect use of HTML attribute aria-hidden="true" (on my links to #BridgyFed) as pointed out by @jkphl.is (@jkphl@mastodon.social@jkphl) and https://sonja-weckenmann.de (@sweckenmann@mas.to), with hidden="from-humans". Since other values are allowed on the hidden attribute and treated as hidden="hidden", the "from-humans" value communicates a subtle semantic that the element is intended for consumption by robots & crawlers, like #Bridgy. 0.8.1 Update: created a pull-request (https://github.com/snarfed/bridgy-fed/pull/701) to update the BridgyFed documentation markup examples to use the 'hidden' attribute accordingly as well.
Time is up for today’s IndieWebCamp Create Day so my remaining projects will have to wait.
{
"type": "entry",
"published": "2023-10-29 08:18-0700",
"url": "https://tantek.com/2023/302/t1/indiewebcamp-completed-projects",
"category": [
"IndieWebCamp",
"Matrix",
"ARIA",
"BridgyFed",
"Bridgy"
],
"content": {
"text": "coding at #IndieWebCamp Nuremberg, completed the following projects:\n\n0.0: fixed the https://chat.indieweb.org/ footer to drop #Matrix as an access option since their bridge is disabled (#IndieWeb IRC, Discord, and Slack still work great), and provide an explicit link/encouragement for filing issues\n\n0.5: investigated IndieWeb wiki issues (mobile presentation), possible fixes, and documented them: https://indieweb.org/MediaWiki_customizations#Issues\n\n0.7: add HTML <search> element support to my home page and permalinks as nerdsniped by @adactio.com (@adactio@mastodon.social @adactio); expanded to <search role=search> to also support folks using older browsers / screenreaders that only support #ARIA 1.1.\n\n0.8: replaced my incorrect use of HTML attribute aria-hidden=\"true\" (on my links to #BridgyFed) as pointed out by @jkphl.is (@jkphl@mastodon.social @jkphl) and https://sonja-weckenmann.de (@sweckenmann@mas.to), with hidden=\"from-humans\". Since other values are allowed on the hidden attribute and treated as hidden=\"hidden\", the \"from-humans\" value communicates a subtle semantic that the element is intended for consumption by robots & crawlers, like #Bridgy.\n0.8.1 Update: created a pull-request (https://github.com/snarfed/bridgy-fed/pull/701) to update the BridgyFed documentation markup examples to use the 'hidden' attribute accordingly as well.\n\nTime is up for today\u2019s IndieWebCamp Create Day so my remaining projects will have to wait.",
"html": "coding at #<span class=\"p-category\">IndieWebCamp</span> Nuremberg, completed the following projects:<br /><br />0.0: fixed the <a href=\"https://chat.indieweb.org/\">https://chat.indieweb.org/</a> footer to drop #<span class=\"p-category\">Matrix</span> as an access option since their bridge is disabled (#IndieWeb IRC, Discord, and Slack still work great), and provide an explicit link/encouragement for filing issues<br /><br />0.5: investigated IndieWeb wiki issues (mobile presentation), possible fixes, and documented them: <a href=\"https://indieweb.org/MediaWiki_customizations#Issues\">https://indieweb.org/MediaWiki_customizations#Issues</a><br /><br />0.7: add HTML <search> element support to my home page and permalinks as nerdsniped by <a href=\"https://adactio.com\">@adactio.com</a> (<a href=\"https://mastodon.social/@adactio\">@adactio@mastodon.social</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/adactio\">@adactio</a>); expanded to <search role=search> to also support folks using older browsers / screenreaders that only support #<span class=\"p-category\">ARIA</span> 1.1.<br /><br />0.8: replaced my incorrect use of HTML attribute aria-hidden=\"true\" (on my links to #<span class=\"p-category\">BridgyFed</span>) as pointed out by <a href=\"https://jkphl.is\">@jkphl.is</a> (<a href=\"https://mastodon.social/@jkphl\">@jkphl@mastodon.social</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/jkphl\">@jkphl</a>) and <a href=\"https://sonja-weckenmann.de\">https://sonja-weckenmann.de</a> (<a href=\"https://mas.to/@sweckenmann\">@sweckenmann@mas.to</a>), with hidden=\"from-humans\". Since other values are allowed on the hidden attribute and treated as hidden=\"hidden\", the \"from-humans\" value communicates a subtle semantic that the element is intended for consumption by robots & crawlers, like #<span class=\"p-category\">Bridgy</span>.<br />0.8.1 Update: created a pull-request (<a href=\"https://github.com/snarfed/bridgy-fed/pull/701\">https://github.com/snarfed/bridgy-fed/pull/701</a>) to update the BridgyFed documentation markup examples to use the 'hidden' attribute accordingly as well.<br /><br />Time is up for today\u2019s IndieWebCamp Create Day so my remaining projects will have to wait."
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "39309586",
"_source": "2460"
}
Looking forward to the next two days at #IndieWebCamp Nürnberg @tollwerk.de (@tollwerk@mastodon.social@tollwerk) of personal site demos, brainstorming sessions, and making, creating, & hacking things from UX to protocols to improve & interconnect our websites, with each other ( #Webmention ), #fediverse ( #BridgyFed & #ActivityPub ), and others ( #POSSE #backfeed ).
Still a few spots if you’re in town or can hop on a train and join us Saturday & Sunday!
{
"type": "entry",
"published": "2023-10-27 16:23-0700",
"url": "https://tantek.com/2023/300/t1/border-none-indiewebcamp-nurnberg",
"category": [
"IndieWebCamp",
"Webmention",
"fediverse",
"BridgyFed",
"ActivityPub",
"POSSE",
"backfeed",
"bordernone",
"bono23",
"IndieWeb"
],
"content": {
"text": "Inspiring mix of perspective expanding and personal talks at border:none (https://border-none.net/ @border_none) the past two days. Thanks speakers, volunteers, and especially organizers @marcthiele.com (@marcthiele@mastodon.social @marcthiele) and @jkphl.is (@jkphl@mastodon.social @jkphl).\n\nLooking forward to the next two days at #IndieWebCamp N\u00fcrnberg @tollwerk.de (@tollwerk@mastodon.social @tollwerk) of personal site demos, brainstorming sessions, and making, creating, & hacking things from UX to protocols to improve & interconnect our websites, with each other ( #Webmention ), #fediverse ( #BridgyFed & #ActivityPub ), and others ( #POSSE #backfeed ).\n\nStill a few spots if you\u2019re in town or can hop on a train and join us Saturday & Sunday!\n\n\ud83c\udf9f Tickets: https://ti.to/beyondtellerrand/bordernone-2023/with/kqyaidtq92k\n\ud83d\uddd3 Event: https://events.indieweb.org/2023/10/indiewebcamp-nuremberg-2023-DmXe4dYdfagc\n\u2139\ufe0f More info: https://indieweb.org/2023/Nuremberg\n\n#bordernone #bono23 #IndieWeb",
"html": "Inspiring mix of perspective expanding and personal talks at border:none (<a href=\"https://border-none.net/\">https://border-none.net/</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/border_none\">@border_none</a>) the past two days. Thanks speakers, volunteers, and especially organizers <a href=\"https://marcthiele.com\">@marcthiele.com</a> (<a href=\"https://mastodon.social/@marcthiele\">@marcthiele@mastodon.social</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/marcthiele\">@marcthiele</a>) and <a href=\"https://jkphl.is\">@jkphl.is</a> (<a href=\"https://mastodon.social/@jkphl\">@jkphl@mastodon.social</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/jkphl\">@jkphl</a>).<br /><br />Looking forward to the next two days at #<span class=\"p-category\">IndieWebCamp</span> N\u00fcrnberg <a href=\"https://tollwerk.de\">@tollwerk.de</a> (<a href=\"https://mastodon.social/@tollwerk\">@tollwerk@mastodon.social</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/tollwerk\">@tollwerk</a>) of personal site demos, brainstorming sessions, and making, creating, & hacking things from UX to protocols to improve & interconnect our websites, with each other ( #<span class=\"p-category\">Webmention</span> ), #<span class=\"p-category\">fediverse</span> ( #<span class=\"p-category\">BridgyFed</span> & #<span class=\"p-category\">ActivityPub</span> ), and others ( #<span class=\"p-category\">POSSE</span> #<span class=\"p-category\">backfeed</span> ).<br /><br />Still a few spots if you\u2019re in town or can hop on a train and join us Saturday & Sunday!<br /><br />\ud83c\udf9f Tickets: <a href=\"https://ti.to/beyondtellerrand/bordernone-2023/with/kqyaidtq92k\">https://ti.to/beyondtellerrand/bordernone-2023/with/kqyaidtq92k</a><br />\ud83d\uddd3 Event: <a href=\"https://events.indieweb.org/2023/10/indiewebcamp-nuremberg-2023-DmXe4dYdfagc\">https://events.indieweb.org/2023/10/indiewebcamp-nuremberg-2023-DmXe4dYdfagc</a><br />\u2139\ufe0f More info: <a href=\"https://indieweb.org/2023/Nuremberg\">https://indieweb.org/2023/Nuremberg</a><br /><br />#<span class=\"p-category\">bordernone</span> #<span class=\"p-category\">bono23</span> #<span class=\"p-category\">IndieWeb</span>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "39296435",
"_source": "2460"
}
{
"type": "entry",
"author": {
"name": null,
"url": "https://herestomwiththeweather.com/",
"photo": null
},
"url": "https://herestomwiththeweather.com/2023/10/26/orwellian-language/",
"published": "2023-10-26T13:50:12+00:00",
"content": {
"html": "<p>The \u201cright to self-defense\u201d is a bizarre one. The exclusive application of such a right infers that others do not have that right. It seems that we should be questioning language like this if there is to be any hope for peace.</p>",
"text": "The \u201cright to self-defense\u201d is a bizarre one. The exclusive application of such a right infers that others do not have that right. It seems that we should be questioning language like this if there is to be any hope for peace."
},
"name": "Orwellian Language",
"post-type": "article",
"_id": "39284398",
"_source": "246"
}
{
"type": "entry",
"published": "2023-10-26T08:50:07-07:00",
"url": "https://aaronparecki.com/2023/10/26/3/oauth",
"category": [
"oauth"
],
"content": {
"text": "This is a good writeup on some sneaky vulnerabilities in OAuth implementations, but ultimately is just a simple access token injection attack: https://salt.security/blog/oh-auth-abusing-oauth-to-take-over-millions-of-accounts",
"html": "This is a good writeup on some sneaky vulnerabilities in OAuth implementations, but ultimately is just a simple access token injection attack: <a href=\"https://salt.security/blog/oh-auth-abusing-oauth-to-take-over-millions-of-accounts\"><span>https://</span>salt.security/blog/oh-auth-abusing-oauth-to-take-over-millions-of-accounts</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": "39281634",
"_source": "16"
}
{
"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"
}
:format(webp)/cdn.vox-cdn.com/uploads/chorus_asset/file/25024444/CleanShot_2023_10_23_at_09.36.40_2x.png)
