Marty McGuire martymcgui.re

Micropub for a static Neocities website

{
    "type": "entry",
    "published": "2018-03-12T13:04:55-0400",
    "url": "https://martymcgui.re/2018/03/12/130455/",
    "category": [
        "IndieWeb",
        "ghostparty",
        "glitch",
        "neocities",
        "micropub",
        "IndieAuth"
    ],
    "syndication": [
        "https://twitter.com/schmarty/status/973249205270704133",
        "https://www.facebook.com/marty.mcguire.54/posts/10211595313620390?comment_id=10211596218443010"
    ],
    "name": "Micropub for a static Neocities website",
    "content": {
        "text": "This post gives more technical detail for the recent talk that I gave at Bring-a-Hack NYC. In it, I describe a system that copies posts from Ghost Party's Instagram automatically to the Ghost Party Website at ghostparty.today.\nThis roughly works like so:\n\n    OwnYourGram periodically checks our Instagram for new images\n    \n\n  For each new post, it makes a Micropub request to a service that I wrote for this purpose.\n  The endpoint accepts the image files and uploads them to our site using the Neocities API. Then it creates some new HTML from the micropub post data, edits the site's main index.html page to include the content, then uploads it back to Neocities.\nAuthorization with IndieAuth\nOne missing step in that rough outline is the bit where we tell OwnYourGram *how* to post to our site via Micropub, as well as making sure that OwnYourGram can prove that we have given it permission to post there. Many Micropub clients support IndieAuth as a way to do this permission-granting step (known as authorization). With a typical personal website, I'd delegate this process to indieauth.com, which lets you offload the step of \"proving\" that you own the website where you're trying to post by instead letting you log into an existing social network account.\nghostparty.today is a shared website, so I thought a simpler way to approach this would be to create a custom authorization endpoint that accepts a password. I could give this password to other GHOST PARTY folks and they can post whatever they like.\nSome nice folks in the IndieWeb community had already created an authorization endpoint that works this way, called selfauth. I created a pretty simplistic port of selfauth from PHP to JavaScript using NodeJS on the awesome Glitch social code hosting platform. It needs some more robust error checking, and some micropub clients seem to have trouble with it, but it works with OwnYourGram and Quill, so it's Good Enough for now!\nEnter the password to get authorized!If you're interested, you can find the source for this endpoint here: https://glitch.com/edit/#!/befitting-price\nMicropub Endpoint\nFinally, there's the Micropub endpoint itself. I based mine off of this Glitch micropub project, created by Adam Bachman at IndieWebCamp Baltimore this year. Specfically, I took the bits that verify the access token. From there, it was a matter of stumbling through various bits of handling a Micropub post, pulling in extra libraries as I needed them. I slowly added support for saving uploaded files to our Neocities site via the Neocities API, then for generating an HTML snippet for the new post, and finally for adding the post to the site's main page.\nThe process for adding the generated post content to the site itself is extremely retro. The Micropub endpoint actually downloads the HTML from https://ghostparty.today/index.html. Inside there is a comment that looks like:\n<!-- NEW POSTS BELOW -->\nSo the new contents for index.html is everything before the comment, the comment, the new content, and then everything after the comment. Once that's constructed, the endpoint uploads index.html back to Neocities with the new contents.\n\n  You can find the source for the Micropub endpoint here: https://glitch.com/edit/#!/prism-dirt\n  \n\nIt should be possible to fork the project on Glitch and configure it to work with your own Neocities site! You'll need to use cURL with the Neocities API to generate an authorization token to configure the app, rather than saving username and password info in the project!\nMaking ghostparty.today \"IndieWeb-Readable\"\nThe GHOST PARTY site follows an extremely old-school publishing model where each post only exists as a small section of HTML on a single long page. This complicates things a bit because interacting with posts on the IndieWeb typically requires three things:\n\n    A machine-readable \"identity\" h-card that says \"who\" this website is, including a logo, the site name, canonical URL.\n    \n\n  A machine-readable feed that contains new posts, allowing people to follow our updates in their favorite indie reader.\n  A separate permalink URL for each post, containing machine-readable info about that post, allowing other IndieWeb sites to \"understand\" the content when they want to RSVP to events, repost or like photos, and more.\nMicroformats2 parsers like X-Ray do a great job at parsing HTML page into meaningful data, but the programs that use the parsed data usually stop at the first thing they find. So, if I ask X-Ray to parse https://ghostparty.today/, this is what it sees:\n{\n  \"data\":{\n    \"type\":\"card\",\n    \"name\":\"GHOST PARTY\",\n    \"url\":\"https://ghostparty.today/\",\n    \"photo\":\"https://ghostparty.neocities.org/ghost-party-logo.png\"\n  },\n  \"url\":\"https://ghostparty.today/\",\n  \"code\":200\n}\nThis is great in that it contains the \"identity\" information that we want the page to have. However, that page also has a feed! How can I get at that? By telling X-Ray to only look at a fragment of the page! Here's how X-Ray sees https://ghostparty.today/#feed: \n{\n  \"data\":{\n    \"type\":\"feed\",\n    \"items\":[\n      {\n        \"type\":\"entry\",\n        \"published\":\"2018-03-07T16:44:16+00:00\",\n        \"url\":\"https://ghostparty.today/#2018-03-07-181020\",\n        \"photo\":[\"https://ghostparty.today/uploads/2018-03-07/181020-ig0LN1JG.jpg\"],\n        \"content\":{\"text\":\"snow day selfie #snowday #snowfie #ghoststories\"} \n      },\n      {\n        \"type\":\"entry\",\n        ...\n      },\n      ...\n    ],\n    \"url\":\"https://ghostparty.today/#feed\",\n    \"code\":200,\n    \"info\":{\"found_fragment\":true}\n  }\n}\n\n  Data! Nice! So if we want to follow ghostparty.today with an indie reader, we use https://ghostparty.today/#feed as the URL.\n  \n\nLooking at the content of the feed, you'll notice that the individual items have a url property which also has a fragment ID in the URL. This allows IndieWeb sites to interact with a particular post, even though it's one of many on the same page. For example, I was able to create an RSVP post to the most recent Ghost Party show, and (by looking just at the content in the fragment at https://ghostparty.today/#show-2018-02-14) my site was able to pick up the machine-readable details about the event to display them on my own site.\nThe microformats markup for the h-card and h-feed are built into the index.html file itself and don't change very often. However, for each new micropub post we need to convert those properties into a chunk of HTML for the index.html page that also contains the microformats h-entry markup. To do this, I made this Handlebars template:\n<div class=\"h-entry\" id=\"{{ mp-slug }}\">\n  <a class=\"u-author\" href=\"/\"></a>\n  <a class=\"u-url\" href=\"#{{ mp-slug }}\">{{#if name}}<h2 class=\"p-name\">{{ name }}</h2>{{/if}}</a>\n  <time class=\"dt-published\" datetime=\"{{ published }}\"></time>\n  {{#if video}}\n    {{#each video}}\n      <video controls loop class=\"u-video\" src=\"{{ . }}\"></video>\n    {{/each}}\n  {{ else }}\n    {{#each photo}}\n      <img class=\"u-photo\" src=\"{{ . }}\" />\n    {{/each}}\n    {{#each audio}}\n      <audio class=\"u-audio\" src=\"{{ . }}\"></audio>\n    {{/each}}\n  {{/if}}\n  <div class=\"e-content\">{{ content }}</div>\n</div>\n<img src=\"ghosts.gif\" />\n\nNot so bad!\nResources\nHere's a collection of some of the other libraries and docs I used to pull this thing together:\n\n    Neocities API\n    Includes details on using cURL to get an authorization token.\n      There\u2019s a Node module for the Neocities API, but it uses username and passwords, so I just used regular HTTP requests to handle talking to Neocities.\n    \n  \n    Node Request HTTP Client\n    Verifies the authorization token by querying the token endpoint (I used tokens.indieauth.com for this)\n      Handles uploading files like images to Neocities via their API.\n      Used to fetch index.html from the site and later to writes it back via Neocities API.\n    \n  \n    ES6 Promises\n    There's a lot of asynchronous code that waits for network requests. This code is very Promise-heavy to handle that.\n    \n  \n    Handlebars templating\n    Made it easy to take the Micropub properties for a new post and rendered them into HTML content with microformats.\n    \n  \n    Express 4 API\n    Glitch uses Node and Express 4 by default, and I got to learn lots about it!\n    \n  \n    Multer Express Middleware\n    For handling uploaded files\n    \n  \n    Body Parser Express Middleware\n    For handling regular Micropub properties\n    \n  \n    Validator.js\n    Half-using this for the authorization endpoint, need to clean it up and finish it up!\n    \n  \n    OwnYourGram API docs\n    Shows what properties are sent over Micropub, so you know exactly the kind of data your Micropub endpoint will need to handle.",
        "html": "<p>This post gives more technical detail for the <a href=\"https://martymcgui.re/2018/03/12/110809/\">recent talk that I gave at Bring-a-Hack NYC</a>. In it, I describe a system that copies posts from <a href=\"https://www.instagram.com/ghostpartyimprov/\">Ghost Party's Instagram</a> automatically to the <a href=\"https://ghostparty.today/\">Ghost Party Website at ghostparty.today</a>.</p>\n<p>This roughly works like so:</p>\n<ul><li>\n    <a href=\"https://ownyourgram.com/\">OwnYourGram</a> periodically checks our Instagram for new images\n    <br /></li>\n  <li>For each new post, it makes a <a href=\"https://indieweb.org/Micropub\">Micropub</a> request to a service that I wrote for this purpose.</li>\n  <li>The endpoint accepts the image files and uploads them to our site using the Neocities API. Then it creates some new HTML from the micropub post data, edits the site's main index.html page to include the content, then uploads it back to Neocities.</li>\n</ul><h2>Authorization with IndieAuth</h2>\n<p>One missing step in that rough outline is the bit where we tell OwnYourGram *how* to post to our site via Micropub, as well as making sure that OwnYourGram can prove that we have given it permission to post there. Many Micropub clients support <a href=\"https://indieweb.org/IndieAuth\">IndieAuth</a> as a way to do this permission-granting step (known as authorization). With a typical personal website, I'd delegate this process to <a href=\"https://indieauth.com/\">indieauth.com</a>, which lets you offload the step of \"proving\" that you own the website where you're trying to post by instead letting you log into an existing social network account.</p>\n<p>ghostparty.today is a shared website, so I thought a simpler way to approach this would be to create a custom authorization endpoint that accepts a password. I could give this password to other GHOST PARTY folks and they can post whatever they like.</p>\n<p>Some nice folks in the IndieWeb community had already created an authorization endpoint that works this way, called <a href=\"https://github.com/Inklings-io/selfauth\">selfauth</a>. I created a pretty simplistic port of selfauth from PHP to JavaScript using NodeJS on the awesome <a href=\"https://glitch.com/\">Glitch social code hosting platform</a>. It needs some more robust error checking, and some micropub clients seem to have trouble with it, but it works with OwnYourGram and <a href=\"https://quill.p3k.io/\">Quill</a>, so it's Good Enough for now!</p>\n<img src=\"https://aperture-media.p3k.io/media.martymcgui.re/bdbddadd6e6c4655bdc084b099c73340eefc5caf76d235ba7f403ac47ecc6730.png\" alt=\"Interface displaying text 'You are attempting to login as https://ghostparty.today/ with client https://quill.p3k.io/' along with a password prompt.\" />Enter the password to get authorized!<p>If you're interested, you can find the source for this endpoint here: <a href=\"https://glitch.com/edit/#!/befitting-price\">https://glitch.com/edit/#!/befitting-price</a></p>\n<h2>Micropub Endpoint</h2>\n<p>Finally, there's the Micropub endpoint itself. I based mine off of <a href=\"https://glitch.com/edit/#!/crocus-garlic\">this Glitch micropub project</a>, created by <a href=\"https://adambachman.org/\">Adam Bachman</a> at <a href=\"https://indieweb.org/2018/Baltimore\">IndieWebCamp Baltimore</a> this year. Specfically, I took the bits that verify the access token. From there, it was a matter of stumbling through various bits of handling a Micropub post, pulling in extra libraries as I needed them. I slowly added support for saving uploaded files to our Neocities site via the Neocities API, then for generating an HTML snippet for the new post, and finally for adding the post to the site's main page.</p>\n<p>The process for adding the generated post content to the site itself is extremely retro. The Micropub endpoint actually downloads the HTML from https://ghostparty.today/index.html. Inside there is a comment that looks like:</p>\n<pre>&lt;!-- NEW POSTS BELOW --&gt;</pre>\n<p>So the new contents for index.html is everything before the comment, the comment, the new content, and then everything after the comment. Once that's constructed, the endpoint uploads index.html back to Neocities with the new contents.</p>\n<p>\n  You can find the source for the Micropub endpoint here: <a href=\"https://glitch.com/edit/#!/prism-dirt\">https://glitch.com/edit/#!/prism-dirt</a>\n  <br /></p>\n<p>It should be possible to fork the project on Glitch and configure it to work with your own Neocities site! You'll need to use cURL with the Neocities API to generate an authorization token to configure the app, rather than saving username and password info in the project!</p>\n<h2>Making ghostparty.today \"IndieWeb-Readable\"</h2>\n<p>The GHOST PARTY site follows an extremely old-school publishing model where each post <i>only</i> exists as a small section of HTML on a single long page. This complicates things a bit because interacting with posts on the IndieWeb typically requires three things:</p>\n<ul><li>\n    A machine-readable \"identity\" <a href=\"https://indieweb.org/h-card\">h-card</a> that says \"who\" this website is, including a logo, the site name, canonical URL.\n    <br /></li>\n  <li>A machine-readable <a href=\"https://indieweb.org/h-feed\">feed</a> that contains new posts, allowing people to follow our updates in their favorite <a href=\"https://indieweb.org/reader\">indie reader</a>.</li>\n  <li>A separate permalink URL for each post, containing <a href=\"https://indieweb.org/h-entry\">machine-readable info about that post</a>, allowing other IndieWeb sites to \"understand\" the content when they want to RSVP to events, repost or like photos, and more.</li>\n</ul><p>Microformats2 parsers like <a href=\"https://xray.p3k.io/\">X-Ray</a> do a great job at parsing HTML page into meaningful data, but the programs that use the parsed data usually stop at the first thing they find. So, if I ask X-Ray to <a href=\"https://xray.p3k.io/parse?url=https%3A%2F%2Fghostparty.today%2F\">parse https://ghostparty.today</a>/, this is what it sees:</p>\n<pre>{\n  \"data\":{\n    \"type\":\"card\",\n    \"name\":\"GHOST PARTY\",\n    \"url\":\"https://ghostparty.today/\",\n    \"photo\":\"https://ghostparty.neocities.org/ghost-party-logo.png\"\n  },\n  \"url\":\"https://ghostparty.today/\",\n  \"code\":200\n}</pre>\n<p>This is great in that it contains the \"identity\" information that we want the page to have. However, that page also has a feed! How can I get at that? By telling X-Ray to only look at a <a href=\"https://www.w3.org/DesignIssues/Fragment.html\">fragment of the page</a>! Here's how X-Ray <a href=\"https://xray.p3k.io/parse?url=https%3A%2F%2Fghostparty.today%2F%23feed\">sees https://ghostparty.today/#feed</a>: </p>\n<pre>{\n  \"data\":{\n    \"type\":\"feed\",\n    \"items\":[\n      {\n        \"type\":\"entry\",\n        \"published\":\"2018-03-07T16:44:16+00:00\",\n        \"url\":\"https://ghostparty.today/#2018-03-07-181020\",\n        \"photo\":[\"https://ghostparty.today/uploads/2018-03-07/181020-ig0LN1JG.jpg\"],\n        \"content\":{\"text\":\"snow day selfie #snowday #snowfie #ghoststories\"} \n      },\n      {\n        \"type\":\"entry\",\n        ...\n      },\n      ...\n    ],\n    \"url\":\"https://ghostparty.today/#feed\",\n    \"code\":200,\n    \"info\":{\"found_fragment\":true}\n  }\n}</pre>\n<p>\n  Data! Nice! So if we want to follow ghostparty.today with an indie reader, we use <code>https://ghostparty.today/#feed</code> as the URL.\n  <br /></p>\n<p>Looking at the content of the feed, you'll notice that the individual items have a url property which <i>also</i> has a fragment ID in the URL. This allows IndieWeb sites to interact with a particular post, even though it's one of many on the same page. For example, I was able to <a href=\"https://martymcgui.re/2018/01/31/224122/\">create an RSVP post to the most recent Ghost Party show</a>, and (by looking just at the content in the fragment at <code>https://ghostparty.today/#show-2018-02-14</code>) my site was able to pick up the machine-readable details about the event to display them on my own site.</p>\n<p>The microformats markup for the h-card and h-feed are built into the index.html file itself and don't change very often. However, for each new micropub post we need to convert those properties into a chunk of HTML for the index.html page that <i>also</i> contains the microformats h-entry markup. To do this, I made <a href=\"https://glitch.com/edit/#!/prism-dirt?path=views/entry.handlebars:1:0\">this Handlebars template</a>:</p>\n<pre><code>&lt;div class=\"h-entry\" id=\"{{ mp-slug }}\"&gt;\n  &lt;a class=\"u-author\" href=\"/\"&gt;&lt;/a&gt;\n  &lt;a class=\"u-url\" href=\"#{{ mp-slug }}\"&gt;{{#if name}}&lt;h2 class=\"p-name\"&gt;{{ name }}&lt;/h2&gt;{{/if}}&lt;/a&gt;\n  &lt;time class=\"dt-published\" datetime=\"{{ published }}\"&gt;&lt;/time&gt;\n  {{#if video}}\n    {{#each video}}\n      &lt;video controls loop class=\"u-video\" src=\"{{ . }}\"&gt;&lt;/video&gt;\n    {{/each}}\n  {{ else }}\n    {{#each photo}}\n      &lt;img class=\"u-photo\" src=\"{{ . }}\" /&gt;\n    {{/each}}\n    {{#each audio}}\n      &lt;audio class=\"u-audio\" src=\"{{ . }}\"&gt;&lt;/audio&gt;\n    {{/each}}\n  {{/if}}\n  &lt;div class=\"e-content\"&gt;{{ content }}&lt;/div&gt;\n&lt;/div&gt;\n&lt;img src=\"ghosts.gif\" /&gt;\n</code></pre>\n<p>Not so bad!</p>\n<h2>Resources</h2>\n<p>Here's a collection of some of the other libraries and docs I used to pull this thing together:</p>\n<ul><li>\n    <a href=\"https://neocities.org/api\">Neocities API</a>\n    <ul><li>Includes details on using cURL to get an authorization token.</li>\n      <li>There\u2019s a <a href=\"https://github.com/neocities/neocities-node/blob/master/index.js\">Node module</a> for the Neocities API, but it uses username and passwords, so I just used regular HTTP requests to handle talking to Neocities.</li>\n    </ul></li>\n  <li>\n    <a href=\"https://github.com/request/request\">Node Request HTTP Client</a>\n    <ul><li>Verifies the authorization token by querying the token endpoint (I used tokens.indieauth.com for this)</li>\n      <li>Handles uploading files like images to Neocities via their API.</li>\n      <li>Used to fetch index.html from the site and later to writes it back via Neocities API.</li>\n    </ul></li>\n  <li>\n    <a href=\"http://www.datchley.name/es6-promises/\">ES6 Promises</a>\n    <ul><li>There's a lot of asynchronous code that waits for network requests. This code is very Promise-heavy to handle that.</li>\n    </ul></li>\n  <li>\n    <a href=\"http://handlebarsjs.com/block_helpers.html\">Handlebars templating</a>\n    <ul><li>Made it easy to take the Micropub properties for a new post and rendered them into HTML content with microformats.</li>\n    </ul></li>\n  <li>\n    <a href=\"https://expressjs.com/en/4x/api.html\">Express 4 API</a>\n    <ul><li>Glitch uses Node and Express 4 by default, and I got to learn lots about it!</li>\n    </ul></li>\n  <li>\n    <a href=\"https://expressjs.com/en/resources/middleware/multer.html\">Multer Express Middleware</a>\n    <ul><li>For handling uploaded files</li>\n    </ul></li>\n  <li>\n    <a href=\"https://expressjs.com/en/resources/middleware/body-parser.html\">Body Parser Express Middleware</a>\n    <ul><li>For handling regular Micropub properties</li>\n    </ul></li>\n  <li>\n    <a href=\"https://github.com/chriso/validator.js/tree/9.4.0\">Validator.js</a>\n    <ul><li>Half-using this for the authorization endpoint, need to clean it up and finish it up!</li>\n    </ul></li>\n  <li>\n    <a href=\"https://ownyourgram.com/docs\">OwnYourGram API docs</a>\n    <ul><li>Shows what properties are sent over Micropub, so you know exactly the kind of data your Micropub endpoint will need to handle.</li>\n    </ul></li>\n</ul>"
    },
    "author": {
        "type": "card",
        "name": "Marty McGuire",
        "url": "https://martymcgui.re/",
        "photo": "https://aperture-media.p3k.io/martymcgui.re/4f9fac2b9e3ae62998c557418143efe288bca8170a119921a9c6bfeb0a1263a2.jpg"
    },
    "_id": "127020",
    "_source": "175",
    "_is_read": true
}

