{
"type": "entry",
"url": "https://realize.be/notes/1223",
"content": {
"text": "Finally got to expose webmentions in a block. Getting slower and slower to alpha state! #drupal #indieweb"
},
"_id": "105490",
"_source": "213",
"_is_read": true
}
Killed the webmention_io module, new module at https://github.com/swentel/indieweb : minimal microformats (more coming soon) and brid.gy publishing in it!
{
"type": "entry",
"url": "https://realize.be/notes/1219",
"content": {
"text": "Killed the webmention_io module, new module at https://github.com/swentel/indieweb : minimal microformats (more coming soon) and brid.gy publishing in it!",
"html": "Killed the webmention_io module, new module at <a href=\"https://github.com/swentel/indieweb\">https://github.com/swentel/indieweb</a> : minimal microformats (more coming soon) and brid.gy publishing in it!"
},
"_id": "104834",
"_source": "213",
"_is_read": true
}
Website owners of Brighton—it’s Homebrew Website Club this Wednesday at 6pm in the @Clearleft office. Come along and we’ll work on our personal sites together.
{
"type": "entry",
"published": "2018-03-05T18:26:29Z",
"url": "https://adactio.com/notes/13537",
"syndication": [
"https://twitter.com/adactio/status/970727267352576000"
],
"content": {
"text": "Website owners of Brighton\u2014it\u2019s Homebrew Website Club this Wednesday at 6pm in the @Clearleft office. Come along and we\u2019ll work on our personal sites together.\n\nhttps://indieweb.org/events/2018-03-07-homebrew-website-club#UK",
"html": "<p>Website owners of Brighton\u2014it\u2019s Homebrew Website Club this Wednesday at 6pm in the <a href=\"https://twitter.com/Clearleft\">@Clearleft</a> office. Come along and we\u2019ll work on our personal sites together.</p>\n\n<p><a href=\"https://indieweb.org/events/2018-03-07-homebrew-website-club#UK\">https://indieweb.org/events/2018-03-07-homebrew-website-club#UK</a></p>"
},
"_id": "104716",
"_source": "2",
"_is_read": true
}
{
"type": "entry",
"published": "2018-03-05T10:21:26-0800",
"url": "https://aaronparecki.com/2018/03/05/17/",
"category": [
"indieweb"
],
"content": {
"text": "Posting GitHub issues from my site makes my day permalinks look much less sad on days I spend a lot of time on the computer. #indieweb",
"html": "<p>Posting GitHub issues from my site makes my <a href=\"https://aaronparecki.com/2018/03/05\">day permalinks</a> look much less sad on days I spend a lot of time on the computer. #indieweb</p>"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/2b8e1668dcd9cfa6a170b3724df740695f73a15c2a825962fd0a0967ec11ecdc.jpg"
},
"_id": "104646",
"_source": "16",
"_is_read": true
}
Just implemented mp-destination on my site! I can connect multiple Micropub or Twitter accounts to my site to be able to post to other accounts from Micropub clients when I'm logged in as me. This is the first step of turning Monocle into more of a Tweetdeck-like experience!
{
"type": "entry",
"published": "2018-03-05T07:48:10-0800",
"url": "https://aaronparecki.com/2018/03/05/4/micropub-destination",
"category": [
"micropub",
"p3k"
],
"content": {
"text": "Just implemented mp-destination on my site! I can connect multiple Micropub or Twitter accounts to my site to be able to post to other accounts from Micropub clients when I'm logged in as me. This is the first step of turning Monocle into more of a Tweetdeck-like experience!",
"html": "<p>Just implemented <a href=\"https://github.com/indieweb/micropub-extensions/issues/3\">mp-destination</a> on my site! I can connect multiple Micropub or Twitter accounts to my site to be able to post to other accounts from Micropub clients when I'm logged in as me. This is the first step of turning Monocle into more of a Tweetdeck-like experience!</p>"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/2b8e1668dcd9cfa6a170b3724df740695f73a15c2a825962fd0a0967ec11ecdc.jpg"
},
"_id": "104106",
"_source": "16",
"_is_read": true
}
He actually meant Microsub which is a early draft of a way for feed reader servers and clients to talk to each other. Allowing for simplified innovative feed reader interfaces to be developed, rather than everyone having it’s own backend and parsing.
{
"type": "entry",
"published": "2018-03-05T10:09:16-0500",
"summary": "He actually meant Microsub which is a early draft of a way for feed reader servers and clients to talk to each other. Allowing for simplified innovative feed reader interfaces to be developed, rather than everyone having it\u2019s own backend and parsing.",
"url": "https://eddiehinkle.com/2018/03/05/9/reply/",
"in-reply-to": [
"https://micro.blog/hjertnes/380825"
],
"content": {
"text": "He actually meant Microsub which is a early draft of a way for feed reader servers and clients to talk to each other. Allowing for simplified innovative feed reader interfaces to be developed, rather than everyone having it\u2019s own backend and parsing.",
"html": "<p>He actually meant <a href=\"https://indieweb.org/Microsub\">Microsub</a> which is a early draft of a way for feed reader servers and clients to talk to each other. Allowing for simplified innovative feed reader interfaces to be developed, rather than everyone having it\u2019s own backend and parsing.</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://eddiehinkle.com/images/profile.jpg"
},
"refs": {
"https://micro.blog/hjertnes/380825": {
"type": "entry",
"url": "https://micro.blog/hjertnes/380825",
"name": "https://micro.blog/hjertnes/380825"
}
},
"_id": "123249",
"_source": "226",
"_is_read": true
}
{
"type": "entry",
"published": "2018-03-05T03:50:20+0000",
"url": "https://cleverdevil.io/2018/im-really-enjoying-using-together-from-ios",
"syndication": [
"https://twitter.com/cleverdevil/status/970506774464917505"
],
"content": {
"text": "I\u2019m really enjoying using Together from iOS for reading and posting on the IndieWeb: https://cleverdevil.io/s/A94HmEbBLALplpcALmAc.mov",
"html": "I\u2019m really enjoying using Together from iOS for reading and posting on the IndieWeb: <a href=\"https://cleverdevil.io/s/A94HmEbBLALplpcALmAc.mov\">https://cleverdevil.io/s/A94HmEbBLALplpcALmAc.mov</a>"
},
"author": {
"type": "card",
"name": "Jonathan LaCour",
"url": "https://cleverdevil.io/profile/cleverdevil",
"photo": "https://cleverdevil.io/file/fdbc7696a5f73864ea11a828c861e138/thumb.jpg"
},
"_id": "102880",
"_source": "71",
"_is_read": true
}
{
"type": "entry",
"published": "2018-03-05T01:43:51+0000",
"url": "https://cleverdevil.io/2018/freeing-myself-from-facebook",
"syndication": [
"https://facebook.com/10101416927213429/posts/10102754557751109",
"https://twitter.com/cleverdevil/status/970475617220222976"
],
"name": "Freeing Myself from Facebook",
"content": {
"text": "Ever since my discovery of the IndieWeb movement, I've wanted to free myself from Facebook (and Instagram) and their brand of surveillance capitalism. I want to own my own data, and be in control of how it is shared, and I don't want it to be used for advertising.\nI've had this incarnation of a personal website for a few years, and have mostly been following the POSSE publishing model, publishing most forms of content on my website, and then automatically (or manually) syndicating that content to silos like Facebook and Twitter. But, much of my content still remains trapped inside of Facebook and Instagram.\nUntil now.\nAs of March 4, 2018, I've pulled the vast majority of my Facebook content into my website, and all of my Instagram photos into my website, paving the way for me to delete myself from Facebook (and potentially Instagram) by the end of 2018. What follows is a high-level overview of how I made the move.\nFacebook\nExporting Data from Facebook\nWhile Facebook does offer an export feature, its extremely limited, only includes very low resolution versions of your photos, and is generally very difficult to process programmatically. After some research, I discovered the excellent fb-export project on GitHub. Once installed, this tool will dump a huge amount (though, not quite all) of your Facebook data into machine-readable JSON files.\nSince my website is compatible with the Micropub publishing standard, I then needed to convert this Facebook-native JSON data into microformats2 formatted JSON. Enter granary, an amazing swiss-army knife of IndieWeb by Ryan Barrett. Using granary, I whipped up a quick script that transforms the exported data into native microformats2 formatted JSON:\nhttps://gist.github.com/cleverdevil/f33530706d6e8dacd13a8bd8e8c15dba\nPublishing Liberated Data\nAt this point, I had a directory full of data ready to publish. Sort of. Unfortunately, not all of the data is easily translatable, or even desirable, to publish to my website. As a result, I created another script that let me, on a case by case basis, publish a piece of content, choose to skip it entirely, or save it to deal with later.\nhttps://gist.github.com/cleverdevil/c857695bb2de1e46686d720cad9d124c\nAfter running this script, I had a significant amount of my data copied from Facebook to my website. Huzzah!\nDealing with Photo Albums\nFacebook has a \"photo albums\" feature, and I definitely wanted to get those memories onto my website. Again, I wrote a script that processes the exported data, and selectively allows me to upload all of the photos in an album to my website via Micropub, and then drops microformats2 JSON out that I could publish later.\nhttps://gist.github.com/cleverdevil/d9c08ddc6eb2da0d060a5f6fe87ddf64\nOnce I finished processing and uploading all of the photos for the albums I wished to copy over, I ran a simple utility script I keep around to publish all of the albums as new posts to my website.\nHere are some of the results:\n\nhttps://cleverdevil.io/2015/the-lunds-visit-for-easter-and-palm-springs\n\n\nhttps://cleverdevil.io/2014/maui-2014\n\n\nhttps://cleverdevil.io/2012/hawaii-2012\n\n\nhttps://cleverdevil.io/2012/out-and-about-with-colette\n\n\nhttps://cleverdevil.io/2009/europe-trip---part-1\n\nNotice, one of these comes all the way back from 2009!\nAlmost There\nThere are still quite a few photos and other types of posts that I haven't yet been able to figure out how to migrate. Notably, Facebook has strange special albums such as \"iOS Uploads,\" \"Mobile Uploads,\" and \"iPhoto Uploads\" that represent how the photos were uploaded, not so much a group of related photos. Unfortunately, the data contained in the export produced by fb-export isn't quite adequate to deal with these yet.\nStill, I am quite pleased with my progress so far. Time to move on to Instagram!\nInstagram\nInstagram has been slowly deteriorating as a service for years, so much so that I decided to completely stop publishing to Instagram earlier this year. It turns out, dealing with Instagram is a lot easier than Facebook when it comes to liberating your data.\nDownloading My Data\nAfter some research, I found instaLooter on GitHub, which allowed me to quickly export every single photo in its original resolution, along with nearly every bit of data I needed... except the photo captions. I ran instaLooter, and embedded the unique identifier in the filenames (which instaLooter refers to as the \"code').\nGetting Metadata and Publishing\nI wrote a script that used granary to lookup the photo metadata and publish to my website via Micropub:\nhttps://gist.github.com/cleverdevil/5bb767fd152de9b4c246d01086e91399\nNote, I used the non-JSON form of Micropub in this case, because Known's Micropub implementation doesn't properly handle JSON for photos yet.\nConclusions\nIt turns out, that with a little knowhow, and a lot of persistence, you can liberate much of your data from Facebook and Instagram. I feel well on target to my goal of leaving Facebook (and maybe Instagram) entirely.",
"html": "<p>Ever since my discovery of the <a href=\"https://indieweb.org\">IndieWeb movement</a>, I've wanted to free myself from Facebook (and Instagram) and their brand of <a href=\"https://en.wikipedia.org/wiki/Surveillance_capitalism\">surveillance capitalism</a>. I want to own my own data, and be in control of how it is shared, and I don't want it to be used for advertising.</p>\n<p>I've had this incarnation of a personal website for a few years, and have mostly been following the <a href=\"https://indieweb.org/POSSE\">POSSE publishing model</a>, publishing most forms of content on my website, and then automatically (or manually) syndicating that content to <a href=\"https://indieweb.org/silo\">silos</a> like Facebook and Twitter. But, much of my content still remains trapped inside of Facebook and Instagram.</p>\n<p><em>Until now</em>.</p>\n<p>As of March 4, 2018, I've pulled the vast majority of my Facebook content into my website, and all of my Instagram photos into my website, paving the way for me to delete myself from Facebook (and potentially Instagram) by the end of 2018. What follows is a high-level overview of how I made the move.</p>\n<h2>Facebook</h2>\n<h3>Exporting Data from Facebook</h3>\n<p>While Facebook does offer an export feature, its extremely limited, only includes very low resolution versions of your photos, and is generally very difficult to process programmatically. After some research, I discovered the <a href=\"https://github.com/danburzo/fb-export\">excellent fb-export project</a> on GitHub. Once installed, this tool will dump a huge amount (though, not quite all) of your Facebook data into machine-readable JSON files.</p>\n<p>Since my website is compatible with the <a href=\"https://indieweb.org/Micropub\">Micropub publishing standard</a>, I then needed to convert this Facebook-native JSON data into <a href=\"http://microformats.org/wiki/microformats2\">microformats2 formatted JSON</a>. Enter <a href=\"https://github.com/snarfed/granary\">granary</a>, an amazing swiss-army knife of IndieWeb by <a href=\"https://snarfed.org\">Ryan Barrett</a>. Using granary, I whipped up a quick script that transforms the exported data into native microformats2 formatted JSON:</p>\n<p><a href=\"https://gist.github.com/cleverdevil/f33530706d6e8dacd13a8bd8e8c15dba\"></a><a href=\"https://gist.github.com/cleverdevil/f33530706d6e8dacd13a8bd8e8c15dba\">https://gist.github.com/cleverdevil/f33530706d6e8dacd13a8bd8e8c15dba</a></p>\n<h3>Publishing Liberated Data</h3>\n<p>At this point, I had a directory full of data ready to publish. Sort of. Unfortunately, not all of the data is easily translatable, or even desirable, to publish to my website. As a result, I created another script that let me, on a case by case basis, publish a piece of content, choose to skip it entirely, or save it to deal with later.</p>\n<p><a href=\"https://gist.github.com/cleverdevil/c857695bb2de1e46686d720cad9d124c\"></a><a href=\"https://gist.github.com/cleverdevil/c857695bb2de1e46686d720cad9d124c\">https://gist.github.com/cleverdevil/c857695bb2de1e46686d720cad9d124c</a></p>\n<p>After running this script, I had a significant amount of my data copied from Facebook to my website. Huzzah!</p>\n<h3>Dealing with Photo Albums</h3>\n<p>Facebook has a \"photo albums\" feature, and I definitely wanted to get those memories onto my website. Again, I wrote a script that processes the exported data, and selectively allows me to upload all of the photos in an album to my website via Micropub, and then drops microformats2 JSON out that I could publish later.</p>\n<p><a href=\"https://gist.github.com/cleverdevil/d9c08ddc6eb2da0d060a5f6fe87ddf64\"></a><a href=\"https://gist.github.com/cleverdevil/d9c08ddc6eb2da0d060a5f6fe87ddf64\">https://gist.github.com/cleverdevil/d9c08ddc6eb2da0d060a5f6fe87ddf64</a></p>\n<p>Once I finished processing and uploading all of the photos for the albums I wished to copy over, I ran a simple utility script I keep around to publish all of the albums as new posts to my website.</p>\n<p>Here are some of the results:</p>\n<ul><li>\n<a href=\"https://cleverdevil.io/2015/the-lunds-visit-for-easter-and-palm-springs\"></a><a href=\"https://cleverdevil.io/2015/the-lunds-visit-for-easter-and-palm-springs\">https://cleverdevil.io/2015/the-lunds-visit-for-easter-and-palm-springs</a>\n</li>\n<li>\n<a href=\"https://cleverdevil.io/2014/maui-2014\"></a><a href=\"https://cleverdevil.io/2014/maui-2014\">https://cleverdevil.io/2014/maui-2014</a>\n</li>\n<li>\n<a href=\"https://cleverdevil.io/2012/hawaii-2012\"></a><a href=\"https://cleverdevil.io/2012/hawaii-2012\">https://cleverdevil.io/2012/hawaii-2012</a>\n</li>\n<li>\n<a href=\"https://cleverdevil.io/2012/out-and-about-with-colette\"></a><a href=\"https://cleverdevil.io/2012/out-and-about-with-colette\">https://cleverdevil.io/2012/out-and-about-with-colette</a>\n</li>\n<li>\n<a href=\"https://cleverdevil.io/2009/europe-trip---part-1\"></a><a href=\"https://cleverdevil.io/2009/europe-trip---part-1\">https://cleverdevil.io/2009/europe-trip---part-1</a>\n</li>\n</ul><p>Notice, one of these comes all the way back from 2009!</p>\n<h3>Almost There</h3>\n<p>There are still quite a few photos and other types of posts that I haven't yet been able to figure out how to migrate. Notably, Facebook has strange special albums such as \"iOS Uploads,\" \"Mobile Uploads,\" and \"iPhoto Uploads\" that represent how the photos were uploaded, not so much a group of related photos. Unfortunately, the data contained in the export produced by fb-export isn't quite adequate to deal with these yet.</p>\n<p>Still, I am quite pleased with my progress so far. Time to move on to Instagram!</p>\n<h2>Instagram</h2>\n<p>Instagram has been slowly deteriorating as a service for years, so much so that I decided to <a href=\"https://www.instagram.com/p/Bd6HunOBMJ1/\">completely stop publishing to Instagram</a> earlier this year. It turns out, dealing with Instagram is a lot easier than Facebook when it comes to liberating your data.</p>\n<h3>Downloading My Data</h3>\n<p>After some research, I found <a href=\"https://github.com/althonos/instaLooter\">instaLooter</a> on GitHub, which allowed me to quickly export every single photo in its original resolution, along with nearly every bit of data I needed... except the photo captions. I ran instaLooter, and embedded the unique identifier in the filenames (which instaLooter refers to as the \"code').</p>\n<h3>Getting Metadata and Publishing</h3>\n<p>I wrote a script that used granary to lookup the photo metadata and publish to my website via Micropub:</p>\n<p><a href=\"https://gist.github.com/cleverdevil/5bb767fd152de9b4c246d01086e91399\"></a><a href=\"https://gist.github.com/cleverdevil/5bb767fd152de9b4c246d01086e91399\">https://gist.github.com/cleverdevil/5bb767fd152de9b4c246d01086e91399</a></p>\n<p>Note, I used the non-JSON form of Micropub in this case, because <a href=\"https://github.com/idno/Known\">Known</a>'s Micropub implementation doesn't properly handle JSON for photos yet.</p>\n<h2>Conclusions</h2>\n<p>It turns out, that with a little knowhow, and a lot of persistence, you can liberate much of your data from Facebook and Instagram. I feel well on target to my goal of leaving Facebook (and maybe Instagram) entirely.</p>"
},
"author": {
"type": "card",
"name": "Jonathan LaCour",
"url": "https://cleverdevil.io/profile/cleverdevil",
"photo": "https://cleverdevil.io/file/fdbc7696a5f73864ea11a828c861e138/thumb.jpg"
},
"_id": "102577",
"_source": "71",
"_is_read": true
}
I just got my GitHub notifications piped into the reader, which is a much nicer experience than reading them via email or trying to track them down on github.com!
I have a few channels set to show just an indicator dot when there are new posts rather than showing the number of new posts, a much calmer experience.
Unread posts show up with a faint yellow glow around them, and they're automatically marked as read when they scroll off the screen.
At this point, I've actually moved all of the feeds I was previously following from IRC into Aperture as a way to force myself to continue putting the finishing touches on it!
{
"type": "entry",
"published": "2018-03-04T14:22:48-0800",
"url": "https://aaronparecki.com/2018/03/04/14/",
"category": [
"monocle",
"aperture",
"microsub"
],
"photo": [
"https://aperture-media.p3k.io/aaronparecki.com/1586dde09bbac14b018bbda4ab77aa1630959ec97591ad441e10351073690ba4.png"
],
"content": {
"text": "Monocle+Aperture are coming along nicely!\n\nI just got my GitHub notifications piped into the reader, which is a much nicer experience than reading them via email or trying to track them down on github.com!\n\nI have a few channels set to show just an indicator dot when there are new posts rather than showing the number of new posts, a much calmer experience.\n\nUnread posts show up with a faint yellow glow around them, and they're automatically marked as read when they scroll off the screen.\n\nAt this point, I've actually moved all of the feeds I was previously following from IRC into Aperture as a way to force myself to continue putting the finishing touches on it!",
"html": "<p>Monocle+Aperture are coming along nicely!</p>\n\n<p>I just got my GitHub notifications piped into the reader, which is a much nicer experience than reading them via email or trying to track them down on github.com!</p>\n\n<p>I have a few channels set to show just an indicator dot when there are new posts rather than showing the number of new posts, a much calmer experience.</p>\n\n<p>Unread posts show up with a faint yellow glow around them, and they're automatically marked as read when they scroll off the screen.</p>\n\n<p>At this point, I've actually moved all of the feeds I was previously <a href=\"https://aaronparecki.com/2015/08/29/8/why-i-live-in-irc\">following from IRC</a> into Aperture as a way to force myself to continue putting the finishing touches on it!</p>"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/2b8e1668dcd9cfa6a170b3724df740695f73a15c2a825962fd0a0967ec11ecdc.jpg"
},
"_id": "102157",
"_source": "16",
"_is_read": true
}
Once I'm finished copying over individual photos, I'll complete my goal of completely extricating myself from Facebook by the end of 2018. 🎉 #OwnYourData#IndieWeb
{
"type": "entry",
"url": "https://realize.be/notes/1217",
"content": {
"text": "If you see this on Twitter, then it means brid.gy is able to publish this from my site after sending a webmention :) #indieweb"
},
"_id": "101872",
"_source": "213",
"_is_read": true
}
{
"type": "entry",
"published": "2018-03-04T18:05:32+0000",
"url": "https://ascraeus.org/micro/1520186732/",
"photo": [
"https://aperture-media.p3k.io/media.ascraeus.org/bf7c81dc7965d5e042d9a821c1997cf344e6ad4ecf71d79d9589bfc481699d7c.png"
],
"syndication": [
"https://mastodon.social/@dgold/99626957945359731"
],
"content": {
"text": "Very early days, but I\u2019ve managed to create a basic websub reader for myself. Missing more features than it has, but progress is being made #indieweb",
"html": "<a href=\"https://media.ascraeus.org/file-20180304190410-6716.png\">\n\t\t\t\t\t\t</a><p>Very early days, but I\u2019ve managed to create a basic websub reader for myself. Missing more features than it has, but progress is being made #indieweb</p>"
},
"author": {
"type": "card",
"name": "Daniel Goldsmith",
"url": "https://ascraeus.org/",
"photo": "https://aperture-media.p3k.io/ascraeus.org/652f2a9295c60ffe6414dfde913220571843a2f67f26f2e3e5ac1183791f79f5.png"
},
"_id": "101289",
"_source": "195",
"_is_read": true
}
{
"type": "entry",
"published": "2018-03-03T19:17:18-0500",
"url": "https://martymcgui.re/2018/03/03/191718/",
"category": [
"podcast",
"IndieWeb",
"this-week-indieweb-podcast"
],
"audio": [
"https://media.martymcgui.re/ab/4a/ed/d8/e249523ef7ba31bb5c61d0750e852caf68c1b6a54477b10c363de990.mp3"
],
"syndication": [
"https://huffduffer.com/schmarty/463691",
"https://twitter.com/schmarty/status/970094419633467392",
"https://www.facebook.com/marty.mcguire.54/posts/10211525708280300"
],
"name": "This Week in the IndieWeb Audio Edition \u2022 February 24th - March 2nd, 2018",
"content": {
"text": "Show/Hide Transcript \n \n Audio edition for This Week in the IndieWeb for February 24th - March 2nd, 2018.\n\nYou can find all of my audio editions and subscribe with your favorite podcast app here: martymcgui.re/podcasts/indieweb/.\n\nMusic from Aaron Parecki\u2019s 100DaysOfMusic project: Day 85 - Suit, Day 48 - Glitch, Day 49 - Floating, Day 9, and Day 11\n\nThanks to everyone in the IndieWeb chat for their feedback and suggestions. Please drop me a note if there are any changes you\u2019d like to see for this audio edition!",
"html": "Show/Hide Transcript \n \n <p>Audio edition for <a href=\"https://indieweb.org/this-week/2018-03-02.html\">This Week in the IndieWeb for February 24th - March 2nd, 2018</a>.</p>\n\n<p>You can find all of my audio editions and subscribe with your favorite podcast app here: <a href=\"https://martymcgui.re/podcasts/indieweb/\">martymcgui.re/podcasts/indieweb/</a>.</p>\n\n<p>Music from <a href=\"https://aaronparecki.com/\">Aaron Parecki</a>\u2019s <a href=\"https://100.aaronparecki.com/\">100DaysOfMusic project</a>: <a href=\"https://aaronparecki.com/2017/03/15/14/day85\">Day 85 - Suit</a>, <a href=\"https://aaronparecki.com/2017/02/06/7/day48\">Day 48 - Glitch</a>, <a href=\"https://aaronparecki.com/2017/02/07/4/day49\">Day 49 - Floating</a>, <a href=\"https://aaronparecki.com/2016/12/29/21/day-9\">Day 9</a>, and <a href=\"https://aaronparecki.com/2016/12/31/15/\">Day 11</a></p>\n\n<p>Thanks to everyone in the <a href=\"https://chat.indieweb.org/\">IndieWeb chat</a> for their feedback and suggestions. Please drop me a note if there are any changes you\u2019d like to see for this audio edition!</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"_id": "100762",
"_source": "175",
"_is_read": true
}
{
"type": "entry",
"url": "https://strugee.net/blog/2018/01/winter-break-retrospective",
"category": [
"personal",
"development"
],
"name": "Winter break retrospective & spring semester goals",
"content": {
"text": "Tonight I'll have been back at college for a full week, and I wanted to write up a little retrospective of winter break to see what I accomplished (and in particular, which goals I completed or missed).\nYou may wish to skip directly to the executive summary.\nResolved goal: Node.js manpage PR\nI didn't complete this goal per se, but I did at least resolve it by closing the Pull Request. I felt pretty bad about it (especially because I kept saying I intended to finish it) but honestly, it became clear to me that I'd just lost the motivation to keep going with it. I would love it if this was included in Node.js core, but I just consistently have higher priorities. So rather than leave it hanging and cluttering up the Pull Requests view, I just closed it to reflect reality. I made sure not to delete the branch though, in case someone (distant future me?) wants to pick it up again.\nFailed goal: deal with GPG keysigning\nI did nothing to push this goal forward. While I made numerous improvements to my GPG setup, I did not actually sign anyone's key, which was what this goal was about. This feels unfortunate. (I also do not have access to the private key material in college, and am certainly not about to ask that it be shipped to me.)\nPartially completed goal: push Debian packaging work forward\nThere were two components to this: Profanity packaging upgrades and getting the new filter-other-days packaging into Debian. I made no progress on the Profanity packaging. However, I did fix a misconfiguration in my .reportbugrc (which annoyingly had previously sent my incredibly detailed email about Profanity packaging to /dev/null) and then submitted an ITP (Intent To Package bug, which is a Debian thing) for filter-other-days. I then used that ITP bug number to fix the last .deb Lintian warning (although see below). Then I paired with Anja who is, as always, an angel, and we figured out the weirdness that is dput and mentors.debian.net. Finally I was able to upload filter-other-days(!) BUT I was in for a rude awakening - apparently Lintian checks for .debs and .dscs are different. So while my binary package was Lintian-clean, my source package unfortunately wasn't. This is something I will need to work on in the weeks to come. That being said, I'm still pretty proud of what I've accomplished here! I've made significant progress on this front.\nCompleted goal: lazymention v1\nOne of the first things I did was ship lazymention 1.0.0 - and I wrote an announcement blog post to accompany it! (In fact, I syndicated that blog post to IndieNews using lazymention, which felt pretty damn awesome.) I got some great feedback on it from the IndieWeb community, and my lobste.rs submission - which also got some great engagement - even made the front page, which was pretty unreal! I still have a lot more work to do with lazymention - in particular, it doesn't actually respect edits (so it'll resend Webmentions with every job submission) - but for now it works well. I'm super pleased with it, and have integrated it into my site deployment workflow. I even wrote a module so other people can do this, too!\nFailed goals: ActivityPub in pump.io core, pump.io PR review\nNo progress on this front. I did start hacking on a telemetry server which will eventually be helpful for our ActivityPub rollout, but that did not in any way directly help fulfill these goals. I also released 5.1 stable, but that's pretty routine by this point.\nPartially completed goal: two blog posts per week\nI stuck with this goal all the way up until the final week, where I didn't write any. (Although I wrote about my GPG keys around the time I actually flew back to college.) The first week, I wrote about my thoughts on shell script and about lazymention; the second, I wrote about the pump.io 5.1 stable release and about talking to Pull Request reviewers if you think they're wrong.\nFailed stretch goal: paper editing\nI did absolutely no editing on the paper I intend to get published (which I originally wrote for a writing class). This was a stretch goal though, so that's totally fine.\nAdditional activity: steevie maintenance\nAfter I finally found the cable I needed, I swapped out the cable that connects steevie's motherboard with the drives' SATA ports. This seemed to significantly improve disk performance, although there are still noticeable performance problems. I'm very, very happy to have finally gotten this done.\nAdditional activity: Tor relay migration from Amazon EC2 to DigitalOcean\nAfter getting some advice on tor-relays, I finally sat down and looked into moving my relay away from Amazon Web Services. This is because AWS bills by usage, which for a Tor relay ends up being incredibly inefficient. It turned out to actually be way easier than I thought, which only served to make me mad that I hadn't done it sooner. In any case, I now save approximately $240/year AND I can push 1000GB/month as opposed to the 10GB/month I pushed before. In the words of the commit where I made this change: \"this change made possible by the fact that I'm no longer getting billed up the wazoo by Amazon Web Services.\" Here's a of a Tor Metrics graph (captured today) that shows the jump:\n\nAnyway, I'm super happy I can contribute more to the Tor network and save lots of money in the process. That being said I am pretty damn salty I didn't realize this in the four years I've been running a Tor relay.\nAdditional activity: offandonagain.org maintenance\nAfter turning on NodeSecurity monitoring for offandonagain.org, I found out that the module that underlies it, node-serve-random, had some vulnerable dependencies. Not only did I fix this, I wrote a large test suite for the module and found (and fixed!) several bugs in the process. Writing a test suite also allowed me to turn on Greenkeeper for the module, which will be a huge help to me in keeping the module up-to-date.\nAdditional activity: Stratic work\nFirst off, I released beta 7 of generator-stratic! Nothing major, just some polishing stuff. Stratic is getting very close to the point where I might want to start promoting it more aggressively, or declaring it stable, and (with a lot of super-helpful feedback from my family) I worked on something that's super important before we get there: a logo!\nHere are two of my favorites so far:\n\n\n\nThese are based off the JS logo, in case you hadn't seen it before:\n\nAnyway, I have to post another iteration in the GitHub issue based on some feedback from Saul (who I had a lovely lunch with) - he thinks I should reverse it so the pipe is on the left, so it looks like the file is coming out of the pipe. But anyway you should comment there if you have feedback!\nAdditional activity: IndieWeb stuff\nI attended Homebrew Website Club in San Fransisco, which was incredible. I got to meet a bunch of new people, as well as say hi to Ryan and Tantek again, which was so nice - it's always just better to talk in real life. Tantek said (at least if I recall correctly) that my laptop was one of the best-stickered laptops he'd ever seen, which made me feel just unbelievably special. He also gave me a microformats sticker (and helped me figure out where to put it), which I had on my old laptop and had been really missing, as well as a Let's Encrypt sticker. The latter was so special I elected to put it on the inside of my laptop, which I reserve only for really special things (basically a Recurse Center refucktoring sticker and a sticker of Noah in this video, which he handed to me like a business card the first time we met). Anyway, every time I look at the Let's Encrypt sticker I just feel so happy. I love Let's Encrypt so damn much.\nHomebrew Website Club was super inspiring, so when I got back to where I was staying (at my mom's boyfriend's house) I started implementing an IndieWeb-style social stream for strugee.net. It still needs some polishing but is actually pretty close to being done. Who knows when I'll have time to finish it, but it's getting there! I'm so freaking excited, honestly. Also, I added proper timestamp mf2 metadata to my site, as well as a visual display for post edits, and I expanded what type of Webmentions the display code recognizes too!\n\n\nExecutive summary\nI resolved or completed 2 goals, partially completed 2 goals, failed 3 goals, and failed 1 stretch goal. Additionally I did significant work in 5 other areas. Out of the goals I set for myself, I completed 51% (Debian packaging work is ~2/5 complete; blog posts were written 2/3 of the time); not counting the stretch goal, I completed 61.2%. I'm pretty happy with what I got done during this period; however, while I was productive, the numbers show that I did a mediocre job sticking to my goals. In the future I should focus on making more realistic goals and then sticking to them (though not too much - it is a break, after all!).\nSpeaking of which, partway through break I felt like I was on the edge of burnout, which to me was a very clear sign that I was pushing myself way too hard during a time I should have been unwinding. Because of that I cut what I was doing a lot, which helped pretty dramatically. In fact, I think without that I wouldn't have been able to do some of the later stuff, like all the IndieWeb work. So that's another reason I have to find a way to balance sticking to goals and just relaxing (which doesn't necessarily mean not coding, just doing whatever coding I feel like in the moment) - I feel like I was pushing myself too hard to meet my goals (and then getting distracted and not meeting them) and that's what led to the feeling. Obviously there are different constraints for e.g. schoolwork; here I'm referring only to free time like breaks.\nSpring semester goals\nWith that in mind, I want to set some very broad goals for spring semester. I may update this list as time goes on, but for now I have four overarching goals I want to accomplish (besides the usual day-to-day code maintenance stuff):\nFinish editing the paper I wrote last semester on freedom-respecting software and intersectionality, and get it published\nMake some measurable progress on my Push-based Two-factor Authentication IETF draft\n\nGet access to the University of Rochester darkroom and start developing/printing photos again\nStart pushing the University of Rochester library (and maybe the journalism department?) to start adopting Tor technologies\nI'm excited to see how it goes!",
"html": "<p>Tonight I'll have been back at college for a full week, and I wanted to write up a little retrospective of winter break to see what I accomplished (and in particular, which <a href=\"https://strugee.net/blog/2017/12/winter-break-priorities-2017-18\">goals</a> I completed or missed).</p>\n<p>You may wish to skip directly to the <a href=\"https://strugee.net/blog/#executive-summary\">executive summary</a>.</p>\n<h2>Resolved goal: Node.js manpage PR</h2>\n<p>I didn't <em>complete</em> this goal per se, but I did at least resolve it <a href=\"https://github.com/nodejs/node/pull/14164#issuecomment-357909699\">by closing the Pull Request</a>. I felt pretty bad about it (especially because I kept saying I intended to finish it) but honestly, it became clear to me that I'd just lost the motivation to keep going with it. I would love it if this was included in Node.js core, but I just consistently have higher priorities. So rather than leave it hanging and cluttering up the Pull Requests view, I just closed it to reflect reality. I made sure not to delete the branch though, in case someone (distant future me?) wants to pick it up again.</p>\n<h2>Failed goal: deal with GPG keysigning</h2>\n<p>I did nothing to push this goal forward. While I made <a href=\"https://strugee.net/blog/2018/01/improving-gpg-security\">numerous improvements to my GPG setup</a>, I did not actually sign anyone's key, which was what this goal was about. This feels unfortunate. (I also do not have access to the private key material in college, and am <em>certainly</em> not about to ask that it be shipped to me.)</p>\n<h2>Partially completed goal: push Debian packaging work forward</h2>\n<p>There were two components to this: <a href=\"https://tracker.debian.org/pkg/profanity\">Profanity packaging</a> upgrades and getting the new <a href=\"https://github.com/strugee/filter-other-days\">filter-other-days</a> packaging into Debian. I made no progress on the Profanity packaging. However, I did <a href=\"https://github.com/strugee/dots/commit/2b477a7079de9ff675fd4e2d22f58938ffbb7bc9\">fix a misconfiguration in my <code>.reportbugrc</code></a> (which annoyingly had previously sent my incredibly detailed email about Profanity packaging to <code>/dev/null</code>) and then submitted <a href=\"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886310\">an ITP</a> (Intent To Package bug, which is a Debian thing) for filter-other-days. I then used that ITP bug number <a href=\"https://github.com/strugee/filter-other-days/commit/d09943c6ac4eea07720cc88596bed3594c3f4644\">to fix the last <code>.deb</code> Lintian warning</a> (although see below). Then I paired with <a href=\"https://github.com/anjakefala\">Anja</a> who is, as always, an angel, and we figured out the weirdness that is <code>dput</code> and <a href=\"https://mentors.debian.net/\">mentors.debian.net</a>. Finally I was able to upload filter-other-days(!) BUT I was in for a rude awakening - apparently Lintian checks for <code>.deb</code>s and <code>.dsc</code>s are different. So while my binary package was Lintian-clean, my source package unfortunately wasn't. This is something I will need to work on in the weeks to come. That being said, I'm still pretty proud of what I've accomplished here! I've made significant progress on this front.</p>\n<h2>Completed goal: lazymention v1</h2>\n<p>One of the first things I did was ship lazymention 1.0.0 - and I wrote <a href=\"https://strugee.net/blog/2017/12/announcing-lazymention-elegant-outbound-webmention-for-static-sites\">an announcement blog post</a> to accompany it! (In fact, I syndicated that blog post to <a href=\"https://news.indieweb.org/\">IndieNews</a> <em>using lazymention</em>, which felt pretty damn awesome.) I got some great feedback on it from the IndieWeb community, and my <a href=\"https://lobste.rs/s/kip3yk/announcing_lazymention_elegant\">lobste.rs submission</a> - which also got some great engagement - even made the front page, which was pretty unreal! I still have a lot more work to do with lazymention - in particular, it doesn't actually respect edits (so it'll resend Webmentions with every job submission) - but for now it works well. I'm super pleased with it, and have integrated it into my site deployment workflow. I even wrote <a href=\"https://github.com/strugee/ping-lazymention/\">a module</a> so other people can do this, too!</p>\n<h2>Failed goals: ActivityPub in pump.io core, pump.io PR review</h2>\n<p>No progress on this front. I did start hacking on a <a href=\"https://github.com/pump-io/telemetry\">telemetry server</a> which will eventually be helpful for our ActivityPub rollout, but that did not in any way <em>directly</em> help fulfill these goals. I also <a href=\"https://strugee.net/blog/2018/01/pump.io-5.1-stable-published-to-npm\">released 5.1 stable</a>, but that's pretty routine by this point.</p>\n<h2>Partially completed goal: two blog posts per week</h2>\n<p>I stuck with this goal all the way up until the final week, where I didn't write any. (Although I wrote about my <a href=\"https://strugee.net/blog/2018/01/improving-gpg-security\">GPG keys</a> around the time I actually flew back to college.) The first week, I wrote about <a href=\"https://strugee.net/blog/2017/12/shell-script-is-one-of-the-purest-forms-of-human-expression\">my thoughts on shell script</a> and about <a href=\"https://strugee.net/blog/2017/12/announcing-lazymention-elegant-outbound-webmention-for-static-sites\">lazymention</a>; the second, I wrote about the <a href=\"https://strugee.net/blog/2018/01/pump.io-5.1-stable-published-to-npm\">pump.io 5.1 stable release</a> and about <a href=\"https://strugee.net/blog/2018/01/tell-your-pr-reviewers-theyre-wrong\">talking to Pull Request reviewers if you think they're wrong</a>.</p>\n<h2>Failed stretch goal: paper editing</h2>\n<p>I did absolutely no editing on the paper I intend to get published (which I originally wrote for a writing class). This was a stretch goal though, so that's totally fine.</p>\n<h2>Additional activity: steevie maintenance</h2>\n<p>After I finally found the cable I needed, I swapped out the cable that connects steevie's motherboard with the drives' SATA ports. This seemed to significantly improve disk performance, although there are still noticeable performance problems. I'm very, <em>very</em> happy to have finally gotten this done.</p>\n<h2>Additional activity: Tor relay migration from Amazon EC2 to DigitalOcean</h2>\n<p>After getting some advice on <a href=\"https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays\">tor-relays</a>, I <em>finally</em> sat down and looked into moving my relay away from Amazon Web Services. This is because AWS bills by usage, which for a Tor relay ends up being incredibly inefficient. It turned out to actually be way easier than I thought, which only served to make me mad that I hadn't done it sooner. In any case, I now save approximately $240/year AND I can push 1000GB/month as opposed to the 10GB/month I pushed before. In the words of <a href=\"https://github.com/strugee/torrc/commit/8b9fe85378adc834b8b7a9953de45f508b76bc3e\">the commit where I made this change</a>: \"this change made possible by the fact that I'm no longer getting billed up the wazoo by Amazon Web Services.\" Here's a of <a href=\"https://atlas.torproject.org/#details/C3CFCC9B5993A6F0D1349858C598C4A78AFE51F9\">a Tor Metrics graph</a> (captured today) that shows the jump:</p>\n<p><img src=\"https://strugee.net/images/tor-relay-graph.svg\" alt=\"Tor Metrics graph\" /></p>\n<p>Anyway, I'm super happy I can contribute more to the Tor network <em>and</em> save lots of money in the process. That being said I am pretty damn salty I didn't realize this in the four <em>years</em> I've been running a Tor relay.</p>\n<h2>Additional activity: offandonagain.org maintenance</h2>\n<p>After turning on <a href=\"https://nodesecurity.io/\">NodeSecurity</a> monitoring for <a href=\"https://offandonagain.org\">offandonagain.org</a>, I found out that the module that underlies it, <a href=\"https://github.com/strugee/node-serve-random\">node-serve-random</a>, had some vulnerable dependencies. Not only did I fix this, I wrote a large test suite for the module and found (and fixed!) <a href=\"https://github.com/strugee/node-serve-random/blob/master/CHANGELOG.md#200---2018-01-13\">several bugs</a> in the process. Writing a test suite also allowed me to turn on <a href=\"https://greenkeeper.io/\">Greenkeeper</a> for the module, which will be a huge help to me in keeping the module up-to-date.</p>\n<h2>Additional activity: Stratic work</h2>\n<p>First off, I released <a href=\"https://github.com/straticjs/generator-stratic/blob/master/CHANGELOG.md#100-beta-7---2017-12-3\">beta 7</a> of <a href=\"https://github.com/straticjs/generator-stratic\">generator-stratic</a>! Nothing major, just some polishing stuff. Stratic is getting very close to the point where I might want to start promoting it more aggressively, or declaring it stable, and (with a <em>lot</em> of super-helpful feedback from my family) I worked on something that's super important before we get there: <a href=\"https://github.com/straticjs/RFCs/issues/22\">a logo</a>!</p>\n<p>Here are two of my favorites so far:</p>\n\n<p><img src=\"https://strugee.net/images/stratic-logo-asteroid-with-pipe.svg\" alt=\"Yellow background with a centered black file icon and a asteroid coming up from earth in the midddle and a pipe to the right\" /><img src=\"https://strugee.net/images/stratic-logo-rocket-with-pipe.svg\" alt=\"Yellow background with a centered black file icon and a rocket coming up from earth in the midddle and a pipe to the right\" /></p>\n\n<p>These are based off the JS logo, in case you hadn't seen it before:</p>\n<p><img src=\"https://strugee.net/images/js-logo.svg\" alt=\"Black JS text in the bottom-right corner of a yellow background\" /></p>\n<p>Anyway, I have to post another iteration in the <a href=\"https://github.com/straticjs/RFCs/issues/22\">GitHub issue</a> based on some feedback from <a href=\"http://saul.pw/\">Saul</a> (who I had a lovely lunch with) - he thinks I should reverse it so the pipe is on the left, so it looks like the file is coming out of the pipe. But anyway you should comment there if you have feedback!</p>\n<h2>Additional activity: IndieWeb stuff</h2>\n<p>I attended Homebrew Website Club in San Fransisco, which was <em>incredible</em>. I got to meet a bunch of new people, as well as say hi to <a href=\"http://snarfed.org/\">Ryan</a> and <a href=\"http://tantek.com/\">Tantek</a> again, which was so nice - it's always just <em>better</em> to talk in real life. Tantek said (at least if I recall correctly) that my laptop was one of the best-stickered laptops he'd ever seen, which made me feel just unbelievably special. He also gave me a <a href=\"http://microformats.org/\">microformats</a> sticker (and helped me figure out where to put it), which I had on my old laptop and had been really missing, as well as a <a href=\"https://letsencrypt.org/\">Let's Encrypt</a> sticker. The latter was so special I elected to put it on the inside of my laptop, which I reserve only for <em>really</em> special things (basically a <a href=\"https://www.recurse.com/\">Recurse Center</a> refucktoring sticker and a sticker of <a href=\"https://github.com/SwartzCr\">Noah</a> in <a href=\"https://www.eff.org/encrypt-the-web\">this video</a>, which he handed to me like a business card the first time we met). Anyway, every time I look at the Let's Encrypt sticker I just feel so happy. I love Let's Encrypt so damn much.</p>\n<p>Homebrew Website Club was super inspiring, so when I got back to where I was staying (at my mom's boyfriend's house) I started implementing an <a href=\"https://indieweb.org\">IndieWeb</a>-style social stream for strugee.net. It still needs some polishing but is actually pretty close to being done. Who knows when I'll have time to finish it, but it's getting there! I'm so freaking excited, honestly. Also, I added proper timestamp mf2 metadata to my site, as well as a visual display for post edits, and I expanded what type of Webmentions the display code recognizes too!</p>\n\n<p></p>\n<h2>Executive summary</h2>\n<p>I resolved or completed 2 goals, partially completed 2 goals, failed 3 goals, and failed 1 stretch goal. Additionally I did significant work in 5 other areas. Out of the goals I set for myself, I completed 51% (Debian packaging work is ~2/5 complete; blog posts were written 2/3 of the time); not counting the stretch goal, I completed 61.2%. I'm pretty happy with what I got done during this period; however, while I was productive, the numbers show that I did a mediocre job sticking to my goals. In the future I should focus on making more realistic goals and then sticking to them (though not too much - it is a break, after all!).</p>\n<p>Speaking of which, partway through break I felt like I was on the edge of burnout, which to me was a <em>very</em> clear sign that I was pushing myself way too hard during a time I should have been unwinding. Because of that I cut what I was doing a <em>lot</em>, which helped pretty dramatically. In fact, I think without that I wouldn't have been able to do some of the later stuff, like all the IndieWeb work. So that's another reason I have to find a way to balance sticking to goals and just relaxing (which doesn't necessarily mean not coding, just doing whatever coding I feel like in the moment) - I feel like I was pushing myself too hard to meet my goals (and then getting distracted and not meeting them) and that's what led to the feeling. Obviously there are different constraints for e.g. schoolwork; here I'm referring <em>only</em> to free time like breaks.</p>\n<h2>Spring semester goals</h2>\n<p>With that in mind, I want to set some very broad goals for spring semester. I may update this list as time goes on, but for now I have four overarching goals I want to accomplish (besides the usual day-to-day code maintenance stuff):</p>\n<ul><li>Finish editing the paper I wrote last semester on freedom-respecting software and intersectionality, and get it published</li>\n<li>Make <em>some</em> measurable progress on my <a href=\"https://github.com/strugee/draft-webpush-2fa\">Push-based Two-factor Authentication IETF draft</a>\n</li>\n<li>Get access to the University of Rochester darkroom and start developing/printing photos again</li>\n<li>Start pushing the University of Rochester library (and <em>maybe</em> the journalism department?) to start adopting Tor technologies</li>\n</ul><p>I'm excited to see how it goes!</p>"
},
"author": {
"type": "card",
"name": "AJ Jordan",
"url": "https://strugee.net/",
"photo": null
},
"_id": "100367",
"_source": "207",
"_is_read": true
}
{
"type": "entry",
"published": "2018-03-03T23:22:59+0000",
"url": "http://known.kevinmarks.com/2018/the-problem-with-self-dogfooding-was-summed-up-by-shaw-do",
"photo": [
"http://known.kevinmarks.com/file/31162468da6eacefd71fad395438cdb3/thumb.jpg"
],
"syndication": [
"https://twitter.com/kevinmarks/status/970077120931053568"
],
"name": "The problem with self-dogfooding was summed up by Shaw: \u201cDo not do unto others as you would that they should do unto you. Their tastes may not be the same.\u201d #indieweb",
"author": {
"type": "card",
"name": "Kevin Marks",
"url": "http://known.kevinmarks.com/profile/kevinmarks",
"photo": "http://known.kevinmarks.com/file/9255656669173b7867ab839ee6556f9e"
},
"_id": "100343",
"_source": "205",
"_is_read": true
}
Monocle is coming along nicely! It now automatically marks things as read as you scroll through the timeline. The unread counts in the sidebar update automatically when new posts come in as well! I'm getting so close to being able to completely switch off of IRC as my reader!
{
"type": "entry",
"published": "2018-03-02T16:38:06-0800",
"url": "https://aaronparecki.com/2018/03/02/33/monocle",
"category": [
"irc",
"monocle",
"microsub"
],
"photo": [
"https://aperture-media.p3k.io/aaronparecki.com/71a12da54aa02148fa8ddabc37fdedc8b92cccb10cab32e401366a9d47866f6a.png"
],
"video": [
"https://aperture-media.p3k.io/aaronparecki.com/6f05703eadbe481d742a7947532c6a007234bda3fbb952d1e3c818ff78eb9787.mp4"
],
"content": {
"text": "Monocle is coming along nicely! It now automatically marks things as read as you scroll through the timeline. The unread counts in the sidebar update automatically when new posts come in as well! I'm getting so close to being able to completely switch off of IRC as my reader!"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/2b8e1668dcd9cfa6a170b3724df740695f73a15c2a825962fd0a0967ec11ecdc.jpg"
},
"_id": "97469",
"_source": "16",
"_is_read": true
}
