{
    "type": "entry",
    "published": "2020-06-30T21:50:36+10:00",
    "url": "https://mblaney.xyz/2020-06-30-sad_that_IndieWeb_summit_isnt_happening_this_",
    "syndication": [
        "https://twitter.com/malcolmblaney/status/1277932564683112448"
    ],
    "content": {
        "text": "sad that IndieWeb summit isn't happening this year, but enjoying catching up on all the recordings from the online event over the weekend! Thanks to everyone for the great discussions and the organisers for making the content available.",
        "html": "sad that IndieWeb summit isn't happening this year, but enjoying catching up on all the recordings from the online event over the weekend! Thanks to everyone for the great discussions and the organisers for making the content available.<a href=\"https://brid.gy/publish/twitter?bridgy_omit_link=true\"></a><a href=\"https://twitter.com/malcolmblaney/status/1277932564683112448\" class=\"u-syndication\"></a>"
    },
    "author": {
        "type": "card",
        "name": "Malcolm Blaney",
        "url": "https://mblaney.xyz",
        "photo": "https://mblaney.xyz/public/profile_thumb.png"
    },
    "post-type": "note",
    "_id": "12839709",
    "_source": "3708",
    "_is_read": true
}

Aether: A Personal Board For Inspiration

{
    "type": "entry",
    "published": "2020-06-29 23:40:28.756219",
    "summary": "I recently had a chat with a couple of friends about style; it inspired me to take a project off the back-burner and turn it into code.",
    "url": "https://kongaloosh.com/e/2020/6/29/aether-a-p",
    "syndication": [
        "https://twitter.com/kongaloosh/status/1277813401025118208"
    ],
    "name": "Aether: A Personal Board For Inspiration",
    "content": {
        "text": "I recently had a chat with a couple of friends about style; it inspired me to take a project off the back-burner and turn it into code.\n                        \n                    \n                \n                \n\n                \n\n\n                \n                \n                A couple of friends posed a question: is artistic style something that is innate, or cultivated? We spent a few hours digging into art we had created throughout adolescence and into adulthood, picking apart what remained consistent throughout. We sifted through sketchbooks thinking about what may have influenced changes. \nTo some degree, each of us kept track of inspiration. Katryna went as far as to keep collages and document each of them. I've always admired collages: there's something about collecting, organising, and drawing inspiration from unexpected places.\nWhen I travel,  I often take pictures of scenes I find interesting: details that catch my eye. A memorable example: to shelter from the rain in Vienna, I ducked into a chapel. The dreary light diffused through the windows to create a high-contrast baroque scene. Typically overwhelming colours and ornamentation became subdued. I collected the moment for later.\n\nIt's not just scenes that I collect. Occasionally I'll find a striking design element or detail and save it for later. A bar I was dining at during a layover in the Houston airport was tiled with mahjong pieces.\n\nIn spite of my aesthetic hoarding, I don't really have a method for collecting these images in a sensible way. They sit on my phone, my computer, and my desktop: apocalyptically poor organisation. I'm always on the hunt for inspiration, but don't have a place to enjoy the fruits of this collecting. \nSo I made an indie-pinboard.\naether is a small flask-app with hints of javascript that take a folder on your server and transform it into an infinite scroll of images that are slowly loaded as you cruise by. In my head, these scenes and images were being collected to make some wild reference art-book collage. By making a tiled album, I'm conveying the sense of purpose that I originally intended.\n\nYou can find the code in a repo here.\nThese images are displayed in a haphazard way: the only unifying trait is that each represents something that I liked. In the future I hope to add a more contentful display. I'm thinking that by employing some simple computer vision, I can partition the images by theme and sort them by feel.\n            \n\n        \n        \n            \n            \n        \n        \n\n\n        \n\n\n                                 \n                                            \n                \n                \n                \n                tech\n                \n                article\n                \n                dev\n                \n                indie\n                \n                indieweb\n                \n                art\n                \n                inspiration\n                \n                hack",
        "html": "<p>\n                        <i>\n                            I recently had a chat with a couple of friends about style; it inspired me to take a project off the back-burner and turn it into code.\n                        </i>\n                    </p>\n                \n                \n\n                \n\n\n                \n                \n                <p>A couple of friends posed a question: is artistic style something that is innate, or cultivated? We spent a few hours digging into art we had created throughout adolescence and into adulthood, picking apart what remained consistent throughout. We sifted through sketchbooks thinking about what may have influenced changes. </p>\n<p>To some degree, each of us kept track of inspiration. Katryna went as far as to keep collages and document each of them. I've always admired collages: there's something about collecting, organising, and drawing inspiration from unexpected places.</p>\n<p>When I travel,  I often take pictures of scenes I find interesting: details that catch my eye. A memorable example: to shelter from the rain in Vienna, I ducked into a chapel. The dreary light diffused through the windows to create a high-contrast baroque scene. Typically overwhelming colours and ornamentation became subdued. I collected the moment for later.</p>\n<p><img alt=\"\" src=\"http://aether.kongaloosh.com/images/IMG_2734.JPG\" /></p>\n<p>It's not just scenes that I collect. Occasionally I'll find a striking design element or detail and save it for later. A bar I was dining at during a layover in the Houston airport was tiled with <em>mahjong pieces</em>.</p>\n<p><img alt=\"\" src=\"http://aether.kongaloosh.com/images/IMG_5044.jpeg\" /></p>\n<p>In spite of my aesthetic hoarding, I don't really have a method for collecting these images in a sensible way. They sit on my phone, my computer, and my desktop: apocalyptically poor organisation. I'm always on the hunt for inspiration, but don't have a place to enjoy the fruits of this collecting. </p>\n<p><a href=\"http://aether.kongaloosh.com\">So I made an indie-pinboard.</a></p>\n<p><em>aether</em> is a small flask-app with hints of javascript that take a folder on your server and transform it into an infinite scroll of images that are slowly loaded as you cruise by. In my head, these scenes and images were being collected to make some wild reference art-book collage. By making a tiled album, I'm conveying the sense of purpose that I originally intended.</p>\n<p><img alt=\"\" src=\"https://github.com/Kongaloosh/aether/raw/master/demo.gif?raw=true\" /></p>\n<p>You can find the code in a repo <a href=\"https://github.com/Kongaloosh/aether\">here</a>.</p>\n<p>These images are displayed in a haphazard way: the only unifying trait is that each represents <em>something</em> that I liked. In the future I hope to add a more contentful display. I'm thinking that by employing some simple computer vision, I can partition the images by theme and sort them by feel.</p>\n            \n\n        \n        \n            <p></p>\n            \n        \n        \n\n\n        \n\n\n                                 \n                                            \n                \n                <i></i>\n                \n                <a href=\"https://kongaloosh.com/t/tech\">tech</a>\n                \n                <a href=\"https://kongaloosh.com/t/article\">article</a>\n                \n                <a href=\"https://kongaloosh.com/t/dev\">dev</a>\n                \n                <a href=\"https://kongaloosh.com/t/indie\">indie</a>\n                \n                <a href=\"https://kongaloosh.com/t/indieweb\">indieweb</a>\n                \n                <a href=\"https://kongaloosh.com/t/art\">art</a>\n                \n                <a href=\"https://kongaloosh.com/t/inspiration\">inspiration</a>\n                \n                <a href=\"https://kongaloosh.com/t/hack\">hack</a>"
    },
    "author": {
        "type": "card",
        "name": "Alex Kearney",
        "url": "http://kongaloosh.com",
        "photo": null
    },
    "post-type": "article",
    "_id": "12835411",
    "_source": "228",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-06-29T17:40:44.98974-07:00",
    "url": "https://v2.jacky.wtf/post/55426f1d-b4d8-457e-a418-8dba46902641",
    "category": [
        "indieweb",
        "thoughts",
        "social web"
    ],
    "content": {
        "text": "The more time I read and check things, the more I realize that protocols are only half of the problem. Heh, we need people working on really solid content creation tools that can match or rival what we see out there. It\u2019s easy to publish text or an image. Video gets a bit tricky and even more dynamic content like polling, RSVPs or protected content gets more difficult.But those are just touching the surface. I\u2019m starting to see why the idea of being able to push a \u201ccomponent\u201d of information is very attractive - by design, it can provide the necessary means for rendering things if it\u2019s not yet supported and perhaps give users a chance to choose if they\u2019d want to see it anyway. This is part of my hope as I begin toying with the mobile client I have in mind to be a companion to Lwa. By default, none of the post types outside of a note would be supported. It\u2019d have to ask a Microsub server for information / tools / data on how to render it. This adds complexity to the server but it makes clients very thin.",
        "html": "<p>The more time I read and check things, the more I realize that protocols are only <em>half</em> of the problem. Heh, we need people working on really solid content creation tools that can match or rival what we see out there. It\u2019s easy to publish text or an image. Video gets a bit tricky and even more dynamic content like polling, RSVPs or protected content gets more difficult.</p><p>But those are just touching the surface. I\u2019m starting to see why the idea of being able to push a \u201ccomponent\u201d of information is very attractive - by design, it can provide the necessary means for rendering things if it\u2019s not yet supported and perhaps give users a chance to choose <em>if</em> they\u2019d want to see it anyway. This is part of my hope as I begin toying with the mobile client I have in mind to be a companion to Lwa. By default, none of the post types outside of a note would be supported. It\u2019d have to ask a Microsub server for information / tools / data on how to render it. This adds complexity to the server but it makes clients very thin.</p>"
    },
    "author": {
        "type": "card",
        "name": "",
        "url": "https://v2.jacky.wtf",
        "photo": null
    },
    "post-type": "note",
    "_id": "12829494",
    "_source": "1886",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-06-29T14:23:08.42587-07:00",
    "url": "https://v2.jacky.wtf/post/6b95afe0-c350-4a39-8169-ecf0590d1275",
    "category": [
        "lighthouse"
    ],
    "content": {
        "text": "So it\u2019s both Lighthouse not sending the callback when it\u2019s successful and Koype not waiting until the Webmention callback is called to then update the syndication result. Both are fine and easy to fix.",
        "html": "<p>So it\u2019s both Lighthouse not sending the callback when it\u2019s successful and Koype not waiting until the Webmention callback is called to then update the syndication result. Both are fine and easy to fix.</p>"
    },
    "author": {
        "type": "card",
        "name": "",
        "url": "https://v2.jacky.wtf",
        "photo": null
    },
    "post-type": "note",
    "_id": "12825579",
    "_source": "1886",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-06-29T14:00:00.00000-07:00",
    "url": "https://v2.jacky.wtf/post/7588b56f-b16b-4bbc-95e4-0909b3ad60cd",
    "content": {
        "text": "Interesting. It doesn\u2019t look like Lighthouse is actually sending out Webmentions. Ugh.",
        "html": "<p>Interesting. It doesn\u2019t look like Lighthouse is actually sending out Webmentions. Ugh.</p>"
    },
    "author": {
        "type": "card",
        "name": "",
        "url": "https://v2.jacky.wtf",
        "photo": null
    },
    "post-type": "note",
    "_id": "12825308",
    "_source": "1886",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-06-29T06:21:00.00000-07:00",
    "url": "https://v2.jacky.wtf/post/9920e3ce-b6c5-4fc1-a7df-8c53cd00a321",
    "category": [
        "itches",
        "side projects",
        "lighthouse"
    ],
    "content": {
        "text": "I think I\u2019ve successfully introduced the concept of asynchronous Webmentions to my site and Lighthouse. It does look like that\u2019s the only kind Lighthouse might be able to accept. It relies on the sender providing a callback URL that\u2019s sent a post of the same target and source whenever it notices a change. Usually, this shouldn\u2019t be often but I do it to allow for slower services or passive retries.That said, Lighthouse is successfully handling this and I think I\u2019ll begin working on the extraction of a feed to place into a reader soon. That and having a facility to render Webmentions on one\u2019s site will be key! Lighthouse does have a hard requirement that people leverage IndieAuth and that\u2019s largely to reduce the number of domains / sites that one can have monitored. But I\u2019ll have to eventually refactor that because I do want to have a per-site experience for myself (giving each of my projects their own site will be better for me to separate into my reader).",
        "html": "<p>I think I\u2019ve successfully introduced the concept of asynchronous Webmentions to my site and Lighthouse. It does look like that\u2019s the only kind Lighthouse might be able to accept. It relies on the sender providing a callback URL that\u2019s sent a post of the same target and source whenever it notices a change. Usually, this shouldn\u2019t be often but I do it to allow for slower services or passive retries.</p><p>That said, Lighthouse is successfully handling this and I think I\u2019ll begin working on the extraction of a feed to place into a reader soon. That and having a facility to render Webmentions on one\u2019s site will be key! Lighthouse does have a hard requirement that people leverage IndieAuth and that\u2019s largely to reduce the number of domains / sites that one can have monitored. But I\u2019ll have to eventually refactor that because I do want to have a per-site experience for myself (giving each of my projects their own site will be better for me to separate into my reader).</p>"
    },
    "author": {
        "type": "card",
        "name": "",
        "url": "https://v2.jacky.wtf",
        "photo": null
    },
    "post-type": "note",
    "_id": "12814161",
    "_source": "1886",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-06-29T03:15:37.55497-07:00",
    "url": "https://v2.jacky.wtf/post/514ec949-2316-4e98-8060-746783d5b9a8",
    "content": {
        "text": "This is me testing if Webmention-based syndication works for my site. This relies on using the code in https://git.jacky.wtf/indieweb/koype/issues/202 to get that working.",
        "html": "<p>This is me testing if Webmention-based syndication works for my site. This relies on using the code in <a href=\"https://git.jacky.wtf/indieweb/koype/issues/202\">https://git.jacky.wtf/indieweb/koype/issues/202</a> to get that working.</p>"
    },
    "author": {
        "type": "card",
        "name": "",
        "url": "https://v2.jacky.wtf",
        "photo": null
    },
    "post-type": "note",
    "_id": "12811176",
    "_source": "1886",
    "_is_read": true
}

