Dates set for IndieWebCamp Austin

{
    "type": "entry",
    "author": {
        "name": null,
        "url": "https://www.manton.org/",
        "photo": null
    },
    "url": "https://www.manton.org/2018/11/09/dates-set-for.html",
    "name": "Dates set for IndieWebCamp Austin",
    "content": {
        "html": "<p>Last year we held the first IndieWebCamp in Austin. <a href=\"https://www.manton.org/2017/12/12/indiewebcamp-austin-wrapup.html\">I blogged about</a> how the event went, including sessions and topics covered, and what I learned from it:</p>\n\n<blockquote>\n  <p>I\u2019m really happy with the way the event came together. I learned a lot in helping plan it, made a few mistakes that we can improve next time, but overall came away as inspired as ever to keep improving Micro.blog so that it\u2019s a standout platform of the IndieWeb movement.</p>\n</blockquote>\n\n<p>We\u2019re going to do it again early next year: February 23-24 at Capital Factory. If you\u2019ll be in Austin, mark that weekend on your calendar. I\u2019ll make another announcement when registration is open.</p>\n\n<p>Last year there was a lot of work and last-minute stress deciding on a venue, so this year we\u2019re going to keep a bunch of things the same that seemed to work pretty well. By nailing down the details early, we\u2019ll have much more time for promotion. I\u2019d love to see us double attendance from last year. Hope to see you there!</p>",
        "text": "Last year we held the first IndieWebCamp in Austin. I blogged about how the event went, including sessions and topics covered, and what I learned from it:\n\n\n  I\u2019m really happy with the way the event came together. I learned a lot in helping plan it, made a few mistakes that we can improve next time, but overall came away as inspired as ever to keep improving Micro.blog so that it\u2019s a standout platform of the IndieWeb movement.\n\n\nWe\u2019re going to do it again early next year: February 23-24 at Capital Factory. If you\u2019ll be in Austin, mark that weekend on your calendar. I\u2019ll make another announcement when registration is open.\n\nLast year there was a lot of work and last-minute stress deciding on a venue, so this year we\u2019re going to keep a bunch of things the same that seemed to work pretty well. By nailing down the details early, we\u2019ll have much more time for promotion. I\u2019d love to see us double attendance from last year. Hope to see you there!"
    },
    "published": "2018-11-09T10:30:24-06:00",
    "post-type": "article",
    "_id": "1385747",
    "_source": "12",
    "_is_read": true
}

Recap of An Introduction to Microformats

{
    "type": "entry",
    "published": "2018-11-08 23:13-0800",
    "url": "https://gregorlove.com/2018/11/recap-of-an-introduction-to-microformats/",
    "name": "Recap of An Introduction to Microformats",
    "content": {
        "text": "I gave a talk on microformats last night at the San Diego PHP Meetup group. This was my first time giving a formal talk on the topic. I appreciate SDPHP giving me the opportunity!\n\nResources\n\n\nAn Introduction to Microformats slides. I added microformats to them because, of course. :]\n\t\nmicroformats.io: A brief introduction to microformats and links to several parsers. Includes web versions so you can try parsing microformats by direct HTML input or by entering a URL.\n\t\nmicroformats.org wiki: the microformats specifications and the parsing algorithm. I touched on some specific pages: principles, h-card, h-event, microformats2\n\n\t\nmf2-to-iCalendar: a small PHP library that converts h-event microformats to iCalendar. This is what I use on my own calendar page.\n\t\nWebmention: a specification I mentioned that enables cross-site commenting. Many receivers of webmention will parse h-card and h-entry microformats to display responses.\n\t\nMicropub: a specification for publishing using third-party clients. It uses the microformats vocabulary.\n\t\nphp-mf2: PHP parser library for microformats2\n\t\nGranary: a library and web service to convert between multiple formats, including microformats2\n\t\nXRay: a library and web service to parse structured content, including microformats2\nSome people were really interested in webmention and we ended up talking about it more after the event. I recommended Aaron's tutorial: Sending your First Webmention from Scratch. Schema.org also came up in that conversation and I mentioned Aaron's other post that documents the history of Google's recommended formats. They've changed a lot over the years, but they still parse microformats1 hReview.\n\nNotes\n\nThese are mostly notes to myself, or other potential presenters.\n\nI forgot to demo one of my favorite uses for microformats. I use the Granary web service to parse the h-feed on my notes page and generate an Atom feed: https://gregorlove.com/notes.atom\n\nI think it would help to discuss use-cases earlier in the talk. Through the questions and some discussion after the talk, I realized that wasn't fully clicking for people earlier in the talk.\n\nThe live demo of the parser went okay, though I should have planned out some more examples for the direct HTML input instead of trying to come up with it off the top of my head. It would also be good to have some examples that emphasize the flexibility of microformats placement. We discussed that point, but a visual example would be better.\n\nBe prepared to discuss schema.org, alternatives, pros and cons. I think I did okay with this. I chose to focus on the interesting consuming use-cases for microformats.",
        "html": "<p>I gave a talk on microformats last night at the <a href=\"http://sdphp.org\">San Diego PHP Meetup group</a>. This was my first time giving a formal talk on the topic. I appreciate SDPHP giving me the opportunity!</p>\n\n<h2>Resources</h2>\n\n<ul><li>\n<i><a href=\"https://gregorlove.com/presentations/an-introduction-to-microformats/\">An Introduction to Microformats</a></i> slides. I added microformats to them because, of course. :]</li>\n\t<li>\n<a href=\"https://microformats.io\">microformats.io</a>: A brief introduction to microformats and links to several parsers. Includes web versions so you can try parsing microformats by direct HTML input or by entering a URL.</li>\n\t<li>\n<a href=\"http://microformats.org/wiki/\">microformats.org wiki</a>: the microformats specifications and the parsing algorithm. I touched on some specific pages: <a href=\"http://microformats.org/wiki/principles\">principles</a>, <a href=\"http://microformats.org/wiki/h-card\">h-card</a>, <a href=\"http://microformats.org/wiki/h-event\">h-event</a>, <a href=\"http://microformats.org/wiki/microformats2\">microformats2</a>\n</li>\n\t<li>\n<a href=\"https://github.com/gRegorLove/mf2-to-iCalendar\">mf2-to-iCalendar</a>: a small PHP library that converts h-event microformats to iCalendar. This is what I use on my own <a href=\"https://gregorlove.com/calendar/\">calendar</a> page.</li>\n\t<li>\n<a href=\"https://webmention.net\">Webmention</a>: a specification I mentioned that enables cross-site commenting. Many receivers of webmention will parse h-card and h-entry microformats to display responses.</li>\n\t<li>\n<a href=\"https://micropub.net\">Micropub</a>: a specification for publishing using third-party clients. It uses the microformats vocabulary.</li>\n\t<li>\n<a href=\"https://github.com/microformats/php-mf2\">php-mf2</a>: PHP parser library for microformats2</li>\n\t<li>\n<a href=\"https://granary.io\">Granary</a>: a library and web service to convert between multiple formats, including microformats2</li>\n\t<li>\n<a href=\"https://xray.p3k.app\">XRay</a>: a library and web service to parse structured content, including microformats2</li>\n</ul><p>Some people were really interested in webmention and we ended up talking about it more after the event. I recommended Aaron's tutorial: <i><a href=\"https://aaronparecki.com/2018/06/30/11/your-first-webmention\">Sending your First Webmention from Scratch</a></i>. <a href=\"https://schema.org\">Schema.org</a> also came up in that conversation and I mentioned Aaron's <a href=\"https://aaronparecki.com/2016/12/17/8/owning-my-reviews\">other post</a> that documents the history of Google's recommended formats. They've changed a lot over the years, but they still parse microformats1 <a href=\"http://microformats.org/wiki/hreview\">hReview</a>.</p>\n\n<h2>Notes</h2>\n\n<p>These are mostly notes to myself, or other potential presenters.</p>\n\n<p>I forgot to demo one of my favorite uses for microformats. I use the Granary web service to parse the h-feed on my <a href=\"https://gregorlove.com/notes/\">notes</a> page and generate an Atom feed: <a href=\"https://gregorlove.com/notes.atom\">https://gregorlove.com/notes.atom</a></p>\n\n<p>I think it would help to discuss use-cases earlier in the talk. Through the questions and some discussion after the talk, I realized that wasn't fully clicking for people earlier in the talk.</p>\n\n<p>The live demo of the parser went okay, though I should have planned out some more examples for the direct HTML input instead of trying to come up with it off the top of my head. It would also be good to have some examples that emphasize the flexibility of microformats placement. We discussed that point, but a visual example would be better.</p>\n\n<p>Be prepared to discuss schema.org, alternatives, pros and cons. I think I did okay with this. I chose to focus on the interesting consuming use-cases for microformats.</p>"
    },
    "post-type": "article",
    "_id": "1382681",
    "_source": "179",
    "_is_read": true
}

