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
}
Same, I used to pay for crossposting without using it as a way to “donate”. Now I pay for a microblog without using it. haha, but that’s because it allows me to “donate” and use it as I test out my Indigenous micropub client.
{
"type": "entry",
"published": "2018-04-11T13:13:34-04:00",
"summary": "Same, I used to pay for crossposting without using it as a way to \u201cdonate\u201d. Now I pay for a microblog without using it. haha, but that\u2019s because it allows me to \u201cdonate\u201d and use it as I test out my Indigenous micropub client.",
"url": "https://eddiehinkle.com/2018/04/11/3/reply/",
"in-reply-to": [
"https://micro.blog/vincent/473105"
],
"content": {
"text": "Same, I used to pay for crossposting without using it as a way to \u201cdonate\u201d. Now I pay for a microblog without using it. haha, but that\u2019s because it allows me to \u201cdonate\u201d and use it as I test out my Indigenous micropub client.",
"html": "<p>Same, I used to pay for crossposting without using it as a way to \u201cdonate\u201d. Now I pay for a microblog without using it. haha, but that\u2019s because it allows me to \u201cdonate\u201d and use it as I test out my Indigenous micropub client.</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/vincent/473105": {
"type": "entry",
"url": "https://micro.blog/vincent/473105",
"name": "https://micro.blog/vincent/473105"
}
},
"_id": "215874",
"_source": "226",
"_is_read": true
}
{
"type": "entry",
"published": "2018-04-11T15:00:18+0000",
"url": "http://known.kevinmarks.com/2018/any-suggestions-for-somewhere-quiet-with-good",
"category": [
"indieweb"
],
"syndication": [
"https://twitter.com/kevinmarks/status/984083726454812672"
],
"content": {
"text": "Any suggestions for somewhere quiet with good connectivity in central London that I can use to be on TWiG tonight between 9pm and 11pm? #indieweb",
"html": "Any suggestions for somewhere quiet with good connectivity in central London that I can use to be on TWiG tonight between 9pm and 11pm? <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": "215603",
"_source": "205",
"_is_read": true
}
“Imagine, for example, requiring that any personal data you consent to share be offered back to you in an “interoperable” format, so that you could choose to work with companies… rather than being locked in to working with one of only a few.” https://www.nytimes.com/2018/04/09/opinion/zuckerberg-testify-congress.html#indieweb
{
"type": "entry",
"published": "2018-04-11T14:56:19+0000",
"url": "http://known.kevinmarks.com/2018/imagine-for-example-requiring-that-any-personal",
"category": [
"indieweb"
],
"syndication": [
"https://twitter.com/kevinmarks/status/984082728046870528"
],
"content": {
"text": "\u201cImagine, for example, requiring that any personal data you consent to share be offered back to you in an \u201cinteroperable\u201d format, so that you could choose to work with companies\u2026 rather than being locked in to working with one of only a few.\u201d https://www.nytimes.com/2018/04/09/opinion/zuckerberg-testify-congress.html #indieweb",
"html": "\u201cImagine, for example, requiring that any personal data you consent to share be offered back to you in an \u201cinteroperable\u201d format, so that you could choose to work with companies\u2026 rather than being locked in to working with one of only a few.\u201d <a href=\"https://www.nytimes.com/2018/04/09/opinion/zuckerberg-testify-congress.html\">https://www.nytimes.com/2018/04/09/opinion/zuckerberg-testify-congress.html</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": "215604",
"_source": "205",
"_is_read": true
}
When taking the decisions I have about leaving the major social networks over the past few years (LinkedIn, Instagram, Google+, Facebook, Twitter) and moving towards a more #indieweb online existence I am aware that I am placing myself within a certain community with certain ideals.
James Shelley's farewell to social media and Andrew Canion's post about replacing social media are two cases in point. They echo my thoughts but that's only to be expected, we gravitate towards the similar and gather in places like micro.blog, refuges from the abuses elsewhere.
However, we must not allow these refuges to become echo chambers like those we claim to abhor and have left behind.
I'm happy and comfortable with my position but have to be equally comfortable with the decisions of others, have to hear other opinions, and not close myself off saying that "this is the only way."
It's the way that works for me and that's all I can be certain of.
While James removed all the data from his Twitter and Facebook accounts (something I also did a while before finally deleting them) he has opted to retain them as "living directories" and a last ditch method of contacting people when no alternative exists. It's a clever use of the system - the utility without the futility - and always provides the option of a hassle free return should he want it, should things change for him.
Social networks provide a lot of good for a lot of people and this can't be dismissed out of hand even if some choose to demonise those very same networks.
We can educate and warn but we cannot, and should never try to, choose for others. We should not force our decisions or our reasons on them, for they are not us and have a different perspective.
{
"type": "entry",
"author": {
"name": "Colin Walker",
"url": "https://colinwalker.blog/",
"photo": null
},
"url": "https://colinwalker.blog/11-04-2018-1536/",
"published": "2018-04-11T15:37:32+00:00",
"content": {
"html": "<p>When taking the decisions I have about leaving the major social networks over the past few years (LinkedIn, Instagram, Google+, Facebook, Twitter) and moving towards a more <a href=\"https://colinwalker.blog/?s=%23indieweb\">#indieweb</a> online existence I am aware that I am placing myself within a certain community with certain ideals.</p>\n<p>James Shelley's <a href=\"https://jamesshelley.com/2018/04/10/farewell-social-media/\">farewell to social media</a> and Andrew Canion's post about <a href=\"http://www.andrewcanion.com/blog/2018/04/replacing-social-media/\">replacing social media</a> are two cases in point. They echo my thoughts but that's only to be expected, we gravitate towards the similar and gather in places like micro.blog, refuges from the abuses elsewhere.</p>\n<p>However, we must not allow these refuges to become echo chambers like those we claim to abhor and have left behind.</p>\n<p>I'm happy and comfortable with my position but have to be equally comfortable with the decisions of others, have to hear other opinions, and not close myself off saying that \"this is the <em>only</em> way.\"</p>\n<p>It's the way that works for me and that's all I can be certain of.</p>\n<p>While James removed all the data from his Twitter and Facebook accounts (something I also did a while before finally deleting them) he has opted to retain them as <em>\"living directories\"</em> and a last ditch method of contacting people when no alternative exists. It's a clever use of the system - the utility without the futility - and always provides the option of a hassle free return should he want it, should things change for him.</p>\n<p>Social networks provide a lot of good for a lot of people and this can't be dismissed out of hand even if some choose to demonise those very same networks.</p>\n<p>We can educate and warn but we cannot, and should never try to, <em>choose</em> for others. We should not force our decisions or our reasons on them, for they are not us and have a different perspective.</p>",
"text": "When taking the decisions I have about leaving the major social networks over the past few years (LinkedIn, Instagram, Google+, Facebook, Twitter) and moving towards a more #indieweb online existence I am aware that I am placing myself within a certain community with certain ideals.\nJames Shelley's farewell to social media and Andrew Canion's post about replacing social media are two cases in point. They echo my thoughts but that's only to be expected, we gravitate towards the similar and gather in places like micro.blog, refuges from the abuses elsewhere.\nHowever, we must not allow these refuges to become echo chambers like those we claim to abhor and have left behind.\nI'm happy and comfortable with my position but have to be equally comfortable with the decisions of others, have to hear other opinions, and not close myself off saying that \"this is the only way.\"\nIt's the way that works for me and that's all I can be certain of.\nWhile James removed all the data from his Twitter and Facebook accounts (something I also did a while before finally deleting them) he has opted to retain them as \"living directories\" and a last ditch method of contacting people when no alternative exists. It's a clever use of the system - the utility without the futility - and always provides the option of a hassle free return should he want it, should things change for him.\nSocial networks provide a lot of good for a lot of people and this can't be dismissed out of hand even if some choose to demonise those very same networks.\nWe can educate and warn but we cannot, and should never try to, choose for others. We should not force our decisions or our reasons on them, for they are not us and have a different perspective."
},
"_id": "215227",
"_source": "237",
"_is_read": true
}
{
"type": "entry",
"published": "2018-04-10T20:36:20-04:00",
"url": "https://martymcgui.re/2018/04/10/203620/",
"category": [
"HWC",
"IndieWeb",
"Baltimore",
"wrap-up"
],
"name": "HWC Baltimore 2018-04-10 Wrap-Up",
"content": {
"text": "Baltimore's first Homebrew Website Club of April met at the Digital Harbor Foundation Tech Center on April 10th\n \n\nHere are some notes from the \"broadcast\" portion of the meetup:\n\n martymcgui.re \u2013 Demoed an as-yet-unnamed (maybe: kapowski) \"GIF Reaction\" Micropub client. It's currently available on Glitch. It supports IndieAuth, searching for GIFs via the GIPHY API, then posting those as the \"photo\" property in a Micropub form-encoded request. It also supports in-reply-to functionality, putting the \"reaction\" into \"GIF Reaction\", though there's no UI for that, yet. He made an example reply post, but Jonathan's post doesn't seem to support photo replies. \ud83e\udd14\u00a0Also fixed up some metacrap\u00a0for his podcast site\u00a0so sharing looks better on Facebook and Twitter.\n \n\nScreenshot of WIP GIF Reaction Micropub client: https://media.martymcgui.re/dd/90/63/8e/3b33fed912921234eba191af86bb0a358169b7249006b89416b9c238.png\n\n\n rhearamakrishnan.com\u00a0\u2013 Working on a redesign of her site. Making good use of view-source on sites that she likes for inspiration. Working on a mixed media art project with post cards that direct you to a website that contains coordinates to a geo cache containing an actual letter.\n \n\njonathanprozzi.net \u2013 Been doing lots of work stuff that overlaps with personal web interests. Working on his wedding page. It's now up on Netlify\u00a0and\u00a0uses their form collection for RSVPs.\nOther discussion:\n\n The new Killer Queen 5 vs 5 arcade game recently installed in Baltimore at Holy Frijoles.\n \n\n Baltimore zine culture (apparently Atomic Books\u00a0considers carrying local zines).\n \nTwine\u00a0for creating interactive poetry and fiction. It outputs a bunch of HTML and CSS (and maybe JS) that can be hosted anywhere.\n The Netlify static site model of separating content management, storage, layout and rendering, and file hosting.\n The difficulty in evaluating \"frameworks\" like React and Vue based on their low-level merits. Looking at community and availability of higher-level components might help more.\n!! Photo Goes Here !! https://media.martymcgui.re/81/68/f6/b5/0495a3da8bee64886ba66ce2278fe4d2d245a2614e8c9531c1fc2de7.jpg\n\n\n Thanks to everybody who came out! We hope to see you all again at our next meeting!",
"html": "<p>\n Baltimore's <a href=\"https://martymcgui.re/2018/04/02/161711/\">first Homebrew Website Club of April</a> met at the <a href=\"https://www.digitalharbor.org/\">Digital Harbor Foundation Tech Center</a> on April 10th\n <br /></p>\n<p>Here are some notes from the \"broadcast\" portion of the meetup:</p>\n<p>\n <a href=\"https://martymcgui.re/\">martymcgui.re</a> \u2013 Demoed an as-yet-unnamed (maybe: kapowski) \"GIF Reaction\" Micropub client. It's <a href=\"https://glitch.com/edit/#!/garrulous-smile\">currently available on Glitch</a>. It supports <a href=\"https://indieweb.org/IndieAuth\">IndieAuth</a>, searching for GIFs via the <a href=\"https://developers.giphy.com/\">GIPHY API</a>, then posting those as the \"photo\" property in a <a href=\"https://indieweb.org/Micropub\">Micropub</a> form-encoded request. It also supports <a href=\"https://indieweb.org/in-reply-to\">in-reply-to</a> functionality, putting the \"reaction\" into \"GIF Reaction\", though there's no UI for that, yet. He made an <a href=\"https://martymcgui.re/2018/04/10/193815/\">example reply post</a>, but <a href=\"https://jonathanprozzi.net/indieweb/hwc-2018-03-07-wrap-up/#comment-439\">Jonathan's post</a> doesn't seem to support <a href=\"https://indieweb.org/photo_reply\">photo replies</a>. \ud83e\udd14\u00a0Also fixed up some <a href=\"https://indieweb.org/metacrap\">metacrap</a>\u00a0for his <a href=\"https://wehavetoask.com/\">podcast site</a>\u00a0so sharing looks better on Facebook and Twitter.\n <br /></p>\n<p>Screenshot of WIP GIF Reaction Micropub client: https://media.martymcgui.re/dd/90/63/8e/3b33fed912921234eba191af86bb0a358169b7249006b89416b9c238.png</p>\n<p></p>\n<p>\n <a href=\"http://rhearamakrishnan.com/\">rhearamakrishnan.com</a>\u00a0\u2013 Working on a redesign of her site. Making good use of view-source on sites that she likes for inspiration. Working on a mixed media art project with post cards that direct you to a website that contains coordinates to a geo cache containing an actual letter.\n <br /></p>\n<p><a href=\"https://jonathanprozzi.net/\">jonathanprozzi.net</a> \u2013 Been doing lots of work stuff that overlaps with personal web interests. Working on his wedding page. It's now up on <a href=\"https://www.netlify.com/\">Netlify</a>\u00a0and\u00a0uses their form collection for RSVPs.</p>\n<p>Other discussion:</p>\n<ul><li>\n The new <a href=\"http://killerqueenarcade.com/\">Killer Queen</a> 5 vs 5 arcade game recently installed in Baltimore at <a href=\"https://www.holyfrijoles.net/\">Holy Frijoles</a>.\n <br /></li>\n <li>Baltimore zine culture (apparently <a href=\"https://atomicbooks.com/\">Atomic Books</a>\u00a0considers carrying local zines).</li>\n <li>\n<a href=\"https://twinery.org/\">Twine</a>\u00a0for creating interactive poetry and fiction. It outputs a bunch of HTML and CSS (and maybe JS) that can be hosted anywhere.</li>\n <li>The Netlify static site model of separating content management, storage, layout and rendering, and file hosting.</li>\n <li>The difficulty in evaluating \"frameworks\" like React and Vue based on their low-level merits. Looking at community and availability of higher-level components might help more.</li>\n</ul><p>!! Photo Goes Here !! https://media.martymcgui.re/81/68/f6/b5/0495a3da8bee64886ba66ce2278fe4d2d245a2614e8c9531c1fc2de7.jpg</p>\n<p></p>\n<p>\n Thanks to everybody who came out! We hope to see you all again at our next meeting!\n <br /></p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://aperture-media.p3k.io/martymcgui.re/4f9fac2b9e3ae62998c557418143efe288bca8170a119921a9c6bfeb0a1263a2.jpg"
},
"_id": "213112",
"_source": "175",
"_is_read": true
}
I have an in-progress PW3 branch that should work, though I haven’t tested it in a while. If you try it out, please let me know any issues you run into. In the coming months I should be able to get an official release out.
{
"type": "entry",
"published": "2018-04-09 23:03-0700",
"url": "https://gregorlove.com/2018/04/i-have-an-in-progress-pw3/",
"syndication": [
"https://twitter.com/gRegorLove/status/983586453748842496"
],
"in-reply-to": [
"https://twitter.com/thorkon/status/983585164336001024"
],
"content": {
"text": "I have an in-progress PW3 branch that should work, though I haven\u2019t tested it in a while. If you try it out, please let me know any issues you run into. In the coming months I should be able to get an official release out.\n\nhttps://github.com/gRegorLove/ProcessWire-Webmention/tree/master-pw3",
"html": "<p>I have an in-progress PW3 branch that should work, though I haven\u2019t tested it in a while. If you try it out, please let me know any issues you run into. In the coming months I should be able to get an official release out.\n</p>\n<p><a href=\"https://github.com/gRegorLove/ProcessWire-Webmention/tree/master-pw3\">https://github.com/gRegorLove/ProcessWire-Webmention/tree/master-pw3</a></p>"
},
"author": {
"type": "card",
"name": "gRegor Morrill",
"url": "https://gregorlove.com/",
"photo": "https://aperture-media.p3k.io/gregorlove.com/1dfe16005864a9fc9564a3884378cdc89abd66b173ed10bce2ac60ed782dab01.jpg"
},
"refs": {
"https://twitter.com/thorkon/status/983585164336001024": {
"type": "entry",
"url": "https://twitter.com/thorkon/status/983585164336001024",
"content": {
"text": "Dear @gRegorLove - is there any ProcessWire webmentions Modul/Plugin working on the current pw version 3.0.98 ?"
},
"author": {
"type": "card",
"name": "Thorsten",
"url": "http://www.thorsten-konigorski.de/",
"photo": "https://gregorlove.com/site/assets/files/3540/da26db2b13b11c44ea697cf00a37b4c9e42583b0c5597a52e2bf336aa57b768d.jpg"
}
}
},
"_id": "209688",
"_source": "95",
"_is_read": true
}
Yep, microformats are alive and well; used a lot in the #indieweb community. If you’re adding them to new content, I’d recommend checking out microformats2 h-card. Easier markup and parsers are backwards compatible.
{
"type": "entry",
"published": "2018-04-09 14:54-0700",
"url": "https://gregorlove.com/2018/04/yep-microformats-are-alive-and/",
"syndication": [
"https://twitter.com/gRegorLove/status/983464131570360321"
],
"in-reply-to": [
"https://twitter.com/stetsonthree/status/983458703344111617"
],
"content": {
"text": "Yep, microformats are alive and well; used a lot in the #indieweb community. If you\u2019re adding them to new content, I\u2019d recommend checking out microformats2 h-card. Easier markup and parsers are backwards compatible.\n\nhttp://microformats.org/wiki/h-card",
"html": "<p>Yep, microformats are alive and well; used a lot in the #indieweb community. If you\u2019re adding them to new content, I\u2019d recommend checking out microformats2 h-card. Easier markup and parsers are backwards compatible.</p>\n\n<p><a href=\"http://microformats.org/wiki/h-card\">http://microformats.org/wiki/h-card</a></p>"
},
"author": {
"type": "card",
"name": "gRegor Morrill",
"url": "https://gregorlove.com/",
"photo": "https://aperture-media.p3k.io/gregorlove.com/1dfe16005864a9fc9564a3884378cdc89abd66b173ed10bce2ac60ed782dab01.jpg"
},
"refs": {
"https://twitter.com/stetsonthree/status/983458703344111617": {
"type": "entry",
"url": "https://twitter.com/stetsonthree/status/983458703344111617",
"content": {
"text": "In the end I did not go this route. I instead used the hCard microformat. Are people still using microformats? http://microformats.org/wiki/hcard"
},
"author": {
"type": "card",
"name": "Lee Stetson",
"url": "http://stetsonthree.com",
"photo": "https://gregorlove.com/site/assets/files/3540/5778236ce0b78656650a899f4409734bc397b1c54bb2cd8367586f9e0b86be8b.jpg"
}
}
},
"_id": "208755",
"_source": "95",
"_is_read": true
}
I know you have a micro.blog, I have really been enjoying micro.blog and it echoes what you describe here. I use it for 90% of my social net interactions and it’s great! Also, I’ve been using #microsub (https://indieweb.org/Microsub) to emulate feed based networking
{
"type": "entry",
"published": "2018-04-09T10:31:51-04:00",
"summary": "I know you have a micro.blog, I have really been enjoying micro.blog and it echoes what you describe here. I use it for 90% of my social net interactions and it\u2019s great! Also, I\u2019ve been using #microsub (https://indieweb.org/Microsub) to emulate feed based networking",
"url": "https://eddiehinkle.com/2018/04/09/4/reply/",
"category": [
"indieweb",
"microsub"
],
"in-reply-to": [
"https://twitter.com/davidmead/status/983300977745948672"
],
"content": {
"text": "I know you have a micro.blog, I have really been enjoying micro.blog and it echoes what you describe here. I use it for 90% of my social net interactions and it\u2019s great! Also, I\u2019ve been using #microsub (https://indieweb.org/Microsub) to emulate feed based networking",
"html": "<p>I know you have a micro.blog, I have really been enjoying micro.blog and it echoes what you describe here. I use it for 90% of my social net interactions and it\u2019s great! Also, I\u2019ve been using <a href=\"https://eddiehinkle.com/tag/microsub/\">#microsub</a> (https://indieweb.org/Microsub) to emulate feed based networking</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/davidmead/status/983300977745948672": {
"type": "entry",
"url": "https://twitter.com/davidmead/status/983300977745948672",
"name": "https://twitter.com/davidmead/status/983300977745948672"
}
},
"_id": "207558",
"_source": "226",
"_is_read": true
}
{
"type": "entry",
"published": "2018-04-09T09:12:03-07:00",
"url": "https://aaronparecki.com/2018/04/09/5/",
"category": [
"micropub",
"indieweb",
"xmlrpc",
"metaweblog"
],
"name": "A MetaWeblog to Micropub Gateway",
"content": {
"text": "I\u2019m always looking for fun and better ways to publish content to my website. There are several nice writing apps now, such as Byword for MacOS, which lets you write in Markdown and then converts it into HTML. Many of these kinds of apps have an option to publish to a Wordpress site, using Wordpress\u2019 XML-RPC interface, which is more or less the MetaWeblog API. \n\nI thought it would be a fun experiment to try to set up my website to handle those XML-RPC calls so that I can use these apps, at least until they support Micropub natively.\n\nProblems with XML-RPC\n\nAs with most XML formats, XML-RPC is ridiculously verbose for what it\u2019s doing. In order to send a single string value, it requires wrapping it in a surprising amount of XML:\n\n<param>\n<value><string>aaronparecki.com</string></value>\n</param>\n\n\nThe MetaWeblog API also requires that you give apps your Wordpress password, which has been a known anti-pattern for a long time. With things like OAuth, we have better ways of authenticating against APIs without sending passwords around.\n\nMicropub Bridge\n\nTo avoid needing to add actual XML-RPC support to my website, I set up a bridge that translates XML-RPC calls to their equivalent Micropub calls. The bridge also obtains an IndieAuth access token so that I can use a token instead of entering my password into these apps.\n\nI didn\u2019t bother adding any styling to the gateway since it\u2019s something you\u2019d only interact with once to set up, so apologies for the ugly screenshots that follow.\n\nHere\u2019s what it looks like to connect Byword to be able to publish to my website.\n\nFirst I visit the gateway and log in.\n\nThat does the IndieAuth discovery and takes me to my website where I grant it access.\n\nThen I\u2019m redirected back to the gateway which provides instructions on what to do next.\n\nThe key to making Byword find the XML-RPC API is adding that EditURI tag to my website. Then I can go into Byword and add a new Wordpress site, entering my domain name.\n\nIt then asks for my username and password, which I enter by copying from the gateway.\n\nThen Byword is all set and thinks it\u2019s talking to a Wordpress site!\n\nNow when I\u2019m ready to publish this post, I click the \u201cPublish\u201d button in Byword, and fill in the title and tags.\n\nOpen Source\n\nIf you\u2019d like to try this out, head to xmlrpc.p3k.io and connect your website!\n\nThe source code is available on GitHub.\n\nI\u2019ve only implemented the one newPost method that Byword uses when talking to the XML-RPC API. I\u2019ve only tested this with Byword, so it\u2019s very likely that other apps might be expecting more of the API to be implemented. Feel free to file issues if you have trouble using other apps! Eventually I\u2019d like to implement more of the MetaWeblog API in this gateway, even if I really don\u2019t like writing XML-RPC code!",
"html": "<p>I\u2019m always looking for fun and better ways to publish content to my website. There are several nice writing apps now, such as <a href=\"https://indieweb.org/Byword\">Byword</a> for MacOS, which lets you write in Markdown and then converts it into HTML. Many of these kinds of apps have an option to publish to a Wordpress site, using Wordpress\u2019 XML-RPC interface, which is more or less the MetaWeblog API. </p>\n\n<p>I thought it would be a fun experiment to try to set up my website to handle those XML-RPC calls so that I can use these apps, at least until they support Micropub natively.</p>\n\n<h3>Problems with XML-RPC</h3>\n\n<p>As with most XML formats, XML-RPC is ridiculously verbose for what it\u2019s doing. In order to send a single string value, it requires wrapping it in a surprising amount of XML:</p>\n\n<pre><code><param>\n<value><string>aaronparecki.com</string></value>\n</param>\n</code></pre>\n\n<p>The MetaWeblog API also requires that you give apps your Wordpress password, which has been a known anti-pattern for a long time. With things like OAuth, we have better ways of authenticating against APIs without sending passwords around.</p>\n\n<h3>Micropub Bridge</h3>\n\n<p>To avoid needing to add actual XML-RPC support to my website, I set up a bridge that translates XML-RPC calls to their equivalent Micropub calls. The bridge also obtains an IndieAuth access token so that I can use a token instead of entering my password into these apps.</p>\n\n<p>I didn\u2019t bother adding any styling to the gateway since it\u2019s something you\u2019d only interact with once to set up, so apologies for the ugly screenshots that follow.</p>\n\n<p>Here\u2019s what it looks like to connect Byword to be able to publish to my website.</p>\n\n<p>First I visit the gateway and log in.</p>\n\n<img src=\"https://aperture-media.p3k.io/aaronparecki.com/aaaf5c4686ab2cd5c27099923b778250f2d571147963e973d23149c4a5a3cd9c.jpg\" alt=\"\" /><p>That does the IndieAuth discovery and takes me to my website where I grant it access.</p>\n\n<img src=\"https://aperture-media.p3k.io/aaronparecki.com/f11ad070dbc457681111c8ce94d5d50a848b65fa5ed94f6f2ffa222f81d0fabb.jpg\" alt=\"\" /><p>Then I\u2019m redirected back to the gateway which provides instructions on what to do next.</p>\n\n<img src=\"https://aperture-media.p3k.io/aaronparecki.com/19297434abe808970f798340ff82de026e988f8eb9ffbc60b68415c19872fc5e.jpg\" alt=\"\" /><p>The key to making Byword find the XML-RPC API is adding that <code>EditURI</code> tag to my website. Then I can go into Byword and add a new Wordpress site, entering my domain name.</p>\n\n<img src=\"https://aperture-media.p3k.io/aaronparecki.com/a07b05126097ff2b07497484efe37658f98bf3def7b8c2913145fef300588653.png\" alt=\"\" /><p>It then asks for my username and password, which I enter by copying from the gateway.</p>\n\n<img src=\"https://aperture-media.p3k.io/aaronparecki.com/97a5fd1981213dc075b708dc049600efc1a8ba2af58e11e45381fed52b47674d.png\" alt=\"\" /><p>Then Byword is all set and thinks it\u2019s talking to a Wordpress site!</p>\n\n<img src=\"https://aperture-media.p3k.io/aaronparecki.com/d727ab16320b89885889f803943824e4e2379bd432795e432588e4bf45fd29a8.png\" alt=\"\" /><p>Now when I\u2019m ready to publish this post, I click the \u201cPublish\u201d button in Byword, and fill in the title and tags.</p>\n\n<img src=\"https://aperture-media.p3k.io/aaronparecki.com/f0da0ba9609980b2db47bc0529119702e76d458c59b3aa45a91fc3215e780509.jpg\" alt=\"\" /><img src=\"https://aperture-media.p3k.io/aaronparecki.com/71118c1add08111f1933e9211ae1c8fb536c71469bddd524ac74af158041acb2.jpg\" alt=\"\" /><h3>Open Source</h3>\n\n<p>If you\u2019d like to try this out, head to <a href=\"https://xmlrpc.p3k.io\">xmlrpc.p3k.io</a> and connect your website!</p>\n\n<p>The source code is available <a href=\"https://github.com/aaronpk/xmlrpc-micropub-bridge\">on GitHub</a>.</p>\n\n<p>I\u2019ve only implemented the one <code>newPost</code> method that Byword uses when talking to the XML-RPC API. I\u2019ve only tested this with Byword, so it\u2019s very likely that other apps might be expecting more of the API to be implemented. Feel free to file issues if you have trouble using other apps! Eventually I\u2019d like to implement more of the MetaWeblog API in this gateway, even if I really don\u2019t like writing XML-RPC code!</p>"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/2b8e1668dcd9cfa6a170b3724df740695f73a15c2a825962fd0a0967ec11ecdc.jpg"
},
"_id": "206539",
"_source": "16",
"_is_read": true
}
Reading http://apps-of-a-feather.com/ makes me long for a “social network” showing 1st 140 chars of blog posts using #RSS and #Indieweb.
{
"type": "entry",
"url": "http://davidjohnmead.com/blog/2018/04/09/19713/",
"syndication": [
"https://twitter.com/davidmead/status/983300977745948672"
],
"content": {
"text": "Reading http://apps-of-a-feather.com/ makes me long for a \u201csocial network\u201d showing 1st 140 chars of blog posts using #RSS and #Indieweb.",
"html": "Reading <a class=\"u-url\" href=\"http://apps-of-a-feather.com/\">http://apps-of-a-feather.com/</a> makes me long for a \u201csocial network\u201d showing 1st 140 chars of blog posts using <abbr title=\"Rich Site Summary\">#RSS</abbr> and #Indieweb."
},
"_id": "205616",
"_source": "194",
"_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/8797520",
"published": "2018-04-08T21:26:11+00:00",
"content": {
"html": "<a href=\"https://david.shanske.com/2018/04/07/indieauth-for-wordpress/\">IndieAuth for WordPress</a> by <a href=\"https://david.shanske.com/\"><img src=\"https://secure.gravatar.com/avatar/681eba02e72ba1d894097034a8110e61?s=125&d=default&r=g\" alt=\"IndieAuth %name\" title=\"IndieAuth\" />David Shanske</a><em> (David Shanske)</em>\n<blockquote>OAuth is already being used by a variety of services\u2026Login with Facebook or Login with Google options on sites are usually OAuth based. The difference is that for IndieAuth, users and clients are all represented by URLs.<br />Authorization Prompt for Indieauth for WordPress\nSo, why did I want to build one? A few reasons. The most popular use for a IndieAuth server as authentication for Micropub clients. Micropub is a standard for creating posts using third-party clients.</blockquote>\n\n\n<p>The post <a href=\"https://islandinthenet.com/indieauth/\"><span class='p-name'>IndieAuth</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": "IndieAuth for WordPress by David Shanske (David Shanske)\nOAuth is already being used by a variety of services\u2026Login with Facebook or Login with Google options on sites are usually OAuth based. The difference is that for IndieAuth, users and clients are all represented by URLs.\nAuthorization Prompt for Indieauth for WordPress\nSo, why did I want to build one? A few reasons. The most popular use for a IndieAuth server as authentication for Micropub clients. Micropub is a standard for creating posts using third-party clients.\n\n\nThe post <span class='p-name'>IndieAuth</span> by <span class='p-author h-card'>Kh\u00fcrt Williams</span> appeared first on Island in the Net."
},
"name": "IndieAuth",
"_id": "204345",
"_source": "242",
"_is_read": true
}
{
"type": "entry",
"published": "2018-04-08T02:11:15+00:00",
"url": "http://stream.boffosocko.com/2018/spigot-ive-sent-you-a-few-webmentions-directly-from-my",
"syndication": [
"https://twitter.com/ChrisAldrich/status/982803035863879680"
],
"in-reply-to": [
"https://twitter.com/spigot/status/981957032537305088"
],
"content": {
"text": "@spigot I've sent you a few webmentions directly from my site. Be sure to check that they're not getting caught in your spam filter. See also: https://indieweb.org/WordPress_with_Bridgy#Spam",
"html": "<a href=\"https://twitter.com/spigot\">@spigot</a> I've sent you a few webmentions directly from my site. Be sure to check that they're not getting caught in your spam filter. See also: <a href=\"https://indieweb.org/WordPress_with_Bridgy#Spam\">https://indieweb.org/WordPress_with_Bridgy#Spam</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "https://aperture-media.p3k.io/stream.boffosocko.com/d0ba9f65fcbf0cef3bdbcccc0b6a1f42b1310f7ab2e07208c7a396166cde26b1.jpg"
},
"_id": "202580",
"_source": "192",
"_is_read": true
}
{
"type": "entry",
"published": "2018-04-07T23:13:02-04:00",
"url": "https://david.shanske.com/2018/04/07/indieauth-for-wordpress/",
"syndication": [
"https://www.facebook.com/100002356503167/posts/1657224977699370",
"https://twitter.com/dshanske/status/982818602951856129"
],
"name": "IndieAuth for WordPress",
"content": {
"text": "Part of my own project for this week, while taking off for the holiday, was to complete work on an Indieauth endpoint for WordPress.\nIndieAuth is layer on top of OAuth 2.0, a standard that grants websites or applications access to their information on other websites but without providing passwords.\nOAuth is already being used by a variety of services\u2026Login with Facebook or Login with Google options on sites are usually OAuth based. The difference is that for IndieAuth, users and clients are all represented by URLs.\nAuthorization Prompt for Indieauth for WordPressSo, why did I want to build one? A few reasons. The most popular use for a IndieAuth server as authentication for Micropub clients. Micropub is a standard for creating posts using third-party clients.\nWordPress is moving toward deprecating their post interface in favor of a totally new one called \u2018Gutenberg\u2019. As a long time WordPress user, the focus on this concerns me as it does not necessarily represent my needs or desires as a user of the platform. So, I want to have options.\nCurrently, OAuth servers for WordPress of all types are limited. The REST API, which was heralded with much optimism, lacks an OAuth authentication method. In fact, it lacks any built-in authentication options other than the WordPress login for external authentication.\nThere is an incomplete project for an OAuth2 server for WordPress I did get some useful ideas from, however. I also have to thank Aaron Parecki, who wrote a book on OAuth2 and wrote the Indieauth specification, for reviewing my work and giving lots of feedback.\nWhat I\u2019ve built, with help, is a working IndieAuth authentication method that works for the REST API, among other things.\nSince I wanted this to be widely adoptable, I needed to make sure of a secure implementation, and I think the results are a good initial version. There is an opportunity for further refinements and improvements, but it means that WordPress users are no longer dependent on Indieauth.com, the reference implementation of the spec which uses OAuth providers like Github and Twitter to authenticate.\nThis leads to my hopes for the future. There are people working on Micropub clients for Android. And if any of them pans out, or my own mobile options, I could easily post notes to my site from wherever I am using tools that are much more flexible to my needs than are available now, the culmination of nearly 4 years of moving toward this point, on and off.\nThe success for me will be able to read something on my phone, and quickly share that to my site. Or have a thought and quickly share it to my site, without having to spend so much time setting it up I think better of it.\nThere are still pieces that need work to achieve that, but this is a major piece knocked off.",
"html": "Part of my own project for this week, while taking off for the holiday, was to complete work on an Indieauth endpoint for WordPress.\n<p><a href=\"https://indieauth.net/\">IndieAuth</a> is layer on top of OAuth 2.0, a standard that grants websites or applications access to their information on other websites but without providing passwords.</p>\n<p>OAuth is already being used by a variety of services\u2026Login with Facebook or Login with Google options on sites are usually OAuth based. The difference is that for IndieAuth, users and clients are all represented by URLs.</p>\n<a href=\"https://aperture-media.p3k.io/david.shanske.com/f5f33ed009e89a475cae151c7369032987a11edad4b36c3de1faf28aee4b5a5c.png\"><img src=\"https://aperture-media.p3k.io/david.shanske.com/f5f33ed009e89a475cae151c7369032987a11edad4b36c3de1faf28aee4b5a5c.png\" alt=\"\" width=\"409\" height=\"639\" /></a>Authorization Prompt for Indieauth for WordPress<p>So, why did I want to build one? A few reasons. The most popular use for a IndieAuth server as authentication for <a href=\"http://micropub.net\">Micropub</a> clients. Micropub is a standard for creating posts using third-party clients.</p>\n<p>WordPress is moving toward deprecating their post interface in favor of a totally new one called \u2018Gutenberg\u2019. As a long time WordPress user, the focus on this concerns me as it does not necessarily represent my needs or desires as a user of the platform. So, I want to have options.</p>\n<p>Currently, OAuth servers for WordPress of all types are limited. The REST API, which was heralded with much optimism, lacks an OAuth authentication method. In fact, it lacks any built-in authentication options other than the WordPress login for external authentication.</p>\n<p>There is an incomplete project for an OAuth2 server for WordPress I did get some useful ideas from, however. I also have to thank <a href=\"https://aaronparecki.com\">Aaron Parecki</a>, who wrote a <a href=\"https://oauth2simplified.com/\">book</a> on OAuth2 and wrote the Indieauth specification, for reviewing my work and giving lots of feedback.</p>\n<p>What I\u2019ve built, with help, is a working IndieAuth authentication method that works for the REST API, among other things.</p>\n<p>Since I wanted this to be widely adoptable, I needed to make sure of a secure implementation, and I think the results are a good initial version. There is an opportunity for further refinements and improvements, but it means that WordPress users are no longer dependent on Indieauth.com, the reference implementation of the spec which uses OAuth providers like Github and Twitter to authenticate.</p>\n<p>This leads to my hopes for the future. There are people working on Micropub clients for Android. And if any of them pans out, or my own mobile options, I could easily post notes to my site from wherever I am using tools that are much more flexible to my needs than are available now, the culmination of nearly 4 years of moving toward this point, on and off.</p>\n<p>The success for me will be able to read something on my phone, and quickly share that to my site. Or have a thought and quickly share it to my site, without having to spend so much time setting it up I think better of it.</p>\n<p>There are still pieces that need work to achieve that, but this is a major piece knocked off.</p>"
},
"author": {
"type": "card",
"name": "David Shanske",
"url": "https://david.shanske.com",
"photo": "https://aperture-media.p3k.io/secure.gravatar.com/4c37695e8bc2b8287b49521997dbe3d2676261abef57c487165515696087b2e2.png"
},
"_id": "202668",
"_source": "5",
"_is_read": true
}
{
"type": "entry",
"published": "2018-04-07T19:12:18-04:00",
"url": "https://martymcgui.re/2018/04/07/191218/",
"category": [
"podcast",
"IndieWeb",
"this-week-indieweb-podcast"
],
"audio": [
"https://aperture-media.p3k.io/media.martymcgui.re/f96b17de680457f42e1c6f8c86352dc0a472dc20e6bd751603ef121cdaa7bc40.mp3"
],
"syndication": [
"https://huffduffer.com/schmarty/470067",
"https://twitter.com/schmarty/status/982758806420672512",
"https://www.facebook.com/marty.mcguire.54/posts/10211802288234626"
],
"name": "This Week in the IndieWeb Audio Edition \u2022 March 31st - April 6th, 2018",
"content": {
"text": "Show/Hide Transcript \n \n IndieWeb for Drupal, IndieWeb for Businesses, and Foodspotting going under. It\u2019s the audio edition for This Week in the IndieWeb for March 31st - April 6th, 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>IndieWeb for Drupal, IndieWeb for Businesses, and Foodspotting going under. It\u2019s the audio edition for <a href=\"https://indieweb.org/this-week/2018-04-06.html\">This Week in the IndieWeb for March 31st - April 6th, 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": "202539",
"_source": "175",
"_is_read": true
}
