Care Package

{
    "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 &amp; 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
}

Chris Aldrich stream.boffosocko.com/profile/chrisaldrich

{
    "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
}

Chris Aldrich stream.boffosocko.com/profile/chrisaldrich

{
    "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
}

Matthias Pfefferle notiz.blog/author/matthias-pfefferle/

OpenID Connect Federation

{
    "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
}

Adding support for cross-site replies

{
    "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
}

Introduction

{
    "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
}

Jonathan LaCour cleverdevil.io/profile/cleverdevil

Editing a post in Known can have destructive side effects on content

{
    "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
}

{
    "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
}

Jeremy Keith on your content, failing well, and the Indie Web Movement - YouTube

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.

Read More

{
    "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
}

Jonathan LaCour cleverdevil.io/profile/cleverdevil

{
    "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
}

02:06# 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

{
    "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
}

Why I cannot post bookmarks to Known automatically

{
    "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
}

benjamin melançon mlncn.withknown.com/profile/mlncn

{
    "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
}

Aaron Parecki aaronparecki.com

IndieAuth-Client-PHP 0.3.1

{
    "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>&lt;form action=\"/login.php\" method=\"post\"&gt;\n  &lt;input type=\"url\" name=\"url\"&gt;\n  &lt;input type=\"submit\" value=\"Log In\"&gt;\n&lt;/form&gt;\n</code></pre>\n\n<h3>login.php</h3>\n\n<pre><code>&lt;?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 \"&lt;p&gt;Error: \".$error['error'].\"&lt;/p&gt;\";\n  echo \"&lt;p&gt;\".$error['error_description'].\"&lt;/p&gt;\";\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>&lt;?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 \"&lt;p&gt;Error: \".$error['error'].\"&lt;/p&gt;\";\n  echo \"&lt;p&gt;\".$error['error_description'].\"&lt;/p&gt;\";\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'].\"&lt;br&gt;\";\n  if(isset($user['access_token'])) {\n    echo \"Access Token: \".$user['access_token'].\"&lt;br&gt;\";\n    echo \"Scope: \".$user['scope'].\"&lt;br&gt;\";\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
}

Aaron Parecki aaronparecki.com

Episode 18: IndieWebCamp Baltimore

{
    "type": "entry",
    "published": "2018-02-06",
    "url": "https://percolator.today/episode/18",
    "audio": [
        "https://percolator.today/redirect.php?url=https%3A%2F%2Fpercolator.today%2Fmedia%2FEpisode_18.mp3"
    ],
    "name": "Episode 18: IndieWebCamp Baltimore",
    "author": {
        "type": "card",
        "name": "Aaron Parecki",
        "url": "https://aaronparecki.com",
        "photo": "https://percolator.today/images/aaronpk.jpg"
    },
    "_id": "48345",
    "_source": "13",
    "_is_read": true
}

Aaron Parecki aaronparecki.com

OwnYourGram Updates

{
    "type": "entry",
    "published": "2018-02-05T10:12:51-08:00",
    "url": "https://aaronparecki.com/2018/02/05/6/ownyourgram",
    "category": [
        "ownyourgram",
        "indieweb",
        "changelog"
    ],
    "name": "OwnYourGram Updates",
    "content": {
        "text": "Just pushed a few changes to OwnYourGram this morning! Here's what changed:\nYou can now see the schedule of your account so you know when to expect photos! You'll see which tier you're at, and how long until your account is next polled.\nYou can now add a list of tags that will be sent along with every photo! This is useful if you want all your photos to be tagged \"photo\" or \"instagram\" for example.\n\n  I also updated the documentation to include an example of the JSON post format that OwnYourGram can send.\u00a0\n  \nIf your site has a Media Endpoint, then OwnYourGram will first upload your photos to your Media Endpoint, and include those URLs in the Micropub request.\u00a0\nThat's it for now! Happy OwnYourGramming!",
        "html": "<p>Just pushed a few changes to OwnYourGram this morning! Here's what changed:</p>\n<p>You can now see the schedule of your account so you know when to expect photos! You'll see which tier you're at, and how long until your account is next polled.</p>\n<img src=\"https://aaronparecki.com/2018/02/05/6/image-1.png\" alt=\"\" /><p>You can now add a list of tags that will be sent along with every photo! This is useful if you want all your photos to be tagged \"photo\" or \"instagram\" for example.</p>\n<img src=\"https://aaronparecki.com/2018/02/05/6/image-2.png\" alt=\"\" /><p>\n  I also updated the <a href=\"https://ownyourgram.com/docs\">documentation</a> to include an example of the JSON post format that OwnYourGram can send.\u00a0\n  </p>\n<p>If your site has a <a href=\"https://www.w3.org/TR/micropub/#media-endpoint\">Media Endpoint</a>, then OwnYourGram will first upload your photos to your Media Endpoint, and include those URLs in the Micropub request.\u00a0</p>\n<p>That's it for now! Happy OwnYourGramming!</p>"
    },
    "author": {
        "type": "card",
        "name": "Aaron Parecki",
        "url": "https://aaronparecki.com/",
        "photo": "https://aaronparecki.com/images/profile.jpg"
    },
    "_id": "41032",
    "_source": "16",
    "_is_read": true
}