Plaidophile: Access token grants for feed readers

{
    "type": "entry",
    "author": {
        "name": "fluffy",
        "url": "http://beesbuzz.biz/",
        "photo": null
    },
    "url": "http://beesbuzz.biz/blog/5711-Access-token-grants-for-feed-readers",
    "published": "2020-06-28T17:02:36-07:00",
    "content": {
        "html": "<p>This year <a href=\"https://2020.indieweb.org/summit\">IndieWeb Summit</a> was canceled<a href=\"http://beesbuzz.biz/blog/5711-Access-token-grants-for-feed-readers#d_e5711_fn1\">1</a>, and some pretty good conversations took place. As usual my biggest interest was in doing authenticated, secure sharing of private posts, which has been a huge focus in how I\u2019ve been building Publ.</p><p>I wasn\u2019t really able to participate in any of the development stuff (as I\u2019m still in quite a lot of pain due to whatever the hell is going on with my chronic pain stuff interacting with whatever the hell has been going on with my shoulder for the past <em>month</em>), but I did join in on the ending of a discussion/dev session about <a href=\"https://indieweb.org/AutoAuth\">AutoAuth</a>.</p>\n\n\n<p>My understanding about what happened before I joined in is that a few folks did end up implementing an end-to-end version of AutoAuth flow, but they decided that there were still too many parts to deal with for the entire implementation and wanted to separate out parts of the protocol to capture what we actually want out of this mechanism, which is absolutely fair.</p><p>What I liked about the idea of AutoAuth was that people could subscribe to any arbitrary feed in their social reader and opt into (securely) sharing their identity with the publisher, and then the publisher could opt into (securely) adding their private posts into the feed. But the protocol behind that is rather complex and not necessarily what\u2019s needed for the flow, and we eventually reached a consensus that the subscription part could be designed and implemented separately from the access grant.</p><p><a href=\"https://aaronpk.com/\">Aaron</a> had a sketch of a protocol up on his screen, but I didn\u2019t quite understand the flow based on the text notes and his verbal explanation, and I\u2019m hoping that he\u2019ll be able to document it on <a href=\"https://indieweb.org/\">the wiki</a> at some point, but in the meantime, my takeaway of how things could possibly work:</p>\n<ol><li>A feed with a privacy upgrade available can respond with a <code>WWW-Authenticate:</code> header (per AutoAuth)</li>\n<li>The reader UX indicates that authentication might be an option</li>\n<li>Somehow the following relationship is established between the reader and the publisher, and the publisher provides a bearer token to the reader</li>\n<li>The reader makes future requests with the appropriate <code>Authorization: Bearer xxxxx</code> header</li>\n</ol><p>For what it\u2019s worth, Publ already supports steps 1 and 4, and so I want to propose a mechanism for step 3 (which would be fairly easy for me to implement into Publ and possibly into <a href=\"https://github.com/fluffy-critter/Feed-on-Feeds\">Feed On Feeds</a>): If a user is logged in to a site, the site will provide the bearer token. Specifically, it would do so in one or more of the following ways:</p>\n<ul><li>A response header, e.g. <code>Access-Token: Bearer xxxxx</code></li>\n<li>An HTML header, e.g. <code>&lt;meta http-equiv=\"Access-Token\" content=\"Bearer xxxxx\"&gt;</code></li>\n<li>Displayed UX, such as a display to the end user with reasonable messaging regarding the value of the <code>Authorization: Bearer xxxxx</code> header to add to their reader manually</li>\n</ul><p>The first two could work alongside a future AutoAuth-type flow in the reader, or a user extension for the browser to show some flow for adding the access token to their compatible reader or whatever. The third one would cover a manual flow.</p><p>This does lead to some questions, like how do we handle things like token expiration (both from timeouts and from revocation). I think that this can still be covered by a simple flow; first, we\u2019d suggest that any token expiration be fairly long-lived (like, on the order of months, if not permanent). Next, if a token has expired, then the retrieval of the resource should raise a <code>401 Unauthorized</code> header, which would indicate to the reader that the token needs to be updated.<a href=\"http://beesbuzz.biz/blog/5711-Access-token-grants-for-feed-readers#d_e5711_fn2\">2</a></p><p>I\u2019m tempted to try hacking this into Feed On Feeds, but I think what I really want to do going forward is to use this as an excuse to finally start writing <a href=\"http://beesbuzz.biz/blog/8118-So-what-is-Subl-anyway\">Subl</a>, as just a very basic social reader that provides subscription and manual-flow authentication UX. Automation-flow can come later.</p><p>Anyway, I\u2019m hoping that the following folks will have feedback on this proposal: <a href=\"https://aaronpk.com/\">Aaron</a>, <a href=\"https://tantek.com/\">Tantek</a>, <a href=\"https://www.svenknebel.de/posts/\">Sven</a>, and <a href=\"https://www.jacky.wtf/\">Jackie</a>.</p>\n\n<ol><li><p>In the \u201cwe had a pandemic and had to call it off\u201d sense and not in the \u201cwe have too many cishet white guys\u201d sense. <a href=\"http://beesbuzz.biz/blog/5711-Access-token-grants-for-feed-readers#r_e5711_fn1\">\u21a9</a></p></li><li><p>Incidentally, this is also how Publ already implements it, so of course I\u2019m biased towards it. :) <a href=\"http://beesbuzz.biz/blog/5711-Access-token-grants-for-feed-readers#r_e5711_fn2\">\u21a9</a></p></li></ol><p><a href=\"http://beesbuzz.biz/blog/5711-Access-token-grants-for-feed-readers#comments\">comments</a></p>",
        "text": "This year IndieWeb Summit was canceled1, and some pretty good conversations took place. As usual my biggest interest was in doing authenticated, secure sharing of private posts, which has been a huge focus in how I\u2019ve been building Publ.I wasn\u2019t really able to participate in any of the development stuff (as I\u2019m still in quite a lot of pain due to whatever the hell is going on with my chronic pain stuff interacting with whatever the hell has been going on with my shoulder for the past month), but I did join in on the ending of a discussion/dev session about AutoAuth.\n\n\nMy understanding about what happened before I joined in is that a few folks did end up implementing an end-to-end version of AutoAuth flow, but they decided that there were still too many parts to deal with for the entire implementation and wanted to separate out parts of the protocol to capture what we actually want out of this mechanism, which is absolutely fair.What I liked about the idea of AutoAuth was that people could subscribe to any arbitrary feed in their social reader and opt into (securely) sharing their identity with the publisher, and then the publisher could opt into (securely) adding their private posts into the feed. But the protocol behind that is rather complex and not necessarily what\u2019s needed for the flow, and we eventually reached a consensus that the subscription part could be designed and implemented separately from the access grant.Aaron had a sketch of a protocol up on his screen, but I didn\u2019t quite understand the flow based on the text notes and his verbal explanation, and I\u2019m hoping that he\u2019ll be able to document it on the wiki at some point, but in the meantime, my takeaway of how things could possibly work:\nA feed with a privacy upgrade available can respond with a WWW-Authenticate: header (per AutoAuth)\nThe reader UX indicates that authentication might be an option\nSomehow the following relationship is established between the reader and the publisher, and the publisher provides a bearer token to the reader\nThe reader makes future requests with the appropriate Authorization: Bearer xxxxx header\nFor what it\u2019s worth, Publ already supports steps 1 and 4, and so I want to propose a mechanism for step 3 (which would be fairly easy for me to implement into Publ and possibly into Feed On Feeds): If a user is logged in to a site, the site will provide the bearer token. Specifically, it would do so in one or more of the following ways:\nA response header, e.g. Access-Token: Bearer xxxxx\nAn HTML header, e.g. <meta http-equiv=\"Access-Token\" content=\"Bearer xxxxx\">\nDisplayed UX, such as a display to the end user with reasonable messaging regarding the value of the Authorization: Bearer xxxxx header to add to their reader manually\nThe first two could work alongside a future AutoAuth-type flow in the reader, or a user extension for the browser to show some flow for adding the access token to their compatible reader or whatever. The third one would cover a manual flow.This does lead to some questions, like how do we handle things like token expiration (both from timeouts and from revocation). I think that this can still be covered by a simple flow; first, we\u2019d suggest that any token expiration be fairly long-lived (like, on the order of months, if not permanent). Next, if a token has expired, then the retrieval of the resource should raise a 401 Unauthorized header, which would indicate to the reader that the token needs to be updated.2I\u2019m tempted to try hacking this into Feed On Feeds, but I think what I really want to do going forward is to use this as an excuse to finally start writing Subl, as just a very basic social reader that provides subscription and manual-flow authentication UX. Automation-flow can come later.Anyway, I\u2019m hoping that the following folks will have feedback on this proposal: Aaron, Tantek, Sven, and Jackie.\n\nIn the \u201cwe had a pandemic and had to call it off\u201d sense and not in the \u201cwe have too many cishet white guys\u201d sense. \u21a9Incidentally, this is also how Publ already implements it, so of course I\u2019m biased towards it. :) \u21a9comments"
    },
    "name": "Plaidophile: Access token grants for feed readers",
    "post-type": "article",
    "_id": "12803371",
    "_source": "3782",
    "_is_read": true
}

