Add support for destination configuration. From a UI perspective, posting to multiple micropub endpoint versus posting to a single micropub endpoint with multiple destinations should be the same.
https://github.com/indieweb/micropub-extensions/issues/3
The one part to think about is defaults. How should I default the destination? Should it be the first destination in the list or the last destination used? I currently allow someone to set a default Micropub Endpoint, but a default Destination is different. Maybe that’s the answer, maybe if they have more than one destination, I need to allow an option to choose a default destination on the micropub endpoint settings page.
{
"type": "entry",
"published": "2018-02-20T16:47:31-05:00",
"summary": "Add support for destination configuration. From a UI perspective, posting to multiple micropub endpoint versus posting to a single micropub endpoint with multiple destinations should be the same. \n\nhttps://github.com/indieweb/micropub-extensions/issues/3 \n\nThe one part to think about is defaults. How should I default the destination? Should it be the first destination in the list or the last destination used? I currently allow someone to set a default Micropub Endpoint, but a default Destination is different. Maybe that\u2019s the answer, maybe if they have more than one destination, I need to allow an option to choose a default destination on the micropub endpoint settings page.",
"url": "https://eddiehinkle.com/2018/02/20/12/reply/",
"category": [
"indieweb",
"indigenous"
],
"in-reply-to": [
"https://github.com/EdwardHinkle/indigenous-ios"
],
"name": "Add support for mp q=config destination",
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com",
"photo": null
},
"refs": {
"https://github.com/EdwardHinkle/indigenous-ios": {
"type": "entry",
"url": "https://github.com/EdwardHinkle/indigenous-ios",
"name": "https://github.com/EdwardHinkle/indigenous-ios"
}
},
"_id": "67356",
"_source": "39",
"_is_read": true
}
Just created a Lambda function that looks at my website's On This Day page, and publishes the memories to a special channel in my Microsub server. #IndieWeb #OwnYourMemories
{
"type": "entry",
"published": "2018-02-19T01:44:38+00:00",
"url": "https://cleverdevil.io/2018/just-created-a-lambda-function-that-looks",
"category": [
"IndieWeb",
"OwnYourMemories"
],
"syndication": [
"https://twitter.com/cleverdevil/status/965401712012951552"
],
"content": {
"text": "Just created a Lambda function that looks at my website's On This Day page, and publishes the memories to a special channel in my Microsub server. #IndieWeb #OwnYourMemories",
"html": "Just created a Lambda function that looks at my website's On This Day page, and publishes the memories to a special channel in my Microsub server. <a href=\"https://cleverdevil.io/tag/IndieWeb\" class=\"p-category\">#IndieWeb</a> <a href=\"https://cleverdevil.io/tag/OwnYourMemories\" class=\"p-category\">#OwnYourMemories</a>"
},
"author": {
"type": "card",
"name": "Jonathan LaCour",
"url": "https://cleverdevil.io/profile/cleverdevil",
"photo": "https://cleverdevil.io/file/fdbc7696a5f73864ea11a828c861e138/thumb.jpg"
},
"_id": "60711",
"_source": "71",
"_is_read": true
}
{
"type": "entry",
"published": "2018-02-17T18:37:22+00:00",
"url": "https://cleverdevil.io/2018/marcus-povey-on-twitter-pushed-a-bunch-of-withknown-changes",
"like-of": [
"https://twitter.com/mapkyca/status/964919106372882433"
],
"name": "Marcus Povey on Twitter: \"Pushed a bunch of @withknown changes: translation hooks for templates, PHP 7.2 compatibility, refresh/remove option for link previews, a couple of bug fixes, and Gettext support. #indieweb #known\"",
"author": {
"type": "card",
"name": "Jonathan LaCour",
"url": "https://cleverdevil.io/profile/cleverdevil",
"photo": "https://cleverdevil.io/file/fdbc7696a5f73864ea11a828c861e138/thumb.jpg"
},
"_id": "56924",
"_source": "71",
"_is_read": true
}
Maybe I’m weird, but it just feels good. It feels good to reclaim my turf. It feels good to have a spot to think out loud in public where people aren’t spitting and shitting all over the place.
{
"type": "entry",
"published": "2018-02-17T06:03:17Z",
"url": "https://adactio.com/links/13455",
"category": [
"indieweb",
"personal",
"publishing",
"blogging",
"writing",
"sharing",
"frequency",
"flow",
"stock"
],
"bookmark-of": [
"https://austinkleon.com/2017/11/20/a-few-notes-on-daily-blogging/"
],
"content": {
"text": "A few notes on daily blogging\n\n\n\n\n Maybe I\u2019m weird, but it just feels good. It feels good to reclaim my turf. It feels good to have a spot to think out loud in public where people aren\u2019t spitting and shitting all over the place.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://austinkleon.com/2017/11/20/a-few-notes-on-daily-blogging/\">\nA few notes on daily blogging\n</a>\n</h3>\n\n<blockquote>\n <p>Maybe I\u2019m weird, but it just <em>feels</em> good. It feels good to reclaim my turf. It feels good to have a spot to think out loud in public where people aren\u2019t spitting and shitting all over the place.</p>\n</blockquote>"
},
"_id": "56356",
"_source": "2",
"_is_read": true
}
@wimleers @Google @drupal @timmillwood I remember doing an #IndieWeb presentation at DrupalCamp LA a couple of years ago right after a Piwik (@matomo_org) talk and it seemed like an interesting #ownyourdata solution at the time.
https://www.drupal.org/project/piwik
{
"type": "entry",
"published": "2018-02-17T01:28:35+00:00",
"url": "http://stream.boffosocko.com/2018/wimleers-google-drupal-timmillwood-i-remember-doing-an-indieweb-presentation",
"category": [
"IndieWeb",
"ownyourdata"
],
"syndication": [
"https://twitter.com/ChrisAldrich/status/964672909187969026"
],
"in-reply-to": [
"https://twitter.com/wimleers/status/964668303896662023"
],
"content": {
"text": "@wimleers @Google @drupal @timmillwood I remember doing an #IndieWeb presentation at DrupalCamp LA a couple of years ago right after a Piwik (@matomo_org) talk and it seemed like an interesting #ownyourdata solution at the time.\nhttps://www.drupal.org/project/piwik",
"html": "<a href=\"https://twitter.com/wimleers\">@wimleers</a> <a href=\"https://twitter.com/Google\">@Google</a> <a href=\"https://twitter.com/drupal\">@drupal</a> <a href=\"https://twitter.com/timmillwood\">@timmillwood</a> I remember doing an <a href=\"http://stream.boffosocko.com/tag/IndieWeb\" class=\"p-category\">#IndieWeb</a> presentation at DrupalCamp LA a couple of years ago right after a Piwik (@matomo_org) talk and it seemed like an interesting <a href=\"http://stream.boffosocko.com/tag/ownyourdata\" class=\"p-category\">#ownyourdata</a> solution at the time.<br /><a href=\"https://www.drupal.org/project/piwik\">https://www.drupal.org/project/piwik</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
},
"_id": "99798",
"_source": "192",
"_is_read": true
}
@Dries How awesome would it be if I could use @buffer not only to post to social media, but to post to my own website using the Micropub spec? https://www.w3.org/TR/micropub/
{
"type": "entry",
"published": "2018-02-16T22:02:31+00:00",
"url": "http://stream.boffosocko.com/2018/dries-how-awesome-would-it-be-if-i-could-use",
"syndication": [
"https://twitter.com/ChrisAldrich/status/964621051304071168"
],
"in-reply-to": [
"https://twitter.com/Dries/status/964486539844685825",
"https://dri.es/my-posse-plan-for-evolving-my-site"
],
"content": {
"text": "@Dries How awesome would it be if I could use @buffer not only to post to social media, but to post to my own website using the Micropub spec? https://www.w3.org/TR/micropub/",
"html": "@Dries How awesome would it be if I could use @buffer not only to post to social media, but to post to my own website using the Micropub spec? <a href=\"https://www.w3.org/TR/micropub/\">https://www.w3.org/TR/micropub/</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
},
"_id": "99799",
"_source": "192",
"_is_read": true
}
{
"type": "entry",
"published": "2018-02-16 11:09-0800",
"url": "https://gregorlove.com/2018/02/care-package/",
"photo": [
"https://gregorlove.com/site/assets/files/4947/img_20180214_150450.750x0-is.jpg"
],
"syndication": [
"https://twitter.com/gRegorLove/status/964579280939245568",
"https://www.facebook.com/gregorlove/posts/10103476988633974"
],
"name": "Care Package",
"content": {
"text": "I received this awesome Valentine\u2019s Day care package from a special new ...lady in my life. Her name is Hollie and as you can see, she appreciates puns and corny humor like me.\n\nHollie messaged me on OKCupid in October because, as she later told me, she \u201cwanted to talk to a cute California guy\u201d even though she lives in Maryland. The conversation was going well, but I don\u2019t think either of us expected much to come of it. In November I was helping my parents move across the country so I was taking longer to respond. She interpreted that as me not being interested and sent a \u201ctake care\u201d message. I wrote her back explaining the delay, but didn\u2019t hear anything back. I figured that was that. Apparently she didn\u2019t see that message until January, though, which is when she got back in touch. We started chatting more often and were hitting it off.\n\nCoincidentally, I was already going to be in Baltimore for IndieWebCamp, so I mentioned we could meet up. That same week we talked on the phone for the first time. We talked for two hours and I definitely had a good feeling about the two of us. Unfortunately she wasn\u2019t able to come into Baltimore to meet, but we both agreed we needed to meet eventually. That Saturday night in Baltimore I was thinking it over. If I was already willing to fly out again at some point to meet her, why not spend a little extra effort while I\u2019m already nearby? I suggested I could drive out to meet her Sunday night before my early return flight on Monday.\n\nWe met at a Barnes & Noble. I arrived on time and called her, but she didn\u2019t answer. Then I texted and waited a few minutes before calling again. Still no answer. That paranoid little voice in my head started wondering \u201cDid she chicken out on meeting me? Oh no, is she even real? Alright, where is Ashton Kutcher?\u201d To distract myself from the voices temporarily, I decided to browse some books. I didn\u2019t have to wait more than a few minutes, though, when she walked up to me. She was a very real lady, quite happy to see me, and gave me a good hug. No Ashton Kutcher was sighted.\n\nIt was totally worth it, which is probably obvious from the fact you are reading this post now. We clicked and felt comfortable with each other right away. It felt like we had known each other for a much longer time. We had some good conversation about relationships, long-distance, and our concerns. I made my interest clear, but didn\u2019t ask her that night. She was definitely interested, but had some hesitation. I did ask her to be my valentine that night, though, and she said yes. A few days later we discussed it some more and now we\u2019re dating!\n\nLikely To Be Asked Questions\n\nQ: Maryland? Isn\u2019t that pretty far away from San Diego?\n\nA: Yes, it is.\n\nQ: So, are you moving?\n\nA: Not anytime soon. This is among the things we discussed. She has wanted to move to California for a while (yes, before meeting me).\n\nQ: Where is a picture of you two?!\n\nA: Unfortunately we did not take one when we met. She\u2019s totally real, you guys! She goes to another school. You don\u2019t know her.",
"html": "<p></p>\n\n<p>I received this awesome Valentine\u2019s Day care package from a special new ...lady in my life. Her name is Hollie and as you can see, she appreciates puns and corny humor like me.</p>\n\n<p>Hollie messaged me on OKCupid in October because, as she later told me, she \u201cwanted to talk to a cute California guy\u201d even though she lives in Maryland. The conversation was going well, but I don\u2019t think either of us expected much to come of it. In November I was helping my parents move across the country so I was taking longer to respond. She interpreted that as me not being interested and sent a \u201ctake care\u201d message. I wrote her back explaining the delay, but didn\u2019t hear anything back. I figured that was that. Apparently she didn\u2019t see that message until January, though, which is when she got back in touch. We started chatting more often and were hitting it off.</p>\n\n<p>Coincidentally, I was already going to be in Baltimore for <a href=\"https://2018.indieweb.org/baltimore\">IndieWebCamp</a>, so I mentioned we could meet up. That same week we talked on the phone for the first time. We talked for two hours and I definitely had a good feeling about the two of us. Unfortunately she wasn\u2019t able to come into Baltimore to meet, but we both agreed we needed to meet eventually. That Saturday night in Baltimore I was thinking it over. If I was already willing to fly out again at some point to meet her, why not spend a little extra effort while I\u2019m already nearby? I suggested I could drive out to meet her Sunday night before my early return flight on Monday.</p>\n\n<p>We met at a Barnes & Noble. I arrived on time and called her, but she didn\u2019t answer. Then I texted and waited a few minutes before calling again. Still no answer. That paranoid little voice in my head started wondering \u201cDid she chicken out on meeting me? Oh no, is she even real? Alright, where is Ashton Kutcher?\u201d To distract myself from the voices temporarily, I decided to browse some books. I didn\u2019t have to wait more than a few minutes, though, when she walked up to me. She was a very real lady, quite happy to see me, and gave me a good hug. No Ashton Kutcher was sighted.</p>\n\n<p>It was totally worth it, which is probably obvious from the fact you are reading this post now. We clicked and felt comfortable with each other right away. It felt like we had known each other for a much longer time. We had some good conversation about relationships, long-distance, and our concerns. I made my interest clear, but didn\u2019t ask her that night. She was definitely interested, but had some hesitation. I did ask her to be my valentine that night, though, and she said yes. A few days later we discussed it some more and now we\u2019re dating!</p>\n\n<h2>Likely To Be Asked Questions</h2>\n\n<p>Q: Maryland? Isn\u2019t that pretty far away from San Diego?<br />\nA: Yes, it is.</p>\n\n<p>Q: So, are you moving?<br />\nA: Not anytime soon. This is among the things we discussed. She has wanted to move to California for a while (yes, before meeting me).</p>\n\n<p>Q: Where is a picture of you two?!<br />\nA: Unfortunately we did not take one when we met. She\u2019s totally real, you guys! She goes to another school. You don\u2019t know her.</p>"
},
"_id": "98982",
"_source": "179",
"_is_read": true
}
RSVP invited · Issue #156 · pfefferle/wordpress-semantic-linkbacks https://github.com/pfefferle/wordpress-semantic-linkbacks/issues/156
When Brid.gy sends webmentions for people invited via a Facebook POSSE copy, the webmentions for these people don't show up properly in comments because `semantic_linkbacks_type` is set to "invite" instead of "rsvp:invited".
Manually effecting the change in the database provides the expected display. See: http://boffosocko.com/2018/02/14/homebrew-website-club-meetup-on-february-21-2018/#Invited
{
"type": "entry",
"published": "2018-02-15T01:06:58+00:00",
"url": "http://stream.boffosocko.com/2018/rsvp-invited-issue-156-pfefferlewordpress-semantic-linkbacks-pfefferlewordpress-semantic-linkbacksissues156when-bridgy-sends-webmentions-for",
"content": {
"text": "RSVP invited \u00b7 Issue #156 \u00b7 pfefferle/wordpress-semantic-linkbacks https://github.com/pfefferle/wordpress-semantic-linkbacks/issues/156\n\n\nWhen Brid.gy sends webmentions for people invited via a Facebook POSSE copy, the webmentions for these people don't show up properly in comments because `semantic_linkbacks_type` is set to \"invite\" instead of \"rsvp:invited\".\n\n\nManually effecting the change in the database provides the expected display. See: http://boffosocko.com/2018/02/14/homebrew-website-club-meetup-on-february-21-2018/#Invited",
"html": "RSVP invited \u00b7 Issue #156 \u00b7 pfefferle/wordpress-semantic-linkbacks <a href=\"https://github.com/pfefferle/wordpress-semantic-linkbacks/issues/156\">https://github.com/pfefferle/wordpress-semantic-linkbacks/issues/156</a><br /><br />\nWhen Brid.gy sends webmentions for people invited via a Facebook POSSE copy, the webmentions for these people don't show up properly in comments because `semantic_linkbacks_type` is set to \"invite\" instead of \"rsvp:invited\".<br /><br />\nManually effecting the change in the database provides the expected display. See: <a href=\"http://boffosocko.com/2018/02/14/homebrew-website-club-meetup-on-february-21-2018/#Invited\">http://boffosocko.com/2018/02/14/homebrew-website-club-meetup-on-february-21-2018/#Invited</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
},
"_id": "99802",
"_source": "192",
"_is_read": true
}
Something about his website makes me think that @weslinda might appreciate Homebrew Website Club in Baltimore next week: https://indieweb.org/events/2018-02-20-homebrew-website-club
{
"type": "entry",
"published": "2018-02-15T00:28:53+00:00",
"url": "http://stream.boffosocko.com/2018/something-about-his-website-makes-me-think-that-weslinda-might",
"syndication": [
"https://twitter.com/ChrisAldrich/status/963933113578598401"
],
"content": {
"text": "Something about his website makes me think that @weslinda might appreciate Homebrew Website Club in Baltimore next week: https://indieweb.org/events/2018-02-20-homebrew-website-club",
"html": "Something about his website makes me think that @weslinda might appreciate Homebrew Website Club in Baltimore next week: <a href=\"https://indieweb.org/events/2018-02-20-homebrew-website-club\">https://indieweb.org/events/2018-02-20-homebrew-website-club</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
},
"_id": "99803",
"_source": "192",
"_is_read": true
}
{
"type": "entry",
"published": "2018-02-14T21:45:32+0000",
"url": "https://notiz.blog/2018/02/14/openid-connect-federation/",
"name": "OpenID Connect Federation",
"content": {
"text": "Irgendwann letzte oder vorletzte Woche ist die \u00dcberschrift \"OpenID Connect Federation 1.0 \u2013 draft XX\" in meinem Feed-Reeder aufgetaucht und auf Buzz-Words wie Federation o. \u00c4. springe ich nat\u00fcrlich immer noch sofort auf!\n\nSpezifikationen lesen, macht ja generell nicht viel Spa\u00df, aber bei der OpenID Connect Federation 1.0 kam ich nicht mal bis zur H\u00e4lfte. Bevor man wirklich versteht was das Protokoll eigentlich macht (f\u00fcr mich h\u00f6rt es sich \u00e4hnlich an wie OpenID Connect Dynamic Client Registration), geht es um Metadaten, JSON Web Signature (JWS), JSON Web Tokens (JWT) und JSON Web Keys (JWK).\n\nEigentlich dachte ich, dass OpenID Connect durch OAuth 2 super simpel sein soll\u2026 Immerhin basiert ja OAuth 2 auf SSL/TLS und nicht wie OAuth 1 auf komplizierte Signaturen.\n\n\n The majority of failed OAuth 1.0 implementation attempts are caused by the complexity of the cryptographic requirements of the specification. The fact that the original specification was poorly written didn\u2019t help, but even with the newly published RFC 5849, OAuth 1.0 is still not trivial to use on the client side. The convenient and ease offered by simply using passwords is sorely missing in OAuth.\nEran Hammer\n\n\nDie OpenID Foundation scheint ihre Meinung ge\u00e4ndert zu haben\u2026 SSL scheint wohl doch nicht auszureichen.\n\n\n Another problem that has been raised is the dependency on TLS as the sole protection against attacks on the transferred information. These last couple of years a number of problems with OpenSSL, which is probably the most widely used TLS library, have been discovered that put reasonable doubt into this dependency.\nOpenID Connect Dynamic Client Registration\n\n\nSchade, schade\u2026\n\nWer eine wirkliche Alternative zu OpenID Connect sucht, der soll sich mal IndieAuth anschauen. IndieAuth kommt der urspr\u00fcnglichen Idee von OpenID Connect sehr nahe und ist relativ einfach zu verstehen und auch zu implementieren!",
"html": "<p>Irgendwann letzte oder vorletzte Woche ist die \u00dcberschrift \"OpenID Connect Federation 1.0 \u2013 draft XX\" in meinem Feed-Reeder aufgetaucht und auf Buzz-Words wie <strong>Federation</strong> o. \u00c4. springe ich nat\u00fcrlich immer noch sofort auf!</p>\n\n<p>Spezifikationen lesen, macht ja generell nicht viel Spa\u00df, aber bei der <em><a href=\"http://openid.net/specs/openid-connect-federation-1_0.html\"><strong>OpenID Connect Federation 1.0</strong></a></em> kam ich nicht mal bis zur H\u00e4lfte. Bevor man wirklich versteht was das Protokoll eigentlich macht (f\u00fcr mich h\u00f6rt es sich \u00e4hnlich an wie <a href=\"https://openid.net/specs/openid-connect-registration-1_0.html\"><strong>OpenID Connect Dynamic Client Registration</strong></a>), geht es um Metadaten, <a href=\"https://tools.ietf.org/html/rfc7515\">JSON Web Signature (JWS)</a>, JSON Web Tokens (JWT) und <a href=\"https://tools.ietf.org/html/rfc7517\">JSON Web Keys (JWK)</a>.</p>\n\n<p>Eigentlich dachte ich, dass <em>OpenID Connect</em> durch <em>OAuth 2</em> super simpel sein soll\u2026 Immerhin basiert ja <em>OAuth 2</em> auf SSL/TLS und nicht wie <em>OAuth 1</em> auf komplizierte Signaturen.</p>\n\n<blockquote>\n <p>The majority of failed OAuth 1.0 implementation attempts are caused by the complexity of the cryptographic requirements of the specification. The fact that the original specification was poorly written didn\u2019t help, but even with the newly published <a href=\"http://tools.ietf.org/html/rfc5849\">RFC 5849</a>, OAuth 1.0 is still not trivial to use on the client side. The convenient and ease offered by simply using passwords is sorely missing in OAuth.</p>\n<a href=\"https://hueniverse.com/introducing-oauth-2-0-b5681da60ce2\">Eran Hammer</a>\n</blockquote>\n\n<p>Die OpenID Foundation scheint ihre Meinung ge\u00e4ndert zu haben\u2026 SSL scheint wohl doch nicht auszureichen.</p>\n\n<blockquote>\n <p>Another problem that has been raised is the dependency on TLS as the sole protection against attacks on the transferred information. These last couple of years a number of problems with OpenSSL, which is probably the most widely used TLS library, have been discovered that put reasonable doubt into this dependency.</p>\n<a href=\"https://openid.net/specs/openid-connect-registration-1_0.html\">OpenID Connect Dynamic Client Registration</a>\n</blockquote>\n\n<p>Schade, schade\u2026</p>\n\n<p>Wer eine wirkliche Alternative zu <em>OpenID Connect</em> sucht, der soll sich mal <a href=\"https://www.w3.org/TR/indieauth/\"><strong>IndieAuth</strong></a> anschauen. <strong>IndieAuth</strong> kommt der urspr\u00fcnglichen Idee von <a href=\"https://web.archive.org/web/20100609191041/http://openidconnect.com:80/\"><em>OpenID Connect</em></a> sehr nahe und ist relativ einfach zu verstehen und auch zu implementieren!</p>"
},
"author": {
"type": "card",
"name": "Matthias Pfefferle",
"url": "https://notiz.blog/author/matthias-pfefferle/",
"photo": "https://secure.gravatar.com/avatar/75512bb584bbceae57dfc503692b16b2?s=40&d=mm&r=g"
},
"_id": "100357",
"_source": "206",
"_is_read": true
}
This issue is for an in-development idea of being able to get a reply post into the micro.blog system when the post is created on an external site.
{
"type": "entry",
"published": "2018-02-14T13:18:59-05:00",
"summary": "This issue is for an in-development idea of being able to get a reply post into the micro.blog system when the post is created on an external site.",
"url": "https://eddiehinkle.com/2018/02/14/5/reply/",
"category": [
"indieweb"
],
"in-reply-to": [
"https://github.com/microdotblog/issues"
],
"name": "Adding support for cross-site replies",
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com",
"photo": null
},
"refs": {
"https://github.com/microdotblog/issues": {
"type": "entry",
"url": "https://github.com/microdotblog/issues",
"name": "https://github.com/microdotblog/issues"
}
},
"_id": "59859",
"_source": "39",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Sarah Mundy",
"url": "https://sarahmundy.com/",
"photo": null
},
"url": "https://sarahmundy.com/2018/02/12/hello-world/",
"published": "2018-02-12T18:40:53+00:00",
"content": {
"html": "<p>This is my first personal blog or website in years that is not hosted on a silo. I\u2019ve been watching #IndieWeb get up and running, and played with all sorts of Facebook and Google alternatives\u2026 and I finally decided to give it a shot. I\u2019m planning on getting this set up as a sort of collection book for my thoughts, my projects, my current readings, my social lives, and I hope to have fun whilst doing it!</p>",
"text": "This is my first personal blog or website in years that is not hosted on a silo. I\u2019ve been watching #IndieWeb get up and running, and played with all sorts of Facebook and Google alternatives\u2026 and I finally decided to give it a shot. I\u2019m planning on getting this set up as a sort of collection book for my thoughts, my projects, my current readings, my social lives, and I hope to have fun whilst doing it!"
},
"name": "Introduction",
"_id": "124153",
"_source": "245",
"_is_read": true
}
{
"type": "entry",
"published": "2018-02-12T17:15:32+00:00",
"url": "https://cleverdevil.io/2018/editing-a-post-in-known-can-have-destructive-side-effects",
"in-reply-to": [
"https://github.com/idno/Known"
],
"name": "Editing a post in Known can have destructive side effects on content",
"content": {
"text": "There is a bug in Known which causes HTML posts published via Micropub to be changed (usually in bad ways) when \"editing\" the post, even when you don't actually make any changes to the post. I discovered this issue when publishing via Sunlit 2.0, which supports Micropub.\nI published two stories:\nCar Museum with William\nSan Diego with Lacey\nBecause Sunlit doesn't yet support syndication via Micropub, I clicked \"edit\" on one of the posts, and toggled on syndication to Twitter and Facebook, and then clicked \"save.\" The result was that the post's content was changed (in a destructive way, resulting in visual regressions), even though I hadn't actually edited the content, or even clicked into the content editor.\nSeems like this is a bug.",
"html": "<p>There is a bug in <a class=\"u-in-reply-to\" href=\"https://github.com/idno/Known\">Known</a> which causes HTML posts published via Micropub to be changed (usually in bad ways) when \"editing\" the post, even when you don't actually make any changes to the post. I discovered this issue when publishing via <a href=\"http://www.manton.org/2018/01/sunlit-beta-update.html\">Sunlit 2.0</a>, which supports Micropub.</p>\n<p>I published two stories:</p>\n<ul><li><a href=\"https://cleverdevil.io/2018/car-museum-with-william\">Car Museum with William</a></li>\n<li><a href=\"https://cleverdevil.io/2018/san-diego-with-lacey\">San Diego with Lacey</a></li>\n</ul><p>Because Sunlit doesn't yet support syndication via Micropub, I clicked \"edit\" on one of the posts, and toggled on syndication to Twitter and Facebook, and then clicked \"save.\" The result was that the post's content was changed (in a destructive way, resulting in visual regressions), even though I hadn't actually edited the content, or even clicked into the content editor.</p>\n<p>Seems like this is a bug.</p>"
},
"author": {
"type": "card",
"name": "Jonathan LaCour",
"url": "https://cleverdevil.io/profile/cleverdevil",
"photo": "https://cleverdevil.io/file/2fa19f964fb8970faaf20b909c69d6cb/thumb.png"
},
"_id": "49422",
"_source": "71",
"_is_read": true
}
In trying to decide on his indie web approach, Dries gives an excellent breakdown of the concepts of PESOS (Publish Elsewhere, Syndicate to Own Site) and POSSE (Publish to Own Site, Syndicate Elsewhere).
There are some great responses in the comments too, like this one from Chris and this one from Tantek (syndicated from their own sites, obvs).
{
"type": "entry",
"published": "2018-02-11T01:30:41Z",
"url": "https://adactio.com/links/13427",
"category": [
"indieweb",
"pesos",
"posse",
"drupal",
"personal",
"publishing",
"social",
"networks",
"facebook",
"twitter",
"sharing"
],
"bookmark-of": [
"https://dri.es/to-pesos-or-to-posse"
],
"content": {
"text": "To PESOS or to POSSE? | Dries Buytaert\n\n\n\nIn trying to decide on his indie web approach, Dries gives an excellent breakdown of the concepts of PESOS (Publish Elsewhere, Syndicate to Own Site) and POSSE (Publish to Own Site, Syndicate Elsewhere).\n\nThere are some great responses in the comments too, like this one from Chris and this one from Tantek (syndicated from their own sites, obvs).",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://dri.es/to-pesos-or-to-posse\">\nTo PESOS or to POSSE? | Dries Buytaert\n</a>\n</h3>\n\n<p>In trying to decide on his indie web approach, Dries gives an excellent breakdown of the concepts of PESOS (Publish Elsewhere, Syndicate to Own Site) and POSSE (Publish to Own Site, Syndicate Elsewhere).</p>\n\n<p>There are some great responses in the comments too, like <a href=\"http://boffosocko.com/2018/02/07/reply-to-to-pesos-or-to-posse-by-dries-buytaert/\">this one from Chris</a> and <a href=\"http://tantek.com/2018/037/t1/posse-indieweb-twitter-facebook\">this one from Tantek</a> (syndicated from their own sites, obvs).</p>"
},
"_id": "46551",
"_source": "2",
"_is_read": true
}
I had a chat with some people from Name.com while I was in Denver for An Event Apart. Here’s a few minutes of me rambling on about web development and the indie web.
{
"type": "entry",
"published": "2018-02-10T11:04:24Z",
"url": "https://adactio.com/links/13420",
"category": [
"youtube",
"video",
"indieweb",
"posse",
"browsers",
"standards",
"web",
"development",
"evaluating",
"technology",
"interview"
],
"bookmark-of": [
"https://www.youtube.com/watch?v=tLAI02TY7vI"
],
"content": {
"text": "Jeremy Keith on your content, failing well, and the Indie Web Movement - YouTube\n\n\n\nI had a chat with some people from Name.com while I was in Denver for An Event Apart. Here\u2019s a few minutes of me rambling on about web development and the indie web.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://www.youtube.com/watch?v=tLAI02TY7vI\">\nJeremy Keith on your content, failing well, and the Indie Web Movement - YouTube\n</a>\n</h3>\n\n<p>I had a chat with some people from Name.com while I was in Denver for An Event Apart. Here\u2019s a few minutes of me rambling on about web development and the indie web.</p>\n\n<a href=\"https://www.youtube.com/watch?v=tLAI02TY7vI\"><img src=\"https://i.ytimg.com/vi/tLAI02TY7vI/hqdefault.jpg\" alt=\"Jeremy Keith on your content, failing well, and the Indie Web Movement\" /></a>"
},
"_id": "46093",
"_source": "2",
"_is_read": true
}
While I think a Gallery object would be nice, eventually, I am not convinced that its necessarily the best way to go here. Its my understanding that pretty much all Entities support attachments, so doing it in the near-term in a more cross-cutting way would enable any type of post created via Micropub that contains multiple attachments to elegantly display the images.
{
"type": "entry",
"published": "2018-02-09T20:33:23+00:00",
"url": "https://cleverdevil.io/2018/while-i-think-a-gallery-object-would",
"in-reply-to": [
"https://github.com/idno/Known/issues/1991"
],
"content": {
"text": "While I think a Gallery object would be nice, eventually, I am not convinced that its necessarily the best way to go here. Its my understanding that pretty much all Entities support attachments, so doing it in the near-term in a more cross-cutting way would enable any type of post created via Micropub that contains multiple attachments to elegantly display the images."
},
"author": {
"type": "card",
"name": "Jonathan LaCour",
"url": "https://cleverdevil.io/profile/cleverdevil",
"photo": "https://cleverdevil.io/file/2fa19f964fb8970faaf20b909c69d6cb/thumb.png"
},
"_id": "49435",
"_source": "71",
"_is_read": true
}
{
"type": "entry",
"published": "2018-02-09T02:06:03+00:00",
"url": "https://miklb.com/blog/2018/02/09/3409/",
"syndication": [
"https://twitter.com/miklb/status/961783010604605441"
],
"name": "02:06# \n\t\t\t\t\t\t\t\t\t\t\t\t \n\t\t\t\t\t\t\t\t\t\t\t\nBeen in a dev rut, so to break out going to see how quickly I can go from 0 to live #indieweb site sending/receiving webmentions with @eleven_ty. Since it supports liquid, I can use my work from jekyll-indieweb as a heads start https://github.com/miklb/jekyll-indieweb",
"content": {
"text": "Been in a dev rut, so to break out going to see how quickly I can go from 0 to live #indieweb site sending/receiving webmentions with @eleven_ty. Since it supports liquid, I can use my work from jekyll-indieweb as a heads start https://github.com/miklb/jekyll-indieweb",
"html": "<p>Been in a dev rut, so to break out going to see how quickly I can go from 0 to live #indieweb site sending/receiving webmentions with <a href=\"https://twitter.com/eleven_ty\">@eleven_ty</a>. Since it supports liquid, I can use my work from jekyll-indieweb as a heads start <a href=\"https://github.com/miklb/jekyll-indieweb\">https://github.com/miklb/jekyll-indieweb</a>\n</p>"
},
"_id": "44475",
"_source": "42",
"_is_read": true
}
I've said before that I would like to bring a record of the things I mark at reading.am back to my notes website as Bookmarks. In theory, WithKnown makes this very easy, because every type of entry (Posts, Status updates, Bookmarks etc) has its own API, to which you can send correctly formatted POST requests. You can also send POST requests to Known's micropub endpoint. Unfortunately, neither option works for Bookmarks (and probably not for Likes and Reposts, but I haven't played with them).
More this way ...
{
"type": "entry",
"published": "2018-02-08T16:00:00+0100",
"summary": "I've said before that I would like to bring a record of the things I mark at reading.am back to my notes website as Bookmarks. In theory, WithKnown makes this very easy, because every type of entry (Posts, Status updates, Bookmarks etc) has its own API, to which you can send correctly formatted POST requests. You can also send POST requests to Known's micropub endpoint. Unfortunately, neither option works for Bookmarks (and probably not for Likes and Reposts, but I haven't played with them). \n\n More this way ...",
"url": "https://www.jeremycherfas.net/blog/why-i-cannot-post-bookmarks-to-known-automatically",
"name": "Why I cannot post bookmarks to Known automatically",
"content": {
"text": "I've said before that I would like to bring a record of the things I mark at reading.am back to my notes website as Bookmarks. In theory, WithKnown makes this very easy, because every type of entry (Posts, Status updates, Bookmarks etc) has its own API, to which you can send correctly formatted POST requests. You can also send POST requests to Known's micropub endpoint. Unfortunately, neither option works for Bookmarks (and probably not for Likes and Reposts, but I haven't played with them).\n\n More this way ...",
"html": "<p>I've said before that I would like to bring a record of the things I mark at reading.am back to my notes website as Bookmarks. In theory, WithKnown makes this very easy, because every type of entry (Posts, Status updates, Bookmarks etc) has its own API, to which you can send correctly formatted POST requests. You can also send POST requests to Known's micropub endpoint. Unfortunately, neither option works for Bookmarks (and probably not for Likes and Reposts, but I haven't played with them).</p>\n\n <p><a href=\"https://www.jeremycherfas.net/blog/why-i-cannot-post-bookmarks-to-known-automatically\">More this way ...</a></p>"
},
"_id": "100319",
"_source": "202",
"_is_read": true
}
Thanks Chris for expanding on Dries' super-welcome post about using Drupal to participate in the independent web first, and push to locked-down privatized pieces of the Internet like Facebook, Twitter, et. al. secondarily!
I'm sure you didn't mean it this way – and honestly i was happy to be alerted to your post by https://withknown.com/ – but you seem to have pioneered a sort of webmention spam! I couldn't figure out where in your post you actually referenced me, like Known claimed, until i viewed source and saw that in empty links you had my https://mlncn.withknown.com/ blog and indeed my cooperative's post http://agaric.com/blogs/marking-drupals-blog-posts-indieweb as well as a link to the fantastic http://hongpong.com (he is more active on http://twitter.com/hongpong but is indeed working to push the #IndieWeb movement forward).
Were you intending to alert us through webmentions, or had we come up in research but didn't end up being included in the finished post?
{
"type": "entry",
"published": "2018-02-07T23:53:22+0000",
"url": "https://mlncn.withknown.com/2018/thanks-chris-for-expanding-on-dries-super-welcome-post-about-using",
"category": [
"IndieWeb"
],
"syndication": [
"https://twitter.com/mlncn/status/961387444741419008",
"https://facebook.com/10152328966186123/posts/10155066805111123"
],
"in-reply-to": [
"http://boffosocko.com/2018/02/07/reply-to-to-pesos-or-to-posse-by-dries-buytaert/"
],
"content": {
"text": "Thanks Chris for expanding on Dries' super-welcome post about using Drupal to participate in the independent web first, and push to locked-down privatized pieces of the Internet like Facebook, Twitter, et. al. secondarily!\n\n\nI'm sure you didn't mean it this way \u2013 and honestly i was happy to be alerted to your post by https://withknown.com/ \u2013 but you seem to have pioneered a sort of webmention spam! I couldn't figure out where in your post you actually referenced me, like Known claimed, until i viewed source and saw that in empty links you had my https://mlncn.withknown.com/ blog and indeed my cooperative's post http://agaric.com/blogs/marking-drupals-blog-posts-indieweb as well as a link to the fantastic http://hongpong.com (he is more active on http://twitter.com/hongpong but is indeed working to push the #IndieWeb movement forward).\n\n\nWere you intending to alert us through webmentions, or had we come up in research but didn't end up being included in the finished post?",
"html": "Thanks Chris for expanding on Dries' super-welcome post about using Drupal to participate in the independent web first, and push to locked-down privatized pieces of the Internet like Facebook, Twitter, et. al. secondarily!<br /><br />\nI'm sure you didn't mean it this way \u2013 and honestly i was happy to be alerted to your post by <a href=\"https://withknown.com/\">https://withknown.com/</a> \u2013 but you seem to have pioneered a sort of webmention spam! I couldn't figure out where in your post you actually referenced me, like Known claimed, until i viewed source and saw that in empty links you had my <a href=\"https://mlncn.withknown.com/\">https://mlncn.withknown.com/</a> blog and indeed my cooperative's post <a href=\"http://agaric.com/blogs/marking-drupals-blog-posts-indieweb\">http://agaric.com/blogs/marking-drupals-blog-posts-indieweb</a> as well as a link to the fantastic <a href=\"http://hongpong.com\">http://hongpong.com</a> (he is more active on <a href=\"http://twitter.com/hongpong\">http://twitter.com/hongpong</a> but is indeed working to push the <a href=\"https://mlncn.withknown.com/tag/IndieWeb\" class=\"p-category\">#IndieWeb</a> movement forward).<br /><br />\nWere you intending to alert us through webmentions, or had we come up in research but didn't end up being included in the finished post?"
},
"author": {
"type": "card",
"name": "benjamin melan\u00e7on",
"url": "https://mlncn.withknown.com/profile/mlncn",
"photo": "https://mlncn.withknown.com/file/00c7d8e67682303419851cd5bf04d11d/thumb.jpg"
},
"_id": "123958",
"_source": "234",
"_is_read": true
}
{
"type": "entry",
"published": "2018-02-07T11:30:16-08:00",
"url": "https://aaronparecki.com/2018/02/07/7/indieauth",
"category": [
"indieauth",
"indieweb"
],
"name": "IndieAuth-Client-PHP 0.3.1",
"content": {
"text": "This release includes two new methods for quickly developing an IndieAuth client.\n\nThe library can now handle all the boilerplate work of generating a state parameter, URL canonicalization, and state management between the request and callback.\n\nDeveloping an IndieAuth client now requires just setting a few configuration variables and deciding how to show error messages in your application. See the code below for an example of using the new features!\n\nindex.php\n\n<form action=\"/login.php\" method=\"post\">\n <input type=\"url\" name=\"url\">\n <input type=\"submit\" value=\"Log In\">\n</form>\n\n\nlogin.php\n\n<?php\nrequire('vendor/autoload.php');\nif(!isset($_POST['url'])) {\n die('Missing URL');\n}\n\n// Start a session for the library to be able to save state between requests.\nsession_start();\n\n// You'll need to set up two pieces of information before you can use the client,\n// the client ID and and the redirect URL.\n// The client ID should be the home page of your app.\nIndieAuth\\Client::$clientID = 'https://example.com/client/';\n\n// The redirect URL is where the user will be returned to after they approve the request.\nIndieAuth\\Client::$redirectURL = 'https://example.com/client/redirect.php';\n\n// Pass the user's URL and your requested scope to the client.\n// If you are writing a Micropub client, you should include at least the \"create\" scope.\n// If you are just trying to log the user in, you can omit the second parameter.\nlist($authorizationURL, $error) = IndieAuth\\Client::begin($_POST['url']);\n// or list($authorizationURL, $error) = IndieAuth\\Client::begin($_POST['url']);\n\n// Check whether the library was able to discover the necessary endpoints\nif($error) {\n echo \"<p>Error: \".$error['error'].\"</p>\";\n echo \"<p>\".$error['error_description'].\"</p>\";\n} else {\n // Redirect the user to their authorization endpoint\n header('Location: '.$authorizationURL);\n}\n\n\nredirect.php\n\n<?php\nrequire('vendor/autoload.php');\n\nsession_start();\nIndieAuth\\Client::$clientID = 'https://example.com/client/';\nIndieAuth\\Client::$redirectURL = 'https://example.com/client/redirect.php';\n\nlist($user, $error) = IndieAuth\\Client::complete($_GET);\n\nif($error) {\n echo \"<p>Error: \".$error['error'].\"</p>\";\n echo \"<p>\".$error['error_description'].\"</p>\";\n} else {\n // Login succeeded!\n // If you requested a scope, then there will be an access token in the response.\n // Otherwise there will just be the user's URL.\n echo \"URL: \".$user['me'].\"\n\";\n if(isset($user['access_token'])) {\n echo \"Access Token: \".$user['access_token'].\"\n\";\n echo \"Scope: \".$user['scope'].\"\n\";\n }\n}",
"html": "<p>This release includes two new methods for quickly developing an IndieAuth client.</p>\n\n<p>The library can now handle all the boilerplate work of generating a state parameter, URL canonicalization, and state management between the request and callback.</p>\n\n<p>Developing an IndieAuth client now requires just setting a few configuration variables and deciding how to show error messages in your application. See the code below for an example of using the new features!</p>\n\n<h3>index.php</h3>\n\n<pre><code><form action=\"/login.php\" method=\"post\">\n <input type=\"url\" name=\"url\">\n <input type=\"submit\" value=\"Log In\">\n</form>\n</code></pre>\n\n<h3>login.php</h3>\n\n<pre><code><?php\nrequire('vendor/autoload.php');\nif(!isset($_POST['url'])) {\n die('Missing URL');\n}\n\n// Start a session for the library to be able to save state between requests.\nsession_start();\n\n// You'll need to set up two pieces of information before you can use the client,\n// the client ID and and the redirect URL.\n// The client ID should be the home page of your app.\nIndieAuth\\Client::$clientID = 'https://example.com/client/';\n\n// The redirect URL is where the user will be returned to after they approve the request.\nIndieAuth\\Client::$redirectURL = 'https://example.com/client/redirect.php';\n\n// Pass the user's URL and your requested scope to the client.\n// If you are writing a Micropub client, you should include at least the \"create\" scope.\n// If you are just trying to log the user in, you can omit the second parameter.\nlist($authorizationURL, $error) = IndieAuth\\Client::begin($_POST['url']);\n// or list($authorizationURL, $error) = IndieAuth\\Client::begin($_POST['url']);\n\n// Check whether the library was able to discover the necessary endpoints\nif($error) {\n echo \"<p>Error: \".$error['error'].\"</p>\";\n echo \"<p>\".$error['error_description'].\"</p>\";\n} else {\n // Redirect the user to their authorization endpoint\n header('Location: '.$authorizationURL);\n}\n</code></pre>\n\n<h3>redirect.php</h3>\n\n<pre><code><?php\nrequire('vendor/autoload.php');\n\nsession_start();\nIndieAuth\\Client::$clientID = 'https://example.com/client/';\nIndieAuth\\Client::$redirectURL = 'https://example.com/client/redirect.php';\n\nlist($user, $error) = IndieAuth\\Client::complete($_GET);\n\nif($error) {\n echo \"<p>Error: \".$error['error'].\"</p>\";\n echo \"<p>\".$error['error_description'].\"</p>\";\n} else {\n // Login succeeded!\n // If you requested a scope, then there will be an access token in the response.\n // Otherwise there will just be the user's URL.\n echo \"URL: \".$user['me'].\"<br>\";\n if(isset($user['access_token'])) {\n echo \"Access Token: \".$user['access_token'].\"<br>\";\n echo \"Scope: \".$user['scope'].\"<br>\";\n }\n}\n</code></pre>"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aaronparecki.com/images/profile.jpg"
},
"_id": "42695",
"_source": "16",
"_is_read": true
}