Just pushed some updates to IndieNews! Notes like this one, (posts with no name) will now be displayed better, hopefully encouraging people to post more short stuff instead of just blog posts.
There is also a calendar view for posts, similar to the calendar on https://indieweb.org/2017-12-indieweb-challenge Thanks to @sknebel for the idea! I didn't link to the calendar permalinks from the UI yet, but you can browse to them with URLs like this: https://news.indieweb.org/en/2017/12
I also fixed an issue where the content and name of posts was not being truncated, which caused a minor IRC flood this morning due to a Microformats implied name containing an entire blog post being sent to IRC.
{
"type": "entry",
"published": "2017-12-31T10:19:11-08:00",
"url": "https://aaronparecki.com/2017/12/31/3/indienews",
"category": [
"indieweb",
"indiewebchallenge",
"indienews"
],
"photo": [
"https://aaronparecki.com/2017/12/31/3/photo.png"
],
"syndication": [
"https://news.indieweb.org/en/aaronparecki.com/2017/12/31/3/indienews"
],
"content": {
"text": "Just pushed some updates to IndieNews! Notes like this one, (posts with no name) will now be displayed better, hopefully encouraging people to post more short stuff instead of just blog posts. \n\nThere is also a calendar view for posts, similar to the calendar on https://indieweb.org/2017-12-indieweb-challenge Thanks to @sknebel for the idea! I didn't link to the calendar permalinks from the UI yet, but you can browse to them with URLs like this: https://news.indieweb.org/en/2017/12\n\nI also fixed an issue where the content and name of posts was not being truncated, which caused a minor IRC flood this morning due to a Microformats implied name containing an entire blog post being sent to IRC.",
"html": "Just pushed some updates to IndieNews! Notes like this one, (posts with no name) will now be displayed better, hopefully encouraging people to post more short stuff instead of just blog posts. \n\nThere is also a calendar view for posts, similar to the calendar on <a href=\"https://indieweb.org/2017-12-indieweb-challenge\">https://indieweb.org/2017-12-indieweb-challenge</a> Thanks to <a href=\"https://www.svenknebel.de/\">@sknebel</a> for the idea! I didn't link to the calendar permalinks from the UI yet, but you can browse to them with URLs like this: <a href=\"https://news.indieweb.org/en/2017/12\">https://news.indieweb.org/en/2017/12</a>\n\nI also fixed an issue where the content and name of posts was not being truncated, which caused a minor IRC flood this morning due to a Microformats implied name containing an entire blog post being sent to IRC."
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aaronparecki.com/images/profile.jpg"
},
"_id": "11681",
"_source": "16",
"_is_read": true
}
{
"type": "entry",
"published": "2017-12-30T20:15:08-08:00",
"url": "https://aaronparecki.com/2017/12/30/10/weather",
"category": [
"indieweb",
"newwwyear",
"weather"
],
"name": "Adding Weather to my Posts!",
"content": {
"text": "I'm super happy to be able to add myself to the list of people who publish weather info in their posts! \nI've had a long-standing goal to include weather info on all of my posts on my site! In fact, I actually started collecting historical weather info just so that I could backfill the data on my site once I added the feature. The weather database I've been collecting goes back to 2012! I decided it's been long enough and bit the bullet and sat down to finally knock it out. \nI've had the current weather up in my website header since 2016, and it turns out that I was able to reuse a lot of that existing code. \nToday I finally added support for storing weather info per post, and adding it when new posts are created. The weather is based on my current location, which I've already been automatically including in my posts for a long time. So now, when a new post is created, if the cached weather info that is shown in the header is recent enough, it bakes it into the post's storage file. \nNow my posts will all have little weather icons and the current temperature! \n I decided on using an icon font for the weather icons so that they are all visually consistent and inline with the text. The icon set I'm using is http://erikflowers.github.io/weather-icons/ The weather info itself comes from Wunderground, although I may switch to Dark Sky in the future since they have a higher per-day API limit. \nI also decided to put the weather info on the same line as the location name, since I feel like this information very closely linked to the location. (It's also stored in the location property internally.) \nI'm pretty excited to finally have this done, just in time for all my posts in 2018 to be weather-tagged! \nI'm postponing the work of backfilling all my past posts since that is going to take quite a bit of effort. I'll add it to the ever-growing list of old data to import to my site! \ud83d\ude02",
"html": "<p>I'm super happy to be able to add myself to the <a href=\"https://indieweb.org/weather#IndieWeb_Examples\">list of people</a> who publish weather info in their posts!</p>\n<p>I've had a long-standing goal to include weather info on all of my posts on my site! In fact, I actually started collecting historical weather info just so that I could backfill the data on my site once I added the feature. The weather database I've been collecting goes back to 2012! I decided it's been long enough and bit the bullet and sat down to finally knock it out.</p>\n<p>I've had the current weather up in my website header since 2016, and it turns out that I was able to reuse a lot of that existing code.</p>\n<p>Today I finally added support for storing weather info per post, and adding it when new posts are created. The weather is based on my current location, which I've already been automatically <a href=\"https://aaronparecki.com/gps/\">including in my posts</a> for a long time. So now, when a new post is created, if the cached weather info that is shown in the header is recent enough, it bakes it into the post's storage file.</p>\n<p>Now my posts will all have little weather icons and the current temperature!</p>\n<img src=\"https://aaronparecki.com/2017/12/30/10/image-1.png\" alt=\"\" /><p>I decided on using an icon font for the weather icons so that they are all visually consistent and inline with the text. The icon set I'm using is\u00a0<a href=\"http://erikflowers.github.io/weather-icons/\">http://erikflowers.github.io/weather-icons/</a>\u00a0The weather info itself comes from Wunderground, although I may switch to Dark Sky in the future since they have a higher per-day API limit.</p>\n<p>I also decided to put the weather info on the same line as the location name, since I feel like this information very closely linked to the location. (It's also stored in the location property internally.)\u00a0</p>\n<p>I'm pretty excited to finally have this done, just in time for all my posts in 2018 to be weather-tagged!\u00a0</p>\n<p>I'm postponing the work of backfilling all my past posts since that is going to take quite a bit of effort. I'll add it to the ever-growing list of old data to import to my site! \ud83d\ude02</p>"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aaronparecki.com/images/profile.jpg"
},
"_id": "11682",
"_source": "16",
"_is_read": true
}
{
"type": "entry",
"published": "2017-12-30T17:47:53-05:00",
"summary": "I made a goal of adding weather to my site by January 1st, 2018. Today, I\u2019m happy to announce that I completed that goal. Here\u2019s what it looks like:",
"url": "https://eddiehinkle.com/2017/12/30/20/article/",
"category": [
"indieweb",
"indieweb-goals"
],
"name": "Adding weather to my site",
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com",
"photo": null
},
"_id": "9543",
"_source": "39",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": null,
"url": "https://strugee.net/blog/",
"photo": null
},
"url": "https://strugee.net/blog/2017/12/announcing-lazymention-elegant-outbound-webmention-for-static-sites",
"published": "2017-12-29T18:52:04+00:00",
"content": {
"html": "<p>Last night I hit publish on version 1.0.0 of a new project, <a href=\"https://github.com/strugee/lazymention\">lazymention</a>! Whoohoo!</p>\n<p>tl;dr: lazymention exists to add Webmention support to static sites!</p>\n<p>To elaborate a little bit, I developed lazymention because I had a problem with this site: I wanted to send outbound <a href=\"https://indieweb.org/Webmention\">Webmentions</a> when I link to things, but my website is completely static. (Webmention, in case you didn't know, is a way to notify another website that you linked to them, so the other website can display some UI about your reply or whatever.) The page builds happen on my local machine, not on the server. One option would be to just send Webmentions from my local machine too, but this isn't really a good solution for a couple reasons. First, I couldn't do it automatically at build-time because the built pages wouldn't have been deployed to the server yet, so receivers of my Webmentions would reject the mentions due to the source being nonexistant. That meant that I would have to have a separate step, which wouldn't really be <em>that</em> big of a deal (lazymention reqires pinging a server too) except for the second reason: I would need some way to keep track of where I'd already sent Webmentions to, and that would require synchronizing across computers. Probably the only decent way to do that would be to check it into Git, but having a program's data store checked in right next to the source code just feels kinda ugly. Plus, then it can't be shared with other people as a service.</p>\n<p>So instead of doing it locally, I elected to build a server instead. Here's how it works: you mark up your stuff with <a href=\"https://indieweb.org/h-feed\"><code>h-feed</code></a> and <a href=\"https://indieweb.org/h-entry\"><code>h-entry</code></a>, and whenever anything happens (e.g. you publish a new blog post or whatever), you ping lazymention with the URL (either the feed or the post itself). lazymention will use your microformats2 markup to find the canonical location for a given post, then it will find all the links in the post and send Webmentions for them. And presto! You've just sent Webmentions for your blog. lazymention also records when it's sent mentions, so if you ping it again, nothing will happen unless you've updated your content. I'm also planning to add <a href=\"https://indieweb.org/WebSub\">WebSub</a> support to lazymention, too, and that'll work in the exact same way.</p>\n<p>lazymention is super easy to get started with, especially because I've provided thorough documentation in the <a href=\"https://github.com/strugee/lazymention/blob/master/README.md\">README</a>. If you find anything that's confusing or missing, please let me know by <a href=\"https://github.com/strugee/lazymention/issues/new\">filing an issue</a>! I'd love to get it fixed. In fact, I'd be thrilled to hear about both positive <em>and</em> negative installation experiences.</p>\n<p>Oh, and one more thing - lazymention is reusable in other applications. If you're writing a Node.js app and want to reuse its HTTP API, you can use its embedding API to get at the Express application and <code>Router</code> used internally. I'm not sure if people will actually find this useful, but I wrote it just for kicks anyway. See <a href=\"https://github.com/strugee/lazymention/blob/master/README.md#embedding\">the embedding documentation</a> for more!</p>\n<p>Cheers, and happy mentioning! Elegant outbound Webmention for static sites is here.</p>",
"text": "Last night I hit publish on version 1.0.0 of a new project, lazymention! Whoohoo!\ntl;dr: lazymention exists to add Webmention support to static sites!\nTo elaborate a little bit, I developed lazymention because I had a problem with this site: I wanted to send outbound Webmentions when I link to things, but my website is completely static. (Webmention, in case you didn't know, is a way to notify another website that you linked to them, so the other website can display some UI about your reply or whatever.) The page builds happen on my local machine, not on the server. One option would be to just send Webmentions from my local machine too, but this isn't really a good solution for a couple reasons. First, I couldn't do it automatically at build-time because the built pages wouldn't have been deployed to the server yet, so receivers of my Webmentions would reject the mentions due to the source being nonexistant. That meant that I would have to have a separate step, which wouldn't really be that big of a deal (lazymention reqires pinging a server too) except for the second reason: I would need some way to keep track of where I'd already sent Webmentions to, and that would require synchronizing across computers. Probably the only decent way to do that would be to check it into Git, but having a program's data store checked in right next to the source code just feels kinda ugly. Plus, then it can't be shared with other people as a service.\nSo instead of doing it locally, I elected to build a server instead. Here's how it works: you mark up your stuff with h-feed and h-entry, and whenever anything happens (e.g. you publish a new blog post or whatever), you ping lazymention with the URL (either the feed or the post itself). lazymention will use your microformats2 markup to find the canonical location for a given post, then it will find all the links in the post and send Webmentions for them. And presto! You've just sent Webmentions for your blog. lazymention also records when it's sent mentions, so if you ping it again, nothing will happen unless you've updated your content. I'm also planning to add WebSub support to lazymention, too, and that'll work in the exact same way.\nlazymention is super easy to get started with, especially because I've provided thorough documentation in the README. If you find anything that's confusing or missing, please let me know by filing an issue! I'd love to get it fixed. In fact, I'd be thrilled to hear about both positive and negative installation experiences.\nOh, and one more thing - lazymention is reusable in other applications. If you're writing a Node.js app and want to reuse its HTTP API, you can use its embedding API to get at the Express application and Router used internally. I'm not sure if people will actually find this useful, but I wrote it just for kicks anyway. See the embedding documentation for more!\nCheers, and happy mentioning! Elegant outbound Webmention for static sites is here."
},
"name": "Announcing lazymention: elegant outbound Webmention for static sites",
"_id": "123840",
"_source": "227",
"_is_read": true
}
{
"type": "entry",
"published": "2017-12-29T11:29:45Z",
"url": "https://adactio.com/links/13247",
"category": [
"technology",
"frontend",
"development",
"indieauth",
"comlink",
"apis",
"webcomponents"
],
"bookmark-of": [
"https://medium.com/samsung-internet-dev/raindrops-on-roses-whiskers-on-kittens-declarative-web-apis-and-truly-serverless-web-endpoints-50d733e6d867"
],
"content": {
"text": "Raindrops on roses, whiskers on kittens, declarative web APIs and truly serverless web endpoints\n\n \n\nThree technologies that Ada is excited about: \n\na service: IndieAuth, \na front end library: Comlink, \na pattern: APIs as Web Components.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://medium.com/samsung-internet-dev/raindrops-on-roses-whiskers-on-kittens-declarative-web-apis-and-truly-serverless-web-endpoints-50d733e6d867\">\nRaindrops on roses, whiskers on kittens, declarative web APIs and truly serverless web endpoints\n</a>\n</h3>\n\n<p>Three technologies that Ada is excited about:</p>\n\n<ol><li>a service: IndieAuth,</li>\n<li>a front end library: Comlink,</li>\n<li>a pattern: APIs as Web Components.</li>\n</ol>"
},
"_id": "8377",
"_source": "2",
"_is_read": true
}
{
"type": "entry",
"published": "2017-12-27T20:25:53-05:00",
"url": "https://david.shanske.com/2017/12/27/thinking-homepage-mentions/",
"syndication": [
"https://www.facebook.com/100002356503167/posts/1556381637783705",
"https://twitter.com/dshanske/status/946190463857512450"
],
"name": "Thinking of Homepage Mentions",
"content": {
"text": "Going to get a bit technical. This is your only warning.\nOne of the challenges I have been looking at has actually come because of others. Now, if you\u2019ve been looking at my website, you might notice that, thanks to the efforts of myself, Matthias Pfefferle, and Ryan Barrett that there have been major improvements to the presentation of different types of responses on my site. I have a screenshot of the replies on a recent post.\nFacepiles, the row of faces representing people who \u2018liked\u2019 or what have you, was actually the first project I tackled when I joined the Indieweb community back in 2014. I\u2019ve learned a lot since then.\nEither way, the current work not only builds on what I\u2019ve learned, but the contributions by Ryan, who really wanted this feature available, really jumpstarted things. Now, all of these people below don\u2019t know they commented on my site\u2026as they commented elsewhere and I pulled it back to my site via webmention.\nSo, it brings me to a new problem I want to solve. Homepage mentions. What is that? So, in June, we implemented the ability to direct webmentions(which I\u2019ve talked about before) that reference your homepage as opposed to a specific article to a designated page.\nWordPress doesn\u2019t allow the attachment of responses directly to the homepage, and david.shanske.com represents me, having a direct relationship to me on Twitter, Facebook, etc. So, any mention of my website or my username on one of those sites generates a mention that is sent to my site.\nThis is a problem in display. In recent weeks, I\u2019ve had the following scenarios my website doesn\u2019t yet deal with in a satisfactory way\nSomeone referencing my website as me, effectively tagging me in their post as having been somewhere. Example: With David(david.shanske.com)\nSomeone referencing my website as me in mentioning something I did. Example: David(david.shanske.com) kindly helped me.\nNeither of this usages by others are displayed properly website, which is why they are not showing at all. I\u2019m not sure how or where to display them.\nShould someone mentioning me in this manner give me the option of generating a post, ala Facebook\u2019s service of letting others post on your timeline, even if I moderate it somehow?\nAt the least, it should generate a message appropriate to the situation. And if it does, where should it go? Should I display recent mentions on the sidebar of my homepage? On a dedicated page?\nThe Indieweb declares a person tag as a tag on a post that refers to a specific person by URL and is done as a explicit action. Many of these mentions are explicit, but some are less so.\nMy goal is by mid January to figure out how I\u2019m going to display these, one way or another, and write some code to do this. Perhaps as my project for Indiewebcamp Baltimore, coming up in late January.\n\u00a0",
"html": "Going to get a bit technical. This is your only warning.\n<p>One of the challenges I have been looking at has actually come because of others. Now, if you\u2019ve been looking at my website, you might notice that, thanks to the efforts of myself, <a href=\"https://notiz.blog/author/matthias-pfefferle/\">Matthias Pfefferle</a>, and <a href=\"https://snarfed.org/about\">Ryan Barrett</a> that there have been major improvements to the presentation of different types of responses on my site. I have a screenshot of the replies on a recent post.</p>\n<p>Facepiles, the row of faces representing people who \u2018liked\u2019 or what have you, was actually the first <a href=\"https://david.shanske.com/2014/05/26/semantic-comments-user-testing/\">project</a> I tackled when I joined the Indieweb community back in 2014. I\u2019ve learned a lot since then.</p>\n<p>Either way, the current work not only builds on what I\u2019ve learned, but the contributions by Ryan, who really wanted this feature available, really jumpstarted things. Now, all of these people below don\u2019t know they commented on my site\u2026as they commented elsewhere and I pulled it back to my site via webmention.</p>\n<p>So, it brings me to a new problem I want to solve. Homepage mentions. What is that? So, in June, we implemented the ability to direct webmentions(which I\u2019ve talked about before) that reference your homepage as opposed to a specific article to a designated page.</p>\n<p>WordPress doesn\u2019t allow the attachment of responses directly to the homepage, and david.shanske.com represents me, having a direct relationship to me on Twitter, Facebook, etc. So, any mention of my website or my username on one of those sites generates a mention that is sent to my site.</p>\n<p>This is a problem in display. In recent weeks, I\u2019ve had the following scenarios my website doesn\u2019t yet deal with in a satisfactory way</p>\n<ul><li>Someone referencing my website as me, effectively tagging me in their post as having been somewhere. Example: With David(david.shanske.com)</li>\n<li>Someone referencing my website as me in mentioning something I did. Example: David(david.shanske.com) kindly helped me.</li>\n</ul><p>Neither of this usages by others are displayed properly website, which is why they are not showing at all. I\u2019m not sure how or where to display them.</p>\n<p>Should someone mentioning me in this manner give me the option of generating a post, ala Facebook\u2019s service of letting others post on your timeline, even if I moderate it somehow?</p>\n<p>At the least, it should generate a message appropriate to the situation. And if it does, where should it go? Should I display recent mentions on the sidebar of my homepage? On a dedicated page?</p>\n<p>The Indieweb declares a person tag as a tag on a post that refers to a specific person by URL and is done as a explicit action. Many of these mentions are explicit, but some are less so.</p>\n<p>My goal is by mid January to figure out how I\u2019m going to display these, one way or another, and write some code to do this. Perhaps as my project for Indiewebcamp Baltimore, coming up in late January.</p>\n<p>\u00a0</p>\n<p><a href=\"https://david.shanske.com/wp-content/uploads/2017/12/Screenshot-from-2017-12-27-19-51-03.png\"><img src=\"https://david.shanske.com/wp-content/uploads/2017/12/Screenshot-from-2017-12-27-19-51-03.png\" alt=\"\" width=\"614\" height=\"546\" /></a></p>"
},
"author": {
"type": "card",
"name": "David Shanske",
"url": "https://david.shanske.com",
"photo": "https://secure.gravatar.com/avatar/681eba02e72ba1d894097034a8110e61?s=125&d=default&r=g"
},
"_id": "8076",
"_source": "5",
"_is_read": true
}
{
"type": "entry",
"published": "2017-12-23T18:20:34Z",
"url": "https://adactio.com/links/13232",
"category": [
"indieweb",
"publishing",
"zines",
"design",
"trends"
],
"bookmark-of": [
"https://kottke.org/17/12/zines-are-the-future-of-media"
],
"content": {
"text": "Zines are the future of media\n\n \n\n\n So maybe we need to look at the whole package and create an\u2026 oh, I don\u2019t know, what\u2019s the phrase I need\u2026 an \u201cindie web\u201d?",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://kottke.org/17/12/zines-are-the-future-of-media\">\nZines are the future of media\n</a>\n</h3>\n\n<blockquote>\n <p>So maybe we need to look at the whole package and create an\u2026 oh, I don\u2019t know, what\u2019s the phrase I need\u2026 an \u201cindie web\u201d?</p>\n</blockquote>"
},
"_id": "7106",
"_source": "2",
"_is_read": true
}
The world-wide-web always scared the hell out of those who want to control what people consume and what their career is. The web was the equaliser.
A heartfelt missive by Christian on the eve of the US potentially losing net neutrality. I agree with every single word he’s written.
I hope that people still care that the web flows, no matter for whom or what the stream carries. The web did me a lot of good, and it can do so for many others. But it can’t do that if it turns into Cable TV. I’ve always seen the web as my media to control. To pick what I want to consume and question it by comparing it. A channel for me to publish and be scrutinised by others. A read-write medium. The only one we have. Let’s do more of the write part.
{
"type": "entry",
"published": "2017-12-22T12:13:06Z",
"url": "https://adactio.com/links/13227",
"category": [
"netneutrality",
"worldwideweb",
"history",
"personal",
"publishing",
"media",
"indieweb",
"control",
"freedom",
"resistance"
],
"bookmark-of": [
"https://christianheilmann.com/2017/12/17/the-web-we-may-have-lost/"
],
"content": {
"text": "The web we may have lost | Christian Heilmann\n\n \n\n\n The world-wide-web always scared the hell out of those who want to control what people consume and what their career is. The web was the equaliser. \n \n\nA heartfelt missive by Christian on the eve of the US potentially losing net neutrality. I agree with every single word he\u2019s written. \n\n\n I hope that people still care that the web flows, no matter for whom or what the stream carries. The web did me a lot of good, and it can do so for many others. But it can\u2019t do that if it turns into Cable TV. I\u2019ve always seen the web as my media to control. To pick what I want to consume and question it by comparing it. A channel for me to publish and be scrutinised by others. A read-write medium. The only one we have. Let\u2019s do more of the write part.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://christianheilmann.com/2017/12/17/the-web-we-may-have-lost/\">\nThe web we may have lost | Christian Heilmann\n</a>\n</h3>\n\n<blockquote>\n <p>The world-wide-web always scared the hell out of those who want to control what people consume and what their career is. The web was the equaliser.</p>\n</blockquote>\n\n<p>A heartfelt missive by Christian on the eve of the US potentially losing net neutrality. I agree with every single word he\u2019s written.</p>\n\n<blockquote>\n <p>I hope that people still care that the web flows, no matter for whom or what the stream carries. The web did me a lot of good, and it can do so for many others. But it can\u2019t do that if it turns into Cable TV. I\u2019ve always seen the web as my media to control. To pick what I want to consume and question it by comparing it. A channel for me to publish and be scrutinised by others. A read-write medium. The only one we have. Let\u2019s do more of the write part.</p>\n</blockquote>"
},
"_id": "6863",
"_source": "2",
"_is_read": true
}
This homepage is media-querytastic. It’s so refreshing to see this kind of fun experimentation on a personal site—have fun resizing your browser window!
{
"type": "entry",
"published": "2017-12-21T11:04:44Z",
"url": "https://adactio.com/links/13221",
"category": [
"responsive",
"mediaqueries",
"squishy",
"fun",
"homepage",
"indieweb",
"personal",
"publishing",
"design",
"css",
"frontend",
"development"
],
"bookmark-of": [
"https://lynnandtonic.com/"
],
"content": {
"text": "Lynn Fisher\n\n \n\nThis homepage is media-querytastic. It\u2019s so refreshing to see this kind of fun experimentation on a personal site\u2014have fun resizing your browser window!",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://lynnandtonic.com/\">\nLynn Fisher\n</a>\n</h3>\n\n<p>This homepage is media-querytastic. It\u2019s so refreshing to see this kind of fun experimentation on a personal site\u2014have fun resizing your browser window!</p>"
},
"_id": "6578",
"_source": "2",
"_is_read": true
}
{
"type": "entry",
"published": "2017-12-15T13:18:05-05:00",
"summary": "As I\u2019ve been doing my 100 Day of Reading Chapters challenge I\u2019ve been thinking about my use of Goodreads and the various functions I use it for:",
"url": "https://eddiehinkle.com/2017/12/15/11/article/",
"category": [
"indieweb",
"indieweb-goals"
],
"name": "Further thoughts the future of owning my reading",
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com",
"photo": null
},
"_id": "9544",
"_source": "39",
"_is_read": true
}
In the name of holy engagement, the native experience of products like Twitter, Facebook, and Instagram are moving away from giving people the ability to curate. They do this by taking control away from you, the user. By showing what other people liked, or by showing recommendations, without any way to turn it off, they prevent people from creating a better experience for themselves.
{
"type": "entry",
"published": "2017-12-14T19:50:36Z",
"url": "https://adactio.com/links/13199",
"category": [
"curation",
"silos",
"facebook",
"twitter",
"instagram",
"indieweb",
"algorithms"
],
"bookmark-of": [
"https://snook.ca/archives/opinion/curation"
],
"content": {
"text": "Curation - Snook.ca\n\n \n\n\n In the name of holy engagement, the native experience of products like Twitter, Facebook, and Instagram are moving away from giving people the ability to curate. They do this by taking control away from you, the user. By showing what other people liked, or by showing recommendations, without any way to turn it off, they prevent people from creating a better experience for themselves.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://snook.ca/archives/opinion/curation\">\nCuration - Snook.ca\n</a>\n</h3>\n\n<blockquote>\n <p>In the name of holy engagement, the native experience of products like Twitter, Facebook, and Instagram are moving away from giving people the ability to curate. They do this by taking control away from you, the user. By showing what other people liked, or by showing recommendations, without any way to turn it off, they prevent people from creating a better experience for themselves.</p>\n</blockquote>"
},
"_id": "4919",
"_source": "2",
"_is_read": true
}
{
"type": "entry",
"published": "2017-12-13T20:53:43-05:00",
"url": "https://david.shanske.com/2017/12/13/update-read-posts-physical-books/",
"in-reply-to": [
"http://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40049"
],
"name": "An update to read posts for physical books by Chris AldrichChris Aldrich (Chris Aldrich | BoffoSocko) Inspired by gRegor Morrill\u2019s IndieWebCamp Austin project, I went back and took a look at some of my read posts, and particularly for books. \r\nFor online material, I use the Post Kinds Plugin which does a good job of adding h-cite and p-read-of (experimental) microformats classes to the data for the... This just gave me an idea\u2026\nhttps://github.com/dshanske/indieweb-post-kinds/issues/134 \n \n\t \n\n\tPosted on 8:53PM EST\nDecember 13, 2017Kind Reply5 Comments on An update to read posts for physical books",
"content": {
"text": "This just gave me an idea\u2026\nhttps://github.com/dshanske/indieweb-post-kinds/issues/134",
"html": "This just gave me an idea\u2026\n<p>https://github.com/dshanske/indieweb-post-kinds/issues/134</p>\n<p>\u00a0</p>"
},
"author": {
"type": "card",
"name": "David Shanske",
"url": "https://david.shanske.com",
"photo": "https://secure.gravatar.com/avatar/681eba02e72ba1d894097034a8110e61?s=125&d=default&r=g"
},
"refs": {
"http://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40049": {
"type": "entry",
"url": "http://boffosocko.com/2017/12/11/an-update-to-read-posts-for-physical-books/#comment-40049",
"name": "An update to read posts for physical books",
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://boffosocko.com/author/chrisaldrich/",
"photo": "http://1.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=49&d=mm&r=pg"
}
}
},
"_id": "4725",
"_source": "5",
"_is_read": true
}
Since Tantek is still in Austin, we’re having a last-minute Homebrew Website Club meetup tonight! 6:30pm at Halcyon on 4th street. Join us to chat about the IndieWeb or work on your own site.
{
"type": "entry",
"author": {
"name": "manton",
"url": "http://www.manton.org",
"photo": null
},
"url": "http://www.manton.org/2017/12/6183.html",
"content": {
"html": "<p>Since Tantek is still in Austin, we\u2019re having a last-minute Homebrew Website Club meetup tonight! 6:30pm at Halcyon on 4th street. Join us to chat about the IndieWeb or work on your own site.</p>",
"text": "Since Tantek is still in Austin, we’re having a last-minute Homebrew Website Club meetup tonight! 6:30pm at Halcyon on 4th street. Join us to chat about the IndieWeb or work on your own site."
},
"published": "2017-12-13T14:01:01+00:00",
"updated": "2017-12-13T14:01:01+00:00",
"_id": "4569",
"_source": "12",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "manton",
"url": "http://www.manton.org",
"photo": null
},
"url": "http://www.manton.org/2017/12/indiewebcamp-austin-wrap-up.html",
"name": "IndieWebCamp Austin wrap-up",
"content": {
"html": "<p>Over the weekend we hosted the first IndieWebCamp in Austin. I\u2019m really happy with the way the event came together. I learned a lot in helping plan it, made a few mistakes that we can improve next time, but overall came away as inspired as ever to keep improving Micro.blog so that it\u2019s a standout platform of the IndieWeb movement.</p>\n<p>There\u2019s nothing like meeting in person with other members of the community. I know this from attending Apple developer conferences, but the weekend in Austin only underscored that I should be more active in the larger web community as well.</p>\n<p><img src=\"https://manton.org/images/2017/indiewebcamp_group_photo.png\" width=\"600\" height=\"400\" alt=\"IndieWebCamp group photo\" /></p>\n<p>The first day of IndieWebCamp started with introductions, a chance for attendees to demo their web sites, an overview of IndieWeb building blocks by Aaron Parecki, and then brainstorming <a href=\"http://www.manton.org/2017/12/6164.html\">what topics</a> the afternoon sessions should cover. After lunch, we held sessions on WordPress, static sites, Micropub posts, Webmentions, payment APIs, audio, decentralized aggregation, and post kinds.</p>\n<p>The second day was a hack day, with a chance to work on our own web sites. This was a very valuable day for me \u2014\u00a0being able to bounce ideas or questions off other attendees. I chose to make an improvement to Micro.blog\u2019s Micropub API endpoint to accept \u201cbookmark-of\u201d POSTs, mapping them to favorites. This evolved into opening up Micro.blog to allow favoriting any URL, even if the post doesn\u2019t exist in any feed that Micro.blog knows about yet.</p>\n<p>At the end of the day I was happy enough with the feature that I deployed my code and database changes. I demoed it using <a href=\"https://indieweb.org/Indigenous\">Indigenous</a> for iPhone and Micro.blog for Mac, favoriting an indiewebcat.com post on the web and watching it show up in the app under the post\u2019s domain name. Micro.blog got better support for Microformats with this change, pulling the author info, post text, and photo when you favorite a post via Micropub.</p>\n<p><img src=\"https://manton.org/images/2017/microblog_bookmark_of.png\" width=\"550\" height=\"590\" alt=\"Mac screenshot\" /></p>\n<p>For the last few years I\u2019ve attended WWDC and Release Notes each year, and I\u2019d usually give a talk at CocoaConf. This year I added WordCamp and IndieWebCamp, and gave a talk about indie microblogging at Refresh Austin. I hope that it works out to attend another IndieWebCamp or IndieWebSummit in 2018.</p>\n<p>Special thanks again to Tom Brown for helping out with planning IndieWebCamp Austin, EFF-Austin for hosting their holiday party after our event, and our sponsors DreamHost, Polycot Associates, and SuperBorrowNet. We should do this again next year.</p>",
"text": "Over the weekend we hosted the first IndieWebCamp in Austin. I’m really happy with the way the event came together. I learned a lot in helping plan it, made a few mistakes that we can improve next time, but overall came away as inspired as ever to keep improving Micro.blog so that it’s a standout platform of the IndieWeb movement.\nThere’s nothing like meeting in person with other members of the community. I know this from attending Apple developer conferences, but the weekend in Austin only underscored that I should be more active in the larger web community as well.\n\nThe first day of IndieWebCamp started with introductions, a chance for attendees to demo their web sites, an overview of IndieWeb building blocks by Aaron Parecki, and then brainstorming what topics the afternoon sessions should cover. After lunch, we held sessions on WordPress, static sites, Micropub posts, Webmentions, payment APIs, audio, decentralized aggregation, and post kinds.\nThe second day was a hack day, with a chance to work on our own web sites. This was a very valuable day for me \u2014\u00a0being able to bounce ideas or questions off other attendees. I chose to make an improvement to Micro.blog’s Micropub API endpoint to accept “bookmark-of” POSTs, mapping them to favorites. This evolved into opening up Micro.blog to allow favoriting any URL, even if the post doesn’t exist in any feed that Micro.blog knows about yet.\nAt the end of the day I was happy enough with the feature that I deployed my code and database changes. I demoed it using Indigenous for iPhone and Micro.blog for Mac, favoriting an indiewebcat.com post on the web and watching it show up in the app under the post’s domain name. Micro.blog got better support for Microformats with this change, pulling the author info, post text, and photo when you favorite a post via Micropub.\n\nFor the last few years I’ve attended WWDC and Release Notes each year, and I’d usually give a talk at CocoaConf. This year I added WordCamp and IndieWebCamp, and gave a talk about indie microblogging at Refresh Austin. I hope that it works out to attend another IndieWebCamp or IndieWebSummit in 2018.\nSpecial thanks again to Tom Brown for helping out with planning IndieWebCamp Austin, EFF-Austin for hosting their holiday party after our event, and our sponsors DreamHost, Polycot Associates, and SuperBorrowNet. We should do this again next year."
},
"published": "2017-12-12T17:39:26+00:00",
"updated": "2017-12-12T17:54:02+00:00",
"_id": "4449",
"_source": "12",
"_is_read": true
}
One of my goals in 2018 is to own my reading data rather than using Goodreads for all of that information. This will allow me to track information the way I want rather than have to do it like Goodreads wants me to.
{
"type": "entry",
"published": "2017-12-12T09:39:33-05:00",
"summary": "One of my goals in 2018 is to own my reading data rather than using Goodreads for all of that information. This will allow me to track information the way I want rather than have to do it like Goodreads wants me to.",
"url": "https://eddiehinkle.com/2017/12/12/2/article/",
"category": [
"100chapters",
"indieweb",
"indieweb-goals"
],
"name": "Owning my Reading and 100 Days of Reading Chapters",
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com",
"photo": null
},
"_id": "9545",
"_source": "39",
"_is_read": true
}
Following the IndieWeb mantra of “manual until it hurts”, all of my RSVP posts have been manually posted by hand to my website because it’s not something I did often and I hadn’t had the time to sit down and fix that.
{
"type": "entry",
"published": "2017-12-11T17:05:10-05:00",
"summary": "Following the IndieWeb mantra of \u201cmanual until it hurts\u201d, all of my RSVP posts have been manually posted by hand to my website because it\u2019s not something I did often and I hadn\u2019t had the time to sit down and fix that.",
"url": "https://eddiehinkle.com/2017/12/11/13/article/",
"category": [
"indieweb",
"web-dev"
],
"name": "Making RSVP posts less painful",
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com",
"photo": null
},
"_id": "9546",
"_source": "39",
"_is_read": true
}
Worked on expanding Micro.blog’s Micropub endpoint with support for bookmark-of today during IndieWebCamp Austin. The weekend really helped clarify how I want to approach replies, favorites/bookmarks, and other reactions.
{
"type": "entry",
"author": {
"name": "manton",
"url": "http://www.manton.org",
"photo": null
},
"url": "http://www.manton.org/2017/12/6166.html",
"content": {
"html": "<p>Worked on expanding Micro.blog\u2019s Micropub endpoint with support for <code>bookmark-of</code> today during IndieWebCamp Austin. The weekend really helped clarify how I want to approach replies, favorites/bookmarks, and other reactions.</p>",
"text": "Worked on expanding Micro.blog’s Micropub endpoint with support for bookmark-of today during IndieWebCamp Austin. The weekend really helped clarify how I want to approach replies, favorites/bookmarks, and other reactions."
},
"published": "2017-12-11T03:40:38+00:00",
"updated": "2017-12-11T03:40:38+00:00",
"_id": "3997",
"_source": "12",
"_is_read": true
}