Aaron Parecki aaronparecki.com

{
    "type": "entry",
    "published": "2018-03-12T11:11:57-0700",
    "url": "https://aaronparecki.com/2018/03/12/11/aperture",
    "category": [
        "aperture",
        "microsub",
        "indieweb"
    ],
    "content": {
        "text": "Just made Aperture download a cached copy of avatars and other media it finds in posts! Now the images will always be available over https, and images from old posts won't disappear!\n\nIf you're running your own copy of Aperture, it'll take an extra step of setting up a subdomain to serve the images from the storage folder. They're not served from the main domain for security reasons.",
        "html": "Just made Aperture download a cached copy of avatars and other media it finds in posts! Now the images will always be available over https, and images from old posts won't disappear!<br /><br />If you're running your own copy of Aperture, it'll take an extra step of setting up a subdomain to serve the images from the storage folder. They're not served from the main domain for security reasons."
    },
    "author": {
        "type": "card",
        "name": "Aaron Parecki",
        "url": "https://aaronparecki.com/",
        "photo": "https://aperture-media.p3k.io/aaronparecki.com/2b8e1668dcd9cfa6a170b3724df740695f73a15c2a825962fd0a0967ec11ecdc.jpg"
    },
    "_id": "126518",
    "_source": "16",
    "_is_read": true
}

