This is a great addition! I would have loved this feature when I was new to the IndieWeb, so I’m sure it will be useful to many people! I’ll add it to my Indigenous IndieAuth help page 🙂
{
"type": "entry",
"published": "2018-07-04T11:04:41-04:00",
"summary": "This is a great addition! I would have loved this feature when I was new to the IndieWeb, so I\u2019m sure it will be useful to many people! I\u2019ll add it to my Indigenous IndieAuth help page \ud83d\ude42",
"url": "https://eddiehinkle.com/2018/07/04/8/reply/",
"in-reply-to": [
"http://www.manton.org/2018/07/indieauth-for-external-blogs.html"
],
"content": {
"text": "This is a great addition! I would have loved this feature when I was new to the IndieWeb, so I\u2019m sure it will be useful to many people! I\u2019ll add it to my Indigenous IndieAuth help page \ud83d\ude42",
"html": "<p>This is a great addition! I would have loved this feature when I was new to the IndieWeb, so I\u2019m sure it will be useful to many people! I\u2019ll add it to my Indigenous IndieAuth help page \ud83d\ude42</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"refs": {
"http://www.manton.org/2018/07/indieauth-for-external-blogs.html": {
"type": "entry",
"url": "http://www.manton.org/2018/07/indieauth-for-external-blogs.html",
"name": "http://www.manton.org/2018/07/indieauth-for-external-blogs.html"
}
},
"_id": "534986",
"_source": "226",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "manton",
"url": "http://www.manton.org",
"photo": null
},
"url": "http://www.manton.org/2018/07/indieauth-for-external-blogs.html",
"name": "IndieAuth for external blogs",
"content": {
"html": "<p>Earlier this week I wrote about <a href=\"http://www.manton.org/2018/07/indieauth-for-micro-blog.html\">making Micro.blog an IndieAuth provider</a>. This allows anyone with a Micro.blog-hosted blog to sign in to IndieWeb-compatible apps. For example, using <a href=\"http://ownyourgram.com/\">OwnYourGram</a> to automatically copy Instagram photos to your own blog on Micro.blog.</p>\n<p>I\u2019ve now expanded this support to let anyone use Micro.blog to authorize an app even if your blog is hosted outside of Micro.blog. If you host somewhere else, you\u2019ll still be responsible for setting up posting, but having basic IndieAuth support can be useful if you want to connect your blog to tools that don\u2019t need to post, like <a href=\"https://xn--sr8hvo.ws/\">IndieWeb Ring</a> or the <a href=\"https://indieweb.org/\">IndieWeb.org</a> wiki.</p>\n<p>There are instructions <a href=\"http://help.micro.blog/2017/web-site-verification/\">on this Micro.blog help page</a> for adding the appropriate HTML tags to your site.</p>",
"text": "Earlier this week I wrote about making Micro.blog an IndieAuth provider. This allows anyone with a Micro.blog-hosted blog to sign in to IndieWeb-compatible apps. For example, using OwnYourGram to automatically copy Instagram photos to your own blog on Micro.blog.\nI\u2019ve now expanded this support to let anyone use Micro.blog to authorize an app even if your blog is hosted outside of Micro.blog. If you host somewhere else, you\u2019ll still be responsible for setting up posting, but having basic IndieAuth support can be useful if you want to connect your blog to tools that don\u2019t need to post, like IndieWeb Ring or the IndieWeb.org wiki.\nThere are instructions on this Micro.blog help page for adding the appropriate HTML tags to your site."
},
"published": "2018-07-04T13:21:54+00:00",
"updated": "2018-07-04T13:21:54+00:00",
"_id": "534056",
"_source": "12",
"_is_read": true
}
{
"type": "entry",
"published": "2018-07-03T08:33:38+0000",
"url": "http://known.kevinmarks.com/2018/the-truth-is-that-the-ability-to",
"category": [
"Indieweb"
],
"syndication": [
"https://twitter.com/kevinmarks/status/1014064616026955778"
],
"content": {
"text": "\u201cThe truth is that the ability to build Facebook-like services is relatively common. What was rare was the moral recklessness necessary to go through with it.\u201d @doctorow #Indieweb http://locusmag.com/2018/07/cory-doctorow-zucks-empire-of-oily-rags/",
"html": "\u201cThe truth is that the ability to build Facebook-like services is relatively common. What was rare was the moral recklessness necessary to go through with it.\u201d @doctorow <a href=\"http://known.kevinmarks.com/tag/Indieweb\" class=\"p-category\">#Indieweb</a> <a href=\"http://locusmag.com/2018/07/cory-doctorow-zucks-empire-of-oily-rags/\">http://locusmag.com/2018/07/cory-doctorow-zucks-empire-of-oily-rags/</a>"
},
"author": {
"type": "card",
"name": "Kevin Marks",
"url": "http://known.kevinmarks.com/profile/kevinmarks",
"photo": "https://aperture-proxy.p3k.io/ed7979fd10a648fc253eae0b54e66fb36e57d3d4/687474703a2f2f6b6e6f776e2e6b6576696e6d61726b732e636f6d2f66696c652f3932353536353636363931373362373836376162383339656536353536663965"
},
"_id": "522573",
"_source": "205",
"_is_read": true
}
Are we headed toward an Orwellian future where a handful of corporations monitor and control our lives? Or are we on the verge of creating a better version of society online, one where the free flow of ideas and information helps cure disease, expose corruption, reverse injustices?
It’s hard to believe that anyone—even Zuckerberg—wants the 1984 version. He didn’t found Facebook to manipulate elections; Jack Dorsey and the other Twitter founders didn’t intend to give Donald Trump a digital bullhorn. And this is what makes Berners-Lee believe that this battle over our digital future can be won. As public outrage grows over the centralization of the Web, and as enlarging numbers of coders join the effort to decentralize it, he has visions of the rest of us rising up and joining him.
{
"type": "entry",
"published": "2018-07-03T08:10:52Z",
"url": "https://adactio.com/links/14076",
"category": [
"timbernerslee",
"indieweb",
"decentralisation",
"solid",
"facebook",
"google",
"twitter",
"open",
"surveillance",
"privacy",
"rights",
"empowerment"
],
"bookmark-of": [
"https://www.vanityfair.com/news/2018/07/the-man-who-created-the-world-wide-web-has-some-regrets"
],
"content": {
"text": "\u201cI Was Devastated\u201d: Tim Berners-Lee, the Man Who Created the World Wide Web, Has Some Regrets | Vanity Fair\n\n\n\n\n Are we headed toward an Orwellian future where a handful of corporations monitor and control our lives? Or are we on the verge of creating a better version of society online, one where the free flow of ideas and information helps cure disease, expose corruption, reverse injustices?\n \n It\u2019s hard to believe that anyone\u2014even Zuckerberg\u2014wants the 1984 version. He didn\u2019t found Facebook to manipulate elections; Jack Dorsey and the other Twitter founders didn\u2019t intend to give Donald Trump a digital bullhorn. And this is what makes Berners-Lee believe that this battle over our digital future can be won. As public outrage grows over the centralization of the Web, and as enlarging numbers of coders join the effort to decentralize it, he has visions of the rest of us rising up and joining him.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://www.vanityfair.com/news/2018/07/the-man-who-created-the-world-wide-web-has-some-regrets\">\n\u201cI Was Devastated\u201d: Tim Berners-Lee, the Man Who Created the World Wide Web, Has Some Regrets | Vanity Fair\n</a>\n</h3>\n\n<blockquote>\n <p>Are we headed toward an Orwellian future where a handful of corporations monitor and control our lives? Or are we on the verge of creating a better version of society online, one where the free flow of ideas and information helps cure disease, expose corruption, reverse injustices?</p>\n \n <p>It\u2019s hard to believe that anyone\u2014even Zuckerberg\u2014wants the 1984 version. He didn\u2019t found Facebook to manipulate elections; Jack Dorsey and the other Twitter founders didn\u2019t intend to give Donald Trump a digital bullhorn. And this is what makes Berners-Lee believe that this battle over our digital future can be won. As public outrage grows over the centralization of the Web, and as enlarging numbers of coders join the effort to decentralize it, he has visions of the rest of us rising up and joining him.</p>\n</blockquote>"
},
"_id": "522530",
"_source": "2",
"_is_read": true
}
{
"type": "entry",
"published": "2018-07-02T23:37:58-04:00",
"url": "https://martymcgui.re/2018/07/02/233758/",
"category": [
"podcast",
"IndieWeb",
"this-week-indieweb-podcast"
],
"audio": [
"https://aperture-proxy.p3k.io/8816c4840cf53ae67549a55dc848463ecc0f9017/68747470733a2f2f6d656469612e6d617274796d636775692e72652f39642f38622f32612f33392f33653064653431383837353934653434663663646232626339623133666431306631366139356265363038363034386131633932333937632e6d7033"
],
"syndication": [
"https://huffduffer.com/schmarty/489991",
"https://twitter.com/schmarty/status/1013991968245014528",
"https://www.facebook.com/marty.mcguire.54/posts/10212359351440858"
],
"name": "This Week in the IndieWeb Audio Edition \u2022 June 23rd - 29th, 2018",
"content": {
"text": "Show/Hide Transcript \n \n Recaps from the 8th annual IndieWeb Summit, Indigenous and Aperture open to the public, and announcing IndieWebCamp Berlin 2018. It\u2019s the audio edition for This Week in the IndieWeb for June 23rd - 29th, 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>Recaps from the 8th annual IndieWeb Summit, Indigenous and Aperture open to the public, and announcing IndieWebCamp Berlin 2018. It\u2019s the audio edition for <a href=\"https://indieweb.org/this-week/2018-06-29.html\">This Week in the IndieWeb for June 23rd - 29th, 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://aperture-proxy.p3k.io/8275f85e3a389bd0ae69f209683436fc53d8bad9/68747470733a2f2f6d617274796d636775692e72652f696d616765732f6c6f676f2e6a7067"
},
"_id": "520925",
"_source": "175",
"_is_read": true
}
{
"type": "entry",
"published": "2018-07-03T04:39:29+00:00",
"url": "https://cleverdevil.io/2018/i-whipped-up-a-quick-plugin-for",
"category": [
"OwnYourIssues",
"IndieWeb"
],
"syndication": [
"https://twitter.com/cleverdevil/status/1014005695514075136"
],
"content": {
"text": "I whipped up a quick plugin for @WithKnown to publish GitHub issues and comments on your own site, with automatic syndication to GitHub via Bridgy \u2013\u00a0https://github.com/cleverdevil/Known-GitHub #OwnYourIssues #IndieWeb",
"html": "I whipped up a quick plugin for @WithKnown to publish GitHub issues and comments on your own site, with automatic syndication to GitHub via Bridgy \u2013\u00a0<a href=\"https://github.com/cleverdevil/Known-GitHub\">https://github.com/cleverdevil/Known-GitHub</a> <a href=\"https://cleverdevil.io/tag/OwnYourIssues\" class=\"p-category\">#OwnYourIssues</a> <a href=\"https://cleverdevil.io/tag/IndieWeb\" class=\"p-category\">#IndieWeb</a>"
},
"author": {
"type": "card",
"name": "Jonathan LaCour",
"url": "https://cleverdevil.io/profile/cleverdevil",
"photo": "https://aperture-proxy.p3k.io/77e5d6e5871324c43aebf2e3e7a5553e14578f66/68747470733a2f2f636c65766572646576696c2e696f2f66696c652f66646263373639366135663733383634656131316138323863383631653133382f7468756d622e6a7067"
},
"_id": "520808",
"_source": "71",
"_is_read": true
}
After we do this manually, it we would be good to brainstorm how we could potentially make the configuration discoverable from the user's website or microsub server, or both.
{
"type": "entry",
"published": "2018-07-03T03:32:14+00:00",
"url": "https://cleverdevil.io/2018/after-we-do-this-manually-it-we-would-be-good",
"in-reply-to": [
"https://github.com/cleverdevil/together/issues/70"
],
"content": {
"text": "After we do this manually, it we would be good to brainstorm how we could potentially make the configuration discoverable from the user's website or microsub server, or both.",
"html": "<p>After we do this manually, it we would be good to brainstorm how we could potentially make the configuration discoverable from the user's website or microsub server, or both.</p>"
},
"author": {
"type": "card",
"name": "Jonathan LaCour",
"url": "https://cleverdevil.io/profile/cleverdevil",
"photo": "https://aperture-proxy.p3k.io/77e5d6e5871324c43aebf2e3e7a5553e14578f66/68747470733a2f2f636c65766572646576696c2e696f2f66696c652f66646263373639366135663733383634656131316138323863383631653133382f7468756d622e6a7067"
},
"_id": "520274",
"_source": "71",
"_is_read": true
}
@jameshull We should be getting back to a more regular schedule for the LA area Homebrew Website Club soon if you're interested in some of this stuff: https://indieweb.org/next-hwc
{
"type": "entry",
"published": "2018-07-03T01:14:06+00:00",
"url": "http://stream.boffosocko.com/2018/jameshull-we-should-be-getting-back-to-a-more-regular",
"syndication": [
"https://twitter.com/ChrisAldrich/status/1013954011689562112"
],
"in-reply-to": [
"https://twitter.com/jameshull/status/1013628846426517504"
],
"content": {
"text": "@jameshull We should be getting back to a more regular schedule for the LA area Homebrew Website Club soon if you're interested in some of this stuff: https://indieweb.org/next-hwc",
"html": "<a href=\"https://twitter.com/jameshull\">@jameshull</a> We should be getting back to a more regular schedule for the LA area Homebrew Website Club soon if you're interested in some of this stuff: <a href=\"https://indieweb.org/next-hwc\">https://indieweb.org/next-hwc</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "https://aperture-proxy.p3k.io/4a01a54aa55b69dd1b2633c835610491c575e2e2/687474703a2f2f73747265616d2e626f66666f736f636b6f2e636f6d2f66696c652f36303034323762383166373738356537303465616466653531316139323730662f7468756d622e6a7067"
},
"_id": "519346",
"_source": "192",
"_is_read": true
}
I wonder what happened with the maker community. Hackaday seems to link mostly to YouTube and Instructables. Top notch work is still posted there and all around us (and at /r/diy.) It just seems that the will to “make” your web has left this crowd.
I guess this brings us to the Indieweb where you can probably still call each other Netizens and bemoan the death of RSS. Even though it’s been around since 2013, I see a spark of hope in this ragtag group of HTMLists.
{
"type": "entry",
"author": {
"name": "Kh\u00fcrt Williams",
"url": "https://islandinthenet.com/",
"photo": null
},
"url": "https://islandinthenet.com/40308-2/",
"published": "2018-07-03T01:14:53+00:00",
"content": {
"html": "Read <a href=\"https://www.kickscondor.com/2018/07/02/things-we-left-in-the-old-web/\">Things We Left in the Old Web</a> <em>(kickscondor.com)</em>\n<blockquote><p>I wonder what happened with the maker community. Hackaday seems to link mostly to YouTube and Instructables. Top notch work is still posted there and all around us (and at /r/diy.) It just seems that the will to \u201cmake\u201d your web has left this crowd.</p>\n<p>I guess this brings us to the Indieweb where you can probably still call each other Netizens and bemoan the death of RSS. Even though it\u2019s been around since 2013, I see a spark of hope in this ragtag group of HTMLists. </p></blockquote>",
"text": "Read Things We Left in the Old Web (kickscondor.com)\nI wonder what happened with the maker community. Hackaday seems to link mostly to YouTube and Instructables. Top notch work is still posted there and all around us (and at /r/diy.) It just seems that the will to \u201cmake\u201d your web has left this crowd.\nI guess this brings us to the Indieweb where you can probably still call each other Netizens and bemoan the death of RSS. Even though it\u2019s been around since 2013, I see a spark of hope in this ragtag group of HTMLists."
},
"_id": "519167",
"_source": "242",
"_is_read": true
}
I don’t currently have plans to link the posts that appear on indiebookclub to a third-party service like Amazon or GoodReads. However, since the ISBN is sent in the micropub request to your site, plugin/theme developers could use that information to link the posts on their site to a third-party service.
I have made some improvements during the IndieWeb Summit which I will write more about soon. It’s now easier to make bookmarklets to pre-populate the new post form. This should allow developers to create few-click options for adding books without typing anything. It also makes it easier if you see someone else’s read post and want to quickly add it to your list.
{
"type": "entry",
"published": "2018-07-02 10:49-0700",
"url": "https://gregorlove.com/2018/07/thanks-serena-im-glad-youre/",
"in-reply-to": [
"https://www.serenawho.com/2018/07/01/7004/"
],
"content": {
"text": "Thanks, Serena. I\u2019m glad you\u2019re enjoying it!\n\nI don\u2019t currently have plans to link the posts that appear on indiebookclub to a third-party service like Amazon or GoodReads. However, since the ISBN is sent in the micropub request to your site, plugin/theme developers could use that information to link the posts on their site to a third-party service.\n\nI have made some improvements during the IndieWeb Summit which I will write more about soon. It\u2019s now easier to make bookmarklets to pre-populate the new post form. This should allow developers to create few-click options for adding books without typing anything. It also makes it easier if you see someone else\u2019s read post and want to quickly add it to your list.",
"html": "<p>Thanks, Serena. I\u2019m glad you\u2019re enjoying it!\n</p>\n<p>I don\u2019t currently have plans to link the posts that appear <em>on</em> indiebookclub to a third-party service like Amazon or GoodReads. However, since the ISBN is sent in the micropub request to your site, plugin/theme developers could use that information to link the posts on their site to a third-party service.\n</p>\n<p>I have made some improvements during the IndieWeb Summit which I will write more about soon. It\u2019s now easier to make bookmarklets to pre-populate the new post form. This should allow developers to create few-click options for adding books without typing anything. It also makes it easier if you see someone else\u2019s read post and want to quickly add it to your list.</p>"
},
"author": {
"type": "card",
"name": "gRegor Morrill",
"url": "https://gregorlove.com/",
"photo": "https://aperture-proxy.p3k.io/929c8777d059069a2a16a064d96f4c29b65548f8/68747470733a2f2f677265676f726c6f76652e636f6d2f736974652f6173736574732f66696c65732f333437332f70726f66696c652d323031362d6d65642e6a7067"
},
"refs": {
"https://www.serenawho.com/2018/07/01/7004/": {
"type": "entry",
"url": "https://www.serenawho.com/2018/07/01/7004/",
"content": {
"text": "Replied to Announcing indiebookclub by gRegor Morrill (gregorlove.com)I really enjoy indiebookclub, but I have a few questions directly in response to your post: Can indiebookclub posts be syndicated to GoodReads? Can the ISBN link to the GoodReads page for the book? As a future feature, would you consider having indiebookclub extract book information from the ISBN (through Amazon or GoodReads), such as book title, author and book cover image?"
},
"author": {
"type": "card",
"name": "Serena",
"url": "https://www.serenawho.com/",
"photo": "https://gregorlove.com/notes/"
}
}
},
"_id": "518386",
"_source": "95",
"_is_read": true
}
{
"type": "entry",
"published": "2018-07-02T16:41:47-04:00",
"summary": "So achieved my goal of release version 1.0 of Indigenous in the iOS App Store before the end of June!",
"url": "https://eddiehinkle.com/2018/07/02/18/article/",
"category": [
"indigenous",
"indigenous-log",
"development-log",
"tech",
"personal",
"micropub",
"microsub",
"indieauth"
],
"name": "Indigenous v1.0 is in the App Store! (Indigenous Development Log #3)",
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"_id": "518290",
"_source": "226",
"_is_read": true
}
{
"type": "entry",
"published": "2018-07-02T21:12:26+00:00",
"url": "https://cleverdevil.io/2018/add-native-support-for-indiepaper",
"in-reply-to": [
"https://cleverdevil.io/"
],
"name": "Add native support for Indiepaper",
"content": {
"text": "Regarding TogetherNow that I've launched Indiepaper, I'd love to see Together\u00a0add native support for sending articles to Indiepaper with the click of a button. This would require a few configuration settings, including the configuration of a bearer token and a target micropub destination.",
"html": "<p><a class=\"u-in-reply-to\" href=\"https://cleverdevil.io/\">Regarding Together</a></p><p>Now that I've launched <a href=\"https://indiepaper.cleverdevil.io\">Indiepaper</a>, I'd love to see Together\u00a0add native support for sending articles to Indiepaper with the click of a button. This would require a few configuration settings, including the configuration of a bearer token and a target micropub destination.</p>"
},
"author": {
"type": "card",
"name": "Jonathan LaCour",
"url": "https://cleverdevil.io/profile/cleverdevil",
"photo": "https://aperture-proxy.p3k.io/77e5d6e5871324c43aebf2e3e7a5553e14578f66/68747470733a2f2f636c65766572646576696c2e696f2f66696c652f66646263373639366135663733383634656131316138323863383631653133382f7468756d622e6a7067"
},
"_id": "518162",
"_source": "71",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "manton",
"url": "http://www.manton.org",
"photo": null
},
"url": "http://www.manton.org/2018/07/the-web-is-the-social-network.html",
"name": "The web is the social network",
"content": {
"html": "<p>In my talk at Peers Conference earlier this year I closed with this quote from Brent Simmons:</p>\n<blockquote><p>\n Micro.blog is not an alternative silo: instead, it\u2019s what you build when you believe that <em>the web itself</em> is the great social network.\n</p></blockquote>\n<p>I\u2019ve been thinking more about Brent\u2019s post since then, and so for the keynote that Jean and I gave at <a href=\"http://www.manton.org/2018/06/indieweb-summit-2018-wrap-up.html\">IndieWeb Summit last week</a> I wanted to start with that quote. Many people have written nice testimonials about Micro.blog, but this one really seems to capture the goal.</p>\n<p>It should come as no surprise that I liked <a href=\"http://inessential.com/2018/02/01/why_micro_blog_is_not_another_app_net\">Brent\u2019s full post from February about why Micro.blog isn\u2019t like App.net</a>. He made the case even better than I usually do, about how the web is more important than any one platform:</p>\n<blockquote><p>\n But if you think of the years 1995-2005, you remember when the web was our social network: blogs, comments on blogs, feed readers, and services such as Flickr, Technorati, and BlogBridge to glue things together. Those were great years \u2014 but then a few tragedies happened: Google Reader came out, and then, almost <em>worse</em>, it went away. Worse still was the rise of Twitter and Facebook, when we decided it would be okay to give up ownership and let just a couple companies own our communication.\n</p></blockquote>\n<p>Micro.blog is one of the first platforms to focus on domain names that decouple the timeline from post storage. Anyone can post a Micro.blog-hosted site at their own domain name today and move it all somewhere else tomorrow. It\u2019s a simple, IndieWeb-friendly architecture that we think is essential to the next phase of the web.</p>",
"text": "In my talk at Peers Conference earlier this year I closed with this quote from Brent Simmons:\n\n Micro.blog is not an alternative silo: instead, it\u2019s what you build when you believe that the web itself is the great social network.\n\nI\u2019ve been thinking more about Brent\u2019s post since then, and so for the keynote that Jean and I gave at IndieWeb Summit last week I wanted to start with that quote. Many people have written nice testimonials about Micro.blog, but this one really seems to capture the goal.\nIt should come as no surprise that I liked Brent\u2019s full post from February about why Micro.blog isn\u2019t like App.net. He made the case even better than I usually do, about how the web is more important than any one platform:\n\n But if you think of the years 1995-2005, you remember when the web was our social network: blogs, comments on blogs, feed readers, and services such as Flickr, Technorati, and BlogBridge to glue things together. Those were great years \u2014 but then a few tragedies happened: Google Reader came out, and then, almost worse, it went away. Worse still was the rise of Twitter and Facebook, when we decided it would be okay to give up ownership and let just a couple companies own our communication.\n\nMicro.blog is one of the first platforms to focus on domain names that decouple the timeline from post storage. Anyone can post a Micro.blog-hosted site at their own domain name today and move it all somewhere else tomorrow. It\u2019s a simple, IndieWeb-friendly architecture that we think is essential to the next phase of the web."
},
"published": "2018-07-02T19:37:38+00:00",
"updated": "2018-07-02T19:37:38+00:00",
"_id": "517830",
"_source": "12",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "manton",
"url": "http://www.manton.org",
"photo": null
},
"url": "http://www.manton.org/2018/07/indieauth-for-micro-blog.html",
"name": "IndieAuth for Micro.blog",
"content": {
"html": "<p>After posting about <a href=\"http://www.manton.org/2018/06/indieweb-summit-2018-wrap-up.html\">my time at IndieWeb Summit</a> and <a href=\"http://www.manton.org/2018/06/indiebookclub.html\">the new IndieBookClub support</a>, let me give some more details on what IndieAuth means for Micro.blog. I spent the second day of IndieWeb Summit working on this, and it has now been rolled out to all Micro.blog users. (If you haven\u2019t posted in the last few days, after your next post your microblog will be updated with the new authorization endpoints.)</p>\n<p>IndieAuth lets you sign in to other apps using your own domain name. If Micro.blog is hosting a blog for you, you can use that custom domain or your subdomain like yourname.micro.blog to sign in.</p>\n<p>While this was possible before with extra configuration to delegate auth to another service, Micro.blog can now be an IndieAuth provider on its own. It\u2019s much easier for IndieWeb apps to work with Micro.blog.</p>\n<p>Here are some apps that work great with Micro.blog:</p>\n<ul><li><a href=\"https://quill.p3k.io/\">Quill</a>: web-based interface for posting to your microblog.</li>\n<li><a href=\"https://ownyourgram.com/\">OwnYourGram</a>: automatically post your Instagram photos to your microblog.</li>\n<li><a href=\"https://ownyourswarm.p3k.io/\">OwnYourSwarm</a>: automatically post your Swarm check-ins to your microblog.</li>\n<li><a href=\"https://indiebookclub.biz/\">IndieBookClub</a>: post what books you\u2019re reading or want to read.</li>\n<li><a href=\"https://omnibear.com/\">Omnibear</a>: Chrome or Firefox extension for quick posting.</li>\n<li><a>IndieWeb Ring</a>: wait\u2026 <a href=\"http://help.micro.blog/2018/web-rings/\">what?</a></li>\n</ul><p>I\u2019m really happy with the progress over the last week because it makes Micro.blog-hosted sites more useful. As I mentioned in my IndieWeb Summit keynote, the business model for Micro.blog is aligned with what users need. If you pay for Micro.blog hosting, we\u2019ll keep making it better without worrying about ads or other user-hostile distractions.</p>",
"text": "After posting about my time at IndieWeb Summit and the new IndieBookClub support, let me give some more details on what IndieAuth means for Micro.blog. I spent the second day of IndieWeb Summit working on this, and it has now been rolled out to all Micro.blog users. (If you haven\u2019t posted in the last few days, after your next post your microblog will be updated with the new authorization endpoints.)\nIndieAuth lets you sign in to other apps using your own domain name. If Micro.blog is hosting a blog for you, you can use that custom domain or your subdomain like yourname.micro.blog to sign in.\nWhile this was possible before with extra configuration to delegate auth to another service, Micro.blog can now be an IndieAuth provider on its own. It\u2019s much easier for IndieWeb apps to work with Micro.blog.\nHere are some apps that work great with Micro.blog:\nQuill: web-based interface for posting to your microblog.\nOwnYourGram: automatically post your Instagram photos to your microblog.\nOwnYourSwarm: automatically post your Swarm check-ins to your microblog.\nIndieBookClub: post what books you\u2019re reading or want to read.\nOmnibear: Chrome or Firefox extension for quick posting.\nIndieWeb Ring: wait\u2026 what?\nI\u2019m really happy with the progress over the last week because it makes Micro.blog-hosted sites more useful. As I mentioned in my IndieWeb Summit keynote, the business model for Micro.blog is aligned with what users need. If you pay for Micro.blog hosting, we\u2019ll keep making it better without worrying about ads or other user-hostile distractions."
},
"published": "2018-07-02T13:24:37+00:00",
"updated": "2018-07-02T13:24:37+00:00",
"_id": "515644",
"_source": "12",
"_is_read": true
}
Very interesting! This is timely considering all the reader stuff is taking off. It would make it a lot easier to post follow posts if the readers (which already send Micropub posts) created them when we started following a new feed (with our permission, of course). Looking forward to following and speaking into the development of this!
{
"type": "entry",
"published": "2018-07-02T00:51:25-04:00",
"summary": "Very interesting! This is timely considering all the reader stuff is taking off. It would make it a lot easier to post follow posts if the readers (which already send Micropub posts) created them when we started following a new feed (with our permission, of course). Looking forward to following and speaking into the development of this!",
"url": "https://eddiehinkle.com/2018/07/02/4/reply/",
"in-reply-to": [
"https://david.shanske.com/2018/07/01/brainstorming-on-implementing-vouch-following-and-blogrolls/"
],
"content": {
"text": "Very interesting! This is timely considering all the reader stuff is taking off. It would make it a lot easier to post follow posts if the readers (which already send Micropub posts) created them when we started following a new feed (with our permission, of course). Looking forward to following and speaking into the development of this!",
"html": "<p>Very interesting! This is timely considering all the reader stuff is taking off. It would make it a lot easier to post follow posts if the readers (which already send Micropub posts) created them when we started following a new feed (with our permission, of course). Looking forward to following and speaking into the development of this!</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"refs": {
"https://david.shanske.com/2018/07/01/brainstorming-on-implementing-vouch-following-and-blogrolls/": {
"type": "entry",
"url": "https://david.shanske.com/2018/07/01/brainstorming-on-implementing-vouch-following-and-blogrolls/",
"name": "https://david.shanske.com/2018/07/01/brainstorming-on-implementing-vouch-following-and-blogrolls/"
}
},
"_id": "513230",
"_source": "226",
"_is_read": true
}
{
"type": "entry",
"published": "2018-07-02T00:35:39-04:00",
"summary": "Once you get it set up, there is also a Microsub client on iOS (I made it): Indigenous",
"url": "https://eddiehinkle.com/2018/07/02/3/reply/",
"in-reply-to": [
"https://jhull.micro.blog/2018/07/01/oh-no-i.html"
],
"content": {
"text": "Once you get it set up, there is also a Microsub client on iOS (I made it): Indigenous",
"html": "<p>Once you get it set up, there is also a Microsub client on iOS (I made it): <a href=\"https://itunes.apple.com/us/app/indigenous-social-timeline/id1271004584?mt=8\">Indigenous</a></p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"refs": {
"https://jhull.micro.blog/2018/07/01/oh-no-i.html": {
"type": "entry",
"url": "https://jhull.micro.blog/2018/07/01/oh-no-i.html",
"name": "https://jhull.micro.blog/2018/07/01/oh-no-i.html"
}
},
"_id": "513231",
"_source": "226",
"_is_read": true
}
Do you use a hosted-Micro.blog? Unfortunately, I think the challenge is you have to add a Microsub link to the header Hosted-micro.blog’s, which doesn’t have built in support yet I don’t think.
{
"type": "entry",
"published": "2018-07-02T00:31:33-04:00",
"summary": "Do you use a hosted-Micro.blog? Unfortunately, I think the challenge is you have to add a Microsub link to the header Hosted-micro.blog\u2019s, which doesn\u2019t have built in support yet I don\u2019t think.",
"url": "https://eddiehinkle.com/2018/07/02/2/reply/",
"in-reply-to": [
"https://twitter.com/jameshull/status/1013639132923551744"
],
"content": {
"text": "Do you use a hosted-Micro.blog? Unfortunately, I think the challenge is you have to add a Microsub link to the header Hosted-micro.blog\u2019s, which doesn\u2019t have built in support yet I don\u2019t think.",
"html": "<p>Do you use a hosted-Micro.blog? Unfortunately, I think the challenge is you have to add a Microsub link to the header Hosted-micro.blog\u2019s, which doesn\u2019t have built in support yet I don\u2019t think.</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"refs": {
"https://twitter.com/jameshull/status/1013639132923551744": {
"type": "entry",
"url": "https://twitter.com/jameshull/status/1013639132923551744",
"name": "https://twitter.com/jameshull/status/1013639132923551744"
}
},
"_id": "513232",
"_source": "226",
"_is_read": true
}
{
"type": "entry",
"published": "2018-07-01T18:23:12-04:00",
"url": "https://david.shanske.com/2018/07/01/brainstorming-on-implementing-vouch-following-and-blogrolls/",
"syndication": [
"https://twitter.com/dshanske/status/1013548707453730817"
],
"name": "Brainstorming on Implementing Vouch, Following and Blogrolls",
"content": {
"text": "Vouch is an extension to the webmention protocol. Webmentions usually have two parameters\u2026source and target. Target is the URL on your website\u00a0 that the Source URL is linking to.\nThe vouch parameter is a third URL to help the target determine whether or not they should accept the webmention. This should block automated spam and aid in moderation.\nSeveral people have implemented receiving vouches. It is relatively easy\u00a0 to look at a vouch URL and see if it links to a third-party who you have approved of in the past.\u00a0 While there are more advanced things you can do, that is the basic summary of the protocol.\nThe harder part, and less implemented by others is sending of vouches. Where do you find people who have been approved by people you have approved of? It would really help if we had some more discussion on this.\nSo, at the Indieweb Summit, we talked about this a bit, after which I implemented a primitive Vouch receiver. My solution was to use a manually curated domain whitelist that I\u2019d previously built as my source for acceptable domains.\nThere are some suggestions on where to get this list. Several people generate a list from referrers. This sent me down the road of looking as to whether I\u2019d want to implement refbacks to add more mentions to my website\u2026except there is a lot of noise. Refbacks are basically the same as webmentions, except the source is gleaned from the\u00a0 referrer header that sites send when a page is accessed.\nEven if I\u00a0 have a list of sites that I approve of, I would have to crawl them to find links from them to other sites. So, I think we should all help each other out on this.\nThat means we need to post our list of approved domains somewhere on our site. That used to be quite popular. It was called a Blogroll. It was sites you read, followed, or recommended. There are other terms for it. But, this is a perfect place to get a nice list, and if we publish them, then we can help the Vouch cause.\nBut the problem is, how do you tell a Vouch receiver where your list is. There are some brainstorming items about blogrolls and following/follower lists\nFollower lists marked up with rel=\u201dfollower\u201d or rel=\u201dfollowing\u201d\nContact lists marked up with rel=\u201dcontact\u201d\n\nFollow Posts marked up with u-follow-of\nFollow posts would create an h-feed of follow posts that could be used to generate a list. You can have a specific page on your website, but there isn\u2019t a way to indicate this to someone looking for it.\nThere is rel-directory, which is the reverse direction. It indicates that the link is to a directory in which the current page is listed. What we seem to be missing is a property that says that a page is a feed of followers that can be placed inside an h-card or on a home page.\nu-follow-of is a proposed property that indicates that an h-entry is considered a follow post, which is a post indicating you have followed someone, then a feed of follow posts could be parsed and read by a reader. If you add in the XFN relationships to that, you can build even more detail.\nThe reverse relationship would, in theory, be u-follow, which would be a URL to the follow post of the current URL(the thing being followed).\nFeeds are identicated by rel=\u201dfeed\u201d to link from your homepage to those feeds. But there is a lack of indicating what type of feed it is, such as rel=\u201dblogroll\u201d or rel=\u201dfollowing\u201d.\u00a0 I\u2019m not sure, and need more discussion about what to use for this.\nBut, this has the ability to solve a lot of problems. Imagine I\u2026\nPost Follow posts when I follow someone\nUse this to generate a blogroll/followers list\nSend webmentions when I follow someone so they can build relationships\nUse that list as a vouch list. Use other people\u2019s blogrolls/followers lists as a means to generate vouch lists\u2026which reduces the implementation cost of Vouch.\nNeeds work, but suddenly I want to do Follow posts.",
"html": "<a href=\"https://indieweb.org/Vouch\">Vouch</a> is an extension to the webmention protocol. Webmentions usually have two parameters\u2026source and target. Target is the URL on your website\u00a0 that the Source URL is linking to.\n<p>The vouch parameter is a third URL to help the target determine whether or not they should accept the webmention. This should block automated spam and aid in moderation.</p>\n<p>Several people have implemented receiving vouches. It is relatively easy\u00a0 to look at a vouch URL and see if it links to a third-party who you have approved of in the past.\u00a0 While there are more advanced things you can do, that is the basic summary of the protocol.</p>\n<p>The harder part, and less implemented by others is sending of vouches. Where do you find people who have been approved by people you have approved of? It would really help if we had some more discussion on this.</p>\n<p>So, at the Indieweb Summit, we <a href=\"https://indieweb.org/2018/vouch\">talked</a> about this a bit, after which I implemented a primitive Vouch receiver. My solution was to use a manually curated domain whitelist that I\u2019d previously built as my source for acceptable domains.</p>\n<p>There are some suggestions on where to get this list. Several people generate a list from referrers. This sent me down the road of looking as to whether I\u2019d want to implement refbacks to add more mentions to my website\u2026except there is a lot of noise. <a href=\"https://indieweb.org/refback\">Refbacks</a> are basically the same as webmentions, except the source is gleaned from the\u00a0 referrer header that sites send when a page is accessed.</p>\n<p>Even if I\u00a0 have a list of sites that I approve of, I would have to crawl them to find links from them to other sites. So, I think we should all help each other out on this.</p>\n<p>That means we need to post our list of approved domains somewhere on our site. That used to be quite popular. It was <a href=\"https://indieweb.org/blogroll\">called</a> a Blogroll. It was sites you read, followed, or recommended. There are other terms for it. But, this is a perfect place to get a nice list, and if we publish them, then we can help the Vouch cause.</p>\n<p>But the problem is, how do you tell a Vouch receiver where your list is. There are some brainstorming items about blogrolls and following/follower lists</p>\n<ul><li>Follower lists marked up with rel=\u201dfollower\u201d or rel=\u201dfollowing\u201d</li>\n<li>Contact lists marked up with rel=\u201dcontact\u201d</li>\n<li>\n<a href=\"https://indieweb.org/follow\">Follow</a> Posts marked up with u-follow-of</li>\n</ul><p>Follow posts would create an h-feed of follow posts that could be used to generate a list. You can have a specific page on your website, but there isn\u2019t a way to indicate this to someone looking for it.</p>\n<p>There is rel-directory, which is the reverse direction. It indicates that the link is to a directory in which the current page is listed. What we seem to be missing is a property that says that a page is a feed of followers that can be placed inside an h-card or on a home page.</p>\n<p>u-follow-of is a proposed property that indicates that an h-entry is considered a follow post, which is a post indicating you have followed someone, then a feed of follow posts could be parsed and read by a reader. If you add in the <a href=\"https://indieweb.org/XFN\">XFN</a> relationships to that, you can build even more detail.</p>\n<p>The reverse relationship would, in theory, be u-follow, which would be a URL to the follow post of the current URL(the thing being followed).</p>\n<p>Feeds are identicated by rel=\u201dfeed\u201d to link from your homepage to those feeds. But there is a lack of indicating what type of feed it is, such as rel=\u201dblogroll\u201d or rel=\u201dfollowing\u201d.\u00a0 I\u2019m not sure, and need more discussion about what to use for this.</p>\n<p>But, this has the ability to solve a lot of problems. Imagine I\u2026</p>\n<ul><li>Post Follow posts when I follow someone</li>\n<li>Use this to generate a blogroll/followers list</li>\n<li>Send webmentions when I follow someone so they can build relationships</li>\n<li>Use that list as a vouch list. Use other people\u2019s blogrolls/followers lists as a means to generate vouch lists\u2026which reduces the implementation cost of Vouch.</li>\n</ul><p>Needs work, but suddenly I want to do Follow posts.</p>"
},
"author": {
"type": "card",
"name": "David Shanske",
"url": "https://david.shanske.com/",
"photo": "https://aperture-proxy.p3k.io/6f1f841c095626a5e52a3b86849e757329773a28/68747470733a2f2f64617669642e7368616e736b652e636f6d2f77702d636f6e74656e742f75706c6f6164732f6176617461722d707269766163792f63616368652f67726176617461722f322f632f326362316638616664396338643362363436623430373163356564383837633937306438316436323565656564383765343437373036393430653263343033642d3132352e706e67"
},
"_id": "512397",
"_source": "5",
"_is_read": true
}
Indigenous v1.0.3 has been approved and should be on the App Store soon. It has new on-boarding screens when you’re not logged in, updated compatibility with micro.blog’s IndieAuth, as well as bug fixes. A new Indigenous Development Log blog post is coming soon.
{
"type": "entry",
"published": "2018-07-01T21:03:28-04:00",
"summary": "Indigenous v1.0.3 has been approved and should be on the App Store soon. It has new on-boarding screens when you\u2019re not logged in, updated compatibility with micro.blog\u2019s IndieAuth, as well as bug fixes. A new Indigenous Development Log blog post is coming soon.",
"url": "https://eddiehinkle.com/2018/07/01/21/note/",
"category": [
"indigenous",
"tech"
],
"content": {
"text": "Indigenous v1.0.3 has been approved and should be on the App Store soon. It has new on-boarding screens when you\u2019re not logged in, updated compatibility with micro.blog\u2019s IndieAuth, as well as bug fixes. A new Indigenous Development Log blog post is coming soon.",
"html": "<p><a href=\"https://itunes.apple.com/us/app/indigenous-social-timeline/id1271004584?mt=8\">Indigenous</a> v1.0.3 has been approved and should be on the App Store soon. It has new on-boarding screens when you\u2019re not logged in, updated compatibility with micro.blog\u2019s IndieAuth, as well as bug fixes. A new Indigenous Development Log blog post is coming soon.</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"_id": "512130",
"_source": "226",
"_is_read": true
}