{
    "type": "entry",
    "author": {
        "name": "manton",
        "url": "http://www.manton.org",
        "photo": null
    },
    "url": "http://www.manton.org/2018/02/6421.html",
    "content": {
        "html": "<p>Wrapping up the next Micro.blog iOS update, which has more control over cross-posting. Decided to focus on Micro.blog\u2019s own cross-posting for this release, and consider Micropub syndication later. (They are very different models. Just need to focus on the immediate need first.)</p>",
        "text": "Wrapping up the next Micro.blog iOS update, which has more control over cross-posting. Decided to focus on Micro.blog\u2019s own cross-posting for this release, and consider Micropub syndication later. (They are very different models. Just need to focus on the immediate need first.)"
    },
    "published": "2018-02-04T15:28:27+00:00",
    "updated": "2018-02-04T15:28:27+00:00",
    "_id": "38768",
    "_source": "12",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2018-02-01T16:15:38Z",
    "url": "https://adactio.com/links/13371",
    "category": [
        "indieweb",
        "posse",
        "medium",
        "syndication",
        "ifttt",
        "rss"
    ],
    "bookmark-of": [
        "https://remysharp.com/2018/02/01/how-to-cross-post-to-medium"
    ],
    "content": {
        "text": "How to cross post to Medium\n\n\n\nRemy outlines the process he uses for POSSEing to Medium now that they\u2019ve removed their IFTTT integration.\n\n\n  At some point during 2017, Medium decided to pull their IFTTT applets that allows content to be posted into Medium. Which I think is a pretty shitty move since there was no notification that the applet was pulled (I only noticed after Medium just didn\u2019t contain a few of my posts), and it smacks of \u201cMedium should be the original source\u201d\u2026which may be fine for some people, but I\u2019m expecting my own content to outlast the Medium web site.",
        "html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://remysharp.com/2018/02/01/how-to-cross-post-to-medium\">\nHow to cross post to Medium\n</a>\n</h3>\n\n<p>Remy outlines the process he uses for POSSEing to Medium now that they\u2019ve removed their IFTTT integration.</p>\n\n<blockquote>\n  <p>At some point during 2017, Medium decided to pull their IFTTT applets that allows content to be posted into Medium. Which I think is a pretty shitty move since there was no notification that the applet was pulled (I only noticed after Medium just didn\u2019t contain a few of my posts), and it smacks of \u201cMedium should be the original source\u201d\u2026which may be fine for some people, but I\u2019m expecting my own content to outlast the Medium web site.</p>\n</blockquote>"
    },
    "_id": "35539",
    "_source": "2",
    "_is_read": true
}

Aaron Parecki aaronparecki.com

{
    "type": "entry",
    "published": "2018-01-30T15:22:56-08:00",
    "url": "https://aaronparecki.com/2018/01/30/23/",
    "category": [
        "indieweb"
    ],
    "content": {
        "text": "\"A photoblog is like Instagram, only it's harder to use, your friends aren't on it, and it's owned by you, not a megacorp.\" \ud83d\ude02 https://www.kickstarter.com/projects/davidfg/you-have-to-see-this-place",
        "html": "\"A photoblog is like Instagram, only it's harder to use, your friends aren't on it, and it's owned by you, not a megacorp.\" <a href=\"https://aaronparecki.com/emoji/%F0%9F%98%82\">\ud83d\ude02</a> <a href=\"https://www.kickstarter.com/projects/davidfg/you-have-to-see-this-place\">https://www.kickstarter.com/projects/davidfg/you-have-to-see-this-place</a>"
    },
    "author": {
        "type": "card",
        "name": "Aaron Parecki",
        "url": "https://aaronparecki.com/",
        "photo": "https://aaronparecki.com/images/profile.jpg"
    },
    "_id": "41039",
    "_source": "16",
    "_is_read": true
}

Aaron Parecki aaronparecki.com

{
    "type": "entry",
    "published": "2018-01-28T20:04:15-08:00",
    "url": "https://aaronparecki.com/2018/01/28/17/",
    "category": [
        "indieweb",
        "ios"
    ],
    "photo": [
        "https://aaronparecki.com/2018/01/28/17/photo.jpg"
    ],
    "content": {
        "text": "This is pretty cool being able to sign in to an iOS app with my own website"
    },
    "author": {
        "type": "card",
        "name": "Aaron Parecki",
        "url": "https://aaronparecki.com/",
        "photo": "https://aaronparecki.com/images/profile.jpg"
    },
    "_id": "30387",
    "_source": "16",
    "_is_read": true
}