Catching up on the Distributed Web Summit. Great lightning talk from @t introducing the IndieWeb. Here’s a link directly to the start of his talk in the YouTube stream.
{
"type": "entry",
"author": {
"name": null,
"url": "https://www.manton.org/",
"photo": null
},
"url": "https://www.manton.org/2018/08/03/165743.html",
"content": {
"html": "<p>Catching up on the Distributed Web Summit. Great lightning talk from <a href=\"https://micro.blog/t\">@t</a> introducing the IndieWeb. <a href=\"https://www.youtube.com/watch?v=u-XtbUEiL38&t=1h20m37s\">Here\u2019s a link</a> directly to the start of his talk in the YouTube stream.</p>",
"text": "Catching up on the Distributed Web Summit. Great lightning talk from @t introducing the IndieWeb. Here\u2019s a link directly to the start of his talk in the YouTube stream."
},
"published": "2018-08-03T11:57:43-05:00",
"post-type": "note",
"_id": "725543",
"_source": "12",
"_is_read": true
}
{
"type": "entry",
"published": "2018-08-03T07:51:10-07:00",
"url": "https://snarfed.org/2018-08-03_rip-facebook-for-bridgy",
"syndication": [
"https://news.indieweb.org/en/snarfed.org/2018-08-03_rip-facebook-for-bridgy"
],
"name": "RIP Facebook for Bridgy",
"content": {
"text": "As planned, Facebook turned off some of its key APIs for posting and fetching data on Wednesday, and I disabled Facebook for Bridgy entirely.\nIt\u2019s a sad day. Facebook was the single biggest reason I came up with Bridgy way back in 2011. I\u2019ve always wanted to own my data online, on my own web site, but my friends and family generally used social networks like Facebook instead. I didn\u2019t care too much about dogma or evangelizing, but I still wanted to connect with them wherever they were, and if they were online, more often than not they were on Facebook.\nSocial networks are under siege in the press right now, so it\u2019s easy to forget all the ways they\u2019ve made our lives better. Not only have they brought us indispensable tools for day to day life, they\u2019ve also enriched our ties to many real people, not just those we care about most but also entirely new people, across the globe, who we may never have met otherwise.\nWe regularly look to big social networks for inspiration and motivation in the IndieWeb. We analyze and document features, UI designs, and yes, even antipatterns\u2026but more importantly, we work hard to interoperate. We may try to live on our web sites, but we still treasure and value the relationships we have with everyone else. They\u2019re still on the social networks, Facebook above all.\nI\u2019ll still use Facebook directly now and then. Friends will get engaged, colleagues will start new jobs, cousins will have babies. I\u2019ll still expect to see someone at a party whose name I\u2019ve forgotten \u2013 you know, we met her at that place, for that thing \u2013 and look it up on Facebook first. Embarrassment avoided, life improved. But I\u2019ll use it less. I wish there was another way.\nSo long for now. See you on the web!",
"html": "<p>\n <a href=\"https://brid.gy/\">\n <img src=\"https://aperture-proxy.p3k.io/ba5fa097747514d3123a876799eae62921760991/68747470733a2f2f736e61726665642e6f72672f772f77702d636f6e74656e742f706c7567696e732f6a65747061636b2f6d6f64756c65732f6c617a792d696d616765732f696d616765732f3178312e7472616e732e676966\" alt=\"1x1.trans.gif\" /></a></p><img src=\"https://aperture-proxy.p3k.io/58b00808619d02e2b00da815e8c6e79858a816cc/68747470733a2f2f736e61726665642e6f72672f6272696467795f6c6f676f2e6a7067\" alt=\"bridgy_logo.jpg\" />\n<p>As planned, <a href=\"https://developers.facebook.com/blog/post/2018/05/01/facebook-login-updates-further-protect-privacy/\">Facebook turned off some of its key APIs for posting and fetching data</a> on Wednesday, and I <a href=\"https://snarfed.org/2018-06-07_turning-off-facebook-for-bridgy\">disabled Facebook for Bridgy entirely</a>.</p>\n<p>It\u2019s a sad day. Facebook was the single biggest reason I came up with Bridgy <a href=\"https://brid.gy/about#history\">way back in 2011</a>. I\u2019ve always wanted to own my data online, <a href=\"https://snarfed.org/2012-07-25_why_i_have_my_own_web_site\">on my own web site</a>, but my friends and family generally used social networks like Facebook instead. I didn\u2019t care too much about dogma or evangelizing, but I still wanted to connect with them wherever they were, and if they were online, more often than not they were on Facebook.</p>\n<p>Social networks are under siege in the press right now, so it\u2019s easy to forget all the ways they\u2019ve made our lives better. Not only have they brought us indispensable tools for day to day life, they\u2019ve also enriched our ties to many real people, not just those we care about most but also entirely new people, across the globe, who we may never have met otherwise.</p>\n<p>We regularly look to big social networks for inspiration and motivation in the <a href=\"https://indieweb.org/\">IndieWeb</a>. We analyze and document features, UI designs, and yes, even <a href=\"https://indieweb.org/antipatterns\">antipatterns</a>\u2026but more importantly, we work hard to <em>interoperate</em>. We may try to live on our web sites, but we still treasure and value the relationships we have with everyone else. They\u2019re still on the social networks, Facebook above all.</p>\n<p>I\u2019ll still use Facebook directly now and then. Friends will get engaged, colleagues will start new jobs, cousins will have babies. I\u2019ll still expect to see someone at a party whose name I\u2019ve forgotten \u2013 you know, we met her at that place, for that thing \u2013 and look it up on Facebook first. Embarrassment avoided, life improved. But I\u2019ll use it less. I wish there was another way.</p>\n<p>So long for now. <a href=\"https://indieweb.org/\">See you on the web!</a></p>"
},
"author": {
"type": "card",
"name": "Ryan Barrett",
"url": "https://snarfed.org/",
"photo": "https://aperture-proxy.p3k.io/7e644a0ecb0339b875f998fc405c685591d80cd7/68747470733a2f2f7365637572652e67726176617461722e636f6d2f6176617461722f39343762356633663332336461306566373835623666303264396332363564363f733d393626643d626c616e6b26723d67"
},
"post-type": "article",
"_id": "725139",
"_source": "3",
"_is_read": true
}
{
"type": "entry",
"published": "2018-08-02T18:11:53-04:00",
"summary": "The server he talks about is now available with limited history, and all of the current Microsub clients are free. But you do need a website to login because IndieAuth uses a URL: https://indigenous.abode.pub/ios/help/#indieauth",
"url": "https://eddiehinkle.com/2018/08/02/26/reply/",
"category": [
"indieauth",
"indieweb",
"microsub"
],
"in-reply-to": [
"https://twitter.com/jan_koeppen/status/1025079478500909056?s=12"
],
"content": {
"text": "The server he talks about is now available with limited history, and all of the current Microsub clients are free. But you do need a website to login because IndieAuth uses a URL: https://indigenous.abode.pub/ios/help/#indieauth",
"html": "<p>The server he talks about <a href=\"https://aperture.eddiehinkle.com/pricing\">is now available with limited history</a>, and all of the current Microsub clients are free. But you do need a website to login because IndieAuth uses a URL: <a href=\"https://indigenous.abode.pub/ios/help/#indieauth\">https://indigenous.abode.pub/ios/help/#indieauth</a></p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"post-type": "reply",
"refs": {
"https://twitter.com/jan_koeppen/status/1025079478500909056?s=12": {
"type": "entry",
"url": "https://twitter.com/jan_koeppen/status/1025079478500909056?s=12",
"name": "https://twitter.com/jan_koeppen/status/1025079478500909056?s=12",
"post-type": "article"
}
},
"_id": "721628",
"_source": "226",
"_is_read": true
}
Welp! As of today, none of my posts, links, or notes can be syndicated to Facebook:
The publish_actions permission will be deprecated. This permission granted apps access to publish posts to Facebook as the logged in user. Apps created from today onwards will not have access to this permission. Apps created before today that have been previously approved to request publish_actions can continue to do so until August 1, 2018.
If you’re reading this on Facebook: so long, it’s been good to know ya.
{
"type": "entry",
"published": "2018-08-02T16:26:47Z",
"url": "https://adactio.com/links/14228",
"category": [
"facebook",
"api",
"posse",
"publishing",
"indieweb",
"syndication"
],
"bookmark-of": [
"https://developers.facebook.com/blog/post/2018/04/24/new-facebook-platform-product-changes-policy-updates/"
],
"content": {
"text": "New Facebook Platform Product Changes and Policy Updates - Facebook for Developers\n\n\n\nWelp! As of today, none of my posts, links, or notes can be syndicated to Facebook:\n\n\n The publish_actions permission will be deprecated. This permission granted apps access to publish posts to Facebook as the logged in user. Apps created from today onwards will not have access to this permission. Apps created before today that have been previously approved to request publish_actions can continue to do so until August 1, 2018.\n\n\nIf you\u2019re reading this on Facebook: so long, it\u2019s been good to know ya.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://developers.facebook.com/blog/post/2018/04/24/new-facebook-platform-product-changes-policy-updates/\">\nNew Facebook Platform Product Changes and Policy Updates - Facebook for Developers\n</a>\n</h3>\n\n<p>Welp! As of today, none of my posts, links, or notes can be syndicated to Facebook:</p>\n\n<blockquote>\n <p>The <code>publish_actions</code> permission will be deprecated. This permission granted apps access to publish posts to Facebook as the logged in user. Apps created from today onwards will not have access to this permission. Apps created before today that have been previously approved to request <code>publish_actions</code> can continue to do so until August 1, 2018.</p>\n</blockquote>\n\n<p>If you\u2019re reading this on Facebook: so long, it\u2019s been good to know ya.</p>"
},
"post-type": "bookmark",
"_id": "719707",
"_source": "2",
"_is_read": true
}
Updated my inline micropub client a little. So now it includes a more subtle button in your browser rather than a floating button to create and edit posts.
{
"type": "entry",
"published": "2018-08-02T14:39:51.339Z",
"url": "https://grant.codes/2018/08/02/5b6317b7b83b374d52782679",
"syndication": [
"https://twitter.com/grantcodes/status/1025028410693824513"
],
"content": {
"text": "Updated my inline micropub client a little. So now it includes a more subtle button in your browser rather than a floating button to create and edit posts.",
"html": "<p>Updated my inline micropub client a little. So now it includes a more subtle button in your browser rather than a floating button to create and edit posts.<br /></p>"
},
"author": {
"type": "card",
"name": "Grant Richmond",
"url": "https://grant.codes",
"photo": "https://aperture-proxy.p3k.io/be31049af9884a65289b2d14300adafc0e4030c6/68747470733a2f2f6772616e742e636f6465732f696d672f6d652e6a7067"
},
"post-type": "note",
"_id": "718587",
"_source": "11",
"_is_read": true
}
{
"type": "entry",
"published": "2018-07-31T21:35:08-04:00",
"url": "https://david.shanske.com/2018/07/31/your-endpoint-did-not-return-a-location-header/",
"name": "Your Endpoint Did Not Return a Location Header",
"content": {
"text": "There have been some issues with Quill and other services advising that the WordPress Micropub endpoint did not return a Location header. There seems to be some confusion about this, which is partly because the message is a bit technical. One individual thought that this was related to Simple Location.\nThis indicates an error on the part of the Micropub plugin. Regrettably, in addition to not displaying the error response prominently, the Micropub specification dictates that the error response returns one of 4 error codes, and may return a human readable error description to assist the client developer in understanding the error, but is not meant to be shown to the end user.\nThis does not account for errors on the endpoint side that may need to be debugged. Currently, the WordPress plugin that creates the endpoint does not surface error messages on its side either to allow you to figure this out.\nBetter error messaging to the end-user on one side or the other seems to be a common issue amongst Indieweb tools to help them figure out the issue.\nThe most common issue that explains the failure is an inability to associate the URL with the user account. There are two versions of the software that does this.\nIn the IndieAuth plugin, to ensure accuracy, the plugin passes the WordPress user ID in the return to ensure that it can find it.\nIf you don\u2019t have the IndieAuth plugin installed, the Micropub plugin uses an external IndieAuth endpoint instead of a built-in one, and the following techniques to find the WordPress user from your URL\nIf you have the Indieweb plugin installed, it looks in its settings for the default author on a single author site.\nIf you are using the URL of your author post archive, usually /author/username it will try to use that to get your username and therefore your user ID\nIf you have set a website URL in your profile, it will try to use that. Please make sure your website URL uses https if your website does, as this has caused some issues in matching.\n\nIn both plugins, we continue to improve the functionality in this case and I often port ideas that improved functionality in one version into the other, as they are both authorize Micropub using IndieAuth, but in the case of the Indieauth plugin, it also implements the IndieAuth functionality.\nRight now, I\u2019m working on improvements to the Micropub plugin to improve the error handling, among other things, and hopefully this will help.\n\u00a0",
"html": "There have been some issues with <a href=\"https://quill.p3k.io\">Quill</a> and other services advising that the WordPress Micropub endpoint did not return a Location header. There seems to be some confusion about this, which is partly because the message is a bit technical. One individual thought that this was related to Simple Location.\n<p>This indicates an error on the part of the Micropub plugin. Regrettably, in addition to not displaying the error response prominently, the Micropub specification dictates that the error response returns one of 4 error codes, and may return a human readable error description to assist the client developer in understanding the error, but is not meant to be shown to the end user.</p>\n<p>This does not account for errors on the endpoint side that may need to be debugged. Currently, the WordPress plugin that creates the endpoint does not surface error messages on its side either to allow you to figure this out.</p>\n<p>Better error messaging to the end-user on one side or the other seems to be a common issue amongst Indieweb tools to help them figure out the issue.</p>\n<p>The most common issue that explains the failure is an inability to associate the URL with the user account. There are two versions of the software that does this.</p>\n<ul><li>In the IndieAuth plugin, to ensure accuracy, the plugin passes the WordPress user ID in the return to ensure that it can find it.</li>\n<li>If you don\u2019t have the IndieAuth plugin installed, the Micropub plugin uses an external IndieAuth endpoint instead of a built-in one, and the following techniques to find the WordPress user from your URL\n<ul><li>If you have the Indieweb plugin installed, it looks in its settings for the default author on a single author site.</li>\n<li>If you are using the URL of your author post archive, usually /author/username it will try to use that to get your username and therefore your user ID</li>\n<li>If you have set a website URL in your profile, it will try to use that. Please make sure your website URL uses https if your website does, as this has caused some issues in matching.</li>\n</ul></li>\n</ul><p>In both plugins, we continue to improve the functionality in this case and I often port ideas that improved functionality in one version into the other, as they are both authorize Micropub using IndieAuth, but in the case of the Indieauth plugin, it also implements the IndieAuth functionality.</p>\n<p>Right now, I\u2019m working on improvements to the Micropub plugin to improve the error handling, among other things, and hopefully this will help.</p>\n<p>\u00a0</p>"
},
"author": {
"type": "card",
"name": "David Shanske",
"url": "https://david.shanske.com/",
"photo": "https://david.shanske.com/wp-content/uploads/avatar-privacy/cache/gravatar/2/c/2cb1f8afd9c8d3b646b4071c5ed887c970d81d625eeed87e447706940e2c403d-125.png"
},
"post-type": "article",
"_id": "714529",
"_source": "5",
"_is_read": true
}
I have to agree with Ben. The Micropub plugin for WordPress triggers a WordPress hook based on syndication targets and I’m working on a compatible system for the Post Editor, so that the UI doesn’t need to know how the item is POSSEd.
This is because I also don’t want to deal with silo interfaces most of the time.
{
"type": "entry",
"published": "2018-07-31T20:43:30-04:00",
"url": "https://david.shanske.com/2018/07/31/2025/",
"in-reply-to": [
"https://werd.io/2018/stepping-back-from-posse"
],
"content": {
"text": "I have to agree with Ben. The Micropub plugin for WordPress triggers a WordPress hook based on syndication targets and I\u2019m working on a compatible system for the Post Editor, so that the UI doesn\u2019t need to know how the item is POSSEd.\nThis is because I also don\u2019t want to deal with silo interfaces most of the time.",
"html": "I have to agree with Ben. The Micropub plugin for WordPress triggers a WordPress hook based on syndication targets and I\u2019m working on a compatible system for the Post Editor, so that the UI doesn\u2019t need to know how the item is POSSEd.\n<p>This is because I also don\u2019t want to deal with silo interfaces most of the time.</p>"
},
"author": {
"type": "card",
"name": "David Shanske",
"url": "https://david.shanske.com/",
"photo": "https://david.shanske.com/wp-content/uploads/avatar-privacy/cache/gravatar/2/c/2cb1f8afd9c8d3b646b4071c5ed887c970d81d625eeed87e447706940e2c403d-125.png"
},
"post-type": "reply",
"refs": {
"https://werd.io/2018/stepping-back-from-posse": {
"type": "entry",
"url": "https://werd.io/2018/stepping-back-from-posse",
"name": "Stepping back from POSSE",
"author": {
"type": "card",
"name": "Ben Werdm\u00fcller",
"url": "https://werd.io/profile/benwerd",
"photo": "https://werd.io/file/56c4b818bed7de5b507fa2a5/thumb.jpg"
},
"post-type": "article"
}
},
"_id": "714530",
"_source": "5",
"_is_read": true
}
I’ve been really enjoying the focus on personal websites that Vi Hart and M Eifler aka blinkpopshift have been putting into their recent Patrons-only VIM LIVE streams.
In addition to some great discussion about subscribing to RSS feeds of personal sites, I have really enjoyed the homework-slash-games like “post something on your website” and “collect what you might have tweeted into a blog”.
I think there’s a lot that the IndieWeb can learn from discussions like these as folks from different backgrounds are (re-)discovering what the web can be.
You can find previous and future VIM LIVE streams by supporting blinkpopshift or Vi Hart on Patreon.
{
"type": "entry",
"published": "2018-08-01T11:45:12-04:00",
"url": "https://martymcgui.re/2018/08/01/114512/",
"category": [
"IndieWeb",
"vihart",
"blinkpopshift",
"vimlive"
],
"syndication": [
"https://twitter.com/schmarty/status/1024684340486320131",
"https://www.facebook.com/marty.mcguire.54/posts/10212556824617564"
],
"content": {
"text": "I\u2019ve been really enjoying the focus on personal websites that Vi Hart and M Eifler aka blinkpopshift have been putting into their recent Patrons-only VIM LIVE streams.\nIn addition to some great discussion about subscribing to RSS feeds of personal sites, I have really enjoyed the homework-slash-games like \u201cpost something on your website\u201d and \u201ccollect what you might have tweeted into a blog\u201d.\nI think there\u2019s a lot that the IndieWeb can learn from discussions like these as folks from different backgrounds are (re-)discovering what the web can be.\nYou can find previous and future VIM LIVE streams by supporting blinkpopshift or Vi Hart on Patreon.",
"html": "<p>I\u2019ve been really enjoying the focus on personal websites that <a href=\"http://vihart.com/\">Vi Hart</a> and <a href=\"http://www.blinkpopshift.com/\">M Eifler aka blinkpopshift</a> have been putting into their recent Patrons-only VIM LIVE streams.</p>\n<p>In addition to some great discussion about subscribing to RSS feeds of personal sites, I have really enjoyed the homework-slash-games like \u201cpost something on your website\u201d and \u201c<a href=\"http://vihart.com/my-not-tweets-7-21-2018/\">collect what you might have tweeted into a blog</a>\u201d.</p>\n<p>I think there\u2019s a lot that the <a href=\"https://indieweb.org/\">IndieWeb</a> can learn from discussions like these as folks from different backgrounds are (re-)discovering what the web can be.</p>\n<p>You can find previous and future VIM LIVE streams by supporting <a href=\"https://www.patreon.com/BlinkPopShift/posts\">blinkpopshift</a> or <a href=\"https://martymcgui.re/posts/patreon.com/vihart\">Vi Hart</a> on Patreon.</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://aperture-proxy.p3k.io/8275f85e3a389bd0ae69f209683436fc53d8bad9/68747470733a2f2f6d617274796d636775692e72652f696d616765732f6c6f676f2e6a7067"
},
"post-type": "note",
"_id": "714318",
"_source": "175",
"_is_read": true
}
{
"type": "entry",
"published": "2018-07-31T18:12:35+00:00",
"url": "http://stream.boffosocko.com/2018/outlandishjosh-i-could-easily-see-getpantheon-building-indieweb-stacks-with",
"syndication": [
"https://twitter.com/ChrisAldrich/status/1024357195004235782"
],
"in-reply-to": [
"https://twitter.com/outlandishjosh/status/1024354797883781120"
],
"content": {
"text": "@outlandishjosh I could easily see @getpantheon building IndieWeb stacks with @WordPress +Plugins or @Drupal or @backdropcms + https://www.drupal.org/project/indieweb to expand this type of decentralized web interaction in a way similar to @microdotblog",
"html": "<a href=\"https://twitter.com/outlandishjosh\">@outlandishjosh</a> I could easily see <a href=\"https://twitter.com/getpantheon\">@getpantheon</a> building IndieWeb stacks with <a href=\"https://twitter.com/WordPress\">@WordPress</a> +Plugins or <a href=\"https://twitter.com/Drupal\">@Drupal</a> or <a href=\"https://twitter.com/backdropcms\">@backdropcms</a> + <a href=\"https://www.drupal.org/project/indieweb\">https://www.drupal.org/project/indieweb</a> to expand this type of decentralized web interaction in a way similar to <a href=\"https://twitter.com/microdotblog\">@microdotblog</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "https://aperture-proxy.p3k.io/4a01a54aa55b69dd1b2633c835610491c575e2e2/687474703a2f2f73747265616d2e626f66666f736f636b6f2e636f6d2f66696c652f36303034323762383166373738356537303465616466653531316139323730662f7468756d622e6a7067"
},
"post-type": "reply",
"_id": "710137",
"_source": "192",
"_is_read": true
}
Homebrew Website Club tomorrow! 6:30pm at Mozart’s Coffee. We’ll keep it informal as we get back into holding this meetup. Time to review recent IndieWeb events, Micro.blog progress, or talk about updates to our sites.
{
"type": "entry",
"author": {
"name": null,
"url": "https://www.manton.org/",
"photo": null
},
"url": "https://www.manton.org/2018/07/31/184117.html",
"content": {
"html": "<p><a href=\"https://indieweb.org/Homebrew_Website_Club\">Homebrew Website Club</a> tomorrow! 6:30pm at Mozart\u2019s Coffee. We\u2019ll keep it informal as we get back into holding this meetup. Time to review recent IndieWeb events, Micro.blog progress, or talk about updates to our sites.</p>",
"text": "Homebrew Website Club tomorrow! 6:30pm at Mozart\u2019s Coffee. We\u2019ll keep it informal as we get back into holding this meetup. Time to review recent IndieWeb events, Micro.blog progress, or talk about updates to our sites."
},
"published": "2018-07-31T13:41:17-05:00",
"post-type": "note",
"_id": "710003",
"_source": "12",
"_is_read": true
}
{
"type": "entry",
"published": "2018-07-31T14:32:38+00:00",
"url": "https://werd.io/2018/stepping-back-from-posse",
"name": "Stepping back from POSSE",
"content": {
"text": "Just a quick note: ostensibly to fight algorithmic propaganda, Facebook is shutting off API access to publish to profiles tomorrow. I expect other platforms to follow. That's completely their right.The indieweb has this intrinsic idea of Publishing on your Own Site, Syndicating Elsewhere: automatically sending your content to other social networks. When we pitched this as part of Known, we rightly got a lot of feedback about outsized supplier power from the social networks. They could withdraw their APIs - and if the value in the platform was in this ability to syndicate, instantly erode value in the platform. It doesn't take an industry analyst to see that this criticism was right on the money.I still see a lot of value in having your own website. I've been blogging since 1998, but switched to Movable Type in 2001, a new WordPress site in 2006, and then Idno / Known in 2013. I'm a little bit jealous of people who have had a consistent web presence for decades, but even this timeline has outlasted most social networks.But I see less value in syndicating directly. I had already stopped syndicating tweets and status updates. From here on out, I'm going to stop automatically syndicating anything, and will revert to manually posting. I'm also going to make a strong argument\u00a0in the open source Known community that syndication should be limited to webhooks going forward. In other words, third parties will be able to create microservices with a standard API, which your Known or other indieweb-compatible site will be able to connect to. You could click a button to notify those services (or have your site do it automatically).But any kind of API maintenance would be taken out of the core code or official plugins. Not only is life too short, but it's long past time to stop building code on top of centralized silos of content.",
"html": "<p><a title=\"IndieWeb\" href=\"https://indieweb.org\"><img style=\"float:right;\" src=\"https://aperture-proxy.p3k.io/f7bf3c2e20388ccc311ecf18ab0a9f390f3fe33c/68747470733a2f2f776572642e696f2f66696c652f3562363037316361643363396232333665643539656233322f7468756d622e706e67\" alt=\"\" width=\"403\" height=\"192\" /></a>Just a quick note: ostensibly to fight algorithmic propaganda, Facebook is shutting off API access to publish to profiles tomorrow. I expect other platforms to follow. That's completely their right.</p><p>The indieweb has this intrinsic idea of <a href=\"https://indieweb.org/POSSE\">Publishing on your Own Site, Syndicating Elsewhere</a>: automatically sending your content to other social networks. When we pitched this as part of Known, we rightly got a lot of feedback about outsized supplier power from the social networks. They could withdraw their APIs - and if the value in the platform was in this ability to syndicate, instantly erode value in the platform. It doesn't take an industry analyst to see that this criticism was right on the money.</p><p>I still see a lot of value in having your own website. I've been blogging since 1998, but switched to Movable Type in 2001, a new WordPress site in 2006, and then Idno / Known in 2013. I'm a little bit jealous of people who have had a consistent web presence for decades, but even this timeline has outlasted most social networks.</p><p>But I see less value in syndicating directly. I had already stopped syndicating tweets and status updates. From here on out, I'm going to stop automatically syndicating anything, and will revert to manually posting. I'm also going to make a strong argument\u00a0<a href=\"https://github.com/idno/known\">in the open source Known community</a> that syndication should be limited to webhooks going forward. In other words, third parties will be able to create microservices with a standard API, which your Known or other indieweb-compatible site will be able to connect to. You could click a button to notify those services (or have your site do it automatically).</p><p>But any kind of API maintenance would be taken out of the core code or official plugins. Not only is life too short, but it's long past time to stop building code on top of centralized silos of content.</p>"
},
"author": {
"type": "card",
"name": "Ben Werdm\u00fcller",
"url": "https://werd.io/profile/benwerd",
"photo": "https://aperture-proxy.p3k.io/78fd5896b799926517b28cef89e270537a205537/68747470733a2f2f776572642e696f2f66696c652f3536633462383138626564376465356235303766613261352f7468756d622e6a7067"
},
"post-type": "article",
"_id": "709277",
"_source": "191",
"_is_read": true
}
{
"type": "entry",
"published": "2018-07-31 08:21-0700",
"url": "http://tantek.com/2018/212/t1/indiewebcamp-sf-dweb-hackers-day",
"category": [
"IndieWebCamp"
],
"content": {
"text": "#IndieWebCamp SF / DWeb Hackers day is TODAY @MozSF!\n\nhttps://indieweb.org/2018/SF\n\nIf you\u2019ve RSVP\u2019d already great! We\u2019re expecting you at 10am.\n\nIf you\u2019re just hearing about this, reply or drop by https://chat.indieweb.org/ and say hello!",
"html": "#IndieWebCamp SF / DWeb Hackers day is TODAY <a class=\"h-cassis-username\" href=\"https://twitter.com/MozSF\">@MozSF</a>!<br /><br /><a href=\"https://indieweb.org/2018/SF\">https://indieweb.org/2018/SF</a><br /><br />If you\u2019ve RSVP\u2019d already great! We\u2019re expecting you at 10am.<br /><br />If you\u2019re just hearing about this, reply or drop by <a href=\"https://chat.indieweb.org/\">https://chat.indieweb.org/</a> and say hello!"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "http://tantek.com/",
"photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "note",
"_id": "708769",
"_source": "1",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": null,
"url": "https://www.manton.org/",
"photo": null
},
"url": "https://www.manton.org/2018/07/31/151054.html",
"name": "On this day",
"content": {
"html": "<p>Last week I added a new archive page to Micro.blog-hosted sites. It includes dates and the first part of each post, marked up with Microformats. <a href=\"https://cleverdevil.io/\">Jonathan LaCour</a> used this to write a script that parses the HTML looking for posts on today\u2019s date in previous years, then pulls the full content for each post it finds and assembles them together.</p>\n\n<p>But it gets better. After Jonathan mentioned that it took quite a while to parse the large HTML file, I added a JSON Feed version of the archive page. If you\u2019ve posted to Micro.blog since yesterday, this has been created for you at <code>your-domain.com/archive/index.json</code>. Jonathan updated the script to use the JSON Feed and it can now return the \u201con this day\u201d posts very quickly, with no configuration needed because it\u2019s all driven from a JavaScript include on your blog.</p>\n\n<p>You can see this in action on my own blog\u2019s <a href=\"http://manton.org/on-this-day/\">on this day page</a>. It works for any Micro.blog-hosted blog by pasting in a few lines of HTML from the <a href=\"https://github.com/cleverdevil/micromemories\">Micro Memories project on GitHub</a>.</p>\n\n<p>This is the potential for indie blogging and simple formats. Adding a feature to Micro.blog-hosted blogs enabled a new tool I hadn\u2019t even thought of. There was some discussion in the IndieWeb chat, but it took very little coordination because all of this is built with web stuff, not proprietary APIs.</p>",
"text": "Last week I added a new archive page to Micro.blog-hosted sites. It includes dates and the first part of each post, marked up with Microformats. Jonathan LaCour used this to write a script that parses the HTML looking for posts on today\u2019s date in previous years, then pulls the full content for each post it finds and assembles them together.\n\nBut it gets better. After Jonathan mentioned that it took quite a while to parse the large HTML file, I added a JSON Feed version of the archive page. If you\u2019ve posted to Micro.blog since yesterday, this has been created for you at your-domain.com/archive/index.json. Jonathan updated the script to use the JSON Feed and it can now return the \u201con this day\u201d posts very quickly, with no configuration needed because it\u2019s all driven from a JavaScript include on your blog.\n\nYou can see this in action on my own blog\u2019s on this day page. It works for any Micro.blog-hosted blog by pasting in a few lines of HTML from the Micro Memories project on GitHub.\n\nThis is the potential for indie blogging and simple formats. Adding a feature to Micro.blog-hosted blogs enabled a new tool I hadn\u2019t even thought of. There was some discussion in the IndieWeb chat, but it took very little coordination because all of this is built with web stuff, not proprietary APIs."
},
"published": "2018-07-31T10:10:54-05:00",
"post-type": "article",
"_id": "708750",
"_source": "12",
"_is_read": true
}
{
"type": "entry",
"published": "2018-07-30 18:08-0700",
"url": "http://tantek.com/2018/211/t1/",
"in-reply-to": [
"https://github.com/microformats/microformats2-parsing/issues/36#issuecomment-407348526"
],
"content": {
"text": "https://github.com/sknebel yes that is the interpretation I intended, and thanks for the review and suggestion. I have added \"explicit\" explicitly :)\n\nhttp://microformats.org/wiki/index.php?title=microformats2-parsing&diff=66898&oldid=66890\n\nIf with that change we have sufficiently resolved this issue 36, go ahead and close it. Thanks!",
"html": "<a href=\"https://github.com/sknebel\">https://github.com/sknebel</a> yes that is the interpretation I intended, and thanks for the review and suggestion. I have added \"explicit\" explicitly :)<br /><br /><a href=\"http://microformats.org/wiki/index.php?title=microformats2-parsing&diff=66898&oldid=66890\">http://microformats.org/wiki/index.php?title=microformats2-parsing&diff=66898&oldid=66890</a><br /><br />If with that change we have sufficiently resolved this issue 36, go ahead and close it. Thanks!"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "http://tantek.com/",
"photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "reply",
"refs": {
"https://github.com/microformats/microformats2-parsing/issues/36#issuecomment-407348526": {
"type": "entry",
"url": "https://github.com/microformats/microformats2-parsing/issues/36#issuecomment-407348526",
"name": "a comment on issue 36 of GitHub project \u201cmicroformats2-parsing\u201d",
"post-type": "article"
}
},
"_id": "707205",
"_source": "1",
"_is_read": true
}
XRay, the library that I use to parse URLs to show comments, now supports parsing direct Microformats JSON, ActivityStreams 2.0, as well as finding a rel=alternate link and parsing data from that instead!
This means I now get great results when parsing Mastodon or other ActivityPub links, and this is also the first step in what I hope will result in fixing the Microformats situation for WordPress, since a WordPress plugin will be able to generate Microformats JSON and advertise that in a rel=alternate link.
Next up is updating Aperture to take advantage of these new features!
{
"type": "entry",
"published": "2018-07-30T19:32:33-07:00",
"url": "https://aaronparecki.com/2018/07/30/18/xray-updates",
"category": [
"activitypub",
"xray",
"microformats",
"p3k",
"indieweb"
],
"content": {
"text": "XRay, the library that I use to parse URLs to show comments, now supports parsing direct Microformats JSON, ActivityStreams 2.0, as well as finding a rel=alternate link and parsing data from that instead!\n\nThis means I now get great results when parsing Mastodon or other ActivityPub links, and this is also the first step in what I hope will result in fixing the Microformats situation for WordPress, since a WordPress plugin will be able to generate Microformats JSON and advertise that in a rel=alternate link.\n\nNext up is updating Aperture to take advantage of these new features!",
"html": "<p><a href=\"https://github.com/aaronpk/XRay\">XRay</a>, the library that I use to parse URLs to show comments, now supports parsing direct Microformats JSON, ActivityStreams 2.0, as well as finding a <code>rel=alternate</code> link and parsing data from that instead!</p>\n\n<p>This means I now get great results when parsing Mastodon or other ActivityPub links, and this is also the first step in what I hope will result in fixing the Microformats situation for WordPress, since a WordPress plugin will be able to generate Microformats JSON and advertise that in a <code>rel=alternate</code> link.</p>\n\n<p>Next up is updating <a href=\"https://indieweb.org/Aperture\">Aperture</a> to take advantage of these new features!</p>"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/2b8e1668dcd9cfa6a170b3724df740695f73a15c2a825962fd0a0967ec11ecdc.jpg"
},
"post-type": "note",
"_id": "707047",
"_source": "16",
"_is_read": true
}
Uh oh. Just realized that when I made a change to my automatic webmention sending code just before going to the hospital broke sending webmentions to everything other than Bridgy. Now I’m gonna have to go back, find and resend the webmentions that weren’t sent previously.
{
"type": "entry",
"published": "2018-07-30T18:03:14-04:00",
"summary": "Uh oh. Just realized that when I made a change to my automatic webmention sending code just before going to the hospital broke sending webmentions to everything other than Bridgy. Now I\u2019m gonna have to go back, find and resend the webmentions that weren\u2019t sent previously.",
"url": "https://eddiehinkle.com/2018/07/30/14/note/",
"content": {
"text": "Uh oh. Just realized that when I made a change to my automatic webmention sending code just before going to the hospital broke sending webmentions to everything other than Bridgy. Now I\u2019m gonna have to go back, find and resend the webmentions that weren\u2019t sent previously.",
"html": "<p>Uh oh. Just realized that when I made a change to my automatic webmention sending code just before going to the hospital broke sending webmentions to everything other than Bridgy. Now I\u2019m gonna have to go back, find and resend the webmentions that weren\u2019t sent previously.</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"post-type": "note",
"_id": "706514",
"_source": "226",
"_is_read": true
}
{
"type": "entry",
"published": "2018-07-29T19:30:08-04:00",
"url": "https://martymcgui.re/2018/07/29/193008/",
"category": [
"podcast",
"IndieWeb",
"this-week-indieweb-podcast"
],
"audio": [
"https://aperture-proxy.p3k.io/11a1b08e03249eeb82319b90f60f0b80bff0d0a9/68747470733a2f2f6d656469612e6d617274796d636775692e72652f32382f61352f39392f62662f66393837666639383932313932333564313066616661663435326339663439623265316137626434623632313661633836333662383831622e6d7033"
],
"syndication": [
"https://huffduffer.com/schmarty/494172",
"https://twitter.com/schmarty/status/1023713484117364742",
"https://www.facebook.com/marty.mcguire.54/posts/10212538661603500"
],
"name": "This Week in the IndieWeb Audio Edition \u2022 July 21st - 27th, 2018",
"content": {
"text": "Show/Hide Transcript \n \n Decentralized Web Summit is here, a webring for microcasts, and what should happen to our data when we die? It\u2019s the audio edition for This Week in the IndieWeb for July 21st - 27th, 2018.\n\nYou can find all of my audio editions and subscribe with your favorite podcast app here: martymcgui.re/podcasts/indieweb/.\n\nMusic from Aaron Parecki\u2019s 100DaysOfMusic project: Day 85 - Suit, Day 48 - Glitch, Day 49 - Floating, Day 9, and Day 11\n\nThanks to everyone in the IndieWeb chat for their feedback and suggestions. Please drop me a note if there are any changes you\u2019d like to see for this audio edition!",
"html": "Show/Hide Transcript \n \n <p>Decentralized Web Summit is here, a webring for microcasts, and what should happen to our data when we die? It\u2019s the audio edition for <a href=\"https://indieweb.org/this-week/2018-07-27.html\">This Week in the IndieWeb for July 21st - 27th, 2018</a>.</p>\n\n<p>You can find all of my audio editions and subscribe with your favorite podcast app here: <a href=\"https://martymcgui.re/podcasts/indieweb/\">martymcgui.re/podcasts/indieweb/</a>.</p>\n\n<p>Music from <a href=\"https://aaronparecki.com/\">Aaron Parecki</a>\u2019s <a href=\"https://100.aaronparecki.com/\">100DaysOfMusic project</a>: <a href=\"https://aaronparecki.com/2017/03/15/14/day85\">Day 85 - Suit</a>, <a href=\"https://aaronparecki.com/2017/02/06/7/day48\">Day 48 - Glitch</a>, <a href=\"https://aaronparecki.com/2017/02/07/4/day49\">Day 49 - Floating</a>, <a href=\"https://aaronparecki.com/2016/12/29/21/day-9\">Day 9</a>, and <a href=\"https://aaronparecki.com/2016/12/31/15/\">Day 11</a></p>\n\n<p>Thanks to everyone in the <a href=\"https://chat.indieweb.org/\">IndieWeb chat</a> for their feedback and suggestions. Please drop me a note if there are any changes you\u2019d like to see for this audio edition!</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://aperture-proxy.p3k.io/8275f85e3a389bd0ae69f209683436fc53d8bad9/68747470733a2f2f6d617274796d636775692e72652f696d616765732f6c6f676f2e6a7067"
},
"post-type": "audio",
"_id": "702047",
"_source": "175",
"_is_read": true
}
