David Shanske david.shanske.com

Brainstorming on Implementing Vouch, Following and Blogrolls

{
    "type": "entry",
    "published": "2018-07-01T18:23:12-04:00",
    "url": "https://david.shanske.com/2018/07/01/brainstorming-on-implementing-vouch-following-and-blogrolls/",
    "syndication": [
        "https://twitter.com/dshanske/status/1013548707453730817"
    ],
    "name": "Brainstorming on Implementing Vouch, Following and Blogrolls",
    "content": {
        "text": "Vouch is an extension to the webmention protocol. Webmentions usually have two parameters\u2026source and target. Target is the URL on your website\u00a0 that the Source URL is linking to.\nThe vouch parameter is a third URL to help the target determine whether or not they should accept the webmention. This should block automated spam and aid in moderation.\nSeveral people have implemented receiving vouches. It is relatively easy\u00a0 to look at a vouch URL and see if it links to a third-party who you have approved of in the past.\u00a0 While there are more advanced things you can do, that is the basic summary of the protocol.\nThe harder part, and less implemented by others is sending of vouches. Where do you find people who have been approved by people you have approved of? It would really help if we had some more discussion on this.\nSo, at the Indieweb Summit, we talked about this a bit, after which I implemented a primitive Vouch receiver. My solution was to use a manually curated domain whitelist that I\u2019d previously built as my source for acceptable domains.\nThere are some suggestions on where to get this list. Several people generate a list from referrers. This sent me down the road of looking as to whether I\u2019d want to implement refbacks to add more mentions to my website\u2026except there is a lot of noise. Refbacks are basically the same as webmentions, except the source is gleaned from the\u00a0 referrer header that sites send when a page is accessed.\nEven if I\u00a0 have a list of sites that I approve of, I would have to crawl them to find links from them to other sites. So, I think we should all help each other out on this.\nThat means we need to post our list of approved domains somewhere on our site. That used to be quite popular. It was called a Blogroll. It was sites you read, followed, or recommended. There are other terms for it. But, this is a perfect place to get a nice list, and if we publish them, then we can help the Vouch cause.\nBut the problem is, how do you tell a Vouch receiver where your list is. There are some brainstorming items about blogrolls and following/follower lists\nFollower lists marked up with rel=\u201dfollower\u201d or rel=\u201dfollowing\u201d\nContact lists marked up with rel=\u201dcontact\u201d\n\nFollow Posts marked up with u-follow-of\nFollow posts would create an h-feed of follow posts that could be used to generate a list. You can have a specific page on your website, but there isn\u2019t a way to indicate this to someone looking for it.\nThere is rel-directory, which is the reverse direction. It indicates that the link is to a directory in which the current page is listed. What we seem to be missing is a property that says that a page is a feed of followers that can be placed inside an h-card or on a home page.\nu-follow-of is a proposed property that indicates that an h-entry is considered a follow post, which is a post indicating you have followed someone, then a feed of follow posts could be parsed and read by a reader. If you add in the XFN relationships to that, you can build even more detail.\nThe reverse relationship would, in theory, be u-follow, which would be a URL to the follow post of the current URL(the thing being followed).\nFeeds are identicated by rel=\u201dfeed\u201d to link from your homepage to those feeds. But there is a lack of indicating what type of feed it is, such as rel=\u201dblogroll\u201d or rel=\u201dfollowing\u201d.\u00a0 I\u2019m not sure, and need more discussion about what to use for this.\nBut, this has the ability to solve a lot of problems. Imagine I\u2026\nPost Follow posts when I follow someone\nUse this to generate a blogroll/followers list\nSend webmentions when I follow someone so they can build relationships\nUse that list as a vouch list. Use other people\u2019s blogrolls/followers lists as a means to generate vouch lists\u2026which reduces the implementation cost of Vouch.\nNeeds work, but suddenly I want to do Follow posts.",
        "html": "<a href=\"https://indieweb.org/Vouch\">Vouch</a> is an extension to the webmention protocol. Webmentions usually have two parameters\u2026source and target. Target is the URL on your website\u00a0 that the Source URL is linking to.\n<p>The vouch parameter is a third URL to help the target determine whether or not they should accept the webmention. This should block automated spam and aid in moderation.</p>\n<p>Several people have implemented receiving vouches. It is relatively easy\u00a0 to look at a vouch URL and see if it links to a third-party who you have approved of in the past.\u00a0 While there are more advanced things you can do, that is the basic summary of the protocol.</p>\n<p>The harder part, and less implemented by others is sending of vouches. Where do you find people who have been approved by people you have approved of? It would really help if we had some more discussion on this.</p>\n<p>So, at the Indieweb Summit, we <a href=\"https://indieweb.org/2018/vouch\">talked</a> about this a bit, after which I implemented a primitive Vouch receiver. My solution was to use a manually curated domain whitelist that I\u2019d previously built as my source for acceptable domains.</p>\n<p>There are some suggestions on where to get this list. Several people generate a list from referrers. This sent me down the road of looking as to whether I\u2019d want to implement refbacks to add more mentions to my website\u2026except there is a lot of noise. <a href=\"https://indieweb.org/refback\">Refbacks</a> are basically the same as webmentions, except the source is gleaned from the\u00a0 referrer header that sites send when a page is accessed.</p>\n<p>Even if I\u00a0 have a list of sites that I approve of, I would have to crawl them to find links from them to other sites. So, I think we should all help each other out on this.</p>\n<p>That means we need to post our list of approved domains somewhere on our site. That used to be quite popular. It was <a href=\"https://indieweb.org/blogroll\">called</a> a Blogroll. It was sites you read, followed, or recommended. There are other terms for it. But, this is a perfect place to get a nice list, and if we publish them, then we can help the Vouch cause.</p>\n<p>But the problem is, how do you tell a Vouch receiver where your list is. There are some brainstorming items about blogrolls and following/follower lists</p>\n<ul><li>Follower lists marked up with rel=\u201dfollower\u201d or rel=\u201dfollowing\u201d</li>\n<li>Contact lists marked up with rel=\u201dcontact\u201d</li>\n<li>\n<a href=\"https://indieweb.org/follow\">Follow</a> Posts marked up with u-follow-of</li>\n</ul><p>Follow posts would create an h-feed of follow posts that could be used to generate a list. You can have a specific page on your website, but there isn\u2019t a way to indicate this to someone looking for it.</p>\n<p>There is rel-directory, which is the reverse direction. It indicates that the link is to a directory in which the current page is listed. What we seem to be missing is a property that says that a page is a feed of followers that can be placed inside an h-card or on a home page.</p>\n<p>u-follow-of is a proposed property that indicates that an h-entry is considered a follow post, which is a post indicating you have followed someone, then a feed of follow posts could be parsed and read by a reader. If you add in the <a href=\"https://indieweb.org/XFN\">XFN</a> relationships to that, you can build even more detail.</p>\n<p>The reverse relationship would, in theory, be u-follow, which would be a URL to the follow post of the current URL(the thing being followed).</p>\n<p>Feeds are identicated by rel=\u201dfeed\u201d to link from your homepage to those feeds. But there is a lack of indicating what type of feed it is, such as rel=\u201dblogroll\u201d or rel=\u201dfollowing\u201d.\u00a0 I\u2019m not sure, and need more discussion about what to use for this.</p>\n<p>But, this has the ability to solve a lot of problems. Imagine I\u2026</p>\n<ul><li>Post Follow posts when I follow someone</li>\n<li>Use this to generate a blogroll/followers list</li>\n<li>Send webmentions when I follow someone so they can build relationships</li>\n<li>Use that list as a vouch list. Use other people\u2019s blogrolls/followers lists as a means to generate vouch lists\u2026which reduces the implementation cost of Vouch.</li>\n</ul><p>Needs work, but suddenly I want to do Follow posts.</p>"
    },
    "author": {
        "type": "card",
        "name": "David Shanske",
        "url": "https://david.shanske.com/",
        "photo": "https://aperture-proxy.p3k.io/6f1f841c095626a5e52a3b86849e757329773a28/68747470733a2f2f64617669642e7368616e736b652e636f6d2f77702d636f6e74656e742f75706c6f6164732f6176617461722d707269766163792f63616368652f67726176617461722f322f632f326362316638616664396338643362363436623430373163356564383837633937306438316436323565656564383765343437373036393430653263343033642d3132352e706e67"
    },
    "_id": "512397",
    "_source": "5",
    "_is_read": true
}

