{
"type": "entry",
"published": "2018-07-17T05:58:22+00:00",
"url": "http://stream.boffosocko.com/2018/matpacker-theres-some-documentation-at-workflow-i-also-suspect-that",
"syndication": [
"https://twitter.com/ChrisAldrich/status/1019098986551173120"
],
"in-reply-to": [
"https://twitter.com/matpacker/status/1018978108077207552",
"https://matpacker.com/2018/07/17/7838"
],
"content": {
"text": "@matpacker There's some documentation at https://indieweb.org/Workflow. \n\nI also suspect that some of the WordPress/iOS crowd hanging out in micro.blog may have some experience with this.Searching in chat may reveal more: https://chat.indieweb.org/indieweb/",
"html": "@matpacker There's some documentation at <a href=\"https://indieweb.org/Workflow\">https://indieweb.org/Workflow</a>. <br />\nI also suspect that some of the WordPress/iOS crowd hanging out in micro.blog may have some experience with this.Searching in chat may reveal more: <a href=\"https://chat.indieweb.org/indieweb/\">https://chat.indieweb.org/indieweb/</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "https://aperture-proxy.p3k.io/4a01a54aa55b69dd1b2633c835610491c575e2e2/687474703a2f2f73747265616d2e626f66666f736f636b6f2e636f6d2f66696c652f36303034323762383166373738356537303465616466653531316139323730662f7468756d622e6a7067"
},
"post-type": "reply",
"_id": "648798",
"_source": "192",
"_is_read": true
}
{
"type": "entry",
"published": "2018-07-16T18:53:54-04:00",
"url": "https://martymcgui.re/2018/07/16/185354/",
"category": [
"podcast",
"IndieWeb",
"this-week-indieweb-podcast"
],
"audio": [
"https://aperture-proxy.p3k.io/65e5c65286b420966a851390030932a6f864b1f3/68747470733a2f2f6d656469612e6d617274796d636775692e72652f30382f32642f35642f64612f39653938323133636465643831373931306435393164356333383138636561663839373337366662376639663033383439373565333761352e6d7033"
],
"name": "This Week in the IndieWeb Audio Edition \u2022 July 7th - 13th, 2018",
"content": {
"text": "Nostalgia for homepages, IndieAuth gets an explainer, and lots of new events. It\u2019s the audio edition for This Week in the IndieWeb for July 7th - 13th, 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": "<p>Nostalgia for homepages, IndieAuth gets an explainer, and lots of new events. It\u2019s the audio edition for <a href=\"https://indieweb.org/this-week/2018-07-13.html\">This Week in the IndieWeb for July 7th - 13th, 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"
},
"post-type": "audio",
"_id": "647150",
"_source": "175",
"_is_read": true
}
{
"type": "entry",
"published": "2018-07-16T07:05:56-07:00",
"url": "https://snarfed.org/2018-07-16_introducing-baffle",
"syndication": [
"https://news.indieweb.org/en/snarfed.org/2018-07-16_introducing-baffle",
"https://twitter.com/schnarfed/status/1018888972150267908"
],
"name": "Introducing Baffle",
"content": {
"text": "A while back, I wrote up a design for bridging Microsub clients to traditional feed reader backends. Fast forward to a few weeks ago: I hacked together a bare bones prototype at IndieWebCamp 2018. Fast forward to now: I\u2019m launching Baffle!\nBaffle lets you use Microsub reader apps like Together, Indigenous, and Monocle with traditional feed readers like NewsBlur and maybe eventually Feedly and more.\nRight now, it only supports viewing channels and timelines. If there\u2019s enough interest and usage, I can add channel management, muting, and blocking. I\u2019d also consider adding Feedly if I hear enough desire.\nHappy reading!",
"html": "<p>\n <a href=\"https://baffle.tech/\">\n <img src=\"https://aperture-proxy.p3k.io/ba5fa097747514d3123a876799eae62921760991/68747470733a2f2f736e61726665642e6f72672f772f77702d636f6e74656e742f706c7567696e732f6a65747061636b2f6d6f64756c65732f6c617a792d696d616765732f696d616765732f3178312e7472616e732e676966\" alt=\"1x1.trans.gif\" /></a></p><img src=\"https://aperture-proxy.p3k.io/4d6d8e0cceda2e607f3fa6bc54cf8e1c2d1556de/68747470733a2f2f736e61726665642e6f72672f626166666c652d6c6f676f2e706e67\" alt=\"baffle-logo.png\" />\n<p>A while back, <a href=\"https://snarfed.org/microsub-bridge\">I wrote up a design for bridging Microsub clients to traditional feed reader backends</a>. Fast forward to a few weeks ago: <a href=\"https://chat.indieweb.org/2018-06-27#t1530141961518300\">I hacked together a bare bones prototype</a> at <a href=\"https://2018.indieweb.org/\">IndieWebCamp 2018</a>. Fast forward to now: I\u2019m launching <a href=\"https://baffle.tech/\">Baffle</a>!</p>\n<p>Baffle lets you use <a href=\"https://indieweb.org/Microsub-spec\">Microsub</a> reader apps like <a href=\"https://indieweb.org/Together\">Together</a>, <a href=\"https://indieweb.org/Indigenous\">Indigenous</a>, and <a href=\"https://monocle.p3k.io/\">Monocle</a> with traditional feed readers like <a href=\"https://www.newsblur.com/\">NewsBlur</a> and maybe eventually <a href=\"https://feedly.com/\">Feedly</a> and more.</p>\n<p>Right now, it only supports viewing channels and timelines. If there\u2019s enough interest and usage, I can add channel management, muting, and blocking. I\u2019d also consider adding Feedly if I hear enough desire.</p>\n<p>Happy reading!</p>"
},
"author": {
"type": "card",
"name": "Ryan Barrett",
"url": "https://snarfed.org/",
"photo": "https://aperture-proxy.p3k.io/7e644a0ecb0339b875f998fc405c685591d80cd7/68747470733a2f2f7365637572652e67726176617461722e636f6d2f6176617461722f39343762356633663332336461306566373835623666303264396332363564363f733d393626643d626c616e6b26723d67"
},
"post-type": "article",
"_id": "645526",
"_source": "3",
"_is_read": true
}
Webmention enables a LOT of possibilities, at the root it is just a decentralized notification from one website to another. Currently, the best and most common use case is social media style responses (replies, likes, emoji reactions, and listen posts).
{
"type": "entry",
"published": "2018-07-16T10:20:48-04:00",
"summary": "Webmention enables a LOT of possibilities, at the root it is just a decentralized notification from one website to another. Currently, the best and most common use case is social media style responses (replies, likes, emoji reactions, and listen posts).",
"url": "https://eddiehinkle.com/2018/07/16/3/reply/",
"in-reply-to": [
"https://twitter.com/dialogCRM/status/1018766549274902529"
],
"content": {
"text": "Webmention enables a LOT of possibilities, at the root it is just a decentralized notification from one website to another. Currently, the best and most common use case is social media style responses (replies, likes, emoji reactions, and listen posts).",
"html": "<p>Webmention enables a LOT of possibilities, at the root it is just a decentralized notification from one website to another. Currently, the best and most common use case is social media style responses (replies, likes, emoji reactions, and listen posts).</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"post-type": "reply",
"refs": {
"https://twitter.com/dialogCRM/status/1018766549274902529": {
"type": "entry",
"url": "https://twitter.com/dialogCRM/status/1018766549274902529",
"name": "https://twitter.com/dialogCRM/status/1018766549274902529",
"post-type": "article"
}
},
"_id": "644952",
"_source": "226",
"_is_read": true
}
{
"type": "entry",
"published": "2018-07-16T08:09:51-04:00",
"url": "https://david.shanske.com/2018/07/16/an-indieweb-podcast-episode-8-interflux/",
"audio": [
"https://aperture-proxy.p3k.io/ba47c2f009dd4dbf331cf1c93996ed277268bba0/68747470733a2f2f64617669642e7368616e736b652e636f6d2f77702d636f6e74656e742f75706c6f6164732f323031382f30372f496e646965776562382e6d7033"
],
"syndication": [
"https://twitter.com/dshanske/status/1018830085900636160"
],
"name": "Episode 8: Interflux",
"content": {
"text": "In this episode, Chris and I recap our takeaways and stories from the Indieweb Summit 2018 last month in Portland, Oregon, discuss Microsub, Vouch, and other ideas.\nVouch\nBrainstorming on Implementing Vouch, Following, and Blogrolls \u2013 David Shanske\nRefbacks\nThe Year of the Reader\nGranary\nMicrosub\nIndiewebring\nSending Your First Webmention \u2013 Aaron Parecki\nOAuth for the Open Web \u2013 Aaron Parecki",
"html": "In this episode, Chris and I recap our takeaways and stories from the <a href=\"http://indieweb.org/2018\">Indieweb Summit 2018</a> last month in Portland, Oregon, discuss Microsub, Vouch, and other ideas.\n<ul><li><a href=\"http://indieweb.org/Vouch\">Vouch</a></li>\n<li><a href=\"https://david.shanske.com/2018/07/01/brainstorming-on-implementing-vouch-following-and-blogrolls/\">Brainstorming on Implementing Vouch, Following, and Blogrolls \u2013 David Shanske</a></li>\n<li><a href=\"http://indieweb.org/refback\">Refbacks</a></li>\n<li>The Year of the Reader</li>\n<li><a href=\"https://granary.io\">Granary</a></li>\n<li><a href=\"http://indieweb.org/Microsub\">Microsub</a></li>\n<li><a href=\"http://indieweb.org/indiewebring\">Indiewebring</a></li>\n<li><a href=\"https://aaronparecki.com/2018/06/30/11/your-first-webmention\">Sending Your First Webmention \u2013 Aaron Parecki</a></li>\n<li><a href=\"https://aaronparecki.com/2018/07/07/7/oauth-for-the-open-web\">OAuth for the Open Web \u2013 Aaron Parecki</a></li>\n</ul>"
},
"author": {
"type": "card",
"name": "David Shanske",
"url": "https://david.shanske.com/",
"photo": "https://david.shanske.com/wp-content/uploads/avatar-privacy/cache/gravatar/2/c/2cb1f8afd9c8d3b646b4071c5ed887c970d81d625eeed87e447706940e2c403d-125.png"
},
"post-type": "audio",
"_id": "643936",
"_source": "5",
"_is_read": true
}
@cogdog I have a lot of email spammers talking about my site who can't spell CONVERSATIONS either. What's worse is that when I contact them, none have ever even heard of simple standards like Webmention.
;)
{
"type": "entry",
"published": "2018-07-15T21:57:51+00:00",
"url": "http://stream.boffosocko.com/2018/cogdog-i-have-a-lot-of-email-spammers-talking-about",
"syndication": [
"https://twitter.com/ChrisAldrich/status/1018615665111035904"
],
"in-reply-to": [
"https://twitter.com/cogdog/status/1017781817594859520"
],
"content": {
"text": "@cogdog I have a lot of email spammers talking about my site who can't spell CONVERSATIONS either. What's worse is that when I contact them, none have ever even heard of simple standards like Webmention. \n\n;)",
"html": "<a href=\"https://twitter.com/cogdog\">@cogdog</a> I have a lot of email spammers talking about my site who can't spell CONVERSATIONS either. What's worse is that when I contact them, none have ever even heard of simple standards like Webmention. <br />\n;)"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "https://aperture-proxy.p3k.io/4a01a54aa55b69dd1b2633c835610491c575e2e2/687474703a2f2f73747265616d2e626f66666f736f636b6f2e636f6d2f66696c652f36303034323762383166373738356537303465616466653531316139323730662f7468756d622e6a7067"
},
"post-type": "reply",
"_id": "642406",
"_source": "192",
"_is_read": true
}
“A friend gave me design advice once. He said to start with left-aligned black text on a white background, and to apply styling only to solve a specific problem. This is good advice.” @davetron5000 https://brutalist-web.design/#Indieweb
{
"type": "entry",
"published": "2018-07-14T06:13:22+0000",
"url": "http://known.kevinmarks.com/2018/a-friend-gave-me-design-advice-once",
"category": [
"Indieweb"
],
"syndication": [
"https://twitter.com/kevinmarks/status/1018015580358447106"
],
"content": {
"text": "\u201cA friend gave me design advice once. He said to start with left-aligned black text on a white background, and to apply styling only to solve a specific problem. This is good advice.\u201d @davetron5000 \nhttps://brutalist-web.design/ #Indieweb",
"html": "\u201cA friend gave me design advice once. He said to start with left-aligned black text on a white background, and to apply styling only to solve a specific problem. This is good advice.\u201d @davetron5000 <br /><a href=\"https://brutalist-web.design/\">https://brutalist-web.design/</a> <a href=\"http://known.kevinmarks.com/tag/Indieweb\" class=\"p-category\">#Indieweb</a>"
},
"author": {
"type": "card",
"name": "Kevin Marks",
"url": "http://known.kevinmarks.com/profile/kevinmarks",
"photo": "https://aperture-proxy.p3k.io/ed7979fd10a648fc253eae0b54e66fb36e57d3d4/687474703a2f2f6b6e6f776e2e6b6576696e6d61726b732e636f6d2f66696c652f3932353536353636363931373362373836376162383339656536353536663965"
},
"_id": "618802",
"_source": "205",
"_is_read": true
}
That’s a tough decision. I can see both sides. On one side, it’s not too difficult to add an “-x” to the properties in the Micropub servers. On the other side, it seems like leaving it the same until the standard is the simplest step.
Sorry I’m not much help, but I can understand the catch-22.
{
"type": "entry",
"published": "2018-07-13T23:29:55-04:00",
"summary": "That\u2019s a tough decision. I can see both sides. On one side, it\u2019s not too difficult to add an \u201c-x\u201d to the properties in the Micropub servers. On the other side, it seems like leaving it the same until the standard is the simplest step.\nSorry I\u2019m not much help, but I can understand the catch-22.",
"url": "https://eddiehinkle.com/2018/07/13/56/reply/",
"in-reply-to": [
"https://gregorlove.com/2018/07/micropub-properties-for-indiebookclub/"
],
"content": {
"text": "That\u2019s a tough decision. I can see both sides. On one side, it\u2019s not too difficult to add an \u201c-x\u201d to the properties in the Micropub servers. On the other side, it seems like leaving it the same until the standard is the simplest step.\n\nSorry I\u2019m not much help, but I can understand the catch-22.",
"html": "<p>That\u2019s a tough decision. I can see both sides. On one side, it\u2019s not too difficult to add an \u201c-x\u201d to the properties in the Micropub servers. On the other side, it seems like leaving it the same until the standard is the simplest step.</p>\n\n<p>Sorry I\u2019m not much help, but I can understand the catch-22.</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"refs": {
"https://gregorlove.com/2018/07/micropub-properties-for-indiebookclub/": {
"type": "entry",
"url": "https://gregorlove.com/2018/07/micropub-properties-for-indiebookclub/",
"name": "https://gregorlove.com/2018/07/micropub-properties-for-indiebookclub/"
}
},
"_id": "618215",
"_source": "226",
"_is_read": true
}
{
"type": "entry",
"published": "2018-07-13 17:36-0700",
"url": "https://gregorlove.com/2018/07/micropub-properties-for-indiebookclub/",
"name": "Micropub properties for indiebookclub",
"content": {
"text": "Tantek and I were discussing the read-of and read-status properties and the process of standardizing them in the h-entry specification. I realized read-status may be an overly-specific property name, since the same concept might apply to listen, watch, and exercise posts. Since these are experimental properties, ideally they should be published with the x prefix: p-x-read-status. I noted this in the brainstorming for read posts.\n\nThe problem\n\nI\u2019m trying to decide if/how I should update the indiebookclub Micropub request to reflect this. I know of three Micropub servers processing both properties when publishing:\n\nmicro.blog\n\tMarty McGuire\n\tmy site\nThe WordPress Semantic Linkbacks plugin consumes the read-of property from webmentions to display a separate reading facepile.\n\nThe seemingly correct thing would be for indiebookclub to send these properties as x-read-status and x-read-of. My first reaction is: I don\u2019t want to break the servers above (especially micro.blog) by changing it. My second reaction is: if I do change them now and eventually read properties get standardized, changing at that point will break servers a second time. Is it better to break things once or twice? I wonder if the \u201cbest\u201d thing to do is leave the request as-is and only update it later, once the properties are standardized. This could have the negative effect of encouraging people to keep publishing read-status and read-of, giving the impression they\u2019re standard.\n\nA potential solution?\n\nI could make different versions of the Micropub request and let users toggle them on their settings page. To prevent micro.blog from breaking immediately, I could default micro.blog users to the legacy version. Everyone else would default to v2. Whenever the properties are standardized, v3 would be setup and become the default.\n\nThis solution feels a bit unfriendly to Micropub server implementers, so I keep coming back to wondering if I should keep it as-is and only change when it\u2019s standardized.\n\nI feel a bit stuck, so I\u2019m definitely open to suggestions. Help me, Micropub masters! :]",
"html": "<p><a class=\"h-card\" href=\"http://tantek.com\">Tantek</a> and I were <a href=\"https://chat.indieweb.org/microformats/2018-07-09#t1531169722471100\">discussing</a> the <code>read-of</code> and <code>read-status</code> properties and the process of standardizing them in the <a href=\"http://microformats.org/wiki/h-entry\">h-entry specification</a>. I realized <code>read-status</code> may be an overly-specific property name, since the same concept might apply to listen, watch, and exercise posts. Since these are experimental properties, ideally they should be published with the x prefix: <code>p-x-read-status</code>. I noted this in the <a href=\"https://indieweb.org/read#gRegor_Morrill_thoughts\">brainstorming</a> for read posts.</p>\n\n<h2>The problem</h2>\n\n<p>I\u2019m trying to decide if/how I should update the <a href=\"https://indiebookclub.biz/documentation#micropub\">indiebookclub Micropub request</a> to reflect this. I know of three Micropub servers processing both properties when publishing:</p>\n\n<ul><li><a href=\"https://micro.blog\">micro.blog</a></li>\n\t<li><a class=\"h-card\" href=\"https://martymcgui.re\">Marty McGuire</a></li>\n\t<li>my site</li>\n</ul><p>The WordPress Semantic Linkbacks plugin consumes the <code>read-of</code> property from webmentions to display a separate <i>reading</i> facepile.</p>\n\n<p>The seemingly correct thing would be for indiebookclub to send these properties as <code>x-read-status</code> and <code>x-read-of</code>. My first reaction is: I don\u2019t want to break the servers above (especially micro.blog) by changing it. My second reaction is: if I do change them now and eventually <i>read</i> properties get standardized, changing at that point will break servers a second time. Is it better to break things once or twice? I wonder if the \u201cbest\u201d thing to do is leave the request as-is and only update it later, once the properties are standardized. This could have the negative effect of encouraging people to keep publishing <code>read-status</code> and <code>read-of</code>, giving the impression they\u2019re standard.</p>\n\n<h2>A potential solution?</h2>\n\n<p>I could make different versions of the Micropub request and let users toggle them on their settings page. To prevent micro.blog from breaking immediately, I could default micro.blog users to the <i>legacy</i> version. Everyone else would default to <i>v2</i>. Whenever the properties are standardized, <i>v3</i> would be setup and become the default.</p>\n\n<p>This solution feels a bit unfriendly to Micropub server implementers, so I keep coming back to wondering if I should keep it as-is and only change when it\u2019s standardized.</p>\n\n<p>I feel a bit stuck, so I\u2019m definitely open to suggestions. Help me, Micropub masters! :]</p>"
},
"author": {
"type": "card",
"name": "gRegor Morrill",
"url": "https://gregorlove.com/",
"photo": "https://aperture-proxy.p3k.io/929c8777d059069a2a16a064d96f4c29b65548f8/68747470733a2f2f677265676f726c6f76652e636f6d2f736974652f6173736574732f66696c65732f333437332f70726f66696c652d323031362d6d65642e6a7067"
},
"_id": "616963",
"_source": "95",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": null,
"url": "https://www.manton.org/",
"photo": null
},
"url": "https://www.manton.org/2018/07/13/web-rings-are.html",
"name": "Web rings are back",
"content": {
"html": "<p>One reason that <a href=\"http://manton.org/2018/06/30/indieweb-summit-wrapup.html\">IndieWeb Summit was such a success</a> was the range of projects to come out of the second day as attendees worked on their own projects. There were new tools and features of existing platforms, but also personal site updates and just fun stuff. And web rings are fun!</p>\n\n<p>I know, I know\u2026 Is it 2018 or 1998? I\u2019ve added a <a href=\"http://help.micro.blog/2018/web-rings/\">help page on Micro.blog</a> for how to add a web ring to your blog using \ud83d\udd78\ufe0f\ud83d\udc8d. One of the great things about microblogging at your own domain name is you can experiment with features like this.</p>\n\n<p>Daniel and I talk a little more about this on <a href=\"https://coreint.org/2018/07/episode-336-bringing-webrings-back/\">the new episode of Core Intuition</a> out today. Enjoy.</p>",
"text": "One reason that IndieWeb Summit was such a success was the range of projects to come out of the second day as attendees worked on their own projects. There were new tools and features of existing platforms, but also personal site updates and just fun stuff. And web rings are fun!\n\nI know, I know\u2026 Is it 2018 or 1998? I\u2019ve added a help page on Micro.blog for how to add a web ring to your blog using \ud83d\udd78\ufe0f\ud83d\udc8d. One of the great things about microblogging at your own domain name is you can experiment with features like this.\n\nDaniel and I talk a little more about this on the new episode of Core Intuition out today. Enjoy."
},
"published": "2018-07-13T15:01:29-05:00",
"_id": "615611",
"_source": "12",
"_is_read": true
}
Thanks for writing this up. The standard is stable enough to be used daily but as you said, the features to make the apps (including Indigenous for iOS, which I am developing) excel are still in development. I’ve been able to implement some of what you mentioned (mark posts as read/unread), but others are still on my list of things to tackle (sorting, filtering, etc). I think two things are needed to get where we need to be: 1) all Microsub developers need to use it daily (I’m pretty sure we all do) and 2) People that try it out need to write blog posts just like this one so that we see where we need to improve and iterate.
Thanks for trying Microsub out. Hopefully it won’t be too long before it supports the features you need! 🙂
{
"type": "entry",
"published": "2018-07-13T15:21:49-04:00",
"summary": "Thanks for writing this up. The standard is stable enough to be used daily but as you said, the features to make the apps (including Indigenous for iOS, which I am developing) excel are still in development. I\u2019ve been able to implement some of what you mentioned (mark posts as read/unread), but others are still on my list of things to tackle (sorting, filtering, etc). I think two things are needed to get where we need to be: 1) all Microsub developers need to use it daily (I\u2019m pretty sure we all do) and 2) People that try it out need to write blog posts just like this one so that we see where we need to improve and iterate.\nThanks for trying Microsub out. Hopefully it won\u2019t be too long before it supports the features you need! \ud83d\ude42",
"url": "https://eddiehinkle.com/2018/07/13/18/reply/",
"in-reply-to": [
"https://www.amitgawande.com/state-of-microsub/"
],
"content": {
"text": "Thanks for writing this up. The standard is stable enough to be used daily but as you said, the features to make the apps (including Indigenous for iOS, which I am developing) excel are still in development. I\u2019ve been able to implement some of what you mentioned (mark posts as read/unread), but others are still on my list of things to tackle (sorting, filtering, etc). I think two things are needed to get where we need to be: 1) all Microsub developers need to use it daily (I\u2019m pretty sure we all do) and 2) People that try it out need to write blog posts just like this one so that we see where we need to improve and iterate.\n\nThanks for trying Microsub out. Hopefully it won\u2019t be too long before it supports the features you need! \ud83d\ude42",
"html": "<p>Thanks for writing this up. The standard is stable enough to be used daily but as you said, the features to make the apps (including Indigenous for iOS, which I am developing) excel are still in development. I\u2019ve been able to implement some of what you mentioned (mark posts as read/unread), but others are still on my list of things to tackle (sorting, filtering, etc). I think two things are needed to get where we need to be: 1) all Microsub developers need to use it daily (I\u2019m pretty sure we all do) and 2) People that try it out need to write blog posts just like this one so that we see where we need to improve and iterate.</p>\n\n<p>Thanks for trying Microsub out. Hopefully it won\u2019t be too long before it supports the features you need! \ud83d\ude42</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"refs": {
"https://www.amitgawande.com/state-of-microsub/": {
"type": "entry",
"url": "https://www.amitgawande.com/state-of-microsub/",
"name": "https://www.amitgawande.com/state-of-microsub/"
}
},
"_id": "614970",
"_source": "226",
"_is_read": true
}
I tried very hard in that book, when it came to social media, to be platform agnostic, to emphasize that social media sites come and go, and to always invest first and foremost in your own media (website, blog, etc.) and mailing list.
I still stand by that advice, but if I re-wrote the book now, I would encourage artists to use much more caution when it comes to using social media websites like Facebook, Twitter, and Instagram.
{
"type": "entry",
"published": "2018-07-13T08:04:10Z",
"url": "https://adactio.com/links/14127",
"category": [
"indieweb",
"social",
"media",
"publishing",
"attention",
"publicity"
],
"bookmark-of": [
"https://austinkleon.com/2018/07/05/you-dont-have-to-live-in-public/"
],
"content": {
"text": "You don\u2019t have to live in public\n\n\n\n\n I tried very hard in that book, when it came to social media, to be platform agnostic, to emphasize that social media sites come and go, and to always invest first and foremost in your own media (website, blog, etc.) and mailing list.\n \n I still stand by that advice, but if I re-wrote the book now, I would encourage artists to use much more caution when it comes to using social media websites like Facebook, Twitter, and Instagram.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://austinkleon.com/2018/07/05/you-dont-have-to-live-in-public/\">\nYou don\u2019t have to live in public\n</a>\n</h3>\n\n<blockquote>\n <p>I tried very hard in that book, when it came to social media, to be platform agnostic, to emphasize that social media sites come and go, and to always invest first and foremost in your own media (website, blog, etc.) and mailing list.</p>\n \n <p>I still stand by that advice, but if I re-wrote the book now, I would encourage artists to use much more caution when it comes to using social media websites like Facebook, Twitter, and Instagram.</p>\n</blockquote>"
},
"_id": "609580",
"_source": "2",
"_is_read": true
}
{
"type": "entry",
"published": "2018-07-11T19:20:59-04:00",
"url": "https://martymcgui.re/2018/07/11/192059/",
"category": [
"HWC",
"IndieWeb",
"Baltimore",
"wrap-up"
],
"syndication": [
"https://twitter.com/schmarty/status/1017188787363962880",
"https://www.facebook.com/events/2131315447143424/"
],
"name": "HWC Baltimore 2018-07-11 Wrap-Up",
"content": {
"text": "Baltimore's first Homebrew Website Club of July met at the Digital Harbor Foundation Tech Center on July 11th! \nHere are some notes from the \"broadcast\" portion of the meetup:\njonathanprozzi.net \u2014 Been building static HTML/CSS layouts for fun! Some\u00a0examples. Also started practicing turning those designs into layouts in Figma. Had a usability testing call w/ the folks from Gatsby that turned into a great discussion about how to better build community starters.\ndariusmccoy.com \u2014 Was having some issues w/ his site, which is hosted on AWS. He is thinking about wiping his instance and starting a new one, since he has lost track of some of his passwords. In a tricky spot because AWS doesn't offer any tech support for free tier users. Talked about switching to Digital Ocean or something simpler but will have to balance his budgets to justify the costs.\nderekfields.is\u00a0\u2014 Been taking a Udemy course on VueJS. Before that has been working on a schedule for developing his website. Has a friend doing the same and they mutually keep each other on track to spend a certain amount of time on developing their skills and sites. It's kind of working!\n\n martymcgui.re \u2014 Brought a bunch of stickers and other fun things home from IndieWeb Summit! Had a great time seeing folks he met last year and meeting new folks. Lots of great discussion sessions, hacking projects, wild ideas, and more. He really needs to write it up on his site! His hack day project also desperately needs to be written up \u2013 it's an IndieWeb-style web ring, available at \ud83d\udd78\ud83d\udc8d.ws\u00a0! This week he added support for indielogin.com, which lets people sign in using their own websites by setting up only a couple of links.\n \n\nOther discussion:\n\nIndieWeb Summit! Marty went and loved it. Next year would love to bring more folks from HWC Baltimore, and travel assistance is available. We'll work on it.\n \n Marty met Jared Ewy\u00a0of name.com\u00a0at the Summit and talked about all the cool work DHF does teaching youth to build websites, the upcoming Web Shop, hosting HWC and IWC Baltimore, etc. Jared gave him a bunch of codes for free domains and some hosting discounts to benefit that work, so we discussed lots of ideas!\n \n\n Some possibilities: give Web Shop youth employees incentive to work on their own projects, outside of paid jobs, to learn more about building their own sites. Host a special Homebrew Website Club that's a 2-hour jam for new folks who don't have a domain yet to get set up with a website. Host a longer \"Build Your Website Day\" (maybe in coordination with a multi-city Drag Queen Build-a-Website Day?)\n What would an IndieWeb \"starter pack\" look like for a quick \"you have a domain but no money\" way to get started? GitHub looks good for skill building for folks that want to get into web development someday because it's mostly managed by hand. Netlify looks pretty good for this because they offer hosting, flexible static site generation, SSL for HTTPS, and the NetlifyCMS. They also support some features like building your own webhooks on JavaScript, which could eventually be used to handle common IndieWeb building block endpoints (IndieAuth, Micropub, Webmention, ...) Because they run all the stuff for a given site from a git repository, it's possible to take a site from Netlify and set it up elsewhere if their offerings change.\n \"Packages\" for a getting started workshop. E.g. \"what will you get at the end + what will you need to learn along the way.\" Static HTML/CSS on GitHub could get a portfolio site done. For $5/mo a Neocities site can be hosted on a custom domain and requires no Git/GitHub wrangling. Micro.blog hosting is also $5/mo and brings a ton of features, interactivity, and community.\n Talked about VueJS passing React in terms of number of stars on GitHub, and speculating why that is. For example, VueJS can be a lot easier to dip your toes in and get started without a complicated build toolchain.\nLeft-to-right: martymcgui.re, dariusmccoy.net, jonathanprozzi.net, derekfields.isThanks to everybody who came out! We hope to see you all again at our next meeting on Wednesday July 25th\u00a0at 6:30pm (quiet writing hour at 5:30pm)!",
"html": "Baltimore's <a href=\"https://indieweb.org/events/2018-07-11-homebrew-website-club\">first Homebrew Website Club of July</a> met at the <a href=\"https://www.digitalharbor.org/\">Digital Harbor Foundation Tech Center</a> on July 11th! \n<p>Here are some notes from the \"broadcast\" portion of the meetup:</p>\n<p><a href=\"https://jonathanprozzi.net/\">jonathanprozzi.net</a> \u2014 Been building static HTML/CSS layouts for fun! <a href=\"https://jonathanprozzi.net/learning/fun-with-html-css-layouts-part-one-layouts-1-3/\">Some</a>\u00a0<a href=\"https://jonathanprozzi.net/learning/fun-with-html-css-layouts-part-two/\">examples</a>. Also started practicing turning those designs into layouts in <a href=\"https://www.figma.com\">Figma</a>. Had a usability testing call w/ the folks from <a href=\"https://www.gatsbyjs.com/\">Gatsby</a> that turned into a great discussion about how to better build community starters.</p>\n<a href=\"http://www.dariusmccoy.com/\">dariusmccoy.com</a> \u2014 Was having some issues w/ his site, which is hosted on AWS. He is thinking about wiping his instance and starting a new one, since he has lost track of some of his passwords. In a tricky spot because AWS doesn't offer any tech support for free tier users. Talked about switching to Digital Ocean or something simpler but will have to balance his budgets to justify the costs.\n<p><a href=\"http://derekfields.is/\">derekfields.is</a>\u00a0\u2014 Been taking a Udemy course on VueJS. Before that has been working on a schedule for developing his website. Has a friend doing the same and they mutually keep each other on track to spend a certain amount of time on developing their skills and sites. It's kind of working!</p>\n<p>\n <a href=\"https://martymcgui.re/\">martymcgui.re</a> \u2014 Brought a bunch of stickers and other fun things home from IndieWeb Summit! Had a great time seeing folks he met last year and meeting new folks. Lots of great discussion sessions, hacking projects, wild ideas, and more. He really needs to write it up on his site! His hack day project also desperately needs to be written up \u2013 it's an IndieWeb-style web ring, available at <a>\ud83d\udd78\ud83d\udc8d.ws</a>\u00a0! This week he added support for <a href=\"https://indielogin.com/\">indielogin.com</a>, which lets people sign in using their own websites by <a href=\"https://indieweb.org/RelMeAuth\">setting up only a couple of links</a>.\n <br /></p>\nOther discussion:\n<ul><li>\n<a href=\"https://indieweb.org/2018\">IndieWeb Summit</a>! Marty went and loved it. Next year would love to bring more folks from HWC Baltimore, and travel assistance is available. We'll work on it.</li>\n <li>\n Marty met <a href=\"http://ewy.me/\">Jared Ewy</a>\u00a0of <a href=\"https://name.com/\">name.com</a>\u00a0at the Summit and talked about all the cool work DHF does teaching youth to build websites, the upcoming Web Shop, hosting HWC and IWC Baltimore, etc. Jared gave him a bunch of codes for free domains and some hosting discounts to benefit that work, so we discussed lots of ideas!\n <br /></li>\n <li>Some possibilities: give Web Shop youth employees incentive to work on their own projects, outside of paid jobs, to learn more about building their own sites. Host a special Homebrew Website Club that's a 2-hour jam for new folks who don't have a domain yet to get set up with a website. Host a longer \"Build Your Website Day\" (maybe in coordination with a <a href=\"https://twitter.com/sdepolo/status/1011739362122334208\">multi-city Drag Queen Build-a-Website Day</a>?)</li>\n <li>What would an IndieWeb \"starter pack\" look like for a quick \"you have a domain but no money\" way to get started? GitHub looks good for skill building for folks that want to get into web development someday because it's mostly managed by hand. Netlify looks pretty good for this because they offer hosting, flexible static site generation, SSL for HTTPS, and the NetlifyCMS. They also support some features like building your own webhooks on JavaScript, which could eventually be used to handle common IndieWeb building block endpoints (IndieAuth, Micropub, Webmention, ...) Because they run all the stuff for a given site from a git repository, it's possible to take a site from Netlify and set it up elsewhere if their offerings change.</li>\n <li>\"Packages\" for a getting started workshop. E.g. \"what will you get at the end + what will you need to learn along the way.\" Static HTML/CSS on GitHub could get a portfolio site done. For $5/mo a <a href=\"http://neocities.org/\">Neocities</a> site can be hosted on a custom domain and requires no Git/GitHub wrangling. <a href=\"https://micro.blog/\">Micro.blog</a> hosting is also $5/mo and brings a ton of features, interactivity, and community.</li>\n <li>Talked about VueJS passing React in terms of number of stars on GitHub, and speculating why that is. For example, VueJS can be a lot easier to dip your toes in and get started without a complicated build toolchain.</li>\n</ul><img src=\"https://aperture-proxy.p3k.io/1127acf1b67d51fa640077be4c098625690f567f/68747470733a2f2f6d656469612e6d617274796d636775692e72652f38392f62332f33312f36372f31316364383233633833343838396430353035623339336137343432653333653134396262393261303533356631366634303232653966352e6a7067\" alt=\"Photo of HWC Baltimore attendees\" />Left-to-right: martymcgui.re, dariusmccoy.net, jonathanprozzi.net, derekfields.is<p>Thanks to everybody who came out! We hope to see you all again at our next meeting on <strong>Wednesday </strong><a href=\"https://indieweb.org/events/2018-07-25-homebrew-website-club\">July 25th</a>\u00a0at <strong>6:30pm</strong> (quiet writing hour at 5:30pm)!</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://aperture-proxy.p3k.io/8275f85e3a389bd0ae69f209683436fc53d8bad9/68747470733a2f2f6d617274796d636775692e72652f696d616765732f6c6f676f2e6a7067"
},
"_id": "596894",
"_source": "175",
"_is_read": true
}
{
"type": "entry",
"published": "2018-07-11T16:08:40Z",
"url": "https://adactio.com/journal/14120",
"category": [
"rss",
"tags",
"feeds",
"links",
"linking",
"folksonomy",
"indieweb",
"publishing",
"journal",
"blogging",
"tagging",
"hyperlinks",
"hypertext"
],
"syndication": [
"https://medium.com/@adactio/29514a02ccc2"
],
"name": "Links, tags, and feeds",
"content": {
"text": "A little while back, I switched from using Chrome as my day-to-day browser to using Firefox. I could feel myself getting a bit too comfortable with one particular browser, and that\u2019s not good. I reckon it\u2019s good to shake things up a little every now and then. Besides, there really isn\u2019t that much difference once you\u2019ve transferred over bookmarks and cookies.\n\nUnfortunately I\u2019m being bitten by this little bug in Firefox. It causes some of my bookmarklets to fail on certain sites with strict Content Security Policies (and CSPs shouldn\u2019t affect bookmarklets). I might have to switch back to Chrome because of this.\n\nI use bookmarklets throughout the day. There\u2019s the Huffduffer bookmarklet, of course, for whenever I come across a podcast episode or other piece of audio that I want to listen to later. But there\u2019s also my own home-rolled bookmarklet for posting links to my site. It doesn\u2019t do anything clever\u2014it grabs the title and URL of the currently open page and pre-populates a form in a new window, leaving me to add a short description and some tags.\n\nIf you\u2019re reading this, then you\u2019re familiar with the \u201cjournal\u201d section of adactio.com, but the \u201clinks\u201d section is where I post the most. Here, for example, are all the links I posted yesterday. It varies from day to day, but there\u2019s generally a handful.\n\nShould you wish to keep track of everything I\u2019m linking to, there\u2019s a twitterbot you can follow called @adactioLinks. It uses a simple IFTTT recipe to poll my RSS feed of links and send out a tweet whenever there\u2019s a new entry.\n\nOr you can drink straight from the source and subscribe to the RSS feed itself, if you\u2019re still rocking it old-school. But if RSS is your bag, then you might appreciate a way to filter those links\u2026\n\nAll my links are tagged. Heavily. This is because all my links are \u201cnotes to future self\u201d, and all my future self has to do is ask \u201cwhat would past me have tagged that link with?\u201d when I\u2019m trying to find something I previously linked to. I end up using my site\u2019s URLs as an interface:\n\n\nadactio.com/links/tags/serviceworkers or \nadactio.com/links/tags/sci-fi\nAt the front-end gatherings at Clearleft, I usually wrap up with a quick tour of whatever I\u2019ve added that week to:\n\nadactio.com/links/tags/frontend\nWell, each one of those tags also has a corresponding RSS feed:\n\nadactio.com/links/tags/serviceworkers/rss\nadactio.com/links/tags/sci-fi/rss\nadactio.com/links/tags/frontend/rss\n\u2026and so on.\n\nThat means you can subscribe to just the links tagged with something you\u2019re interested in. Here\u2019s the full list of tags if you\u2019re interested in seeing the inside of my head.\n\nThis also works for my journal entries. If you\u2019re only interested in my blog posts about frontend development, you might want to subscribe to:\n\nadactio.com/journal/tags/frontend/rss\nHere are all the tags from my journal.\n\nYou can even mix them up. For everything I\u2019ve tagged with \u201ctypography\u201d\u2014whether it\u2019s links, journal entries, or articles\u2014the URL is:\n\nadactio.com/tags/typography\nThe corresponding RSS feed is:\n\nadactio.com/tags/typography/rss\nYou get the idea. Basically, if something on my site is a list of items, chances are there\u2019s a corresponding RSS feeds. Sometimes there might even be a JSON feed. Hack some URLs to see.\n\nMeanwhile, I\u2019ll be linking, linking, linking\u2026",
"html": "<p>A little while back, I switched from using Chrome as my day-to-day browser to using Firefox. I could feel myself getting a bit too comfortable with one particular browser, and that\u2019s not good. I reckon it\u2019s good to shake things up a little every now and then. Besides, there really isn\u2019t that much difference once you\u2019ve transferred over bookmarks and cookies.</p>\n\n<p>Unfortunately I\u2019m being bitten by <a href=\"https://bugzilla.mozilla.org/show_bug.cgi?id=866522\">this little bug in Firefox</a>. It causes some of my bookmarklets to fail on certain sites with strict Content Security Policies (and CSPs shouldn\u2019t affect bookmarklets). I might have to switch back to Chrome because of this.</p>\n\n<p>I use bookmarklets throughout the day. There\u2019s the <a href=\"https://huffduffer.com/\">Huffduffer</a> bookmarklet, of course, for whenever I come across a podcast episode or other piece of audio that I want to listen to later. But there\u2019s also my own home-rolled bookmarklet for posting links to my site. It doesn\u2019t do anything clever\u2014it grabs the title and URL of the currently open page and pre-populates a form in a new window, leaving me to add a short description and some tags.</p>\n\n<p>If you\u2019re reading this, then you\u2019re familiar with <a href=\"https://adactio.com/journal/\">the \u201cjournal\u201d section</a> of adactio.com, but <a href=\"https://adactio.com/links/\">the \u201clinks\u201d section</a> is where I post the most. Here, for example, are <a href=\"https://adactio.com/links/archive/2018/07/10\">all the links I posted yesterday</a>. It varies from day to day, but there\u2019s generally a handful.</p>\n\n<p>Should you wish to keep track of everything I\u2019m linking to, there\u2019s a twitterbot you can follow called <a href=\"https://twitter.com/adactioLinks\">@adactioLinks</a>. It uses a simple IFTTT recipe to poll <a href=\"https://adactio.com/links/rss\">my RSS feed of links</a> and send out a tweet whenever there\u2019s a new entry.</p>\n\n<p>Or you can drink straight from the source and subscribe to <a href=\"https://adactio.com/links/rss\">the RSS feed</a> itself, if you\u2019re still rocking it old-school. But if RSS is your bag, then you might appreciate a way to filter those links\u2026</p>\n\n<p>All my links are tagged. Heavily. This is because all my links are \u201cnotes to future self\u201d, and all my future self has to do is ask \u201cwhat would past me have tagged that link with?\u201d when I\u2019m trying to find something I previously linked to. I end up using my site\u2019s URLs as an interface:</p>\n\n<ul><li>\n<a href=\"https://adactio.com/links/tags/serviceworkers\"><code>adactio.com/links/tags/serviceworkers</code></a> or </li>\n<li><a href=\"https://adactio.com/links/tags/sci-fi\"><code>adactio.com/links/tags/sci-fi</code></a></li>\n</ul><p>At the front-end gatherings at <a href=\"https://clearleft.com/\">Clearleft</a>, I usually wrap up with a quick tour of whatever I\u2019ve added that week to:</p>\n\n<ul><li><a href=\"https://adactio.com/links/tags/frontend\"><code>adactio.com/links/tags/frontend</code></a></li>\n</ul><p>Well, each one of those tags also has a corresponding RSS feed:</p>\n\n<ul><li><a href=\"https://adactio.com/links/tags/serviceworkers/rss\"><code>adactio.com/links/tags/serviceworkers/rss</code></a></li>\n<li><a href=\"https://adactio.com/links/tags/sci-fi/rss\"><code>adactio.com/links/tags/sci-fi/rss</code></a></li>\n<li><a href=\"https://adactio.com/links/tags/frontend/rss\"><code>adactio.com/links/tags/frontend/rss</code></a></li>\n</ul><p>\u2026and so on.</p>\n\n<p>That means you can subscribe to just the links tagged with something you\u2019re interested in. Here\u2019s <a href=\"https://adactio.com/links/tags/\">the full list of tags</a> if you\u2019re interested in seeing the inside of my head.</p>\n\n<p>This also works for my journal entries. If you\u2019re only interested in my <a href=\"https://adactio.com/journal/tags/frontend\">blog posts about frontend development</a>, you might want to subscribe to:</p>\n\n<ul><li><a href=\"https://adactio.com/journal/tags/frontend/rss\"><code>adactio.com/journal/tags/frontend/rss</code></a></li>\n</ul><p>Here are <a href=\"https://adactio.com/journal/tags\">all the tags</a> from my journal.</p>\n\n<p>You can even mix them up. For everything I\u2019ve tagged with \u201ctypography\u201d\u2014whether it\u2019s links, journal entries, or articles\u2014the URL is:</p>\n\n<ul><li><a href=\"https://adactio.com/tags/typography\"><code>adactio.com/tags/typography</code></a></li>\n</ul><p>The corresponding RSS feed is:</p>\n\n<ul><li><a href=\"https://adactio.com/tags/typography/rss\"><code>adactio.com/tags/typography/rss</code></a></li>\n</ul><p>You get the idea. Basically, if something on my site is a list of items, chances are there\u2019s a corresponding RSS feeds. Sometimes there might even be a <a href=\"https://jsonfeed.org/\">JSON feed</a>. Hack some URLs to see.</p>\n\n<p>Meanwhile, I\u2019ll be linking, linking, linking\u2026</p>"
},
"_id": "594242",
"_source": "2",
"_is_read": true
}
Quill's event creation UI now has venue autocomplete and a map preview, and sends the full venue information to your Micropub endpoint as an h-card! Selecting a location also sets the timezone offset of the event start/end date properly too!
This just made it so much easier to post events to my site, so I expect to be posting a lot more now!
{
"type": "entry",
"published": "2018-07-11T07:55:06-07:00",
"url": "https://aaronparecki.com/2018/07/11/8/quill-event",
"category": [
"p3k",
"quill"
],
"photo": [
"https://aperture-media.p3k.io/aaronparecki.com/e9ffa3f5d6949223e3d06764a67cd67d41a616ae51a9e0b5167f7939f4ee3800.png"
],
"video": [
"https://aperture-media.p3k.io/aaronparecki.com/9540e208e76c278256c630b7f6d66c4137994ffcf68b0239b6972f948899e986.mp4"
],
"content": {
"text": "Quill's event creation UI now has venue autocomplete and a map preview, and sends the full venue information to your Micropub endpoint as an h-card! Selecting a location also sets the timezone offset of the event start/end date properly too! \n\nThis just made it so much easier to post events to my site, so I expect to be posting a lot more now!",
"html": "Quill's event creation UI now has venue autocomplete and a map preview, and sends the full venue information to your Micropub endpoint as an h-card! Selecting a location also sets the timezone offset of the event start/end date properly too! <br /><br />This just made it so much easier to post events to my site, so I expect to be posting a lot more now!"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/2b8e1668dcd9cfa6a170b3724df740695f73a15c2a825962fd0a0967ec11ecdc.jpg"
},
"_id": "593156",
"_source": "16",
"_is_read": true
}
Yeah, I think from the micro.blog side of things it makes sense to hide it from the UI. From the IndieWeb side of things, I think over the next year we’ll see expansion into follower lists to help readers, recommendations and the vouch system. For this reason, I think data wise keeping the full follower list is important.
{
"type": "entry",
"published": "2018-07-10T13:06:20-04:00",
"summary": "Yeah, I think from the micro.blog side of things it makes sense to hide it from the UI. From the IndieWeb side of things, I think over the next year we\u2019ll see expansion into follower lists to help readers, recommendations and the vouch system. For this reason, I think data wise keeping the full follower list is important.",
"url": "https://eddiehinkle.com/2018/07/10/6/reply/",
"in-reply-to": [
"https://micro.blog/manton/703850"
],
"content": {
"text": "Yeah, I think from the micro.blog side of things it makes sense to hide it from the UI. From the IndieWeb side of things, I think over the next year we\u2019ll see expansion into follower lists to help readers, recommendations and the vouch system. For this reason, I think data wise keeping the full follower list is important.",
"html": "<p>Yeah, I think from the micro.blog side of things it makes sense to hide it from the UI. From the IndieWeb side of things, I think over the next year we\u2019ll see expansion into follower lists to help readers, recommendations and the vouch system. For this reason, I think data wise keeping the full follower list is important.</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"refs": {
"https://micro.blog/manton/703850": {
"type": "entry",
"url": "https://micro.blog/manton/703850",
"name": "https://micro.blog/manton/703850"
}
},
"_id": "585751",
"_source": "226",
"_is_read": true
}
{
"type": "entry",
"published": "2018-07-09T22:47:13-04:00",
"summary": "In fact, that reply (and this reply) was sent into Micro.blog system via webmention from my website.",
"url": "https://eddiehinkle.com/2018/07/09/23/reply/",
"in-reply-to": [
"https://www.izq.fm/2018/07/09/id-love-it.html"
],
"content": {
"text": "In fact, that reply (and this reply) was sent into Micro.blog system via webmention from my website.",
"html": "<p>In fact, that reply (and this reply) was sent into Micro.blog system via webmention from my website.</p>"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"refs": {
"https://www.izq.fm/2018/07/09/id-love-it.html": {
"type": "entry",
"url": "https://www.izq.fm/2018/07/09/id-love-it.html",
"name": "https://www.izq.fm/2018/07/09/id-love-it.html"
}
},
"_id": "583867",
"_source": "226",
"_is_read": true
}
