{
"type": "entry",
"author": {
"name": "manton",
"url": "http://www.manton.org",
"photo": null
},
"url": "http://www.manton.org/2017/11/6096.html",
"content": {
"html": "<p><a href=\"http://timetable.manton.org/2017/11/episode-83-event-countdown/\">On this morning\u2019s episode</a> of my short-form podcast Timetable: plans for the week including IndieWebCamp promotion and the Micro.blog launch.</p>",
"text": "On this morning’s episode of my short-form podcast Timetable: plans for the week including IndieWebCamp promotion and the Micro.blog launch."
},
"published": "2017-11-27T17:14:14+00:00",
"updated": "2017-11-27T17:14:14+00:00",
"_id": "406",
"_source": "12",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "manton",
"url": "http://www.manton.org",
"photo": null
},
"url": "http://www.manton.org/2017/11/eff-austin-party-after-indiewebcamp.html",
"name": "EFF-Austin party after IndieWebCamp",
"content": {
"html": "<p>In a little less than 2 weeks we\u2019re holding the first IndieWebCamp in Austin: December 9th and 10th at Capital Factory. You can <a href=\"https://www.eventbrite.com/e/indiewebcamp-austin-2017-tickets-39918084064\">register here</a>. Doors open at 9am and we\u2019ll have coffee and breakfast tacos while everyone checks in.</p>\n<p>Saturday night after IndieWebCamp will be the EFF-Austin Holiday Party. <a href=\"https://www.meetup.com/EFF-Austin/events/245317381/\">There\u2019s a meetup page</a> to RSVP for the party. Even if you can\u2019t attend IndieWebCamp for the full weekend, you\u2019re welcome to join us anytime Saturday and stick around for the party. (Please register for both so we can better plan for the event.)</p>\n<p>Who should attend IndieWebCamp? Anyone who cares about the independent web. Anyone who remembers how the web used to be \u2014\u00a0the creativity of personal web sites, the freedom of open APIs \u2014 and how it could be that way again. From <a href=\"https://2017.indieweb.org/austin\">the event web site</a>:</p>\n<blockquote><p>\n IndieWebCamp Austin 2017 is a gathering for independent web creators of all kinds, from graphic artists, to designers, UX engineers, coders, hackers, to share ideas, actively work on creating for their own personal websites, and build upon each others creations.\n</p></blockquote>\n<p>I hope you can make it. If you have any questions, email me at <a href=\"mailto:manton@micro.blog\">manton@micro.blog</a>.</p>",
"text": "In a little less than 2 weeks we’re holding the first IndieWebCamp in Austin: December 9th and 10th at Capital Factory. You can register here. Doors open at 9am and we’ll have coffee and breakfast tacos while everyone checks in.\nSaturday night after IndieWebCamp will be the EFF-Austin Holiday Party. There’s a meetup page to RSVP for the party. Even if you can’t attend IndieWebCamp for the full weekend, you’re welcome to join us anytime Saturday and stick around for the party. (Please register for both so we can better plan for the event.)\nWho should attend IndieWebCamp? Anyone who cares about the independent web. Anyone who remembers how the web used to be \u2014\u00a0the creativity of personal web sites, the freedom of open APIs \u2014 and how it could be that way again. From the event web site:\n\n IndieWebCamp Austin 2017 is a gathering for independent web creators of all kinds, from graphic artists, to designers, UX engineers, coders, hackers, to share ideas, actively work on creating for their own personal websites, and build upon each others creations.\n\nI hope you can make it. If you have any questions, email me at manton@micro.blog."
},
"published": "2017-11-27T15:34:24+00:00",
"updated": "2017-11-27T15:34:24+00:00",
"_id": "404",
"_source": "12",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "manton",
"url": "http://www.manton.org",
"photo": null
},
"url": "http://www.manton.org/2017/11/blog-archive-format.html",
"name": "Blog archive format",
"content": {
"html": "<p>As I\u2019ve been improving the import and export functionality in Micro.blog, I\u2019ve done a lot of work with WordPress\u2019s WXR format, which is based on RSS. While there\u2019s nothing particularly wrong with WXR, it\u2019s more complicated than it needs to be for non-WordPress sites, especially when you start to tackle image uploads that exist outside of the post text.</p>\n<p>Micro.blog can also push an entire site\u2019s Markdown, HTML, and images to GitHub, which is the most complete mirror and perfect for migrating to another Jekyll server. It introduces so many extra files, though, it\u2019s not reasonable to expect that other blog platforms could support the same level of detail.</p>\n<p>I\u2019d be happy to ignore the WordPress-centric nature of WXR and use it as a common blog archive format if WXR provided a mechanism to store image uploads. Helping people migrate from WordPress to Micro.blog-hosted blogs has only emphasized to me that a better format is needed.</p>\n<p>In chatting with the IndieWeb community, the idea was proposed that an HTML file using <a href=\"https://indieweb.org/h-feed\">h-feed</a> would provide portability and also an added bonus: it could be opened in any web browser to view your archived site. Images could be stored as files with relative references in the HTML file. (I\u2019d throw in a JSON Feed file, too, so that importers could choose between using a Microformats parser or JSON parser.)</p>\n<p>The files would look something like this:</p>\n<ul><li>index.html</li>\n<li>feed.json</li>\n<li>uploads\n<ul><li>2017\n<ul><li>test.jpg</li>\n</ul></li>\n</ul></li>\n</ul><p>The basics from h-feed would follow this structure:</p>\n<ul><li>h-feed\n<ul><li>h-entry\n<ul><li>p-name</li>\n<li>e-content</li>\n<li>dt-published</li>\n<li>u-url</li>\n</ul></li>\n<li>h-entry\n<ul><li>\u2026</li>\n</ul></li>\n</ul></li>\n</ul><p>Only index.html and feed.json would be required. Any other paths in the archive would be determined by the contents of the HTML. (I\u2019m using \u201cuploads\u201d in this example, but it could just as easily be \u201carchive\u201d, \u201caudio\u201d, or any other set of folders.)</p>\n<p>For large sites, the HTML could be split into multiple files with appropriate <code><link></code> tags in the header to page through the additional files. While it could contain CSS and your full blog\u2019s design, I\u2019m imagining that the HTML would be extremely lightweight: just enough to capture the posts, not a way to transfer templates and themes between blogs.</p>\n<p>The whole folder is zipped and renamed with a .bar extension. Easy to move around and upload all at once. I\u2019ve created <a href=\"https://manton.org/misc/example.bar\">an example file here</a> (rename it .zip to open it).</p>\n<p>I\u2019d love to hear what you think. I talked about this on <a href=\"http://timetable.manton.org/2017/11/episode-81-blog-archive-format/\">a recent episode of Timetable</a> as well. Might be a nice topic to follow up on at <a href=\"https://2017.indieweb.org/austin\">IndieWebCamp Austin</a> in 2 weeks.</p>",
"text": "As I’ve been improving the import and export functionality in Micro.blog, I’ve done a lot of work with WordPress’s WXR format, which is based on RSS. While there’s nothing particularly wrong with WXR, it’s more complicated than it needs to be for non-WordPress sites, especially when you start to tackle image uploads that exist outside of the post text.\nMicro.blog can also push an entire site’s Markdown, HTML, and images to GitHub, which is the most complete mirror and perfect for migrating to another Jekyll server. It introduces so many extra files, though, it’s not reasonable to expect that other blog platforms could support the same level of detail.\nI’d be happy to ignore the WordPress-centric nature of WXR and use it as a common blog archive format if WXR provided a mechanism to store image uploads. Helping people migrate from WordPress to Micro.blog-hosted blogs has only emphasized to me that a better format is needed.\nIn chatting with the IndieWeb community, the idea was proposed that an HTML file using h-feed would provide portability and also an added bonus: it could be opened in any web browser to view your archived site. Images could be stored as files with relative references in the HTML file. (I’d throw in a JSON Feed file, too, so that importers could choose between using a Microformats parser or JSON parser.)\nThe files would look something like this:\n\nindex.html\nfeed.json\nuploads\n\n2017\n\ntest.jpg\n\n\n\n\n\nThe basics from h-feed would follow this structure:\n\nh-feed\n\nh-entry\n\np-name\ne-content\ndt-published\nu-url\n\n\nh-entry\n\n…\n\n\n\n\n\nOnly index.html and feed.json would be required. Any other paths in the archive would be determined by the contents of the HTML. (I’m using “uploads” in this example, but it could just as easily be “archive”, “audio”, or any other set of folders.)\nFor large sites, the HTML could be split into multiple files with appropriate <link> tags in the header to page through the additional files. While it could contain CSS and your full blog’s design, I’m imagining that the HTML would be extremely lightweight: just enough to capture the posts, not a way to transfer templates and themes between blogs.\nThe whole folder is zipped and renamed with a .bar extension. Easy to move around and upload all at once. I’ve created an example file here (rename it .zip to open it).\nI’d love to hear what you think. I talked about this on a recent episode of Timetable as well. Might be a nice topic to follow up on at IndieWebCamp Austin in 2 weeks."
},
"published": "2017-11-24T21:20:36+00:00",
"updated": "2017-11-24T21:23:06+00:00",
"_id": "355",
"_source": "12",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": null,
"url": "https://strugee.net/blog/",
"photo": null
},
"url": "https://strugee.net/blog/2017/11/webmention-test-post",
"published": "2017-11-24T20:24:46+00:00",
"content": {
"html": "<p>Once again I need to test whether <a href=\"https://github.com/strugee/lazymention\">lazymention</a> - and more importantly, the underlying libraries (<a href=\"https://github.com/strugee/node-send-webmention\">node-send-webmention</a> and <a href=\"https://github.com/strugee/node-get-webmention-url\">node-get-webmention-url</a>) - complies with the <a href=\"https://www.w3.org/TR/webmention/\">W3C spec</a>. I'll be using <a href=\"https://webmention.rocks/\">webmention.rocks</a>, so, here's a large list of links:</p>\n<p><a href=\"https://webmention.rocks/test/1\">Test 1</a>, <a href=\"https://webmention.rocks/test/2\">Test 2</a>, <a href=\"https://webmention.rocks/test/3\">Test 3</a>, <a href=\"https://webmention.rocks/test/4\">Test 4</a>, <a href=\"https://webmention.rocks/test/5\">Test 5</a>, <a href=\"https://webmention.rocks/test/6\">Test 6</a>, <a href=\"https://webmention.rocks/test/7\">Test 7</a>, <a href=\"https://webmention.rocks/test/8\">Test 8</a>, <a href=\"https://webmention.rocks/test/9\">Test 9</a>, <a href=\"https://webmention.rocks/test/10\">Test 10</a>, <a href=\"https://webmention.rocks/test/11\">Test 11</a>, <a href=\"https://webmention.rocks/test/12\">Test 12</a>, <a href=\"https://webmention.rocks/test/13\">Test 13</a>, <a href=\"https://webmention.rocks/test/14\">Test 14</a>, <a href=\"https://webmention.rocks/test/15\">Test 15</a>, <a href=\"https://webmention.rocks/test/16\">Test 16</a>, <a href=\"https://webmention.rocks/test/17\">Test 17</a>, <a href=\"https://webmention.rocks/test/18\">Test 18</a>, <a href=\"https://webmention.rocks/test/19\">Test 19</a>, <a href=\"https://webmention.rocks/test/20\">Test 20</a>, <a href=\"https://webmention.rocks/test/21\">Test 21</a>, <a href=\"https://webmention.rocks/test/22\">Test 22</a>, <a href=\"https://webmention.rocks/test/23/page\">Test 23</a></p>\n<p>Hopefully it works \\o/</p>",
"text": "Once again I need to test whether lazymention - and more importantly, the underlying libraries (node-send-webmention and node-get-webmention-url) - complies with the W3C spec. I'll be using webmention.rocks, so, here's a large list of links:\nTest 1, Test 2, Test 3, Test 4, Test 5, Test 6, Test 7, Test 8, Test 9, Test 10, Test 11, Test 12, Test 13, Test 14, Test 15, Test 16, Test 17, Test 18, Test 19, Test 20, Test 21, Test 22, Test 23\nHopefully it works \\o/"
},
"name": "Webmention test post",
"_id": "123844",
"_source": "227",
"_is_read": true
}
{
"type": "entry",
"published": "2017-11-20T18:42:17-05:00",
"rsvp": "yes",
"url": "https://david.shanske.com/2017/11/20/indiewebcamp-austin-december-9-10-2017-austin-texas/",
"in-reply-to": [
"https://2017.indieweb.org/austin"
],
"name": "Attending IndieWebCamp Austin - December 9-10, 2017 - Austin, Texas IndieWebCamp Austin 2017 is a gathering for independent web creators of all kinds, from graphic artists, to designers, UX engineers, coders, hackers, to share ideas, actively work on creating for their own personal websites, and build upon each others creations. Heading to IndieWebCamp Austin. \n\t \n\n\tPosted on 6:42PM EST\nNovember 20, 2017Kind RSVPLeave a response on IndieWebCamp Austin \u2013 December 9-10, 2017 \u2013 Austin, Texas",
"content": {
"text": "Heading to IndieWebCamp Austin."
},
"author": {
"type": "card",
"name": "David Shanske",
"url": "https://david.shanske.com",
"photo": "https://secure.gravatar.com/avatar/681eba02e72ba1d894097034a8110e61?s=125&d=default&r=g"
},
"_id": "275",
"_source": "5",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "manton",
"url": "http://www.manton.org",
"photo": null
},
"url": "http://www.manton.org/2017/11/6072.html",
"content": {
"html": "<p>Tinkered with WordPress last night so I could ping the new RSVP page for <a href=\"https://2017.indieweb.org/austin\">IndieWebCamp Austin</a>. Also rolled out WordPress export for Micro.blog.</p>",
"text": "Tinkered with WordPress last night so I could ping the new RSVP page for IndieWebCamp Austin. Also rolled out WordPress export for Micro.blog."
},
"published": "2017-11-20T15:19:10+00:00",
"updated": "2017-11-20T15:19:10+00:00",
"_id": "274",
"_source": "12",
"_is_read": true
}
Congratulations on a decade of publishing on your own site—you’re a blogging wizard, Harry!
Having this website changed and shaped my career. If you don’t have a blog, I urge you, start working on one this weekend. Your own blog, with your own content, at your own domain. It might just change your life.
{
"type": "entry",
"published": "2017-11-19T11:33:27Z",
"url": "https://adactio.com/links/13111",
"category": [
"blogging",
"personal",
"publishing",
"indieweb",
"anniversary",
"decade",
"writing",
"sharing",
"csswizardry"
],
"bookmark-of": [
"https://csswizardry.com/2017/11/ten-years-old/"
],
"content": {
"text": "Ten Years Old \u2013 CSS Wizardry\n\n \n\nCongratulations on a decade of publishing on your own site\u2014you\u2019re a blogging wizard, Harry! \n\n\n Having this website changed and shaped my career. If you don\u2019t have a blog, I urge you, start working on one this weekend. Your own blog, with your own content, at your own domain. It might just change your life.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://csswizardry.com/2017/11/ten-years-old/\">\nTen Years Old \u2013 CSS Wizardry\n</a>\n</h3>\n\n<p>Congratulations on a decade of publishing on your own site\u2014you\u2019re a blogging wizard, Harry!</p>\n\n<blockquote>\n <p>Having this website changed and shaped my career. If you don\u2019t have a blog, I urge you, start working on one this weekend. Your own blog, with your own content, at your own domain. It might just change your life.</p>\n</blockquote>"
},
"_id": "260",
"_source": "2",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "manton",
"url": "http://www.manton.org",
"photo": null
},
"url": "http://www.manton.org/2017/11/6035.html",
"content": {
"html": "<p><a href=\"http://timetable.manton.org/2017/11/episode-79-indiewebcamp-venue/\">Posted a quick Timetable episode</a> about how the Micro.blog photo challenge is going, and on finalizing the venue and plans for IndieWebCamp Austin.</p>",
"text": "Posted a quick Timetable episode about how the Micro.blog photo challenge is going, and on finalizing the venue and plans for IndieWebCamp Austin."
},
"published": "2017-11-16T21:32:40+00:00",
"updated": "2017-11-16T21:32:40+00:00",
"_id": "153",
"_source": "12",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "manton",
"url": "http://www.manton.org",
"photo": null
},
"url": "http://www.manton.org/2017/11/indiewebcamp-austin-set-for-december.html",
"name": "IndieWebCamp Austin set for December",
"content": {
"html": "<p>We\u2019re holding an IndieWebCamp in Austin next month! This is a 2-day event \u2014 Saturday and Sunday, December 9th and 10th \u2014 for anyone who wants to learn more about the IndieWeb, discuss web standards and tools, or just hack on your own web site. We\u2019re lucky to have IndieWeb co-founders Tantek \u00c7elik and Aaron Parecki in town for the event.</p>\n<p>There was another IndieWebCamp in Berlin last week. <a href=\"https://doubleloop.net/2017/11/11/indiewebcamp-berlin-2017-day-1/\">Neil Mather had a great blog post</a> about his experience there:</p>\n<blockquote><p>\n It ran over 2 days, with day 1 an unconference with a number of discussions, the topics and schedule decided entirely by participants in the morning. Day 2 was hack day, with everyone working on an indieweb related bit of work, be it on their own website or on a shared project.\n</p></blockquote>\n<p>IndieWebCamp Austin <a href=\"https://2017.indieweb.org/austin\">registration is open now</a>. Tickets are just $5. Looking forward to planning some next steps for Micro.blog over that weekend. Hope to see you there!</p>",
"text": "We’re holding an IndieWebCamp in Austin next month! This is a 2-day event \u2014 Saturday and Sunday, December 9th and 10th \u2014 for anyone who wants to learn more about the IndieWeb, discuss web standards and tools, or just hack on your own web site. We’re lucky to have IndieWeb co-founders Tantek \u00c7elik and Aaron Parecki in town for the event.\nThere was another IndieWebCamp in Berlin last week. Neil Mather had a great blog post about his experience there:\n\n It ran over 2 days, with day 1 an unconference with a number of discussions, the topics and schedule decided entirely by participants in the morning. Day 2 was hack day, with everyone working on an indieweb related bit of work, be it on their own website or on a shared project.\n\nIndieWebCamp Austin registration is open now. Tickets are just $5. Looking forward to planning some next steps for Micro.blog over that weekend. Hope to see you there!"
},
"published": "2017-11-16T15:28:43+00:00",
"updated": "2017-11-16T15:28:43+00:00",
"_id": "147",
"_source": "12",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "manton",
"url": "http://www.manton.org",
"photo": null
},
"url": "http://www.manton.org/2017/11/6027.html",
"content": {
"html": "<p>Minor update to Micro.blog for iOS is now available in the App Store. Fixes posting via the Micropub API, plus a couple more iPhone X tweaks.</p>",
"text": "Minor update to Micro.blog for iOS is now available in the App Store. Fixes posting via the Micropub API, plus a couple more iPhone X tweaks."
},
"published": "2017-11-16T05:50:55+00:00",
"updated": "2017-11-16T05:50:55+00:00",
"_id": "145",
"_source": "12",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": null,
"url": "https://strugee.net/blog/",
"photo": null
},
"url": "https://strugee.net/blog/2017/11/not-going-to-todays-hwc-san-fransisco-2017",
"published": "2017-11-15T14:43:16+00:00",
"content": {
"html": "<p>Testing whether my new Webmention implementation, <a href=\"https://github.com/strugee/lazymention\">lazymention</a> (which will ship Real Soon Now\u2122), will send a Webmention to note that I will NOT be attending today's <a href=\"http://tantek.com/2017/319/e1/homebrew-website-club\">Homebrew Website Club San Francisco</a>! Though let's be honest, I really want to.</p>\n<p>(With <3 for <a href=\"https://chat.indieweb.org/social/2017-11-15#t1510774596509000\">Tantek</a>)</p>",
"text": "Testing whether my new Webmention implementation, lazymention (which will ship Real Soon Now\u2122), will send a Webmention to note that I will NOT be attending today's Homebrew Website Club San Francisco! Though let's be honest, I really want to.\n(With <3 for Tantek)"
},
"name": "Not going to today's HWC San Francisco",
"_id": "123845",
"_source": "227",
"_is_read": true
}
Had a great time at Refresh Austin tonight. Good to hear what other people are up to, and share a little about what’s going on with Micro.blog and the upcoming IndieWebCamp Austin.
{
"type": "entry",
"author": {
"name": "manton",
"url": "http://www.manton.org",
"photo": null
},
"url": "http://www.manton.org/2017/11/6022.html",
"content": {
"html": "<p>Had a great time at Refresh Austin tonight. Good to hear what other people are up to, and share a little about what\u2019s going on with Micro.blog and the upcoming IndieWebCamp Austin.</p>",
"text": "Had a great time at Refresh Austin tonight. Good to hear what other people are up to, and share a little about what’s going on with Micro.blog and the upcoming IndieWebCamp Austin."
},
"published": "2017-11-15T04:57:10+00:00",
"updated": "2017-11-15T04:57:10+00:00",
"_id": "126",
"_source": "12",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "manton",
"url": "http://www.manton.org",
"photo": null
},
"url": "http://www.manton.org/2017/11/6010.html",
"content": {
"html": "<p>Great to see new apps for posting to Micro.blog and IndieWeb-enabled sites. <a href=\"https://eddiehinkle.com/2017/11/10/5/article/\">Here\u2019s some info</a> for the Indigenous iOS app beta.</p>",
"text": "Great to see new apps for posting to Micro.blog and IndieWeb-enabled sites. Here’s some info for the Indigenous iOS app beta."
},
"published": "2017-11-13T19:24:28+00:00",
"updated": "2017-11-13T19:24:28+00:00",
"_id": "131",
"_source": "12",
"_is_read": true
}
Okay, this is somewhat odd …it looked like I was getting spam webmentions from an escort agency to an old post of mine. It turns out that technically it’s not spam—they’re genuinely linking to my post from this post on their blog which is actually about webmentions.
And that, your honour, is how this site ended up in my browser history.
{
"type": "entry",
"published": "2017-11-13T09:07:20Z",
"url": "https://adactio.com/links/13090",
"category": [
"webmention",
"indieweb",
"pinging",
"comments",
"spam",
"sexworkers"
],
"bookmark-of": [
"https://www.midlandsmaidens-escorts.com/post-pinger/"
],
"content": {
"text": "Post Pinging and Webmentions at Midlands Maidens Nottingham Escorts\n\n \n\nOkay, this is somewhat odd \u2026it looked like I was getting spam webmentions from an escort agency to an old post of mine. It turns out that technically it\u2019s not spam\u2014they\u2019re genuinely linking to my post from this post on their blog which is actually about webmentions. \n\nAnd that, your honour, is how this site ended up in my browser history.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://www.midlandsmaidens-escorts.com/post-pinger/\">\nPost Pinging and Webmentions at Midlands Maidens Nottingham Escorts\n</a>\n</h3>\n\n<p>Okay, this is somewhat odd \u2026it looked like I was getting spam webmentions from an escort agency to <a href=\"https://adactio.com/journal/6469/\">an old post of mine</a>. It turns out that technically it\u2019s not spam\u2014they\u2019re genuinely linking to my post from this post on their blog which is actually about webmentions.</p>\n\n<p>And that, your honour, is how this site ended up in my browser history.</p>"
},
"_id": "20",
"_source": "2",
"_is_read": true
}
{
"type": "entry",
"url": "https://snarfed.org/2017-10-22_bridgy-fed",
"name": "Bridgy Fed",
"content": {
"text": "I\u2019m launching a new side project! Bridgy Fed connects your IndieWeb site with federated social networks like Mastodon and Hubzilla. If your site can send and receive webmentions, Bridgy Fed can federate it with the fediverse!\nI originally discovered the IndieWeb after I started connecting this web site with social networks like Facebook and Twitter. That led to Bridgy, which has grown bigger than I care to admit. I still have that desire to bridge different communities and networks, and Bridgy Fed is just the latest incarnation. Give it a whirl, kick the tires, and let me know what you think!",
"html": "<p>\n <a href=\"https://fed.brid.gy/\">\n <img src=\"https://snarfed.org/bridgy_fed.png\" alt=\"bridgy_fed.png\" /></a></p>\n<p>I\u2019m launching a new side project! <a href=\"https://fed.brid.gy/\">Bridgy Fed</a> connects your <a href=\"https://indieweb.org/\">IndieWeb</a> site with federated social networks like <a href=\"https://joinmastodon.org/\">Mastodon</a> and <a href=\"https://project.hubzilla.org/\">Hubzilla</a>. If your site can send and receive <a href=\"https://indieweb.org/webmention\">webmentions</a>, Bridgy Fed can federate it with the <a href=\"https://en.wikipedia.org/wiki/Fediverse\">fediverse</a>!</p>\n<p>I originally discovered the IndieWeb after I started <a href=\"https://snarfed.org/2011-07-27_facebook_app_for_ostatus\">connecting this web site</a> with social networks like Facebook and Twitter. That led to <a href=\"https://brid.gy/\">Bridgy</a>, which has grown bigger than I care to admit. I still have that desire to bridge different communities and networks, and Bridgy Fed is just the latest incarnation. Give it a whirl, kick the tires, and <a href=\"https://github.com/snarfed/bridgy-fed/issues\">let me know what you think</a>!</p>\n<ul><li><a class=\"u-syndication\" href=\"https://news.indieweb.org/en/snarfed.org/2017-10-22_bridgy-fed\"> </a></li></ul>"
},
"author": {
"type": "card",
"name": "Ryan Barrett",
"url": "https://snarfed.org/",
"photo": "https://secure.gravatar.com/avatar/947b5f3f323da0ef785b6f02d9c265d6?s=96&d=blank&r=g"
},
"_id": "41",
"_source": "3",
"_is_read": true
}
{
"type": "entry",
"published": "2017-10-09T19:50:03+0000",
"url": "https://seblog.nl/2017/10/09/9/bookmarks-and-likes",
"category": [
"indieweb"
],
"syndication": [
"https://news.indieweb.org/en/seblog.nl/2017/10/09/9/bookmarks-and-likes"
],
"name": "Thinking about bookmarks and likes on the IndieWeb",
"content": {
"text": "At Virtual HWC last week, Sven Knebel pointed me to the new Firefox beta. I use it now, and one of the things I noticed is that ships with integration with Pocket, a bookmarking service to save articles you want to read later. It\u2019s owned by Mozilla now, so they accentuate their service by adding a button prominently in your address bar.\nDespite the pushiness, I tested it out a bit. I like that I can save articles with one click, so I can read them later, possibly on a different device. It made me think about the way I post bookmarks on my own site.\nMy bookmarks and likes look too similar\nThe way I have implemented bookmarks at this moment, is very, very similar to the way I implemented likes. It is a Microformats property (u-bookmark-of vs u-like-of), displayed as an icon (a grey bookmark vs a red heart), with a Dutch text (\u2018Seb heeft [dit] gebookmarkt.\u2019 vs \u2018Seb vindt [dit] leuk.\u2019). \nBy making bookmarks and likes this similar, one would almost think that there is a clearly defined difference in the words \u2018bookmark\u2019 and \u2018like\u2019, that keep them apart, since there is no other distinction. I don\u2019t think there is such a definition.\nBookmarks are mostly used as a \u2018want to read\u2019-list, or a way of keeping track of things that have been read, but might be of interest on a later moment (\u2018want to read again\u2019). Likes are more a reply of some sorts, directed at the author of the post, expressing appreciation.\nThe problem comes when I take readers of my blog into account. The things I like, might be read as a recommendation, but the things I bookmark, might also read as a recommendation. Once I start looking from that perspective, likes and bookmarks fulfill the same role again.\nWhen likes and bookmarks are not recommendations\nSometimes I like things on social media, not because of the contents of the post, but because of the social context around the post. I do not really like the bad picture of the malformed pizza of a friend, I like the fact that I recognize that pizza as the outcome of the enthusiastic plans about making a pizza that my friend told me about earlier that day. I sometimes don\u2019t like the specific check-in a person posted, I just like the person. Some tweets are also quite ambigu: do I like the tweet because of the tweet, or because of the linked article I might or might not have read?\nThose likes are not recommendations for readers, they are purely appreciation, or even just social acknowledgement. Within a certain social context they can be of value to other people, but to random strangers, they are not. Currently, I solve this problem by not posting those kinds of likes to my site at all (leaving them on Facebook or whatever silo), but that\u2019s of course not ideal in the IndieWeb scheme of things.\nWith bookmarks, a similar thing can happen: not all bookmarks are recommendations. The easiest example is an article that I think looks interesting, so I bookmark it to read it later, but I haven\u2019t read it yet. I do not recommend that article, but a reader might think that.\nIn both cases: sometimes I do want to recommend an article in a single post.\nWhat I don\u2019t want to propose\nLet me make a little pause here and say something about likes, favorites, recommendations and what more. We can solve the above things by just adding more webactions to the field. \u201cLet\u2019s also support, next to bookmarks and likes, favorites and recommendations.\u201d But I don\u2019t think that\u2019s the solution, because adding those options means just more post types to keep track of, for both publishing sites and consuming indie-readers. \nKeeping things a little bit abstract and minimal helps us focus on the problem at hand. (Which is at this moment, I think, building an functioning indie-reader in the first place.)\nWhat I would add to my bookmarks\nSeeing what Pocket does with bookmarks, I think I want to expand what I post as a bookmark. To be fair: a lot of other people on the IndieWeb have more detailed bookmarks too. Other properties of a bookmark include: tags, a little summary of the bookmarked post, the reason why the post was bookmarked and sometimes even a screenshot of the bookmarked page.\nI\u2019m not sure how much I want to add to them, but since they are very skinny now, I certainly would like to add some tags. Tags, and possible a reason, make it easier to find a bookmarked article back after a while.\nThat brings me to what I think a bookmark would be for me: showing an interest in the linked article, without adding too much judgement. I see bookmarks as a personal archive of things I want to read or have read. If technical skills allow it, I would also save a copy of the post for personal use, hidden in the bookmark-post itself.\nWhat I would change to likes\nTo likes I wouldn\u2019t change much. For likes, I want to make a personal copy of the original too, because I do care about that content, but from the outside, it\u2019s just a link. \nBut the value of the like would than be more of a vote: this is a piece of content I care about. I think indie-readers should also consume those likes, but just don\u2019t display them the way they display a photo or a note. If there is a post by an author that I don\u2019t follow, but that is liked by, say, three people I do follow, then I want to see that post, accompanied by the names of the three people who liked it. \nThe threshold for the external posts to show up may vary from person to person, both personal preferences of the reader as well as the status of the poster of the like. But the point is that it\u2019s a indie-reader-problem. \nIn this way, a like is in fact a recommendation, from the readers perspective, but just appreciation from the poster.\nBut back to these social likes\nThen there are still those likes that depend on some social context, that aren\u2019t solved by the above approaches.\nI think that the root of the problem lies in those exact words: social context. If I like a certain badly photographed pizza, I should not post that to my main feed, but set the visibility of that like to \u2018friends only\u2019. Chances are that the badly photographed pizza was already published as a private post, only visible to a certain audience, so I can copy that. \nThe problem here lies more in an easy way of publishing private posts, and an easy way to change the audience of those posts. And of course a way for sites to securely share those posts with the right indie-readers, there is a long way to go still.\nAnd what about the bookmarks you haven\u2019t read?\nSharing unread bookmarks is also, I think, question of adding the right audience to the post. Such bookmarks can be posted with an \u2018only me\u2019 visibility. You can then subscribe your indie-reader to your own (private and public) bookmarks-feed. This is, without the private part, what I actually did for a while when I was using an indie-reader. Apart from the bugs in my self-build reader, it worked very well.\nAnd really recommending something? Well, if I really want to recommend something to people who follow me, I can always just post a note, linking the article, and explain why they should read it. That also improves the chance of actually clicking through, no need for extra formatting.\nConclusion\nIn the end I don\u2019t think we need better boundaries between a bookmark and a like, in the form of extra \u2018recommend\u2019 or \u2018favorite\u2019 webactions. A bookmark adds something to an archive for yourself, and a like is giving appreciation to the creator of the post. Recommendations can be either explicit by posting a note, or implicit by publicly liking or bookmarking. But, the way this is implied should be the responsibility of your indie-reader, where you can mix to your own taste. Publishers could filter things that they don\u2019t want everybody to pick up as recommendations by using \u2018only friends\u2019, \u2018only who I follow\u2019 or \u2018only me\u2019 posts.\nIn the end of the day, this is a lot of thinking and talking. I should get back to creating a indie-reader. As should you, because that\u2019s where the one of the undefined parts of the IndieWeb lies now.",
"html": "<p>At Virtual HWC last week, <a href=\"http://svenknebel.de\">Sven Knebel</a> pointed me to the new Firefox beta. I use it now, and one of the things I noticed is that ships with integration with <a href=\"https://getpocket.com/\">Pocket</a>, a bookmarking service to save articles you want to read later. It\u2019s owned by Mozilla now, so they accentuate their service by adding a button prominently in your address bar.</p>\n<p>Despite the pushiness, I tested it out a bit. I like that I can save articles with one click, so I can read them later, possibly on a different device. It made me think about the way I post bookmarks on my own site.</p>\n<h2>My bookmarks and likes look too similar</h2>\n<p>The way I have implemented bookmarks at this moment, is very, very similar to the way I implemented likes. It is a Microformats property (<code>u-bookmark-of</code> vs <code>u-like-of</code>), displayed as an icon (a grey bookmark vs a red heart), with a Dutch text (\u2018Seb heeft [dit] gebookmarkt.\u2019 vs \u2018Seb vindt [dit] leuk.\u2019). </p>\n<p>By making bookmarks and likes this similar, one would almost think that there is a clearly defined difference in the words \u2018bookmark\u2019 and \u2018like\u2019, that keep them apart, since there is no other distinction. I don\u2019t think there is such a definition.</p>\n<p>Bookmarks are mostly used as a \u2018want to read\u2019-list, or a way of keeping track of things that have been read, but might be of interest on a later moment (\u2018want to read again\u2019). Likes are more a reply of some sorts, directed at the author of the post, expressing appreciation.</p>\n<p>The problem comes when I take readers of my blog into account. The things I like, might be read as a recommendation, but the things I bookmark, might also read as a recommendation. Once I start looking from that perspective, likes and bookmarks fulfill the same role again.</p>\n<h2>When likes and bookmarks are not recommendations</h2>\n<p>Sometimes I like things on social media, not because of the contents of the post, but because of the social context around the post. I do not really like the bad picture of the malformed pizza of a friend, I like the fact that I recognize that pizza as the outcome of the enthusiastic plans about making a pizza that my friend told me about earlier that day. I sometimes don\u2019t like the specific check-in a person posted, I just like the person. Some tweets are also quite ambigu: do I like the tweet because of the tweet, or because of the linked article I might or might not have read?</p>\n<p>Those likes are not recommendations for readers, they are purely appreciation, or even just social acknowledgement. Within a certain social context they can be of value to other people, but to random strangers, they are not. Currently, I solve this problem by not posting those kinds of likes to my site at all (leaving them on Facebook or whatever silo), but that\u2019s of course not ideal in the IndieWeb scheme of things.</p>\n<p>With bookmarks, a similar thing can happen: not all bookmarks are recommendations. The easiest example is an article that I think looks interesting, so I bookmark it to read it later, but I haven\u2019t read it yet. I do not recommend that article, but a reader might think that.</p>\n<p>In both cases: sometimes I do want to recommend an article in a single post.</p>\n<h2>What I don\u2019t want to propose</h2>\n<p>Let me make a little pause here and say something about likes, favorites, recommendations and what more. We can solve the above things by just adding more webactions to the field. \u201cLet\u2019s also support, next to bookmarks and likes, favorites and recommendations.\u201d But I don\u2019t think that\u2019s the solution, because adding those options means just more post types to keep track of, for both publishing sites and consuming indie-readers. </p>\n<p>Keeping things a little bit abstract and minimal helps us focus on the problem at hand. (Which is at this moment, I think, building an functioning indie-reader in the first place.)</p>\n<h2>What I would add to my bookmarks</h2>\n<p>Seeing what Pocket does with bookmarks, I think I want to expand what I post as a bookmark. To be fair: a lot of other people on the IndieWeb have more detailed bookmarks too. Other properties of a bookmark include: tags, a little summary of the bookmarked post, the reason why the post was bookmarked and sometimes even a screenshot of the bookmarked page.</p>\n<p>I\u2019m not sure how much I want to add to them, but since they are very skinny now, I certainly would like to add some tags. Tags, and possible a reason, make it easier to find a bookmarked article back after a while.</p>\n<p>That brings me to what I think a bookmark would be for me: showing an interest in the linked article, without adding too much judgement. I see bookmarks as a personal archive of things I want to read or have read. If technical skills allow it, I would also save a copy of the post for personal use, hidden in the bookmark-post itself.</p>\n<h2>What I would change to likes</h2>\n<p>To likes I wouldn\u2019t change much. For likes, I want to make a personal copy of the original too, because I do care about that content, but from the outside, it\u2019s just a link. </p>\n<p>But the value of the like would than be more of a vote: this is a piece of content I care about. I think indie-readers should also consume those likes, but just don\u2019t display them the way they display a photo or a note. If there is a post by an author that I don\u2019t follow, but that is liked by, say, three people I do follow, then I want to see that post, accompanied by the names of the three people who liked it. </p>\n<p>The threshold for the external posts to show up may vary from person to person, both personal preferences of the reader as well as the status of the poster of the like. But the point is that it\u2019s a indie-reader-problem. </p>\n<p>In this way, a like is in fact a recommendation, from the readers perspective, but just appreciation from the poster.</p>\n<h2>But back to these social likes</h2>\n<p>Then there are still those likes that depend on some social context, that aren\u2019t solved by the above approaches.</p>\n<p>I think that the root of the problem lies in those exact words: social context. If I like a certain badly photographed pizza, I should not post that to my main feed, but set the visibility of that like to \u2018friends only\u2019. Chances are that the badly photographed pizza was already published as a private post, only visible to a certain audience, so I can copy that. </p>\n<p>The problem here lies more in an easy way of publishing private posts, and an easy way to change the audience of those posts. And of course a way for sites to securely share those posts with the right indie-readers, there is a long way to go still.</p>\n<h2>And what about the bookmarks you haven\u2019t read?</h2>\n<p>Sharing unread bookmarks is also, I think, question of adding the right audience to the post. Such bookmarks can be posted with an \u2018only me\u2019 visibility. You can then subscribe your indie-reader to your own (private and public) bookmarks-feed. This is, without the private part, what I actually did for a while when I was using an indie-reader. Apart from the bugs in my self-build reader, it worked very well.</p>\n<p>And really recommending something? Well, if I really want to recommend something to people who follow me, I can always just post a note, linking the article, and explain why they should read it. That also improves the chance of actually clicking through, no need for extra formatting.</p>\n<h2>Conclusion</h2>\n<p>In the end I don\u2019t think we need better boundaries between a bookmark and a like, in the form of extra \u2018recommend\u2019 or \u2018favorite\u2019 webactions. A bookmark adds something to an archive for yourself, and a like is giving appreciation to the creator of the post. Recommendations can be either explicit by posting a note, or implicit by publicly liking or bookmarking. But, the way this is implied should be the responsibility of your indie-reader, where you can mix to your own taste. Publishers could filter things that they don\u2019t want everybody to pick up as recommendations by using \u2018only friends\u2019, \u2018only who I follow\u2019 or \u2018only me\u2019 posts.</p>\n<p>In the end of the day, this is a lot of thinking and talking. I should get back to creating a indie-reader. As should you, because that\u2019s where the one of the undefined parts of the IndieWeb lies now.</p>"
},
"post-type": "article",
"_id": "1367154",
"_source": "1366",
"_is_read": true
}