Aaron Parecki aaronparecki.com

{
    "type": "entry",
    "published": "2018-03-12T10:51:04-0700",
    "url": "https://aaronparecki.com/2018/03/12/10/homebrew-microblog",
    "category": [
        "indieweb",
        "microblog"
    ],
    "photo": [
        "https://aperture-media.p3k.io/aaronparecki.com/ffd5f0365bcc141e2e70069945a6899ac2609ea34965c45820853ddaf9b9962d.jpg"
    ],
    "syndication": [
        "https://twitter.com/aaronpk/status/973255081519808512"
    ],
    "content": {
        "text": "Homebrew Website Club PDX is back, and joining forces with the Microbrew and Microblog meetup! Come to Rogue Eastside this Wednesday for the first \"Homebrew Microblog\"! https://indieweb.org/events/2018-03-14-homebrew-microblog #indieweb #microblog",
        "html": "Homebrew Website Club PDX is back, and joining forces with the Microbrew and Microblog meetup! Come to Rogue Eastside this Wednesday for the first \"Homebrew Microblog\"! <a href=\"https://indieweb.org/events/2018-03-14-homebrew-microblog\">https://indieweb.org/events/2018-03-14-homebrew-microblog</a> <a href=\"https://aaronparecki.com/tag/indieweb\">#indieweb</a> <a href=\"https://aaronparecki.com/tag/microblog\">#microblog</a>"
    },
    "author": {
        "type": "card",
        "name": "Aaron Parecki",
        "url": "https://aaronparecki.com/",
        "photo": "https://aperture-media.p3k.io/aaronparecki.com/2b8e1668dcd9cfa6a170b3724df740695f73a15c2a825962fd0a0967ec11ecdc.jpg"
    },
    "_id": "126467",
    "_source": "16",
    "_is_read": true
}