Creating My Own Personal Micropub Client

{
    "type": "entry",
    "published": "2020-06-28 21:08:04 +0100 +0100",
    "summary": "Announcing my own personal Micropub client to publish content that is very specific to my workflows.",
    "url": "https://www.jvt.me/posts/2020/06/28/personal-micropub-client/",
    "category": [
        "www.jvt.me",
        "micropub"
    ],
    "name": "Creating My Own Personal Micropub Client",
    "author": {
        "type": "card",
        "name": "Jamie Tanna",
        "url": "https://www.jvt.me",
        "photo": "https://www.jvt.me/img/profile.png"
    },
    "post-type": "article",
    "_id": "12801271",
    "_source": "2169",
    "_is_read": true
}

Read: Shackles of Digital Freedom

{
    "type": "entry",
    "author": {
        "name": "Neil Mather",
        "url": "https://doubleloop.net/",
        "photo": null
    },
    "url": "https://doubleloop.net/2020/06/28/read-shackles-of-digital-freedom/",
    "published": "2020-06-28T19:33:04+00:00",
    "content": {
        "html": "Read <a href=\"http://www.boundary2.org/2018/03/zachary-loeb-shackles-of-digital-freedom-review-of-qiu-goodbye-islave/\">Shackles of Digital Freedom (Review of Qiu, Goodbye iSlave)</a> by Zachary Loeb <em>(boundary 2)</em>\n<blockquote>a review of Jack Linchuan Qiu, Goodbye iSlave: a Manifesto for Digital Abolition.</blockquote>\n\nReally good review of <a href=\"https://commonplace.doubleloop.net/20200628115050-goodbye_islave.html\">Goodbye iSlave.</a> <a href=\"https://commonplace.doubleloop.net/20200627221332-islavery.html\">iSlavery</a> is Jack Qiu\u2019s framing of the manufacture and demand for modern devices as akin to a modern international slave trade. With exploitation in the material manufacture of these devices, as well as exploitation in the deliberate addiction of people to these devices to drive their sales. With parallels between the pushing of sugar and other commodities to drive their production, all done through the exploitation in the slave trade.\n<p>That parallel linkage of these two parts of the system is really interesting to me, interested as I am in both the <a href=\"https://commonplace.doubleloop.net/20200308230733-right_to_repair.html\">right to repair</a> and the <a href=\"https://commonplace.doubleloop.net/indieweb.html\">IndieWeb</a>. In right to repair we try to counter the rampant consumption of devices, and in the IndieWeb we try to counter the pushers of these technologies.</p>\n<p>The review highly rates the book for giving an unflinching look at the exploitation rife in the manufacture of modern devices. Not without caveats though \u2013 particular the problems of framing these modern practices as slavery in comparison to historic slavery. And also some of the modes of resistance suggested to iSlavery falling under the brackets of simply ethical consumerism, and also perhaps an uncritical assumption that all technology can be liberatory if harnessed right.</p>\n<p><a href=\"http://www.boundary2.org/2018/03/zachary-loeb-shackles-of-digital-freedom-review-of-qiu-goodbye-islave/\">www.boundary2.org/2018/03/zachary-loeb-shackles-of-digital-freedom-review-of-qiu-goodbye-islave/</a></p>",
        "text": "Read Shackles of Digital Freedom (Review of Qiu, Goodbye iSlave) by Zachary Loeb (boundary 2)\na review of Jack Linchuan Qiu, Goodbye iSlave: a Manifesto for Digital Abolition.\n\nReally good review of Goodbye iSlave. iSlavery is Jack Qiu\u2019s framing of the manufacture and demand for modern devices as akin to a modern international slave trade. With exploitation in the material manufacture of these devices, as well as exploitation in the deliberate addiction of people to these devices to drive their sales. With parallels between the pushing of sugar and other commodities to drive their production, all done through the exploitation in the slave trade.\nThat parallel linkage of these two parts of the system is really interesting to me, interested as I am in both the right to repair and the IndieWeb. In right to repair we try to counter the rampant consumption of devices, and in the IndieWeb we try to counter the pushers of these technologies.\nThe review highly rates the book for giving an unflinching look at the exploitation rife in the manufacture of modern devices. Not without caveats though \u2013 particular the problems of framing these modern practices as slavery in comparison to historic slavery. And also some of the modes of resistance suggested to iSlavery falling under the brackets of simply ethical consumerism, and also perhaps an uncritical assumption that all technology can be liberatory if harnessed right.\nwww.boundary2.org/2018/03/zachary-loeb-shackles-of-digital-freedom-review-of-qiu-goodbye-islave/"
    },
    "name": "Read: Shackles of Digital Freedom",
    "post-type": "article",
    "_id": "12800708",
    "_source": "1895",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-06-28T21:30:54.288Z",
    "url": "https://grant.codes/2020/06/28/09-30-54",
    "category": [
        "100days"
    ],
    "syndication": [
        "https://t.me/Telegram/260"
    ],
    "content": {
        "text": "#100days 59 - Made a decent amount of progress on the PostrChild extension as my IndieWebCamp project, but still not very near ready for release \ud83d\ude23What I did manage to do was: make the autocompletion system for emoji, blocks and contacts much more reliable, fix the button to easily reply to any page and some updates to inserting and uploading images.I still have a lot left to do but I am really hoping I now have the biggest hurdles out of the way and future development will go more smoothly.",
        "html": "<p>#100days 59 - Made a decent amount of progress on the PostrChild extension as my IndieWebCamp project, but still not very near ready for release \ud83d\ude23</p><p>What I did manage to do was: make the autocompletion system for emoji, blocks and contacts much more reliable, fix the button to easily reply to any page and some updates to inserting and uploading images.</p><p>I still <a href=\"https://github.com/grantcodes/postrchild-extension/projects/1\">have a lot left to do</a> but I am really hoping I now have the biggest hurdles out of the way and future development will go more smoothly.</p>"
    },
    "author": {
        "type": "card",
        "name": "Grant Richmond",
        "url": "https://grant.codes/",
        "photo": "https://images.weserv.nl/?url=grant.codes%2Fimg%2Fme.jpg&errorredirect=grant.codes%2Fimg%2Fme.jpg&w=20&h=20&fit=contain&dpr=2"
    },
    "post-type": "note",
    "_id": "12800338",
    "_source": "11",
    "_is_read": true
}