Aaron Parecki aaronparecki.com

{
    "type": "entry",
    "published": "2018-11-08T14:38:50-08:00",
    "url": "https://aaronparecki.com/2018/11/08/11/",
    "category": [
        "https://indiewebcat.com/"
    ],
    "photo": [
        "https://aperture-media.p3k.io/aaronparecki.com/ecef22a0a4f7891c4445813f307d0937d31b4661bfbc30c4496887d6e0309bdd.jpg"
    ],
    "video": [
        "https://aperture-media.p3k.io/aaronparecki.com/da5aa6fcbe8c973178f77fc187827c8c6d6d4305361759eafdf018d20207c4c3.mp4"
    ],
    "syndication": [
        "https://www.instagram.com/p/Bp77Zo-gm6h/"
    ],
    "content": {
        "text": "Look at @indiewebcat mostly enjoying the ride to the vet \ud83d\ude3b\ud83d\udc89",
        "html": "Look at <a href=\"https://twitter.com/indiewebcat\">@indiewebcat</a> mostly enjoying the ride to the vet <a href=\"https://aaronparecki.com/emoji/%F0%9F%98%BB\">\ud83d\ude3b</a><a href=\"https://aaronparecki.com/emoji/%F0%9F%92%89\">\ud83d\udc89</a>"
    },
    "author": {
        "type": "card",
        "name": "Aaron Parecki",
        "url": "https://aaronparecki.com/",
        "photo": "https://aperture-media.p3k.io/aaronparecki.com/2b8e1668dcd9cfa6a170b3724df740695f73a15c2a825962fd0a0967ec11ecdc.jpg"
    },
    "post-type": "video",
    "_id": "1380320",
    "_source": "16",
    "_is_read": true
}

Grant Richmond grant.codes

{
    "type": "entry",
    "published": "2018-06-26T00:10:02.185Z",
    "url": "https://grant.codes/2018/06/26/5b31845ac1f2f0162199a45d-1",
    "photo": [
        "https://aperture-proxy.p3k.io/fa46e496d59866a2dc5253737ebe411d94008c86/68747470733a2f2f6772616e742e636f6465732f"
    ],
    "syndication": [
        "https://twitter.com/grantcodes/status/1011401165551087616",
        "https://www.instagram.com/p/Bkd53a7l0Lf/",
        "https://www.facebook.com/2307321132619023"
    ],
    "content": {
        "text": "#IndieWebSummit party time",
        "html": "<p>#IndieWebSummit party time</p>"
    },
    "author": {
        "type": "card",
        "name": "Grant Richmond",
        "url": "https://grant.codes",
        "photo": "https://aperture-proxy.p3k.io/be31049af9884a65289b2d14300adafc0e4030c6/68747470733a2f2f6772616e742e636f6465732f696d672f6d652e6a7067"
    },
    "post-type": "photo",
    "_id": "1380142",
    "_source": "11",
    "_is_read": true
}

Usernames on Micro.blog

