{
"type": "entry",
"published": "2018-08-29 18:36-0700",
"url": "http://tantek.com/2018/241/t1/fsws2010-spurred-create-indieweb-community",
"category": [
"OSCON2010",
"FSWS2010",
"OSCON",
"IndieWeb"
],
"in-reply-to": [
"https://twitter.com/mattl/status/1034971169810796545"
],
"content": {
"text": "@mattl are you confusing #OSCON2010 & #FSWS2010 (which was literally the day before #OSCON)?\n\n#FSWS2010 was the meeting that spurred us (@aaronpk @t) to create the #IndieWeb community. Neither of us went to OSCON that year. \ncc: @aprilaser\n\nMore: \n* https://indieweb.org/timeline\n* 2010-07-18 https://indieweb.org/Federated_Social_Web_Summit#Portland_2010\n* 2010-07-19\u202623 https://conferences.oreilly.com/oscon/oscon2010 (also in Portland, Oregon)",
"html": "<a class=\"h-cassis-username\" href=\"https://twitter.com/mattl\">@mattl</a> are you confusing #<span class=\"p-category\">OSCON2010</span> & #<span class=\"p-category\">FSWS2010</span> (which was literally the day before #<span class=\"p-category\">OSCON</span>)?<br /><br />#<span class=\"p-category\">FSWS2010</span> was the meeting that spurred us (<a class=\"h-cassis-username\" href=\"https://twitter.com/aaronpk\">@aaronpk</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/t\">@t</a>) to create the #<span class=\"p-category\">IndieWeb</span> community. Neither of us went to OSCON that year. <br />cc: <a class=\"h-cassis-username\" href=\"https://twitter.com/aprilaser\">@aprilaser</a><br /><br />More: <br />* <a href=\"https://indieweb.org/timeline\">https://indieweb.org/timeline</a><br />* 2010-07-18 <a href=\"https://indieweb.org/Federated_Social_Web_Summit#Portland_2010\">https://indieweb.org/Federated_Social_Web_Summit#Portland_2010</a><br />* 2010-07-19\u202623 <a href=\"https://conferences.oreilly.com/oscon/oscon2010\">https://conferences.oreilly.com/oscon/oscon2010</a> (also in Portland, Oregon)"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "http://tantek.com/",
"photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "reply",
"refs": {
"https://twitter.com/mattl/status/1034971169810796545": {
"type": "entry",
"url": "https://twitter.com/mattl/status/1034971169810796545",
"name": "@mattl\u2019s tweet",
"post-type": "article"
}
},
"_id": "894773",
"_source": "1",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Peter Molnar",
"url": "https://petermolnar.net",
"photo": null
},
"url": "https://petermolnar.net/making-things-private/",
"published": "2017-10-28T15:00:00+00:00",
"content": {
"html": "<p><strong>Have you ever reached the point when you started questioning why you\u2019re doing something? </strong> <strong>I have, but never before with my website.</strong></p>\n<img src=\"https://aperture-proxy.p3k.io/dd33a8d20f1887b86e18873edb03841546d83318/68747470733a2f2f70657465726d6f6c6e61722e6e65742f6d616b696e672d7468696e67732d707269766174652f776861745f69735f6d795f707572706f73652e676966\" title=\"what_is_my_purpose\" alt=\"\" />\nWhat is my purpose? The unfortunate, sentient robot Rick created for the sole purpose of passing the butter.\n<p>The precursor to petermolnar.net started existing for a very simple reason: I wanted an online home and I wanted to put \u201cinteresting\u201d things on it. It was in 1999, before chronological ordering took over the internet.<a href=\"https://petermolnar.net/#fn1\">1</a> Soon it got a blog-ish stream, then a portfolio for my photos, later tech howtos and long journal entries, but one thing was consistent for a very long time: the majority of the content was made by me.</p>\n<p>After encountering the indieweb movement<a href=\"https://petermolnar.net/#fn2\">2</a> I started developing the idea of centralising one\u2019s self. I wrote about it not once<a href=\"https://petermolnar.net/#fn3\">3</a> but twice<a href=\"https://petermolnar.net/#fn4\">4</a>, but going through with importing bookmarks and favourites had an unexpected outcome: they heavily outweighed my original content.</p>\n<p><strong>Do you know what happens when your own website doesn\u2019t have your own content? It starts feeling distant and unfamiliar. When you get here, you either leave the whole thing behind or reboot it somehow. I couldn\u2019t imagine not having a website, so I rebooted.</strong></p>\n<p>I kept long journal entries; notes, for replies to other websites and for short entries; photos; and tech articles - the rest needs to continue it\u2019s life either archived privately or forgotten for good.</p>\n<h2>Outsourcing bookmarks</h2>\n<p>The indieweb wiki entry on <code>bookmark</code> says<a href=\"https://petermolnar.net/#fn5\">5</a>:</p>\n<blockquote>\n<p>Why should you post bookmark posts? Good question. People seem to have reasons for doing so. (please feel free to replace this rhetorical question with actual reasoning)</p>\n</blockquote>\n<p>Since that didn\u2019t help, I stepped back one step further: why do I bookmark?</p>\n<p>Usually it\u2019s because I found them interesting and/or useful. What I ended up having was a date of bookmarking, a title, a URL, and some badly applied tags. In this form, bookmarks on my site were completely useless: I didn\u2019t have the content that made them interesting nor a way to search them properly.</p>\n<p>To solve the first problem, the missing content, my initial idea was to leave everything in place and pull an extract of the content to have something to search in. It didn\u2019t go well. There\u2019s a plethora of js;dr<a href=\"https://petermolnar.net/#fn6\">6</a> sites these days, which don\u2019t, any more, offer a working, plain HTML output without executing JavaScript. For archival purposes, archive.org introduced an arcane file format, WARC<a href=\"https://petermolnar.net/#fn7\">7</a>: it saves everything about the site, but there is no way to simply open it for view. Saving pages with crawlers including media files generated a silly amount of data on my system and soon became unsustainable.</p>\n<p>Soon I realised I\u2019m trying to solve a problem others worked on for years, if not decades, so I decided to look into existing bookmark managers. I tried two paid services, Pinboard<a href=\"https://petermolnar.net/#fn8\">8</a> and Pocket<a href=\"https://petermolnar.net/#fn9\">9</a> first. Pocket would be unbeatable, even though it\u2019s not self hosted, if the article extracts they make were available through their API. They are not. Unfortunately Pinboard wasn\u2019t giving me much over my existing crawler solutions.</p>\n<p><strong>The winner was Wallabag</strong><a href=\"https://petermolnar.net/#fn10\">10</a>: it\u2019s self-hosted, which is great, painful to install and set up, which is not, but it\u2019s completely self-sustaining, runs on SQLite and good enough for me.</p>\n<p>There was only one problem: none of these offered archival copies of images, and some of the bookmarks I made were solely for the photos on the sites. I found a format, called MHTML<a href=\"https://petermolnar.net/#fn11\">11</a>, also known as <code>.eml</code>, which is perfect for single-file archives of HTML pages: it inlines all images as base64 encoded data.</p>\n<p>However, <strong>no browser offers a save-as-mhtml in headless mode, so to get your archives, you\u2019ll need to revisit your bookmarks. All of them.</strong> I enabled<a href=\"https://petermolnar.net/#fn12\">12</a> save as MHTML in Chrome (Firefox doesn\u2019t know this format), installed the Wayback Machine<a href=\"https://petermolnar.net/#fn13\">13</a> extension and saved GBs of websites. I also added them into Wallabag. It\u2019s an interesting, though very long journey, but you\u2019ll rediscover a lot of things for sure.</p>\n<p>When this was done, I dropped thousands of bookmark entries from my site.</p>\n<p><strong>If I do want to share a site, I\u2019ll write a note about it, but bookmarks, without context, belong to my archives.</strong></p>\n<h2>(Some) microblog imports should never have happened</h2>\n<p>I had iterations of imports, so after bookmarks it seemed reasonable to check what else may simply be noise on my site.</p>\n<p><em>Back in the days</em> people mostly wrote much lengthier entries: journal-like diary pages, thoughts, and it was, nearly always, anonymous. It all happened under pseudonyms.</p>\n<p>Parallel to this there were the oldschool instant messengers, like ICQ and MSN Messenger. In many cases, though you all had handles, or numbers, or usernames, you knew exactly who you were talking to. Most of these programs had a feature called status message - looking back at it they may have been precursors to microblogging, but there was a huge difference: they were ephemeral.</p>\n<p>With the rise of Twitter and Facebook status message also came (forced?) real identities, and tools letting us post from anywhere, within seconds. The content that earlier landed in status messages - <em>XY is listening to\u2026.</em>, <em>Feels like\u2026</em>, etc - suddenly became readable at any time, sometimes to anyone.</p>\n<p>I had content like this and I am, as well, guilty of posting short, meaningless, out-of-context entries. Imported burps of private life; useless shares of music pointing to long dead links; one-liner jokes, linking to bash.org; tiny replies and notes that should have been sent privately, either via email or some other mechanism.</p>\n<p><strong>Some things are meant to be ephemeral</strong>, no matter how loud the librarian is screaming deep inside me. <strong>Others belong in logs, and probably not on the public internet</strong>.</p>\n<p>I deleted most of them and placed a <code>HTTP 410 Gone</code> message for their URLs.</p>\n<h2>Reposts are messy</h2>\n<p>For a few months I\u2019ve been silently populating a category that I didn\u2019t promote openly: <code>favorite</code>s. At that page, I basically had a lot of <code>repost</code>s: images and galleries, with complete content, but with big fat URLs over them, linking to the original content.</p>\n<p>By using a silo you usually give permission to the silo to use your work and there. Due to the effects of <code>vote</code>s and <code>like</code>s (see later) you do, in fact, boost the visibility of the artist. <em>Note that usually these permissions are much broader, than you imagine: a lawyer reworded the policy of Instagram to let everyone understand, that by using the service, you allow them to do more or less anything the want to with your work<a href=\"https://petermolnar.net/#fn14\">14</a></em>.</p>\n<p>But what is you take content out of a silo? <strong>The majority of images and works are not licensed in any special way, meaning you need to assume full copyright protection</strong>. Copyright prohibits publishing works without the author\u2019s explicit consensus, <strong>so when you repost</strong> something that doesn\u2019t indicate it\u2019s OK with it - Creative Commons, Public Domain, etc -, <strong>what you do is illegal</strong>.</p>\n<p>Also: for me, it feels like reposts, without notifying the creator, even though the licence allows it, are somewhat unfair - which is exactly what I was doing with these. Webmentions<a href=\"https://petermolnar.net/#fn15\">15</a> would like to address this by having an option to send notifications and delete requests, but silos are not there yet to send or to receive any of these.</p>\n<p><strong>There is a very simple solution: avoid reposting anything without being sure it\u2019s licence allows you.</strong> Save it in a private, offline copy, if you really want to. Cweiske had a nice idea about adding source URLs into JPG XMP metadata <a href=\"https://petermolnar.net/#fn16\">16</a>, so you know where it\u2019s from.</p>\n<h2>Silo reactions only make sense within the silo</h2>\n<p>When I started writing this entry, I differentiated 3, not-comment reaction types in silos:</p>\n<p>A <code>reaction</code> <strong>is a social interaction, essentially a templated comment</strong>. \u201cWell done\u201d, \u201cI disagree\u201d, \u201cbuu\u201d, \u201cacknowledged\u201d, \u2764, \ud83d\udc4d, \u2605, and so on. <em>I asked my wife what she thinks about likes, why she uses them, and I got an unexpected answer: because, unlike with regular, text comments, others will not be able react to it - so no trolling or abuse is possible.</em></p>\n<p>A <code>vote</code> <strong>has direct effect on ranking</strong>: think reddit up- and downvotes. Ideally it\u2019s anonymous: list of voters should not be displayed, not even for the owner of the entry.</p>\n<p>A <code>bookmark</code> <strong>is solely for one\u2019s self: save this entry because I value it and I want to be able to find it again</strong>. They should have no social implications or boosting effect at all.</p>\n<p>In many of the silos these are mixed - a Twitter fav used to range from an appreciation to a sarcastic meh<a href=\"https://petermolnar.net/#fn17\">17</a>. With a range of reactions available this may get simpler to differentiate, but a <code>like</code> in Facebook still counts as both a <code>vote</code> and a <code>reaction</code>.</p>\n<p>I thought a lot about reactions and I came to the conclusion that I should not have them on my site. The first problem is they will be linking into a walled garden, without context, maybe pointing at a private(ish) post, available to a limited audience. <strong>If the content is that good, bookmark it as well. If it\u2019s a reaction for the sake of being social, it\u2019s ephemeral.</strong></p>\n<h2>Conclusions</h2>\n<p>Don\u2019t let your ideas take over the things you enjoy. Some ideas can be beneficial, others are passing experiments.</p>\n<p>There\u2019s a lot of data worth collecting: scrobbles, location data, etc., but these are logs, and most of them, in my opinion, should be private. If I\u2019m getting paranoid about how much services know about me, I shouldn\u2019t publish the same information publicly either.</p>\n<p>And finally: keep things simple. I\u2019m finding myself throwing out my filter coffee machine and replacing it with a pot that has a paper filter slot - it makes an even better coffee and I have to care about one less electrical thing. The same should apply for my web presence: the simpler is usually better.</p>\n\n\n<ol><li><p><a href=\"https://stackingthebricks.com/how-blogs-broke-the-web/\">https://stackingthebricks.com/how-blogs-broke-the-web/</a><a href=\"https://petermolnar.net/#fnref1\">\u21a9</a></p></li>\n<li><p><a href=\"https://indieweb.org/\">https://indieweb.org/</a><a href=\"https://petermolnar.net/#fnref2\">\u21a9</a></p></li>\n<li><p><a href=\"https://petermolnar.net/indieweb-decentralize-web-centralizing-ourselves/\">https://petermolnar.net/indieweb-decentralize-web-centralizing-ourselves/</a><a href=\"https://petermolnar.net/#fnref3\">\u21a9</a></p></li>\n<li><p><a href=\"https://petermolnar.net/personal-website-as-archiving-vault/\">https://petermolnar.net/personal-website-as-archiving-vault/</a><a href=\"https://petermolnar.net/#fnref4\">\u21a9</a></p></li>\n<li><p><a href=\"https://indieweb.org/bookmark\">https://indieweb.org/bookmark</a><a href=\"https://petermolnar.net/#fnref5\">\u21a9</a></p></li>\n<li><p><a href=\"http://tantek.com/2015/069/t1/js-dr-javascript-required-dead\">http://tantek.com/2015/069/t1/js-dr-javascript-required-dead</a><a href=\"https://petermolnar.net/#fnref6\">\u21a9</a></p></li>\n<li><p><a href=\"http://www.archiveteam.org/index.php?title=Wget_with_WARC_output\">http://www.archiveteam.org/index.php?title=Wget_with_WARC_output</a><a href=\"https://petermolnar.net/#fnref7\">\u21a9</a></p></li>\n<li><p><a href=\"http://pinboard.in/\">http://pinboard.in/</a><a href=\"https://petermolnar.net/#fnref8\">\u21a9</a></p></li>\n<li><p><a href=\"http://getpocket.com/\">http://getpocket.com/</a><a href=\"https://petermolnar.net/#fnref9\">\u21a9</a></p></li>\n<li><p><a href=\"https://wallabag.org/en\">https://wallabag.org/en</a><a href=\"https://petermolnar.net/#fnref10\">\u21a9</a></p></li>\n<li><p><a href=\"https://en.wikipedia.org/wiki/MHTML\">https://en.wikipedia.org/wiki/MHTML</a><a href=\"https://petermolnar.net/#fnref11\">\u21a9</a></p></li>\n<li><p><a href=\"https://superuser.com/a/445988\">https://superuser.com/a/445988</a><a href=\"https://petermolnar.net/#fnref12\">\u21a9</a></p></li>\n<li><p><a href=\"https://chrome.google.com/webstore/detail/waybackmachine/gofnhkhaadkoabedkchceagnjjicaihi\">https://chrome.google.com/webstore/detail/waybackmachine/gofnhkhaadkoabedkchceagnjjicaihi</a><a href=\"https://petermolnar.net/#fnref13\">\u21a9</a></p></li>\n<li><p><a href=\"https://qz.com/878790/a-lawyer-rewrote-instagrams-terms-of-service-for-kids-now-you-can-understand-all-of-the-private-data-you-and-your-teen-are-giving-up-to-social-media/\">https://qz.com/878790/a-lawyer-rewrote-instagrams-terms-of-service-for-kids-now-you-can-understand-all-of-the-private-data-you-and-your-teen-are-giving-up-to-social-media/</a><a href=\"https://petermolnar.net/#fnref14\">\u21a9</a></p></li>\n<li><p><a href=\"https://webmention.net/draft/#sending-webmentions-for-deleted-posts\">https://webmention.net/draft/#sending-webmentions-for-deleted-posts</a><a href=\"https://petermolnar.net/#fnref15\">\u21a9</a></p></li>\n<li><p><a href=\"http://cweiske.de/tagebuch/exif-url.htm\">http://cweiske.de/tagebuch/exif-url.htm</a><a href=\"https://petermolnar.net/#fnref16\">\u21a9</a></p></li>\n<li><p><a href=\"http://time.com/4336/a-simple-guide-to-twitter-favs/\">http://time.com/4336/a-simple-guide-to-twitter-favs/</a><a href=\"https://petermolnar.net/#fnref17\">\u21a9</a></p></li>\n</ol>",
"text": "Have you ever reached the point when you started questioning why you\u2019re doing something? I have, but never before with my website.\n\nWhat is my purpose? The unfortunate, sentient robot Rick created for the sole purpose of passing the butter.\nThe precursor to petermolnar.net started existing for a very simple reason: I wanted an online home and I wanted to put \u201cinteresting\u201d things on it. It was in 1999, before chronological ordering took over the internet.1 Soon it got a blog-ish stream, then a portfolio for my photos, later tech howtos and long journal entries, but one thing was consistent for a very long time: the majority of the content was made by me.\nAfter encountering the indieweb movement2 I started developing the idea of centralising one\u2019s self. I wrote about it not once3 but twice4, but going through with importing bookmarks and favourites had an unexpected outcome: they heavily outweighed my original content.\nDo you know what happens when your own website doesn\u2019t have your own content? It starts feeling distant and unfamiliar. When you get here, you either leave the whole thing behind or reboot it somehow. I couldn\u2019t imagine not having a website, so I rebooted.\nI kept long journal entries; notes, for replies to other websites and for short entries; photos; and tech articles - the rest needs to continue it\u2019s life either archived privately or forgotten for good.\nOutsourcing bookmarks\nThe indieweb wiki entry on bookmark says5:\n\nWhy should you post bookmark posts? Good question. People seem to have reasons for doing so. (please feel free to replace this rhetorical question with actual reasoning)\n\nSince that didn\u2019t help, I stepped back one step further: why do I bookmark?\nUsually it\u2019s because I found them interesting and/or useful. What I ended up having was a date of bookmarking, a title, a URL, and some badly applied tags. In this form, bookmarks on my site were completely useless: I didn\u2019t have the content that made them interesting nor a way to search them properly.\nTo solve the first problem, the missing content, my initial idea was to leave everything in place and pull an extract of the content to have something to search in. It didn\u2019t go well. There\u2019s a plethora of js;dr6 sites these days, which don\u2019t, any more, offer a working, plain HTML output without executing JavaScript. For archival purposes, archive.org introduced an arcane file format, WARC7: it saves everything about the site, but there is no way to simply open it for view. Saving pages with crawlers including media files generated a silly amount of data on my system and soon became unsustainable.\nSoon I realised I\u2019m trying to solve a problem others worked on for years, if not decades, so I decided to look into existing bookmark managers. I tried two paid services, Pinboard8 and Pocket9 first. Pocket would be unbeatable, even though it\u2019s not self hosted, if the article extracts they make were available through their API. They are not. Unfortunately Pinboard wasn\u2019t giving me much over my existing crawler solutions.\nThe winner was Wallabag10: it\u2019s self-hosted, which is great, painful to install and set up, which is not, but it\u2019s completely self-sustaining, runs on SQLite and good enough for me.\nThere was only one problem: none of these offered archival copies of images, and some of the bookmarks I made were solely for the photos on the sites. I found a format, called MHTML11, also known as .eml, which is perfect for single-file archives of HTML pages: it inlines all images as base64 encoded data.\nHowever, no browser offers a save-as-mhtml in headless mode, so to get your archives, you\u2019ll need to revisit your bookmarks. All of them. I enabled12 save as MHTML in Chrome (Firefox doesn\u2019t know this format), installed the Wayback Machine13 extension and saved GBs of websites. I also added them into Wallabag. It\u2019s an interesting, though very long journey, but you\u2019ll rediscover a lot of things for sure.\nWhen this was done, I dropped thousands of bookmark entries from my site.\nIf I do want to share a site, I\u2019ll write a note about it, but bookmarks, without context, belong to my archives.\n(Some) microblog imports should never have happened\nI had iterations of imports, so after bookmarks it seemed reasonable to check what else may simply be noise on my site.\nBack in the days people mostly wrote much lengthier entries: journal-like diary pages, thoughts, and it was, nearly always, anonymous. It all happened under pseudonyms.\nParallel to this there were the oldschool instant messengers, like ICQ and MSN Messenger. In many cases, though you all had handles, or numbers, or usernames, you knew exactly who you were talking to. Most of these programs had a feature called status message - looking back at it they may have been precursors to microblogging, but there was a huge difference: they were ephemeral.\nWith the rise of Twitter and Facebook status message also came (forced?) real identities, and tools letting us post from anywhere, within seconds. The content that earlier landed in status messages - XY is listening to\u2026., Feels like\u2026, etc - suddenly became readable at any time, sometimes to anyone.\nI had content like this and I am, as well, guilty of posting short, meaningless, out-of-context entries. Imported burps of private life; useless shares of music pointing to long dead links; one-liner jokes, linking to bash.org; tiny replies and notes that should have been sent privately, either via email or some other mechanism.\nSome things are meant to be ephemeral, no matter how loud the librarian is screaming deep inside me. Others belong in logs, and probably not on the public internet.\nI deleted most of them and placed a HTTP 410 Gone message for their URLs.\nReposts are messy\nFor a few months I\u2019ve been silently populating a category that I didn\u2019t promote openly: favorites. At that page, I basically had a lot of reposts: images and galleries, with complete content, but with big fat URLs over them, linking to the original content.\nBy using a silo you usually give permission to the silo to use your work and there. Due to the effects of votes and likes (see later) you do, in fact, boost the visibility of the artist. Note that usually these permissions are much broader, than you imagine: a lawyer reworded the policy of Instagram to let everyone understand, that by using the service, you allow them to do more or less anything the want to with your work14.\nBut what is you take content out of a silo? The majority of images and works are not licensed in any special way, meaning you need to assume full copyright protection. Copyright prohibits publishing works without the author\u2019s explicit consensus, so when you repost something that doesn\u2019t indicate it\u2019s OK with it - Creative Commons, Public Domain, etc -, what you do is illegal.\nAlso: for me, it feels like reposts, without notifying the creator, even though the licence allows it, are somewhat unfair - which is exactly what I was doing with these. Webmentions15 would like to address this by having an option to send notifications and delete requests, but silos are not there yet to send or to receive any of these.\nThere is a very simple solution: avoid reposting anything without being sure it\u2019s licence allows you. Save it in a private, offline copy, if you really want to. Cweiske had a nice idea about adding source URLs into JPG XMP metadata 16, so you know where it\u2019s from.\nSilo reactions only make sense within the silo\nWhen I started writing this entry, I differentiated 3, not-comment reaction types in silos:\nA reaction is a social interaction, essentially a templated comment. \u201cWell done\u201d, \u201cI disagree\u201d, \u201cbuu\u201d, \u201cacknowledged\u201d, \u2764, \ud83d\udc4d, \u2605, and so on. I asked my wife what she thinks about likes, why she uses them, and I got an unexpected answer: because, unlike with regular, text comments, others will not be able react to it - so no trolling or abuse is possible.\nA vote has direct effect on ranking: think reddit up- and downvotes. Ideally it\u2019s anonymous: list of voters should not be displayed, not even for the owner of the entry.\nA bookmark is solely for one\u2019s self: save this entry because I value it and I want to be able to find it again. They should have no social implications or boosting effect at all.\nIn many of the silos these are mixed - a Twitter fav used to range from an appreciation to a sarcastic meh17. With a range of reactions available this may get simpler to differentiate, but a like in Facebook still counts as both a vote and a reaction.\nI thought a lot about reactions and I came to the conclusion that I should not have them on my site. The first problem is they will be linking into a walled garden, without context, maybe pointing at a private(ish) post, available to a limited audience. If the content is that good, bookmark it as well. If it\u2019s a reaction for the sake of being social, it\u2019s ephemeral.\nConclusions\nDon\u2019t let your ideas take over the things you enjoy. Some ideas can be beneficial, others are passing experiments.\nThere\u2019s a lot of data worth collecting: scrobbles, location data, etc., but these are logs, and most of them, in my opinion, should be private. If I\u2019m getting paranoid about how much services know about me, I shouldn\u2019t publish the same information publicly either.\nAnd finally: keep things simple. I\u2019m finding myself throwing out my filter coffee machine and replacing it with a pot that has a paper filter slot - it makes an even better coffee and I have to care about one less electrical thing. The same should apply for my web presence: the simpler is usually better.\n\n\nhttps://stackingthebricks.com/how-blogs-broke-the-web/\u21a9\nhttps://indieweb.org/\u21a9\nhttps://petermolnar.net/indieweb-decentralize-web-centralizing-ourselves/\u21a9\nhttps://petermolnar.net/personal-website-as-archiving-vault/\u21a9\nhttps://indieweb.org/bookmark\u21a9\nhttp://tantek.com/2015/069/t1/js-dr-javascript-required-dead\u21a9\nhttp://www.archiveteam.org/index.php?title=Wget_with_WARC_output\u21a9\nhttp://pinboard.in/\u21a9\nhttp://getpocket.com/\u21a9\nhttps://wallabag.org/en\u21a9\nhttps://en.wikipedia.org/wiki/MHTML\u21a9\nhttps://superuser.com/a/445988\u21a9\nhttps://chrome.google.com/webstore/detail/waybackmachine/gofnhkhaadkoabedkchceagnjjicaihi\u21a9\nhttps://qz.com/878790/a-lawyer-rewrote-instagrams-terms-of-service-for-kids-now-you-can-understand-all-of-the-private-data-you-and-your-teen-are-giving-up-to-social-media/\u21a9\nhttps://webmention.net/draft/#sending-webmentions-for-deleted-posts\u21a9\nhttp://cweiske.de/tagebuch/exif-url.htm\u21a9\nhttp://time.com/4336/a-simple-guide-to-twitter-favs/\u21a9"
},
"name": "Content, bloat, privacy, archives",
"post-type": "article",
"_id": "890320",
"_source": "268",
"_is_read": true
}
Are you an #indieweb #WordPress user? We could use your help testing the latest version of micropub and Indieauth plugins. Drop by https://chat.indieweb.org/wordpress for details or ping me here. Thanks!
{
"type": "entry",
"published": "2018-08-27T19:33:02-04:00",
"url": "https://miklb.com/blog/2018/08/27/4258/",
"syndication": [
"https://mastodon.social/@miklb/100624812184011697",
"https://twitter.com/miklb/status/1034222308175400961"
],
"content": {
"text": "Are you an #indieweb #WordPress user? We could use your help testing the latest version of micropub and Indieauth plugins. Drop by https://chat.indieweb.org/wordpress for details or ping me here. Thanks!"
},
"author": {
"type": "card",
"name": "Michael Bishop",
"url": "https://miklb.com/",
"photo": "https://aperture-proxy.p3k.io/ea0271a66c081d9e09b200106fd14e4c49d9751c/68747470733a2f2f6d696b6c622e636f6d2f7061676573706565645f7374617469632f312e4a69426e4d71796c36532e676966"
},
"post-type": "note",
"_id": "878359",
"_source": "42",
"_is_read": true
}
Ryan Barrett, who created the Micropub endpoint for WordPress, has turned the project over to the Indieweb repository as he has not been using it or actively working on it. I have been actively working on a major set of changes for it over the last two months. Ryan, despite not using it, has been generous with his time and feedback, despite the occasional WordPress or PHP frustration…and hopefully not too much from me. In his honor, I wrote this post on Indigenous for Android, published via the current release version of Micropub.
{
"type": "entry",
"published": "2018-08-26T15:36:49-04:00",
"url": "https://david.shanske.com/2018/08/26/2054/",
"content": {
"text": "Ryan Barrett, who created the Micropub endpoint for WordPress, has turned the project over to the Indieweb repository as he has not been using it or actively working on it. I have been actively working on a major set of changes for it over the last two months. Ryan, despite not using it, has been generous with his time and feedback, despite the occasional WordPress or PHP frustration\u2026and hopefully not too much from me. In his honor, I wrote this post on Indigenous for Android, published via the current release version of Micropub."
},
"author": {
"type": "card",
"name": "David Shanske",
"url": "https://david.shanske.com/",
"photo": "https://david.shanske.com/wp-content/uploads/avatar-privacy/cache/gravatar/2/c/2cb1f8afd9c8d3b646b4071c5ed887c970d81d625eeed87e447706940e2c403d-125.png"
},
"post-type": "note",
"_id": "871328",
"_source": "5",
"_is_read": true
}
People continued working on it. Everything you need using W3C standards like Webmention, Microformats2…give it a try? https://IndieWeb.org/WordPress/Plugins
I believe it uses my-destination attribute: https://indieweb.org/Micropub-extensions#Destination there’s also more info here: https://github.com/indieweb/micropub-extensions/issues/3#issuecomment-367211500
{
"type": "entry",
"published": "2018-08-25T20:30:54-04:00",
"url": "https://martymcgui.re/2018/08/25/203054/",
"category": [
"podcast",
"IndieWeb",
"this-week-indieweb-podcast"
],
"audio": [
"https://aperture-proxy.p3k.io/a0f41c90521a2686711a03c82528431fb23a8080/68747470733a2f2f6d656469612e6d617274796d636775692e72652f35382f36662f39322f31352f30336661353934396136333833326334646637663865653666333736656664396438313131333634336333336364326438653432346536302e6d7033"
],
"syndication": [
"https://huffduffer.com/schmarty/498921",
"https://twitter.com/schmarty/status/1033513244277829634",
"https://www.facebook.com/marty.mcguire.54/posts/10212719117194777"
],
"name": "This Week in the IndieWeb Audio Edition \u2022 August 18th - 24th, 2018",
"content": {
"text": "Show/Hide Transcript \n \n Barriers to diversity, a centralization of our own, and is federated overrated? It\u2019s the audio edition for This Week in the IndieWeb for August 18th - 24th, 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>Barriers to diversity, a centralization of our own, and is federated overrated? It\u2019s the audio edition for <a href=\"https://indieweb.org/this-week/2018-08-24.html\">This Week in the IndieWeb for August 18th - 24th, 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": false,
"photo": "https://aperture-proxy.p3k.io/8275f85e3a389bd0ae69f209683436fc53d8bad9/68747470733a2f2f6d617274796d636775692e72652f696d616765732f6c6f676f2e6a7067"
},
"post-type": "audio",
"_id": "866513",
"_source": "175",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": null,
"url": "https://herestomwiththeweather.com/",
"photo": null
},
"url": "https://herestomwiththeweather.com/2018/08/25/great-success-with-twentysixteen-indieweb-wordpress-theme/",
"published": "2018-08-25T18:32:54+00:00",
"content": {
"html": "<p>With <a href=\"https://boffosocko.com/2018/08/18/a-reply-to-david-shanske-regarding-implementation-of-the-diso-project/#comment-71576\">guidance from Chris Aldrich</a>, I confirmed that the <a href=\"https://github.com/dshanske/twentysixteen-indieweb\">dshanske/twentysixteen-indieweb</a> works great with webmentions on the <a href=\"https://effaustin.org/\">EFF-Austin</a> site. Thanks once again to <a href=\"https://david.shanske.com/\">David Shanske</a>.</p>",
"text": "With guidance from Chris Aldrich, I confirmed that the dshanske/twentysixteen-indieweb works great with webmentions on the EFF-Austin site. Thanks once again to David Shanske."
},
"name": "Great Success with twentysixteen-indieweb Wordpress Theme",
"post-type": "article",
"_id": "866189",
"_source": "246",
"_is_read": true
}
Just came across this 5 year old post from Pippin about using the_title_attribute instead of the_title and wondering why twentysixteen is using the_title. This very issue has tripped up the IndieWeb community trying to add mf2. https://pippinsplugins.com/use-the_title-and-the_title_attribute-correctly/
{
"type": "entry",
"syndication": [
"https://mastodon.social/@miklb/100602197221385032",
"https://twitter.com/miklb/status/1032774949272997888"
],
"content": {
"text": "Just came across this 5 year old post from Pippin about using the_title_attribute instead of the_title and wondering why twentysixteen is using the_title. This very issue has tripped up the IndieWeb community trying to add mf2. https://pippinsplugins.com/use-the_title-and-the_title_attribute-correctly/",
"html": "Just came across this <strong>5 year old post</strong> from Pippin about using <code>the_title_attribute</code> instead of <code>the_title</code> and wondering why twentysixteen is using <code>the_title</code>. This very issue has tripped up the IndieWeb community trying to add mf2. https://pippinsplugins.com/use-the_title-and-the_title_attribute-correctly/"
},
"author": {
"type": "card",
"name": "Michael Bishop",
"url": "https://miklb.com/",
"photo": "https://aperture-proxy.p3k.io/fa0674caee1c8265a0b0a240a0ec9c5d99ee50a2/68747470733a2f2f7365637572652e67726176617461722e636f6d2f6176617461722f63333961316436646637333532353934356366653530653939646164613733303f733d353026643d64656661756c7426723d72"
},
"post-type": "note",
"_id": "854621",
"_source": "42",
"_is_read": true
}
But as it stands, with only two minor edits to the mf2 plugin & suite of Indieweb WP plugins I already had installed, I’m using default twentysixteen WordPress theme. I’m syndicating to micro.blog, Twitter (via brid.gy) and Mastodon (via auto-poster plugin). I’m also receiving backfeed from all three. I can also comment and create GitHub issues as post on my site, again, using existing plugins and brid.gy. The work this community has done in the last 2 years is amazing.
{
"type": "entry",
"syndication": [
"https://mastodon.social/@miklb/100594695503428942",
"https://twitter.com/miklb/status/1032294842385223681"
],
"in-reply-to": [
"https://miklb.com/blog/2018/08/22/4188/"
],
"content": {
"text": "But as it stands, with only two minor edits to the mf2 plugin & suite of Indieweb WP plugins I already had installed, I\u2019m using default twentysixteen WordPress theme. I\u2019m syndicating to micro.blog, Twitter (via brid.gy) and Mastodon (via auto-poster plugin). I\u2019m also receiving backfeed from all three. I can also comment and create GitHub issues as post on my site, again, using existing plugins and brid.gy. The work this community has done in the last 2 years is amazing.",
"html": "But as it stands, with only two minor edits to the mf2 plugin & suite of Indieweb WP plugins I already had installed, I\u2019m using default twentysixteen WordPress theme. I\u2019m syndicating to micro.blog, Twitter (via brid.gy) and Mastodon (via auto-poster plugin). I\u2019m also receiving backfeed from all three. I can also comment and create GitHub issues as post on my site, again, using existing plugins and brid.gy. The work this community has done in the last 2 years is amazing."
},
"author": {
"type": "card",
"name": "Michael Bishop",
"url": "https://miklb.com/",
"photo": "https://aperture-proxy.p3k.io/fa0674caee1c8265a0b0a240a0ec9c5d99ee50a2/68747470733a2f2f7365637572652e67726176617461722e636f6d2f6176617461722f63333961316436646637333532353934356366653530653939646164613733303f733d353026643d64656661756c7426723d72"
},
"post-type": "reply",
"refs": {
"https://miklb.com/blog/2018/08/22/4188/": {
"type": "entry",
"url": "https://miklb.com/blog/2018/08/22/4188/",
"name": "Miklb Mindless Ramblings",
"author": {
"type": "card",
"name": "Michael Bishop",
"url": "https://miklb.com/",
"photo": "https://secure.gravatar.com/avatar/c39a1d6df73525945cfe50e99dada730?s=50&d=default&r=r"
},
"post-type": "article"
}
},
"_id": "854629",
"_source": "42",
"_is_read": true
}
So part way through my testing of the State of WordPress in IndieWeb and it really is so far less “broken” than I think a lot of us believed in regards to using the core 2016 theme. Still more testing to do.
{
"type": "entry",
"syndication": [
"https://mastodon.social/@miklb/100594594447576363",
"https://twitter.com/miklb/status/1032288371467591681"
],
"content": {
"text": "So part way through my testing of the State of WordPress in IndieWeb and it really is so far less \u201cbroken\u201d than I think a lot of us believed in regards to using the core 2016 theme. Still more testing to do."
},
"author": {
"type": "card",
"name": "Michael Bishop",
"url": "https://miklb.com/",
"photo": "https://aperture-proxy.p3k.io/fa0674caee1c8265a0b0a240a0ec9c5d99ee50a2/68747470733a2f2f7365637572652e67726176617461722e636f6d2f6176617461722f63333961316436646637333532353934356366653530653939646164613733303f733d353026643d64656661756c7426723d72"
},
"post-type": "note",
"_id": "854630",
"_source": "42",
"_is_read": true
}
A little appropos seeing this quote shared by Matt today after I wrote this last night
“WordPress was orginally about making it easier to put words and pictures on the Internet. Gutenberg and 5.0 is about ushering in a new interface to do that. We should at least fight to make the full IndieWeb experience a little easier to be a part of that change.”
{
"type": "entry",
"bookmark-of": [
"https://ma.tt/2018/08/light-heretofore-unkown/"
],
"content": {
"text": "A little appropos seeing this quote shared by Matt today after I wrote this last night\n\u201cWordPress was orginally about making it easier to put words and pictures on the Internet. Gutenberg and 5.0 is about ushering in a new interface to do that. We should at least fight to make the full IndieWeb experience a little easier to be a part of that change.\u201d",
"html": "A little appropos seeing this quote shared by Matt today after I wrote this last night\n<p>\u201cWordPress was orginally about making it easier to put words and pictures on the Internet. Gutenberg and 5.0 is about ushering in a new interface to do that. We should at least fight to make the full IndieWeb experience a little easier to be a part of that change.\u201d</p>"
},
"author": {
"type": "card",
"name": "Michael Bishop",
"url": "https://miklb.com/",
"photo": "https://aperture-proxy.p3k.io/fa0674caee1c8265a0b0a240a0ec9c5d99ee50a2/68747470733a2f2f7365637572652e67726176617461722e636f6d2f6176617461722f63333961316436646637333532353934356366653530653939646164613733303f733d353026643d64656661756c7426723d72"
},
"post-type": "bookmark",
"refs": {
"https://ma.tt/2018/08/light-heretofore-unkown/": {
"type": "entry",
"url": "https://ma.tt/2018/08/light-heretofore-unkown/",
"name": "Light Heretofore\u00a0Unknown",
"author": {
"type": "card",
"name": "JOHANNES GUTENBERG",
"url": false,
"photo": null
},
"post-type": "article"
}
},
"_id": "854640",
"_source": "42",
"_is_read": true
}
{
"type": "entry",
"syndication": [
"https://twitter.com/miklb/status/1031359000162516999"
],
"name": "Live Testing the State of Affairs in WordPress & the IndieWeb",
"content": {
"text": "Suffice to say I\u2019ve said a lot about WordPress and the IndieWeb. Here and in #indieweb-wordpress in IRC. But the gist is, I don\u2019t know what issues there are summer of 2018 with a core WordPress theme and the suite of IndieWeb plugins. No one seems to be able to point to anything specific.\nThere are efforts under way to bypass the mf2 in the markup and pass a mf2 feed for parsers to use. It is an honest attempt to find a solution right now. But the elegance of semantic classes in proper HTML5 markup is what drew me to the technology in the first place. I would hate to ditch that approach without attempting to find a solution that includes the underlying markup in WordPress themes.\nMy base understanding is that there are microformats 1 in core. Over time folks have used those semantic classes as styling hooks. A pull request was sent and was closed as wontfix due to concern of \u201cbreaking\u201d legacy themes that used the mf1 semantic class as styling hook.\nThat was 2 years ago. I don\u2019t know if anything has changed since then. A lot has changed in the Indieweb landscape including improvements to backward compatibility in the mf2 parses.\nSo, if you consume this feed in any kind of reader and see weird output, please send a webmention to this post so I can collect them in one place and document. Feel free to send a webmention without an issue just so I can assess replies as well.\nAlso, if you\u2019ve done this excercise in the last few months, please share your experience.",
"html": "Suffice to say I\u2019ve said a lot about WordPress and the IndieWeb. Here and in #indieweb-wordpress in IRC. But the gist is, I don\u2019t know what issues there are summer of 2018 with a core WordPress theme and the suite of IndieWeb plugins. No one seems to be able to point to anything specific.\n<p>There are efforts under way to bypass the mf2 in the markup and pass a mf2 feed for parsers to use. It is an honest attempt to find a solution right now. But the elegance of semantic classes in proper HTML5 markup is what drew me to the technology in the first place. I would hate to ditch that approach without attempting to find a solution that includes the underlying markup in WordPress themes.</p>\n<p>My base understanding is that there are microformats 1 in core. Over time folks have used those semantic classes as styling hooks. A <a href=\"https://core.trac.wordpress.org/ticket/30783\">pull request was sent</a> and was closed as <code>wontfix</code> due to concern of \u201cbreaking\u201d legacy themes that used the mf1 semantic class as styling hook.</p>\n<p>That was 2 years ago. I don\u2019t know if anything has changed since then. A lot has changed in the Indieweb landscape including improvements to backward compatibility in the mf2 parses.</p>\n<p>So, if you consume this feed in any kind of reader and see weird output, please send a webmention to this post so I can collect them in one place and document. Feel free to send a webmention without an issue just so I can assess replies as well.</p>\n<p>Also, if you\u2019ve done this excercise in the last few months, <strong>please</strong> share your experience.</p>"
},
"author": {
"type": "card",
"name": "Michael Bishop",
"url": "https://miklb.com/",
"photo": "https://aperture-proxy.p3k.io/fa0674caee1c8265a0b0a240a0ec9c5d99ee50a2/68747470733a2f2f7365637572652e67726176617461722e636f6d2f6176617461722f63333961316436646637333532353934356366653530653939646164613733303f733d353026643d64656661756c7426723d72"
},
"post-type": "article",
"_id": "854645",
"_source": "42",
"_is_read": true
}
{
"type": "entry",
"syndication": [
"https://twitter.com/miklb/status/1031342679706284032"
],
"content": {
"text": "I need to keep a list of draft notes to use for testing micropub so I\u2019m not just saying \"testing\""
},
"author": {
"type": "card",
"name": "Michael Bishop",
"url": "https://miklb.com/",
"photo": "https://aperture-proxy.p3k.io/fa0674caee1c8265a0b0a240a0ec9c5d99ee50a2/68747470733a2f2f7365637572652e67726176617461722e636f6d2f6176617461722f63333961316436646637333532353934356366653530653939646164613733303f733d353026643d64656661756c7426723d72"
},
"post-type": "note",
"_id": "854646",
"_source": "42",
"_is_read": true
}
Just came across this 5 year old post from Pippin about using the_title_attribute instead of the_title and wondering why twentysixteen is using the_title. This very issue has tripped up the IndieWeb community trying to add mf2. https://pippinsplugins.com/use-the_title-and-the_title_attribute-correctly/
{
"type": "entry",
"published": "2018-08-23T19:41:46-04:00",
"url": "https://miklb.com/blog/2018/08/23/4201/",
"syndication": [
"https://mastodon.social/@miklb/100602197221385032",
"https://twitter.com/miklb/status/1032774949272997888"
],
"content": {
"text": "Just came across this 5 year old post from Pippin about using the_title_attribute instead of the_title and wondering why twentysixteen is using the_title. This very issue has tripped up the IndieWeb community trying to add mf2. https://pippinsplugins.com/use-the_title-and-the_title_attribute-correctly/",
"html": "Just came across this <strong>5 year old post</strong> from Pippin about using <code>the_title_attribute</code> instead of <code>the_title</code> and wondering why twentysixteen is using <code>the_title</code>. This very issue has tripped up the IndieWeb community trying to add mf2. https://pippinsplugins.com/use-the_title-and-the_title_attribute-correctly/"
},
"author": {
"type": "card",
"name": "Michael Bishop",
"url": "https://miklb.com/",
"photo": "https://aperture-proxy.p3k.io/fa0674caee1c8265a0b0a240a0ec9c5d99ee50a2/68747470733a2f2f7365637572652e67726176617461722e636f6d2f6176617461722f63333961316436646637333532353934356366653530653939646164613733303f733d353026643d64656661756c7426723d72"
},
"post-type": "note",
"_id": "852946",
"_source": "42",
"_is_read": true
}
If you use Micro.blog completely from the native apps, everything works smoothly. If you communicate via the IndieWeb through webmentions, everything (mostly) works smoothly. But there is a big hiccup that is still being worked out when you communicate via Webmentions to Micro.blog. The current functionality is described here, however it’s not exhaustive and it doesn’t work 100% of the time.
{
"type": "entry",
"published": "2018-08-23T12:07:13-04:00",
"summary": "If you use Micro.blog completely from the native apps, everything works smoothly. If you communicate via the IndieWeb through webmentions, everything (mostly) works smoothly. But there is a big hiccup that is still being worked out when you communicate via Webmentions to Micro.blog. The current functionality is described here, however it\u2019s not exhaustive and it doesn\u2019t work 100% of the time.",
"url": "https://eddiehinkle.com/2018/08/23/11/article/",
"name": "How I send webmentions to Micro.blog",
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"post-type": "article",
"_id": "850563",
"_source": "226",
"_is_read": true
}
Yes, I use Indigenous on iOS which is what I use 90% of the time. But the benefit of the setup is if I’m on my computer I can use @aaronpk’s Monocle web App. (Although I’m looking forward to UIKit on the Mac so Indigenous can be everywhere). I send a webmention ping to https://micro.blog/webmention for every post I write, that way if the post I’m replying to is in the Micro.blog system, my reply appears here.
{
"type": "entry",
"published": "2018-08-23T10:12:59-04:00",
"summary": "Yes, I use Indigenous on iOS which is what I use 90% of the time. But the benefit of the setup is if I\u2019m on my computer I can use @aaronpk\u2019s Monocle web App. (Although I\u2019m looking forward to UIKit on the Mac so Indigenous can be everywhere). I send a webmention ping to https://micro.blog/webmention for every post I write, that way if the post I\u2019m replying to is in the Micro.blog system, my reply appears here.",
"url": "https://eddiehinkle.com/2018/08/23/5/reply/",
"in-reply-to": [
"https://micro.blog/amit/822193"
],
"content": {
"text": "Yes, I use Indigenous on iOS which is what I use 90% of the time. But the benefit of the setup is if I\u2019m on my computer I can use @aaronpk\u2019s Monocle web App. (Although I\u2019m looking forward to UIKit on the Mac so Indigenous can be everywhere). I send a webmention ping to https://micro.blog/webmention for every post I write, that way if the post I\u2019m replying to is in the Micro.blog system, my reply appears here.",
"html": "<p>Yes, I use Indigenous on iOS which is what I use 90% of the time. But the benefit of the setup is if I\u2019m on my computer I can use <a href=\"https://micro.blog/aaronpk\">@aaronpk</a>\u2019s Monocle web App. (Although I\u2019m looking forward to UIKit on the Mac so Indigenous can be everywhere). I send a webmention ping to https://micro.blog/webmention for every post I write, that way if the post I\u2019m replying to is in the Micro.blog system, my reply appears here.</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"post-type": "reply",
"refs": {
"https://micro.blog/amit/822193": {
"type": "entry",
"url": "https://micro.blog/amit/822193",
"name": "https://micro.blog/amit/822193",
"post-type": "article"
}
},
"_id": "850568",
"_source": "226",
"_is_read": true
}