Marty McGuire martymcgui.re

A Ghost (Party) is Haunting the Silo'd Web

{
    "type": "entry",
    "published": "2018-03-12T11:08:09-0400",
    "url": "https://martymcgui.re/2018/03/12/110809/",
    "category": [
        "IndieWeb",
        "ghostparty",
        "micropub",
        "speaking"
    ],
    "syndication": [
        "https://twitter.com/schmarty/status/973219715907772416",
        "https://www.facebook.com/marty.mcguire.54/posts/10211595313620390"
    ],
    "name": "A Ghost (Party) is Haunting the Silo'd Web",
    "content": {
        "text": "This post is a rough summary of a lightning talk that I gave on February 28th at the Bring-A-Hack NYC with Hackaday + Ultimaker + New Lab. Many thanks to Shayna Gentiluomo for organizing and sometimes co-conspirator Matt Griffin for nudging me to speak!\nI have a lot of distrust for social silos like Facebook and Twitter which draw us in with the promise of connecting with family, friends, and interesting people, but I sometimes have trouble articulating that in a succinct way. Thankfully, I saw a perfect example this morning:\nPosting on the @facebook website is not working in Mac OS today. JavaScript eats CSS & HTML, making data entry field disappear except for a spookily disembodied close-box X. Been this way a few hours. \u2014 @zeldman, 9:53 AM - 28 Feb 2018\n\nSome Facebook team pushed an (untested?) update which broke the website, preventing some users from posting. \"Move fast and break things\". These silos don't value us or our content. So, we should get out. But what is the alternative?\nThe IndieWeb helps us take our content back, by posting to our own websites on our own domains. With some work, we can even get the benefits of these social networks and take our conversations with us. There\u2019s a whole lot of great stuff on the IndieWeb website, so go spend a couple of days reading it. But I\u2019m not here to talk about all those good things today. I\u2019m here to talk about how I used them to do a dumb hack.\n  \n\nghostparty.today is a website for Ghost Party \u2013 an improv project that has a ... certain aesthetic. Specifically the website was pitched as \u201cexactly like the Heaven\u2019s Gate website\u201d but we compromised on \u201cextreme Geocities\u201d.\n\nWe have an aesthetic.My Ghost Party co-host (co-ghost) built the first version of the site on Neocities.org, a lovely hosting provider that recaptures the feel of editing raw HTML directly in your browser. However, hand-editing HTML gets exhausting and sometimes you just want to post things to Instagram (and, of course,  Ghost Party has an Instagram).\nAnd Instagram is fine as a marketing platform! Lots of people look at it and like the pictures. But what about our website? Our aesthetic?\nMicropub is a standard (and now W3C Recommendation) designed over some years of practice from the IndieWeb community that defines a way for apps and clients to easily make new posts to any website (even yours) if it supports Micropub.\nI used Glitch, an amazing community and JavaScript-server-app hosting service, to make a simple micropub service for ghostparty.today.\n\nIt accepts posts via micropub, including file uploads, and uses the Neocities API (hey, it\u2019s not the 90s! Neocities has an API!) to upload the files to our website. Then, it fetches our site\u2019s index.html, adds the content of the new post, and uploads it back. You can find the source here on Glitch and fork it for your own purposes!\nNow that our site supports micropub, we can make use of a wonderful service called OwnYourGram. Once we give OwnYourGram permission to post to our site and read our Instagram feed, it will poll our Instagram account and copy each new post back to our website, where we can display it however we want.\nAestheticWe can go a step further, using an IndieWeb building block called Webmention and a service called brid.gy, to bring all of those responses, those Instagram and Facebook likes and comments, Twitter retweets, and more, back to our site for display.\nAnd to show how it works, here\u2019s a micropub client call Quill that works for any micropub-enabled site. Let\u2019s make a quick post, now!\nQuill's note interfaceOnce we hit the \"Post\" button and refresh the homepage, we can see the new post on the site!\nAestheticThis was the end of time time. I would have like to further encourage folks to check out Homebrew Website Clubs in their own communities, or to start one if they don't exist. They're part show-and-tell, part support group, and part mad science lab for people who love the web!",
        "html": "<p>This post is a rough summary of a lightning talk that I gave on February 28th at the <a href=\"https://hackaday.com/2018/02/23/next-week-bring-a-hack-in-nyc/\">Bring-A-Hack NYC with Hackaday + Ultimaker + New Lab</a>. Many thanks to Shayna Gentiluomo for organizing and sometimes co-conspirator <a href=\"https://mfgriffin.com/\">Matt Griffin</a> for nudging me to speak!</p>\n<p>I have a lot of distrust for social silos like Facebook and Twitter which draw us in with the promise of connecting with family, friends, and interesting people, but I sometimes have trouble articulating that in a succinct way. Thankfully, I saw a perfect example this morning:</p>\n<blockquote>Posting on the @facebook website is not working in Mac OS today. JavaScript eats CSS &amp; HTML, making data entry field disappear except for a spookily disembodied close-box X. Been this way a few hours. \u2014 <a href=\"https://twitter.com/zeldman\">@zeldman</a>, <a href=\"https://twitter.com/zeldman/status/968861672541708290\">9:53 AM - 28 Feb 2018</a>\n</blockquote>\n<p>Some Facebook team pushed an (untested?) update which broke the website, preventing some users from posting. \"Move fast and break things\". These silos don't value us or our content. So, we should get out. But what is the alternative?</p>\n<p>The <a href=\"https://indieweb.org/\">IndieWeb</a> helps us take our content back, by posting to our own websites on our own domains. With some work, we can even get the benefits of these social networks and take our conversations with us. There\u2019s a whole lot of great stuff on the IndieWeb website, so <a href=\"https://indieweb.org/Getting_Started\">go spend a couple of days reading it</a>. But I\u2019m not here to talk about all those good things today. I\u2019m here to talk about how I used them to do a dumb hack.\n  <br /></p>\n<p><a href=\"https://ghostparty.today/\">ghostparty.today</a> is a website for Ghost Party \u2013 an improv project that has a ... certain aesthetic. Specifically the website was pitched as \u201cexactly like the Heaven\u2019s Gate website\u201d but we compromised on \u201cextreme Geocities\u201d.</p>\n<p></p>\n<img src=\"https://media.martymcgui.re/09/a1/ac/48/9365fceee9147050b56175762179446084558b2611bec008d03146ed.png\" alt=\"Ugly large text says 'Welcome to GHOST PARTY'\" />We have an aesthetic.<p>My Ghost Party co-host (co-ghost) built the first version of the site on <a href=\"https://neocities.org/\">Neocities.org</a>, a lovely hosting provider that recaptures the feel of editing raw HTML directly in your browser. However, hand-editing HTML gets exhausting and sometimes you just want to post things to Instagram (and, of course,  <a href=\"https://instagram.com/ghostpartyimprov/\">Ghost Party has an Instagram</a>).</p>\n<p>And Instagram is fine as a marketing platform! Lots of people look at it and like the pictures. But what about our website? <i>Our aesthetic</i>?</p>\n<p><a href=\"https://indieweb.org/Micropub\">Micropub</a> is a standard (and now W3C Recommendation) designed over some years of practice from the IndieWeb community that defines a way for apps and clients to easily make new posts to any website (even yours) if it supports Micropub.</p>\n<p>I used <a href=\"https://glitch.com/\">Glitch</a>, an amazing community and JavaScript-server-app hosting service, to make a simple micropub service for ghostparty.today.</p>\n<p></p>\n<img src=\"https://media.martymcgui.re/9c/e4/3b/6a/2acaa5622a3129066fbe2cccae3e41bbaa56db82ff3d0eff51f9e2ed.png\" alt=\"Screenshot of code in the Glitch UI\" /><p>It accepts posts via micropub, including file uploads, and uses the Neocities API (hey, it\u2019s not the 90s! Neocities has an API!) to upload the files to our website. Then, it fetches our site\u2019s index.html, adds the content of the new post, and uploads it back. <a href=\"https://glitch.com/edit/#!/prism-dirt\">You can find the source here on Glitch and fork it for your own purposes</a>!</p>\n<p>Now that our site supports micropub, we can make use of a wonderful service called <a href=\"https://ownyourgram.com/\">OwnYourGram</a>. Once we give OwnYourGram permission to post to our site and read our Instagram feed, it will poll our Instagram account and copy each new post back to our website, where we can display it however we want.</p>\n<img src=\"https://media.martymcgui.re/2c/fe/90/e7/881eb3e2066c4fe6230eb7f6005921d22ff1691171c389dc92f2527f.png\" alt=\"Super simplified Instagram photo on Ghost Party website\" />Aesthetic<p>We can go a step further, using an IndieWeb building block called <a href=\"https://indieweb.org/Webmention\">Webmention</a> and a service called <a href=\"https://brid.gy/\">brid.gy</a>, to bring all of those responses, those Instagram and Facebook likes and comments, Twitter retweets, and more, back to our site for display.</p>\n<p>And to show how it works, here\u2019s a micropub client call <a href=\"https://quill.p3k.io/\">Quill</a> that works for any micropub-enabled site. Let\u2019s make a quick post, now!</p>\n<img src=\"https://media.martymcgui.re/50/c3/e5/91/56ecb23b74abdd71f8a31a41040a321dbd94b70b8da981dd954a11ae.png\" alt=\"Posting interface with 'Hello from New Lab' typed into note field\" />Quill's note interface<p>Once we hit the \"Post\" button and refresh the homepage, we can see the new post on the site!</p>\n<img src=\"https://media.martymcgui.re/82/0a/5e/fc/19b83c42948ee8517be2677de6f120ba374aeb0ed1d5343ba053409f.png\" alt=\"'Hello from New Lab' text with ghost separator image\" /><em>Aesthetic</em><p>This was the end of time time. I would have like to further encourage folks to check out <a href=\"https://indieweb.org/Homebrew_Website_Club\">Homebrew Website Club</a>s in their own communities, or to start one if they don't exist. They're part show-and-tell, part support group, and part mad science lab for people who love the web!</p>"
    },
    "author": {
        "type": "card",
        "name": "Marty McGuire",
        "url": "https://martymcgui.re/",
        "photo": "https://martymcgui.re/images/logo.jpg"
    },
    "_id": "126220",
    "_source": "175",
    "_is_read": true
}