{
    "type": "entry",
    "author": {
        "name": null,
        "url": "https://www.manton.org/",
        "photo": null
    },
    "url": "https://www.manton.org/2018/11/08/usernames-on-microblog.html",
    "name": "Usernames on Micro.blog",
    "content": {
        "html": "<p><a href=\"https://micro.blog/\">Micro.blog</a> now has 3 distinct styles of usernames to make the platform more compatible with other services:</p>\n\n<ul><li>Micro.blog usernames, e.g. <strong>@you</strong>. These are simple usernames for @-mentioning someone else in the Micro.blog community.</li>\n  <li>Mastodon usernames, e.g. <strong>@you@yourdomain.com</strong>. When you search Micro.blog for these usernames, Micro.blog will look for the user in another federated Mastodon instance so that you can follow them.</li>\n  <li>IndieWeb-friendly domain names, e.g. <strong>@yourdomain.com</strong>. This is where I always thought we\u2019d go for more distributed \u201cthe web is the social network\u201d interactions. Replying to one of these usernames will send a Webmention to that user\u2019s external web site.</li>\n</ul><p>I\u2019m <a href=\"https://micro.blog/manton\">@manton</a> on Micro.blog, my blog is <a href=\"https://manton.org/\">manton.org</a>, and because <a href=\"https://manton.org/2018/11/07/microblog-mastodon.html\">Micro.blog-hosted blogs support the ActivityPub API</a>, you can follow me from Mastodon by using @manton@manton.org.</p>\n\n<p>I just rolled out some ActivityPub-related reply improvements. I\u2019ll continue to improve the Micro.blog timeline so that these usernames can all coexist nicely. We\u2019ll also be updating the native apps to better support these usernames, for highlighting and auto-completion.</p>",
        "text": "Micro.blog now has 3 distinct styles of usernames to make the platform more compatible with other services:\n\nMicro.blog usernames, e.g. @you. These are simple usernames for @-mentioning someone else in the Micro.blog community.\n  Mastodon usernames, e.g. @you@yourdomain.com. When you search Micro.blog for these usernames, Micro.blog will look for the user in another federated Mastodon instance so that you can follow them.\n  IndieWeb-friendly domain names, e.g. @yourdomain.com. This is where I always thought we\u2019d go for more distributed \u201cthe web is the social network\u201d interactions. Replying to one of these usernames will send a Webmention to that user\u2019s external web site.\nI\u2019m @manton on Micro.blog, my blog is manton.org, and because Micro.blog-hosted blogs support the ActivityPub API, you can follow me from Mastodon by using @manton@manton.org.\n\nI just rolled out some ActivityPub-related reply improvements. I\u2019ll continue to improve the Micro.blog timeline so that these usernames can all coexist nicely. We\u2019ll also be updating the native apps to better support these usernames, for highlighting and auto-completion."
    },
    "published": "2018-11-08T15:32:39-06:00",
    "post-type": "article",
    "_id": "1379552",
    "_source": "12",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2018-11-08T08:26:07Z",
    "url": "https://adactio.com/links/14498",
    "category": [
        "writing",
        "sharing",
        "publishing",
        "indieweb",
        "communication",
        "connection",
        "text"
    ],
    "bookmark-of": [
        "https://robinrendle.com/notes/what-do-you-want-to-do-when-you-grow-up-kid/"
    ],
    "content": {
        "text": "What do you want to do when you grow up, kid? \u2022 Robin Rendle\n\n\n\nPublishing on the web really is quite marvellous:\n\n\n  \u2026an endless thrill, a sort of everlasting, punk-rock feeling and I hope it will never really go away.",
        "html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://robinrendle.com/notes/what-do-you-want-to-do-when-you-grow-up-kid/\">\nWhat do you want to do when you grow up, kid? \u2022 Robin Rendle\n</a>\n</h3>\n\n<p>Publishing on the web really is quite marvellous:</p>\n\n<blockquote>\n  <p>\u2026an endless thrill, a sort of everlasting, punk-rock feeling and I hope it will never really go away.</p>\n</blockquote>"
    },
    "post-type": "bookmark",
    "_id": "1373429",
    "_source": "2",
    "_is_read": true
}

Micro.blog + Mastodon