Eddie Hinkle eddiehinkle.com

{
    "type": "entry",
    "published": "2018-07-01T21:03:28-04:00",
    "summary": "Indigenous v1.0.3 has been approved and should be on the App Store soon. It has new on-boarding screens when you\u2019re not logged in, updated compatibility with micro.blog\u2019s IndieAuth, as well as bug fixes. A new Indigenous Development Log blog post is coming soon.",
    "url": "https://eddiehinkle.com/2018/07/01/21/note/",
    "category": [
        "indigenous",
        "tech"
    ],
    "content": {
        "text": "Indigenous v1.0.3 has been approved and should be on the App Store soon. It has new on-boarding screens when you\u2019re not logged in, updated compatibility with micro.blog\u2019s IndieAuth, as well as bug fixes. A new Indigenous Development Log blog post is coming soon.",
        "html": "<p><a href=\"https://itunes.apple.com/us/app/indigenous-social-timeline/id1271004584?mt=8\">Indigenous</a> v1.0.3 has been approved and should be on the App Store soon. It has new on-boarding screens when you\u2019re not logged in, updated compatibility with micro.blog\u2019s IndieAuth, as well as bug fixes. A new Indigenous Development Log blog post is coming soon.</p>"
    },
    "author": {
        "type": "card",
        "name": "Eddie Hinkle",
        "url": "https://eddiehinkle.com/",
        "photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
    },
    "_id": "512130",
    "_source": "226",
    "_is_read": true
}

Kevin Marks known.kevinmarks.com/profile/kevinmarks

{
    "type": "entry",
    "published": "2018-07-01T16:21:52+0000",
    "url": "http://known.kevinmarks.com/2018/aaron-put-together-a-nice-clear-guide",
    "category": [
        "Indieweb"
    ],
    "syndication": [
        "https://twitter.com/kevinmarks/status/1013457673109434368"
    ],
    "content": {
        "text": "Aaron put together a nice clear guide to creating and sending your first webmention https://aaronparecki.com/2018/06/30/11/your-first-webmention #Indieweb",
        "html": "Aaron put together a nice clear guide to creating and sending your first webmention <a href=\"https://aaronparecki.com/2018/06/30/11/your-first-webmention\">https://aaronparecki.com/2018/06/30/11/your-first-webmention</a> <a href=\"http://known.kevinmarks.com/tag/Indieweb\" class=\"p-category\">#Indieweb</a>"
    },
    "author": {
        "type": "card",
        "name": "Kevin Marks",
        "url": "http://known.kevinmarks.com/profile/kevinmarks",
        "photo": "https://aperture-proxy.p3k.io/ed7979fd10a648fc253eae0b54e66fb36e57d3d4/687474703a2f2f6b6e6f776e2e6b6576696e6d61726b732e636f6d2f66696c652f3932353536353636363931373362373836376162383339656536353536663965"
    },
    "_id": "509366",
    "_source": "205",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2018-07-01T10:56:22Z",
    "url": "https://adactio.com/links/14071",
    "category": [
        "webmention",
        "indieweb",
        "syndication",
        "blogging",
        "writing",
        "sharing",
        "pings",
        "markup",
        "html",
        "hentry",
        "microformats",
        "frontend",
        "development",
        "hcard",
        "comments",
        "replies"
    ],
    "bookmark-of": [
        "https://aaronparecki.com/2018/06/30/11/your-first-webmention"
    ],
    "content": {
        "text": "Sending your First Webmention from Scratch \u2022 Aaron Parecki\n\n\n\nA nice little tutorial from Aaron.",
        "html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://aaronparecki.com/2018/06/30/11/your-first-webmention\">\nSending your First Webmention from Scratch \u2022 Aaron Parecki\n</a>\n</h3>\n\n<p>A nice little tutorial from Aaron.</p>"
    },
    "_id": "506774",
    "_source": "2",
    "_is_read": true
}

Keynote: The Building Blocks Of The Indie Web - YouTube

Here’s the video of the talk I gave at Design4Drupal last week in Boston. There’s a good half an hour of questions at the end.

Read More