Kartik Prabhu kartikprabhu.com/about#me

{
    "type": "entry",
    "published": "2018-03-11T23:30:08-0400",
    "url": "https://kartikprabhu.com/notes/re-citizen-of-indieweb",
    "category": [
        "indieweb",
        "indiewebcitizen"
    ],
    "syndication": [
        "https://twitter.com/kartik_prabhu/status/973044439135506432"
    ],
    "in-reply-to": [
        "https://collect.readwriterespond.com/citizen-of-indieweb/"
    ],
    "content": {
        "text": "To me it means: have a domain name and post content on it. Everything else is a bonus.\n\n#indieweb #indiewebcitizen"
    },
    "author": {
        "type": "card",
        "name": "Kartik Prabhu",
        "url": "https://kartikprabhu.com/about#me",
        "photo": "https://kartikprabhu.com/static/images/avatar.jpg"
    },
    "_id": "124974",
    "_source": "204",
    "_is_read": true
}

Eddie Hinkle eddiehinkle.com

A Citizen of the IndieWeb

{
    "type": "entry",
    "published": "2018-03-11T23:47:01-0400",
    "summary": "Aaron Davis asked the question",
    "url": "https://eddiehinkle.com/2018/03/11/9/article/",
    "category": [
        "indieweb",
        ""
    ],
    "name": "A Citizen of the IndieWeb",
    "author": {
        "type": "card",
        "name": "Eddie Hinkle",
        "url": "https://eddiehinkle.com/",
        "photo": "https://eddiehinkle.com/images/profile.jpg"
    },
    "_id": "124838",
    "_source": "226",
    "_is_read": true
}