Redesigning my Blog Post Pages

{
    "type": "entry",
    "published": "2020-06-28T11:18:18-07:00",
    "summary": "I had a great time in the sessions at IndieWebCamp West yesterday! Today is project day, so I started the morning off listening to some chill tunes with other folks on the Zoom \"hallway track\" deciding what to work on.",
    "url": "https://aaronparecki.com/2020/06/28/7/blog-posts",
    "category": [
        "indieweb",
        "indiewebcamp"
    ],
    "name": "Redesigning my Blog Post Pages",
    "author": {
        "type": "card",
        "name": "Aaron Parecki",
        "url": "https://aaronparecki.com/",
        "photo": "https://aperture-media.p3k.io/aaronparecki.com/41061f9de825966faa22e9c42830e1d4a614a321213b4575b9488aa93f89817a.jpg"
    },
    "post-type": "article",
    "_id": "12796721",
    "_source": "16",
    "_is_read": true
}

Bridgy stats update

{
    "type": "entry",
    "published": "2020-06-27T11:40:37-07:00",
    "url": "https://snarfed.org/2020-06-27_bridgy-stats-update-5",
    "photo": [
        "https://snarfed.org/bridgy_stats/2020/accounts_stacked_thumb.png",
        "https://snarfed.org/bridgy_stats/2020/accounts_thumb.png",
        "https://snarfed.org/bridgy_stats/2020/features_thumb.png",
        "https://snarfed.org/bridgy_stats/2020/webmentions_thumb.png",
        "https://snarfed.org/bridgy_stats/2020/publishes_thumb.png",
        "https://snarfed.org/bridgy_stats/2020/costs_thumb.png"
    ],
    "name": "Bridgy stats update",
    "content": {
        "text": "Another year down, another update on Bridgy\u2018s usage stats! We first announced these during State of the Indieweb at IndieWebCamp West 2020, then posted them here for posterity.\n\n \n\n\n \n\nThe most noticeable part of last year\u2019s stats was losing Facebook and Google+. We made up for that this year by adding three new silos: Mastodon, Meetup, and Reddit. (Thanks Jamie, Will!) The real growth story over the past few years, however, has been GitHub. It has almost 400 users now, making it Bridgy\u2019s third largest silo behind Twitter and Instagram!\nOtherwise, growth continues apace, up and to the right.\n\n \n\n\n \n\nWe\u2019ve also seen the all time webmention count continue to increase. By our best estimates, we crossed 1M total webmentions sent in the wild in December 2017, 95% of which was sent or received by Bridgy. It\u2019s now handled over 1.6M, so if that same proportion has held, then roughly 1.7M webmentions total have been sent in the wild to date.\n\n \n\n\n \n\nAlso, this post has the ironic distinction of receiving the most webmentions ever (2441) from Bridgy, outside of home pages. Hmm.\n\n  Do any of you tech folk ever think about just quitting tech altogether? Opening a bakery, or retraining as a park ranger? I\u2019d love to look after a forest for a living. There would be a far lower chance of a guy being in the forest and starting an argument due to his insecurities.\nData,\nmethodology,\npreviously,\npreviously,\npreviously,\npreviously,\npreviously.",
        "html": "<p>\n <a href=\"https://brid.gy/\">\n</a></p>\n<p>Another year down, another update on <a href=\"https://brid.gy/\">Bridgy</a>\u2018s usage stats! We first announced these during State of the Indieweb at <a href=\"https://indieweb.org/2020/West\">IndieWebCamp West 2020</a>, then posted them here for posterity.</p>\n<p style=\"margin-left:0px;margin-right:-10px;\">\n <a href=\"https://snarfed.org/bridgy_stats/2020/accounts_stacked.png\">\n</a></p>\n<p style=\"margin-right:0px;\">\n <a href=\"https://snarfed.org/bridgy_stats/2020/accounts.png\">\n</a></p>\n<p>The most noticeable part of <a href=\"https://snarfed.org/2019-01-02_bridgy-stats-update-4#comment-2731107\">last year\u2019s stats</a> was <a href=\"https://brid.gy/about#rip-facebook\">losing Facebook</a> <a href=\"https://brid.gy/about#rip-google+\">and Google+</a>. We made up for that this year by adding three new silos: Mastodon, Meetup, and Reddit. (Thanks <a href=\"https://www.jvt.me/\">Jamie</a>, <a href=\"https://www.bonkerfield.org/\">Will</a>!) The real growth story over the past few years, however, has been GitHub. It has almost 400 users now, making it Bridgy\u2019s third largest silo behind Twitter and Instagram!</p>\n<p>Otherwise, growth continues apace, up and to the right.</p>\n<p style=\"margin-left:0px;margin-right:-10px;\">\n <a href=\"https://snarfed.org/bridgy_stats/2020/features.png\">\n</a></p>\n<p style=\"margin-right:0px;\">\n <a href=\"https://snarfed.org/bridgy_stats/2020/webmentions.png\">\n</a></p>\n<p>We\u2019ve also seen the all time webmention count continue to increase. By our best estimates, <a href=\"https://snarfed.org/1-million-webmentions\">we crossed 1M total webmentions sent in the wild in December 2017</a>, 95% of which was sent or received by Bridgy. <a href=\"https://brid.gy/#stats\">It\u2019s now handled over 1.6M</a>, so if that same proportion has held, then roughly 1.7M webmentions total have been sent in the wild to date.</p>\n<p style=\"margin-left:0px;margin-right:-10px;\">\n <a href=\"https://snarfed.org/bridgy_stats/2020/publishes.png\">\n</a></p>\n<p style=\"margin-right:0px;\">\n <a href=\"https://snarfed.org/bridgy_stats/2020/costs.png\">\n</a></p>\n<p>Also, <a href=\"https://www.sonniesedge.net/notes/3055/\">this post has the ironic distinction of receiving the most webmentions ever (2441) from Bridgy</a>, outside of home pages. Hmm.</p>\n<blockquote><p>\n  Do any of you tech folk ever think about just quitting tech altogether? Opening a bakery, or retraining as a park ranger? I\u2019d love to look after a forest for a living. There would be a far lower chance of a guy being in the forest and starting an argument due to his insecurities.</p></blockquote>\n<p><a href=\"https://docs.google.com/spreadsheets/d/1VhGiZ9Z9PEl7f9ciiVZZgupNcUTsRVltQ8_CqFETpfU/edit\">Data</a>,\n<a href=\"https://github.com/snarfed/bridgy#stats\">methodology</a>,\n<a href=\"https://snarfed.org/2018-01-02_bridgy-stats-update-4\">previously</a>,\n<a href=\"https://snarfed.org/2018-01-02_bridgy-stats-update-3\">previously</a>,\n<a href=\"https://snarfed.org/2016-06-06_bridgy-stats-update-2\">previously</a>,\n<a href=\"https://snarfed.org/2015-12-07_bridgy-stats-update\">previously</a>,\n<a href=\"https://snarfed.org/2014-11-06_happy-1000th-bridgy\">previously</a>.</p>"
    },
    "author": {
        "type": "card",
        "name": "Ryan Barrett",
        "url": "https://snarfed.org/",
        "photo": "https://secure.gravatar.com/avatar/947b5f3f323da0ef785b6f02d9c265d6?s=96&d=blank&r=g"
    },
    "post-type": "photo",
    "_id": "12778501",
    "_source": "3",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-06-27T12:13:36-07:00",
    "url": "https://aaronparecki.com/2020/06/27/13/indiewebcamp",
    "category": [
        "indiewebcamp"
    ],
    "photo": [
        "https://aperture-media.p3k.io/aaronparecki.com/2127d386ad2d600b29de4313d948c59299e726100c6b27a10ccbc350ef370ae7.jpg"
    ],
    "syndication": [
        "https://twitter.com/aaronpk/status/1276956880888229888",
        "https://micro.blog/aaronpk/9852252"
    ],
    "content": {
        "text": "Great crowd for @IndieWebCamp West keynotes and intros! We're running sessions the rest of the day, and projects and demos tomorrow! Join here \u27a4 https://events.indieweb.org/2020/06/indiewebcamp-west-2020-ZB8zoAAu6sdN",
        "html": "Great crowd for <a href=\"https://indieweb.org/IndieWebCamps\">@IndieWebCamp</a> West keynotes and intros! We're running sessions the rest of the day, and projects and demos tomorrow! Join here \u27a4 <a href=\"https://events.indieweb.org/2020/06/indiewebcamp-west-2020-ZB8zoAAu6sdN\"><span>https://</span>events.indieweb.org/2020/06/indiewebcamp-west-2020-ZB8zoAAu6sdN</a>"
    },
    "author": {
        "type": "card",
        "name": "Aaron Parecki",
        "url": "https://aaronparecki.com/",
        "photo": "https://aperture-media.p3k.io/aaronparecki.com/41061f9de825966faa22e9c42830e1d4a614a321213b4575b9488aa93f89817a.jpg"
    },
    "post-type": "photo",
    "_id": "12776540",
    "_source": "16",
    "_is_read": true
}

