{
"type": "entry",
"published": "2018-01-18T19:40:10-05:00",
"rsvp": "yes",
"url": "https://david.shanske.com/2018/01/18/indiewebcamp-baltimore-jan-20-21-2018-baltimore-maryland/",
"in-reply-to": [
"https://2018.indieweb.org/baltimore"
],
"name": "Attending IndieWebCamp Baltimore - Jan 20-21, 2018 - Baltimore, Maryland IndieWebCamp Baltimore 2018 is a gathering for independent web creators of all kinds, from graphic artists, to designers, UX engineers, coders, hackers, to share ideas, actively work on creating for their own personal websites, and build upon each others creations. \n\n\tPosted on 7:40PM EST\nJanuary 18, 2018Kind RSVPLeave a response on IndieWebCamp Baltimore \u2013 Jan 20-21, 2018 \u2013 Baltimore, Maryland",
"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": "18328",
"_source": "5",
"_is_read": true
}
{
"type": "entry",
"published": "2018-01-18T12:55:09+1000",
"url": "https://unicyclic.com/mal/2018-01-18-Urls_as_value_systems",
"syndication": [
"https://twitter.com/malcolmblaney/status/953823084892573696"
],
"name": "Urls as value systems",
"content": {
"text": "This New York Times Magazine article covers quite a few aspects of Bitcoin and it's blockchain brethren, but the ones I'm interested in are identity and token scarcity. The article has much to say on the enabling effects of the technology in this area, but I can't help but think about other, simpler, ways to do the same thing.\n\nIndieweb is all about identity, so we have that one solved. I think token scarcity could be done too... after all, we get to decide what our websites hand out. It's easy to imagine a system where urls carry value and reciprocal links validate a value relationship. And it would avoid the FOMO problem in the crypto currency world which conflates token functionality with wild speculation on the token's value. The tokens your own website hands out will never be hoarded by speculators, I promise. ;-)\n\n\nSo what does the blockchain provide that far simpler, url based systems do not? Immutability for one, link-rot is our enemy when relying on urls as a value system. But if urls had more explicit value, maybe we would put more effort into keeping them around? The blockchain is interesting, but I think it's worth asking what problems it's trying to solve and what other solutions might look like.",
"html": "<a href=\"https://www.nytimes.com/2018/01/16/magazine/beyond-the-bitcoin-bubble.html?action=click&contentCollection=undefined&region=Footer&module=WhatsNext&version=WhatsNext&contentID=WhatsNext&moduleDetail=most-emailed-0&pgtype=undefined\">This New York Times Magazine article</a> covers quite a few aspects of Bitcoin and it's blockchain brethren, but the ones I'm interested in are identity and token scarcity. The article has much to say on the enabling effects of the technology in this area, but I can't help but think about other, simpler, ways to do the same thing.<br /><br /><a href=\"https://indieweb.org\">Indieweb</a> is all about identity, so we have that one solved. I think token scarcity could be done too... after all, we get to decide what our websites hand out. It's <a href=\"https://unicyclic.com/mal/2016-06-10-credmentions_a_distributed_ledger_for_the_indieweb\">easy to imagine</a> a system where urls carry value and reciprocal links validate a value relationship. And it would avoid the FOMO problem in the crypto currency world which conflates token functionality with wild speculation on the token's value. The tokens your own website hands out will never be hoarded by speculators, I promise. ;-)<br /><br />\nSo what does the blockchain provide that far simpler, url based systems do not? Immutability for one, link-rot is our enemy when relying on urls as a value system. But if urls had more explicit value, maybe we would put more effort into keeping them around? The blockchain is interesting, but I think it's worth asking what problems it's trying to solve and what other solutions might look like.<a href=\"https://brid.gy/publish/twitter\"></a><a href=\"https://twitter.com/malcolmblaney/status/953823084892573696\" class=\"u-syndication\"></a>"
},
"author": {
"type": "card",
"name": "Malcolm Blaney",
"url": "https://unicyclic.com/mal",
"photo": "https://aperture-media.p3k.io/unicyclic.com/bdad1528925264a15ecd0bdb92bdc5836d965b0d5f4db8797489eec259fa32de.png"
},
"_id": "124143",
"_source": "243",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "chris",
"url": "https://www.stillbreathing.co.uk/",
"photo": null
},
"url": "https://www.stillbreathing.co.uk/2018/01/15/indieweb",
"published": "2018-01-15T22:25:21+00:00",
"content": {
"html": "<p>In a moment of madness \u2013 proved by the spelling mistake \u2013 I tweeted that <a href=\"https://twitter.com/mrwiblog/status/946130324085530626\">2018 would be the year I go full IndieWeb</a>.</p>\n<p>But what is it? Basically, <a href=\"https://indieweb.org/\">IndieWeb</a> is a movement of people who want to own their own data, not have it wholly controlled by corporations. So rather than posting updates to Big Corp Social Media Website, you\u2019d post to your own site and <em>syndicate</em> out to other places. If the social media site goes down, goes bust, or goes evil, you still have all your content. After all, you wrote it \u2013 it should be yours.</p>\n<p>The syndication part is possible thanks to various clever technical bits (<a href=\"https://adactio.com/links/13151\">Jeremy Keith has a great video explaning of the building blocks of IndieWeb</a>). So you can still participate in social media sites, for example, but still own your own content.</p>\n<p>It\u2019s a \u201chave your cake and eat it\u201d situation. And I like cake.</p>\n<p>I, over the course of this year I intend to become independent of Twitter, Pocket and GMail. That\u2019s not to say I\u2019ll stop using those services \u2013 I find them all valuable \u2013 but my data won\u2019t be owned by them. Fortunately all my websites have their own self-hosted CMS systems (mainly WordPress) which makes the job a lot easier.</p>\n<p>And who knows, I may find that this IndieWeb thing allows me to start syndicating to new places such as this Mastadon thing I keep hearing about. The choice will be, for the first time, all mine.</p>",
"text": "In a moment of madness \u2013 proved by the spelling mistake \u2013 I tweeted that 2018 would be the year I go full IndieWeb.\nBut what is it? Basically, IndieWeb is a movement of people who want to own their own data, not have it wholly controlled by corporations. So rather than posting updates to Big Corp Social Media Website, you\u2019d post to your own site and syndicate out to other places. If the social media site goes down, goes bust, or goes evil, you still have all your content. After all, you wrote it \u2013 it should be yours.\nThe syndication part is possible thanks to various clever technical bits (Jeremy Keith has a great video explaning of the building blocks of IndieWeb). So you can still participate in social media sites, for example, but still own your own content.\nIt\u2019s a \u201chave your cake and eat it\u201d situation. And I like cake.\nI, over the course of this year I intend to become independent of Twitter, Pocket and GMail. That\u2019s not to say I\u2019ll stop using those services \u2013 I find them all valuable \u2013 but my data won\u2019t be owned by them. Fortunately all my websites have their own self-hosted CMS systems (mainly WordPress) which makes the job a lot easier.\nAnd who knows, I may find that this IndieWeb thing allows me to start syndicating to new places such as this Mastadon thing I keep hearing about. The choice will be, for the first time, all mine."
},
"name": "IndieWeb",
"_id": "123961",
"_source": "235",
"_is_read": true
}
{
"type": "entry",
"published": "2018-01-15T02:45:36+00:00",
"url": "https://miklb.com/blog/2018/01/15/3223/",
"syndication": [
"https://twitter.com/miklb/status/952733486942695424"
],
"name": "02:45# \n\t\t\t\t\t\t\t\t\t\t\t\t \n\t\t\t\t\t\t\t\t\t\t\t\nNice update to @brentsimmons Evergreen, send item to Micro.blog macOS app. Simple markdown ready link to the feed item. \ud83e\udd1efor micropub support down the road. https://ranchero.com/evergreen/",
"content": {
"text": "Nice update to @brentsimmons Evergreen, send item to Micro.blog macOS app. Simple markdown ready link to the feed item. \ud83e\udd1efor micropub support down the road. https://ranchero.com/evergreen/",
"html": "<p>Nice update to <a href=\"https://twitter.com/brentsimmons\">@brentsimmons</a> Evergreen, send item to Micro.blog macOS app. Simple markdown ready link to the feed item. \ud83e\udd1efor micropub support down the road. <a href=\"https://ranchero.com/evergreen/\">https://ranchero.com/evergreen/</a>\n</p>"
},
"_id": "18348",
"_source": "42",
"_is_read": true
}
{
"type": "entry",
"published": "2018-01-15T02:45:36+00:00",
"url": "https://miklb.com/2018/01/3223/",
"syndication": [
"https://twitter.com/miklb/status/952733486942695424"
],
"name": "02:45# \n\t\t\t\t\t\t\t\t\t\t\t\t \n\t\t\t\t\t\t\t\t\t\t\t\nNice update to @brentsimmons Evergreen, send item to Micro.blog macOS app. Simple markdown ready link to the feed item. \ud83e\udd1efor micropub support down the road. https://ranchero.com/evergreen/",
"content": {
"text": "Nice update to @brentsimmons Evergreen, send item to Micro.blog macOS app. Simple markdown ready link to the feed item. \ud83e\udd1efor micropub support down the road. https://ranchero.com/evergreen/",
"html": "<p>Nice update to <a href=\"https://twitter.com/brentsimmons\">@brentsimmons</a> Evergreen, send item to Micro.blog macOS app. Simple markdown ready link to the feed item. \ud83e\udd1efor micropub support down the road. <a href=\"https://ranchero.com/evergreen/\">https://ranchero.com/evergreen/</a>\n</p>"
},
"_id": "16287",
"_source": "42",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Peter Molnar",
"url": "https://petermolnar.net",
"photo": null
},
"url": "https://petermolnar.net/linkedin-public-settings-ignored/",
"published": "2018-01-14T12:00:00+00:00",
"content": {
"html": "<p>A few days ago, on the #indieweb Freenode channel<a href=\"https://petermolnar.net/#fn1\">1</a> one of the users asked if we knew an indieweb-friendly way of getting data out of LinkedIn. I wasn't paying attention to any recent news related to LinkedIn, though I've heard a few things, such as they are struggling to prevent data scraping: the note mentioned that they believe it's a problem that employers keep an eye on changes in LinkedIn profiles via 3rd party. This, indeed, can be an issue, but there are ways to manage this within LinkedIn: your public profile settings<a href=\"https://petermolnar.net/#fn2\">2</a>.</p>\n<p>In my case, this was set to visible to everyone for years, and by the time I had to set it up (again: years), it was working as intended. But a few days ago, for my surprise, visiting my profile while logged out resulted in this:</p>\n<a href=\"https://petermolnar.net/files/linkedin-public-profile-issues-authwall_b.png\"> <img src=\"https://petermolnar.net/files/linkedin-public-profile-issues-authwall_z.png\" title=\"\" alt=\"LinkedIn showing a paywall-like 'authwall' for profiles set explicitly to public for everyone\" /></a>\n\nLinkedIn showing a paywall-like 'authwall' for profiles set explicitly to public for everyone\n<p>and this:</p>\n<pre><code>$ wget -O- https://www.linkedin.com/in/petermolnareu\n--2018-01-14 10:26:12-- https://www.linkedin.com/in/petermolnareu\nResolving www.linkedin.com (www.linkedin.com)... 91.225.248.129, 2620:109:c00c:104::b93f:9001\nConnecting to www.linkedin.com (www.linkedin.com)|91.225.248.129|:443... connected.\nHTTP request sent, awaiting response... 999 Request denied\n2018-01-14 10:26:12 ERROR 999: Request denied.</code></pre>\n<p>or this:</p>\n<pre><code>$ curl https://www.linkedin.com/in/petermolnareu\n<html><head>\n<script type=\"text/javascript\">\nwindow.onload = function() {\n // Parse the tracking code from cookies.\n var trk = \"bf\";\n var trkInfo = \"bf\";\n var cookies = document.cookie.split(\"; \");\n for (var i = 0; i < cookies.length; ++i) {\n if ((cookies[i].indexOf(\"trkCode=\") == 0) && (cookies[i].length > 8)) {\n trk = cookies[i].substring(8);\n }\n else if ((cookies[i].indexOf(\"trkInfo=\") == 0) && (cookies[i].length > 8)) {\n trkInfo = cookies[i].substring(8);\n }\n }\n\n if (window.location.protocol == \"http:\") {\n // If \"sl\" cookie is set, redirect to https.\n for (var i = 0; i < cookies.length; ++i) {\n if ((cookies[i].indexOf(\"sl=\") == 0) && (cookies[i].length > 3)) {\n window.location.href = \"https:\" + window.location.href.substring(window.location.protocol.length);\n return;\n }\n }\n }\n\n // Get the new domain. For international domains such as\n // fr.linkedin.com, we convert it to www.linkedin.com\n var domain = \"www.linkedin.com\";\n if (domain != location.host) {\n var subdomainIndex = location.host.indexOf(\".linkedin\");\n if (subdomainIndex != -1) {\n domain = \"www\" + location.host.substring(subdomainIndex);\n }\n }\n\n window.location.href = \"https://\" + domain + \"/authwall?trk=\" + trk + \"&trkInfo=\" + trkInfo +\n \"&originalReferer=\" + document.referrer.substr(0, 200) +\n \"&sessionRedirect=\" + encodeURIComponent(window.location.href);\n}\n</script>\n</head></html></code></pre>\nSo I started digging. According to the LinkedIn FAQ<a href=\"https://petermolnar.net/#fn3\">3</a> there is a page where you can set your profile's public visibility. Those settings, for me, were still set to:\n<a href=\"https://petermolnar.net/files/linkedin-public-profile-issues-settings_b.png\"> <img src=\"https://petermolnar.net/files/linkedin-public-profile-issues-settings_z.png\" title=\"\" alt=\"LinkedIn public profile settings\" /></a>\n\nLinkedIn public profile settings\n<p>Despite the settings, there is no public profile for logged out users.</p>\n<p>I'd like to understand what it going on, because so far, this looks like a fat lie from LinkedIn. Hopefully just a bug.</p>\n<h2>UPDATE</h2>\n<p><del>I tried setting referrers and user agents, used different IP addresses, still nothing.</del> I can't type today and managed to mistype <code>https://google.com</code> - the referrer ended up as <code>https:/google.com</code>. So, following the notes on HN, setting a referrer to Google sometimes works. After a few failures it will lock you out again, referrer or not. This is even uglier if it was a proper authwall for everyone.</p>\n<pre><code>curl 'https://www.linkedin.com/in/petermolnareu' \\\n-e 'https://google.com/' \\\n-H 'accept-encoding: text' -H \\\n'accept-language: en-US,en;q=0.9,' \\\n-H 'user-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36'</code></pre>\n<pre><code><!DOCTYPE html>...</code></pre>\n\n\n<ol><li><p><a href=\"https://chat.indieweb.org/\">https://chat.indieweb.org</a><a href=\"https://petermolnar.net/#fnref1\">\u21a9</a></p></li>\n<li><p><a href=\"https://www.linkedin.com/public-profile/settings\">https://www.linkedin.com/public-profile/settings</a><a href=\"https://petermolnar.net/#fnref2\">\u21a9</a></p></li>\n<li><p><a href=\"https://www.linkedin.com/help/linkedin/answer/83?query=public\">https://www.linkedin.com/help/linkedin/answer/83?query=public</a><a href=\"https://petermolnar.net/#fnref3\">\u21a9</a></p></li>\n</ol>",
"text": "A few days ago, on the #indieweb Freenode channel1 one of the users asked if we knew an indieweb-friendly way of getting data out of LinkedIn. I wasn't paying attention to any recent news related to LinkedIn, though I've heard a few things, such as they are struggling to prevent data scraping: the note mentioned that they believe it's a problem that employers keep an eye on changes in LinkedIn profiles via 3rd party. This, indeed, can be an issue, but there are ways to manage this within LinkedIn: your public profile settings2.\nIn my case, this was set to visible to everyone for years, and by the time I had to set it up (again: years), it was working as intended. But a few days ago, for my surprise, visiting my profile while logged out resulted in this:\n \n\nLinkedIn showing a paywall-like 'authwall' for profiles set explicitly to public for everyone\nand this:\n$ wget -O- https://www.linkedin.com/in/petermolnareu\n--2018-01-14 10:26:12-- https://www.linkedin.com/in/petermolnareu\nResolving www.linkedin.com (www.linkedin.com)... 91.225.248.129, 2620:109:c00c:104::b93f:9001\nConnecting to www.linkedin.com (www.linkedin.com)|91.225.248.129|:443... connected.\nHTTP request sent, awaiting response... 999 Request denied\n2018-01-14 10:26:12 ERROR 999: Request denied.\nor this:\n$ curl https://www.linkedin.com/in/petermolnareu\n<html><head>\n<script type=\"text/javascript\">\nwindow.onload = function() {\n // Parse the tracking code from cookies.\n var trk = \"bf\";\n var trkInfo = \"bf\";\n var cookies = document.cookie.split(\"; \");\n for (var i = 0; i < cookies.length; ++i) {\n if ((cookies[i].indexOf(\"trkCode=\") == 0) && (cookies[i].length > 8)) {\n trk = cookies[i].substring(8);\n }\n else if ((cookies[i].indexOf(\"trkInfo=\") == 0) && (cookies[i].length > 8)) {\n trkInfo = cookies[i].substring(8);\n }\n }\n\n if (window.location.protocol == \"http:\") {\n // If \"sl\" cookie is set, redirect to https.\n for (var i = 0; i < cookies.length; ++i) {\n if ((cookies[i].indexOf(\"sl=\") == 0) && (cookies[i].length > 3)) {\n window.location.href = \"https:\" + window.location.href.substring(window.location.protocol.length);\n return;\n }\n }\n }\n\n // Get the new domain. For international domains such as\n // fr.linkedin.com, we convert it to www.linkedin.com\n var domain = \"www.linkedin.com\";\n if (domain != location.host) {\n var subdomainIndex = location.host.indexOf(\".linkedin\");\n if (subdomainIndex != -1) {\n domain = \"www\" + location.host.substring(subdomainIndex);\n }\n }\n\n window.location.href = \"https://\" + domain + \"/authwall?trk=\" + trk + \"&trkInfo=\" + trkInfo +\n \"&originalReferer=\" + document.referrer.substr(0, 200) +\n \"&sessionRedirect=\" + encodeURIComponent(window.location.href);\n}\n</script>\n</head></html>\nSo I started digging. According to the LinkedIn FAQ3 there is a page where you can set your profile's public visibility. Those settings, for me, were still set to:\n \n\nLinkedIn public profile settings\nDespite the settings, there is no public profile for logged out users.\nI'd like to understand what it going on, because so far, this looks like a fat lie from LinkedIn. Hopefully just a bug.\nUPDATE\nI tried setting referrers and user agents, used different IP addresses, still nothing. I can't type today and managed to mistype https://google.com - the referrer ended up as https:/google.com. So, following the notes on HN, setting a referrer to Google sometimes works. After a few failures it will lock you out again, referrer or not. This is even uglier if it was a proper authwall for everyone.\ncurl 'https://www.linkedin.com/in/petermolnareu' \\\n-e 'https://google.com/' \\\n-H 'accept-encoding: text' -H \\\n'accept-language: en-US,en;q=0.9,' \\\n-H 'user-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36'\n<!DOCTYPE html>...\n\n\nhttps://chat.indieweb.org\u21a9\nhttps://www.linkedin.com/public-profile/settings\u21a9\nhttps://www.linkedin.com/help/linkedin/answer/83?query=public\u21a9"
},
"name": "LinkedIn is ignoring user settings",
"_id": "161767",
"_source": "268",
"_is_read": true
}
{
"type": "entry",
"published": "2018-01-11T09:52:30-08:00",
"url": "https://aaronparecki.com/2018/01/11/5/",
"category": [
"indieweb"
],
"content": {
"text": "Test post for Superfeedr to see if it will find my #indieweb tagged posts",
"html": "Test post for Superfeedr to see if it will find my <a href=\"https://aaronparecki.com/tag/indieweb\">#indieweb</a> tagged posts"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aaronparecki.com/images/profile.jpg"
},
"_id": "14608",
"_source": "16",
"_is_read": true
}
{
"type": "entry",
"published": "2018-01-08T23:16:14+00:00",
"url": "https://cleverdevil.io/2018/great-progress-is-being-made-on-together---cleverdeviltogether",
"syndication": [
"https://twitter.com/cleverdevil/status/950506461079228417"
],
"content": {
"text": "Great progress is being made on Together - https://github.com/cleverdevil/together - an open source \"reader\" for the open web, with support for IndieWeb standards like Micropub and Microsub. Check out this quick demo \u2013 http://share.cleverdevil.io/JNrG4pVNfY.mp4",
"html": "Great progress is being made on Together - <a href=\"https://github.com/cleverdevil/together\">https://github.com/cleverdevil/together</a> - an open source \"reader\" for the open web, with support for IndieWeb standards like Micropub and Microsub. Check out this quick demo \u2013 <a href=\"http://share.cleverdevil.io/JNrG4pVNfY.mp4\">http://share.cleverdevil.io/JNrG4pVNfY.mp4</a>"
},
"author": {
"type": "card",
"name": "Jonathan LaCour",
"url": "https://cleverdevil.io/profile/cleverdevil",
"photo": "https://cleverdevil.io/file/2fa19f964fb8970faaf20b909c69d6cb/thumb.png"
},
"_id": "12709",
"_source": "71",
"_is_read": true
}
{
"type": "entry",
"published": "2018-01-08T17:46:14+00:00",
"url": "https://cleverdevil.io/2018/micro-monday-eddie-hinkle",
"syndication": [
"https://twitter.com/cleverdevil/status/950423413444706305"
],
"name": "Micro Monday: Eddie Hinkle",
"content": {
"text": "Its our first ever Micro Monday, people! Thanks to @manton and @macgenie for deciding to make this happen. I think its a great way to grow the community of Indie Bloggers and Micro.blog itself. My first recommendation for my followers is @eddiehinkle. Eddie is a fellow IndieWeb developer that I've enjoyed getting to know over the past year or two. Eddie works on an iOS app called Indigenous: Indigenous is an iOS app that is in development. It\u2019s goal is to provide a native iOS interface to the indieweb movement. Indigenous is open source, written in Apple's Swift programming language. If you're an IndieWeb-curious developer on Apple platforms, I'd encourage you to get involved with Eddie, and help him with Indigenous! In addition to his work on the IndieWeb, I also appreciate following Eddie because he writes thoughtful posts about, you know, being a human. Its always refreshing to see someone share how their faith informs their life in an open and honest, accepting way. Thanks for being awesome, Eddie!",
"html": "<p>Its our first ever <a href=\"http://micro.welltempered.net/2018/01/07/micro-monday-launches.html\">Micro Monday</a>, people! Thanks to <a href=\"https://micro.blog/manton\">@manton</a>\u00a0and <a href=\"https://micro.blog/macgenie\">@macgenie</a>\u00a0for deciding to make this happen. I think its a great way to grow the community of Indie Bloggers and <a href=\"https://micro.blog\">Micro.blog</a>\u00a0itself. My first recommendation for my followers is <a href=\"https://micro.blog/eddiehinkle\">@eddiehinkle</a>.</p>\n<p>Eddie is a fellow <a href=\"https://indieweb.org\">IndieWeb</a>\u00a0developer that I've enjoyed getting to know over the past year or two. Eddie works on an iOS app called <a href=\"https://eddiehinkle.com/projects/indigenous/\">Indigenous</a>:</p>\n<blockquote><p><strong>Indigenous</strong> is an iOS app that is in development. It\u2019s goal is to provide a native iOS interface to the indieweb movement.</p></blockquote>\n<p><a href=\"https://github.com/EdwardHinkle/indigenous-ios\">Indigenous is open source</a>, written in Apple's Swift programming language. If you're an IndieWeb-curious developer on Apple platforms, I'd encourage you to get involved with Eddie, and help him with Indigenous!</p>\n<p>In addition to his work on the IndieWeb, I also appreciate following Eddie because he writes <a href=\"https://eddiehinkle.com/2018/01/08/7/article/\">thoughtful</a>\u00a0<a href=\"https://eddiehinkle.com/2018/01/08/7/article/\">posts</a> about, you know, <em>being a human</em>. Its always refreshing to see someone share how their\u00a0faith informs their life in an open and honest, accepting way.</p>\n<p>Thanks for being awesome, Eddie!</p>"
},
"author": {
"type": "card",
"name": "Jonathan LaCour",
"url": "https://cleverdevil.io/profile/cleverdevil",
"photo": "https://cleverdevil.io/file/2fa19f964fb8970faaf20b909c69d6cb/thumb.png"
},
"_id": "12466",
"_source": "71",
"_is_read": true
}
{
"type": "entry",
"published": "2018-01-07T18:41:28+00:00",
"url": "https://miklb.com/2018/01/3164/",
"syndication": [
"https://twitter.com/miklb/status/950074698041356290"
],
"in-reply-to": [
"https://twitter.com/shiflett/status/950067527958200320?ref_src=twsrc%5Etfw"
],
"name": "January 7, 2018 \n\t\t\t\t\t\t\t\t\t\t\t\t18:41# \n\t\t\t\t\t\t\t\t\t\t\t \n\t\t\t\t\t\t\t\t\t\t\t\n\t\n\n\t\t\n\t\t\t\n\t\t\t\t\n \n\t\nI debated using Webmentions but ultimately decided no comments this time. Let people respond thoughtfully with a post of their own. Bring blogging back. :-) \u2014 Chris Shiflett (@shiflett) January 7, 2018 \n \n\nthat\u2019s what a webmention is \u2013 a post on my blog in reply to someone else\u2019s post. Just like how I\u2019m using my site to create this reply that goes to Twitter.",
"content": {
"text": "that\u2019s what a webmention is \u2013 a post on my blog in reply to someone else\u2019s post. Just like how I\u2019m using my site to create this reply that goes to Twitter.",
"html": "<p>that\u2019s what a webmention is \u2013 a post on my blog in reply to someone else\u2019s post. Just like how I\u2019m using my site to create this reply that goes to Twitter.\n</p>"
},
"refs": {
"https://twitter.com/shiflett/status/950067527958200320?ref_src=twsrc%5Etfw": {
"type": "entry",
"url": "https://twitter.com/shiflett/status/950067527958200320?ref_src=twsrc%5Etfw",
"content": {
"text": "I debated using Webmentions but ultimately decided no comments this time. Let people respond thoughtfully with a post of their own. Bring blogging back. :-) \u2014 Chris Shiflett (@shiflett) January 7, 2018"
}
}
},
"_id": "11784",
"_source": "42",
"_is_read": true
}
{
"type": "entry",
"published": "2018-01-06T14:49:39-08:00",
"url": "https://aaronparecki.com/2018/01/06/13/code-snippets",
"featured": "https://aaronparecki.com/2018/01/06/13/image-2.png",
"category": [
"p3k",
"indieweb",
"code"
],
"name": "Owning my Code Snippets",
"content": {
"text": "It's very convenient to be able to quickly share a link to a code snippet, which is something I've mostly done using gist.github.com. While often the code snippets are sort of throwaway, I still feel bad that I'm posting them in a place that I don't control.\nToday I added support to my site for natively posting code snippets. It wasn't nearly as hard as I was imagining it was going to be! Since my site doesn't have a posting interface of its own, that also meant that I needed to add support to Quill to create these posts via Micropub.\nSince this is still relatively experimental, I didn't add a button to it in Quill, but the page is live.\nThe only required part of this is the code box. The interface lets you optionally set a filename, which will automatically set the language if it matches a list of known languages. The language is included in order to indicate to my site which syntax highlighter to use. Here's what that ends up looking like on my site.\nI use the GeSHi syntax highlighter, which covers a wide range of languages and works very well, but I'm not super happy with the colors it uses. I'd like to find a stylesheet or even a different syntax highlighter that looks closer to the colors on GitHub. In the mean time, I'm happy enough with this to use it.\nI ended up doing quite a bit of fiddling with my CSS to make these posts look good. You'll notice the grey background of the code block extends to the edges of the post, whereas normally there would be some padding. I also changed the font of the post name to a fixed-width font. If there is no filename, then I wanted the grey background to extend to the top of the frame, which is also something unique to these posts.\nThe last step of making this actually useful is to integrate this into my browser workflow, including editing the posts easily. There is a bookmarklet that will either open up a new window or launch the editing interface depending on whether I'm looking at an existing code post.\nI'm pretty happy with this, and I hope I don't post on GitHub anymore unless I'm specifically using their fork feature of Gists!",
"html": "<p>It's very convenient to be able to quickly share a link to a code snippet, which is something I've mostly done using <a href=\"https://gist.github.com\">gist.github.com</a>. While often the code snippets are sort of throwaway, I still feel bad that I'm posting them in a place that I don't control.</p>\n<p>Today I added support to my site for natively posting code snippets. It wasn't nearly as hard as I was imagining it was going to be! Since my site doesn't have a posting interface of its own, that also meant that I needed to add support to <a href=\"https://quill.p3k.io\">Quill</a> to create these posts via <a href=\"https://micropub.net\">Micropub</a>.</p>\n<p>Since this is still relatively experimental, I didn't add a button to it in Quill, but the page is live.</p>\n<img src=\"https://aaronparecki.com/2018/01/06/13/image-1.png\" alt=\"\" /><p>The only required part of this is the code box. The interface lets you optionally set a filename, which will automatically set the language if it matches a list of known languages. The language is included in order to indicate to my site which syntax highlighter to use. Here's what that ends up looking like on my site.</p>\n<img src=\"https://aaronparecki.com/2018/01/06/13/image-2.png\" alt=\"\" class=\"u-featured\" /><p>I use the <a href=\"http://qbnz.com/highlighter/\">GeSHi</a> syntax highlighter, which covers a wide range of languages and works very well, but I'm not super happy with the colors it uses. I'd like to find a stylesheet or even a different syntax highlighter that looks closer to the colors on GitHub. In the mean time, I'm happy enough with this to use it.</p>\n<p>I ended up doing quite a bit of fiddling with my CSS to make these posts look good. You'll notice the grey background of the code block extends to the edges of the post, whereas normally there would be some padding. I also changed the font of the post name to a fixed-width font. If there is no filename, then I wanted the grey background to extend to the top of the frame, which is also something unique to these posts.</p>\n<img src=\"https://aaronparecki.com/2018/01/06/13/image-3.png\" alt=\"\" /><p>The last step of making this actually useful is to integrate this into my browser workflow, including editing the posts easily. There is a bookmarklet that will either open up a new window or launch the editing interface depending on whether I'm looking at an existing code post.</p>\n<p>I'm pretty happy with this, and I hope I don't post on GitHub anymore unless I'm specifically using their fork feature of Gists!</p>"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aaronparecki.com/images/profile.jpg"
},
"_id": "11663",
"_source": "16",
"_is_read": true
}
{
"type": "entry",
"published": "2018-01-06T14:35:09-08:00",
"url": "https://aaronparecki.com/2018/01/06/12/blog-archives",
"category": [
"indieweb",
"p3k"
],
"name": "Improved Blog Post Archives",
"content": {
"text": "I've been wanting to improve the layout of my blog post archive pages for some time. Previously, the page just listed out the full contents of the last 20 posts, and you could continue navigating back 20 posts at a time. I realize that some people like reading the full posts on the archive page, rather than having to click into each one, but it wasn't easy to just skim the post titles to get a sense of what was on the page.\nAs an intermediate step before launching a real archives view, I took Tantek's suggestion of adding a sort of \"table of contents\" view to my existing pages.\nNow on my \"articles\" page, there is a list at the top of the names of each post.\u00a0\nBelow that, I still show the full contents of each post. The table of contents also links to fragment IDs for each post on the page, so that you can quickly read the posts without doing full page loads.\nAs a bonus, this also works with my tag-filtered article pages, such as Articles Tagged #indieweb.\nI like this view since it makes it a little easier to find a lot of past content by topic rather than having to continue to page back 20 posts at a time.\nI'm still planning on improving the overall archive browsing on my site, but this was a relatively easy first step and is a good improvement.",
"html": "<p>I've been wanting to improve the layout of my blog post archive pages for some time. Previously, the page just listed out the full contents of the last 20 posts, and you could continue navigating back 20 posts at a time. I realize that some people like reading the full posts on the archive page, rather than having to click into each one, but it wasn't easy to just skim the post titles to get a sense of what was on the page.</p>\n<p>As an intermediate step before launching a real archives view, I took <a href=\"http://tantek.com\">Tantek</a>'s suggestion of adding a sort of \"table of contents\" view to my existing pages.</p>\n<p>Now on my \"<a href=\"https://aaronparecki.com/articles\">articles</a>\" page, there is a list at the top of the names of each post.\u00a0</p>\n<img src=\"https://aaronparecki.com/2018/01/06/12/image-1.png\" alt=\"\" /><p>Below that, I still show the full contents of each post. The table of contents also links to fragment IDs for each post on the page, so that you can quickly read the posts without doing full page loads.</p>\n<p>As a bonus, this also works with my tag-filtered article pages, such as <a href=\"https://aaronparecki.com/articles?tag=indieweb\">Articles Tagged #indieweb</a>.</p>\n<img src=\"https://aaronparecki.com/2018/01/06/12/image-2.png\" alt=\"\" /><p>I like this view since it makes it a little easier to find a lot of past content by topic rather than having to continue to page back 20 posts at a time.</p>\n<p>I'm still planning on improving the overall archive browsing on my site, but this was a relatively easy first step and is a good improvement.</p>"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aaronparecki.com/images/profile.jpg"
},
"_id": "11664",
"_source": "16",
"_is_read": true
}
{
"type": "entry",
"published": "2018-01-05T19:04:22Z",
"url": "https://adactio.com/links/13280",
"category": [
"indieweb",
"writing",
"publishing",
"blogging",
"data",
"ownership",
"content",
"syndication",
"sharing"
],
"bookmark-of": [
"https://timkadlec.com/2018/01/owning-my-own-content/"
],
"content": {
"text": "Owning My Own Content - TimKadlec.com\n\n \n\nHell, yeah! \n\n\n I write to understand and remember. Sometimes that will be interesting to others, often it won\u2019t be. \n \n But it\u2019s going to happen. Here, on my own site.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://timkadlec.com/2018/01/owning-my-own-content/\">\nOwning My Own Content - TimKadlec.com\n</a>\n</h3>\n\n<p>Hell, yeah!</p>\n\n<blockquote>\n <p>I write to understand and remember. Sometimes that will be interesting to others, often it won\u2019t be.</p>\n \n <p>But it\u2019s going to happen. Here, on my own site.</p>\n</blockquote>"
},
"_id": "11106",
"_source": "2",
"_is_read": true
}
gRegor Morrill
liked
a post
on singletary.io