Eddie Hinkle eddiehinkle.com

{
    "type": "entry",
    "published": "2018-03-11T21:07:19-0400",
    "summary": "Hey, I\u2019m sorry to hear you\u2019re having a hard time. If you haven\u2019t joined us on Slack/IRC, we love to help talking through things with people that are having a hard time, you can find the chat info here: https://indieweb.org/discuss",
    "url": "https://eddiehinkle.com/2018/03/11/8/reply/",
    "in-reply-to": [
        "https://twitter.com/downdb/status/972992691301576707"
    ],
    "content": {
        "text": "Hey, I\u2019m sorry to hear you\u2019re having a hard time. If you haven\u2019t joined us on Slack/IRC, we love to help talking through things with people that are having a hard time, you can find the chat info here: https://indieweb.org/discuss",
        "html": "<p>Hey, I\u2019m sorry to hear you\u2019re having a hard time. If you haven\u2019t joined us on Slack/IRC, we love to help talking through things with people that are having a hard time, you can find the chat info here: <a href=\"https://indieweb.org/discuss\">https://indieweb.org/discuss</a></p>"
    },
    "author": {
        "type": "card",
        "name": "Eddie Hinkle",
        "url": "https://eddiehinkle.com/",
        "photo": "https://eddiehinkle.com/images/profile.jpg"
    },
    "refs": {
        "https://twitter.com/downdb/status/972992691301576707": {
            "type": "entry",
            "url": "https://twitter.com/downdb/status/972992691301576707",
            "name": "https://twitter.com/downdb/status/972992691301576707"
        }
    },
    "_id": "124699",
    "_source": "226",
    "_is_read": true
}

Marty McGuire martymcgui.re

This Week in the IndieWeb Audio Edition • March 3rd - 9th, 2018

{
    "type": "entry",
    "published": "2018-03-10T15:37:55-0500",
    "url": "https://martymcgui.re/2018/03/10/153755/",
    "category": [
        "podcast",
        "IndieWeb",
        "this-week-indieweb-podcast"
    ],
    "audio": [
        "https://media.martymcgui.re/20/fc/78/e8/6ab36bca487d5c2d468116c65cbe05e2f95c0aeeedd6ccf0d1e56371.mp3"
    ],
    "syndication": [
        "https://huffduffer.com/schmarty/465175",
        "https://twitter.com/schmarty/status/972572891580682240",
        "https://www.facebook.com/marty.mcguire.54/posts/10211580886619724"
    ],
    "name": "This Week in the IndieWeb Audio Edition \u2022 March 3rd - 9th, 2018",
    "content": {
        "text": "Show/Hide Transcript  \n            \n            Audio edition for This Week in the IndieWeb for March 3rd - 9th, 2018.\n\nYou can find all of my audio editions and subscribe with your favorite podcast app here: martymcgui.re/podcasts/indieweb/.\n\nMusic from Aaron Parecki\u2019s 100DaysOfMusic project: Day 85 - Suit, Day 48 - Glitch, Day 49 - Floating, Day 9, and Day 11\n\nThanks to everyone in the IndieWeb chat for their feedback and suggestions. Please drop me a note if there are any changes you\u2019d like to see for this audio edition!",
        "html": "Show/Hide Transcript  \n            \n            <p>Audio edition for <a href=\"https://indieweb.org/this-week/2018-03-09.html\">This Week in the IndieWeb for March 3rd - 9th, 2018</a>.</p>\n\n<p>You can find all of my audio editions and subscribe with your favorite podcast app here: <a href=\"https://martymcgui.re/podcasts/indieweb/\">martymcgui.re/podcasts/indieweb/</a>.</p>\n\n<p>Music from <a href=\"https://aaronparecki.com/\">Aaron Parecki</a>\u2019s <a href=\"https://100.aaronparecki.com/\">100DaysOfMusic project</a>: <a href=\"https://aaronparecki.com/2017/03/15/14/day85\">Day 85 - Suit</a>, <a href=\"https://aaronparecki.com/2017/02/06/7/day48\">Day 48 - Glitch</a>, <a href=\"https://aaronparecki.com/2017/02/07/4/day49\">Day 49 - Floating</a>, <a href=\"https://aaronparecki.com/2016/12/29/21/day-9\">Day 9</a>, and <a href=\"https://aaronparecki.com/2016/12/31/15/\">Day 11</a></p>\n\n<p>Thanks to everyone in the <a href=\"https://chat.indieweb.org/\">IndieWeb chat</a> for their feedback and suggestions. Please drop me a note if there are any changes you\u2019d like to see for this audio edition!</p>"
    },
    "author": {
        "type": "card",
        "name": "Marty McGuire",
        "url": "https://martymcgui.re/",
        "photo": "https://martymcgui.re/images/logo.jpg"
    },
    "_id": "121418",
    "_source": "175",
    "_is_read": true
}

