Also, micro.blog with Monocle is a little bit more complicated because Monocle is Microsub (reading API) plus Micropub (posting API). Micro.blog currently supports a subset of Micropub (intentionally), and Microsub is still so new, that while I think there are eventual plans to add support, it’ll probably be a little while.
{
"type": "entry",
"published": "2018-03-25T13:01:49-04:00",
"summary": "Also, micro.blog with Monocle is a little bit more complicated because Monocle is Microsub (reading API) plus Micropub (posting API). Micro.blog currently supports a subset of Micropub (intentionally), and Microsub is still so new, that while I think there are eventual plans to add support, it\u2019ll probably be a little while.",
"url": "https://eddiehinkle.com/2018/03/25/8/reply/",
"category": [
"indieweb",
"micro.blog"
],
"in-reply-to": [
"https://micro.blog/mikehaynes/427827"
],
"content": {
"text": "Also, micro.blog with Monocle is a little bit more complicated because Monocle is Microsub (reading API) plus Micropub (posting API). Micro.blog currently supports a subset of Micropub (intentionally), and Microsub is still so new, that while I think there are eventual plans to add support, it\u2019ll probably be a little while.",
"html": "<p>Also, micro.blog with Monocle is a little bit more complicated because Monocle is Microsub (reading API) plus Micropub (posting API). Micro.blog currently supports a subset of Micropub (intentionally), and Microsub is still so new, that while I <em>think</em> there are eventual plans to add support, it\u2019ll probably be a little while.</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-media.p3k.io/eddiehinkle.com/cf9f85e26d4be531bc908d37f69bff1c50b50b87fd066b254f1332c3553df1a8.jpg"
},
"refs": {
"https://micro.blog/mikehaynes/427827": {
"type": "entry",
"url": "https://micro.blog/mikehaynes/427827",
"name": "https://micro.blog/mikehaynes/427827"
}
},
"_id": "159200",
"_source": "226",
"_is_read": true
}
Using Twitter for OAuth 2.0 is just a first step into the IndieWeb. IndieAuth can technically support all sorts of login options (emails, mobile login, passwords, etc) @manton has expressed that he has plans for deeper IndieAuth integration in micro.blog, and David Shanske is currently working on an IndieAuth plug-in for WordPress that will allow the use of the Wordpress User/Pass to login to Quill and other Micropub clients
{
"type": "entry",
"published": "2018-03-25T12:49:45-04:00",
"summary": "Using Twitter for OAuth 2.0 is just a first step into the IndieWeb. IndieAuth can technically support all sorts of login options (emails, mobile login, passwords, etc) @manton has expressed that he has plans for deeper IndieAuth integration in micro.blog, and David Shanske is currently working on an IndieAuth plug-in for WordPress that will allow the use of the Wordpress User/Pass to login to Quill and other Micropub clients",
"url": "https://eddiehinkle.com/2018/03/25/7/reply/",
"category": [
"indieauth",
"indieweb"
],
"in-reply-to": [
"https://blog.vanessahamshere.uk/2018/03/25/90/"
],
"content": {
"text": "Using Twitter for OAuth 2.0 is just a first step into the IndieWeb. IndieAuth can technically support all sorts of login options (emails, mobile login, passwords, etc) @manton has expressed that he has plans for deeper IndieAuth integration in micro.blog, and David Shanske is currently working on an IndieAuth plug-in for WordPress that will allow the use of the Wordpress User/Pass to login to Quill and other Micropub clients",
"html": "<p>Using Twitter for OAuth 2.0 is just a first step into the IndieWeb. IndieAuth can technically support all sorts of login options (emails, mobile login, passwords, etc) <a href=\"https://eddiehinkle.com/timeline/undefined\">@manton</a> has expressed that he has plans for deeper IndieAuth integration in micro.blog, and <a href=\"https://david.shanske.com/\">David Shanske</a> is currently working on an IndieAuth plug-in for WordPress that will allow the use of the Wordpress User/Pass to login to Quill and other Micropub clients</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-media.p3k.io/eddiehinkle.com/cf9f85e26d4be531bc908d37f69bff1c50b50b87fd066b254f1332c3553df1a8.jpg"
},
"refs": {
"https://blog.vanessahamshere.uk/2018/03/25/90/": {
"type": "entry",
"url": "https://blog.vanessahamshere.uk/2018/03/25/90/",
"name": "https://blog.vanessahamshere.uk/2018/03/25/90/"
}
},
"_id": "159201",
"_source": "226",
"_is_read": true
}
{
"type": "entry",
"published": "2018-03-25T09:26:03-07:00",
"url": "https://aaronparecki.com/2018/03/25/10/",
"category": [
"monocle",
"indieweb"
],
"photo": [
"https://aperture-media.p3k.io/aaronparecki.com/dda4335a71d68e5ac28c3494190f93904c8830df99cb18e7ab88ee1d718739da.png"
],
"content": {
"text": "I think it might be time to turn off email notifications from GitHub since it's nicer to read these in Monocle where I can reply inline!"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/2b8e1668dcd9cfa6a170b3724df740695f73a15c2a825962fd0a0967ec11ecdc.jpg"
},
"_id": "158899",
"_source": "16",
"_is_read": true
}
{
"type": "entry",
"published": "2018-03-24T23:09:18-04:00",
"url": "https://martymcgui.re/2018/03/24/230918/",
"category": [
"podcast",
"IndieWeb",
"this-week-indieweb-podcast"
],
"audio": [
"https://aperture-media.p3k.io/media.martymcgui.re/64a1f1cdca306c4d6e6a90fcfd23faef3bd2f92e63925ef0a810347434e4642d.mp3"
],
"syndication": [
"https://huffduffer.com/schmarty/467687",
"https://twitter.com/schmarty/status/977746199993348096",
"https://www.facebook.com/marty.mcguire.54/posts/10211696865999136"
],
"name": "This Week in the IndieWeb Audio Edition \u2022 March 17th - 23rd, 2018",
"content": {
"text": "Show/Hide Transcript \n \n Facebook quitters, a Puny micropub server, and where\u2019s the love for future generations?\n\nIt\u2019s the audio edition for This Week in the IndieWeb for March 17th - 23rd, 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>Facebook quitters, a Puny micropub server, and where\u2019s the love for future generations?</p>\n\n<p>It\u2019s the audio edition for <a href=\"https://indieweb.org/this-week/2018-03-23.html\">This Week in the IndieWeb for March 17th - 23rd, 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-media.p3k.io/martymcgui.re/4f9fac2b9e3ae62998c557418143efe288bca8170a119921a9c6bfeb0a1263a2.jpg"
},
"_id": "158236",
"_source": "175",
"_is_read": true
}
{
"type": "entry",
"published": "2018-03-23T16:38:48-04:00",
"url": "https://kartikprabhu.com/notes/fb-for-shopping",
"category": [
"indieweb"
],
"photo": [
"https://aperture-media.p3k.io/lh3.googleusercontent.com/54d17dfdb01067a643859aceef536fbc29f03c4a4270785b5d20389d427e7b52.jpg"
],
"syndication": [
"https://twitter.com/kartik_prabhu/status/977284810791059456"
],
"content": {
"text": "Seems like @facebook is becoming a place more for shopping and less for people.\n\nsee also: https://kartikprabhu.com/notes/twitter-for-brands\n\nSomeone should invent a new social network!",
"html": "Seems like @facebook is becoming a place more for shopping and less for people.\n\nsee also: <a href=\"https://kartikprabhu.com/notes/twitter-for-brands\">https://kartikprabhu.com/notes/twitter-for-brands</a>\n\nSomeone should invent a new social network!\n\t<a href=\"https://lh3.googleusercontent.com/IUk0ud3sxZaupNJU9zBWTbrDkjR7X8KlZyTJngeoVnVQ4f6SRmIymbA4Bj1Xu2_JoLKDuh-2SmDftnWAd1bBIhD4U8PoMCr2ZNTia_wKgzMMcPl3E2S5n4c0mmVJD4Ro_9REbSiTwIINhCzQssTXPoqe_m3HHOMXryo6SPdDKhh477t0GEA5WbPTPAW2VhL-N7ks0Z6DzqkLB2igQWeP7WCoRzDqsC7tKxBNLsoMD00EyL1pO4fZCD_9yc0Ngf9IuJ6aXWxNP4zmdWNz3iON8ZVyPEkVS3vuP6atIsZshZtw1KvcEYJ6nLdNPzqDsGCLI-isS_vAboobvG-8oDUJILWANzrLXPahXRcRQld3OtjXj31El05YkclyOW9ofBnfQHekZfzpYGF6L2G3rZsNDRUtlv9qMAq9H4-sP9PhXfdFfOpiRO82MdIslogl21pz20V3dsiU3OwdaXUgn7B0R31qEQICPmL1RmjYrZBr4rFnV8aL42tkYuQ-DdTT9aDqSNeHbceg7DMtIsWxS03qhAi3urRXQls1ZRR-CLzItf598JzS4gXsB6sdWI7iBImn--apbYTcndAXO38x8Q2H8hCYtJOhEyaAQQV9gZJZ=w312-h669-no\"></a>"
},
"author": {
"type": "card",
"name": "Kartik Prabhu",
"url": "https://kartikprabhu.com/about#me",
"photo": "https://aperture-media.p3k.io/kartikprabhu.com/981e0000045eab42b01b65701176ae41915fc92f36edd0137979ffd4af0c00d1.jpg"
},
"_id": "157448",
"_source": "204",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Jimmy Baum",
"url": "http://amongthestones.com",
"photo": null
},
"url": "http://amongthestones.com/microblog/friday1144am/",
"name": "Friday 11:44 AM",
"content": {
"html": "<blockquote><p>\n \u201cIf you can\u2019t use your own domain name, you can\u2019t own it. Your content will be forever stuck at those silo URLs, beholden to the whims of the algorithmic timeline and shifting priorities of the executive team.\u201d\n</p></blockquote>\n<p>\u2014 <a href=\"http://www.manton.org/2018/03/indieweb-generation-4-and-hosted-domains.html\">IndieWeb generation 4 and hosted domains</a></p>",
"text": "\u201cIf you can\u2019t use your own domain name, you can\u2019t own it. Your content will be forever stuck at those silo URLs, beholden to the whims of the algorithmic timeline and shifting priorities of the executive team.\u201d\n\n\u2014 IndieWeb generation 4 and hosted domains"
},
"published": "2018-03-23T16:28:45+00:00",
"updated": "2018-03-23T16:28:45+00:00",
"_id": "157404",
"_source": "231",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Colin Walker",
"url": "https://colinwalker.blog/",
"photo": null
},
"url": "https://colinwalker.blog/bridging-the-gap/",
"published": "2018-03-23T20:08:38+00:00",
"content": {
"html": "<p>Eli Mellen <a href=\"https://eli.li/entry.php?id=20180318015703\">wrote a great post</a> about how the <a href=\"https://colinwalker.blog/?s=%23indieweb\">#indieweb</a> needs to be more accessible to non-developers. It prompted some considered response including <a href=\"https://www.jeremycherfas.net/blog/a-user-considers\">this post from Jeremy Cherfas</a> in which he points to <a href=\"https://petermolnar.net/re-eli-20180318015703/\">a response from Peter Molnar</a>. And then there is \"<a href=\"https://david.shanske.com/2018/03/18/an-indieweb-podcast-episode-0/\">An Indieweb Podcast</a>\" from David Shanske and Chris Aldridge.</p>\n<p>Eli linked to the <a href=\"https://indieweb.org/generations\">indieweb generations</a> page (the suggested adoption path) exclaiming that much of the current technology is rooted in generations 1 & 2 (the more technical users) but needs to be accessible to those in generations 3 & 4.</p>\n<p>He espoused <a href=\"https://micro.blog/\">micro.blog</a> as an example of pushing things towards the later generations suggesting it's <em>'time to update some of the tooling\"</em> to bridge the gap.</p>\n<p>Having written previously about the need for easier implementation I didn't want to just repeat myself, or Eli, so wasn't sure how to respond or what extra I could add.</p>\n<p>But then two posts cemented my thoughts.</p>\n<p>Firstly, Manton Reece (creator of micro.blog) highlighted that the much sought after ownership of content doesn't just mean owning the server and having direct control over the source code. Instead, it's about <em>\"portable URLs and data. It\u2019s about domain names\"</em> so that a site can outlive any platform.</p>\n<p>Micro.blog as a service definitely straddles generations 3 & 4 as it works just as well with existing blogs as a blog hosted on the service itself. But If you opt for the latter then Manton has made things considerably simpler for you.</p>\n<p>A CMS, webmentions, publishing by micropub, it's all built in, nothing else required apart from a micropub client - of which the native iOS and Mac micro.blog apps are perfectly functional and more than adequate examples.</p>\n<p>This is exactly what Eli alludes to when he says you can't assume that users will care about the tech or the specs - they just want the tools.</p>\n<p>Peter Molnar argues that <em>\"people should care, they should be at least be aware of what's happening when they press a publish button\"</em> and that <em>\"providing the tools only is not a goal I can align with.\"</em></p>\n<p>I have to agree with Eli here.</p>\n<p>People don't have any idea how Twitter and Facebook work but are willing to throw themselves at it despite warnings. Merely a fraction of the population has ever heard of MX records, and wouldn't know their POP3 from their IMAP, but billions still use email.</p>\n<p>This is why ecosystems and adoption curves exist; some blaze the trails and develop solutions so others can use them without having to.</p>\n<p>WordPress users, for example, load plugins to get the functionality they require with no idea of how that's actually achieved. It's taken on faith because the creators and the standards organisations have done their jobs.</p>\n<p>And <em>that</em> is the generational gap</p>\n<p>Next, Jason Kottke's linked to Dan Cohen's post \"<a href=\"https://dancohen.org/2018/03/21/back-to-the-blog/\">Back to the Blog</a>\" in which he talks about the importance of writing on one's own domain but suggests many don't because we are social animals and social networks provide <em>\"a powerful sense of ambient humanity.\"</em></p>\n<p>I've previously described micro.blog as a social layer or glue but I think \"ambient humanity\" sums it up perfectly - the feeling that <em>\"others are here\"</em> as Dan puts it. This is absolutely what micro.blog helps to achieve: that connection between people, between blogs, even if you have set up on your own.</p>\n<p>You don't have to be isolated.</p>\n<p>The aim of the indieweb is that we can do our own thing, or join something like micro.blog, and that our sites and services are portable and interoperable because the technology is platform agnostic. For this to happen the ecosystem needs to be mature with tooling simple enough that anyone can plug and play, or have it built in to their platform of choice, without needing to know how it works.</p>\n<p>It needs to be invisible.</p>",
"text": "Eli Mellen wrote a great post about how the #indieweb needs to be more accessible to non-developers. It prompted some considered response including this post from Jeremy Cherfas in which he points to a response from Peter Molnar. And then there is \"An Indieweb Podcast\" from David Shanske and Chris Aldridge.\nEli linked to the indieweb generations page (the suggested adoption path) exclaiming that much of the current technology is rooted in generations 1 & 2 (the more technical users) but needs to be accessible to those in generations 3 & 4.\nHe espoused micro.blog as an example of pushing things towards the later generations suggesting it's 'time to update some of the tooling\" to bridge the gap.\nHaving written previously about the need for easier implementation I didn't want to just repeat myself, or Eli, so wasn't sure how to respond or what extra I could add.\nBut then two posts cemented my thoughts.\nFirstly, Manton Reece (creator of micro.blog) highlighted that the much sought after ownership of content doesn't just mean owning the server and having direct control over the source code. Instead, it's about \"portable URLs and data. It\u2019s about domain names\" so that a site can outlive any platform.\nMicro.blog as a service definitely straddles generations 3 & 4 as it works just as well with existing blogs as a blog hosted on the service itself. But If you opt for the latter then Manton has made things considerably simpler for you.\nA CMS, webmentions, publishing by micropub, it's all built in, nothing else required apart from a micropub client - of which the native iOS and Mac micro.blog apps are perfectly functional and more than adequate examples.\nThis is exactly what Eli alludes to when he says you can't assume that users will care about the tech or the specs - they just want the tools.\nPeter Molnar argues that \"people should care, they should be at least be aware of what's happening when they press a publish button\" and that \"providing the tools only is not a goal I can align with.\"\nI have to agree with Eli here.\nPeople don't have any idea how Twitter and Facebook work but are willing to throw themselves at it despite warnings. Merely a fraction of the population has ever heard of MX records, and wouldn't know their POP3 from their IMAP, but billions still use email.\nThis is why ecosystems and adoption curves exist; some blaze the trails and develop solutions so others can use them without having to.\nWordPress users, for example, load plugins to get the functionality they require with no idea of how that's actually achieved. It's taken on faith because the creators and the standards organisations have done their jobs.\nAnd that is the generational gap\nNext, Jason Kottke's linked to Dan Cohen's post \"Back to the Blog\" in which he talks about the importance of writing on one's own domain but suggests many don't because we are social animals and social networks provide \"a powerful sense of ambient humanity.\"\nI've previously described micro.blog as a social layer or glue but I think \"ambient humanity\" sums it up perfectly - the feeling that \"others are here\" as Dan puts it. This is absolutely what micro.blog helps to achieve: that connection between people, between blogs, even if you have set up on your own.\nYou don't have to be isolated.\nThe aim of the indieweb is that we can do our own thing, or join something like micro.blog, and that our sites and services are portable and interoperable because the technology is platform agnostic. For this to happen the ecosystem needs to be mature with tooling simple enough that anyone can plug and play, or have it built in to their platform of choice, without needing to know how it works.\nIt needs to be invisible."
},
"name": "Bridging the gap",
"_id": "156958",
"_source": "237",
"_is_read": true
}
{
"type": "entry",
"published": "2018-03-23T15:00:20+01:00",
"url": "https://realize.be/notes/1313",
"name": "#11",
"content": {
"text": "@pstuifzand do you think I could get an alpha invite for your micropub client. Curious to test :) Working myself on https://github.com/swentel/indigenous-android (and pinging you now from it heh)",
"html": "<p>@pstuifzand do you think I could get an alpha invite for your micropub client. Curious to test :) Working myself on <a href=\"https://github.com/swentel/indigenous-android\">https://github.com/swentel/indigenous-android</a> (and pinging you now from it heh)</p>"
},
"_id": "156957",
"_source": "213",
"_is_read": true
}
{
"type": "entry",
"published": "2018-03-23T16:18:43+00:00",
"url": "http://stream.boffosocko.com/2018/huby-and-now-the-bigger-reveal-since-youve-liked-my",
"syndication": [
"https://twitter.com/ChrisAldrich/status/977218119574917120"
],
"in-reply-to": [
"https://twitter.com/huby/status/976930523238060034",
"http://stream.boffosocko.com/2018/huby-plain-old-semantic-html-with-microformats-in-combination-with"
],
"content": {
"text": "@huby And now the bigger reveal! Since you've liked my tweet, you'll notice that I'm backfeeding reactions and comments from my tweets, so your \"like\" also lives on my website at the original post which was syndicated to Twitter. http://stream.boffosocko.com/2018/huby-plain-old-semantic-html-with-microformats-in-combination-with",
"html": "@huby And now the bigger reveal! Since you've liked my tweet, you'll notice that I'm backfeeding reactions and comments from my tweets, so your \"like\" also lives on my website at the original post which was syndicated to Twitter. <a href=\"http://stream.boffosocko.com/2018/huby-plain-old-semantic-html-with-microformats-in-combination-with\">http://stream.boffosocko.com/2018/huby-plain-old-semantic-html-with-microformats-in-combination-with</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "https://aperture-media.p3k.io/stream.boffosocko.com/d0ba9f65fcbf0cef3bdbcccc0b6a1f42b1310f7ab2e07208c7a396166cde26b1.jpg"
},
"_id": "155948",
"_source": "192",
"_is_read": true
}
{
"type": "entry",
"published": "2018-03-23T09:48:05+00:00",
"url": "http://stream.boffosocko.com/2018/kaushalmodi-_dgoldsmith-it-also-looks-like-_am1t-is-also-in",
"syndication": [
"https://twitter.com/ChrisAldrich/status/977119847040593920"
],
"in-reply-to": [
"https://twitter.com/ChrisAldrich/status/977116413436493824"
],
"content": {
"text": "@kaushalmodi @_dgoldsmith It also looks like @_am1t is also in the Hugo camp as well for additional possible help and collaboration. \nhttps://www.amitgawande.com/indiewebify-hugo-website/",
"html": "<a href=\"https://twitter.com/kaushalmodi\">@kaushalmodi</a> <a href=\"https://twitter.com/_dgoldsmith\">@_dgoldsmith</a> It also looks like <a href=\"https://twitter.com/_am1t\">@_am1t</a> is also in the Hugo camp as well for additional possible help and collaboration. <br /><a href=\"https://www.amitgawande.com/indiewebify-hugo-website/\">https://www.amitgawande.com/indiewebify-hugo-website/</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "https://aperture-media.p3k.io/stream.boffosocko.com/d0ba9f65fcbf0cef3bdbcccc0b6a1f42b1310f7ab2e07208c7a396166cde26b1.jpg"
},
"_id": "155949",
"_source": "192",
"_is_read": true
}
{
"type": "entry",
"published": "2018-03-23T09:34:26+00:00",
"url": "http://stream.boffosocko.com/2018/kaushalmodi-_dgoldsmith-it-looks-like-schussman-has-gotten-webmention-and",
"syndication": [
"https://twitter.com/ChrisAldrich/status/977116413436493824"
],
"in-reply-to": [
"https://twitter.com/_dgoldsmith/status/977109743532724224"
],
"content": {
"text": "@kaushalmodi @_dgoldsmith It looks like @schussman has gotten Webmention and display as well as a manual box working on his Hugo site as well, so he may be of some help too: https://prettygoodhat.com/post/2018-01-14-retuning-indieweb/",
"html": "<a href=\"https://twitter.com/kaushalmodi\">@kaushalmodi</a> <a href=\"https://twitter.com/_dgoldsmith\">@_dgoldsmith</a> It looks like <a href=\"https://twitter.com/schussman\">@schussman</a> has gotten Webmention and display as well as a manual box working on his Hugo site as well, so he may be of some help too: <a href=\"https://prettygoodhat.com/post/2018-01-14-retuning-indieweb/\">https://prettygoodhat.com/post/2018-01-14-retuning-indieweb/</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "https://aperture-media.p3k.io/stream.boffosocko.com/d0ba9f65fcbf0cef3bdbcccc0b6a1f42b1310f7ab2e07208c7a396166cde26b1.jpg"
},
"_id": "155950",
"_source": "192",
"_is_read": true
}
{
"type": "entry",
"published": "2018-03-22T23:54:50+00:00",
"url": "http://stream.boffosocko.com/2018/jorge_romeo-ive-written-a-short-intro-to-some-of-the",
"syndication": [
"https://twitter.com/ChrisAldrich/status/976970510985777152"
],
"in-reply-to": [
"https://twitter.com/Jorge_Romeo/status/976697869502746624"
],
"content": {
"text": "@Jorge_Romeo I've written a short intro to some of the pieces if you can't wait: http://boffosocko.com/2017/07/28/an-introduction-to-the-indieweb/",
"html": "<a href=\"https://twitter.com/Jorge_Romeo\">@Jorge_Romeo</a> I've written a short intro to some of the pieces if you can't wait: <a href=\"http://boffosocko.com/2017/07/28/an-introduction-to-the-indieweb/\">http://boffosocko.com/2017/07/28/an-introduction-to-the-indieweb/</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "https://aperture-media.p3k.io/stream.boffosocko.com/d0ba9f65fcbf0cef3bdbcccc0b6a1f42b1310f7ab2e07208c7a396166cde26b1.jpg"
},
"_id": "155951",
"_source": "192",
"_is_read": true
}
@huby plain old semantic HTML with microformats in combination with the webmention protocol allow one to post "likes" to one's own website and send them to others. Here's a simple example: http://boffosocko.com/2018/01/11/1-million-webmentions/
{
"type": "entry",
"published": "2018-03-22T23:34:55+00:00",
"url": "http://stream.boffosocko.com/2018/huby-plain-old-semantic-html-with-microformats-in-combination-with",
"syndication": [
"https://twitter.com/ChrisAldrich/status/976965497429352450"
],
"in-reply-to": [
"https://twitter.com/huby/status/976930523238060034"
],
"content": {
"text": "@huby plain old semantic HTML with microformats in combination with the webmention protocol allow one to post \"likes\" to one's own website and send them to others. Here's a simple example: http://boffosocko.com/2018/01/11/1-million-webmentions/",
"html": "<a href=\"https://twitter.com/huby\">@huby</a> plain old semantic HTML with microformats in combination with the webmention protocol allow one to post \"likes\" to one's own website and send them to others. Here's a simple example: <a href=\"http://boffosocko.com/2018/01/11/1-million-webmentions/\">http://boffosocko.com/2018/01/11/1-million-webmentions/</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "https://aperture-media.p3k.io/stream.boffosocko.com/d0ba9f65fcbf0cef3bdbcccc0b6a1f42b1310f7ab2e07208c7a396166cde26b1.jpg"
},
"_id": "155952",
"_source": "192",
"_is_read": true
}
{
"type": "entry",
"published": "2018-03-22T22:53:07+00:00",
"url": "http://stream.boffosocko.com/2018/kaushalmodi-also-on-your-site-im-seeing-relme-instead-of",
"syndication": [
"https://twitter.com/ChrisAldrich/status/976954987778539522"
],
"in-reply-to": [
"https://twitter.com/kaushalmodi/status/976946679504130050"
],
"content": {
"text": "@kaushalmodi Also, on your site I'm seeing rel=me instead of the rel=\"me\" with the proper quotes around me. See http://microformats.org/wiki/rel-me for examples.",
"html": "<a href=\"https://twitter.com/kaushalmodi\">@kaushalmodi</a> Also, on your site I'm seeing rel=me instead of the rel=\"me\" with the proper quotes around me. See <a href=\"http://microformats.org/wiki/rel-me\">http://microformats.org/wiki/rel-me</a> for examples."
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "https://aperture-media.p3k.io/stream.boffosocko.com/d0ba9f65fcbf0cef3bdbcccc0b6a1f42b1310f7ab2e07208c7a396166cde26b1.jpg"
},
"_id": "155953",
"_source": "192",
"_is_read": true
}
{
"type": "entry",
"published": "2018-03-22T22:49:19+00:00",
"url": "http://stream.boffosocko.com/2018/kaushalmodi-i-know-that-_dgoldsmith-has-gotten-webmention-working-with",
"syndication": [
"https://twitter.com/ChrisAldrich/status/976954027744415744"
],
"in-reply-to": [
"https://twitter.com/kaushalmodi/status/976946679504130050"
],
"content": {
"text": "@kaushalmodi I know that @_dgoldsmith has gotten Webmention working with Hugo before, presuming that's what you're building on top of. https://chat.indieweb.org/ is also a good place to ask.",
"html": "<a href=\"https://twitter.com/kaushalmodi\">@kaushalmodi</a> I know that <a href=\"https://twitter.com/_dgoldsmith\">@_dgoldsmith</a> has gotten Webmention working with Hugo before, presuming that's what you're building on top of. <a href=\"https://chat.indieweb.org/\">https://chat.indieweb.org/</a> is also a good place to ask."
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "https://aperture-media.p3k.io/stream.boffosocko.com/d0ba9f65fcbf0cef3bdbcccc0b6a1f42b1310f7ab2e07208c7a396166cde26b1.jpg"
},
"_id": "155954",
"_source": "192",
"_is_read": true
}
Hey, Micropub is a protocol that apps and sites can agree to allow posting to your site using various apps that you don’t have to build. A Micropub endpoint is the url that the Micropub app needs to use to communicate with the site. More here https://indieweb.org/Micropub/Clients
{
"type": "entry",
"published": "2018-03-23T10:57:43-04:00",
"summary": "Hey, Micropub is a protocol that apps and sites can agree to allow posting to your site using various apps that you don\u2019t have to build. A Micropub endpoint is the url that the Micropub app needs to use to communicate with the site. More here https://indieweb.org/Micropub/Clients",
"url": "https://eddiehinkle.com/2018/03/23/3/reply/",
"in-reply-to": [
"https://mobile.twitter.com/_/status/977151283223257088"
],
"content": {
"text": "Hey, Micropub is a protocol that apps and sites can agree to allow posting to your site using various apps that you don\u2019t have to build. A Micropub endpoint is the url that the Micropub app needs to use to communicate with the site. More here https://indieweb.org/Micropub/Clients",
"html": "<p>Hey, Micropub is a protocol that apps and sites can agree to allow posting to your site using various apps that you don\u2019t have to build. A Micropub endpoint is the url that the Micropub app needs to use to communicate with the site. More here https://indieweb.org/Micropub/Clients</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-media.p3k.io/eddiehinkle.com/cf9f85e26d4be531bc908d37f69bff1c50b50b87fd066b254f1332c3553df1a8.jpg"
},
"refs": {
"https://mobile.twitter.com/_/status/977151283223257088": {
"type": "entry",
"url": "https://mobile.twitter.com/_/status/977151283223257088",
"name": "https://mobile.twitter.com/_/status/977151283223257088"
}
},
"_id": "155913",
"_source": "226",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "manton",
"url": "http://www.manton.org",
"photo": null
},
"url": "http://www.manton.org/2018/03/indieweb-generation-4-and-hosted-domains.html",
"name": "IndieWeb generation 4 and hosted domains",
"content": {
"html": "<p>Naturally because of the goals of Micro.blog, I see a lot of discussion about \u201cowning your content\u201d. It\u2019s an important part of the mission for Micro.blog to take control back from closed, ad-supported social networks and instead embrace posting on our own blogs again.</p>\n<p>But what does it mean to own our content? Do we have to install WordPress or some home-grown blogging system for it to be considered true content ownership, where we have the source code and direct SFTP access to the server? No. If that\u2019s our definition, then content ownership will be permanently reserved for programmers and technical folks who have hours to spend on server configuration.</p>\n<p><a href=\"https://indieweb.org/generations\">IndieWebCamp has a generations chart</a> to illustrate the path from early adopters to mainstream users. Eli Mellen highlighted it <a href=\"https://eli.li/entry.php?id=20180318015703\">in a recent post</a> about the need to bridge the gap between the technical aspects of IndieWeb tools and more approachable platforms. With Micro.blog specifically, the goal is \u201cgeneration 4\u201d, and I think we\u2019re on track to get there.</p>\n<p>I want blogging to be as easy as tweeting. Anything short of that isn\u2019t good enough for Micro.blog. You\u2019ll notice when you use Twitter that they never ask you to SFTP into twitter.com to configure your account. They don\u2019t ask you to install anything.</p>\n<p>More powerful software that you can endlessly customize will always have its place. It\u2019s good to have a range of options, including open source to tinker with. That\u2019s often where some of the best ideas start. But too often I see people get lost in the weeds of plugins and themes, lured in by the myth that you have to self-host with WordPress to be part of the IndieWeb.</p>\n<p>Owning your content isn\u2019t about portable software. It\u2019s about portable URLs and data. It\u2019s about domain names.</p>\n<p>When you write and post photos at your own domain name, your content can outlive any one blogging platform. This month marked the 16th anniversary of blogging at manton.org, and in that time I\u2019ve switched blogging platforms and hosting providers a few times. The posts and URLs can all be preserved through those changes because it\u2019s my own domain name.</p>\n<p>I was disappointed when Medium announced they were <a href=\"http://web.archive.org/web/20180301231401/https://help.medium.com/hc/en-us/articles/115005579728-Get-started-with-custom-domains\">discontinuing support for custom domain names</a>. I\u2019m linking to the Internet Archive copy because Medium\u2019s help page about this is no longer available. If \u201cno custom domains\u201d is still their policy, it\u2019s a setback for the open web, and dooms Medium to the same dead-end as twitter.com/username URLs.</p>\n<p>If you can\u2019t use your own domain name, you can\u2019t own it. Your content will be forever stuck at those silo URLs, beholden to the whims of the algorithmic timeline and shifting priorities of the executive team.</p>\n<p>For hosted blogs on Micro.blog, we encourage everyone to map a custom domain to their content, and we throw in free SSL and preserve redirects for old posts on imported WordPress content. There\u2019s more we can do.</p>\n<p>I\u2019m working on the next version of the macOS app for Micro.blog now, which features multiple accounts and even multiple blogs under the same account. Here\u2019s a screenshot of the settings screen:</p>\n<p><img src=\"https://manton.org/images/2018/prefs_accounts.png\" width=\"512\" height=\"415\" alt=\"Mac screenshot\" /></p>\n<p>The goal with Micro.blog is not to be a stop-gap hosting provider, with truly \u201cserious\u201d users eventually moving on to something else (although we make that easy). We want Micro.blog hosting to be the best platform for owning your content and participating in the Micro.blog and IndieWeb communities.</p>",
"text": "Naturally because of the goals of Micro.blog, I see a lot of discussion about \u201cowning your content\u201d. It\u2019s an important part of the mission for Micro.blog to take control back from closed, ad-supported social networks and instead embrace posting on our own blogs again.\nBut what does it mean to own our content? Do we have to install WordPress or some home-grown blogging system for it to be considered true content ownership, where we have the source code and direct SFTP access to the server? No. If that\u2019s our definition, then content ownership will be permanently reserved for programmers and technical folks who have hours to spend on server configuration.\nIndieWebCamp has a generations chart to illustrate the path from early adopters to mainstream users. Eli Mellen highlighted it in a recent post about the need to bridge the gap between the technical aspects of IndieWeb tools and more approachable platforms. With Micro.blog specifically, the goal is \u201cgeneration 4\u201d, and I think we\u2019re on track to get there.\nI want blogging to be as easy as tweeting. Anything short of that isn\u2019t good enough for Micro.blog. You\u2019ll notice when you use Twitter that they never ask you to SFTP into twitter.com to configure your account. They don\u2019t ask you to install anything.\nMore powerful software that you can endlessly customize will always have its place. It\u2019s good to have a range of options, including open source to tinker with. That\u2019s often where some of the best ideas start. But too often I see people get lost in the weeds of plugins and themes, lured in by the myth that you have to self-host with WordPress to be part of the IndieWeb.\nOwning your content isn\u2019t about portable software. It\u2019s about portable URLs and data. It\u2019s about domain names.\nWhen you write and post photos at your own domain name, your content can outlive any one blogging platform. This month marked the 16th anniversary of blogging at manton.org, and in that time I\u2019ve switched blogging platforms and hosting providers a few times. The posts and URLs can all be preserved through those changes because it\u2019s my own domain name.\nI was disappointed when Medium announced they were discontinuing support for custom domain names. I\u2019m linking to the Internet Archive copy because Medium\u2019s help page about this is no longer available. If \u201cno custom domains\u201d is still their policy, it\u2019s a setback for the open web, and dooms Medium to the same dead-end as twitter.com/username URLs.\nIf you can\u2019t use your own domain name, you can\u2019t own it. Your content will be forever stuck at those silo URLs, beholden to the whims of the algorithmic timeline and shifting priorities of the executive team.\nFor hosted blogs on Micro.blog, we encourage everyone to map a custom domain to their content, and we throw in free SSL and preserve redirects for old posts on imported WordPress content. There\u2019s more we can do.\nI\u2019m working on the next version of the macOS app for Micro.blog now, which features multiple accounts and even multiple blogs under the same account. Here\u2019s a screenshot of the settings screen:\n\nThe goal with Micro.blog is not to be a stop-gap hosting provider, with truly \u201cserious\u201d users eventually moving on to something else (although we make that easy). We want Micro.blog hosting to be the best platform for owning your content and participating in the Micro.blog and IndieWeb communities."
},
"published": "2018-03-23T14:24:36+00:00",
"updated": "2018-03-23T14:24:36+00:00",
"_id": "155503",
"_source": "12",
"_is_read": true
}
