@davemillar Hey, David, are you still planning on coming to IndieWebCamp Austin? Would be great to see you there! https://2019.indieweb.org/austin
{ "type": "entry", "published": "2019-02-11 13:46-0800", "url": "https://gregorlove.com/2019/02/hey-david-are-you-still/", "syndication": [ "https://twitter.com/gRegorLove/status/1095076753310183424" ], "content": { "text": "@davemillar Hey, David, are you still planning on coming to IndieWebCamp Austin? Would be great to see you there! https://2019.indieweb.org/austin", "html": "<p>@davemillar Hey, David, are you still planning on coming to IndieWebCamp Austin? Would be great to see you there! <a href=\"https://2019.indieweb.org/austin\">https://2019.indieweb.org/austin</a></p>" }, "author": { "type": "card", "name": "gRegor Morrill", "url": "https://gregorlove.com/", "photo": "https://aperture-proxy.p3k.io/929c8777d059069a2a16a064d96f4c29b65548f8/68747470733a2f2f677265676f726c6f76652e636f6d2f736974652f6173736574732f66696c65732f333437332f70726f66696c652d323031362d6d65642e6a7067" }, "post-type": "note", "_id": "2142290", "_source": "95", "_is_read": true }
{ "type": "entry", "author": { "name": "mail@petermolnar.net (Peter Molnar)", "url": "https://petermolnar.net/feed/", "photo": null }, "url": "https://petermolnar.net/web-of-the-machines/", "published": "2019-02-10T20:10:00+00:00", "content": { "html": "<img src=\"https://aperture-proxy.p3k.io/8bd62c333e30a6b45914afd4cc43b3912857b305/68747470733a2f2f70657465726d6f6c6e61722e6e65742f666565642f7264662d69742d646f65732d6e6f742d737061726b2d6a6f792e6a7067\" alt=\"working with RDF - this one does not spark joy\" />working with RDF - this one does not spark joy<p>I want to say it all started with a rather offensive tweet<a href=\"https://petermolnar.net/feed/#fn1\">1</a>, but it wouldn\u2019t be true. No, it all started with my curiosity to please the Google Structured Data testing tool<a href=\"https://petermolnar.net/feed/#fn2\">2</a>. Last year, in August, I added microdata<a href=\"https://petermolnar.net/feed/#fn3\">3</a> to my website - it was more or less straightforward to do so.</p>\n<p>Except it was ugly, and, after half a year, I\u2019m certain to say, quite useless. I got no pretty Google cards - maybe because I refuse to do AMP<a href=\"https://petermolnar.net/feed/#fn4\">4</a>, maybe because I\u2019m not important enough, who knows. But by the time I was reaching this conclusion, that aforementioned tweet happened, and I got caught up in Semantic Hell, also known as arguing about RDF.</p>\n<p>The first time I heard about the Semantic Web collided with the dawn of the web 2.0 hype, so it wasn\u2019t hard to dismiss it when so much was happening. I was rather new to the whole web thing, and most of the academic discussions were not even available in Hungarian.</p>\n<p>In that thread, it pointed out to me that what I have on my site is microdata, not RDFa - I genuinely thought they are more or less interchangeable: both can use the same vocabulary, so it shouldn\u2019t really matter which HTML properties I use, should it? Well, it does, but I believe the basis for my confusion can be found in the microdata description: it was an initiative to make RDF simple enough for people making websites.</p>\n<p>If you\u2019re just as confused as I was, in my own words:</p>\n<ul><li><strong>RDF</strong> is a ruleset framework, which is <strong>only used to describe sets of rules</strong></li>\n<li>these rules are named <strong>vocabularies</strong>: Schema.org, Dublin Core, Open Graph (<em>the not-invented-here is strong in Facebook</em>), FOAF (<em>for the sake of your own sanity, don\u2019t read the FOAF doc, unless you already know how to greet Shub-Niggurath or what geekcode is/was</em>), etc</li>\n<li>if you try to use multiple vocabularies at once - which you can -, it will be incredibly hard to remember when to use what</li>\n<li>a vocabulary is what you can actually add to your data - machines then go to the RDF definition of the vocabulary make databases out of the data</li>\n<li><strong>microdata</strong> is <code>itemprop</code>, <code>itemscope</code>, <code>itemtype</code> and <code>itemref</code> HTML5 attributes</li>\n<li>whereas <strong>RDFa</strong> is <code>vocab</code>, <code>typeof</code>, <code>property</code> HTML5 attributes</li>\n<li>if you want to please academics or some sort of internal tool that is built to utlize RDF, use RDFa - I keep asking if RDFa vocabularies, such as Dublin Core, are consumed by anything on the public internet, but I keep getting answers<a href=\"https://petermolnar.net/feed/#fn5\">5</a> with no actual answers</li>\n<li>if you\u2019re doing this for a search engine, stick to microdata, it\u2019s less prone to errors\u2026</li>\n<li>.. or just do <strong>JSON-LD</strong>, which is JSON with special keys: <code>@context</code>, which points to a vocabulary, and <code>@type</code>, which points you to a vocabulary element, and these two define what your data keys should be named and what kind of data they might contain</li>\n</ul><p>With all this now known, I tried to turn mark up my content as microformats v1, microformats v2, and RDFa.</p>\n<p>I already had errors with microdata\u2026</p>\n<a href=\"https://petermolnar.net/web-of-the-machines/gsdtt_microdata_error_01_b.png\"> <img src=\"https://aperture-proxy.p3k.io/ac2aee208cce936e718df92f11e04a4e38a3c059/68747470733a2f2f70657465726d6f6c6e61722e6e65742f7765622d6f662d7468652d6d616368696e65732f67736474745f6d6963726f646174615f6572726f725f30312e706e67\" title=\"gsdtt_microdata_error_01\" alt=\"gsdtt_microdata_error_01\" /></a>\n\nInteresting, it has some problems\u2026\n<a href=\"https://petermolnar.net/web-of-the-machines/gsdtt_microdata_error_02_b.png\"> <img src=\"https://aperture-proxy.p3k.io/370f10a7e762e6ccaf4328b04e30a76b1225a8cb/68747470733a2f2f70657465726d6f6c6e61722e6e65742f7765622d6f662d7468652d6d616368696e65732f67736474745f6d6963726f646174615f6572726f725f30322e706e67\" title=\"gsdtt_microdata_error_02\" alt=\"gsdtt_microdata_error_02\" /></a>\n\nit says URL for org is missing\u2026 it\u2019s there. Line 13.\n<p>\u2026but those errors then became ever more peculiar problems with RDFa\u2026</p>\n<a href=\"https://petermolnar.net/web-of-the-machines/gsdtt_rdfa_error_01_b.png\"> <img src=\"https://aperture-proxy.p3k.io/2607fbcfb0443d64c6e219c30c26bc397bf8276c/68747470733a2f2f70657465726d6f6c6e61722e6e65742f7765622d6f662d7468652d6d616368696e65732f67736474745f726466615f6572726f725f30312e706e67\" title=\"gsdtt_rdfa_error_01\" alt=\"gsdtt_rdfa_error_01\" /></a>\n\nUndefined type, eh?\n<a href=\"https://petermolnar.net/web-of-the-machines/gsdtt_rdfa_error_02_b.png\"> <img src=\"https://aperture-proxy.p3k.io/c8a01ebee0bdc161376d425b7fe921e926836a27/68747470733a2f2f70657465726d6f6c6e61722e6e65742f7765622d6f662d7468652d6d616368696e65732f67736474745f726466615f6572726f725f30322e706e67\" title=\"gsdtt_rdfa_error_02\" alt=\"gsdtt_rdfa_error_02\" /></a>\n\nwat\n<p>\u2026 while microformats v1 was parsed without any glitches. <em>Sidenote: <strong>microformats</strong> (v1 and v2), unlike the previous things, are extra HTML <code>class</code> data, and v1 is still parsed by most search engines.</em></p>\n<p><strong>At this point I gave up on RDFa and moved over to test JSON-LD.</strong></p>\n<p>It\u2019s surprisingly easy to represent data in JSON-LD with schema.org context (<em>vocabulary, why on earth was vocabulary renamed to context?! Oh. Because we\u2019re in hell.</em>). There\u2019s a long entry about why JSON-LD happened<a href=\"https://petermolnar.net/feed/#fn6\">6</a> and it has a lot of reasonable points.</p>\n<p>What it forgets to talk about is that JSON-LD is an invisible duplication of what is either already or what should be in HTML. It\u2019s a decent way to store data, to exchange data, but not to present it to someone on the other end of the cable.</p>\n<p>The most common JSON-LD vocabulary, Schema.org has it\u2019s own interesting world of problems. It wants to be a single point of entry, one gigantic vocabulary, for anything web, a humongous task and noble goal. However, it\u2019s still lacking a lot of definitions (<em>ever tried to represent a resume with it?</em>), it has weird quirks (<em>\u2018follows\u2019 on a Person can only be another Person, it can\u2019t be a Brand, a WebSite, or a simple URL</em>) and it\u2019s driven heavily by Google (<em>most people working on it are working at Google</em>).</p>\n<p>I ended up with compromises.</p>\n<pre><code><html lang=\"en\" prefix=\"og: http://ogp.me/ns# article: http://ogp.me/ns/article#\">\n<head>\n <title>A piece of Powerscourt Waterfall - petermolnar.net</title>\n<!-- JSON-LD as alternative -->\n <link rel=\"alternate\" type=\"application/json\" title=\"a-piece-of-powerscourt-waterfall JSON-LD\" href=\"https://petermolnar.net/a-piece-of-powerscourt-waterfall/index.json\" />\n<!-- Open Graph vocabulary RDFa -->\n <meta property=\"og:title\" content=\"A piece of Powerscourt Waterfall\" />\n <meta property=\"og:type\" content=\"article\" />\n <meta property=\"og:url\" content=\"https://petermolnar.net/a-piece-of-powerscourt-waterfall/\" />\n <meta property=\"og:description\" content=\"\" />\n <meta property=\"article:published_time\" content=\"2017-11-09T18:00:00+00:00\" />\n <meta property=\"article:modified_time\" content=\"2019-01-05T11:52:47.543053+00:00\" />\n <meta property=\"article:author\" content=\"Peter Molnar (mail@petermolnar.net)\" />\n <meta property=\"og:image\" content=\"https://petermolnar.net/a-piece-of-powerscourt-waterfall/a-piece-of-powerscourt-waterfall_b.jpg\" />\n <meta property=\"og:image:type\" content=\"image/jpeg\" />\n <meta property=\"og:image:width\" content=\"1280\" />\n <meta property=\"og:image:height\" content=\"847\" />\n<!-- the rest of meta and header elements -->\n<!-- followed by the content, with microformats v1 and v2 markup --></code></pre>\n<p>HTML provides an interesting functionality, the <code>rel=alternate</code>. This is meant to be the representation of the same data, but in another format. The most common use is links to RSS and Atom feeds.</p>\n<p>I don\u2019t know if Google will consume the JSON-LD alternate format, but it\u2019s there, any anyone can easily use it.</p>\n<p>As for RDFa, I turned to <code>meta</code> elements. Unlike with JSON-LD, I decided to use the extremely simple vocabulary of Open Graph - at least Facebook is known to consume that.</p>\n<p><strong>The tragedy of this whole story: HTML5 has so many tags that is should be possible to do structured data without any need for any of the things above.</strong></p>\n<p>My content is now:</p>\n<ul><li>microformats v1 and v2 within the visible content</li>\n<li>a minimal RDFa in <code>meta</code> tags</li>\n<li>a sidecar JSON-LD version</li>\n</ul><p>This way it\u2019s simple, but compatible enough for most cases.</p>\n\n\n<ol><li><p><a href=\"https://twitter.com/csarven/status/1091314310465421312\">https://twitter.com/csarven/status/1091314310465421312</a><a href=\"https://petermolnar.net/feed/#fnref1\">\u21a9</a></p></li>\n<li><p><a href=\"https://search.google.com/structured-data/testing-tool\">https://search.google.com/structured-data/testing-tool</a><a href=\"https://petermolnar.net/feed/#fnref2\">\u21a9</a></p></li>\n<li><p><a href=\"https://twitter.com/csarven/status/1091314310465421312\">https://twitter.com/csarven/status/1091314310465421312</a><a href=\"https://petermolnar.net/feed/#fnref3\">\u21a9</a></p></li>\n<li><p><a href=\"https://www.ampproject.org/\">https://www.ampproject.org/</a><a href=\"https://petermolnar.net/feed/#fnref4\">\u21a9</a></p></li>\n<li><p><a href=\"https://twitter.com/RubenVerborgh/status/1092029740364587008\">https://twitter.com/RubenVerborgh/status/1092029740364587008</a><a href=\"https://petermolnar.net/feed/#fnref5\">\u21a9</a></p></li>\n<li><p><a href=\"http://manu.sporny.org/2014/json-ld-origins-2/\">http://manu.sporny.org/2014/json-ld-origins-2/</a><a href=\"https://petermolnar.net/feed/#fnref6\">\u21a9</a></p></li>\n</ol>", "text": "working with RDF - this one does not spark joyI want to say it all started with a rather offensive tweet1, but it wouldn\u2019t be true. No, it all started with my curiosity to please the Google Structured Data testing tool2. Last year, in August, I added microdata3 to my website - it was more or less straightforward to do so.\nExcept it was ugly, and, after half a year, I\u2019m certain to say, quite useless. I got no pretty Google cards - maybe because I refuse to do AMP4, maybe because I\u2019m not important enough, who knows. But by the time I was reaching this conclusion, that aforementioned tweet happened, and I got caught up in Semantic Hell, also known as arguing about RDF.\nThe first time I heard about the Semantic Web collided with the dawn of the web 2.0 hype, so it wasn\u2019t hard to dismiss it when so much was happening. I was rather new to the whole web thing, and most of the academic discussions were not even available in Hungarian.\nIn that thread, it pointed out to me that what I have on my site is microdata, not RDFa - I genuinely thought they are more or less interchangeable: both can use the same vocabulary, so it shouldn\u2019t really matter which HTML properties I use, should it? Well, it does, but I believe the basis for my confusion can be found in the microdata description: it was an initiative to make RDF simple enough for people making websites.\nIf you\u2019re just as confused as I was, in my own words:\nRDF is a ruleset framework, which is only used to describe sets of rules\nthese rules are named vocabularies: Schema.org, Dublin Core, Open Graph (the not-invented-here is strong in Facebook), FOAF (for the sake of your own sanity, don\u2019t read the FOAF doc, unless you already know how to greet Shub-Niggurath or what geekcode is/was), etc\nif you try to use multiple vocabularies at once - which you can -, it will be incredibly hard to remember when to use what\na vocabulary is what you can actually add to your data - machines then go to the RDF definition of the vocabulary make databases out of the data\nmicrodata is itemprop, itemscope, itemtype and itemref HTML5 attributes\nwhereas RDFa is vocab, typeof, property HTML5 attributes\nif you want to please academics or some sort of internal tool that is built to utlize RDF, use RDFa - I keep asking if RDFa vocabularies, such as Dublin Core, are consumed by anything on the public internet, but I keep getting answers5 with no actual answers\nif you\u2019re doing this for a search engine, stick to microdata, it\u2019s less prone to errors\u2026\n.. or just do JSON-LD, which is JSON with special keys: @context, which points to a vocabulary, and @type, which points you to a vocabulary element, and these two define what your data keys should be named and what kind of data they might contain\nWith all this now known, I tried to turn mark up my content as microformats v1, microformats v2, and RDFa.\nI already had errors with microdata\u2026\n \n\nInteresting, it has some problems\u2026\n \n\nit says URL for org is missing\u2026 it\u2019s there. Line 13.\n\u2026but those errors then became ever more peculiar problems with RDFa\u2026\n \n\nUndefined type, eh?\n \n\nwat\n\u2026 while microformats v1 was parsed without any glitches. Sidenote: microformats (v1 and v2), unlike the previous things, are extra HTML class data, and v1 is still parsed by most search engines.\nAt this point I gave up on RDFa and moved over to test JSON-LD.\nIt\u2019s surprisingly easy to represent data in JSON-LD with schema.org context (vocabulary, why on earth was vocabulary renamed to context?! Oh. Because we\u2019re in hell.). There\u2019s a long entry about why JSON-LD happened6 and it has a lot of reasonable points.\nWhat it forgets to talk about is that JSON-LD is an invisible duplication of what is either already or what should be in HTML. It\u2019s a decent way to store data, to exchange data, but not to present it to someone on the other end of the cable.\nThe most common JSON-LD vocabulary, Schema.org has it\u2019s own interesting world of problems. It wants to be a single point of entry, one gigantic vocabulary, for anything web, a humongous task and noble goal. However, it\u2019s still lacking a lot of definitions (ever tried to represent a resume with it?), it has weird quirks (\u2018follows\u2019 on a Person can only be another Person, it can\u2019t be a Brand, a WebSite, or a simple URL) and it\u2019s driven heavily by Google (most people working on it are working at Google).\nI ended up with compromises.\n<html lang=\"en\" prefix=\"og: http://ogp.me/ns# article: http://ogp.me/ns/article#\">\n<head>\n <title>A piece of Powerscourt Waterfall - petermolnar.net</title>\n<!-- JSON-LD as alternative -->\n <link rel=\"alternate\" type=\"application/json\" title=\"a-piece-of-powerscourt-waterfall JSON-LD\" href=\"https://petermolnar.net/a-piece-of-powerscourt-waterfall/index.json\" />\n<!-- Open Graph vocabulary RDFa -->\n <meta property=\"og:title\" content=\"A piece of Powerscourt Waterfall\" />\n <meta property=\"og:type\" content=\"article\" />\n <meta property=\"og:url\" content=\"https://petermolnar.net/a-piece-of-powerscourt-waterfall/\" />\n <meta property=\"og:description\" content=\"\" />\n <meta property=\"article:published_time\" content=\"2017-11-09T18:00:00+00:00\" />\n <meta property=\"article:modified_time\" content=\"2019-01-05T11:52:47.543053+00:00\" />\n <meta property=\"article:author\" content=\"Peter Molnar (mail@petermolnar.net)\" />\n <meta property=\"og:image\" content=\"https://petermolnar.net/a-piece-of-powerscourt-waterfall/a-piece-of-powerscourt-waterfall_b.jpg\" />\n <meta property=\"og:image:type\" content=\"image/jpeg\" />\n <meta property=\"og:image:width\" content=\"1280\" />\n <meta property=\"og:image:height\" content=\"847\" />\n<!-- the rest of meta and header elements -->\n<!-- followed by the content, with microformats v1 and v2 markup -->\nHTML provides an interesting functionality, the rel=alternate. This is meant to be the representation of the same data, but in another format. The most common use is links to RSS and Atom feeds.\nI don\u2019t know if Google will consume the JSON-LD alternate format, but it\u2019s there, any anyone can easily use it.\nAs for RDFa, I turned to meta elements. Unlike with JSON-LD, I decided to use the extremely simple vocabulary of Open Graph - at least Facebook is known to consume that.\nThe tragedy of this whole story: HTML5 has so many tags that is should be possible to do structured data without any need for any of the things above.\nMy content is now:\nmicroformats v1 and v2 within the visible content\na minimal RDFa in meta tags\na sidecar JSON-LD version\nThis way it\u2019s simple, but compatible enough for most cases.\n\n\nhttps://twitter.com/csarven/status/1091314310465421312\u21a9\nhttps://search.google.com/structured-data/testing-tool\u21a9\nhttps://twitter.com/csarven/status/1091314310465421312\u21a9\nhttps://www.ampproject.org/\u21a9\nhttps://twitter.com/RubenVerborgh/status/1092029740364587008\u21a9\nhttp://manu.sporny.org/2014/json-ld-origins-2/\u21a9" }, "name": "A journey to the underworld that is RDF", "post-type": "article", "_id": "2123955", "_source": "268", "_is_read": true }
Just had a thought. I know you can run arbitrary Jekyll plugins in a GitHub action–I bet you can send/receive webmentions too!
{ "type": "entry", "published": "2019-02-10T14:02:26-05:00", "url": "https://miklb.com/blog/2019/02/10/4719/", "syndication": [ "https://twitter.com/miklb/status/1094672976925069312" ], "content": { "text": "Just had a thought. I know you can run arbitrary Jekyll plugins in a GitHub action\u2013I bet you can send/receive webmentions too!", "html": "<p>Just had a thought. I know you can run arbitrary Jekyll plugins in a GitHub action\u2013I bet you can send/receive webmentions too!\n</p>" }, "post-type": "note", "_id": "2123080", "_source": "42", "_is_read": true }
As the commercial viability of the web grew, we saw more and more users become consumers and not creators. Many consumers see websites as black boxes full of magic that they could never understand. Because of this, they would never think to try to create something.
This is a shame. We lost a little piece of the magic of the web when this culture came about.
A call to action to create a fan site about something you love. It would be an unmonetisable enthusiasm. But it’s still worth doing:
- The act of creation itself is fun!
- Sharing something you love with the world is worthwhile.
- You’ll learn something.
So here’s the challenge:
- Create a Fan Site.
- Help someone create a Fan Site.
- Create a webring.
{ "type": "entry", "published": "2019-02-09T17:24:41Z", "url": "https://adactio.com/links/14780", "category": [ "fansites", "webrings", "fun", "enjoyment", "making", "creating", "sharing", "publishing", "indieweb" ], "bookmark-of": [ "https://bryanlrobinson.com/blog/2019/02/07/bring-fansites-back-to-the-web/" ], "content": { "text": "Let\u2019s bring Fan Sites and webrings back! - bryanlrobinson.com\n\n\n\n\n As the commercial viability of the web grew, we saw more and more users become consumers and not creators. Many consumers see websites as black boxes full of magic that they could never understand. Because of this, they would never think to try to create something.\n \n This is a shame. We lost a little piece of the magic of the web when this culture came about.\n\n\nA call to action to create a fan site about something you love. It would be an unmonetisable enthusiasm. But it\u2019s still worth doing:\n\n\n The act of creation itself is fun!\n Sharing something you love with the world is worthwhile.\n You\u2019ll learn something.\n \n\nSo here\u2019s the challenge:\n\n\n Create a Fan Site.\n Help someone create a Fan Site.\n Create a webring.", "html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://bryanlrobinson.com/blog/2019/02/07/bring-fansites-back-to-the-web/\">\nLet\u2019s bring Fan Sites and webrings back! - bryanlrobinson.com\n</a>\n</h3>\n\n<blockquote>\n <p>As the commercial viability of the web grew, we saw more and more users become consumers and not creators. Many consumers see websites as black boxes full of magic that they could never understand. Because of this, they would never think to try to create something.</p>\n \n <p>This is a shame. We lost a little piece of the magic of the web when this culture came about.</p>\n</blockquote>\n\n<p>A call to action to create a fan site about something you love. It would be an <a href=\"https://www.wired.co.uk/article/obsessive-depth-of-the-internet\">unmonetisable enthusiasm</a>. But it\u2019s still worth doing:</p>\n\n<blockquote>\n <ol><li>The act of creation itself is fun!</li>\n <li>Sharing something you love with the world is worthwhile.</li>\n <li>You\u2019ll learn something.</li>\n </ol></blockquote>\n\n<p>So here\u2019s the challenge:</p>\n\n<blockquote>\n <ol><li>Create a Fan Site.</li>\n <li>Help someone create a Fan Site.</li>\n <li>Create a webring.</li>\n </ol></blockquote>" }, "author": { "type": "card", "name": "Jeremy Keith", "url": "https://adactio.com/", "photo": "https://aperture-proxy.p3k.io/bbbacdf0a064621004f2ce9026a1202a5f3433e0/68747470733a2f2f6164616374696f2e636f6d2f696d616765732f70686f746f2d3135302e6a7067" }, "post-type": "bookmark", "_id": "2112084", "_source": "2", "_is_read": true }
IndieWebCamp Austin is in 2 weeks! Whether you’re a blogger, developer, designer, or just want to learn more about the independent web, hope you can join us. Registration is just $5 or free if you blog your RSVP to the event.
{ "type": "entry", "author": { "name": "Manton Reece", "url": "https://www.manton.org/", "photo": "https://aperture-proxy.p3k.io/907926e361383204bd1bc913c143c23e70ae69bb/68747470733a2f2f6d6963726f2e626c6f672f6d616e746f6e2f6176617461722e6a7067" }, "url": "https://www.manton.org/2019/02/08/indiewebcamp-austin-is.html", "content": { "html": "<p><a href=\"https://2019.indieweb.org/austin\">IndieWebCamp Austin</a> is in 2 weeks! Whether you\u2019re a blogger, developer, designer, or just want to learn more about the independent web, hope you can join us. Registration is just $5 or free if you blog your RSVP to the event.</p>", "text": "IndieWebCamp Austin is in 2 weeks! Whether you\u2019re a blogger, developer, designer, or just want to learn more about the independent web, hope you can join us. Registration is just $5 or free if you blog your RSVP to the event." }, "published": "2019-02-08T13:53:51-06:00", "post-type": "note", "_id": "2101755", "_source": "12", "_is_read": true }
My first IndieWebCamp Online. The first one in ~5 years, in fact! Let’s build fun personal things for the web, together!
{ "type": "entry", "published": "2019-02-08T13:17:36-0500", "rsvp": "yes", "url": "https://martymcgui.re/2019/02/08/131736/", "in-reply-to": [ "https://2019.indieweb.org/online" ], "content": { "text": "I'm going!My first IndieWebCamp Online. The first one in ~5 years, in fact! Let\u2019s build fun personal things for the web, together!", "html": "I'm going!<p>My first IndieWebCamp Online. The first one in ~5 years, in fact! Let\u2019s build fun personal things for the web, together!</p>" }, "author": { "type": "card", "name": "Marty McGuire", "url": "https://martymcgui.re/", "photo": "https://aperture-proxy.p3k.io/8275f85e3a389bd0ae69f209683436fc53d8bad9/68747470733a2f2f6d617274796d636775692e72652f696d616765732f6c6f676f2e6a7067" }, "post-type": "rsvp", "refs": { "https://2019.indieweb.org/online": { "type": "entry", "summary": "IndieWebCamp Online 2019 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.", "url": "https://2019.indieweb.org/online", "name": "IndieWebCamp Online", "author": { "type": "card", "name": "2019.indieweb.org", "url": "http://2019.indieweb.org", "photo": null }, "post-type": "note" } }, "_id": "2101410", "_source": "175", "_is_read": true }
{ "type": "entry", "published": "2019-02-06T22:13:15-05:00", "url": "https://eddiehinkle.com/2019/02/06/13/note/", "category": [ "indieweb", "indiewebcamp" ], "syndication": [ "https://micro.blog/EddieHinkle", "https://news.indieweb.org/en", "https://twitter.com/eddiehinkle" ], "content": { "text": "Registration for IndieWebCamp Online 2019 is open!, it's the first IndieWebCamp based on the internet since 2014 and we're experimenting with really embracing the internet medium for everything it has. Come experiment with us?", "html": "Registration for <a href=\"https://2019.indieweb.org/online\">IndieWebCamp Online 2019 is open!</a>, it's the first IndieWebCamp based on the internet since 2014 and we're experimenting with really embracing the internet medium for everything it has. Come experiment with us?" }, "author": { "type": "card", "name": "Eddie Hinkle", "url": "https://eddiehinkle.com/", "photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067" }, "post-type": "note", "_id": "2083023", "_source": "226", "_is_read": true }
{ "type": "entry", "author": { "name": null, "url": "https://herestomwiththeweather.com/", "photo": null }, "url": "https://herestomwiththeweather.com/2019/02/06/indiewebcamp-austin-2019/", "published": "2019-02-06T18:28:05+00:00", "content": { "html": "<p>RSVP yes to <a href=\"https://2019.indieweb.org/austin\">IndieWebCamp Austin 2019</a><a href=\"https://herestomwiththeweather.com/\"><img src=\"https://avatars2.githubusercontent.com/u/16299?v=3&s=460\" alt=\"16299?v=3&s=460\" />Tom Brown</a></p>", "text": "RSVP yes to IndieWebCamp Austin 2019Tom Brown" }, "name": "IndiewebCamp Austin 2019", "post-type": "article", "_id": "2082776", "_source": "246", "_is_read": true }
{ "type": "entry", "published": "2019-02-06 19:30-0800", "url": "http://tantek.com/2019/037/t2/scifi-variable-font-progressive-enhancement", "category": [ "indieweb", "scifi", "variablefont", "JS", "HTMLfirst", "CSS", "variablefonts", "typography" ], "content": { "text": "#indieweb HWCSF\n\n@beacrea https://coty.design showed #scifi #variablefont https://www.readvisions.com/marvin\n\nCool scrolling & hover effects with #JS, still renders beautifully without JS. Good progressive enhancement. #HTMLfirst #CSS #variablefonts #typography", "html": "#<span class=\"p-category\">indieweb</span> HWCSF<br /><br /><a class=\"h-cassis-username\" href=\"https://twitter.com/beacrea\">@beacrea</a> https://coty.design showed #<span class=\"p-category\">scifi</span> #<span class=\"p-category\">variablefont</span> <a href=\"https://www.readvisions.com/marvin\">https://www.readvisions.com/marvin</a><br /><br />Cool scrolling & hover effects with #<span class=\"p-category\">JS</span>, still renders beautifully without JS. Good progressive enhancement. #<span class=\"p-category\">HTMLfirst</span> #<span class=\"p-category\">CSS</span> #<span class=\"p-category\">variablefonts</span> #<span class=\"p-category\">typography</span>" }, "author": { "type": "card", "name": "Tantek \u00c7elik", "url": "http://tantek.com/", "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg" }, "post-type": "note", "_id": "2082376", "_source": "1", "_is_read": true }
{ "type": "entry", "published": "2019-02-06 18:57-0800", "url": "http://tantek.com/2019/037/t1/javascript-required-didnt-render", "category": [ "indieweb", "js" ], "content": { "text": "#indieweb Homebrew Website Club @MozSF:\n\n@jackyalcine (nice site: https://jacky.wtf) came up with a great backronym for \"js;dr\":\n\nJavaScript [required]; Didn\u2019t Render\n\nOriginal #js;dr dfn: tantek.com/2015/069/t1/js-dr-javascript-required-dead (https://twitter.com/t/status/575434935554584576)", "html": "#<span class=\"p-category\">indieweb</span> Homebrew Website Club <a class=\"h-cassis-username\" href=\"https://twitter.com/MozSF\">@MozSF</a>:<br /><br /><a class=\"h-cassis-username\" href=\"https://twitter.com/jackyalcine\">@jackyalcine</a> (nice site: <a href=\"https://jacky.wtf\">https://jacky.wtf</a>) came up with a great backronym for \"js;dr\":<br /><br />JavaScript [required]; Didn\u2019t Render<br /><br />Original #<span class=\"p-category\">js</span>;dr dfn: <a href=\"http://tantek.com/2015/069/t1/js-dr-javascript-required-dead\">tantek.com/2015/069/t1/js-dr-javascript-required-dead</a> (<a href=\"https://twitter.com/t/status/575434935554584576\">https://twitter.com/t/status/575434935554584576</a>)" }, "author": { "type": "card", "name": "Tantek \u00c7elik", "url": "http://tantek.com/", "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg" }, "post-type": "note", "_id": "2082377", "_source": "1", "_is_read": true }
{ "type": "entry", "author": { "name": "Kh\u00fcrt Williams", "url": "https://islandinthenet.com/", "photo": null }, "url": "https://islandinthenet.com/indiewebcamp/", "published": "2019-02-07T03:52:44+00:00", "content": { "html": "Attending <a href=\"https://2019.indieweb.org/online\">IndieWebCamp Online</a>\n<blockquote>IndieWebCamp Online 2019 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.</blockquote>", "text": "Attending IndieWebCamp Online\nIndieWebCamp Online 2019 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." }, "name": "IndieWebCamp", "post-type": "note", "_id": "2081964", "_source": "242", "_is_read": true }
{ "type": "entry", "published": "2019-02-06T18:48:29-0500", "url": "https://martymcgui.re/2019/02/06/hwc-nyc-wrap-up-2019-02-06/", "category": [ "HWC", "NYC", "IndieWeb", "wrap-up" ], "name": "HWC NYC Wrap-Up 2019-02-06", "content": { "text": "New York City's first Homebrew Website Club of 2019 met at Aroma Espresso Bar on February 6th.\nHere are some notes from the \"broadcast\" portion of the meetup.\n\n rootedfromnature.com \u2014 Was working on a Grav skeleton... thinking of throwing it out. Had a client site that received some praise, though! Spent some time this evening looking at flights to Germany\n \n\n\n aaronparecki.com \u2014 Was working on fixing Quill's URL resolution for IndieAuth login (e.g. so you can login with a shortdomain like aaronpk.com and have it resolve to https://aaronparecki.com/). Got distracted by Marty showing an iOS Shortcut that works like Teacup to post ate/drank posts via Micropub. Made an iOS shortcut to allow him to upload videos to his site.\n \n\n\n martymcgui.re \u2014 Spent quiet hour porting some old notes out of Evernote-like browser-based app Laverna into his personal notes site. Just housekeepin'. Current personal site project is probably getting event hosting up for his upcoming improv and livestreaming shows.\n \n\n\n david.shanske.com \u2014 Wrote a post saying something is ready to test. Current project for his site: everything. Took a break for a few days and doesn't know what is next.\n \n\nOther discussions:\n\n Aaron's cool tiny gimbal / timelapse camera\n \n\n Looking at flights to Germany for IWCs\n Bus vs subway/rail/driving between Manhattan and Queens\n What do you mean this coffee shop's hours have changed to close at 7pm?\n \n There's a Starbucks like two blocks away, I guess.\n \n\n\n Thanks to everyone who came out! We look forward to seeing you at our next meetup on Wednesday, February 20th at 6:30pm!", "html": "<p>New York City's <a href=\"https://indieweb.org/events/2019-02-06-homebrew-website-club-nyc\">first Homebrew Website Club of 2019</a> met at <a href=\"http://www.aroma.us/\">Aroma Espresso Bar</a> on February 6th.</p>\n<p>Here are some notes from the \"broadcast\" portion of the meetup.</p>\n<p>\n rootedfromnature.com \u2014 Was working on a Grav skeleton... thinking of throwing it out. Had a client site that received some praise, though! Spent some time this evening looking at flights to Germany\n <br /></p>\n<p>\n aaronparecki.com \u2014 Was working on fixing Quill's URL resolution for IndieAuth login (e.g. so you can login with a shortdomain like aaronpk.com and have it resolve to https://aaronparecki.com/). Got distracted by Marty showing an iOS Shortcut that works like Teacup to post ate/drank posts via Micropub. Made an iOS shortcut to allow him to upload videos to his site.\n <br /></p>\n<p>\n martymcgui.re \u2014 Spent quiet hour porting some old notes out of Evernote-like browser-based app Laverna into his personal notes site. Just housekeepin'. Current personal site project is probably getting event hosting up for his upcoming improv and livestreaming shows.\n <br /></p>\n<p>\n david.shanske.com \u2014 Wrote a post saying something is ready to test. Current project for his site: everything. Took a break for a few days and doesn't know what is next.\n <br /></p>\n<p>Other discussions:</p>\n<ul><li>\n Aaron's cool tiny gimbal / timelapse camera\n <br /></li>\n <li>Looking at flights to Germany for IWCs</li>\n <li>Bus vs subway/rail/driving between Manhattan and Queens</li>\n <li>What do you mean this coffee shop's hours have changed to close at 7pm?</li>\n <li>\n There's a Starbucks like two blocks away, I guess.\n <br /></li>\n</ul><img src=\"https://aperture-proxy.p3k.io/8a5560eae00ec92bb8a0d71ede8cfaac3920836b/68747470733a2f2f6d656469612e6d617274796d636775692e72652f38302f65612f63352f63652f64343466353031346361323935393134623665343736653132376564353738326538616334393636393063336633353764643762623462652e6a7067\" alt=\"\" /><p>\n Thanks to everyone who came out! We look forward to seeing you at our next meetup on Wednesday, February 20th at 6:30pm!\n <br /></p>" }, "author": { "type": "card", "name": "Marty McGuire", "url": "https://martymcgui.re/", "photo": "https://aperture-proxy.p3k.io/8275f85e3a389bd0ae69f209683436fc53d8bad9/68747470733a2f2f6d617274796d636775692e72652f696d616765732f6c6f676f2e6a7067" }, "post-type": "article", "_id": "2080465", "_source": "175", "_is_read": true }
Homebrew Website Club is 6:30pm at Mozart’s Coffee tonight. We’ll be talking about final plans for IndieWebCamp Austin. Registration for the Feb 23-24 event is open now.
{ "type": "entry", "author": { "name": "Manton Reece", "url": "https://www.manton.org/", "photo": "https://aperture-proxy.p3k.io/907926e361383204bd1bc913c143c23e70ae69bb/68747470733a2f2f6d6963726f2e626c6f672f6d616e746f6e2f6176617461722e6a7067" }, "url": "https://www.manton.org/2019/02/06/homebrew-website-club.html", "content": { "html": "<p>Homebrew Website Club is 6:30pm at Mozart\u2019s Coffee tonight. We\u2019ll be talking about final plans for IndieWebCamp Austin. Registration for the Feb 23-24 event <a href=\"https://2019.indieweb.org/austin\">is open now</a>.</p>", "text": "Homebrew Website Club is 6:30pm at Mozart\u2019s Coffee tonight. We\u2019ll be talking about final plans for IndieWebCamp Austin. Registration for the Feb 23-24 event is open now." }, "published": "2019-02-06T12:12:01-06:00", "post-type": "note", "_id": "2076132", "_source": "12", "_is_read": true }
{ "type": "entry", "published": "2019-02-06 00:54:23.464466", "url": "https://kongaloosh.com/e/2019/2/6/im-going-b", "name": "Software Rots: SCUBA Edition", "content": { "text": "I'm going back through my dive logbook after a three year diving hiatus. The software I use to track my dives has become an ungodly mess of company acquisitions and software maintenance. Turns out the company that made my dive-computer was bought out by scuba-pro.\nTo even get my hands on the software to open my dive-log file, I had to scour looking for a hidden link that would take me to the SmartTrak site. That wasn't even enough alone, I had to engage in browser witchcraft to coerce the site to not redirect me to scuba-pro's main site. The file is nowhere else, at least by my searching. Interesting that no one liked it enough to keep a mirror of it...\nOf course, the software didn't solve my problems. oh no. The dates were incorrect on some of my dives. Another example malady of poor software support: I could turn the background of dive profiles gradient olive green, but I could not edit basic dive info---e.g., the date and location of a dive. For the first-time in my life, I'm actually facing a deprecation of software that I need. It's important that I keep the data I collect when I'm diving.\nAfter going through old dev-forums and dive-forums, I found a converter which takes shameful SmartTrack files and converts them into a modified XML for use with SubSurface. At least I can coerce the file into being read as XML, rather than proprietary nonsense. More than that, not only does sub-surface allow me to edit the date of a dive in increments greater than 7, I can edit multiple dives at the same time. \nIt's the future.\nI can't help but feel that this is a sort of digital vagrancy. SubSurface seems great now, but what about in 3 years? 10 years? I know there's a trend of web-based dive-logs, but I don't want to have to shuffle around, converting what has no business being anything but XML or a CSV to bunch of proprietary, uninterpretable file formats. \nHaving been burnt by SmartTrack, I'm looking for robust export functionality. Luck for me, it seems sub-surface is able to export as CSVs. This seems like a clear candidate to make a stand and own my own data.\nIt's just screaming to be added to the blog. \nThen if something breaks, it's my own damn fault.\n \n\n \n\n \n\n\n \n \n \n \n \n diving\n \n dev\n \n indieweb\n \n article", "html": "<p class=\"e-content\"></p><p>I'm going back through my dive logbook after a three year diving hiatus. The software I use to track my dives has become an ungodly mess of company acquisitions and software maintenance. Turns out the company that made my dive-computer was bought out by scuba-pro.</p>\n<p>To even get my hands on the software to open my dive-log file, I had to scour looking for a hidden link that would take me to the SmartTrak site. That wasn't even enough alone, I had to engage in browser witchcraft to coerce the site to not redirect me to scuba-pro's main site. The file is <em>nowhere else</em>, at least by my searching. Interesting that no one liked it enough to keep a mirror of it...</p>\n<p>Of course, the software didn't solve my problems. <em>oh no</em>. The dates were incorrect on some of my dives. Another example malady of poor software support: I could turn the background of dive profiles <em>gradient olive green</em>, but I could not edit basic dive info---e.g., the date and location of a dive. For the first-time in my life, I'm actually facing a deprecation of software that I <em>need</em>. It's important that I keep the data I collect when I'm diving.</p>\n<p>After going through old dev-forums and <a href=\"https://www.scubaboard.com/community/threads/smart-trak-to-logtrak-import.546613/page-2\">dive-forums</a>, I found <a href=\"https://thetheoreticaldiver.org/rch-cgi-bin/smtk2ssrf.pl\">a converter</a> which takes shameful SmartTrack files and converts them into a modified XML for use with <a href=\"https://subsurface-divelog.org/download/\">SubSurface</a>. At least I can coerce the file into being read as XML, rather than proprietary nonsense. More than that, not only does sub-surface allow me to edit the date of a dive in increments greater than 7, I can edit <em>multiple</em> dives at the same time. </p>\n<p>It's the future.</p>\n<p>I can't help but feel that this is a sort of digital vagrancy. SubSurface seems great now, but what about in 3 years? 10 years? I know there's a trend of web-based <a href=\"https://en.divelogs.de/\">dive-logs</a>, but I don't want to have to shuffle around, converting what has no business being anything but XML or a CSV to bunch of proprietary, uninterpretable file formats. </p>\n<p>Having been burnt by SmartTrack, I'm looking for robust export functionality. Luck for me, it seems sub-surface is able to export as CSVs. This seems like a clear candidate to make a stand and own my own data.</p>\n<p>It's just screaming to be added to the blog. \nThen if something breaks, it's my own damn fault.</p>\n \n\n \n\n \n\n\n \n \n \n <i></i>\n \n <a href=\"https://kongaloosh.com/t/diving\">diving</a>\n \n <a href=\"https://kongaloosh.com/t/dev\">dev</a>\n \n <a href=\"https://kongaloosh.com/t/indieweb\">indieweb</a>\n \n <a href=\"https://kongaloosh.com/t/article\">article</a>" }, "author": { "type": "card", "name": "Alex Kearney", "url": "http://kongaloosh.com", "photo": null }, "post-type": "article", "_id": "2070368", "_source": "228", "_is_read": true }
{ "type": "entry", "author": { "name": "cdevroe", "url": "http://cdevroe.com/author/cdevroe/", "photo": "http://0.gravatar.com/avatar/c248217e9cdc83ce95acc615199ce57f?s=512&d=http://cdevroe.com/wp-content/plugins/semantic-linkbacks/img/mm.jpg&r=g" }, "url": "http://cdevroe.com/2019/02/05/manton-interview-2019/", "name": "A new interview with Manton Reece of Micro.blog for 2019", "content": { "html": "<p>Last year, around this time, <a href=\"http://cdevroe.com/2018/01/19/interview-manton/\">I published an interview</a> with <a href=\"http://manton.org\">Manton Reece</a> \u2013 founder of <a href=\"http://micro.blog\">Micro.blog</a> (M.b) \u2013 about how the platform was growing and what the goals for 2018 were. It was such a great interview and it helped me to understand the direction that M.b was going that I knew I had to interview him again to check in for 2019.</p>\n\n\n\n<p>Answering these questions isn\u2019t easy. Manton and I have been volleying back and forth for about 60 days for this interview to come to this point. So before we jump into the interview I just want to take a moment to thank Manton for taking the time to thoughtfully respond to my questions. I hope the entire M.b community enjoys this interview and it helps to give an idea of what is happening there and where the community and platform are headed.</p>\n\n\n\n<p>I\u2019ve tried to include links to most everything we mention so that you\u2019re able to find all of the little tidbits. If I missed anything, leave a comment or reply on M.b and I\u2019ll try to track down what you\u2019re looking for.</p>\n\n\n\n<p>Now, onto the interview:</p>\n\n\n\n<p><strong>Thank you again Manton for taking some time to answer my questions. <a href=\"http://cdevroe.com/2018/01/19/interview-manton/\">Last year\u2019s interview</a> was fun so I thought it\u2019d be a good idea to revisit a few of the topics in it and also catch up with you on how Micro.blog is doing and see where it is headed in 2019. Last year you mentioned that most of the growth on the team would come in the form of curators or support. Has the team grown? If so, what does the team look like today and what will it look like in 2019?</strong></p>\n\n\n\n<p><strong>Manton:</strong> Great to talk to you again! The size of the team has not grown since last year, but I think we\u2019ve done more with the people we have. <a href=\"https://micro.blog/macgenie\">Jean MacDonald</a> has hosted over 40 episodes of our <a href=\"https://monday.micro.blog/\">Micro Monday podcast</a>, and <a href=\"https://micro.blog/cheesemaker\">Jon Hays</a> has lead recent improvements to our iOS app and new apps <a href=\"https://sunlit.io/\">Sunlit</a> and <a href=\"https://help.micro.blog/2018/wavelength/\">Wavelength</a>. I still expect the growth to be on the curation side and hope that can be a focus of 2019. Where the other big social networks try to use algorithms to solve problems, we think if you want a great community, humans need to be actively involved \u2014 featuring content, listening for problems, and thinking about the impact of new features.</p>\n\n\n\n<p>Customer support and system administration are the other areas that I\u2019m looking forward to getting help with, but as the platform evolves it\u2019s still valuable for me to be handling most of that myself. I hear from customers every day about what they love and what features are missing. Since we last talked, I\u2019ve also moved <a href=\"http://manton.org\">my primary blog</a> with thousands of posts from WordPress to Micro.blog hosting, and that has been a great way to prioritize improvements to the hosting part of the platform. Blog hosting is the actual business of Micro.blog and enables us to do everything else we want to do for the social network and community.</p>\n\n\n\n<p><strong>From an outsider\u2019s perspective, I don\u2019t know how you\u2019re able to do as much as you do! You are coding Micro.blog, keeping up with the infrastructure software/hardware, dealing with support, paying the bills\u2026 the list goes on and on. Then, on top of all that, you\u2019re building a few iOS apps like Sunlit and Wavelength. You also have your own podcast called <a href=\"https://timetable.manton.org/\">Timetable</a> and a long-running podcast called <a href=\"https://coreint.org/\">Core Intuition</a>. Not to mention your personal blog, <a href=\"http://help.micro.blog/\">help documents for Micro.blog</a>, and keeping up with the community and <a href=\"https://micro.blog/slack\">the Slack channel</a>.</strong></p>\n\n\n\n<p><strong>How do you prioritize all of this? Is one project more important than another?</strong></p>\n\n\n\n<p><strong>Manton:</strong> I think good things can come from trying to do a little too much, but it\u2019s not usually sustainable. Eventually it catches up with you and you have to simplify and wrap up or delegate some tasks. We are in that kind of period right now with Micro.blog. We will continue to do a lot, but some parts of the platform \u2014 like the iOS apps \u2014 can reach a point of maturity where we work on stability improvements and polishing existing features rather than adding brand new features.</p>\n\n\n\n<p>Android is another good example. Many people ask for an official Android app for Micro.blog. Because I don\u2019t have much Android experience myself, I know I would be stretched too thin right now to tackle it, so we are encouraging third-party solutions instead. There\u2019s a new version of <a href=\"https://dialogapp.net/\">Dialog</a> for Android which has full support for the Micro.blog timeline, posting, replying, the Discover sections, and more. I\u2019m really excited about it.</p>\n\n\n\n<p>The most important project is the Micro.blog web platform, because without that foundation nothing else is possible. Improving <a href=\"https://help.micro.blog/2018/api-overview/\">the API</a> and blog hosting will always be something we work on, alongside other priorities that come and go.</p>\n\n\n\n<p><strong>I for one am very happy that Dialog exists. I\u2019m also happy that it is pretty good too. What other third-party projects have you come across that more people should know about? And, what haven\u2019t you seen made on top of Micro.blog that you wish existed?</strong></p>\n\n\n\n<p><strong>Manton:</strong> People should keep an eye on <a href=\"https://vincentritter.com/apps\">Gluon</a>, which is in development now for iOS and Android. I\u2019ve enjoyed reading developer <a href=\"https://vincentritter.com/2019/01/29/gluon-a-new-beginning\">Vincent Ritter\u2019s blog post updates</a> about working on it \u2014 the early choices he made on how to build the app and later decisions to update the UI and rewrite portions of it.</p>\n\n\n\n<p>Integrating other platforms is another area that is great for third-party apps. For example, IndieWeb-compatible tools like <a href=\"https://ownyourgram.com/\">OwnYourGram</a> (for copying Instagram posts to your blog) or <a href=\"https://indiebookclub.biz/\">IndieBookClub</a> (for posting about books you\u2019re reading or want to read). Having so many third-party apps that can supplement the basic features on Micro.blog means that we can keep the primary experience as streamlined as possible, because the goal is to make blogging easier. I\u2019d love to see more advanced tools for managing posts as well, such as batch editing posts or for import and export.</p>\n\n\n\n<p><strong>Switching gears for a moment to Micro.blog\u2019s long term financial sustainability. I know at first there was a funding push related to the Kickstarter campaign, and of course there are those that pay a few dollars per year for the hosted service or other features like cross posting. What does long term sustainability look like for Micro.blog? Does there need to be a lot of growth in the customer base? How else can people like me, who use Micro.blog daily but are not currently paying, help keep Micro.blog funded?</strong></p>\n\n\n\n<p><strong>Manton:</strong> Kickstarter was perfect to get us started, but paid subscriptions are better long term. I want to build features that are valuable and worth paying for. So we\u2019ll keep making our blog hosting more compelling so that it\u2019s good for people who are just getting started with a new blog, or people who want to migrate from other platforms. We often see people who might have a primary blog on WordPress \u2014 and a secondary microblog or photo blog on Micro.blog \u2014 decide that it\u2019s simpler to just consolidate everything to Micro.blog, importing their WordPress posts. We don\u2019t expect all the millions of bloggers who host on WordPress to move over to Micro.blog, but even a relatively small number moving to Micro.blog will make the platform more sustainable.</p>\n\n\n\n<p>We just rolled out several major new features for blog hosting, including categories and custom themes, so you can have full control over the HTML, CSS, and JavaScript on your site. You don\u2019t need to be a designer or developer to use Micro.blog, but it\u2019s nice to allow some more flexibility for those people who do want to tinker with their site. And now <a href=\"https://www.manton.org/2019/01/30/custom-templates-categories.html\">web developers can create custom themes for Micro.blog</a> that can be used by other members of the community.</p>\n\n\n\n<p>As for supporting Micro.blog if you aren\u2019t a paying customer, the best way is to tell people about it. All our growth right now is from word of mouth. It\u2019s great when people invite their friends from other social networks, or when they post about why they like Micro.blog on their own blog or talk about it on their podcast. You don\u2019t need to have a large audience to make a big difference.</p>\n\n\n\n<p><strong>I\u2019d be remiss to not mention the apparent resurgence of blogging. If not in action then in the collective consciousness. It seems many people are talking and writing about blogging lately. With Medium changing its policies, Tumblr being owned by Oath/Verizon/Aol, Twitter being a hive of villainy, Facebook selling our fears to our captors, and Instagram growing up to be like\u2019s its parent\u2026 it seems that blogging is poised to have a huge comeback. Are you doing anything at all to capture that momentum? Or, are you just trying to keep on your roadmap as usual?</strong></p>\n\n\n\n<p><strong>Manton:</strong> It feels like everything we\u2019ve been working toward for a few years is starting to come together, as more people realize the downsides of these massive, centralized platforms. Whether someone is quitting Facebook tomorrow or a year from now, I want Micro.blog to be a great default choice for reclaiming ownership of your content and getting in the habit of writing or posting photos regularly. When Basecamp recently migrated their long-running blog Signal v. Noise away from Medium, <a href=\"https://m.signalvnoise.com/signal-v-noise-exits-medium/\">they summed up the change just like we see it</a>: \u201cTraditional blogs might have swung out of favor,\u00a0as we all discovered the benefits of social media and aggregating platforms, but we think they\u2019re about to swing back in style, as we all discover the\u00a0real costs and problems brought by such centralization.\u201d</p>\n\n\n\n<p>The other part of this is to have a safe, welcoming community. I hate to see people get discouraged from blogging because \u201cno one\u201d is reading, so it helps that we have the Micro.blog timeline and replies where a blog post can start a conversation, or new posts can be featured in the Discover section.\u00a0I think 2019 is going to be great for blogging. Micro.blog differentiates itself because it offers a solution for both blog hosting and a great community.</p>\n\n\n\n<p><strong>Professional blogging; whether that be funded by advertisers, subscribers, fans \u2013 is a big business. What are your thoughts on how Micro.blog helps or ignores people or businesses that may want to use the platform to share their content and earn a living from it?</strong></p>\n\n\n\n<p><strong>Manton:</strong> Micro.blog was designed for people, not \u201cbrands\u201d, but there\u2019s no reason it can\u2019t be used for businesses as well. Toward the end of last year I wrote a \u201c12 days of microblogging\u201d blog post series, and on one day <a href=\"https://manton.org/2018/12/10/days-of-microblogging.html\">highlighted how businesses can use Micro.blog</a>.</p>\n\n\n\n<p>Personal blogs can evolve into a revenue source as well, like offering subscriptions or sponsorships. But Micro.blog will never have ads and we aren\u2019t likely to add features specifically for people to make money from their content in the way that Medium is trying to do. We want to focus on helping people discover blog posts, and whether someone monetizes their blog or uses it for occasional self-promotion is up to them. It\u2019s okay if most blogs are personal and non-commercial because that lends itself to authenticity, and there\u2019s great value in just having a space of your own to publish to.</p>\n\n\n\n<p>We also think podcasting is only going to get bigger, which is why our first new <a href=\"https://help.micro.blog/2018/pricing/\">paid plan</a> was microcast hosting for short-form podcasts. We keep increasing the limits and now you can publish even hour-long episodes to Micro.blog. Like personal blogs, podcasts could be sponsored, or they could be just for fun, or they could indirectly benefit your business, such as supplementing a blog or helping promote something else you\u2019re working on.</p>\n\n\n\n<p><strong>I believe you\u2019ve touched on open source regarding Micro.blog in the past. Some of your own projects, like JSON Feed, are open source. Will you be open sourcing Micro.blog or any pieces of it?</strong></p>\n\n\n\n<p><strong>Manton:</strong> I don\u2019t plan to open source all of Micro.blog in the near future. It\u2019s a complicated project with several components across multiple servers, so it\u2019s not really suitable for just \u201crunning yourself\u201d right now. However, I\u2019d love to open source more of it, especially when there\u2019s an immediate benefit to people. For example, for the new custom themes feature, I rewrote all of the themes to use the Hugo blogging engine, and <a href=\"https://github.com/microdotblog\">we\u2019ve shared all our changes on GitHub</a>. That\u2019s something people can use right away. Jon Hays also wrote a framework called <a href=\"https://github.com/microdotblog/snippets\">\u201cSnippets\u201d for the Micro.blog API and Micropub API</a> that we\u2019ll be using in our iOS apps, and we\u2019ve open sourced that as well. I think there is more in our iOS apps (including Wavelength for podcasts and Sunlit for photos) that would be great to open source.</p>\n\n\n\n<p><strong>I think I catch myself looking for a search feature on Micro.blog at least twice a week. For instance, I\u2019m big into houseplants lately and I wanted to find some people on M.b that were as well. And I can\u2019t figure out how to do that. Is search coming?</strong></p>\n\n\n\n<p>We now have <a href=\"https://micro.blog/discover/search?q=devroe\">a basic search on the web</a> version of Micro.blog under <a href=\"https://micro.blog/discover\">Discover</a>. This currently searches any post that has been included in Discover. We have plans to add search to the native apps so that it\u2019s easier to access, and expand it so that it searches even more posts on Micro.blog. However, one of the early design goals with Micro.blog was to launch without a full search index, because I didn\u2019t like how Twitter\u2019s search and especially trending topics could be gamed or expose the worst conversations on the platform, even in some cases being a place for more abusive, hateful replies. So we\u2019re going a little slowly with search to make sure that we don\u2019t recreate any of those problems.</p>\n\n\n\n<p><strong>I know I\u2019m only scratching the surface for the questions that the community is likely curious about. I hope I did an OK job asking the important ones. Are there any topics I left off that you wish I had asked you about? Or anything you\u2019d like to highlight?</strong></p>\n\n\n\n<p>Your questions were great. Thank you! I\u2019d like to mention again what Jean MacDonald has done with our podcast <a href=\"https://monday.micro.blog/\">Micro Monday</a>. This podcast didn\u2019t exist when you interviewed me last year, and now we have a great archive of episodes highlighting members of the community \u2014 how they got started blogging and what they are interested in, whether that\u2019s related to Micro.blog or something else. It helps people understand Micro.blog while at the same time featuring stories from the community. I\u2019m always inspired hearing what people are up to, and it\u2019s a weekly reminder to me of how important it is that people have a voice on the web with their own blog.</p>\n\n\n\n<p>What a fun interview! Until next year\u2026<br /></p>", "text": "Last year, around this time, I published an interview with Manton Reece – founder of Micro.blog (M.b) – about how the platform was growing and what the goals for 2018 were. It was such a great interview and it helped me to understand the direction that M.b was going that I knew I had to interview him again to check in for 2019.\n\n\n\nAnswering these questions isn’t easy. Manton and I have been volleying back and forth for about 60 days for this interview to come to this point. So before we jump into the interview I just want to take a moment to thank Manton for taking the time to thoughtfully respond to my questions. I hope the entire M.b community enjoys this interview and it helps to give an idea of what is happening there and where the community and platform are headed.\n\n\n\nI’ve tried to include links to most everything we mention so that you’re able to find all of the little tidbits. If I missed anything, leave a comment or reply on M.b and I’ll try to track down what you’re looking for.\n\n\n\nNow, onto the interview:\n\n\n\nThank you again Manton for taking some time to answer my questions. Last year\u2019s interview was fun so I thought it\u2019d be a good idea to revisit a few of the topics in it and also catch up with you on how Micro.blog is doing and see where it is headed in 2019. Last year you mentioned that most of the growth on the team would come in the form of curators or support. Has the team grown? If so, what does the team look like today and what will it look like in 2019?\n\n\n\nManton: Great to talk to you again! The size of the team has not grown since last year, but I think we’ve done more with the people we have. Jean MacDonald has hosted over 40 episodes of our Micro Monday podcast, and Jon Hays has lead recent improvements to our iOS app and new apps Sunlit and Wavelength. I still expect the growth to be on the curation side and hope that can be a focus of 2019. Where the other big social networks try to use algorithms to solve problems, we think if you want a great community, humans need to be actively involved \u2014 featuring content, listening for problems, and thinking about the impact of new features.\n\n\n\nCustomer support and system administration are the other areas that I’m looking forward to getting help with, but as the platform evolves it’s still valuable for me to be handling most of that myself. I hear from customers every day about what they love and what features are missing. Since we last talked, I’ve also moved my primary blog with thousands of posts from WordPress to Micro.blog hosting, and that has been a great way to prioritize improvements to the hosting part of the platform. Blog hosting is the actual business of Micro.blog and enables us to do everything else we want to do for the social network and community.\n\n\n\nFrom an outsider\u2019s perspective, I don\u2019t know how you\u2019re able to do as much as you do! You are coding Micro.blog, keeping up with the infrastructure software/hardware, dealing with support, paying the bills\u2026 the list goes on and on. Then, on top of all that, you\u2019re building a few iOS apps like Sunlit and Wavelength. You also have your own podcast called Timetable and a long-running podcast called Core Intuition. Not to mention your personal blog, help documents for Micro.blog, and keeping up with the community and the Slack channel.\n\n\n\nHow do you prioritize all of this? Is one project more important than another?\n\n\n\nManton: I think good things can come from trying to do a little too much, but it’s not usually sustainable. Eventually it catches up with you and you have to simplify and wrap up or delegate some tasks. We are in that kind of period right now with Micro.blog. We will continue to do a lot, but some parts of the platform \u2014 like the iOS apps \u2014 can reach a point of maturity where we work on stability improvements and polishing existing features rather than adding brand new features.\n\n\n\nAndroid is another good example. Many people ask for an official Android app for Micro.blog. Because I don’t have much Android experience myself, I know I would be stretched too thin right now to tackle it, so we are encouraging third-party solutions instead. There’s a new version of Dialog for Android which has full support for the Micro.blog timeline, posting, replying, the Discover sections, and more. I’m really excited about it.\n\n\n\nThe most important project is the Micro.blog web platform, because without that foundation nothing else is possible. Improving the API and blog hosting will always be something we work on, alongside other priorities that come and go.\n\n\n\nI for one am very happy that Dialog exists. I\u2019m also happy that it is pretty good too. What other third-party projects have you come across that more people should know about? And, what haven\u2019t you seen made on top of Micro.blog that you wish existed?\n\n\n\nManton: People should keep an eye on Gluon, which is in development now for iOS and Android. I’ve enjoyed reading developer Vincent Ritter’s blog post updates about working on it \u2014 the early choices he made on how to build the app and later decisions to update the UI and rewrite portions of it.\n\n\n\nIntegrating other platforms is another area that is great for third-party apps. For example, IndieWeb-compatible tools like OwnYourGram (for copying Instagram posts to your blog) or IndieBookClub (for posting about books you’re reading or want to read). Having so many third-party apps that can supplement the basic features on Micro.blog means that we can keep the primary experience as streamlined as possible, because the goal is to make blogging easier. I’d love to see more advanced tools for managing posts as well, such as batch editing posts or for import and export.\n\n\n\nSwitching gears for a moment to Micro.blog\u2019s long term financial sustainability. I know at first there was a funding push related to the Kickstarter campaign, and of course there are those that pay a few dollars per year for the hosted service or other features like cross posting. What does long term sustainability look like for Micro.blog? Does there need to be a lot of growth in the customer base? How else can people like me, who use Micro.blog daily but are not currently paying, help keep Micro.blog funded?\n\n\n\nManton: Kickstarter was perfect to get us started, but paid subscriptions are better long term. I want to build features that are valuable and worth paying for. So we’ll keep making our blog hosting more compelling so that it’s good for people who are just getting started with a new blog, or people who want to migrate from other platforms. We often see people who might have a primary blog on WordPress \u2014 and a secondary microblog or photo blog on Micro.blog \u2014 decide that it’s simpler to just consolidate everything to Micro.blog, importing their WordPress posts. We don’t expect all the millions of bloggers who host on WordPress to move over to Micro.blog, but even a relatively small number moving to Micro.blog will make the platform more sustainable.\n\n\n\nWe just rolled out several major new features for blog hosting, including categories and custom themes, so you can have full control over the HTML, CSS, and JavaScript on your site. You don’t need to be a designer or developer to use Micro.blog, but it’s nice to allow some more flexibility for those people who do want to tinker with their site. And now web developers can create custom themes for Micro.blog that can be used by other members of the community.\n\n\n\nAs for supporting Micro.blog if you aren’t a paying customer, the best way is to tell people about it. All our growth right now is from word of mouth. It’s great when people invite their friends from other social networks, or when they post about why they like Micro.blog on their own blog or talk about it on their podcast. You don’t need to have a large audience to make a big difference.\n\n\n\nI\u2019d be remiss to not mention the apparent resurgence of blogging. If not in action then in the collective consciousness. It seems many people are talking and writing about blogging lately. With Medium changing its policies, Tumblr being owned by Oath/Verizon/Aol, Twitter being a hive of villainy, Facebook selling our fears to our captors, and Instagram growing up to be like\u2019s its parent\u2026 it seems that blogging is poised to have a huge comeback. Are you doing anything at all to capture that momentum? Or, are you just trying to keep on your roadmap as usual?\n\n\n\nManton: It feels like everything we’ve been working toward for a few years is starting to come together, as more people realize the downsides of these massive, centralized platforms. Whether someone is quitting Facebook tomorrow or a year from now, I want Micro.blog to be a great default choice for reclaiming ownership of your content and getting in the habit of writing or posting photos regularly. When Basecamp recently migrated their long-running blog Signal v. Noise away from Medium, they summed up the change just like we see it: “Traditional blogs might have swung out of favor, as we all discovered the benefits of social media and aggregating platforms, but we think they\u2019re about to swing back in style, as we all discover the real costs and problems brought by such centralization.”\n\n\n\nThe other part of this is to have a safe, welcoming community. I hate to see people get discouraged from blogging because “no one” is reading, so it helps that we have the Micro.blog timeline and replies where a blog post can start a conversation, or new posts can be featured in the Discover section. I think 2019 is going to be great for blogging. Micro.blog differentiates itself because it offers a solution for both blog hosting and a great community.\n\n\n\nProfessional blogging; whether that be funded by advertisers, subscribers, fans \u2013 is a big business. What are your thoughts on how Micro.blog helps or ignores people or businesses that may want to use the platform to share their content and earn a living from it?\n\n\n\nManton: Micro.blog was designed for people, not “brands”, but there’s no reason it can’t be used for businesses as well. Toward the end of last year I wrote a “12 days of microblogging” blog post series, and on one day highlighted how businesses can use Micro.blog.\n\n\n\nPersonal blogs can evolve into a revenue source as well, like offering subscriptions or sponsorships. But Micro.blog will never have ads and we aren’t likely to add features specifically for people to make money from their content in the way that Medium is trying to do. We want to focus on helping people discover blog posts, and whether someone monetizes their blog or uses it for occasional self-promotion is up to them. It’s okay if most blogs are personal and non-commercial because that lends itself to authenticity, and there’s great value in just having a space of your own to publish to.\n\n\n\nWe also think podcasting is only going to get bigger, which is why our first new paid plan was microcast hosting for short-form podcasts. We keep increasing the limits and now you can publish even hour-long episodes to Micro.blog. Like personal blogs, podcasts could be sponsored, or they could be just for fun, or they could indirectly benefit your business, such as supplementing a blog or helping promote something else you’re working on.\n\n\n\nI believe you\u2019ve touched on open source regarding Micro.blog in the past. Some of your own projects, like JSON Feed, are open source. Will you be open sourcing Micro.blog or any pieces of it?\n\n\n\nManton: I don’t plan to open source all of Micro.blog in the near future. It’s a complicated project with several components across multiple servers, so it’s not really suitable for just “running yourself” right now. However, I’d love to open source more of it, especially when there’s an immediate benefit to people. For example, for the new custom themes feature, I rewrote all of the themes to use the Hugo blogging engine, and we’ve shared all our changes on GitHub. That’s something people can use right away. Jon Hays also wrote a framework called “Snippets” for the Micro.blog API and Micropub API that we’ll be using in our iOS apps, and we’ve open sourced that as well. I think there is more in our iOS apps (including Wavelength for podcasts and Sunlit for photos) that would be great to open source.\n\n\n\nI think I catch myself looking for a search feature on Micro.blog at least twice a week. For instance, I\u2019m big into houseplants lately and I wanted to find some people on M.b that were as well. And I can\u2019t figure out how to do that. Is search coming?\n\n\n\nWe now have a basic search on the web version of Micro.blog under Discover. This currently searches any post that has been included in Discover. We have plans to add search to the native apps so that it’s easier to access, and expand it so that it searches even more posts on Micro.blog. However, one of the early design goals with Micro.blog was to launch without a full search index, because I didn’t like how Twitter’s search and especially trending topics could be gamed or expose the worst conversations on the platform, even in some cases being a place for more abusive, hateful replies. So we’re going a little slowly with search to make sure that we don’t recreate any of those problems.\n\n\n\nI know I\u2019m only scratching the surface for the questions that the community is likely curious about. I hope I did an OK job asking the important ones. Are there any topics I left off that you wish I had asked you about? Or anything you\u2019d like to highlight?\n\n\n\nYour questions were great. Thank you! I’d like to mention again what Jean MacDonald has done with our podcast Micro Monday. This podcast didn’t exist when you interviewed me last year, and now we have a great archive of episodes highlighting members of the community \u2014 how they got started blogging and what they are interested in, whether that’s related to Micro.blog or something else. It helps people understand Micro.blog while at the same time featuring stories from the community. I’m always inspired hearing what people are up to, and it’s a weekly reminder to me of how important it is that people have a voice on the web with their own blog.\n\n\n\n\n\n\n\nWhat a fun interview! Until next year…" }, "published": "2019-02-05T13:47:10-05:00", "updated": "2019-02-05T14:56:04-05:00", "category": [ "android", "blogging", "dialog", "gluon", "interview", "ios", "jean macdonald", "manton reece", "medium", "micro.blog", "podcasting", "recommended", "sunlit", "vincent ritter", "wavelength", "wordpress" ], "post-type": "article", "_id": "2065407", "_source": "236", "_is_read": true }
I still can’t believe it’s February! IndieWebCamp Austin is coming up in just a few weeks. You can register here for $5. It’s a great time to learn more about the open web or get help with your own site.
{ "type": "entry", "author": { "name": "Manton Reece", "url": "https://www.manton.org/", "photo": "https://aperture-proxy.p3k.io/907926e361383204bd1bc913c143c23e70ae69bb/68747470733a2f2f6d6963726f2e626c6f672f6d616e746f6e2f6176617461722e6a7067" }, "url": "https://www.manton.org/2019/02/04/i-still-cant.html", "content": { "html": "<p>I still can\u2019t believe it\u2019s February! IndieWebCamp Austin is coming up in just a few weeks. <a href=\"http://2019.indieweb.org/austin\">You can register here</a> for $5. It\u2019s a great time to learn more about the open web or get help with your own site.</p>", "text": "I still can\u2019t believe it\u2019s February! IndieWebCamp Austin is coming up in just a few weeks. You can register here for $5. It\u2019s a great time to learn more about the open web or get help with your own site." }, "published": "2019-02-04T13:59:53-06:00", "post-type": "note", "_id": "2052698", "_source": "12", "_is_read": true }
Fixed posting from IndieWeb-compatible apps (such as OwnYourGram or IndieBookClub) if they sent categories along with the new post. I didn’t realize that OwnYourGram will automatically convert Instagram hashtags into blog post categories. Neat!
{ "type": "entry", "author": { "name": "Manton Reece", "url": "https://www.manton.org/", "photo": "https://aperture-proxy.p3k.io/907926e361383204bd1bc913c143c23e70ae69bb/68747470733a2f2f6d6963726f2e626c6f672f6d616e746f6e2f6176617461722e6a7067" }, "url": "https://www.manton.org/2019/02/02/fixed-posting-from.html", "content": { "html": "<p>Fixed posting from IndieWeb-compatible apps (such as OwnYourGram or IndieBookClub) if they sent categories along with the new post. I didn\u2019t realize that <a href=\"https://ownyourgram.com/\">OwnYourGram</a> will automatically convert Instagram hashtags into blog post categories. Neat!</p>", "text": "Fixed posting from IndieWeb-compatible apps (such as OwnYourGram or IndieBookClub) if they sent categories along with the new post. I didn\u2019t realize that OwnYourGram will automatically convert Instagram hashtags into blog post categories. Neat!" }, "published": "2019-02-02T14:46:21-06:00", "post-type": "note", "_id": "2029853", "_source": "12", "_is_read": true }
Today you may have seen SSL errors on my domain. No, my private keys are safe. It's just that my domain was put on parking since I have forgot to renew it. Thankfully, the issue is resolved. Long live my #indieweb site! #domains #security
{ "type": "entry", "published": "2019-01-31T21:21:34+03:00", "url": "https://fireburn.ru/note/1548958894", "category": [ "indieweb", "domains", "security", "None://fireburn.ru/tags/indieweb", "None://fireburn.ru/tags/domains", "None://fireburn.ru/tags/security" ], "syndication": [ "https://twitter.com/kisik21/status/1091038824514445314" ], "content": { "text": "Today you may have seen SSL errors on my domain. No, my private keys are safe. It's just that my domain was put on parking since I have forgot to renew it. Thankfully, the issue is resolved. Long live my #indieweb site! #domains #security", "html": "<p>Today you may have seen SSL errors on my domain. No, my private keys are safe. It's just that my domain was put on parking since I have forgot to renew it. Thankfully, the issue is resolved. Long live my <a class=\"u-category\">#indieweb</a> site! <a class=\"u-category\">#domains</a> <a class=\"u-category\">#security</a></p>" }, "author": { "type": "card", "name": "Vika", "url": "https://fireburn.ru/", "photo": "https://aperture-proxy.p3k.io/3baa9a034ae34d783c6de676c0304b7640673c03/68747470733a2f2f666972656275726e2e72752f617661746172732f76696b612e706e67" }, "post-type": "note", "_id": "2020855", "_source": "1371", "_is_read": true }
{ "type": "entry", "published": "2019-02-01 15:25-0800", "url": "http://tantek.com/2019/032/t2/simpler-more-inclusive-accessible-indieweb", "category": [ "microformats", "indieweb", "microformats2" ], "in-reply-to": [ "https://mxb.at/blog/on-simplicity/" ], "content": { "text": "Great @mxbck post On Simplicity https://mxb.at/blog/on-simplicity/ via @adactio\n\nAdditionally: simpler approaches are more inclusive & accessible, e.g. #microformats & #indieweb\n\nFewer abstractions = less to learn before getting started.\n\nSimpler = less time cost on plumbing, tooling; faster to build something more useful.\n\nLess time required = more tinkerable by more people, especially those with less spare time on the margins = more inclusive and accessible.\n\nThe @microformats and @indiewebcamp communities have deliberately chosen explicitly simpler approaches:\n* microformats.org/wiki/start-simple\n* making #microformats2 even simpler: microformats.org/wiki/microformats2-origins#can_we_make_the_simplest_case_simpler\n* The IndieWeb Building Blocks approach (https://indieweb.org/building-blocks) rather than a monolithic \"Stack\"\n\nChoosing explicitly simpler approaches is more than just being smart & efficient, it\u2019s ethically the right thing to do.\n\nSimpler is a sociopolitical choice to deliberately provide more creative agency to more people. Beyond just more usable by more people, simpler technologies enable more people to build, adapt, alter, evolve their own tools of creation, rather than depending on a select privileged few to do so.\n\nPreviously, previously:\n* tantek.com/2018/309/t1/complexity-reinforces-privilege\n* tantek.com/2010/034/t3/simplicity", "html": "Great <a class=\"h-cassis-username\" href=\"https://twitter.com/mxbck\">@mxbck</a> post On Simplicity <a href=\"https://mxb.at/blog/on-simplicity/\">https://mxb.at/blog/on-simplicity/</a> via <a class=\"h-cassis-username\" href=\"https://twitter.com/adactio\">@adactio</a><br /><br />Additionally: simpler approaches are more inclusive & accessible, e.g. #<span class=\"p-category\">microformats</span> & #<span class=\"p-category\">indieweb</span><br /><br />Fewer abstractions = less to learn before getting started.<br /><br />Simpler = less time cost on plumbing, tooling; faster to build something more useful.<br /><br />Less time required = more tinkerable by more people, especially those with less spare time on the margins = more inclusive and accessible.<br /><br />The <a class=\"h-cassis-username\" href=\"https://twitter.com/microformats\">@microformats</a> and <a class=\"h-cassis-username\" href=\"https://twitter.com/indiewebcamp\">@indiewebcamp</a> communities have deliberately chosen explicitly simpler approaches:<br />* <a href=\"http://microformats.org/wiki/start-simple\">microformats.org/wiki/start-simple</a><br />* making #<span class=\"p-category\">microformats2</span> even simpler: <a href=\"http://microformats.org/wiki/microformats2-origins#can_we_make_the_simplest_case_simpler\">microformats.org/wiki/microformats2-origins#can_we_make_the_simplest_case_simpler</a><br />* The IndieWeb Building Blocks approach (<a href=\"https://indieweb.org/building-blocks\">https://indieweb.org/building-blocks</a>) rather than a monolithic \"Stack\"<br /><br />Choosing explicitly simpler approaches is more than just being smart & efficient, it\u2019s ethically the right thing to do.<br /><br />Simpler is a sociopolitical choice to deliberately provide more creative agency to more people. Beyond just more usable by more people, simpler technologies enable more people to build, adapt, alter, evolve their own tools of creation, rather than depending on a select privileged few to do so.<br /><br />Previously, previously:<br />* <a href=\"http://tantek.com/2018/309/t1/complexity-reinforces-privilege\">tantek.com/2018/309/t1/complexity-reinforces-privilege</a><br />* <a href=\"http://tantek.com/2010/034/t3/simplicity\">tantek.com/2010/034/t3/simplicity</a>" }, "author": { "type": "card", "name": "Tantek \u00c7elik", "url": "http://tantek.com/", "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg" }, "post-type": "reply", "refs": { "https://mxb.at/blog/on-simplicity/": { "type": "entry", "url": "https://mxb.at/blog/on-simplicity/", "name": "mxb.at\u2019s post", "post-type": "article" } }, "_id": "2020845", "_source": "1", "_is_read": true }
{ "type": "entry", "published": "2019-02-01 14:13-0800", "url": "http://tantek.com/2019/032/t1/any-photos-wizardstower2019", "category": [ "wizardstower2019", "IndieWeb" ], "in-reply-to": [ "https://twitter.com/dustyweb/status/1091293951569641473" ], "content": { "text": "@dustyweb @sl007 great! Always awesome when hackathon demos work!\nAny photos from y\u2019all or the demo(s) at #wizardstower2019? \n\nIf you can post or link one in the next 30 min we should be able to get it into the This Week In The #IndieWeb newsletter.", "html": "<a class=\"h-cassis-username\" href=\"https://twitter.com/dustyweb\">@dustyweb</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/sl007\">@sl007</a> great! Always awesome when hackathon demos work!<br />Any photos from y\u2019all or the demo(s) at #<span class=\"p-category\">wizardstower2019</span>? <br /><br />If you can post or link one in the next 30 min we should be able to get it into the This Week In The #<span class=\"p-category\">IndieWeb</span> newsletter." }, "author": { "type": "card", "name": "Tantek \u00c7elik", "url": "http://tantek.com/", "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg" }, "post-type": "reply", "refs": { "https://twitter.com/dustyweb/status/1091293951569641473": { "type": "entry", "url": "https://twitter.com/dustyweb/status/1091293951569641473", "name": "@dustyweb\u2019s tweet", "post-type": "article" } }, "_id": "2019767", "_source": "1", "_is_read": true }