Are Micropub Queries the missing link?

{
    "type": "entry",
    "published": "2020-06-27T16:14:37.887Z",
    "url": "https://grant.codes/2020/06/27/micropub-queries",
    "name": "Are Micropub Queries the missing link?",
    "content": {
        "text": "With IndieWebCamp West just about to start I figured this would be a good time to write up some of my thoughts on one of the missing pieces of the IndieWeb ecosystem: Micropub Queries.What is MicropubThe quick version is that Micropub is an open standard to allow publishing to your own website from a variety of apps or clients. It's great. I love it. But it's mostly a one way experience, publishing only.The spec does define ways to query and update specific posts, but they are generally not implemented by very many clients - perhaps because they are more complex to design and develop or perhaps because it's not the most useful thing.Increase in usageRecently we've also seen a couple of large projects add Micropub support in iA Writer and Thread Reader. Which is awesome, but I think if queries become more mainstream there is the potential for much better apps and a more convincing reason for Micropub to be integrated into more existing apps.QueriesProposals for Micropub Queries have been around for a while without a huge amount of movement. Maybe it's a chicken and egg type scenario, if no clients add support, then why add support to your site?Existing examplesI've made a couple of things that use queries myself. My chatbot can query posts (although it's not very useful) and Together has a useful view of your published posts as well, and Indigenous for Android also can show a basic list of your published posts.But for me all those examples are fairly basic, and there is a lot of potential for more powerful and compelling experiences.A vision of the futureThere are so many possibilities for super useful experiences for Micropub Queries that I'm just going to list off a bunch of things I can think of:Readers could check if you have already liked, bookmarked, replied etc. to a url\nApps like indiebookclub could query for books you have already read, or even track your reading progress\nSave drafts to your own site and then edit and publish them from a Micropub client\nFull admin UIs like the WordPress admin menu or Publii (recently mentioned in the IndieWeb chat) could support Micropub with the ability to query for drafts, trash, different post types etc.\nFind your last location by querying the last post with a location included\nGallery posting apps that can query for already created photos like best nine\n\nCollection apps that can find existing posts\nSearch your own posts via the API\nCreate generic sites just using the Micropub Query API, eg. checkin views are hard, an app could query your site and generate a nice UI for you\nThere are so many more that I've thought of and forgotten or that I've not though of yet.Although there are plenty of nice, usable apps on the Indieweb I still think we are missing a next level experience to really highlight the power and potential of Indieweb technologies, maybe Micropub Queries could help bring that about...",
        "html": "<p>With <a href=\"https://indieweb.org/2020/West\">IndieWebCamp West just about to start</a> I figured this would be a good time to write up some of my thoughts on one of the missing pieces of the IndieWeb ecosystem: Micropub Queries.</p><h2>What is Micropub</h2><p>The quick version is that <a href=\"https://indieweb.org/Micropub\">Micropub</a> is an open standard to allow publishing to your own website from a variety of apps or clients. It's great. I love it. But it's <em>mostly</em> a one way experience, publishing only.</p><p>The spec does define ways to query and update specific posts, but they are generally not implemented by very many clients - perhaps because they are more complex to design and develop or perhaps because it's not the most useful thing.</p><h3>Increase in usage</h3><p>Recently we've also seen a couple of large projects add Micropub support in <a href=\"https://ia.net/writer\">iA Writer</a> and <a href=\"https://threadreaderapp.com/\">Thread Reader</a>. Which is awesome, but I think if queries become more mainstream there is the potential for much better apps and a more convincing reason for Micropub to be integrated into more existing apps.</p><h2>Queries</h2><p><a href=\"https://github.com/indieweb/micropub-extensions/issues/4\">Proposals for Micropub Queries</a> have been around for a while without a huge amount of movement. Maybe it's a chicken and egg type scenario, if no clients add support, then why add support to your site?</p><h3>Existing examples</h3><p>I've made a couple of things that use queries myself. My <a href=\"https://postrchild.com/\">chatbot</a> can query posts (although it's not very useful) and <a href=\"https://alltogethernow.io\">Together</a> has a useful view of your published posts as well, and <a href=\"https://indieweb.org/Indigenous_for_Android\">Indigenous for Android</a> also can show a basic list of your published posts.</p><p>But for me all those examples are fairly basic, and there is a lot of potential for more powerful and compelling experiences.</p><h3>A vision of the future</h3><p>There are so many possibilities for super useful experiences for Micropub Queries that I'm just going to list off a bunch of things I can think of:</p><ul><li>Readers could check if you have already liked, bookmarked, replied etc. to a url</li>\n<li>Apps like <a href=\"https://indiebookclub.biz/\">indiebookclub</a> could query for books you have already read, or even track your reading progress</li>\n<li>Save drafts to your own site and then edit and publish them from a Micropub client</li>\n<li>Full admin UIs like the WordPress admin menu or <a href=\"https://getpublii.com/\">Publii</a> (recently mentioned in the IndieWeb chat) could support Micropub with the ability to query for drafts, trash, different post types etc.</li>\n<li>Find your last location by querying the last post with a location included</li>\n<li>Gallery posting apps that can query for already created photos like <a href=\"https://indieweb.org/best_nine\">best nine</a>\n</li>\n<li>Collection apps that can find existing posts</li>\n<li>Search your own posts via the API</li>\n<li>Create generic sites just using the Micropub Query API, eg. checkin views are hard, an app could query your site and generate a nice UI for you</li>\n</ul><p>There are so many more that I've thought of and forgotten or that I've not though of yet.</p><p>Although there are plenty of nice, usable apps on the Indieweb I still think we are missing a next level experience to really highlight the power and potential of Indieweb technologies, maybe Micropub Queries could help bring that about...</p>"
    },
    "author": {
        "type": "card",
        "name": "Grant Richmond",
        "url": "https://grant.codes/",
        "photo": "https://images.weserv.nl/?url=grant.codes%2Fimg%2Fme.jpg&errorredirect=grant.codes%2Fimg%2Fme.jpg&w=20&h=20&fit=contain&dpr=2"
    },
    "post-type": "article",
    "_id": "12772813",
    "_source": "11",
    "_is_read": true
}

{
    "type": "entry",
    "author": {
        "name": "Manton Reece",
        "url": "https://www.manton.org/",
        "photo": "https://micro.blog/manton/avatar.jpg"
    },
    "url": "https://www.manton.org/2020/06/27/with-wwdc-mostly.html",
    "content": {
        "html": "<p>With WWDC mostly wrapped up, it\u2019s time to look to <a href=\"https://indieweb.org/2020/West\">IndieWebCamp West</a> this weekend. Virtual doors open via Zoom at 9am Pacific, then keynotes, demos, and afternoon sessions.</p>",
        "text": "With WWDC mostly wrapped up, it\u2019s time to look to IndieWebCamp West this weekend. Virtual doors open via Zoom at 9am Pacific, then keynotes, demos, and afternoon sessions."
    },
    "published": "2020-06-27T09:56:27-05:00",
    "post-type": "note",
    "_id": "12771508",
    "_source": "12",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-06-26 19:46-0700",
    "url": "https://gregorlove.com/2020/06/by-the-way-are-you/",
    "content": {
        "text": "By the way, are you using the PW2 or PW3 version of the Webmention plugin? I'm still on PW2 myself but will likely switch to PW3 in the coming months. I plan to support both versions for a while, but since most new people will be on PW3 I'll feel more comfortable once I'm running that on my own site as well.",
        "html": "<p>By the way, are you using the PW2 or PW3 version of the Webmention plugin? I'm still on PW2 myself but will likely switch to PW3 in the coming months. I plan to support both versions for a while, but since most new people will be on PW3 I'll feel more comfortable once I'm running that on my own site as well.</p>"
    },
    "post-type": "note",
    "_id": "12761998",
    "_source": "95",
    "_is_read": true
}

Excavating my former homepages