Jonathan LaCour cleverdevil.io/profile/cleverdevil

{
    "type": "entry",
    "published": "2018-03-10T05:01:01+0000",
    "url": "https://cleverdevil.io/2018/started-working-on-a-json-schema-for",
    "category": [
        "indieweb",
        "microformats2"
    ],
    "syndication": [
        "https://twitter.com/cleverdevil/status/972336503698460672"
    ],
    "content": {
        "text": "Started working on a JSON Schema for microformats2 about a week ago. Posted the first version on GitHub tonight \u2013 https://github.com/cleverdevil/microformats2 \u2013 Feedback welcome! #indieweb #microformats2",
        "html": "Started working on a JSON Schema for microformats2 about a week ago. Posted the first version on GitHub tonight \u2013 <a href=\"https://github.com/cleverdevil/microformats2\">https://github.com/cleverdevil/microformats2</a> \u2013 Feedback welcome! <a href=\"https://cleverdevil.io/tag/indieweb\" class=\"p-category\">#indieweb</a> <a href=\"https://cleverdevil.io/tag/microformats2\" class=\"p-category\">#microformats2</a>"
    },
    "author": {
        "type": "card",
        "name": "Jonathan LaCour",
        "url": "https://cleverdevil.io/profile/cleverdevil",
        "photo": "https://cleverdevil.io/file/fdbc7696a5f73864ea11a828c861e138/thumb.jpg"
    },
    "_id": "120213",
    "_source": "71",
    "_is_read": true
}

Kartik Prabhu kartikprabhu.com/about#me

{
    "type": "entry",
    "published": "2018-03-10T00:29:37-0500",
    "url": "https://kartikprabhu.com/notes/re-snarfed-like-mf2py-backcompat",
    "category": [
        "indieweb",
        "microformats"
    ],
    "in-reply-to": [
        "https://snarfed.org/2018-03-09_backcompat-mf2py-parallel-transport"
    ],
    "content": {
        "text": "The irony of this \u201clike post\u201d is that under the new backcompat rules (according to spec) the u-like-of is ignored under a hentry! see: http://microformats.org/wiki/microformats2-parsing#note_backward_compatibility_details\n\nSo it shows up as a mention to my post! :P",
        "html": "The irony of this \u201clike post\u201d is that under the new backcompat rules (according to spec) the u-like-of is ignored under a hentry! see: <a href=\"http://microformats.org/wiki/microformats2-parsing#note_backward_compatibility_details\">http://microformats.org/wiki/microformats2-parsing#note_backward_compatibility_details</a>\n\nSo it shows up as a mention to my post! :P"
    },
    "author": {
        "type": "card",
        "name": "Kartik Prabhu",
        "url": "https://kartikprabhu.com/about#me",
        "photo": "https://kartikprabhu.com/static/images/avatar.jpg"
    },
    "_id": "120003",
    "_source": "204",
    "_is_read": true
}

Kartik Prabhu kartikprabhu.com/about#me

{
    "type": "entry",
    "published": "2018-03-09T18:19:57-0500",
    "url": "https://kartikprabhu.com/notes/backcompat-mf2py",
    "category": [
        "python",
        "microformats",
        "indieweb"
    ],
    "syndication": [
        "https://twitter.com/kartik_prabhu/status/972251357443952640"
    ],
    "content": {
        "text": "Took a solid 10 hours but better backcompat parsing rules in mf2py now https://github.com/kartikprabhu/mf2py",
        "html": "Took a solid 10 hours but better backcompat parsing rules in mf2py now <a href=\"https://github.com/kartikprabhu/mf2py\">https://github.com/kartikprabhu/mf2py</a>"
    },
    "author": {
        "type": "card",
        "name": "Kartik Prabhu",
        "url": "https://kartikprabhu.com/about#me",
        "photo": "https://kartikprabhu.com/static/images/avatar.jpg"
    },
    "_id": "119741",
    "_source": "204",
    "_is_read": true
}

Chris Aldrich stream.boffosocko.com/profile/chrisaldrich

{
    "type": "entry",
    "published": "2018-03-09T21:29:02+0000",
    "url": "http://stream.boffosocko.com/2018/%E3%81%8A%E3%81%AF%E3%82%88%E3%81%86%E3%81%94%E3%81%96%E3%81%84%E3%81%BE%E3%81%99-welcome-to-the-indieweb-im-sure-many-can-help",
    "in-reply-to": [
        "https://www.prjorgensen.com/2018/03/08/949"
    ],
    "content": {
        "text": "\u304a\u306f\u3088\u3046\u3054\u3056\u3044\u307e\u3059. Welcome to the IndieWeb! I'm sure many can help you out with some additional detail about what you're experiencing. Try catching us live in the chat at: https://indieweb.org/discuss",
        "html": "\u304a\u306f\u3088\u3046\u3054\u3056\u3044\u307e\u3059. Welcome to the IndieWeb! I'm sure many can help you out with some additional detail about what you're experiencing. Try catching us live in the chat at: <a href=\"https://indieweb.org/discuss\">https://indieweb.org/discuss</a>"
    },
    "author": {
        "type": "card",
        "name": "Chris Aldrich",
        "url": "http://stream.boffosocko.com/profile/chrisaldrich",
        "photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
    },
    "_id": "119726",
    "_source": "192",
    "_is_read": true
}

Kevin Marks known.kevinmarks.com/profile/kevinmarks

{
    "type": "entry",
    "published": "2018-03-09T17:14:33+0000",
    "url": "http://known.kevinmarks.com/2018/the-contract-between-a-web-browser-and",
    "category": [
        "indieweb"
    ],
    "syndication": [
        "https://twitter.com/kevinmarks/status/972158712918958080"
    ],
    "content": {
        "text": "\u201cthe contract between a web browser and a web server, outlining how HTML would work. These standards didn\u2019t define just software, but also culture; this was the raw material of human interaction.\u201d - @ftrain https://www.bloomberg.com/news/features/2018-03-09/bitcoin-is-ridiculous-blockchain-is-dangerous-pau... #indieweb",
        "html": "\u201cthe contract between a web browser and a web server, outlining how HTML would work. These standards didn\u2019t define just software, but also culture; this was the raw material of human interaction.\u201d - @ftrain <a href=\"https://www.bloomberg.com/news/features/2018-03-09/bitcoin-is-ridiculous-blockchain-is-dangerous-paul-ford\">https://www.bloomberg.com/news/features/2018-03-09/bitcoin-is-ridiculous-blockchain-is-dangerous-pau...</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": "http://known.kevinmarks.com/file/9255656669173b7867ab839ee6556f9e"
    },
    "_id": "118469",
    "_source": "205",
    "_is_read": true
}

