I see github.com/aaronpk’s agreement with this proposal, and would like to see at least one, preferably 2-3, more parser developer(s) explicitly agreeing as well.
We also need to see this proposed change prototyped in at least one parser to make sure it is implementable (seems like it) and to see if there are any unintended consequences.
{
"type": "entry",
"published": "2018-04-17 10:40-0700",
"url": "http://tantek.com/2018/107/t2/",
"category": [
"9"
],
"content": {
"text": "Upon reconsideration, I retract my suggestion in https://github.com/microformats/microformats2-parsing/issues/10#issuecomment-331511675 that \"this issue's resolution should depend on resolving #9 first\", and commented on how to orthogonally resolve issue #9 (http://tantek.com/2018/107/t1).\n\nAs promised in https://github.com/microformats/microformats2-parsing/issues/10#issuecomment-331499024, I\u2019ve added PROPOSED text inline in the u-* parsing section per the proposal of this issue: http://microformats.org/wiki/index.php?title=microformats2-parsing&diff=66782&oldid=66724.\n\nI see github.com/aaronpk\u2019s agreement with this proposal, and would like to see at least one, preferably 2-3, more parser developer(s) explicitly agreeing as well.\n\nWe also need to see this proposed change prototyped in at least one parser to make sure it is implementable (seems like it) and to see if there are any unintended consequences.",
"html": "Upon reconsideration, I retract my suggestion in <a href=\"https://github.com/microformats/microformats2-parsing/issues/10#issuecomment-331511675\">https://github.com/microformats/microformats2-parsing/issues/10#issuecomment-331511675</a> that \"this issue's resolution should depend on resolving #9 first\", and commented on how to orthogonally resolve issue #9 (<a href=\"http://tantek.com/2018/107/t1\">http://tantek.com/2018/107/t1</a>).<br /><br />As promised in <a href=\"https://github.com/microformats/microformats2-parsing/issues/10#issuecomment-331499024\">https://github.com/microformats/microformats2-parsing/issues/10#issuecomment-331499024</a>, I\u2019ve added PROPOSED text inline in the u-* parsing section per the proposal of this issue: <a href=\"http://microformats.org/wiki/index.php?title=microformats2-parsing&diff=66782&oldid=66724\">http://microformats.org/wiki/index.php?title=microformats2-parsing&diff=66782&oldid=66724</a>.<br /><br />I see <a href=\"http://github.com/aaronpk\">github.com/aaronpk</a>\u2019s agreement with this proposal, and would like to see at least one, preferably 2-3, more parser developer(s) explicitly agreeing as well.<br /><br />We also need to see this proposed change prototyped in at least one parser to make sure it is implementable (seems like it) and to see if there are any unintended consequences."
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "http://tantek.com/",
"photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"_id": "237207",
"_source": "1",
"_is_read": true
}
{
"type": "entry",
"published": "2018-04-17T06:50:35+00:00",
"url": "https://jonnybarnes.uk/notes/L0",
"content": {
"text": "My micropub client works for the actual note, but location data isn\u2019t being sent with the request. \u2639\ufe0f",
"html": "<p>My micropub client works for the actual note, but location data isn\u2019t being sent with the request. \u2639\ufe0f</p>"
},
"author": {
"type": "card",
"name": "Jonny Barnes",
"url": "https://jonnybarnes.uk",
"photo": "https://aperture-media.p3k.io/jonnybarnes.uk/1339d21942b78d5fd1a9dea124fef7b5f895d0c8e4046ddb6119b9d6ef9ba7ef.jpg"
},
"_id": "235148",
"_source": "203",
"_is_read": true
}
I really enjoy these development logs. I think you’ve inspired me to start doing them for my own app, Indigenous, which is more IndieWeb focused but will support micro.blog kind of as a sibling relationship.
{
"type": "entry",
"published": "2018-04-17T00:52:24-04:00",
"summary": "I really enjoy these development logs. I think you\u2019ve inspired me to start doing them for my own app, Indigenous, which is more IndieWeb focused but will support micro.blog kind of as a sibling relationship.",
"url": "https://eddiehinkle.com/2018/04/17/2/reply/",
"in-reply-to": [
"http://blog.chrishannah.me/slate-development-log-6/"
],
"content": {
"text": "I really enjoy these development logs. I think you\u2019ve inspired me to start doing them for my own app, Indigenous, which is more IndieWeb focused but will support micro.blog kind of as a sibling relationship.",
"html": "<p>I really enjoy these development logs. I think you\u2019ve inspired me to start doing them for my own app, Indigenous, which is more IndieWeb focused but will support micro.blog kind of as a sibling relationship.</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-media.p3k.io/eddiehinkle.com/cf9f85e26d4be531bc908d37f69bff1c50b50b87fd066b254f1332c3553df1a8.jpg"
},
"refs": {
"http://blog.chrishannah.me/slate-development-log-6/": {
"type": "entry",
"url": "http://blog.chrishannah.me/slate-development-log-6/",
"name": "http://blog.chrishannah.me/slate-development-log-6/"
}
},
"_id": "235119",
"_source": "226",
"_is_read": true
}
{
"type": "entry",
"published": "2018-04-16T22:15:16-04:00",
"url": "https://david.shanske.com/2018/04/16/an-indieweb-podcast-episode-1-leaving-facebook/",
"audio": [
"https://aperture-media.p3k.io/david.shanske.com/295e7e9a76c576d37db2556a84cba3ac696cb0e87e4476fc102dc47f983c4e59.mp3"
],
"syndication": [
"https://www.facebook.com/100002356503167/posts/1666046973483837",
"https://twitter.com/dshanske/status/986065579860742144"
],
"name": "Episode 1: Leaving Facebook?",
"content": {
"text": "This second episode was originally recorded in March, abruptly ended, and then was not completed until April due scheduling. In it, Chris and I discuss the hot topic of Facebook scandals and where you might go if you decide to leave Facebook.\nShow Notes\nThe originating articles that kicked off the Facebook/Cambridge Analytica issue:\n3/16/18: Facebook\u2019s Newsroom: Suspending Cambridge Analytica and SCL Group from Facebook by Paul Grewal Protecting people\u2019s information is at the heart of everything we do.\n\n3/17/18: The Guardian: Revealed: 50 million Facebook profiles harvested for Cambridge Analytica in major data breach https://www.theguardian.com/news/2018/mar/17/cambridge-analytica-facebook-influence-us-election\n\n3/17/18: New York Times: \u201cHow Trump Consultants Exploited the Facebook data of Millions\u201d: https://www.nytimes.com/2018/03/17/us/politics/cambridge-analytica-trump-campaign.html\n\n\u00a0\nOther related articles:\nAnil Dash: Article bringing the Facebook issue back around to regaining the good parts of the \u201cold\u201d web\u201d https://medium.com/@anildash/the-missing-building-blocks-of-the-web-3fa490ae5cbc\n\nHow To Change Your Facebook Settings To Opt Out of Platform API Sharing (Electronic Frontier Foundation) https://www.eff.org/deeplinks/2018/03/how-change-your-facebook-settings-opt-out-platform-api-sharing\n\n3/24/18: Ars Technica: Facebook scraped call, text message data for years from Android phones\n\nRecent Documented Facebook Quitters:\nJonathan LaCour: https://cleverdevil.io/2018/ive-officially-deleted-my-facebook-account-and\nEddie Hinkle: https://eddiehinkle.com/2018/03/22/5/article/\nNatalie Wolchover: https://twitter.com/nattyover/status/975711260221362177\nNew York Times Profile of multiple quitters: https://www.nytimes.com/2018/03/21/technology/users-abandon-facebook.html\nIndieWeb Wiki related pages of interest here:\nhttps://indieweb.org/why\nhttps://indieweb.org/principles\nhttps://indieweb.org/Facebook\nhttps://indieweb.org/silo-quits\nhttps://github.com/tootsuite/mastodon/issues/6074\nPotential simple places to move to when leaving Facebook\n\nMicro.blog for $5/month (or bring your own web site for free)\nMastodon\nWordPress.com\nTumblr.com\n\nWithKnown (Paid service or host your own)\n\nWordPress.org (self-hosted or managed)\nOther possible projects/options: https://indieweb.org/projects\n\n\u00a0\nSebastian Greger\u2019s Privacy policy: https://sebastiangreger.net/privacy-policy/\nMastodon not supporting Webmention specification: https://github.com/tootsuite/mastodon/issues/6074#issuecomment-378452136",
"html": "This second episode was originally recorded in March, abruptly ended, and then was not completed until April due scheduling. In it, Chris and I discuss the hot topic of Facebook scandals and where you might go if you decide to leave Facebook.\n<h1><strong>Show Notes</strong></h1>\n<p>The originating articles that kicked off the Facebook/Cambridge Analytica issue:</p>\n<ul><li>3/16/18: Facebook\u2019s Newsroom: <a href=\"http://newsroom.fb.com/news/2018/03/suspending-cambridge-analytica/\">Suspending Cambridge Analytica and SCL Group from Facebook</a> by Paul Grewal <i>Protecting people\u2019s information is at the heart of everything we do.</i>\n</li>\n<li>3/17/18: The Guardian: Revealed: 50 million Facebook profiles harvested for Cambridge Analytica in major data breach <a href=\"https://www.theguardian.com/news/2018/mar/17/cambridge-analytica-facebook-influence-us-election\">https://www.theguardian.com/news/2018/mar/17/cambridge-analytica-facebook-influence-us-election</a>\n</li>\n</ul><ul><li>3/17/18: New York Times: \u201cHow Trump Consultants Exploited the Facebook data of Millions\u201d: <a href=\"https://www.nytimes.com/2018/03/17/us/politics/cambridge-analytica-trump-campaign.html\">https://www.nytimes.com/2018/03/17/us/politics/cambridge-analytica-trump-campaign.html</a>\n</li>\n</ul><p>\u00a0</p>\n<p>Other related articles:</p>\n<ul><li>Anil Dash: Article bringing the Facebook issue back around to regaining the good parts of the \u201cold\u201d web\u201d <a href=\"https://medium.com/@anildash/the-missing-building-blocks-of-the-web-3fa490ae5cbc\">https://medium.com/@anildash/the-missing-building-blocks-of-the-web-3fa490ae5cbc</a>\n</li>\n<li>How To Change Your Facebook Settings To Opt Out of Platform API Sharing (Electronic Frontier Foundation) <a href=\"https://www.eff.org/deeplinks/2018/03/how-change-your-facebook-settings-opt-out-platform-api-sharing\">https://www.eff.org/deeplinks/2018/03/how-change-your-facebook-settings-opt-out-platform-api-sharing</a>\n</li>\n<li>3/24/18: Ars Technica: <a href=\"https://arstechnica.com/information-technology/2018/03/facebook-scraped-call-text-message-data-for-years-from-android-phones/\">Facebook scraped call, text message data for years from Android phones</a>\n</li>\n</ul><h2>Recent Documented Facebook Quitters:</h2>\n<p>Jonathan LaCour: <a href=\"https://cleverdevil.io/2018/ive-officially-deleted-my-facebook-account-and\">https://cleverdevil.io/2018/ive-officially-deleted-my-facebook-account-and</a></p>\n<p>Eddie Hinkle: <a href=\"https://eddiehinkle.com/2018/03/22/5/article/\">https://eddiehinkle.com/2018/03/22/5/article/</a></p>\n<p>Natalie Wolchover: <a href=\"https://twitter.com/nattyover/status/975711260221362177\">https://twitter.com/nattyover/status/975711260221362177</a></p>\n<p>New York Times Profile of multiple quitters: <a href=\"https://www.nytimes.com/2018/03/21/technology/users-abandon-facebook.html\">https://www.nytimes.com/2018/03/21/technology/users-abandon-facebook.html</a></p>\n<h2>IndieWeb Wiki related pages of interest here:</h2>\n<ul><li><a href=\"https://indieweb.org/why\">https://indieweb.org/why</a></li>\n<li><a href=\"https://indieweb.org/principles\">https://indieweb.org/principles</a></li>\n<li><a href=\"https://indieweb.org/Facebook\">https://indieweb.org/Facebook</a></li>\n<li><a href=\"https://indieweb.org/silo-quits\">https://indieweb.org/silo-quits</a></li>\n<li><a href=\"https://github.com/tootsuite/mastodon/issues/6074\">https://github.com/tootsuite/mastodon/issues/6074</a></li>\n</ul><h2>Potential simple places to move to when leaving Facebook</h2>\n<ul><li>\n<a href=\"https://indieweb.org/micro.blog\">Micro.blog</a> for $5/month (or bring your own web site for free)</li>\n<li><a href=\"https://indieweb.org/Mastodon\">Mastodon</a></li>\n<li><a href=\"https://indieweb.org/WordPress.com\">WordPress.com</a></li>\n<li><a href=\"https://indieweb.org/Tumblr\">Tumblr.com</a></li>\n<li>\n<a href=\"https://indieweb.org/Known\">WithKnown</a> (Paid service or host your own)</li>\n<li>\n<a href=\"https://indieweb.org/WordPress\">WordPress.org</a> (self-hosted or managed)</li>\n<li>Other possible projects/options: <a href=\"https://indieweb.org/projects\">https://indieweb.org/projects</a>\n</li>\n</ul><p>\u00a0</p>\n<p>Sebastian Greger\u2019s Privacy policy: <a href=\"https://sebastiangreger.net/privacy-policy/\">https://sebastiangreger.net/privacy-policy/</a></p>\n<p>Mastodon not supporting Webmention specification: <a href=\"https://github.com/tootsuite/mastodon/issues/6074#issuecomment-378452136\">https://github.com/tootsuite/mastodon/issues/6074#issuecomment-378452136</a></p>"
},
"author": {
"type": "card",
"name": "David Shanske",
"url": "https://david.shanske.com",
"photo": "https://aperture-media.p3k.io/secure.gravatar.com/ee1cea4a5d6465ac3bd8e56fc0bbfdacd25be40ef0968e6b2b2e8016103cb826.png"
},
"_id": "235065",
"_source": "5",
"_is_read": true
}
“the Twitter system doesn’t recognize that it’s encouraging people to follow additional extremist accounts, and Facebook’s Groups engine doesn’t understand why directing conspiracy theorists to new conspiracy communities is possibly a bad idea.” https://www.wired.com/story/creating-ethical-recommendation-engines/#Indieweb
An indie reader (I probably shouldn’t have used caps. Haha) is an attempt at getting the Facebook/Twitter like experience into feed readers. So that one can control what content they read and yet enjoy the reply/like/save functionality that exists in modern social media. This page provides some additional info: https://indieweb.org/reader
{
"type": "entry",
"published": "2018-04-16T11:26:38-04:00",
"summary": "An indie reader (I probably shouldn\u2019t have used caps. Haha) is an attempt at getting the Facebook/Twitter like experience into feed readers. So that one can control what content they read and yet enjoy the reply/like/save functionality that exists in modern social media. This page provides some additional info: https://indieweb.org/reader",
"url": "https://eddiehinkle.com/2018/04/16/19/reply/",
"in-reply-to": [
"https://micro.blog/oyam/487355"
],
"content": {
"text": "An indie reader (I probably shouldn\u2019t have used caps. Haha) is an attempt at getting the Facebook/Twitter like experience into feed readers. So that one can control what content they read and yet enjoy the reply/like/save functionality that exists in modern social media. This page provides some additional info: https://indieweb.org/reader",
"html": "<p>An indie reader (I probably shouldn\u2019t have used caps. Haha) is an attempt at getting the Facebook/Twitter like experience into feed readers. So that one can control what content they read and yet enjoy the reply/like/save functionality that exists in modern social media. This page provides some additional info: <a href=\"https://indieweb.org/reader#Indigenous\">https://indieweb.org/reader</a></p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-media.p3k.io/eddiehinkle.com/cf9f85e26d4be531bc908d37f69bff1c50b50b87fd066b254f1332c3553df1a8.jpg"
},
"refs": {
"https://micro.blog/oyam/487355": {
"type": "entry",
"url": "https://micro.blog/oyam/487355",
"name": "https://micro.blog/oyam/487355"
}
},
"_id": "232907",
"_source": "226",
"_is_read": true
}
I found that I have so many channels in my IndieReader that it was starting to create stress when I opened it. So I’m testing out viewing only channels with new content. Eventually this will be a filter setting you can quickly switch back and forth between
{
"type": "entry",
"published": "2018-04-15T23:58:27-04:00",
"summary": "I found that I have so many channels in my IndieReader that it was starting to create stress when I opened it. So I\u2019m testing out viewing only channels with new content. Eventually this will be a filter setting you can quickly switch back and forth between",
"url": "https://eddiehinkle.com/2018/04/15/39/photo/",
"category": [
"indieweb",
"reader",
"microsub"
],
"photo": [
"https://aperture-media.p3k.io/eddiehinkle.com/cafa81194fa5204626385e3ac6d00de179382f7e5adbfa84cb1a2092b50c556d.jpg"
],
"content": {
"text": "I found that I have so many channels in my IndieReader that it was starting to create stress when I opened it. So I\u2019m testing out viewing only channels with new content. Eventually this will be a filter setting you can quickly switch back and forth between"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-media.p3k.io/eddiehinkle.com/cf9f85e26d4be531bc908d37f69bff1c50b50b87fd066b254f1332c3553df1a8.jpg"
},
"_id": "231339",
"_source": "226",
"_is_read": true
}
FYI in terms of easy and iOS. One option on Jekyll or Wordpress is Micropub (https://indieweb.org/Micropub). Wordpress has plugins and Jekyll has options (https://indieweb.org/Jekyll). Then you can use Indigenous (https://indieweb.org/Indigenous_for_iOS) to post
{
"type": "entry",
"published": "2018-04-15T17:58:34-04:00",
"summary": "FYI in terms of easy and iOS. One option on Jekyll or Wordpress is Micropub (https://indieweb.org/Micropub). Wordpress has plugins and Jekyll has options (https://indieweb.org/Jekyll). Then you can use Indigenous (https://indieweb.org/Indigenous_for_iOS) to post",
"url": "https://eddiehinkle.com/2018/04/15/23/reply/",
"in-reply-to": [
"https://twitter.com/MisterKapowski/status/985628130504331264"
],
"content": {
"text": "FYI in terms of easy and iOS. One option on Jekyll or Wordpress is Micropub (https://indieweb.org/Micropub). Wordpress has plugins and Jekyll has options (https://indieweb.org/Jekyll). Then you can use Indigenous (https://indieweb.org/Indigenous_for_iOS) to post",
"html": "<p>FYI in terms of easy and iOS. One option on Jekyll or Wordpress is Micropub (https://indieweb.org/Micropub). Wordpress has plugins and Jekyll has options (https://indieweb.org/Jekyll). Then you can use Indigenous (https://indieweb.org/Indigenous_for_iOS) to post</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-media.p3k.io/eddiehinkle.com/cf9f85e26d4be531bc908d37f69bff1c50b50b87fd066b254f1332c3553df1a8.jpg"
},
"refs": {
"https://twitter.com/MisterKapowski/status/985628130504331264": {
"type": "entry",
"url": "https://twitter.com/MisterKapowski/status/985628130504331264",
"name": "https://twitter.com/MisterKapowski/status/985628130504331264"
}
},
"_id": "230910",
"_source": "226",
"_is_read": true
}
By replying on my site, I am using @schnarfed's service to collect tweeted responses, then both his service and my site have cached copies of the reply and the name photo and url of the responder. @ade_oshineye could do that with webmention.herokuapp.com on his static site too.
{
"type": "entry",
"published": "2018-04-15T15:28:24+0000",
"url": "http://known.kevinmarks.com/2018/by-replying-on-my-site-i-am",
"syndication": [
"https://twitter.com/kevinmarks/status/985540350965006338"
],
"in-reply-to": [
"https://twitter.com/_dgoldsmith/status/985538957730598913?s=19"
],
"content": {
"text": "By replying on my site, I am using @schnarfed's service to collect tweeted responses, then both his service and my site have cached copies of the reply and the name photo and url of the responder. @ade_oshineye could do that with webmention.herokuapp.com on his static site too.",
"html": "By replying on my site, I am using <a href=\"https://twitter.com/schnarfed\">@schnarfed</a>'s service to collect tweeted responses, then both his service and my site have cached copies of the reply and the name photo and url of the responder. <a href=\"https://twitter.com/ade_oshineye\">@ade_oshineye</a> could do that with webmention.herokuapp.com on his static site too."
},
"author": {
"type": "card",
"name": "Kevin Marks",
"url": "http://known.kevinmarks.com/profile/kevinmarks",
"photo": "https://aperture-media.p3k.io/known.kevinmarks.com/f893d11435a62200ec9585e0ea3d84b2bdc478aa0a056dda35a43ce4c04d58a0.jpg"
},
"_id": "229682",
"_source": "205",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "<span class='p-author h-card'>Kh\u00fcrt Williams</span>",
"url": "https://islandinthenet.com/",
"photo": null
},
"url": "https://tracking.feedpress.it/link/1771/8863853",
"published": "2018-04-15T14:28:54+00:00",
"content": {
"html": "<a href=\"https://www.jeremycherfas.net/blog/a-user-considers\">A user considers</a> by <a href=\"https://jeremycherfas.net/\"><img src=\"https://jeremycherfas.net/user/plugins/aboutme/assets/avatars/zoot.jpg\" alt=\"It\u2019s a Journey zoot\" title=\"It\u2019s a Journey\" />Jeremy Cherfas</a><em> (jeremycherfas.net)</em>\n<blockquote>There's a strain of thought going around that the IndieWeb is deliberately exclusionary. I don't know why, and I've tried to counter that kind of message when I see it, but it is only the deliberately part that I feel I can counter. With a couple of little exceptions, I see no evidence that barriers are being erected intentionally. I just see that the people who create the building blocks sometimes forget to put themselves in a less-knowledgeable user's shoes. Once that has been pointed out, as Eli did, they're quick to fix things.</blockquote>\n\nJeremy, when I first started using the IndieWeb plugins, I was initially frustrated and despite a technical background, felt at a loss in understanding what was going on. Several <a href=\"http://boffosocko.com/research/indieweb/\">posts by Chris Aldrich</a> helped get me past the frustrating stage but I admit that right now, it\u2019s very much a work in progress. It\u2019s not ready for the general public.\n<p>The post <a href=\"https://islandinthenet.com/its-a-journey/\"><span class='p-name'>It\u2019s a Journey</span></a> by <a href=\"https://islandinthenet.com/\"><span class='p-author h-card'>Kh\u00fcrt Williams</span></a> appeared first on <a href=\"https://islandinthenet.com/\">Island in the Net</a>.</p>",
"text": "A user considers by Jeremy Cherfas (jeremycherfas.net)\nThere's a strain of thought going around that the IndieWeb is deliberately exclusionary. I don't know why, and I've tried to counter that kind of message when I see it, but it is only the deliberately part that I feel I can counter. With a couple of little exceptions, I see no evidence that barriers are being erected intentionally. I just see that the people who create the building blocks sometimes forget to put themselves in a less-knowledgeable user's shoes. Once that has been pointed out, as Eli did, they're quick to fix things.\n\nJeremy, when I first started using the IndieWeb plugins, I was initially frustrated and despite a technical background, felt at a loss in understanding what was going on. Several posts by Chris Aldrich helped get me past the frustrating stage but I admit that right now, it\u2019s very much a work in progress. It\u2019s not ready for the general public.\nThe post <span class='p-name'>It\u2019s a Journey</span> by <span class='p-author h-card'>Kh\u00fcrt Williams</span> appeared first on Island in the Net."
},
"name": "It\u2019s a Journey",
"_id": "229345",
"_source": "242",
"_is_read": true
}
{
"type": "entry",
"published": "2018-04-15T01:25:36-04:00",
"summary": "Awesome! Those are some great updates! Especially the automatic webmentions (something I want to do soon) and the h-card embedded of person tags.",
"url": "https://eddiehinkle.com/2018/04/15/2/reply/",
"in-reply-to": [
"https://martymcgui.re/2018/04/14/194434/"
],
"content": {
"text": "Awesome! Those are some great updates! Especially the automatic webmentions (something I want to do soon) and the h-card embedded of person tags.",
"html": "<p>Awesome! Those are some great updates! Especially the automatic webmentions (something I want to do soon) and the h-card embedded of person tags.</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-media.p3k.io/eddiehinkle.com/cf9f85e26d4be531bc908d37f69bff1c50b50b87fd066b254f1332c3553df1a8.jpg"
},
"refs": {
"https://martymcgui.re/2018/04/14/194434/": {
"type": "entry",
"url": "https://martymcgui.re/2018/04/14/194434/",
"name": "https://martymcgui.re/2018/04/14/194434/"
}
},
"_id": "228679",
"_source": "226",
"_is_read": true
}
The IndieAuth plugin update I was writing about last week finally got released to the WordPress repository. It’s a great development for the community. You can now use your website to log into a variety of different services.
{
"type": "entry",
"published": "2018-04-14T22:31:37-04:00",
"url": "https://david.shanske.com/2018/04/14/1866/",
"content": {
"text": "The IndieAuth plugin update I was writing about last week finally got released to the WordPress repository. It\u2019s a great development for the community. You can now use your website to log into a variety of different services."
},
"author": {
"type": "card",
"name": "David Shanske",
"url": "https://david.shanske.com",
"photo": "https://aperture-media.p3k.io/secure.gravatar.com/ee1cea4a5d6465ac3bd8e56fc0bbfdacd25be40ef0968e6b2b2e8016103cb826.png"
},
"_id": "228452",
"_source": "5",
"_is_read": true
}
{
"type": "entry",
"published": "2018-04-14T19:44:34-04:00",
"url": "https://martymcgui.re/2018/04/14/194434/",
"category": [
"site-update",
"webmention",
"person-tag"
],
"name": "Site Updates: automatic webmentions, person tags, better reply image handling",
"content": {
"text": "I had a bit of time this weekend to tinker with my site.\nThe biggest change is one that happens totally behind the scenes - I've added a step to the service that compiles and deploys my site to automatically send Webmentions\u00a0from my posts to posts that I am responding to or mentioning. There are many folks with projects around this, but they tend to be a little more aggressive than I like in finding URLs to send mentions to. For example, they often want to send mentions to my homepage and avatar image for my own posts!\nSo, I have added a Webmention sender to my site that is triggered by new and updated pages and sends mentions to any URLs that I am specifically responding to\u00a0or person tagging, along with any URLs mentioned in the actual content of the post.\nAlong with this, I now support person tags on regular entries like this one. I can add a tag like http://tantek.com to a post and it will tag them with proper markup and, if possible, show the name and photo from their homepage h-card.\nFinally, I did a little cleanup in how I display reply contexts for other people's posts that have multiple images in them, like this one from Aaron Parecki.\nIt's nice to be able to sit down and knock off the little nagging TODOs here on the site. That said, I'm hoping to be able to make some big changes, soon! We'll see what my schedule allows.",
"html": "<p>I had a bit of time this weekend to tinker with my site.</p>\n<p>The biggest change is one that happens totally behind the scenes - I've added a step to the service that compiles and deploys my site to automatically send <a href=\"https://indieweb.org/Webmention\">Webmentions</a>\u00a0from my posts to posts that I am responding to or mentioning. There are many folks with projects around this, but they tend to be a little more aggressive than I like in finding URLs to send mentions to. For example, they often want to send mentions to my homepage and avatar image for my own posts!</p>\n<p>So, I have added a Webmention sender to my site that is triggered by new and updated pages and sends mentions to any URLs that I am specifically <a href=\"https://indieweb.org/response\">responding to</a>\u00a0or <a href=\"https://indieweb.org/person-tag\">person tagging</a>, along with any URLs mentioned in the actual content of the post.</p>\n<p>Along with this, I now support person tags on regular entries <a href=\"https://martymcgui.re/2018/04/13/080659/\">like this one</a>. I can add a tag like http://tantek.com to a post and it will tag them with proper markup and, if possible, show the name and photo from their homepage h-card.</p>\n<p>Finally, I did a little cleanup in how I display reply contexts for other people's posts that have multiple images in them, like <a href=\"https://martymcgui.re/2018/04/08/082932/\">this one from Aaron Parecki</a>.</p>\n<p>It's nice to be able to sit down and knock off the little nagging TODOs here on the site. That said, I'm hoping to be able to make some big changes, soon! We'll see what my schedule allows.</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://aperture-media.p3k.io/martymcgui.re/4f9fac2b9e3ae62998c557418143efe288bca8170a119921a9c6bfeb0a1263a2.jpg"
},
"_id": "228107",
"_source": "175",
"_is_read": true
}
{
"type": "entry",
"published": "2018-04-14T11:46:35-04:00",
"url": "https://martymcgui.re/2018/04/14/114635/",
"category": [
"podcast",
"IndieWeb",
"this-week-indieweb-podcast"
],
"audio": [
"https://aperture-media.p3k.io/media.martymcgui.re/85d12fa1cf7e22c8cee5ed2c600280d0b1c5601b15235690f69008b7a35b28d3.mp3"
],
"syndication": [
"https://huffduffer.com/schmarty/471373",
"https://twitter.com/schmarty/status/985183436724953088",
"https://www.facebook.com/marty.mcguire.54/posts/10211846185332026"
],
"name": "This Week in the IndieWeb Audio Edition \u2022 April 7th - 13th, 2018",
"content": {
"text": "Show/Hide Transcript \n \n A new way to podcast, blogging is back, and so many silo quits. It\u2019s the audio edition for This Week in the IndieWeb for April 7th - 13th, 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>A new way to podcast, blogging is back, and so many silo quits. It\u2019s the audio edition for <a href=\"https://indieweb.org/this-week/2018-04-13.html\">This Week in the IndieWeb for April 7th - 13th, 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-media.p3k.io/martymcgui.re/4f9fac2b9e3ae62998c557418143efe288bca8170a119921a9c6bfeb0a1263a2.jpg"
},
"_id": "226814",
"_source": "175",
"_is_read": true
}
“ By focusing on growth and growth only, and ignoring the problems, they amassed a large set of cultural norms on their platforms that stem from harassment or abuse or bad behavior.” http://nzzl.us/XPMlGI3#Indieweb
{
"type": "entry",
"published": "2018-04-14T08:33:26+0000",
"url": "http://known.kevinmarks.com/2018/-by-focusing-on-growth-and-growth",
"category": [
"Indieweb"
],
"syndication": [
"https://twitter.com/kevinmarks/status/985073536887750657"
],
"content": {
"text": "\u201c By focusing on growth and growth only, and ignoring the problems, they amassed a large set of cultural norms on their platforms that stem from harassment or abuse or bad behavior.\u201d http://nzzl.us/XPMlGI3 #Indieweb",
"html": "\u201c By focusing on growth and growth only, and ignoring the problems, they amassed a large set of cultural norms on their platforms that stem from harassment or abuse or bad behavior.\u201d <a href=\"http://nzzl.us/XPMlGI3\">http://nzzl.us/XPMlGI3</a> <a href=\"http://known.kevinmarks.com/tag/Indieweb\" class=\"p-category\">#Indieweb</a>"
},
"author": {
"type": "card",
"name": "Kevin Marks",
"url": "http://known.kevinmarks.com/profile/kevinmarks",
"photo": "https://aperture-media.p3k.io/known.kevinmarks.com/f893d11435a62200ec9585e0ea3d84b2bdc478aa0a056dda35a43ce4c04d58a0.jpg"
},
"_id": "226071",
"_source": "205",
"_is_read": true
}
One of the difficulties of trying to be IndieWeb is that because there is no One True Way, only a set of useful building blocks, lovingly assembled, when something isn't working well it can be hard to know which bit is responsible for what. I had that problem recently with micro.blog waiting a long time before a post here appeared there. Then today, a post I published this morning popped up on micro.blog, and I had time to think about fixing things.
It was trivial, but I fixed it. Here's how.
More this way ...
{
"type": "entry",
"published": "2018-04-12T19:45:00+02:00",
"summary": "One of the difficulties of trying to be IndieWeb is that because there is no One True Way, only a set of useful building blocks, lovingly assembled, when something isn't working well it can be hard to know which bit is responsible for what. I had that problem recently with micro.blog waiting a long time before a post here appeared there. Then today, a post I published this morning popped up on micro.blog, and I had time to think about fixing things.\nIt was trivial, but I fixed it. Here's how.\nMore this way ...",
"url": "https://www.jeremycherfas.net/blog/change-for-a-time",
"name": "Change for a time",
"content": {
"text": "One of the difficulties of trying to be IndieWeb is that because there is no One True Way, only a set of useful building blocks, lovingly assembled, when something isn't working well it can be hard to know which bit is responsible for what. I had that problem recently with micro.blog waiting a long time before a post here appeared there. Then today, a post I published this morning popped up on micro.blog, and I had time to think about fixing things.\nIt was trivial, but I fixed it. Here's how.\n\n More this way ...",
"html": "<p>One of the difficulties of trying to be IndieWeb is that because there is no One True Way, only a set of useful building blocks, lovingly assembled, when something isn't working well it can be hard to know which bit is responsible for what. I had that problem recently with <a href=\"https://micro.blog\">micro.blog</a> waiting a long time before a post here appeared there. Then today, a post I published this morning popped up on micro.blog, and I had time to think about fixing things.</p>\n<p>It was trivial, but I fixed it. Here's how.</p>\n\n <p><a href=\"https://www.jeremycherfas.net/blog/change-for-a-time\">More this way ...</a></p>"
},
"_id": "219630",
"_source": "202",
"_is_read": true
}
{
"type": "entry",
"published": "2018-04-12T11:46:50-04:00",
"url": "https://miklb.com/blog/2018/04/12/3726/",
"syndication": [
"https://twitter.com/miklb/status/984457842005610506"
],
"in-reply-to": [
"https://twitter.com/zachleat/status/984457213904334850?ref_src=twsrc%5Etfw"
],
"content": {
"text": "Indieweb and webmentions. Posts originate on my site, then syndicate to Twitter. I\u2019m replying from my site to your tweet now. \ud83d\ude42",
"html": "<p>Indieweb and webmentions. Posts originate on my site, then syndicate to Twitter. I\u2019m replying from my site to your tweet now. \ud83d\ude42\n</p>"
},
"refs": {
"https://twitter.com/zachleat/status/984457213904334850?ref_src=twsrc%5Etfw": {
"type": "entry",
"url": "https://twitter.com/zachleat/status/984457213904334850?ref_src=twsrc%5Etfw",
"content": {
"text": "love the twitter aggregator!\u2014 Zach Leatherman (@zachleat) April 12, 2018"
}
}
},
"_id": "219119",
"_source": "42",
"_is_read": true
}
First off, thanks for writing this up! Often times discussions that happen on IRC can remain locked up in there when no one takes the time and effort to write their thoughts from the IRC conversations out onto their blogs (which is a key component to everything we are discussing, using our blogs for thoughts. haha)
I think a key issue that people producing clients (like swentel and I with the Indigenous clients) will run into is that when generation 3 or 4 people download our apps they can often be scared off by the discussion of protocols, even if those protocols are easily accessible through a user-friendly service. At the same time, you can’t AVOID using protocol names in discussing client compatibility. I think the key is finding the middle ground. This was actually brainstormed by schmarty that the key is beginning by mentioning popular services that support the protocol and only then following up with the protocol. For example “You can use this with Micro.blog, Known or any other Micropub compatible server”. It starts with the terms that a user might already know and aren’t as scary, but it also doesn’t shy away from the fact that the real compatibility lays in the Micropub compatibility.
These are great thoughts to be thinking through, how we can better aim IndieWeb-focused technologies toward a wider audience. I think one of the reason you found so much push back regarding protocols is because the IndieWeb group tends to be practical in the understanding that not all sites and/or people will use the protocols that we use. The goal is to interoperate as much as we can and when possible push for support of IndieWeb-focused protocols. That means often times people can attempt to distance themselves from the protocols because while they are vital to what we do as a community, we don’t want to be limited by them either. (Hence our push of POSSE and PESOS). Rather than saying everyone that wants to follow us has to read our h-feed, we often times will run services that convert our h-feeds into RSS feeds or JSON feeds so we can interoperate with services like micro.blog that supports Micropub and Webmention but doesn’t parse h-feeds.
{
"type": "entry",
"published": "2018-04-12T10:44:14-04:00",
"summary": "First off, thanks for writing this up! Often times discussions that happen on IRC can remain locked up in there when no one takes the time and effort to write their thoughts from the IRC conversations out onto their blogs (which is a key component to everything we are discussing, using our blogs for thoughts. haha)\nI think a key issue that people producing clients (like swentel and I with the Indigenous clients) will run into is that when generation 3 or 4 people download our apps they can often be scared off by the discussion of protocols, even if those protocols are easily accessible through a user-friendly service. At the same time, you can\u2019t AVOID using protocol names in discussing client compatibility. I think the key is finding the middle ground. This was actually brainstormed by schmarty that the key is beginning by mentioning popular services that support the protocol and only then following up with the protocol. For example \u201cYou can use this with Micro.blog, Known or any other Micropub compatible server\u201d. It starts with the terms that a user might already know and aren\u2019t as scary, but it also doesn\u2019t shy away from the fact that the real compatibility lays in the Micropub compatibility.\nThese are great thoughts to be thinking through, how we can better aim IndieWeb-focused technologies toward a wider audience. I think one of the reason you found so much push back regarding protocols is because the IndieWeb group tends to be practical in the understanding that not all sites and/or people will use the protocols that we use. The goal is to interoperate as much as we can and when possible push for support of IndieWeb-focused protocols. That means often times people can attempt to distance themselves from the protocols because while they are vital to what we do as a community, we don\u2019t want to be limited by them either. (Hence our push of POSSE and PESOS). Rather than saying everyone that wants to follow us has to read our h-feed, we often times will run services that convert our h-feeds into RSS feeds or JSON feeds so we can interoperate with services like micro.blog that supports Micropub and Webmention but doesn\u2019t parse h-feeds.",
"url": "https://eddiehinkle.com/2018/04/12/6/reply/",
"category": [
"indieweb"
],
"in-reply-to": [
"http://quickthoughts.jgregorymcverry.com/2018/04/12/what-exactly-is-indieweb-and-how-can-we-talk-about"
],
"content": {
"text": "First off, thanks for writing this up! Often times discussions that happen on IRC can remain locked up in there when no one takes the time and effort to write their thoughts from the IRC conversations out onto their blogs (which is a key component to everything we are discussing, using our blogs for thoughts. haha)\n\nI think a key issue that people producing clients (like swentel and I with the Indigenous clients) will run into is that when generation 3 or 4 people download our apps they can often be scared off by the discussion of protocols, even if those protocols are easily accessible through a user-friendly service. At the same time, you can\u2019t AVOID using protocol names in discussing client compatibility. I think the key is finding the middle ground. This was actually brainstormed by schmarty that the key is beginning by mentioning popular services that support the protocol and only then following up with the protocol. For example \u201cYou can use this with Micro.blog, Known or any other Micropub compatible server\u201d. It starts with the terms that a user might already know and aren\u2019t as scary, but it also doesn\u2019t shy away from the fact that the real compatibility lays in the Micropub compatibility.\n\nThese are great thoughts to be thinking through, how we can better aim IndieWeb-focused technologies toward a wider audience. I think one of the reason you found so much push back regarding protocols is because the IndieWeb group tends to be practical in the understanding that not all sites and/or people will use the protocols that we use. The goal is to interoperate as much as we can and when possible push for support of IndieWeb-focused protocols. That means often times people can attempt to distance themselves from the protocols because while they are vital to what we do as a community, we don\u2019t want to be limited by them either. (Hence our push of POSSE and PESOS). Rather than saying everyone that wants to follow us has to read our h-feed, we often times will run services that convert our h-feeds into RSS feeds or JSON feeds so we can interoperate with services like micro.blog that supports Micropub and Webmention but doesn\u2019t parse h-feeds.",
"html": "<p>First off, thanks for writing this up! Often times discussions that happen on IRC can remain locked up in there when no one takes the time and effort to write their thoughts from the IRC conversations out onto their blogs (which is a key component to everything we are discussing, using our blogs for thoughts. haha)</p>\n\n<p>I think a key issue that people producing clients (like <a href=\"https://realize.be/\">swentel</a> and I with the Indigenous clients) will run into is that when generation 3 or 4 people download our apps they can often be scared off by the discussion of protocols, even if those protocols are easily accessible through a user-friendly service. At the same time, you can\u2019t AVOID using protocol names in discussing client compatibility. I think the key is finding the middle ground. This was actually brainstormed by <a href=\"https://martymcgui.re/\">schmarty</a> that the key is beginning by mentioning popular services that support the protocol and only then following up with the protocol. For example \u201cYou can use this with Micro.blog, Known or any other Micropub compatible server\u201d. It starts with the terms that a user might already know and aren\u2019t as scary, but it also doesn\u2019t shy away from the fact that the real compatibility lays in the Micropub compatibility.</p>\n\n<p>These are great thoughts to be thinking through, how we can better aim IndieWeb-focused technologies toward a wider audience. I think one of the reason you found so much push back regarding protocols is because the IndieWeb group tends to be practical in the understanding that not all sites and/or people will use the protocols that we use. The goal is to interoperate as much as we can and when possible push for support of IndieWeb-focused protocols. That means often times people can attempt to distance themselves from the protocols because while they are vital to what we do as a community, we don\u2019t want to be limited by them either. (Hence our push of <a href=\"https://indieweb.org/POSSE\">POSSE</a> and <a href=\"https://indieweb.org/PESOS\">PESOS</a>). Rather than saying everyone that wants to follow us has to read our h-feed, we often times will run services that convert our h-feeds into RSS feeds or JSON feeds so we can interoperate with services like micro.blog that supports <a href=\"https://indieweb.org/micropub\">Micropub</a> and <a href=\"https://indieweb.org/webmention\">Webmention</a> but doesn\u2019t parse h-feeds.</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-media.p3k.io/eddiehinkle.com/cf9f85e26d4be531bc908d37f69bff1c50b50b87fd066b254f1332c3553df1a8.jpg"
},
"refs": {
"http://quickthoughts.jgregorymcverry.com/2018/04/12/what-exactly-is-indieweb-and-how-can-we-talk-about": {
"type": "entry",
"url": "http://quickthoughts.jgregorymcverry.com/2018/04/12/what-exactly-is-indieweb-and-how-can-we-talk-about",
"name": "http://quickthoughts.jgregorymcverry.com/2018/04/12/what-exactly-is-indieweb-and-how-can-we-talk-about"
}
},
"_id": "218985",
"_source": "226",
"_is_read": true
}