{
    "type": "entry",
    "author": {
        "name": null,
        "url": "https://www.manton.org/",
        "photo": null
    },
    "url": "https://www.manton.org/2018/11/07/microblog-mastodon.html",
    "name": "Micro.blog + Mastodon",
    "content": {
        "html": "<p>For some time, we have been considering how we could open up compatibility between <a href=\"https://micro.blog/\">Micro.blog</a> and <a href=\"https://joinmastodon.org/\">Mastodon</a>. Any feature that could be disruptive needs to be approached carefully. In this post I want to talk about how Micro.blog supports Mastodon, why I think it\u2019s useful, and anticipate some questions that we\u2019ll get about this feature.</p>\n\n<p>We\u2019re launching 2 major features today:</p>\n\n<ul><li>Micro.blog can now cross-post to a Mastodon user account, in the same way we cross-post to Twitter, Facebook, Medium, and LinkedIn. This takes a copy of your blog posts and sends them to a specified Mastodon account.</li>\n  <li>Your custom domain on Micro.blog can now be ActivityPub-compatible, so that you can follow and reply to Mastodon users directly on Micro.blog. This also means someone can follow your blog posts by adding @you@yourdomain.com on Mastodon. (This username is configurable. Mine is @manton@manton.org.)</li>\n</ul><p>These 2 features are separate and either can be enabled if you want. I have tried to be very deliberate in how ActivityPub is implemented. It is off by default, and to keep the focus on blogging and content ownership, it only works with custom domain names.</p>\n\n<p>One of the most important goals for Micro.blog is to encourage more people to blog. I wrote last year that <a href=\"https://www.manton.org/2017/01/14/key-for-microblog.html\">it\u2019s a success if more people blog</a>. Based on the feedback we\u2019ve received from the Micro.blog community, we are making great progress toward that goal.</p>\n\n<p>We have a lot of things we want to help solve with Micro.blog, but blogging is a core part of the foundation. It\u2019s not about being the most popular social network. It\u2019s not about competing with every platform that launches. It\u2019s much better for the mission of Micro.blog for us to embrace other platforms (as we\u2019ve always done with the <a href=\"https://indieweb.org/\">IndieWeb</a>) rather than put up walls between APIs.</p>\n\n<p><a href=\"https://manton.org/2018/09/07/the-way-out.html\">I recently published a post with 4 parts</a> to how we get out of the current mess with today\u2019s big social networks. I mentioned Mastodon in that post because while I don\u2019t think Mastodon tackles all 4 parts of fixing this, I do think it has a role to play.</p>\n\n<p>More compatibility with Mastodon lets us support the good things that Mastodon has accomplished, while still carrying forward what I think are the unique strengths of Micro.blog. It also opens up the Micro.blog community to interact with a much larger user base.</p>\n\n<p>Sometimes in the Mastodon world your identity can get fragmented across multiple instances. You might start on mastodon.social but then move to another instance, effectively breaking the link between your readers and your posts each time you move, with no way to migrate posts between instances. By supporting Mastodon and ActivityPub in Micro.blog, you can consolidate your identity and posts back to your own blog at your own domain name.</p>\n\n<p><a href=\"https://manton.org/2018/03/23/indieweb-generation-and.html\">As I wrote earlier this year</a>, content ownership on the web is about domain names:</p>\n\n<blockquote>\n  <p>When you write and post photos at your own domain name, your content can outlive any one blogging platform. This month marked the 16th anniversary of blogging at manton.org, and in that time I\u2019ve switched blogging platforms and hosting providers a few times. The posts and URLs can all be preserved through those changes because it\u2019s my own domain name.</p>\n</blockquote>\n\n<p>If you already have your blog on Micro.blog at yourdomain.com, we can build on that to allow @you@yourdomain.com or @whatever@micro.domain.com. This focus on domain names will continue to guide new features in Micro.blog.</p>\n\n<p>Let me answer some questions:</p>\n\n<ul><li><strong>How is Mastodon support enabled on my account?</strong> In Micro.blog on the web, click Account \u2192 ActivityPub. You will be prompted to select a username. A paid hosted microblog is required so that Micro.blog can use your custom domain name.</li>\n  <li><strong>How can I find Mastodon users to follow on Micro.blog?</strong> As more Micro.blog users interact with Mastodon users, some of those users will naturally show up in conversations or even be featured in our Discover timeline. You can also add a specific Mastodon user by searching for their full username.</li>\n  <li><strong>Will Micro.blog now start showing follower counts?</strong> No, it\u2019s important to me that we don\u2019t change the Micro.blog user experience to resemble every other social network. When you follow a Micro.blog user from Mastodon, an individual Mastodon instance will have its own follower count just for that instance. Any follower count shown in Mastodon for a Micro.blog user will be wrong. This isn\u2019t ideal, but it\u2019s the best we can currently do with how Mastodon works.</li>\n  <li><strong>What about Content Warnings?</strong> Micro.blog does not support them. I\u2019ve heard from Mastodon fans who like Content Warnings, but I\u2019m concerned about introducing extra friction in both the posting and reading experience. We\u2019ll reevaluate this feature later.</li>\n  <li><strong>What happens to direct messages sent from Mastodon to Micro.blog?</strong> Micro.blog does not have any private posts by design. Direct messages sent from Mastodon are converted into a private email.</li>\n  <li><strong>Is this going to make Micro.blog just like Mastodon?</strong> No, this is not a clone of Mastodon merged into Micro.blog or running alongside it. It\u2019s a from-scratch implementation of a few common APIs that Mastodon uses so that both systems can talk to each other.</li>\n  <li><strong>Will third-party Mastodon clients work with Micro.blog?</strong> Not currently. We might consider this later, but because of the UI differences, I think it\u2019s a better fit to have third-party apps designed for either Micro.blog or IndieWeb standards.</li>\n  <li><strong>What will happen to the Micro.blog community?</strong> I hope that this will help grow the community, without taking away from what has worked well on Micro.blog. While you might see some Mastodon posts, and those Mastodon users can interact with Micro.blog users, users from other Mastodon instances won\u2019t know about our community guidelines or expectations for Micro.blog. The community will remain predominantly Micro.blog users who share our goals for the platform.</li>\n  <li><strong>How does Micro.blog\u2019s mute feature work with Mastodon?</strong> Muting in Micro.blog has been expanded to support muting individual Mastodon users, or entire Mastodon instances based on their domain name. We have also preloaded a common <a href=\"https://github.com/tootcafe/blocked-instances\">list of Mastodon instances that are muted automatically</a> because of code of conduct violations.</li>\n</ul><p>This is a really big feature. I hope you enjoy it! This is just the baseline. I\u2019ll be working on bug fixes and improvements to make this integration work as smoothly as possible. If you have any feedback, let me know at <a href=\"mailto:help@micro.blog\">help@micro.blog</a>.</p>",
        "text": "For some time, we have been considering how we could open up compatibility between Micro.blog and Mastodon. Any feature that could be disruptive needs to be approached carefully. In this post I want to talk about how Micro.blog supports Mastodon, why I think it\u2019s useful, and anticipate some questions that we\u2019ll get about this feature.\n\nWe\u2019re launching 2 major features today:\n\nMicro.blog can now cross-post to a Mastodon user account, in the same way we cross-post to Twitter, Facebook, Medium, and LinkedIn. This takes a copy of your blog posts and sends them to a specified Mastodon account.\n  Your custom domain on Micro.blog can now be ActivityPub-compatible, so that you can follow and reply to Mastodon users directly on Micro.blog. This also means someone can follow your blog posts by adding @you@yourdomain.com on Mastodon. (This username is configurable. Mine is @manton@manton.org.)\nThese 2 features are separate and either can be enabled if you want. I have tried to be very deliberate in how ActivityPub is implemented. It is off by default, and to keep the focus on blogging and content ownership, it only works with custom domain names.\n\nOne of the most important goals for Micro.blog is to encourage more people to blog. I wrote last year that it\u2019s a success if more people blog. Based on the feedback we\u2019ve received from the Micro.blog community, we are making great progress toward that goal.\n\nWe have a lot of things we want to help solve with Micro.blog, but blogging is a core part of the foundation. It\u2019s not about being the most popular social network. It\u2019s not about competing with every platform that launches. It\u2019s much better for the mission of Micro.blog for us to embrace other platforms (as we\u2019ve always done with the IndieWeb) rather than put up walls between APIs.\n\nI recently published a post with 4 parts to how we get out of the current mess with today\u2019s big social networks. I mentioned Mastodon in that post because while I don\u2019t think Mastodon tackles all 4 parts of fixing this, I do think it has a role to play.\n\nMore compatibility with Mastodon lets us support the good things that Mastodon has accomplished, while still carrying forward what I think are the unique strengths of Micro.blog. It also opens up the Micro.blog community to interact with a much larger user base.\n\nSometimes in the Mastodon world your identity can get fragmented across multiple instances. You might start on mastodon.social but then move to another instance, effectively breaking the link between your readers and your posts each time you move, with no way to migrate posts between instances. By supporting Mastodon and ActivityPub in Micro.blog, you can consolidate your identity and posts back to your own blog at your own domain name.\n\nAs I wrote earlier this year, content ownership on the web is about domain names:\n\n\n  When you write and post photos at your own domain name, your content can outlive any one blogging platform. This month marked the 16th anniversary of blogging at manton.org, and in that time I\u2019ve switched blogging platforms and hosting providers a few times. The posts and URLs can all be preserved through those changes because it\u2019s my own domain name.\n\n\nIf you already have your blog on Micro.blog at yourdomain.com, we can build on that to allow @you@yourdomain.com or @whatever@micro.domain.com. This focus on domain names will continue to guide new features in Micro.blog.\n\nLet me answer some questions:\n\nHow is Mastodon support enabled on my account? In Micro.blog on the web, click Account \u2192 ActivityPub. You will be prompted to select a username. A paid hosted microblog is required so that Micro.blog can use your custom domain name.\n  How can I find Mastodon users to follow on Micro.blog? As more Micro.blog users interact with Mastodon users, some of those users will naturally show up in conversations or even be featured in our Discover timeline. You can also add a specific Mastodon user by searching for their full username.\n  Will Micro.blog now start showing follower counts? No, it\u2019s important to me that we don\u2019t change the Micro.blog user experience to resemble every other social network. When you follow a Micro.blog user from Mastodon, an individual Mastodon instance will have its own follower count just for that instance. Any follower count shown in Mastodon for a Micro.blog user will be wrong. This isn\u2019t ideal, but it\u2019s the best we can currently do with how Mastodon works.\n  What about Content Warnings? Micro.blog does not support them. I\u2019ve heard from Mastodon fans who like Content Warnings, but I\u2019m concerned about introducing extra friction in both the posting and reading experience. We\u2019ll reevaluate this feature later.\n  What happens to direct messages sent from Mastodon to Micro.blog? Micro.blog does not have any private posts by design. Direct messages sent from Mastodon are converted into a private email.\n  Is this going to make Micro.blog just like Mastodon? No, this is not a clone of Mastodon merged into Micro.blog or running alongside it. It\u2019s a from-scratch implementation of a few common APIs that Mastodon uses so that both systems can talk to each other.\n  Will third-party Mastodon clients work with Micro.blog? Not currently. We might consider this later, but because of the UI differences, I think it\u2019s a better fit to have third-party apps designed for either Micro.blog or IndieWeb standards.\n  What will happen to the Micro.blog community? I hope that this will help grow the community, without taking away from what has worked well on Micro.blog. While you might see some Mastodon posts, and those Mastodon users can interact with Micro.blog users, users from other Mastodon instances won\u2019t know about our community guidelines or expectations for Micro.blog. The community will remain predominantly Micro.blog users who share our goals for the platform.\n  How does Micro.blog\u2019s mute feature work with Mastodon? Muting in Micro.blog has been expanded to support muting individual Mastodon users, or entire Mastodon instances based on their domain name. We have also preloaded a common list of Mastodon instances that are muted automatically because of code of conduct violations.\nThis is a really big feature. I hope you enjoy it! This is just the baseline. I\u2019ll be working on bug fixes and improvements to make this integration work as smoothly as possible. If you have any feedback, let me know at help@micro.blog."
    },
    "published": "2018-11-07T14:24:01-06:00",
    "post-type": "article",
    "_id": "1369047",
    "_source": "12",
    "_is_read": true
}