Aaron Parecki aaronparecki.com

{
    "type": "entry",
    "published": "2018-03-08T14:54:52-0800",
    "url": "https://aaronparecki.com/2018/03/08/13/monocle-account-switcher",
    "category": [
        "microsub",
        "monocle",
        "aperture",
        "p3k"
    ],
    "photo": [
        "https://aperture-media.p3k.io/aaronparecki.com/68dff476f923513b48e73de1a20b89a2a0239b768528124fc6af200f6ed17a85.png"
    ],
    "content": {
        "text": "Monocle just got real fancy. I can now set a default account for each channel from which responses should be sent. (Stored in my Microsub server, not in Monocle, so it can work across clients). Monocle recognizes when alternate accounts are available and provides an account switcher UI in the footer. Any \"like/repost/reply\" actions are then sent via that account instead of to my main site!"
    },
    "author": {
        "type": "card",
        "name": "Aaron Parecki",
        "url": "https://aaronparecki.com/",
        "photo": "https://aperture-media.p3k.io/aaronparecki.com/2b8e1668dcd9cfa6a170b3724df740695f73a15c2a825962fd0a0967ec11ecdc.jpg"
    },
    "_id": "115873",
    "_source": "16",
    "_is_read": true
}

Kevin Marks known.kevinmarks.com/profile/kevinmarks

{
    "type": "entry",
    "published": "2018-03-08T10:29:18+0000",
    "url": "http://known.kevinmarks.com/2018/for-both-youtube-and-facebook-solving-this",
    "category": [
        "indieweb"
    ],
    "syndication": [
        "https://twitter.com/kevinmarks/status/971694343252684800"
    ],
    "content": {
        "text": "\u201cFor both YouTube and Facebook, solving this problem would actually be easy: kill Trending Topics, which has a terrible track record. But neither tech giant will do that, because that\u2019s where the advertising money is.\u201d https://mondaynote.com/there-is-no-easy-fix-for-facebooks-reliability-problem-eb7dd45fd360 #indieweb",
        "html": "\u201cFor both YouTube and Facebook, solving this problem would actually be easy: kill Trending Topics, which has a terrible track record. But neither tech giant will do that, because that\u2019s where the advertising money is.\u201d <a href=\"https://mondaynote.com/there-is-no-easy-fix-for-facebooks-reliability-problem-eb7dd45fd360\">https://mondaynote.com/there-is-no-easy-fix-for-facebooks-reliability-problem-eb7dd45fd360</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": "http://known.kevinmarks.com/file/9255656669173b7867ab839ee6556f9e"
    },
    "_id": "113363",
    "_source": "205",
    "_is_read": true
}

{
    "type": "entry",
    "url": "https://realize.be/notes/1227",
    "content": {
        "text": "Posting a note using Indigenous to my site, this is awesome! Guess I have to start on an Android version now .. #drupal #indieweb // cc @Dries @EddieHinkle",
        "html": "<p>Posting a note using Indigenous to my site, this is awesome! Guess I have to start on an Android version now .. #drupal #indieweb // cc @Dries @EddieHinkle</p>"
    },
    "_id": "111963",
    "_source": "213",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2018-03-07T19:34:48Z",
    "url": "https://adactio.com/notes/13550",
    "photo": [
        "https://adactio.com/images/uploaded/13550/small.jpg"
    ],
    "syndication": [
        "https://twitter.com/adactio/status/971469342926876673",
        "https://flickr.com/photos/adactio/26806178428"
    ],
    "content": {
        "text": "Had some great discussions with @qubyte at Homebrew Website Club Brighton\u2014webmentions, service workers, static sites \u2026lots of food for thought.",
        "html": "<a href=\"https://adactio.com/notes/13550\">\n</a>\n<p>Had some great discussions with <a href=\"https://twitter.com/qubyte\">@qubyte</a> at Homebrew Website Club Brighton\u2014webmentions, service workers, static sites \u2026lots of food for thought.</p>"
    },
    "_id": "111749",
    "_source": "2",
    "_is_read": true
}

Aaron Parecki aaronparecki.com

{
    "type": "entry",
    "published": "2018-03-07T10:42:02-0800",
    "url": "https://aaronparecki.com/2018/03/07/16/",
    "category": [
        "aperture",
        "indieweb"
    ],
    "photo": [
        "https://aperture-media.p3k.io/aaronparecki.com/3332aebc1dd41d45d68c64976db72e2ab2f2ce1b7489ec3fa14da87202e17515.jpg"
    ],
    "content": {
        "text": "I think my favorite new weird feature of Aperture is the ability to switch it into \"Demo Mode\" which will hide certain channels from view and from Microsub clients. This comes in handy when taking screenshots and doing presentations where I don't want to reveal some of my private channels I have!"
    },
    "author": {
        "type": "card",
        "name": "Aaron Parecki",
        "url": "https://aaronparecki.com/",
        "photo": "https://aperture-media.p3k.io/aaronparecki.com/2b8e1668dcd9cfa6a170b3724df740695f73a15c2a825962fd0a0967ec11ecdc.jpg"
    },
    "_id": "111443",
    "_source": "16",
    "_is_read": true
}

Chris Aldrich stream.boffosocko.com/profile/chrisaldrich

{
    "type": "entry",
    "published": "2018-03-06T19:24:56+0000",
    "url": "http://stream.boffosocko.com/2018/part-of-the-point-and-beauty-of-the-indieweb-movement",
    "in-reply-to": [
        "https://lo.hn/2018/hello-why-should-we-use-known-instead-of-wordpress-for",
        "http://boffosocko.com/about/ama/"
    ],
    "content": {
        "text": "Part of the point and beauty of the IndieWeb movement is that you can choose any platform or set up you choose! There are far more options than just Known and WordPress. The harder problem is is to figure out what it is you want to do online. Then you can find, build, or find and build a tool that best suits those needs. If you need help, feel free to try the chat rooms at https://indieweb.org/discuss.",
        "html": "Part of the point and beauty of the IndieWeb movement is that you can choose any platform or set up you choose! There are far more options than just Known and WordPress. The harder problem is is to figure out what it is you want to do online. Then you can find, build, or find and build a tool that best suits those needs. If you need help, feel free to try the chat rooms at <a href=\"https://indieweb.org/discuss\">https://indieweb.org/discuss</a>."
    },
    "author": {
        "type": "card",
        "name": "Chris Aldrich",
        "url": "http://stream.boffosocko.com/profile/chrisaldrich",
        "photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
    },
    "_id": "109383",
    "_source": "192",
    "_is_read": true
}

{
    "type": "entry",
    "url": "https://realize.be/notes/1225",
    "content": {
        "text": "So if you now reply on Twitter, it will create a comment on that node on my site (moderated though, I know you all like spamming!) #indieweb #drupal"
    },
    "_id": "107848",
    "_source": "213",
    "_is_read": true
}