{
    "type": "entry",
    "author": {
        "name": null,
        "url": "https://petermolnar.net/",
        "photo": null
    },
    "url": "https://petermolnar.net/article/content-archeology/",
    "published": "2020-06-26T21:55:00+01:00",
    "content": {
        "html": "Someone, a long time ago came up with the thought that whatever is put on the internet, it'll be there forever. Well, it's wrong. The old versions of my own website, including their design, was long gone, so I decided to put the Indiana Jones hat on, and started digging.<p><em>It's early 1999. I'm 13 years old, freshman in high school<a href=\"https://petermolnar.net/#fn1\">1</a>. Altavista is still a decent search engine. At this point I've been using the web for years, but never really participated in making it yet, and it was about to change. The idea of having a homepage stuck with me: I could make my own design, my own little world, without limits, with any kind of content I want to, without anyone supervising. This was such an exciting prospect that it had to be done. Plus: it was open for anyone, like instantly hanging your work in an art gallery!</em></p>\n<p>Long story short, I did that website. And the next one, and the next one... and I kept going till this very day. The tragedy of it is that due to multiple reasons, the first two iterations and designs of my site are now completely lost.</p>\n<p>Back in those days my English skills or my \"programming\" skills were quite lacking. I never heard the idea of version controlling, digital archiving, snapshots - these came so much later. Hungary tends to teach foreign languages with an overwhelming amount of grammar, resulting in a nice, but unusable skill when someone wants to explore the internet.</p>\n<p>Put these and the options on the mid 90s web together - generic Hungary is <em>always</em> around 5 years behind the English speaking world in internet trends. My first sites were made with Microsoft FrontPage 98, FTP-d directly into \"production\", always overwriting the tiny, free space on free homepage providers, hopping from one to another, because the new one offered 5MB for free, not just 1.</p>\n<h2>1999 - 2003 - the FrontPage years</h2>\n<p>When I decided to go after the old versions of my gazillion URLs, I first turned to archive.org, like everyone would. For my gigantic surprise, after remembering that the provider <code>extra.hu</code> had subfolders, and not sub-domains, I found a version from May 2001! A year earlier than my earliest archive! Sadly, it was the already on it's third design, and because archive.org didn't have the images from back then, it wouldn't have mattered anyway.</p>\n<p>The good news was that my site at this point was static HTML, so \"recovering\" it was simply opening the files. Did you know web browsers still support frames?</p>\n<p>I went through this version quite a few times lately, and I alway overlooked a section, in which I had a review of an Ericsson T29s - including notes on how to hack a data cable for it, downloadable programs, full eeprom and flash binaries, and a fascinating note of:</p>\n<blockquote>\n<p>I'm utterly tired that there are only ads on every page, and no real stuff, so I thought I'll put some here, based on my own experience</p>\n</blockquote>\n<p>Again, this is roughly 2002. It's good to be reminded by my own words, that the internet had this problem for a very long time by now.</p>\n<p>I decided put the review back up - look under the IT tab -, even though chances that someone is looking for these is converging to 0.</p>\n<img src=\"https://petermolnar.net/article/content-archeology/2002.jpg\" title=\"2002.jpg\" alt=\"2002 design - tables, absolutely no accessibility, but hey, the content was already about tinkering with phones, and the colour palette looked very similar to my current dark theme.\" />\n    2002 design - tables, absolutely no accessibility, but hey, the content was already about tinkering with phones, and the colour palette looked very similar to my current dark theme.\n<h2>2004 - the PHP4 years</h2>\n<p>To access the 2004 version, magic has to be called upon - also knowns as virtual machines. I had to spin up a Debian Sarge<a href=\"https://petermolnar.net/#fn2\">2</a>, because I needed PHP4 - <strong>immeasurable kudos for the Debian archives<a href=\"https://petermolnar.net/#fn3\">3</a> for still having install CDs, and working software repositories!</strong> The only trick is that during the install the apt mirror needs to be set to <code>archive.debian.org</code>.</p>\n<p>I barely remembered this version. It also made me realize that I was microblogging, before it even became a term - although as Kevin Marks<a href=\"https://petermolnar.net/#fn4\">4</a> pointed it out on the <code>indieweb-chat</code> channel on Freenode, everyone was microblogging at first: the idea of one page per entry came later.</p>\n<p>After not too much digging I found two more phone reviews, also with a lot of background content - in case you're after an 50KB mobile Java email application, I have one for you.</p>\n<img src=\"https://petermolnar.net/article/content-archeology/2004.jpg\" title=\"2004.jpg\" alt=\"2004 - the layout probably worked in IE5 and nothing else\" />\n    2004 - the layout probably worked in IE5 and nothing else\n<p>Instead of webrings, in Hungary, we regularly exchanged banners with eachother: small images, that linked to another site; sort of a graphical blogroll. Contrary to mathematical probability, I found a banner that is still alive! 16 years and still strong: the Hungarian Stargate fan site<a href=\"https://petermolnar.net/#fn5\">5</a> deserves some attribution for that banner<a href=\"https://petermolnar.net/#fn6\">6</a></p>\n<h2>2007 - 2009 - the custom CMS with friends years</h2>\n<p>2007 brought a massive change: I wanted to make the site tiny a community site, a place to where my close friends could also upload photos, short stories, art.</p>\n<p>3 years meant PHP5, so I spun a Debian Etch<a href=\"https://petermolnar.net/#fn7\">7</a> up. These were the days when I had my custom, PHP-based CMS, of which if I looked at the code of; it's proper nightmare material.</p>\n<p>The relevation of the 2007 version was the amount of photos I sort of accidentally <em>removed</em> from my site. In the coming years my site slowly morphed into a portfolio for my photos and my sysadmining skills. When I finally reverted, and swapped from curated, small galleries to a stream of individual images, I never put the old portfolio back. This will need to be addressed.</p>\n<p>Related to this, I came across Ana's \"Blogging and me\" post at <a href=\"https://ohhelloana.blog/blogging-and-me/\">https://ohhelloana.blog/blogging-and-me/</a> . She went through very similar cycles as I did: a website first, blogging of anything, that gradually became a hyper-focused, work-only site, which then got neglected, because it wasn't fun any more. Read it. If you didn't (yet) had these cycles, or if you already did; in both cases, it's a fantastic piece.</p>\n<a href=\"https://petermolnar.net/article/content-archeology/2007_large.jpg\"><img src=\"https://petermolnar.net/article/content-archeology/2007.jpg\" title=\"2007.jpg\" alt=\"Such design, much images. Also, curves! Curves everywhere! Regardless, I believe this was a pleasent to look at design and colour combination, plus those photos are all missing from my site at the moment o.O\" /></a>\n    Such design, much images. Also, curves! Curves everywhere! Regardless, I believe this was a pleasent to look at design and colour combination, plus those photos are all missing from my site at the moment o.O\n<h2>2008 - 2013 - the portfolio years</h2>\n<p>Parallel to th community site idea, I wanted to have a portfolio site; one that is professional content only. At that point, I still believed my life will have something to do with photography, so I made a photo portfolio site under the new domain <code>petermolnar.eu</code>. My name is quite a common one in Hungary, but the <code>.eu</code> domains were new, and I grabbed it immediately.</p>\n<p>During these years I actively participated in an alternative community in Hungary. I wrote some articles to their site, which are still up, to this very day, but the idea to put those on my own site (as well) didn't occur to me.</p>\n<p>In 2010 , the limitations of my CMS collided with the fact that I lost touch with most people who had some content on that community site. I decided to close it, and turn my full attention towards a personal site - by switching it to WordPress.</p>\n<p>Soon after college (2009), I ended up working as a sysadmin; it made sense to start writing my findings, my how-tos (mostly for myself) down.</p>\n<p>With that, I've thrown a silly amount of old content away. No thoughts or personal blog entries any more: streamlined photo portfolio, photo equiment review - <em>this one never even took off; the 2 entries I wrote for it are so low quality that they were not worth salvaging</em> -, and a sysadmin blog is the way to go! I should never have done that, but these were the early Facebook years; everyone was doing personal communication in social silos. It seemed like a good idea that time. Mea culpa.</p>\n<p>I did try cross-posting and syndicating early on: links to new entries to twitter, to facebook, but soon it looked overwhelming. When the same content goes everywhere, and you happend to have a large cross-section of the same people on each silo, it'll be too much for them.</p>\n<img src=\"https://petermolnar.net/article/content-archeology/2010.jpg\" title=\"2010.jpg\" alt=\"First iteration of my very own WordPress theme - along with the immeasurable changes of finally moving to my own domain, with only professional-ish content\" />\n    First iteration of my very own WordPress theme - along with the immeasurable changes of finally moving to my own domain, with only professional-ish content\n<p>Slowly, but steadily, topics and sections kept creeping back in. At first, it was merely a <code>photoblog</code> tab, in which I put collection of images grouped by a topic. It took me a while to realize I didn't like it that way: without context, the galleries were distant; they didn't feel like memories, more like and extended, endless portfolio, yet I kept going with it for years.</p>\n<img src=\"https://petermolnar.net/article/content-archeology/2011.jpg\" title=\"2011.jpg\" alt=\"Second WordPress theme from somewhere in 2011\" />\n    Second WordPress theme from somewhere in 2011\n<p>By the end of 2013, I was back to having a \"world view\" section that was to become \"journal\". The trigger for this was our relocation to England: there was an irrepressible urge to write about our new life.</p>\n<a href=\"https://petermolnar.net/article/content-archeology/2013_large.jpg\"><img src=\"https://petermolnar.net/article/content-archeology/2013.jpg\" title=\"2013.jpg\" alt=\"Thankfully the streamlining didn't stick and the site kept getting more content sections back\" /></a>\n    Thankfully the streamlining didn't stick and the site kept getting more content sections back\n<h2>2014 - 2017 - The features and contents years</h2>\n<p>Sometimes in 2014 I stumbled upon the indieweb<a href=\"https://petermolnar.net/#fn8\">8</a> community. With that, my site started to get features - and a lot of them.</p>\n<h3>2014</h3>\n<a href=\"https://petermolnar.net/article/content-archeology/2014_large.jpg\"><img src=\"https://petermolnar.net/article/content-archeology/2014.jpg\" title=\"2014.jpg\" alt=\"See those bubbles? Those were mainly comments, backfilled from Facebook.\" /></a>\n    See those bubbles? Those were mainly comments, backfilled from Facebook.\n<a href=\"https://petermolnar.net/article/content-archeology/2014-2_large.jpg\"><img src=\"https://petermolnar.net/article/content-archeology/2014-2.jpg\" title=\"2014-2.jpg\" alt=\"Calculated read time; I believe medium.com brought it in.\" /></a>\n    Calculated read time; I believe medium.com brought it in. \n<a href=\"https://petermolnar.net/article/content-archeology/2014-3_large.jpg\"><img src=\"https://petermolnar.net/article/content-archeology/2014-3.jpg\" title=\"2014-3.jpg\" alt=\"I still had my photo portfolio as well. It was already a responsive design; on mobile, it because a simple list of full-width images.\" /></a>\n    I still had my photo portfolio as well. It was already a responsive design; on mobile, it because a simple list of full-width images.\n<p>Once you read too many studies on the internet you may start questioning your own experiences with certain things. One of these is the \"light on dark\" vs \"dark on light\" representation when it comes to computers and the web. To obey this, I started presenting text content in light, photo content with dark background and themeing; a route I should never have taken.</p>\n<p>During the 15 years prior to this, my site was dark. This page is supposed to be my home, and it's supposed to represent me on the internet. And I'm not a light background person; I never was. When I still used Window XP it looked like this:</p>\n<img src=\"https://petermolnar.net/article/content-archeology/windows-xp-themed.png\" title=\"windows-xp-themed.png\" alt=\"The bottom is a launcher bar, not opened applications.\" />\n    The bottom is a launcher bar, not opened applications. \n<p>Even so, for the coming years, the design went lighter and lighter.</p>\n<h3>2016</h3>\n<img src=\"https://petermolnar.net/article/content-archeology/2016.jpg\" title=\"2016.jpg\" alt=\"Painfully bright, and never felt like my own. Plus there was a huge stream of content: bookmarks, quotes, twitter reply copies, etc. I turned my site into a stream, and the more content it had, the more distant it felt, the less of a homepage it became.\" />\n    Painfully bright, and never felt like my own. Plus there was a huge stream of content: bookmarks, quotes, twitter reply copies, etc. I turned my site into a stream, and the more content it had, the more distant it felt, the less of a homepage it became.\n<h3>2017</h3>\n<img src=\"https://petermolnar.net/article/content-archeology/2017.jpg\" title=\"2017.jpg\" alt=\"In 2017, I found the icons I'm using till this very day, but I still had the dreaded light design. Plus I added even more content, including the idea to backfill EVERYTHING I ever made on the internet. Needless to say this idea was later reveted, though without the journey, I may never have realized why it was bad.\" />\n    In 2017, I found the icons I'm using till this very day, but I still had the dreaded light design. Plus I added even more content, including the idea to backfill EVERYTHING I ever made on the internet. Needless to say this idea was later reveted, though without the journey, I may never have realized why it was bad.\n<h2>2018 - back to the roots: dark, static, simple.</h2>\n<p>Content was dropped, and I again, felt like I have a homepage, and not a one person social media site.</p>\n<img src=\"https://petermolnar.net/article/content-archeology/2018.jpg\" title=\"2018.jpg\" alt=\"Back to the darkness. Still not the best, but much less strain on my eyes.\" />\n    Back to the darkness. Still not the best, but much less strain on my eyes. \n<a href=\"https://petermolnar.net/article/content-archeology/2019_large.jpg\"><img src=\"https://petermolnar.net/article/content-archeology/2019.jpg\" title=\"2019.jpg\" alt=\"Turned out the studies were right about a few things, and that for some, light on dark is unreadable. So for everyone to be happy, I added an option to switch between them, making the dark, or the operating system setting the default. I also tried to make it look like some really messed up terminal. It didn't work.\" /></a>\n    Turned out the studies were right about a few things, and that for some, light on dark is unreadable. So for everyone to be happy, I added an option to switch between them, making the dark, or the operating system setting the default. I also tried to make it look like some really messed up terminal. It didn't work.\n<p>And thus we arrived to 2020, and you're looking at the freshest, most current iteration of my website.</p>\n<h2>Conclusions</h2>\n<p>I think at the beginning I started to dig my sites up to verify how much have I gone back to my roots. To see how it started, how it done, when it was solely for the fun. Ana's post, which I already mentioned<a href=\"https://petermolnar.net/#fn9\">9</a> was definitely a trigger to take this journey.</p>\n<p>I lost the first two designs. I remember the very first vividly, with the water-like repeating background. The second I completely forgot about, and only had some reminders in words, from a microblog entry, from 2001, when I was being happy replacing it with something fresh and new.</p>\n<p>My conclusions are simple: your homepage is called that for a reason. It's a poster, a gallery, a window to you, out for anyone to visit, to see. Show everything; show all the topics you're interested in, drag all the posts from decades ago, and only police the ones that are truly outdated - if there are any. It's not a social media profile. It's not a resume. It's you.</p>\n\n\n<ol><li><p><a href=\"https://en.wikipedia.org/wiki/Education_in_Hungary\">https://en.wikipedia.org/wiki/Education_in_Hungary</a><a href=\"https://petermolnar.net/#fnref1\">\u21a9</a></p></li>\n<li><p><a href=\"https://cdimage.debian.org/mirror/cdimage/archive/3.0_r6/i386/iso-cd/\">https://cdimage.debian.org/mirror/cdimage/archive/3.0_r6/i386/iso-cd/</a><a href=\"https://petermolnar.net/#fnref2\">\u21a9</a></p></li>\n<li><p><a href=\"https://cdimage.debian.org/mirror/cdimage/archive/\">https://cdimage.debian.org/mirror/cdimage/archive/</a><a href=\"https://petermolnar.net/#fnref3\">\u21a9</a></p></li>\n<li><p><a href=\"http://www.kevinmarks.com/\">http://www.kevinmarks.com/</a><a href=\"https://petermolnar.net/#fnref4\">\u21a9</a></p></li>\n<li><p><a href=\"http://www.csillagkapu.hu/\">http://www.csillagkapu.hu/</a><a href=\"https://petermolnar.net/#fnref5\">\u21a9</a></p></li>\n<li><p><a href=\"http://www.csillagkapu.hu/img/agbanner.gif\">http://www.csillagkapu.hu/img/agbanner.gif</a><a href=\"https://petermolnar.net/#fnref6\">\u21a9</a></p></li>\n<li><p><a href=\"https://cdimage.debian.org/mirror/cdimage/archive/4.0_r0/i386/iso-cd/\">https://cdimage.debian.org/mirror/cdimage/archive/4.0_r0/i386/iso-cd/</a><a href=\"https://petermolnar.net/#fnref7\">\u21a9</a></p></li>\n<li><p><a href=\"https://indieweb.org/\">https://indieweb.org/</a><a href=\"https://petermolnar.net/#fnref8\">\u21a9</a></p></li>\n<li><p><a href=\"https://ohhelloana.blog/blogging-and-me/\">https://ohhelloana.blog/blogging-and-me/</a><a href=\"https://petermolnar.net/#fnref9\">\u21a9</a></p></li>\n</ol>",
        "text": "Someone, a long time ago came up with the thought that whatever is put on the internet, it'll be there forever. Well, it's wrong. The old versions of my own website, including their design, was long gone, so I decided to put the Indiana Jones hat on, and started digging.It's early 1999. I'm 13 years old, freshman in high school1. Altavista is still a decent search engine. At this point I've been using the web for years, but never really participated in making it yet, and it was about to change. The idea of having a homepage stuck with me: I could make my own design, my own little world, without limits, with any kind of content I want to, without anyone supervising. This was such an exciting prospect that it had to be done. Plus: it was open for anyone, like instantly hanging your work in an art gallery!\nLong story short, I did that website. And the next one, and the next one... and I kept going till this very day. The tragedy of it is that due to multiple reasons, the first two iterations and designs of my site are now completely lost.\nBack in those days my English skills or my \"programming\" skills were quite lacking. I never heard the idea of version controlling, digital archiving, snapshots - these came so much later. Hungary tends to teach foreign languages with an overwhelming amount of grammar, resulting in a nice, but unusable skill when someone wants to explore the internet.\nPut these and the options on the mid 90s web together - generic Hungary is always around 5 years behind the English speaking world in internet trends. My first sites were made with Microsoft FrontPage 98, FTP-d directly into \"production\", always overwriting the tiny, free space on free homepage providers, hopping from one to another, because the new one offered 5MB for free, not just 1.\n1999 - 2003 - the FrontPage years\nWhen I decided to go after the old versions of my gazillion URLs, I first turned to archive.org, like everyone would. For my gigantic surprise, after remembering that the provider extra.hu had subfolders, and not sub-domains, I found a version from May 2001! A year earlier than my earliest archive! Sadly, it was the already on it's third design, and because archive.org didn't have the images from back then, it wouldn't have mattered anyway.\nThe good news was that my site at this point was static HTML, so \"recovering\" it was simply opening the files. Did you know web browsers still support frames?\nI went through this version quite a few times lately, and I alway overlooked a section, in which I had a review of an Ericsson T29s - including notes on how to hack a data cable for it, downloadable programs, full eeprom and flash binaries, and a fascinating note of:\n\nI'm utterly tired that there are only ads on every page, and no real stuff, so I thought I'll put some here, based on my own experience\n\nAgain, this is roughly 2002. It's good to be reminded by my own words, that the internet had this problem for a very long time by now.\nI decided put the review back up - look under the IT tab -, even though chances that someone is looking for these is converging to 0.\n\n    2002 design - tables, absolutely no accessibility, but hey, the content was already about tinkering with phones, and the colour palette looked very similar to my current dark theme.\n2004 - the PHP4 years\nTo access the 2004 version, magic has to be called upon - also knowns as virtual machines. I had to spin up a Debian Sarge2, because I needed PHP4 - immeasurable kudos for the Debian archives3 for still having install CDs, and working software repositories! The only trick is that during the install the apt mirror needs to be set to archive.debian.org.\nI barely remembered this version. It also made me realize that I was microblogging, before it even became a term - although as Kevin Marks4 pointed it out on the indieweb-chat channel on Freenode, everyone was microblogging at first: the idea of one page per entry came later.\nAfter not too much digging I found two more phone reviews, also with a lot of background content - in case you're after an 50KB mobile Java email application, I have one for you.\n\n    2004 - the layout probably worked in IE5 and nothing else\nInstead of webrings, in Hungary, we regularly exchanged banners with eachother: small images, that linked to another site; sort of a graphical blogroll. Contrary to mathematical probability, I found a banner that is still alive! 16 years and still strong: the Hungarian Stargate fan site5 deserves some attribution for that banner6\n2007 - 2009 - the custom CMS with friends years\n2007 brought a massive change: I wanted to make the site tiny a community site, a place to where my close friends could also upload photos, short stories, art.\n3 years meant PHP5, so I spun a Debian Etch7 up. These were the days when I had my custom, PHP-based CMS, of which if I looked at the code of; it's proper nightmare material.\nThe relevation of the 2007 version was the amount of photos I sort of accidentally removed from my site. In the coming years my site slowly morphed into a portfolio for my photos and my sysadmining skills. When I finally reverted, and swapped from curated, small galleries to a stream of individual images, I never put the old portfolio back. This will need to be addressed.\nRelated to this, I came across Ana's \"Blogging and me\" post at https://ohhelloana.blog/blogging-and-me/ . She went through very similar cycles as I did: a website first, blogging of anything, that gradually became a hyper-focused, work-only site, which then got neglected, because it wasn't fun any more. Read it. If you didn't (yet) had these cycles, or if you already did; in both cases, it's a fantastic piece.\n\n    Such design, much images. Also, curves! Curves everywhere! Regardless, I believe this was a pleasent to look at design and colour combination, plus those photos are all missing from my site at the moment o.O\n2008 - 2013 - the portfolio years\nParallel to th community site idea, I wanted to have a portfolio site; one that is professional content only. At that point, I still believed my life will have something to do with photography, so I made a photo portfolio site under the new domain petermolnar.eu. My name is quite a common one in Hungary, but the .eu domains were new, and I grabbed it immediately.\nDuring these years I actively participated in an alternative community in Hungary. I wrote some articles to their site, which are still up, to this very day, but the idea to put those on my own site (as well) didn't occur to me.\nIn 2010 , the limitations of my CMS collided with the fact that I lost touch with most people who had some content on that community site. I decided to close it, and turn my full attention towards a personal site - by switching it to WordPress.\nSoon after college (2009), I ended up working as a sysadmin; it made sense to start writing my findings, my how-tos (mostly for myself) down.\nWith that, I've thrown a silly amount of old content away. No thoughts or personal blog entries any more: streamlined photo portfolio, photo equiment review - this one never even took off; the 2 entries I wrote for it are so low quality that they were not worth salvaging -, and a sysadmin blog is the way to go! I should never have done that, but these were the early Facebook years; everyone was doing personal communication in social silos. It seemed like a good idea that time. Mea culpa.\nI did try cross-posting and syndicating early on: links to new entries to twitter, to facebook, but soon it looked overwhelming. When the same content goes everywhere, and you happend to have a large cross-section of the same people on each silo, it'll be too much for them.\n\n    First iteration of my very own WordPress theme - along with the immeasurable changes of finally moving to my own domain, with only professional-ish content\nSlowly, but steadily, topics and sections kept creeping back in. At first, it was merely a photoblog tab, in which I put collection of images grouped by a topic. It took me a while to realize I didn't like it that way: without context, the galleries were distant; they didn't feel like memories, more like and extended, endless portfolio, yet I kept going with it for years.\n\n    Second WordPress theme from somewhere in 2011\nBy the end of 2013, I was back to having a \"world view\" section that was to become \"journal\". The trigger for this was our relocation to England: there was an irrepressible urge to write about our new life.\n\n    Thankfully the streamlining didn't stick and the site kept getting more content sections back\n2014 - 2017 - The features and contents years\nSometimes in 2014 I stumbled upon the indieweb8 community. With that, my site started to get features - and a lot of them.\n2014\n\n    See those bubbles? Those were mainly comments, backfilled from Facebook.\n\n    Calculated read time; I believe medium.com brought it in. \n\n    I still had my photo portfolio as well. It was already a responsive design; on mobile, it because a simple list of full-width images.\nOnce you read too many studies on the internet you may start questioning your own experiences with certain things. One of these is the \"light on dark\" vs \"dark on light\" representation when it comes to computers and the web. To obey this, I started presenting text content in light, photo content with dark background and themeing; a route I should never have taken.\nDuring the 15 years prior to this, my site was dark. This page is supposed to be my home, and it's supposed to represent me on the internet. And I'm not a light background person; I never was. When I still used Window XP it looked like this:\n\n    The bottom is a launcher bar, not opened applications. \nEven so, for the coming years, the design went lighter and lighter.\n2016\n\n    Painfully bright, and never felt like my own. Plus there was a huge stream of content: bookmarks, quotes, twitter reply copies, etc. I turned my site into a stream, and the more content it had, the more distant it felt, the less of a homepage it became.\n2017\n\n    In 2017, I found the icons I'm using till this very day, but I still had the dreaded light design. Plus I added even more content, including the idea to backfill EVERYTHING I ever made on the internet. Needless to say this idea was later reveted, though without the journey, I may never have realized why it was bad.\n2018 - back to the roots: dark, static, simple.\nContent was dropped, and I again, felt like I have a homepage, and not a one person social media site.\n\n    Back to the darkness. Still not the best, but much less strain on my eyes. \n\n    Turned out the studies were right about a few things, and that for some, light on dark is unreadable. So for everyone to be happy, I added an option to switch between them, making the dark, or the operating system setting the default. I also tried to make it look like some really messed up terminal. It didn't work.\nAnd thus we arrived to 2020, and you're looking at the freshest, most current iteration of my website.\nConclusions\nI think at the beginning I started to dig my sites up to verify how much have I gone back to my roots. To see how it started, how it done, when it was solely for the fun. Ana's post, which I already mentioned9 was definitely a trigger to take this journey.\nI lost the first two designs. I remember the very first vividly, with the water-like repeating background. The second I completely forgot about, and only had some reminders in words, from a microblog entry, from 2001, when I was being happy replacing it with something fresh and new.\nMy conclusions are simple: your homepage is called that for a reason. It's a poster, a gallery, a window to you, out for anyone to visit, to see. Show everything; show all the topics you're interested in, drag all the posts from decades ago, and only police the ones that are truly outdated - if there are any. It's not a social media profile. It's not a resume. It's you.\n\n\nhttps://en.wikipedia.org/wiki/Education_in_Hungary\u21a9\nhttps://cdimage.debian.org/mirror/cdimage/archive/3.0_r6/i386/iso-cd/\u21a9\nhttps://cdimage.debian.org/mirror/cdimage/archive/\u21a9\nhttp://www.kevinmarks.com/\u21a9\nhttp://www.csillagkapu.hu/\u21a9\nhttp://www.csillagkapu.hu/img/agbanner.gif\u21a9\nhttps://cdimage.debian.org/mirror/cdimage/archive/4.0_r0/i386/iso-cd/\u21a9\nhttps://indieweb.org/\u21a9\nhttps://ohhelloana.blog/blogging-and-me/\u21a9"
    },
    "name": "Excavating my former homepages",
    "post-type": "article",
    "_id": "12758328",
    "_source": "268",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-06-26 16:14-0700",
    "rsvp": "yes",
    "url": "https://gregorlove.com/2020/06/8pm-is-kinda-late/",
    "in-reply-to": [
        "https://events.indieweb.org/2020/06/indiewebcamp-west-eat-your-own-cooking-pre-party-DH5F8SRjSHff"
    ],
    "content": {
        "text": "8pm is kinda late so I will have PESOS dinner beforehand. Look forward to seeing everyone at the IndieWebCamp West Pre-party, though!",
        "html": "<p>8pm is kinda late so I will have <abbr title=\"Purchased Elsewhere, Syndicate (to your) Own Stomach\">PESOS</abbr> dinner beforehand. Look forward to seeing everyone at the <a class=\"u-in-reply-to\" href=\"https://events.indieweb.org/2020/06/indiewebcamp-west-eat-your-own-cooking-pre-party-DH5F8SRjSHff\">IndieWebCamp West Pre-party</a>, though!</p>"
    },
    "post-type": "rsvp",
    "_id": "12757801",
    "_source": "95",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-06-26T15:51:41-07:00",
    "url": "https://aaronparecki.com/2020/06/26/23/micropub",
    "category": [
        "indieweb",
        "micropub"
    ],
    "syndication": [
        "https://twitter.com/aaronpk/status/1276649364937601025"
    ],
    "content": {
        "text": "This is huge! @ThreadReaderApp can post your Twitter threads to your blog using Micropub! #indieweb https://twitter.com/threadreaderapp/status/1276635949254889472",
        "html": "This is huge! <a href=\"https://twitter.com/ThreadReaderApp\">@ThreadReaderApp</a> can post your Twitter threads to your blog using Micropub! <a href=\"https://aaronparecki.com/tag/indieweb\">#indieweb</a> <a href=\"https://twitter.com/threadreaderapp/status/1276635949254889472\"><span>https://</span>twitter.com/threadreaderapp/status/1276635949254889472</a>"
    },
    "author": {
        "type": "card",
        "name": "Aaron Parecki",
        "url": "https://aaronparecki.com/",
        "photo": "https://aperture-media.p3k.io/aaronparecki.com/41061f9de825966faa22e9c42830e1d4a614a321213b4575b9488aa93f89817a.jpg"
    },
    "post-type": "note",
    "_id": "12757028",
    "_source": "16",
    "_is_read": true
}