IndieWebRing

{
    "type": "entry",
    "author": {
        "name": "<span class='p-author h-card'>Kh\u00fcrt Williams</span>",
        "url": "https://islandinthenet.com/",
        "photo": null
    },
    "url": "https://islandinthenet.com/indiewebring/",
    "published": "2018-11-07T14:50:32+00:00",
    "content": {
        "html": "<p>Added IndieWebring code to the title header for blog posts.</p>",
        "text": "Added IndieWebring code to the title header for blog posts."
    },
    "name": "IndieWebRing",
    "post-type": "article",
    "_id": "1365437",
    "_source": "242",
    "_is_read": true
}

Exploring queries for private feeds

{
    "type": "entry",
    "published": "2018-11-06T23:18:52+0000",
    "url": "https://seblog.nl/2018/11/06/3/exploring-queries-for-private-feeds",
    "category": [
        "indieweb",
        "private posts"
    ],
    "syndication": [
        "https://news.indieweb.org/en/seblog.nl/2018/11/06/3/exploring-queries-for-private-feeds"
    ],
    "name": "Exploring queries for private feeds",
    "content": {
        "text": "One of the discussions this weekend in Berlin was on the topic of private feeds. Martijn and Sven made great progress by implemeting a flow to fetch private pages using various endpoints for tokens and authentication.\nApart from the question how to fetch private feeds, there is also the question how to present private feeds. The easiest way is probably to give every user their own feed, containing only the private posts for them. They can separately follow your public feed, and your queries are easier.\nBut in line with Silo\u2019s like Twitter and Facebook, I think I would prefer presenting one feed, with both public and private posts, scoped for the authenticated user. When I described this to Aaron he said that he liked it, but that he didn\u2019t know where to begin with writing code that does that. I didn\u2019t either, but it made me want to explore the possibilities.\nOn a sidenote: this feed design also raises another problem, of how to signal to the user that they can see this post but no-one else. I leave that one for another time.\nDrawing rough lines around boxes\nBorrowing from Facebook, there are roughly four categories you can share content in:\n\npublic \u2013\u00a0These posts can be seen by anyone. This is the default on nearly all IndieWeb sites today.\n\nauthenticated \u2013 These posts can only been seen if you sign in, but, anyone can sign in. Facebook has this category and we can mimic that with IndieAuth, but it might not add that much value.\n\nfriends only \u2013 This is a big category on Facebook, and made possible by the friendslist, which is also a big feature on Facebook.\n\nselected audience \u2013\u00a0Facebook also allows you to pick your audience on a per-post basis. This can be done by either selecting individual users, or selecting lists, which can contain users.\nThere is also the possibility of excluding specific people or lists from posts, but that one is even more advanced, so I put it out of scope for this exploration.\nThe first category is easy, for we already have it. The second category is harder, but once you got past the authentication it\u2019s easy again. One could query a database for visibility = 'authenticated' OR visibility = 'public', that would work.\nThe third category would require us to keep a list of friends. The fourth category could also require us to keep lists of people, so it might be better to merge them.\nThrow in some tables\nThis brings us to a simple database schema. I see three main tables: entries, people and groups, with a pivot table between all of them: entry_group, entry_person and group_person. I have chosen \u2018people\u2019 over \u2018users\u2019, because I might not want to give these people write access to anything, but they could be users as well.\nIt should work like this:\nEntries have a field for visibility, which can me marked public, authenticated or private.\nPeople can belong to groups, which have names. Think \u2018Friends\u2019, \u2018Family\u2019 and \u2018Coworkers\u2019.\nEntries can be opened up to individual people, or for a whole group.\nThere might be better ways of naming these, but I like the simplicity of this model. With private posts and audiences, I will always have to manage some form of lists, and this is the most simple way of doing it.\nEnter the monster query\nSo, with some trial and error, PHPUnit tests, and a lot of Laravel magic I came to the following monster query for these tables:\n(\n  select `entries`.* \n  from `groups` \n  inner join `group_person` \n    on `groups`.`id` = `group_person`.`group_id` \n  inner join `entry_group` \n    on `groups`.`id` = `entry_group`.`group_id` \n  inner join `entries` \n    on `entries`.`id` = `entry_group`.`entry_id` \n  where `group_person`.`person_id` = ?\n) \nunion \n(\n  select `entries`.* \n  from `entries` \n  inner join `entry_person` \n    on `entries`.`id` = `entry_person`.`entry_id` \n  where `entry_person`.`person_id` = ?\n) \nunion \n(\n  select * \n  from `entries` \n  where `visibility` = 'public'\n) \norder by `published_at` desc\n... which is way shorter when expressed in with Laravel\u2019s Eloquent:\nclass Person extends Model\n{\n    public function timeline()\n    {\n        return $this->groups()\n            ->join('entry_group', 'groups.id', '=', 'entry_group.group_id')\n            ->join('entries', 'entries.id', '=', 'entry_group.entry_id')\n            ->select('entries.*')\n            ->union($this->entries()->select('entries.*'))\n            ->union(Entry::whereVisibility('public'))\n            ->orderBy('published_at', 'desc');\n    }\n\n    public function groups()\n    {\n        return $this->belongsToMany(Group::class);\n    }\n\n    public function entries()\n    {\n        return $this->belongsToMany(Entry::class);\n    }\n}\nSince the method timeline() returns the Query object, other where-clauses can be appended when needed.\nI am in a bit of a fight with Laravel still, for it adds\n\n'`group_person`.`person_id` as `pivot_person_id`, `group_person`.`group_id` as `pivot_group_id`' to the first query, which makes it blow up, but the raw query works!\nThere is possibly a better way of doing it, but this is a start! Feel free to steal or improve, but if you improve, let me know.",
        "html": "<p>One of the discussions this weekend in <a href=\"https://indieweb.org/2018/Berlin\">Berlin</a> was on the topic of private feeds. <a href=\"https://vanderven.se/martijn/\">Martijn</a> and <a href=\"https://svenknebel.de\">Sven</a> made great progress by implemeting a flow to fetch private pages using <a href=\"https://indieweb.org/2018/Nuremberg/autoauth\">various endpoints for tokens and authentication</a>.</p>\n<p>Apart from the question how to fetch private feeds, there is also the question how to present private feeds. The easiest way is probably to give every user their own feed, containing only the private posts for them. They can separately follow your public feed, and your queries are easier.</p>\n<p>But in line with Silo\u2019s like Twitter and Facebook, I think I would prefer presenting one feed, with both public and private posts, scoped for the authenticated user. When I described this to <a href=\"https://aaronparecki.com\">Aaron</a> he said that he liked it, but that he didn\u2019t know where to begin with writing code that does that. I didn\u2019t either, but it made me want to explore the possibilities.</p>\n<p>On a sidenote: this feed design also raises another problem, of how to signal to the user that they can see this post but no-one else. I leave that one for another time.</p>\n<h2>Drawing rough lines around boxes</h2>\n<p>Borrowing from Facebook, there are roughly four categories you can share content in:</p>\n<ol><li>\n<em>public</em> \u2013\u00a0These posts can be seen by anyone. This is the default on nearly all IndieWeb sites today.</li>\n<li>\n<em>authenticated</em> \u2013 These posts can only been seen if you sign in, but, anyone can sign in. Facebook has this category and we can mimic that with IndieAuth, but it might not add that much value.</li>\n<li>\n<em>friends only</em> \u2013 This is a big category on Facebook, and made possible by the friendslist, which is also a big feature on Facebook.</li>\n<li>\n<em>selected audience</em> \u2013\u00a0Facebook also allows you to pick your audience on a per-post basis. This can be done by either selecting individual users, or selecting lists, which can contain users.</li>\n</ol><p>There is also the possibility of excluding specific people or lists from posts, but that one is even more advanced, so I put it out of scope for this exploration.</p>\n<p>The first category is easy, for we already have it. The second category is harder, but once you got past the authentication it\u2019s easy again. One could query a database for <code>visibility = 'authenticated' OR visibility = 'public'</code>, that would work.</p>\n<p>The third category would require us to keep a list of friends. The fourth category could also require us to keep lists of people, so it might be better to merge them.</p>\n<h2>Throw in some tables</h2>\n<p>This brings us to a simple database schema. I see three main tables: <code>entries</code>, <code>people</code> and <code>groups</code>, with a pivot table between all of them: <code>entry_group</code>, <code>entry_person</code> and <code>group_person</code>. I have chosen \u2018people\u2019 over \u2018users\u2019, because I might not want to give these people write access to anything, but they could be users as well.</p>\n<p>It should work like this:</p>\n<ul><li>Entries have a field for <code>visibility</code>, which can me marked <code>public</code>, <code>authenticated</code> or <code>private</code>.</li>\n<li>People can belong to groups, which have names. Think \u2018Friends\u2019, \u2018Family\u2019 and \u2018Coworkers\u2019.</li>\n<li>Entries can be opened up to individual people, or for a whole group.</li>\n</ul><p>There might be better ways of naming these, but I like the simplicity of this model. With private posts and audiences, I will always have to manage some form of lists, and this is the most simple way of doing it.</p>\n<h2>Enter the monster query</h2>\n<p>So, with some trial and error, PHPUnit tests, and a lot of Laravel magic I came to the following monster query for these tables:</p>\n<pre><code>(\n  select `entries`.* \n  from `groups` \n  inner join `group_person` \n    on `groups`.`id` = `group_person`.`group_id` \n  inner join `entry_group` \n    on `groups`.`id` = `entry_group`.`group_id` \n  inner join `entries` \n    on `entries`.`id` = `entry_group`.`entry_id` \n  where `group_person`.`person_id` = ?\n) \nunion \n(\n  select `entries`.* \n  from `entries` \n  inner join `entry_person` \n    on `entries`.`id` = `entry_person`.`entry_id` \n  where `entry_person`.`person_id` = ?\n) \nunion \n(\n  select * \n  from `entries` \n  where `visibility` = 'public'\n) \norder by `published_at` desc</code></pre>\n<p>... which is way shorter when expressed in with Laravel\u2019s Eloquent:</p>\n<pre><code>class Person extends Model\n{\n    public function timeline()\n    {\n        return $this-&gt;groups()\n            -&gt;join('entry_group', 'groups.id', '=', 'entry_group.group_id')\n            -&gt;join('entries', 'entries.id', '=', 'entry_group.entry_id')\n            -&gt;select('entries.*')\n            -&gt;union($this-&gt;entries()-&gt;select('entries.*'))\n            -&gt;union(Entry::whereVisibility('public'))\n            -&gt;orderBy('published_at', 'desc');\n    }\n\n    public function groups()\n    {\n        return $this-&gt;belongsToMany(Group::class);\n    }\n\n    public function entries()\n    {\n        return $this-&gt;belongsToMany(Entry::class);\n    }\n}</code></pre>\n<p>Since the method <code>timeline()</code> returns the Query object, other where-clauses can be appended when needed.</p>\n<p>I am in a bit of a fight with Laravel still, for it adds<br />\n'`group_person`.`person_id` as `pivot_person_id`, `group_person`.`group_id` as `pivot_group_id`' to the first query, which makes it blow up, but the raw query works!</p>\n<p>There is possibly a better way of doing it, but this is a start! Feel free to steal or improve, but if you improve, let me know.</p>"
    },
    "post-type": "article",
    "_id": "1367147",
    "_source": "1366",
    "_is_read": true
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2018-11-06 09:05-0800",
    "url": "http://tantek.com/2018/310/t2/great-speakers-a11yclub-talks",
    "category": [
        "indieweb",
        "a11yclub",
        "HTMLfirst",
        "a11y",
        "2018_309"
    ],
    "content": {
        "text": "Yesterday: Great speakers @a11yclub (8/9 with blog, 7/9 on own #indieweb site)\nInformative & thought provoking #a11yclub talks.\nThanks @LeonieWatson @hdv for posting slides, especially Leonie with HTML slides: http://decks.tink.uk/2018/a11yclub/\n#HTMLfirst #a11y #2018_309",
        "html": "Yesterday: Great speakers <a class=\"h-cassis-username\" href=\"https://twitter.com/a11yclub\">@a11yclub</a> (8/9 with blog, 7/9 on own #<span class=\"p-category\">indieweb</span> site)<br />Informative &amp; thought provoking #<span class=\"p-category\">a11yclub</span> talks.<br />Thanks <a class=\"h-cassis-username\" href=\"https://twitter.com/LeonieWatson\">@LeonieWatson</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/hdv\">@hdv</a> for posting slides, especially Leonie with HTML slides: <a href=\"http://decks.tink.uk/2018/a11yclub/\">http://decks.tink.uk/2018/a11yclub/</a><br />#<span class=\"p-category\">HTMLfirst</span> #<span class=\"p-category\">a11y</span> #<span class=\"p-category\">2018_309</span>"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "note",
    "_id": "1357027",
    "_source": "1",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2018-11-06T17:45:41Z",
    "url": "https://adactio.com/links/14492",
    "category": [
        "indieweb",
        "comic",
        "primer",
        "explanation",
        "drawing",
        "illustration",
        "webmention",
        "microsub",
        "relme"
    ],
    "bookmark-of": [
        "http://hag.codes/social/2018/11/05/indieweb-comic.html"
    ],
    "content": {
        "text": "How to get on the #indieweb!\n\n\n\nAs well as graciously hosting Indie Web Camp Berlin on the weekend at Mozilla\u2019s offices, Yulia has also drawn this super-cute comic.",
        "html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"http://hag.codes/social/2018/11/05/indieweb-comic.html\">\nHow to get on the #indieweb!\n</a>\n</h3>\n\n<p>As well as graciously hosting Indie Web Camp Berlin on the weekend at Mozilla\u2019s offices, Yulia has also drawn this super-cute comic.</p>"
    },
    "post-type": "bookmark",
    "_id": "1355867",
    "_source": "2",
    "_is_read": true
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2018-11-06 03:29-0800",
    "url": "http://tantek.com/2018/310/t1/beautiful-comic-indieweb",
    "category": [
        "indieweb"
    ],
    "in-reply-to": [
        "http://hag.codes/social/2018/11/05/indieweb-comic.html"
    ],
    "content": {
        "text": "Beautiful comic by @ioctaptceb!\n\u201cHow to get on the #indieweb\u201d\nhttp://hag.codes/social/2018/11/05/indieweb-comic.html",
        "html": "Beautiful comic by <a class=\"h-cassis-username\" href=\"https://twitter.com/ioctaptceb\">@ioctaptceb</a>!<br />\u201cHow to get on the #<span class=\"p-category\">indieweb</span>\u201d<br />http://hag.codes/social/2018/11/05/indieweb-comic.html"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "reply",
    "refs": {
        "http://hag.codes/social/2018/11/05/indieweb-comic.html": {
            "type": "entry",
            "url": "http://hag.codes/social/2018/11/05/indieweb-comic.html",
            "name": "hag.codes\u2019s post",
            "post-type": "article"
        }
    },
    "_id": "1352525",
    "_source": "1",
    "_is_read": true
}

Marty McGuire

{
    "type": "entry",
    "published": "2018-11-06T04:02:28-05:00",
    "url": "https://martymcgui.re/2018/11/06/040228/",
    "category": [
        "IndieWeb",
        "comic"
    ],
    "content": {
        "text": "Oh gosh this IndieWeb comic by yulia is simply delightful:\nhttp://hag.codes/social/2018/11/05/indieweb-comic.html",
        "html": "<p>Oh gosh this IndieWeb comic by <a href=\"http://hag.codes/\">yulia</a> is simply delightful:</p>\n<p><a href=\"http://hag.codes/social/2018/11/05/indieweb-comic.html\">http://hag.codes/social/2018/11/05/indieweb-comic.html</a></p>"
    },
    "author": {
        "type": "card",
        "name": "Marty McGuire",
        "url": false,
        "photo": "https://aperture-proxy.p3k.io/8275f85e3a389bd0ae69f209683436fc53d8bad9/68747470733a2f2f6d617274796d636775692e72652f696d616765732f6c6f676f2e6a7067"
    },
    "post-type": "note",
    "_id": "1352003",
    "_source": "175",
    "_is_read": true
}

Kevin Marks known.kevinmarks.com/profile/kevinmarks

sending webmentions for all links in mention.tech #indieweb #yesvember

{
    "type": "entry",
    "published": "2018-11-06T02:53:56+0000",
    "url": "http://known.kevinmarks.com/2018/sending-webmentions-for-all-links-in-mentiontech-indieweb-yesvember",
    "name": "sending webmentions for all links in mention.tech #indieweb #yesvember",
    "content": {
        "text": "A while back I built\u00a0mention.tech\u00a0which is a webmention sending tool with a couple of differences - you\u00a0can set it as your webmention endpoint, and it will pass through webmentions, but it will also cache the mentions itself, in case the linked URL doesn't have an endpoint.What it didn't have was a way to look for all outbound mentions and send them for a post, so I added that tonight. It may need to work more carefully wiht h-feeds, but with an h-entry it should be OK.Try it out at\u00a0mention.tech/mentionall\u00a0",
        "html": "<p>A while back I built\u00a0<a href=\"https://mention.tech/\">mention.tech</a>\u00a0which is a webmention sending tool with a couple of differences - you\u00a0can set it as your webmention endpoint, and it will pass through webmentions, but it will also <a href=\"https://mention.tech/listmentions?target=https%3A%2F%2Fmention.tech%2Fmentionall\">cache the mentions itself</a>, in case the linked URL doesn't have an endpoint.</p><p>What it didn't have was a way to look for all outbound mentions and send them for a post, so I added that tonight. It may need to work more carefully wiht h-feeds, but with an h-entry it should be OK.</p><p>Try it out at\u00a0<a href=\"https://mention.tech/mentionall\">mention.tech/mentionall</a></p><p>\u00a0</p>"
    },
    "author": {
        "type": "card",
        "name": "Kevin Marks",
        "url": "http://known.kevinmarks.com/profile/kevinmarks",
        "photo": "https://aperture-proxy.p3k.io/ed7979fd10a648fc253eae0b54e66fb36e57d3d4/687474703a2f2f6b6e6f776e2e6b6576696e6d61726b732e636f6d2f66696c652f3932353536353636363931373362373836376162383339656536353536663965"
    },
    "post-type": "article",
    "_id": "1350046",
    "_source": "205",
    "_is_read": true
}

2018-11-05 20.40.51

{
    "type": "entry",
    "author": {
        "name": "Kh\u00fcrt Williams",
        "url": "https://islandinthenet.com/",
        "photo": null
    },
    "url": "https://islandinthenet.com/2018-11-05-20-40-51/",
    "published": "2018-11-06T01:40:51+00:00",
    "content": {
        "html": "<p>Test 1 Test 2 Test 3 Test 4 Test 5 Test 6 Test 7 Test 8 Test 9 Test 10 Test 11 Test 12 Test 13 Test 14 Test 15 Test 16 Test 17 Test 18 Test 19 Test 20 Test 21 Test 22 Test 23 https://webmention.rocks/update/1/part/2</p>",
        "text": "Test 1 Test 2 Test 3 Test 4 Test 5 Test 6 Test 7 Test 8 Test 9 Test 10 Test 11 Test 12 Test 13 Test 14 Test 15 Test 16 Test 17 Test 18 Test 19 Test 20 Test 21 Test 22 Test 23 https://webmention.rocks/update/1/part/2"
    },
    "name": "2018-11-05 20.40.51",
    "post-type": "article",
    "_id": "1349419",
    "_source": "242",
    "_is_read": true
}

{
    "type": "entry",
    "author": {
        "name": null,
        "url": "https://www.manton.org/",
        "photo": null
    },
    "url": "https://www.manton.org/2018/11/05/223922.html",
    "content": {
        "html": "<p>No matter what happens tomorrow, the next day there will still be work to do on Micro.blog and the IndieWeb. Join us Wednesday for Homebrew Website Club in Austin. 6:30pm at Mozart\u2019s Coffee!</p>",
        "text": "No matter what happens tomorrow, the next day there will still be work to do on Micro.blog and the IndieWeb. Join us Wednesday for Homebrew Website Club in Austin. 6:30pm at Mozart\u2019s Coffee!"
    },
    "published": "2018-11-05T14:39:22-08:00",
    "post-type": "note",
    "_id": "1349072",
    "_source": "12",
    "_is_read": true
}

Testing Webmentions

{
    "type": "entry",
    "author": {
        "name": "Kh\u00fcrt Williams",
        "url": "https://islandinthenet.com/",
        "photo": null
    },
    "url": "https://islandinthenet.com/testing-webmentions-2/",
    "published": "2018-11-05T23:19:48+00:00",
    "content": {
        "html": "<p>Testing 1, 2, 3. Test 1 Test 2 Test 3 Test 4 Test 5 Test 6 Test 7 Test 8 Test 9 Test 10 Test 11 Test 12 Test 13 Test 14 Test 15 Test 16 Test 17 Test 18 Test 19 Test 20 Test 21 Test 22 Test 23</p>",
        "text": "Testing 1, 2, 3. Test 1 Test 2 Test 3 Test 4 Test 5 Test 6 Test 7 Test 8 Test 9 Test 10 Test 11 Test 12 Test 13 Test 14 Test 15 Test 16 Test 17 Test 18 Test 19 Test 20 Test 21 Test 22 Test 23"
    },
    "name": "Testing Webmentions",
    "post-type": "article",
    "_id": "1348478",
    "_source": "242",
    "_is_read": true
}

Testing Webmentions

{
    "type": "entry",
    "author": {
        "name": "Kh\u00fcrt Williams",
        "url": "https://islandinthenet.com/",
        "photo": null
    },
    "url": "https://islandinthenet.com/testing-webmentions/",
    "published": "2018-11-05T23:02:56+00:00",
    "content": {
        "html": "<p>Argh!</p>",
        "text": "Argh!"
    },
    "name": "Testing Webmentions",
    "post-type": "article",
    "_id": "1348479",
    "_source": "242",
    "_is_read": true
}

2018-11-05 17.57.53

{
    "type": "entry",
    "author": {
        "name": "Kh\u00fcrt Williams",
        "url": "https://islandinthenet.com/",
        "photo": null
    },
    "url": "https://islandinthenet.com/2018-11-05-17-57-53/",
    "published": "2018-11-05T22:57:53+00:00",
    "content": {
        "html": "<p>Jacky, if you abandon Isso, how will your new website support comments for people who don\u2019t have their own website or who are not using a platform (blogger, Tumblr, wordpress.com) that supports webmentions?</p>",
        "text": "Jacky, if you abandon Isso, how will your new website support comments for people who don\u2019t have their own website or who are not using a platform (blogger, Tumblr, wordpress.com) that supports webmentions?"
    },
    "name": "2018-11-05 17.57.53",
    "post-type": "article",
    "_id": "1348480",
    "_source": "242",
    "_is_read": true
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2018-11-04 08:00-0800",
    "url": "http://tantek.com/2018/308/t2/indiewebcamp-archive-navigation-day-archives",
    "category": [
        "IndieWebCamp",
        "indieweb"
    ],
    "content": {
        "text": "At #IndieWebCamp @MozillaBerlin, coded some archive navigation in @Falcon: sequential previous/next navigation across day archives. More to do, like link from home page to more entries, skip days without posts, but happy with progress. \n\nNext steps: https://indieweb.org/Falcon#archive_pages\n\nRelated #indieweb pages:\n* https://indieweb.org/navigation\n* https://indieweb.org/pagination\n* https://indieweb.org/archive_navigation",
        "html": "At #<span class=\"p-category\">IndieWebCamp</span> <a class=\"h-cassis-username\" href=\"https://twitter.com/MozillaBerlin\">@MozillaBerlin</a>, coded some archive navigation in <a class=\"h-cassis-username\" href=\"https://twitter.com/Falcon\">@Falcon</a>: sequential previous/next navigation across day archives. More to do, like link from home page to more entries, skip days without posts, but happy with progress. <br /><br />Next steps: <a href=\"https://indieweb.org/Falcon#archive_pages\">https://indieweb.org/Falcon#archive_pages</a><br /><br />Related #<span class=\"p-category\">indieweb</span> pages:<br />* <a href=\"https://indieweb.org/navigation\">https://indieweb.org/navigation</a><br />* <a href=\"https://indieweb.org/pagination\">https://indieweb.org/pagination</a><br />* <a href=\"https://indieweb.org/archive_navigation\">https://indieweb.org/archive_navigation</a>"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "note",
    "_id": "1337007",
    "_source": "1",
    "_is_read": true
}