{
    "type": "entry",
    "published": "2018-07-01T10:07:18Z",
    "url": "https://adactio.com/links/14068",
    "category": [
        "youtube",
        "video",
        "indieweb",
        "design4drupal",
        "presentation",
        "conference",
        "talk",
        "relme",
        "authentication",
        "micropub",
        "webmention",
        "posse",
        "pesos",
        "publishing",
        "networks"
    ],
    "bookmark-of": [
        "https://www.youtube.com/watch?v=GZUq1kF4wXk"
    ],
    "content": {
        "text": "Keynote: The Building Blocks Of The Indie Web - YouTube\n\n\n\nHere\u2019s the video of the talk I gave at Design4Drupal last week in Boston. There\u2019s a good half an hour of questions at the end.",
        "html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://www.youtube.com/watch?v=GZUq1kF4wXk\">\nKeynote: The Building Blocks Of The Indie Web - YouTube\n</a>\n</h3>\n\n<p>Here\u2019s the video of the talk I gave at Design4Drupal last week in Boston. There\u2019s a good half an hour of questions at the end.</p>\n\n<a href=\"https://www.youtube.com/watch?v=GZUq1kF4wXk\"><img src=\"https://i.ytimg.com/vi/GZUq1kF4wXk/hqdefault.jpg\" alt=\"Keynote: The Building Blocks Of The Indie Web\" /></a><br />"
    },
    "_id": "506432",
    "_source": "2",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2018-07-01T08:37:10Z",
    "url": "https://adactio.com/links/14066",
    "category": [
        "indieweb",
        "writing",
        "publishing",
        "sharing",
        "personal",
        "websites",
        "empowerment"
    ],
    "bookmark-of": [
        "https://www.blakewatson.com/journal/an-ode-to-web-pages/"
    ],
    "content": {
        "text": "Blake Watson | An ode to web pages\n\n\n\n\n  Before social media monoliths made us into little mechanical turks for advertising platforms, we had organic homes on the web. We had pages that were ours. And they could look however you wanted. And you could write whatever you wanted on there.\n  \n  There weren\u2019t comments if you didn\u2019t want them. There were no photo dimensions to adhere to. No 140-character limits. No BS. Or lots of BS. Either way, the choice was yours because you owned your site and you could do whatever you wanted.",
        "html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://www.blakewatson.com/journal/an-ode-to-web-pages/\">\nBlake Watson | An ode to web pages\n</a>\n</h3>\n\n<blockquote>\n  <p>Before social media monoliths made us into little mechanical turks for advertising platforms, we had organic homes on the web. We had pages that were ours. And they could look however you wanted. And you could write whatever you wanted on there.</p>\n  \n  <p>There weren\u2019t comments if you didn\u2019t want them. There were no photo dimensions to adhere to. No 140-character limits. No BS. Or lots of BS. Either way, the choice was yours because you owned your site and you could do whatever you wanted.</p>\n</blockquote>"
    },
    "_id": "506211",
    "_source": "2",
    "_is_read": true
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2018-06-30 20:25-0700",
    "url": "http://tantek.com/2018/181/t2/portland-week-indiewebsummit-sessions",
    "category": [
        "Portland",
        "IndieWebSummit",
        "IndieWeb",
        "acaibowl",
        "NP_PDX",
        "donut",
        "2018_176",
        "2018_177",
        "2018_178"
    ],
    "photo": [
        "https://aperture-media.p3k.io/igx.4sqi.net/14041e1be0ac293a5cf6a71b0e7ed9d45e479c4f769207cb83719ea442a8b975.jpg",
        "https://aperture-media.p3k.io/igx.4sqi.net/3825b3841c7278cdd066c23a1e54af4c2a6b6d94fb555cf708005ed3f8894be8.jpg",
        "https://aperture-media.p3k.io/igx.4sqi.net/45312b5ae2de8f9a14f0a907f921577285124cc0447cdae0d403604fbd23ad61.jpg",
        "https://aperture-media.p3k.io/igx.4sqi.net/2c435548729b84b0399a13bd301b1106372de685b77402d5ec2f7e3f93372de4.jpg",
        "https://aperture-media.p3k.io/igx.4sqi.net/51bc9f4e0e8d577de8e05894a54dbb3ba732dcf8d8e6181427a7c84e2f780ca9.jpg",
        "https://aperture-media.p3k.io/igx.4sqi.net/92b2add1590c9e813ccfb4d1222f47b4fcdf916ee39872df5b4afe341978fa30.jpg",
        "https://aperture-media.p3k.io/igx.4sqi.net/b26d0b16f806ca6a2bc3fc5acdfa990f76e32731b3c46a520bb93d1208bcfad0.jpg",
        "https://aperture-media.p3k.io/igx.4sqi.net/168b2b6d0cf12493452edc952e7dda792d10fd863066b57b07078916def7a27d.jpg",
        "https://aperture-media.p3k.io/igx.4sqi.net/1a5a49afdce4693fc5bd4ea817d02eea8cf21da74c9589618cbccf20765e8ec5.jpg"
    ],
    "content": {
        "text": "A few from #Portland this week:\n1 #IndieWebSummit group photo, \ud83d\udcf7 @aaronpk\u2019s camera on timer\n2 #IndieWeb Leaders Summit the day before @MozPDX, 6 in room + 6 remote\n3 Bowl of the gods #acaibowl with peanut butter on top at Kure that morning\n4 Chipotle chili bowl with quinoa at Prasad the night before that\n5 Berlin IWS Remote Viewing hosted @EmbassyNetwork by \ud83d\udcf7 @anikasai\n6 Participant proposed & led @IndieWebSummit sessions\n7 Running @Nov_ProjectPDX with @DesignNatalie (not pictured)\n8 Fresh #NP_PDX tag thanks to co-leaders Lara & Shelby\n9 Black Currant Cider limited-edition #donut @BlueStarDonuts\n\n#2018_176 #2018_177 #2018_178\n\nMore photos soon. Got photos from @IndieWebSummit to share? \nAdd them to https://indieweb.org/2018#Photos",
        "html": "<a class=\"u-photo\" href=\"https://igx.4sqi.net/img/general/original/476_hgEAv9_PXCLDY897u-Eh3xjzTiFVEPRAotancg3ZeX8.jpg\"></a><a class=\"u-photo\" href=\"https://igx.4sqi.net/img/general/original/476_HIpjf1VD79YEDwV1FwHlI2qkkluRt35B4dTblPyahgo.jpg\"></a><a class=\"u-photo\" href=\"https://igx.4sqi.net/img/general/original/476_Pi2QI8FDGDdZd5ItOkMKFgzLu84-clODF_-6DLt9cl4.jpg\"></a><a class=\"u-photo\" href=\"https://igx.4sqi.net/img/general/original/476_XRxjpzMwjR378N_NIDMhVUqe_ZT1fKYkOGy8F-O9mrQ.jpg\"></a><a class=\"u-photo\" href=\"https://igx.4sqi.net/img/general/original/476_bB3c4gAOKesIrMboG-1c3PaL60gqayfyXvjEWCWA4Wk.jpg\"></a><a class=\"u-photo\" href=\"https://igx.4sqi.net/img/general/original/476_MF8G9XS2EVlue9dN9OYsYuXkduolAs5GNK4CK21D7Sc.jpg\"></a><a class=\"u-photo\" href=\"https://igx.4sqi.net/img/general/original/476_Yx4M7wToVHhnu_ha7hSAxRlRdbyXGYLw6hscdiihTNY.jpg\"></a><a class=\"u-photo\" href=\"https://igx.4sqi.net/img/general/original/476_ZmgCIwIIxoPG8oDpyPhXOrQKPfTja7v7T75NFcIlOEM.jpg\"></a><a class=\"u-photo\" href=\"https://igx.4sqi.net/img/general/original/476_GZn07wY6PMag1_6Pg4cmPurQOx9HtjeL97llSZ6IQKU.jpg\"></a>A few from #Portland this week:<br />1 #IndieWebSummit group photo, \ud83d\udcf7 <a class=\"h-cassis-username\" href=\"https://twitter.com/aaronpk\">@aaronpk</a>\u2019s camera on timer<br />2 #IndieWeb Leaders Summit the day before <a class=\"h-cassis-username\" href=\"https://twitter.com/MozPDX\">@MozPDX</a>, 6 in room + 6 remote<br />3 Bowl of the gods #acaibowl with peanut butter on top at Kure that morning<br />4 Chipotle chili bowl with quinoa at Prasad the night before that<br />5 Berlin IWS Remote Viewing hosted <a class=\"h-cassis-username\" href=\"https://twitter.com/EmbassyNetwork\">@EmbassyNetwork</a> by \ud83d\udcf7 <a class=\"h-cassis-username\" href=\"https://twitter.com/anikasai\">@anikasai</a><br />6 Participant proposed &amp; led <a class=\"h-cassis-username\" href=\"https://twitter.com/IndieWebSummit\">@IndieWebSummit</a> sessions<br />7 Running <a class=\"h-cassis-username\" href=\"https://twitter.com/Nov_ProjectPDX\">@Nov_ProjectPDX</a> with <a class=\"h-cassis-username\" href=\"https://twitter.com/DesignNatalie\">@DesignNatalie</a> (not pictured)<br />8 Fresh #NP_PDX tag thanks to co-leaders Lara &amp; Shelby<br />9 Black Currant Cider limited-edition #donut <a class=\"h-cassis-username\" href=\"https://twitter.com/BlueStarDonuts\">@BlueStarDonuts</a><br /><br />#2018_176 #2018_177 #2018_178<br /><br />More photos soon. Got photos from <a class=\"h-cassis-username\" href=\"https://twitter.com/IndieWebSummit\">@IndieWebSummit</a> to share? <br />Add them to <a href=\"https://indieweb.org/2018#Photos\">https://indieweb.org/2018#Photos</a>"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "_id": "504978",
    "_source": "1",
    "_is_read": true
}

Aaron Parecki aaronparecki.com

Sending your First Webmention from Scratch

{
    "type": "entry",
    "published": "2018-06-30T20:35:00-07:00",
    "url": "https://aaronparecki.com/2018/06/30/11/your-first-webmention",
    "category": [
        "webmention",
        "indieweb",
        "tutorial",
        "microformats"
    ],
    "syndication": [
        "https://news.indieweb.org/en/aaronparecki.com/2018/06/30/11/your-first-webmention"
    ],
    "name": "Sending your First Webmention from Scratch",
    "content": {
        "text": "Webmention is one of the fundamental indieweb building blocks. It enables rich interactions between websites, like posting a comment or favorite on one site from another site. This post will walk you through the simplest way to get started sending webmentions to other sites so that you can use your own site to join the conversations happening on the Indie Web.\n\nSo what do you need to walk through this tutorial? We'll use static files and simple command line tools so that you can easily adapt this to any environment or programming language later.\n\nGet started\n\nFirst, we'll create a new HTML file that we'll use to contain the comment to post. At the very minimum, that file will need to contain a link to the post we're replying to.\n\n\n<!doctype html>\n<meta charset=\"utf-8\">\n<title>Hello World</title>\n<body>\n  <p>in reply to: <a href=\"https://aaronparecki.com/2018/06/30/11/your-first-webmention\">@aaronpk</a></p>\n  <p>Trying out this guide to sending webmentions</p>\n</body>\n\n\nGo ahead and copy that HTML and save it into a new file on your web server, for example: https://aaronpk.com/reply.html. Take your new post's URL and paste it into the webmention form at the bottom of this post. After a few seconds, reload this page and you should see your post show up under \"Other Mentions\"!\n\n\n\nMaking it look better\n\nThat's a great start! But you might be wondering where your comment text is. To make your comment show up better on other peoples' websites, you'll need to add a little bit of HTML markup to tell the site where your comment text is and to add your name and photo.\n\nLet's take the HTML from before and add a couple pieces.\n\n\n<!doctype html>\n<meta charset=\"utf-8\">\n<title>Hello World</title>\n<body>\n  <div class=\"h-entry\">\n    <p>in reply to: <a class=\"u-in-reply-to\" href=\"https://aaronparecki.com/2018/06/30/11/your-first-webmention\">@aaronpk</a></p>\n    <p class=\"e-content\">Trying out this guide to sending webmentions</p>\n  </div>\n</body>\n\n\nNote the parts added in green. These are Microformats! This tells the site that's receiving your webmention where to find specific parts of your post. We first wrap the whole post in a <div class=\"h-entry\"> to indicate that this is a post. Then we add a class to the <a> tag of the post we're replying to, as well as a class to the element that contains our reply text.\n\nNow, take your URL and paste it into the webmention form below again. After a few seconds, reload the page and your reply should look more complete here!\n\n\n\nNow we see the text of the reply, and also notice that it moved out of the \"Other Mentions\" section and shows up along with the rest of the replies!\n\nOf course this web page still looks pretty plain on your own website, but that's up to you to make it look however you like for visitors visiting your website! As long as you leave the h-entry and other Microformats in your post, you can add additional markup and style the page however you like!\n\nAdding your name and photo\n\nLet's make the comment appear with your name and photo now! To do this, you'll need to add a little section to your web page that indicates who wrote the post.\n\nIn Microformats, the author of a post is represented as an h-cards. An h-card is another type of object like h-entry, but is intended to represent people or places instead of posts. Below is a simple h-card that we'll add to the post.\n\n\n<div class=\"h-card\">\n  <img src=\"https://aaronpk.com/images/aaronpk.jpg\" class=\"u-photo\" width=\"40\">\n  <a href=\"https://aaronpk.com/\" class=\"u-url p-name\">Aaron Parecki</a>\n</div>\n\n\nWhen we add this h-card into the post we've written, we need to tell it that this h-card is the author of the post. To do that, add the class u-author before the h-card class like the example below.\n\n\n<!doctype html>\n<meta charset=\"utf-8\">\n<title>Hello World</title>\n<body>\n  <div class=\"h-entry\">\n    <div class=\"u-author h-card\">\n      <img src=\"https://aaronpk.com/images/aaronpk.jpg\" class=\"u-photo\" width=\"40\">\n      <a href=\"https://aaronpk.com/\" class=\"u-url p-name\">Aaron Parecki</a>\n    </div>\n    <p>in reply to: <a class=\"u-in-reply-to\" href=\"https://aaronparecki.com/2018/06/30/11/your-first-webmention\">@aaronpk</a></p>\n    <p class=\"e-content\">Trying out this guide to sending webmentions</p>\n  </div>\n</body>\n\n\nNow when you re-send the webmention, the receiver will find your author name, photo and URL and show it in the comment!\n\n\n\nGreat job! If you've successfully gotten this far, you're now able to comment on things and even RSVP to events using your own website!\n\nOne more detail that you'll want to include on your posts is the date that your post was written. This will ensure the receiving website shows the correct timestamp of your post. If you eventually incorporate this into a static site generator or CMS where you show a list of your replies all on one page, then you'll also want to add a permalink to the individual reply in this post. Typically an easy way to solve both is with the markup below.\n\n\n<a href=\"https://aaronpk.com/reply.html\" class=\"u-url\">\n  <time class=\"dt-published\" datetime=\"2018-06-30T17:15:00-0700\">July 30, 2018</time>\n</a>\n\n\nWe can add that to the post below the content.\n\n\n<!doctype html>\n<meta charset=\"utf-8\">\n<title>Hello World</title>\n<body>\n  <div class=\"h-entry\">\n    <div class=\"u-author h-card\">\n      <img src=\"https://aaronpk.com/images/aaronpk.jpg\" class=\"u-photo\" width=\"40\">\n      <a href=\"https://aaronpk.com/\" class=\"u-url p-name\">Aaron Parecki</a>\n    </div>\n    <p>in reply to: <a class=\"u-in-reply-to\" href=\"https://aaronparecki.com/2018/06/30/11/your-first-webmention\">@aaronpk</a></p>\n    <p class=\"e-content\">Trying out this guide to sending webmentions</p>\n    <p>\n      <a href=\"https://aaronpk.com/reply.html\" class=\"u-url\">\n        <time class=\"dt-published\" datetime=\"2018-06-30T17:15:00-0700\">July 30, 2018</time>\n      </a>\n    </p>\n  </div>\n</body>\n\n\nAutomatically sending webmentions\n\nThe last piece to the puzzle is having your website send webmentions automatically when a new post is created.\n\nThis part will require writing some code in your particular language of choice. You'll start by making an HTTP request to get the contents of the page you're replying to, then looking in the response for the webmention endpoint.\n\nWe can simulate this on the command line using curl and grep.\n\n\ncurl -si https://aaronparecki.com/2018/06/30/11/your-first-webmention | grep rel=\\\"webmention\\\"\n\n\nThe response will include any HTTP Link headers or HTML <link> tags that have a rel value of \"webmention\".\n\n\nLink: <https://webmention.io/aaronpk/webmention>; rel=\"webmention\"\n<link rel=\"webmention\" href=\"https://webmention.io/aaronpk/webmention\">\n\n\nIf you get more than one, the first one wins. You'll need to extract the URL from the tag and then send the webmention there.\n\nSending a webmention is just a simple POST request to the webmention endpoint with two URLs: the URL of your post (source) and the URL of the post you're replying to (target).\n\n\ncurl -si https://webmention.io/aaronpk/webmention \\\n  -d source=https://aaronpk.com/reply.html \\\n  -d target=https://aaronparecki.com/2018/06/30/11/your-first-webmention\n\n\nThe only significant part of the response is the HTTP response code. Any 2xx response code is considered a success. You'll most often receive either a 202 which indicates that the webmention processing is happening asynchronously, or if the receiver processes webmentions synchronously and everything worked, you'll get a 201 or 200.\n\nIn practice, you'll probably use a library for discovering the endpoint and sending the webmention, so here are a few pointers to start you out in a variety of languages.\n\nRuby\nPHP\nNode\nPython\nGo\nElixir\n...more on indieweb.org\nHopefully this guide was helpful to get you going in the right direction!\n\nIf you want to dive into the weeds, check out the Webmention spec as well as more details on reply posts.\n\nWhen you want to put your automatic webmention sending implementation to the test, try sending webmentions to all of the links on the test suite, webmention.rocks!\n\nIf you have any questions or run into any issues, feel free to ping me or anyone else in the IndieWeb chat!",
        "html": "<p>Webmention is one of the fundamental indieweb building blocks. It enables rich interactions between websites, like posting a comment or favorite on one site from another site. This post will walk you through the simplest way to get started sending webmentions to other sites so that you can use your own site to join the conversations happening on the Indie Web.</p>\n\n<p>So what do you need to walk through this tutorial? We'll use static files and simple command line tools so that you can easily adapt this to any environment or programming language later.</p>\n\n<h2>Get started</h2>\n\n<p>First, we'll create a new HTML file that we'll use to contain the comment to post. At the very minimum, that file will need to contain a link to the post we're replying to.</p>\n\n<pre>\n&lt;!doctype html&gt;\n&lt;meta charset=\"utf-8\"&gt;\n&lt;title&gt;Hello World&lt;/title&gt;\n&lt;body&gt;\n  &lt;p&gt;in reply to: &lt;a href=\"https://aaronparecki.com/2018/06/30/11/your-first-webmention\"&gt;@aaronpk&lt;/a&gt;&lt;/p&gt;\n  &lt;p&gt;Trying out this guide to sending webmentions&lt;/p&gt;\n&lt;/body&gt;\n</pre>\n\n<p>Go ahead and copy that HTML and save it into a new file on your web server, for example: <a href=\"https://aaronpk.com/reply.html\">https://aaronpk.com/reply.html</a>. Take your new post's URL and paste it into the webmention form <a href=\"https://aaronparecki.com/#responses\">at the bottom of this post</a>. After a few seconds, reload this page and you should see your post show up under \"Other Mentions\"!</p>\n\n<p><img src=\"https://aperture-media.p3k.io/aaronparecki.com/18b3f62cda16c0c57f79c7cfab245ed9b97133f8dcb9732f8d7b117b7c3050de.png\" alt=\"First Reply\" /></p>\n\n<h2>Making it look better</h2>\n\n<p>That's a great start! But you might be wondering where your comment text is. To make your comment show up better on other peoples' websites, you'll need to add a little bit of HTML markup to tell the site where your comment text is and to add your name and photo.</p>\n\n<p>Let's take the HTML from before and add a couple pieces.</p>\n\n<pre>\n&lt;!doctype html&gt;\n&lt;meta charset=\"utf-8\"&gt;\n&lt;title&gt;Hello World&lt;/title&gt;\n&lt;body&gt;\n  <b>&lt;div class=\"h-entry\"&gt;</b>\n    &lt;p&gt;in reply to: &lt;a <b>class=\"u-in-reply-to\"</b> href=\"https://aaronparecki.com/2018/06/30/11/your-first-webmention\"&gt;@aaronpk&lt;/a&gt;&lt;/p&gt;\n    &lt;p <b>class=\"e-content\"</b>&gt;Trying out this guide to sending webmentions&lt;/p&gt;\n  <b>&lt;/div&gt;</b>\n&lt;/body&gt;\n</pre>\n\n<p>Note the parts added in green. These are Microformats! This tells the site that's receiving your webmention where to find specific parts of your post. We first wrap the whole post in a <code>&lt;div class=\"h-entry\"&gt;</code> to indicate that this is a post. Then we add a class to the <code>&lt;a&gt;</code> tag of the post we're replying to, as well as a class to the element that contains our reply text.</p>\n\n<p>Now, take your URL and paste it into <a href=\"https://aaronparecki.com/#responses\">the webmention form</a> below again. After a few seconds, reload the page and your reply should look more complete here!</p>\n\n<p><img src=\"https://aperture-media.p3k.io/aaronparecki.com/f0ef8e68ed4e15b9055241d6395441cd1a7b88f6b06b491f1233612190905cf9.png\" alt=\"Second Reply\" /></p>\n\n<p>Now we see the text of the reply, and also notice that it moved out of the \"Other Mentions\" section and shows up along with the rest of the replies!</p>\n\n<p>Of course this web page still looks pretty plain on your own website, but that's up to you to make it look however you like for visitors visiting your website! As long as you leave the <code>h-entry</code> and other Microformats in your post, you can add additional markup and style the page however you like!</p>\n\n<h2>Adding your name and photo</h2>\n\n<p>Let's make the comment appear with your name and photo now! To do this, you'll need to add a little section to your web page that indicates who wrote the post.</p>\n\n<p>In Microformats, the author of a post is represented as an <code>h-card</code>s. An <code>h-card</code> is another type of object like <code>h-entry</code>, but is intended to represent people or places instead of posts. Below is a simple <code>h-card</code> that we'll add to the post.</p>\n\n<pre>\n&lt;div class=\"h-card\"&gt;\n  &lt;img src=\"https://aaronpk.com/images/aaronpk.jpg\" class=\"u-photo\" width=\"40\"&gt;\n  &lt;a href=\"https://aaronpk.com/\" class=\"u-url p-name\"&gt;Aaron Parecki&lt;/a&gt;\n&lt;/div&gt;\n</pre>\n\n<p>When we add this <code>h-card</code> into the post we've written, we need to tell it that this <code>h-card</code> is the author of the post. To do that, add the class <code>u-author</code> before the <code>h-card</code> class like the example below.</p>\n\n<pre>\n&lt;!doctype html&gt;\n&lt;meta charset=\"utf-8\"&gt;\n&lt;title&gt;Hello World&lt;/title&gt;\n&lt;body&gt;\n  &lt;div class=\"h-entry\"&gt;\n    <b>&lt;div class=\"u-author h-card\"&gt;\n      &lt;img src=\"https://aaronpk.com/images/aaronpk.jpg\" class=\"u-photo\" width=\"40\"&gt;\n      &lt;a href=\"https://aaronpk.com/\" class=\"u-url p-name\"&gt;Aaron Parecki&lt;/a&gt;\n    &lt;/div&gt;</b>\n    &lt;p&gt;in reply to: &lt;a class=\"u-in-reply-to\" href=\"https://aaronparecki.com/2018/06/30/11/your-first-webmention\"&gt;@aaronpk&lt;/a&gt;&lt;/p&gt;\n    &lt;p class=\"e-content\"&gt;Trying out this guide to sending webmentions&lt;/p&gt;\n  &lt;/div&gt;\n&lt;/body&gt;\n</pre>\n\n<p>Now when you re-send the webmention, the receiver will find your author name, photo and URL and show it in the comment!</p>\n\n<p><img src=\"https://aperture-media.p3k.io/aaronparecki.com/722641be2af384245782491df1f8abcb2cbb7750eb09f97329b008664938cfc2.png\" alt=\"Second Reply\" /></p>\n\n<p>Great job! If you've successfully gotten this far, you're now able to comment on things and even RSVP to events using your own website!</p>\n\n<p>One more detail that you'll want to include on your posts is the date that your post was written. This will ensure the receiving website shows the correct timestamp of your post. If you eventually incorporate this into a static site generator or CMS where you show a list of your replies all on one page, then you'll also want to add a permalink to the individual reply in this post. Typically an easy way to solve both is with the markup below.</p>\n\n<pre>\n&lt;a href=\"https://aaronpk.com/reply.html\" class=\"u-url\"&gt;\n  &lt;time class=\"dt-published\" datetime=\"2018-06-30T17:15:00-0700\"&gt;July 30, 2018&lt;/time&gt;\n&lt;/a&gt;\n</pre>\n\n<p>We can add that to the post below the content.</p>\n\n<pre>\n&lt;!doctype html&gt;\n&lt;meta charset=\"utf-8\"&gt;\n&lt;title&gt;Hello World&lt;/title&gt;\n&lt;body&gt;\n  &lt;div class=\"h-entry\"&gt;\n    &lt;div class=\"u-author h-card\"&gt;\n      &lt;img src=\"https://aaronpk.com/images/aaronpk.jpg\" class=\"u-photo\" width=\"40\"&gt;\n      &lt;a href=\"https://aaronpk.com/\" class=\"u-url p-name\"&gt;Aaron Parecki&lt;/a&gt;\n    &lt;/div&gt;\n    &lt;p&gt;in reply to: &lt;a class=\"u-in-reply-to\" href=\"https://aaronparecki.com/2018/06/30/11/your-first-webmention\"&gt;@aaronpk&lt;/a&gt;&lt;/p&gt;\n    &lt;p class=\"e-content\"&gt;Trying out this guide to sending webmentions&lt;/p&gt;\n    <b>&lt;p&gt;\n      &lt;a href=\"https://aaronpk.com/reply.html\" class=\"u-url\"&gt;\n        &lt;time class=\"dt-published\" datetime=\"2018-06-30T17:15:00-0700\"&gt;July 30, 2018&lt;/time&gt;\n      &lt;/a&gt;\n    &lt;/p&gt;</b>\n  &lt;/div&gt;\n&lt;/body&gt;\n</pre>\n\n<h2>Automatically sending webmentions</h2>\n\n<p>The last piece to the puzzle is having your website send webmentions automatically when a new post is created.</p>\n\n<p>This part will require writing some code in your particular language of choice. You'll start by making an HTTP request to get the contents of the page you're replying to, then looking in the response for the webmention endpoint.</p>\n\n<p>We can simulate this on the command line using curl and grep.</p>\n\n<pre>\ncurl -si https://aaronparecki.com/2018/06/30/11/your-first-webmention | grep rel=\\\"webmention\\\"\n</pre>\n\n<p>The response will include any HTTP <code>Link</code> headers or HTML <code>&lt;link&gt;</code> tags that have a rel value of \"webmention\".</p>\n\n<pre>\nLink: &lt;https://webmention.io/aaronpk/webmention&gt;; rel=\"webmention\"\n&lt;link rel=\"webmention\" href=\"https://webmention.io/aaronpk/webmention\"&gt;\n</pre>\n\n<p>If you get more than one, the first one wins. You'll need to extract the URL from the tag and then send the webmention there.</p>\n\n<p>Sending a webmention is just a simple <code>POST</code> request to the webmention endpoint with two URLs: the URL of your post (source) and the URL of the post you're replying to (target).</p>\n\n<pre>\ncurl -si https://webmention.io/aaronpk/webmention \\\n  -d source=https://aaronpk.com/reply.html \\\n  -d target=https://aaronparecki.com/2018/06/30/11/your-first-webmention\n</pre>\n\n<p>The only significant part of the response is the HTTP response code. Any <code>2xx</code> response code is considered a success. You'll most often receive either a <code>202</code> which indicates that the webmention processing is happening asynchronously, or if the receiver processes webmentions synchronously and everything worked, you'll get a <code>201</code> or <code>200</code>.</p>\n\n<p>In practice, you'll probably use a library for discovering the endpoint and sending the webmention, so here are a few pointers to start you out in a variety of languages.</p>\n\n<ul><li><a href=\"https://github.com/jgarber623/webmention-endpoint-ruby\">Ruby</a></li>\n<li><a href=\"https://github.com/indieweb/mention-client-php\">PHP</a></li>\n<li><a href=\"https://www.npmjs.com/package/send-webmention\">Node</a></li>\n<li><a href=\"https://github.com/bear/ronkyuu\">Python</a></li>\n<li><a href=\"https://willnorris.com/go/webmention\">Go</a></li>\n<li><a href=\"https://github.com/ckruse/webmentions-elixir\">Elixir</a></li>\n<li><a href=\"https://indieweb.org/Webmention-developer#Libraries\">...more on indieweb.org</a></li>\n</ul><p>Hopefully this guide was helpful to get you going in the right direction!</p>\n\n<p>If you want to dive into the weeds, check out the <a href=\"https://www.w3.org/TR/webmention/\">Webmention spec</a> as well as <a href=\"https://indieweb.org/reply\">more details on reply posts</a>.</p>\n\n<p>When you want to put your automatic webmention sending implementation to the test, try sending webmentions to all of the links on the test suite, <a href=\"https://webmention.rocks/\">webmention.rocks</a>!</p>\n\n<p>If you have any questions or run into any issues, feel free to ping me or anyone else in the <a href=\"https://indieweb.org/discuss\">IndieWeb chat</a>!</p>\n\n<p></p>"
    },
    "author": {
        "type": "card",
        "name": "Aaron Parecki",
        "url": "https://aaronparecki.com/",
        "photo": "https://aperture-media.p3k.io/aaronparecki.com/2b8e1668dcd9cfa6a170b3724df740695f73a15c2a825962fd0a0967ec11ecdc.jpg"
    },
    "_id": "504829",
    "_source": "16",
    "_is_read": true
}

Eddie Hinkle eddiehinkle.com

{
    "type": "entry",
    "published": "2018-06-30T19:16:16-04:00",
    "summary": "A distributed reddit is definitely possible using technologies that the IndieWeb is pioneering.",
    "url": "https://eddiehinkle.com/2018/06/30/16/reply/",
    "in-reply-to": [
        "https://mobile.twitter.com/wjmaggos/status/1013156095714611200"
    ],
    "content": {
        "text": "A distributed reddit is definitely possible using technologies that the IndieWeb is pioneering.",
        "html": "<p>A distributed reddit is definitely possible using technologies that the <a href=\"https://indieweb.org\">IndieWeb</a> is pioneering.</p>"
    },
    "author": {
        "type": "card",
        "name": "Eddie Hinkle",
        "url": "https://eddiehinkle.com/",
        "photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
    },
    "refs": {
        "https://mobile.twitter.com/wjmaggos/status/1013156095714611200": {
            "type": "entry",
            "url": "https://mobile.twitter.com/wjmaggos/status/1013156095714611200",
            "name": "https://mobile.twitter.com/wjmaggos/status/1013156095714611200"
        }
    },
    "_id": "504556",
    "_source": "226",
    "_is_read": true
}

Chris Aldrich stream.boffosocko.com/profile/chrisaldrich

{
    "type": "entry",
    "published": "2018-06-30T22:32:07+00:00",
    "url": "http://stream.boffosocko.com/2018/wjmaggos-aral-depends-on-how-distributed-youre-looking-for-is",
    "syndication": [
        "https://twitter.com/ChrisAldrich/status/1013188476332802049"
    ],
    "in-reply-to": [
        "https://twitter.com/wjmaggos/status/1013156095714611200"
    ],
    "content": {
        "text": "@wjmaggos @aral Depends on how distributed you're looking for. https://news.indieweb.org/ is set up to aggregate content which is first posted on other's sites & syndicated (currently w/o voting). \n\nhttps://indieweb.xyz/en launched today which includes categories and voting.",
        "html": "<a href=\"https://twitter.com/wjmaggos\">@wjmaggos</a> <a href=\"https://twitter.com/aral\">@aral</a> Depends on how distributed you're looking for. <a href=\"https://news.indieweb.org/\">https://news.indieweb.org/</a> is set up to aggregate content which is first posted on other's sites &amp; syndicated (currently w/o voting). <br /><br /><a href=\"https://indieweb.xyz/en\">https://indieweb.xyz/en</a> launched today which includes categories and voting.<br /><br />"
    },
    "author": {
        "type": "card",
        "name": "Chris Aldrich",
        "url": "http://stream.boffosocko.com/profile/chrisaldrich",
        "photo": "https://aperture-proxy.p3k.io/4a01a54aa55b69dd1b2633c835610491c575e2e2/687474703a2f2f73747265616d2e626f66666f736f636b6f2e636f6d2f66696c652f36303034323762383166373738356537303465616466653531316139323730662f7468756d622e6a7067"
    },
    "_id": "503991",
    "_source": "192",
    "_is_read": true
}

Posted on 2018-06-30Adding feeds from an OPML file to a Microsub server Bookmarked https://publog.stuifzandapp.com/posts/701. Syndicated to:

{
    "type": "entry",
    "url": "http://davidjohnmead.com/blog/2018/06/30/adding-feeds-from-an-opml-file-to-a-microsub-server/",
    "syndication": [
        "https://twitter.com/davidmead/status/1013150732470685697"
    ],
    "bookmark-of": [
        "https://publog.stuifzandapp.com/posts/701"
    ],
    "name": "Posted on 2018-06-30Adding feeds from an OPML file to a Microsub server\nBookmarked https://publog.stuifzandapp.com/posts/701. Syndicated to:",
    "_id": "502850",
    "_source": "194",
    "_is_read": true
}

IndieBookClub

{
    "type": "entry",
    "author": {
        "name": "manton",
        "url": "http://www.manton.org",
        "photo": null
    },
    "url": "http://www.manton.org/2018/06/indiebookclub.html",
    "name": "IndieBookClub",
    "content": {
        "html": "<p>As I mentioned in <a href=\"http://www.manton.org/2018/06/indieweb-summit-2018-wrap-up.html\">my IndieWeb Summit wrap-up</a>, I added support for <a href=\"https://indiebookclub.biz/\">IndieBookClub</a> while in Portland. IndieBookClub is a little like Goodreads, but built on standards like Microformats and Micropub so that you can post what you\u2019re reading to your own blog.</p>\n<p>Now that I\u2019m back in Austin, I\u2019ve tweaked the behavior to be smarter about recognizing the ISBN that IndieBookClub sends to Micro.blog. Posts from IndieBookClub also get the \ud83d\udcda emoji added automatically so that they show up in the <a href=\"https://micro.blog/discover/books\">books Discover section</a> on Micro.blog. Here\u2019s a screenshot of what posts look like on your Micro.blog-hosted site:</p>\n<p><img src=\"http://manton.org/images/2018/indiebookclub_post.png\" width=\"593\" height=\"321\" alt=\"Screenshot of IndieBookClub post\" /></p>\n<p>If the ISBN is specified, Micro.blog will redirect the link to Amazon, although we may change that in the future. And it\u2019s just a regular blog post, so you can always edit it using Markdown in Micro.blog.</p>",
        "text": "As I mentioned in my IndieWeb Summit wrap-up, I added support for IndieBookClub while in Portland. IndieBookClub is a little like Goodreads, but built on standards like Microformats and Micropub so that you can post what you\u2019re reading to your own blog.\nNow that I\u2019m back in Austin, I\u2019ve tweaked the behavior to be smarter about recognizing the ISBN that IndieBookClub sends to Micro.blog. Posts from IndieBookClub also get the \ud83d\udcda emoji added automatically so that they show up in the books Discover section on Micro.blog. Here\u2019s a screenshot of what posts look like on your Micro.blog-hosted site:\n\nIf the ISBN is specified, Micro.blog will redirect the link to Amazon, although we may change that in the future. And it\u2019s just a regular blog post, so you can always edit it using Markdown in Micro.blog."
    },
    "published": "2018-06-30T19:06:44+00:00",
    "updated": "2018-06-30T19:06:44+00:00",
    "_id": "502781",
    "_source": "12",
    "_is_read": true
}

IndieWeb Summit 2018 wrap-up

{
    "type": "entry",
    "author": {
        "name": "manton",
        "url": "http://www.manton.org",
        "photo": null
    },
    "url": "http://www.manton.org/2018/06/indieweb-summit-2018-wrap-up.html",
    "name": "IndieWeb Summit 2018 wrap-up",
    "content": {
        "html": "<p>Last week I was in Portland for <a href=\"https://2018.indieweb.org/\">IndieWeb Summit</a>. This was only my second IndieWeb conference (the first was IndieWebCamp in Austin). I had a great time in Portland and got even more than I expected out of IndieWeb Summit.</p>\n<p>The first day was short keynotes and sessions led by attendees on a range of topics. Jean and I talked about our experience and goals with Micro.blog in reaching even more mainstream users. I went to sessions on Microformats, timeline algorithms, code libraries for common IndieWeb building blocks, and Microsub. Some of this carried over to the beginning of the next day, including Aaron Parecki leading a discussion about IndieAuth.</p>\n<p>We held <a href=\"http://macgenie.micro.blog/2018/06/26/micro-meetup-a.html\">a Micro.blog meetup at Von Ebert Brewing</a> after the first day wrapped up. Thanks everyone for joining us!</p>\n<p>Most of the second day was a hack day to work on our own projects, and at the end of the day everyone could present what they had worked on. I was so impressed with what people had come up with, whether that was improvements to their own site or prototypes for new tools.</p>\n<p>It turned out that having this dedicated time was exactly what I needed to turn Micro.blog into an IndieAuth provider. This means that Micro.blog no longer needs to delegate to Twitter or GitHub for authorization when someone is using an IndieWeb posting tool like OwnYourGram or Quill. Users can instead authorize directly with their Micro.blog account. I also added support for the <code>summary</code> fallback parameter in Micropub, which makes Micro.blog compatible with <a href=\"https://indiebookclub.biz/\">IndieBookClub</a>.</p>\n<p>In the morning before I left Portland, I interviewed Tantek and Aaron for my upcoming book Indie Microblogging. We had a great conversation on the founding of IndieWebCamp, the accomplishments and changes in the community, and where everything is going from here.</p>\n<p><img src=\"http://manton.org/images/2018/indiewebsummit_coava.jpg\" width=\"300\" height=\"300\" alt=\"Coava Coffee\" /><img src=\"http://manton.org/images/2018/indiewebsummit_portland.jpg\" width=\"300\" height=\"300\" alt=\"Portland bridge\" /></p>\n<p>Portland was great. For this trip I opted for an Airbnb close to the IndieWeb Summit venue. It was also just a block from <a href=\"https://www.coavacoffee.com/\">Coava Coffee</a>, where I spent a couple mornings catching up on work. I hope to be back in Portland for IndieWeb Summit next year.</p>",
        "text": "Last week I was in Portland for IndieWeb Summit. This was only my second IndieWeb conference (the first was IndieWebCamp in Austin). I had a great time in Portland and got even more than I expected out of IndieWeb Summit.\nThe first day was short keynotes and sessions led by attendees on a range of topics. Jean and I talked about our experience and goals with Micro.blog in reaching even more mainstream users. I went to sessions on Microformats, timeline algorithms, code libraries for common IndieWeb building blocks, and Microsub. Some of this carried over to the beginning of the next day, including Aaron Parecki leading a discussion about IndieAuth.\nWe held a Micro.blog meetup at Von Ebert Brewing after the first day wrapped up. Thanks everyone for joining us!\nMost of the second day was a hack day to work on our own projects, and at the end of the day everyone could present what they had worked on. I was so impressed with what people had come up with, whether that was improvements to their own site or prototypes for new tools.\nIt turned out that having this dedicated time was exactly what I needed to turn Micro.blog into an IndieAuth provider. This means that Micro.blog no longer needs to delegate to Twitter or GitHub for authorization when someone is using an IndieWeb posting tool like OwnYourGram or Quill. Users can instead authorize directly with their Micro.blog account. I also added support for the summary fallback parameter in Micropub, which makes Micro.blog compatible with IndieBookClub.\nIn the morning before I left Portland, I interviewed Tantek and Aaron for my upcoming book Indie Microblogging. We had a great conversation on the founding of IndieWebCamp, the accomplishments and changes in the community, and where everything is going from here.\n\nPortland was great. For this trip I opted for an Airbnb close to the IndieWeb Summit venue. It was also just a block from Coava Coffee, where I spent a couple mornings catching up on work. I hope to be back in Portland for IndieWeb Summit next year."
    },
    "published": "2018-06-30T18:34:01+00:00",
    "updated": "2018-06-30T18:34:01+00:00",
    "_id": "502782",
    "_source": "12",
    "_is_read": true
}

{
    "type": "entry",
    "url": "http://davidjohnmead.com/blog/2018/06/30/exciting-things-from-indieweb-summit-2018-indieweb-readers/",
    "syndication": [
        "https://twitter.com/davidmead/status/1013138629080821760"
    ],
    "content": {
        "text": "This year\u2019s IndieWeb Summit had some really exciting things, as usual, including IndieWeb Readers.  One day I\u2019ll make it out to one of these.",
        "html": "This year\u2019s <a title=\"official 2018 website\" href=\"https://2018.indieweb.org/\">IndieWeb Summit</a> had some really exciting things, as usual, including <a title=\"wiki entry\" href=\"https://indieweb.org/reader\">IndieWeb Readers</a>.  One day I\u2019ll make it out to one of these."
    },
    "_id": "502657",
    "_source": "194",
    "_is_read": true
}

Chris Aldrich stream.boffosocko.com/profile/chrisaldrich

{
    "type": "entry",
    "published": "2018-06-30T18:19:02+00:00",
    "url": "http://stream.boffosocko.com/2018/sandhawke-a-bunch-of-us-started-that-very-conversation-this",
    "syndication": [
        "https://twitter.com/ChrisAldrich/status/1013124793229561858"
    ],
    "in-reply-to": [
        "https://twitter.com/sandhawke/status/1012684911122186240"
    ],
    "content": {
        "text": "@sandhawke A bunch of us started that very conversation this week in response to the public launch of a microsub server and several microsub clients.\nhttps://indieweb.org/2018/indiealgorithm\nhttps://indieweb.org/Microsub",
        "html": "<a href=\"https://twitter.com/sandhawke\">@sandhawke</a> A bunch of us started that very conversation this week in response to the public launch of a microsub server and several microsub clients.<br /><a href=\"https://indieweb.org/2018/indiealgorithm\">https://indieweb.org/2018/indiealgorithm</a><br /><a href=\"https://indieweb.org/Microsub\">https://indieweb.org/Microsub</a>"
    },
    "author": {
        "type": "card",
        "name": "Chris Aldrich",
        "url": "http://stream.boffosocko.com/profile/chrisaldrich",
        "photo": "https://aperture-proxy.p3k.io/4a01a54aa55b69dd1b2633c835610491c575e2e2/687474703a2f2f73747265616d2e626f66666f736f636b6f2e636f6d2f66696c652f36303034323762383166373738356537303465616466653531316139323730662f7468756d622e6a7067"
    },
    "_id": "502636",
    "_source": "192",
    "_is_read": true
}

Chris Aldrich stream.boffosocko.com/profile/chrisaldrich

{
    "type": "entry",
    "published": "2018-06-30T08:20:28+00:00",
    "url": "http://stream.boffosocko.com/2018/jamey_sharp-i-think-theres-some-interesting-architectures-and-ideas-surrounding",
    "syndication": [
        "https://twitter.com/ChrisAldrich/status/1012974188670455808"
    ],
    "content": {
        "text": "@jamey_sharp I think there's some interesting architectures and ideas surrounding @anvcscalar and @omeka that could be interesting for your web comics ideas. \nhttps://indieweb.org/2018/serials",
        "html": "@jamey_sharp I think there's some interesting architectures and ideas surrounding @anvcscalar and @omeka that could be interesting for your web comics ideas. <br /><a href=\"https://indieweb.org/2018/serials\">https://indieweb.org/2018/serials</a>"
    },
    "author": {
        "type": "card",
        "name": "Chris Aldrich",
        "url": "http://stream.boffosocko.com/profile/chrisaldrich",
        "photo": "https://aperture-proxy.p3k.io/4a01a54aa55b69dd1b2633c835610491c575e2e2/687474703a2f2f73747265616d2e626f66666f736f636b6f2e636f6d2f66696c652f36303034323762383166373738356537303465616466653531316139323730662f7468756d622e6a7067"
    },
    "_id": "500055",
    "_source": "192",
    "_is_read": true
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2018-06-30 01:45-0700",
    "url": "http://tantek.com/2018/181/t1/finished-indiewebsummit-coding-reply-contexts",
    "content": {
        "text": "Finished my @IndieWebSummit coding!\n\nCompleted plain text readable reply-contexts^1 (instead of just URLs)\n* in-stream^2 for new GitHub issues\n* permalinks for replies, RSVPs, comments on issues, comments on comments, and reactions to issues & comments.\n\n^1 https://indieweb.org/reply-context#Minimal_text_reply_contexts\n^2 https://indieweb.org/reply-context#Why_in-stream",
        "html": "Finished my <a class=\"h-cassis-username\" href=\"https://twitter.com/IndieWebSummit\">@IndieWebSummit</a> coding!<br /><br />Completed plain text readable reply-contexts^1 (instead of just URLs)<br />* in-stream^2 for new GitHub issues<br />* permalinks for replies, RSVPs, comments on issues, comments on comments, and reactions to issues &amp; comments.<br /><br />^1 <a href=\"https://indieweb.org/reply-context#Minimal_text_reply_contexts\">https://indieweb.org/reply-context#Minimal_text_reply_contexts</a><br />^2 <a href=\"https://indieweb.org/reply-context#Why_in-stream\">https://indieweb.org/reply-context#Why_in-stream</a>"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "_id": "498979",
    "_source": "1",
    "_is_read": true
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2018-06-29 11:06-0700",
    "url": "http://tantek.com/2018/180/t1/indiewebsummit-notes-barcamp-organizing",
    "category": [
        "BarCamp",
        "2018_177"
    ],
    "content": {
        "text": "Sharing brief @IndieWebSummit notes as they come to mind.\n\nThis was the first year people pre-wrote proposals before the #BarCamp organizing session. As facilitator I decided to have people who never proposed before go first.\n\u00a0\nCoincidentally, @Christi3k just announced the same thing @OSBridge unconference organizing session.\n\nThis may be worth codifing as a normal practice. Let first-timers propose sessions first before anyone who has done this before, especially at an @IndieWebCamp before.\n\nThe other thing I did was, after the the first-timers finished explaining and scheduling their BarCamp session proposals, I had people *other than* the remaining session proposers choose from the remaining session proposals posted on the side of the grid, and advocate for them. I think that worked quite well for selecting for the sessions that were more compelling for more people. #2018_177",
        "html": "Sharing brief <a class=\"h-cassis-username\" href=\"https://twitter.com/IndieWebSummit\">@IndieWebSummit</a> notes as they come to mind.<br /><br />This was the first year people pre-wrote proposals before the #BarCamp organizing session. As facilitator I decided to have people who never proposed before go first.<br />\u00a0<br />Coincidentally, <a class=\"h-cassis-username\" href=\"https://twitter.com/Christi3k\">@Christi3k</a> just announced the same thing <a class=\"h-cassis-username\" href=\"https://twitter.com/OSBridge\">@OSBridge</a> unconference organizing session.<br /><br />This may be worth codifing as a normal practice. Let first-timers propose sessions first before anyone who has done this before, especially at an <a class=\"h-cassis-username\" href=\"https://twitter.com/IndieWebCamp\">@IndieWebCamp</a> before.<br /><br />The other thing I did was, after the the first-timers finished explaining and scheduling their BarCamp session proposals, I had people *other than* the remaining session proposers choose from the remaining session proposals posted on the side of the grid, and advocate for them. I think that worked quite well for selecting for the sessions that were more compelling for more people. #2018_177"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "_id": "496663",
    "_source": "1",
    "_is_read": true
}

Indieweb Summit 2018 Thoughts

{
    "type": "entry",
    "author": {
        "name": null,
        "url": "https://herestomwiththeweather.com/",
        "photo": null
    },
    "url": "https://herestomwiththeweather.com/2018/06/28/indieweb-summit-2018-thoughts/",
    "published": "2018-06-28T11:18:06+00:00",
    "content": {
        "html": "<p>There seemed to be a theme of inclusivity at <a href=\"https://2018.indieweb.org/\">Indieweb Summit 2018</a>.  The session <a href=\"https://indieweb.org/2018/changetheratio\">How can we encourage diversity on the Indieweb?</a> was very helpul.  It was noted that for tech event attendance, it\u2019s good to have a wingman so try to bring someone who otherwise might not attend on their own.  Although harassment is prevalent on Twitter and Facebook, it was noted that the nice thing about Indieweb is that you can delete these people from your online life yourself.</p>\n\n<p>In his <a href=\"https://www.youtube.com/watch?v=k4a3rm_dagw&amp;t=1h06m00s\">keynote</a>, author <a href=\"http://www.williamhertling.com/\">William Hertling</a> said \u201cIf the Indieweb is going to change the world, it means building larger scale services.\u201d  In addition to being in this spirit, <a href=\"https://micro.blog/\">micro.blog</a> seems to capture William\u2019s wish for revenue models without advertising.</p>\n\n<p>A special thanks to <a href=\"https://aaronparecki.com/\">Aaron Parecki</a> for the extremely helpful <a href=\"https://indieauth.net/\">Indieauth</a> and <a href=\"https://micropub.rocks/\">Micropub</a> session on Day 2 just prior to projects.</p>",
        "text": "There seemed to be a theme of inclusivity at Indieweb Summit 2018.  The session How can we encourage diversity on the Indieweb? was very helpul.  It was noted that for tech event attendance, it\u2019s good to have a wingman so try to bring someone who otherwise might not attend on their own.  Although harassment is prevalent on Twitter and Facebook, it was noted that the nice thing about Indieweb is that you can delete these people from your online life yourself.\n\nIn his keynote, author William Hertling said \u201cIf the Indieweb is going to change the world, it means building larger scale services.\u201d  In addition to being in this spirit, micro.blog seems to capture William\u2019s wish for revenue models without advertising.\n\nA special thanks to Aaron Parecki for the extremely helpful Indieauth and Micropub session on Day 2 just prior to projects."
    },
    "name": "Indieweb Summit 2018 Thoughts",
    "_id": "493122",
    "_source": "246",
    "_is_read": true
}

gRegor Morrill gregorlove.com

{
    "type": "entry",
    "published": "2018-06-28 13:59-0700",
    "url": "https://gregorlove.com/2018/06/back-in-san-diego-after/",
    "syndication": [
        "https://twitter.com/gRegorLove/status/1012440443466997763"
    ],
    "content": {
        "text": "Back in San Diego after another great #IndieWebSummit. Reflecting on some personal goals for the next year and ideas to expand the indieweb community.",
        "html": "<p>Back in San Diego after another great #IndieWebSummit. Reflecting on some personal goals for the next year and ideas to expand the indieweb community.</p>"
    },
    "author": {
        "type": "card",
        "name": "gRegor Morrill",
        "url": "https://gregorlove.com/",
        "photo": "https://aperture-proxy.p3k.io/929c8777d059069a2a16a064d96f4c29b65548f8/68747470733a2f2f677265676f726c6f76652e636f6d2f736974652f6173736574732f66696c65732f333437332f70726f66696c652d323031362d6d65642e6a7067"
    },
    "_id": "489529",
    "_source": "95",
    "_is_read": true
}