Like Jonathan, I use Overcast to listen to podcasts on my phone, and I was surprised and delighted to learn that Overcast has an "All data" export option on the accounts page that includes per-episode details such as whether you listened to an ep, and when you last interacted with it!
My process follows three steps: download the overcast.opml full export file, run a script to generate the Hugo posts, and run a script to grab extra podcast metadata like cover art.
You can find my scripts in this gist if you're interested in learning more, but they may not be that useful for anyone without my exact Hugo config.
You may notice in the scripts that I have a "block list" of podcast URLs I can add. That's because I wanted my listen posts to helpfully link to and embed audio whenever possible. However, some of the feeds I subscribe to contain private or for-pay content - particularly a couple of podcasts I support on Patreon. I do want to track my listening habits for these podcasts, so I will likely start handling them differently by leaving out the embedded audio and linking directly to Patreon pages where possible.
Running the script, I was able to happily show everything I listened to as just another type of post on my site. However, it turns out I had (and keep making) a lot of listen posts. Visually they were drowning out all my other activity on my site.
So I have sequestered them on a new Listens page where you can only follow my podcast consumption history, keeping it out of my main feeds.
Similarly, I have been interested in having a nice Instagram-like page that shows off my photos in a grid. So I made a Photos page to show off those posts.
Both of these pages have microformats2 feed information embedded, so if you have an Indie reader, you might be interested in following just those pages!
{
"type": "entry",
"published": "2019-02-19T17:53:18-0500",
"url": "https://martymcgui.re/2019/02/19/site-updates-listens-and-photos-pages/",
"category": [
"listen",
"read",
"IndieWeb",
"site-update"
],
"name": "Site Updates: /listens and /photos pages",
"content": {
"text": "Inspired by Jonathan LaCour's January post about tracking his podcast listening habits, I recently decided to bring in my own listening history into my website.\nLike Jonathan, I use Overcast to listen to podcasts on my phone, and I was surprised and delighted to learn that Overcast has an \"All data\" export option on the accounts page that includes per-episode details such as whether you listened to an ep, and when you last interacted with it!\nI took a look at Jonathan's script to automatically log in and import his Overcast data and figured I could make something a little more minimal that would work with my Hugo site.\nMy process follows three steps: download the overcast.opml full export file, run a script to generate the Hugo posts, and run a script to grab extra podcast metadata like cover art.\nYou can find my scripts in this gist if you're interested in learning more, but they may not be that useful for anyone without my exact Hugo config.\n\n You may notice in the scripts that I have a \"block list\" of podcast URLs I can add. That's because I wanted my listen posts to helpfully link to and embed audio whenever possible. However, some of the feeds I subscribe to contain private or for-pay content - particularly a couple of podcasts I support on Patreon. I do want to track my listening habits for these podcasts, so I will likely start handling them differently by leaving out the embedded audio and linking directly to Patreon pages where possible.\n \n\nRunning the script, I was able to happily show everything I listened to as just another type of post on my site. However, it turns out I had (and keep making) a lot of listen posts. Visually they were drowning out all my other activity on my site.\nSo I have sequestered them on a new Listens page where you can only follow my podcast consumption history, keeping it out of my main feeds.\nSimilarly, I have been interested in having a nice Instagram-like page that shows off my photos in a grid. So I made a Photos page to show off those posts.\nBoth of these pages have microformats2 feed information embedded, so if you have an Indie reader, you might be interested in following just those pages!",
"html": "<p>Inspired by <a href=\"https://cleverdevil.io/2019/tracking-my-movie-tv-and-podcast-activity\">Jonathan LaCour's January post about tracking his podcast listening habits</a>, I recently decided to bring in my own listening history into my website.</p>\n<p>Like Jonathan, I use <a href=\"https://overcast.fm/\">Overcast</a> to listen to podcasts on my phone, and I was surprised and delighted to learn that Overcast has an \"All data\" <a href=\"https://overcast.fm/account\">export option on the accounts page</a> that includes per-episode details such as whether you listened to an ep, and when you last interacted with it!</p>\n<p>I took a look at Jonathan's <a href=\"https://gist.github.com/cleverdevil/a8215850420493c1ee06364161e281c0\">script to automatically log in and import his Overcast data </a>and figured I could make something a little more minimal that would work with my Hugo site.</p>\n<p>My process follows three steps: download the overcast.opml full export file, run a script to generate the Hugo posts, and run a script to grab extra podcast metadata like cover art.</p>\n<p>You can find my <a href=\"https://gist.github.com/martymcguire/57bc398d74557904d1eea5ebc01c8c3e\">scripts in this gist</a> if you're interested in learning more, but they may not be that useful for anyone without my exact Hugo config.</p>\n<p>\n You may notice in the scripts that I have a \"block list\" of podcast URLs I can add. That's because I wanted my listen posts to helpfully link to and embed audio whenever possible. However, some of the feeds I subscribe to contain private or for-pay content - particularly a couple of podcasts I support on Patreon. I do want to track my listening habits for these podcasts, so I will likely start handling them differently by leaving out the embedded audio and linking directly to Patreon pages where possible.\n <br /></p>\n<p>Running the script, I was able to happily show everything I listened to as just another type of post on my site. However, it turns out I had (and keep making) a <i>lot of listen posts</i>. Visually they were drowning out all my other activity on my site.</p>\n<p>So I have sequestered them on a new <a href=\"https://martymcgui.re/listens/\">Listens page</a> where you can only follow my podcast consumption history, keeping it out of my main feeds.</p>\n<p>Similarly, I have been interested in having a nice Instagram-like page that shows off my photos in a grid. So I made a <a href=\"https://martymcgui.re/photos/\">Photos page</a> to show off those posts.</p>\n<p>Both of these pages have <a href=\"http://microformats.org/wiki/h-feed\">microformats2 feed</a> information embedded, so if you have an <a href=\"https://indieweb.org/reader\">Indie reader</a>, you might be interested in following just those pages!</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://aperture-proxy.p3k.io/8275f85e3a389bd0ae69f209683436fc53d8bad9/68747470733a2f2f6d617274796d636775692e72652f696d616765732f6c6f676f2e6a7067"
},
"post-type": "article",
"_id": "2239887",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Manton Reece",
"url": "https://www.manton.org/",
"photo": "https://aperture-proxy.p3k.io/907926e361383204bd1bc913c143c23e70ae69bb/68747470733a2f2f6d6963726f2e626c6f672f6d616e746f6e2f6176617461722e6a7067"
},
"url": "https://www.manton.org/2019/02/19/indiewebcamp-austin-is.html",
"content": {
"html": "<p>IndieWebCamp Austin is this weekend! You can still <a href=\"https://2019.indieweb.org/austin\">register here</a>.</p>",
"text": "IndieWebCamp Austin is this weekend! You can still register here."
},
"published": "2019-02-19T15:25:26-06:00",
"post-type": "note",
"_id": "2238184",
"_is_read": true
}
{
"type": "event",
"name": "Homebrew Website Club SF!",
"summary": "17:30: Optional writing hour and quiet socializing\n18:30: IndieWeb demos and hack night!\n\nHomebrew Website Club retro 1980s-style logo\nTopics for this week: IndieWebCamp Austin is this weekend! Year-end hack projects 2018 IndieWeb Challenge completed! Demos of personal website breakthroughs Create or update your personal web site!\nJoin a community with like-minded interests. Bring friends that want a personal site, or are interested in a healthy, independent web!\nAny questions? Ask in #indieweb Slack or IRC\nMore information: IndieWeb Wiki Event Page\nRSVP: post an indie RSVP on your own site!",
"published": "2019-02-19 09:23-0800",
"start": "2019-02-20 17:30-0800",
"end": "2019-02-20 19:30-0800",
"url": "http://tantek.com/2019/051/e1/homebrew-website-club-sf",
"location": [
"https://wiki.mozilla.org/SF"
],
"content": {
"text": "When: 2019-02-20 17:30\u202619:30\nWhere: Mozilla San Francisco\n\nHost: Tantek \u00c7elik\n\n\n\n17:30: Optional writing hour and quiet socializing\n\n18:30: IndieWeb demos and hack night!\n\n\nTopics for this week:\n\nIndieWebCamp Austin is this weekend!\nYear-end hack projects\n\n2018 IndieWeb Challenge completed!\nDemos of personal website breakthroughs\nCreate or update your personal web site!\n\nJoin a community with like-minded interests. Bring friends that want a personal site, or are interested in a healthy, independent web!\n\n\nAny questions? Ask in \n#indieweb Slack or IRC\n\n\nMore information: \nIndieWeb Wiki Event Page\n\n\nRSVP: post an indie RSVP on your own site!",
"html": "<p>\nWhen: <time class=\"dt-start\">2019-02-20 17:30</time>\u2026<time class=\"dt-end\">19:30</time><span>\nWhere: <a class=\"u-location h-card\" href=\"https://wiki.mozilla.org/SF\">Mozilla San Francisco</a>\n</span>\nHost: <a class=\"u-organizer h-card\" href=\"http://tantek.com/\">Tantek \u00c7elik</a>\n</p>\n\n<p>\n17:30: Optional writing hour and quiet socializing<br />\n18:30: IndieWeb demos and hack night!<br /></p>\n<p><img class=\"u-featured\" style=\"height:300px;\" src=\"https://aperture-media.p3k.io/indieweb.org/c24f7b1e711955ef818bde12e2a3e79708ecc9b106d95b460a9fefe93b0be723.jpg\" alt=\"Homebrew Website Club retro 1980s-style logo\" /></p>\n<p>Topics for this week:</p>\n<ul><li>\n<a href=\"https://indieweb.org/2019/Austin\">IndieWebCamp Austin</a> is this weekend!</li>\n<li><a href=\"https://indieweb.org/2019-01-01-commitments\">Year-end hack projects</a></li>\n<li>\n<a href=\"https://indieweb.org/2018-12-indieweb-challenge\">2018 IndieWeb Challenge</a> completed!</li>\n<li>Demos of personal website breakthroughs</li>\n<li>Create or update your personal web site!</li>\n</ul><p>\nJoin a community with like-minded interests. Bring friends that want a personal site, or are interested in a healthy, independent web!\n</p>\n<p>\nAny questions? Ask in \n<a href=\"https://indieweb.org/discuss\">#indieweb Slack or IRC</a>\n</p>\n<p>\nMore information: \n<a class=\"u-url\" href=\"https://indieweb.org/events/2019-02-20-homebrew-website-club\">IndieWeb Wiki Event Page</a>\n</p>\n<p>\nRSVP: post an <a href=\"https://indieweb.org/rsvp\">indie RSVP</a> on your own site!\n</p>"
},
"post-type": "event",
"refs": {
"https://wiki.mozilla.org/SF": {
"type": "card",
"name": "Mozilla San Francisco",
"url": "https://wiki.mozilla.org/SF",
"photo": null
}
},
"_id": "2235337",
"_is_read": true
}
This is the type of pages I visited before inline images were possible. The cool bit is it allows you to see your own site as it would have looked 30 years ago. (Go to Document, then Open from full document reference and fill in your url) My site looks pretty well, which is not surprising as it is very text centered anyway.
Hypertexting this blog like it’s 1989
Maybe somewhat less obvious, but of key importance to me in the context of my own information strategies and workflows, as well as in the dynamics of the current IndieWeb efforts is that this is not just a way to view a site, but you can also edit the page directly in the same window. (See the sentence in all capitals in the image below.)
Read and write, the original premise of the WWW
Hypertext wasn’t meant as viewing-only, but as an interactive way of linking together documents you were actively working on. Closest come current wiki’s. But for instance I also use Tinderbox, a hypertext mindmapping, outlining and writing tool for Mac, that incorporates this principle of linked documents and other elements that can be changed as you go along. This seamless flow between reading and writing is something I feel we need very much for effective information strategies. It is present in the Mother of all Demos, it is present in the current thinking of Aaron Parecki about his Social Reader, and it is a key element in this 30 year old browser.
{
"type": "entry",
"author": {
"name": "Ton Zijlstra",
"url": "https://www.zylstra.org/blog",
"photo": null
},
"url": "https://www.zylstra.org/blog/2019/02/the-web-through-a-30-year-old-lens/",
"published": "2019-02-18T16:19:31+00:00",
"content": {
"html": "<p>A team of people, including <a href=\"https://adactio.com/journal/14821\">Jeremy Keith</a> whose writings are part of my daily RSS infodiet, have been doing some awesome web archeology. Over the course of 5 days at CERN, they <a href=\"https://worldwideweb.cern.ch/\">recreated the browser experience as it was 30 years ago</a> with the (fully text based) <a href=\"https://worldwideweb.cern.ch/browser/#https://worldwideweb.cern.ch/browser/default.html\">WorldWideWeb application</a> for the <a href=\"https://en.wikipedia.org/wiki/NeXT\">NeXT computer</a></p>\n<p><img src=\"https://aperture-proxy.p3k.io/c6a97e50b496d0798e8cb73fc35813c2bfa2e016/68747470733a2f2f7777772e7a796c737472612e6f72672f77702f77702d636f6e74656e742f75706c6f6164732f323031392f30322f6879706572726f6f742d31303234783736352e706e67\" alt=\"\" /></p>\n<em>Hypertext\u2019s root, the CERN page in 1989</em>\n<p>This is the type of pages I visited before inline images were possible.<br />The cool bit is it allows you to see your own site as it would have looked 30 years ago. (Go to Document, then Open from full document reference and fill in your url) My site looks pretty well, which is not surprising as it is very text centered anyway. </p>\n<p><img src=\"https://aperture-proxy.p3k.io/476427a58b776e162f6d63db16f6a9857e4093c4/68747470733a2f2f7777772e7a796c737472612e6f72672f77702f77702d636f6e74656e742f75706c6f6164732f323031392f30322f6f776e736974652d31303234783530312e706e67\" alt=\"\" /></p>\n<em>Hypertexting this blog like it\u2019s 1989</em>\n<p>Maybe somewhat less obvious, but of key importance to me in the context of my own information strategies and workflows, as well as in the dynamics of the current IndieWeb efforts is that this is not just a way to view a site, but you can also edit the page directly in the same window. (See the sentence in all capitals in the image below.)</p>\n<p><img src=\"https://aperture-proxy.p3k.io/1f389c76512bb43205c106125bcbc2b74f8be9d0/68747470733a2f2f7777772e7a796c737472612e6f72672f77702f77702d636f6e74656e742f75706c6f6164732f323031392f30322f6f776e736974656564697465642d31303234783935382e706e67\" alt=\"\" /></p>\n<em>Read and write, the original premise of the WWW</em>\n<p>Hypertext wasn\u2019t meant as viewing-only, but as an interactive way of linking together documents you were actively working on. Closest come current wiki\u2019s. But for instance I also use Tinderbox, a hypertext mindmapping, outlining and writing tool for Mac, that incorporates this principle of linked documents and other elements that can be changed as you go along. This seamless flow between reading and writing is something I feel we need very much for effective information strategies. It is present in the <a href=\"https://www.zylstra.org/blog/2018/12/the-doug-engelbart-demo-at-50/\">Mother of all Demos</a>, it is present in the current thinking of Aaron Parecki about his <a href=\"https://www.zylstra.org/blog/2018/11/state-of-the-social-reader/\">Social Reader</a>, and it is a key element in this 30 year old browser.</p>",
"text": "A team of people, including Jeremy Keith whose writings are part of my daily RSS infodiet, have been doing some awesome web archeology. Over the course of 5 days at CERN, they recreated the browser experience as it was 30 years ago with the (fully text based) WorldWideWeb application for the NeXT computer\n\nHypertext\u2019s root, the CERN page in 1989\nThis is the type of pages I visited before inline images were possible.\nThe cool bit is it allows you to see your own site as it would have looked 30 years ago. (Go to Document, then Open from full document reference and fill in your url) My site looks pretty well, which is not surprising as it is very text centered anyway. \n\nHypertexting this blog like it\u2019s 1989\nMaybe somewhat less obvious, but of key importance to me in the context of my own information strategies and workflows, as well as in the dynamics of the current IndieWeb efforts is that this is not just a way to view a site, but you can also edit the page directly in the same window. (See the sentence in all capitals in the image below.)\n\nRead and write, the original premise of the WWW\nHypertext wasn\u2019t meant as viewing-only, but as an interactive way of linking together documents you were actively working on. Closest come current wiki\u2019s. But for instance I also use Tinderbox, a hypertext mindmapping, outlining and writing tool for Mac, that incorporates this principle of linked documents and other elements that can be changed as you go along. This seamless flow between reading and writing is something I feel we need very much for effective information strategies. It is present in the Mother of all Demos, it is present in the current thinking of Aaron Parecki about his Social Reader, and it is a key element in this 30 year old browser."
},
"name": "The Web Through a 30 Year Old Lens",
"post-type": "article",
"_id": "2221880",
"_is_read": true
}
{
"type": "entry",
"published": "2019-02-18T08:18:52-08:00",
"url": "https://aaronparecki.com/2019/02/18/10/",
"category": [
"IndieWebCamp",
"travel",
"indiewebcamp"
],
"content": {
"text": "Once again, my backpack is heavier than my roller bag. This is what happens when I carry livestreaming gear to #IndieWebCamp Austin. #travel",
"html": "Once again, my backpack is heavier than my roller bag. This is what happens when I carry livestreaming gear to <a href=\"https://aaronparecki.com/tag/indiewebcamp\">#<span class=\"p-category\">IndieWebCamp</span></a> Austin. <a href=\"https://aaronparecki.com/tag/travel\">#<span class=\"p-category\">travel</span></a>"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/2b8e1668dcd9cfa6a170b3724df740695f73a15c2a825962fd0a0967ec11ecdc.jpg"
},
"post-type": "note",
"_id": "2221565",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Ton Zijlstra",
"url": "https://www.zylstra.org/blog",
"photo": null
},
"url": "https://www.zylstra.org/blog/2019/02/6005/",
"published": "2019-02-18T11:23:45+00:00",
"content": {
"html": "<p>Wat is een #indiewebcamp ? <a href=\"https://diggingthedigital.com/wat-is-indiewebcamp/\">Frank Meeuwsen, legt onze verwachtingen voor #indieweb camp Utrecht (#iwcutrecht) uit</a>. Ben jij er bij op 18 en 19 mei? https://diggingthedigital.com/wat-is-indiewebcamp/</p>",
"text": "Wat is een #indiewebcamp ? Frank Meeuwsen, legt onze verwachtingen voor #indieweb camp Utrecht (#iwcutrecht) uit. Ben jij er bij op 18 en 19 mei? https://diggingthedigital.com/wat-is-indiewebcamp/"
},
"post-type": "note",
"_id": "2219390",
"_is_read": true
}
Ok I totally stole the title from this article, which was really good and help me fix my problems so I wanted to link to it.
I recently upgraded all my servers from Jessie to Stretch, which was long overdue. The catalyst being that certbot from Let's Encrypt started complaining about the security I was using to fetch new certificates. (It complained in a very nice way and helped fix the problem, I should add.)
Anyway the upgrades went fine, Debian is very good at that. The problem was that part of the upgrade was switching from MySQL 5 to MariaDB, and all my tables were using an old character set and collation type. This showed up as emoji not rendering properly in my reader. Easy fix: switch the reader items table to the utf8mb4 character set and collation type to utf8mb4_unicode_ci. Problem solved.
This is where the fun really started though, and where my desire to understand the inner workings of databases started fading... My reader became so slow at loading items that it was unusable. The rest of the site worked fine, so I isolated the problem down to one database query. Due to the way I now have channels set up, this was a particularly complicated query running on the largest table in my database, reader_items which was 400k rows and growing. I delved deeper into the murky world of database performance, learning about sargable queries and how to keep your indexes fast.
Making sure all the tables joined in the same query have a matching collation type seemed to do the trick. My query which had blown out to over a minute was now running in a couple of seconds. A good reminder to look after your indexes! Since I was well and truly into database tuning now though, I decided I could get more performance improvements out of my reader.
The problem with adding new feed items to the same table is that you generally only want to read the new stuff. It's great to have fast indexes, but most of the time I really just need smaller tables. To do that my reader needed to be able to look up items in an arbitrary number of tables, but optimised to find new items in the first table it reads from. It can now do that, and the data partitioning process is automated to keep the items tables small. It can also handle reading across tables to return the correct number of items requested.
The problematic query now returns in less than a second for the optimised case. (I would measure it but it's not a noticeable part of using the reader any more.) My plan to fix the performance issues before making this change was to increase the specs of the server it's running on, which are pretty modest for all the work it's doing. I do however like the idea of improving the efficiency of code rather than throwing more hardware at a poorly running solution.
{
"type": "entry",
"published": "2019-02-18T13:35:46+10:00",
"url": "https://unicyclic.com/mal/2019-02-18-The_things_we_do_to_read__emoji",
"category": [
"indieweb"
],
"name": "The things we do to read \ud83d\udca9 emoji",
"content": {
"text": "Ok I totally stole the title from this article, which was really good and help me fix my problems so I wanted to link to it.\n\n\nI recently upgraded all my servers from Jessie to Stretch, which was long overdue. The catalyst being that certbot from Let's Encrypt started complaining about the security I was using to fetch new certificates. (It complained in a very nice way and helped fix the problem, I should add.)\n\n\nAnyway the upgrades went fine, Debian is very good at that. The problem was that part of the upgrade was switching from MySQL 5 to MariaDB, and all my tables were using an old character set and collation type. This showed up as emoji not rendering properly in my reader. Easy fix: switch the reader items table to the utf8mb4 character set and collation type to utf8mb4_unicode_ci. Problem solved.\n\n\nThis is where the fun really started though, and where my desire to understand the inner workings of databases started fading... My reader became so slow at loading items that it was unusable. The rest of the site worked fine, so I isolated the problem down to one database query. Due to the way I now have channels set up, this was a particularly complicated query running on the largest table in my database, reader_items which was 400k rows and growing. I delved deeper into the murky world of database performance, learning about sargable queries and how to keep your indexes fast.\n\n\nMaking sure all the tables joined in the same query have a matching collation type seemed to do the trick. My query which had blown out to over a minute was now running in a couple of seconds. A good reminder to look after your indexes! Since I was well and truly into database tuning now though, I decided I could get more performance improvements out of my reader.\n\n\nThe problem with adding new feed items to the same table is that you generally only want to read the new stuff. It's great to have fast indexes, but most of the time I really just need smaller tables. To do that my reader needed to be able to look up items in an arbitrary number of tables, but optimised to find new items in the first table it reads from. It can now do that, and the data partitioning process is automated to keep the items tables small. It can also handle reading across tables to return the correct number of items requested.\n\n\nThe problematic query now returns in less than a second for the optimised case. (I would measure it but it's not a noticeable part of using the reader any more.) My plan to fix the performance issues before making this change was to increase the specs of the server it's running on, which are pretty modest for all the work it's doing. I do however like the idea of improving the efficiency of code rather than throwing more hardware at a poorly running solution.",
"html": "Ok I totally stole the title from <a href=\"https://mathiasbynens.be/notes/mysql-utf8mb4\">this article</a>, which was really good and help me fix my problems so I wanted to link to it.<br /><br />\nI recently upgraded all my servers from Jessie to Stretch, which was long overdue. The catalyst being that certbot from Let's Encrypt started complaining about the security I was using to fetch new certificates. (It complained in a very nice way and helped fix the problem, I should add.)<br /><br />\nAnyway the upgrades went fine, Debian is very good at that. The problem was that part of the upgrade was switching from MySQL 5 to MariaDB, and all my tables were using an old character set and collation type. This showed up as emoji not rendering properly in my reader. Easy fix: switch the reader items table to the utf8mb4 character set and collation type to utf8mb4_unicode_ci. Problem solved.<br /><br />\nThis is where the fun really started though, and where my desire to understand the inner workings of databases started fading... My reader became so slow at loading items that it was unusable. The rest of the site worked fine, so I isolated the problem down to one database query. Due to the way I now have channels set up, this was a particularly complicated query running on the largest table in my database, reader_items which was 400k rows and growing. I delved deeper into the murky world of database performance, learning about <em>sargable queries</em> and how to keep your indexes fast.<br /><br />\nMaking sure all the tables joined in the same query have a matching collation type seemed to do the trick. My query which had blown out to over a minute was now running in a couple of seconds. A good reminder to look after your indexes! Since I was well and truly into database tuning now though, I decided I could get more performance improvements out of my reader.<br /><br />\nThe problem with adding new feed items to the same table is that you generally only want to read the new stuff. It's great to have fast indexes, but most of the time I really just need smaller tables. To do that my reader needed to be able to look up items in an arbitrary number of tables, but optimised to find new items in the first table it reads from. It can now do that, and the data partitioning process is automated to keep the items tables small. It can also handle reading across tables to return the correct number of items requested.<br /><br />\nThe problematic query now returns in less than a second for the optimised case. (I would measure it but it's not a noticeable part of using the reader any more.) My plan to fix the performance issues before making this change was to increase the specs of the server it's running on, which are pretty modest for all the work it's doing. I do however like the idea of improving the efficiency of code rather than throwing more hardware at a poorly running solution."
},
"author": {
"type": "card",
"name": "Malcolm Blaney",
"url": "https://unicyclic.com/mal",
"photo": "https://aperture-proxy.p3k.io/4f46272c0027449ced0d7cf8de31ea1bec37210e/68747470733a2f2f756e696379636c69632e636f6d2f6d616c2f7075626c69632f70726f66696c655f736d616c6c5f7468756d622e706e67"
},
"post-type": "article",
"_id": "2217414",
"_is_read": true
}
{
"type": "entry",
"published": "2019-02-17T11:04:17-08:00",
"url": "https://aaronparecki.com/2019/02/17/16/",
"category": [
"IndieWebCamp",
"streetcapture",
"streetphoto",
"streetweekly",
"urbanaisle",
"rawurbanshots",
"streetgrammers",
"streetsofnewyork",
"pmwintergridchallenge",
"nyc",
"newyork",
"indiewebcamp"
],
"photo": [
"https://aperture-media.p3k.io/aaronparecki.com/7562cc7735c6bd784bd040323ef6b206deed5ef267d74c480542410f482fc66c.jpg"
],
"syndication": [
"https://www.instagram.com/p/Bt_nRSqgsVa/"
],
"content": {
"text": "Throwback to a rainy and grey New York last week when I lost my voice but powered through my talks anyway. Here's to another packed week! Three talks in two cities followed by #IndieWebCamp Austin! \n#streetcapture #streetphoto #streetweekly #urbanaisle #rawurbanshots #streetgrammers #streetsofnewyork #pmwintergridchallenge #nyc #newyork",
"html": "Throwback to a rainy and grey New York last week when I lost my voice but powered through my talks anyway. Here's to another packed week! Three talks in two cities followed by <a href=\"https://aaronparecki.com/tag/indiewebcamp\">#<span class=\"p-category\">IndieWebCamp</span></a> Austin! <br /><a href=\"https://aaronparecki.com/tag/streetcapture\">#<span class=\"p-category\">streetcapture</span></a> <a href=\"https://aaronparecki.com/tag/streetphoto\">#<span class=\"p-category\">streetphoto</span></a> <a href=\"https://aaronparecki.com/tag/streetweekly\">#<span class=\"p-category\">streetweekly</span></a> <a href=\"https://aaronparecki.com/tag/urbanaisle\">#<span class=\"p-category\">urbanaisle</span></a> <a href=\"https://aaronparecki.com/tag/rawurbanshots\">#<span class=\"p-category\">rawurbanshots</span></a> <a href=\"https://aaronparecki.com/tag/streetgrammers\">#<span class=\"p-category\">streetgrammers</span></a> <a href=\"https://aaronparecki.com/tag/streetsofnewyork\">#<span class=\"p-category\">streetsofnewyork</span></a> <a href=\"https://aaronparecki.com/tag/pmwintergridchallenge\">#<span class=\"p-category\">pmwintergridchallenge</span></a> <a href=\"https://aaronparecki.com/tag/nyc\">#<span class=\"p-category\">nyc</span></a> <a href=\"https://aaronparecki.com/tag/newyork\">#<span class=\"p-category\">newyork</span></a>"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/2b8e1668dcd9cfa6a170b3724df740695f73a15c2a825962fd0a0967ec11ecdc.jpg"
},
"post-type": "photo",
"_id": "2214558",
"_is_read": true
}
It looked like a pretty regular week, but then I developed a fever, so had to stay at home some of the days.
Had conversations with the Open State Foundation deputy director and the one remaining board member I hand’t met before yet, Noor
Discussed with Frank Meeuwsen when and how to organise an IndieWebCamp in Utrecht this spring
Worked on open data for a province
Caught up with André Golliez who has started a new company with two partners in Switzerland, and we discussed their new propositions and services
Started planning a stakeholder mapping exercise for a client
Had in-depth conversations with my The Green Land partners about our plans and course for the coming year
Spent Saturday in Enschede visiting our old neighbours for the birthday of their sons, and then an informal wedding reception at Henk and Melina’s, meeting many people we hadn’t met for a while. Our little one had a great time, so she didn’t mind we stayed a bit longer to catch up with people.
{
"type": "entry",
"author": {
"name": "Ton Zijlstra",
"url": "https://www.zylstra.org/blog",
"photo": null
},
"url": "https://www.zylstra.org/blog/2019/02/week-notes-1907/",
"published": "2019-02-17T19:18:18+00:00",
"content": {
"html": "<p>It looked like a pretty regular week, but then I developed a fever, so had to stay at home some of the days.</p>\n<ul><li>Had conversations with the Open State Foundation deputy director and the one remaining board member I hand\u2019t met before yet, Noor</li>\n<li>Discussed with Frank Meeuwsen when and how to organise an IndieWebCamp in Utrecht this spring</li>\n<li>Worked on open data for a province</li>\n<li>Caught up with Andr\u00e9 Golliez who has started a new company with two partners in Switzerland, and we discussed their new propositions and services</li>\n<li>Started planning a stakeholder mapping exercise for a client</li>\n<li>Had in-depth conversations with my The Green Land partners about our plans and course for the coming year</li>\n<li>Spent Saturday in Enschede visiting our old neighbours for the birthday of their sons, and then an informal wedding reception at Henk and Melina\u2019s, meeting many people we hadn\u2019t met for a while. Our little one had a great time, so she didn\u2019t mind we stayed a bit longer to catch up with people.</li>\n</ul>",
"text": "It looked like a pretty regular week, but then I developed a fever, so had to stay at home some of the days.\nHad conversations with the Open State Foundation deputy director and the one remaining board member I hand\u2019t met before yet, Noor\nDiscussed with Frank Meeuwsen when and how to organise an IndieWebCamp in Utrecht this spring\nWorked on open data for a province\nCaught up with Andr\u00e9 Golliez who has started a new company with two partners in Switzerland, and we discussed their new propositions and services\nStarted planning a stakeholder mapping exercise for a client\nHad in-depth conversations with my The Green Land partners about our plans and course for the coming year\nSpent Saturday in Enschede visiting our old neighbours for the birthday of their sons, and then an informal wedding reception at Henk and Melina\u2019s, meeting many people we hadn\u2019t met for a while. Our little one had a great time, so she didn\u2019t mind we stayed a bit longer to catch up with people."
},
"name": "Week Notes 19#07",
"post-type": "article",
"_id": "2212824",
"_is_read": true
}
#IndieWebCamp #Austin is next weekend! Get a #website, #ownyourdata, cut back #socialmedia, or hack on #dweb #webstandards. Join @manton2(@microdotblog) @aaronpk(#indieauth #webmention) @dshanske(#WordPress #IndieWeb) & more!
IndieWebCamp Austin is coming up in a week at Capital Factory. Bunch of IndieWeb-related things I want to think about for Micro.blog that weekend. Everyone’s welcome!
{
"type": "entry",
"author": {
"name": "Manton Reece",
"url": "https://www.manton.org/",
"photo": "https://aperture-proxy.p3k.io/907926e361383204bd1bc913c143c23e70ae69bb/68747470733a2f2f6d6963726f2e626c6f672f6d616e746f6e2f6176617461722e6a7067"
},
"url": "https://www.manton.org/2019/02/15/indiewebcamp-austin-is.html",
"content": {
"html": "<p><a href=\"https://2019.indieweb.org/austin\">IndieWebCamp Austin</a> is coming up in a week at Capital Factory. Bunch of IndieWeb-related things I want to think about for Micro.blog that weekend. Everyone\u2019s welcome!</p>",
"text": "IndieWebCamp Austin is coming up in a week at Capital Factory. Bunch of IndieWeb-related things I want to think about for Micro.blog that weekend. Everyone\u2019s welcome!"
},
"published": "2019-02-15T17:10:56-06:00",
"post-type": "note",
"_id": "2194339",
"_is_read": true
}
Awesome! Let's try to get you on there! So I think your issue is that your authorization endpoint is set to indiecert.net which doesn't seem to exist. You might want to use indieauth.com instead?
{
"type": "entry",
"published": "2019-02-14T16:26:17.467Z",
"url": "https://grant.codes/2019/02/14/awesome-lets-try-to-get-you",
"syndication": [
"https://twitter.com/grantcodes/status/1096083218669936641"
],
"content": {
"text": "Awesome! Let's try to get you on there! So I think your issue is that your authorization endpoint is set to indiecert.net which doesn't seem to exist. You might want to use indieauth.com instead?",
"html": "<p>Awesome! Let's try to get you on there! So I think your issue is that your authorization endpoint is set to indiecert.net which doesn't seem to exist. You might want to use indieauth.com instead?</p>"
},
"author": {
"type": "card",
"name": "Grant Richmond",
"url": "https://grant.codes",
"photo": "https://aperture-proxy.p3k.io/be31049af9884a65289b2d14300adafc0e4030c6/68747470733a2f2f6772616e742e636f6465732f696d672f6d652e6a7067"
},
"post-type": "note",
"_id": "2176337",
"_is_read": true
}
{
"type": "entry",
"published": "2019-02-13 00:29-0800",
"url": "http://tantek.com/2019/044/t1/15-years-ago-introduced-microformats",
"category": [
"microformats",
"RDFa",
"microdata",
"HTMLFirst",
"CSS"
],
"content": {
"text": "15 years ago @KevinMarks & I introduced #microformats @oreillymedia ETech 2004 \u201creal world semantics\u201d session, before #RDFa #microdata etc., with <15k #HTMLFirst + inline #CSS+#JS: tantek.com/presentations/2004etech/realworldsemanticspres.html (faster than JS-only slides)\n\nPreviously: tantek.com/t4UY2 (https://twitter.com/t/status/433494367601717248)\n\nSince then:\n* drop the (X), just HTML\n* meta tags still web alchemy, even more bloated DRY rot\n* h-entry superceded hAtom/hentry/rel=\"bookmark\" - microformats.org/wiki/h-entry\n* recommendations: hReview still more reliable than anything from Google (https://aaronparecki.com/2016/12/17/8/owning-my-reviews). Use h-review today microformats.org/wiki/h-review\n* syndication: h-feed publishing/consuming growing rapidly. microformats.org/wiki/h-feed\n* music playlists still unsolved for any cross-site/service use-cases\n\nBlogged 15 years ago:\n* tantek.com/log/2004/02.html#d12t0012",
"html": "15 years ago <a class=\"h-cassis-username\" href=\"https://twitter.com/KevinMarks\">@KevinMarks</a> & I introduced #<span class=\"p-category\">microformats</span> <a class=\"h-cassis-username\" href=\"https://twitter.com/oreillymedia\">@oreillymedia</a> ETech 2004 \u201creal world semantics\u201d session, before #<span class=\"p-category\">RDFa</span> #<span class=\"p-category\">microdata</span> etc., with <15k #<span class=\"p-category\">HTMLFirst</span> + inline #<span class=\"p-category\">CSS</span>+#JS: <a href=\"http://tantek.com/presentations/2004etech/realworldsemanticspres.html\">tantek.com/presentations/2004etech/realworldsemanticspres.html</a> (faster than JS-only slides)<br /><br />Previously: <a href=\"http://tantek.com/t4UY2\">tantek.com/t4UY2</a> (<a href=\"https://twitter.com/t/status/433494367601717248\">https://twitter.com/t/status/433494367601717248</a>)<br /><br />Since then:<br />* drop the (X), just HTML<br />* meta tags still web alchemy, even more bloated DRY rot<br />* h-entry superceded hAtom/hentry/rel=\"bookmark\" - <a href=\"http://microformats.org/wiki/h-entry\">microformats.org/wiki/h-entry</a><br />* recommendations: hReview still more reliable than anything from Google (<a href=\"https://aaronparecki.com/2016/12/17/8/owning-my-reviews\">https://aaronparecki.com/2016/12/17/8/owning-my-reviews</a>). Use h-review today <a href=\"http://microformats.org/wiki/h-review\">microformats.org/wiki/h-review</a><br />* syndication: h-feed publishing/consuming growing rapidly. <a href=\"http://microformats.org/wiki/h-feed\">microformats.org/wiki/h-feed</a><br />* music playlists still unsolved for any cross-site/service use-cases<br /><br />Blogged 15 years ago:<br />* <a href=\"http://tantek.com/log/2004/02.html#d12t0012\">tantek.com/log/2004/02.html#d12t0012</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "http://tantek.com/",
"photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "note",
"_id": "2161499",
"_is_read": true
}
I'm hosting a Virtual IndieWeb Meetup next week. Want to talk about things you've recently done with your website or brainstorm ideas about what you want to do next with it. Come join us for a friendly night about your presence on the internet.
{
"type": "entry",
"published": "2019-02-12T11:54:20-05:00",
"url": "https://eddiehinkle.com/2019/02/12/5/rsvp/",
"category": [
"indieweb-meetup"
],
"syndication": [
"https://micro.blog/EddieHinkle",
"https://twitter.com/eddiehinkle"
],
"in-reply-to": [
"https://eddiehinkle.com/2019/02/20/1/event/"
],
"content": {
"text": "I'm hosting a Virtual IndieWeb Meetup next week. Want to talk about things you've recently done with your website or brainstorm ideas about what you want to do next with it. Come join us for a friendly night about your presence on the internet.",
"html": "I'm hosting a Virtual IndieWeb Meetup next week. Want to talk about things you've recently done with your website or brainstorm ideas about what you want to do next with it. Come <a href=\"https://eddiehinkle.com/2019/02/20/1/event/\">join us</a> for a friendly night about your presence on the internet."
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"post-type": "reply",
"_id": "2153070",
"_is_read": true
}
Trying to see how this ends up on my blog and perhaps Flickr, when replying using Yarns microsub server in combination with Monocle reader. Typing this directly in my reader.
{
"type": "entry",
"author": {
"name": "Ton Zijlstra",
"url": "https://www.zylstra.org/blog",
"photo": null
},
"url": "https://www.zylstra.org/blog/2019/02/5979/",
"published": "2019-02-12T15:37:30+00:00",
"content": {
"html": "Replied to \n<blockquote><a href=\"https://www.flickr.com/photos/tonz/47039055381/\"><img src=\"https://aperture-proxy.p3k.io/01ba0832cacdedb686288e813589ebcc99f0f5ae/68747470733a2f2f6661726d382e737461746963666c69636b722e636f6d2f373831312f34373033393035353338315f373831626166303135375f632e6a7067\" alt=\"20190209_144138\" /></a><a href=\"https://www.flickr.com/photos/tonz/47039055381/\"></a></blockquote>\n\n<p>Trying to see how this ends up on my blog and perhaps Flickr, when replying using Yarns microsub server in combination with Monocle reader. Typing this directly in my reader.</p>",
"text": "Replied to \n\n\nTrying to see how this ends up on my blog and perhaps Flickr, when replying using Yarns microsub server in combination with Monocle reader. Typing this directly in my reader."
},
"post-type": "note",
"_id": "2150857",
"_is_read": true
}
