IndieWebCamps Timeline 2011-2019: Amsterdam to Utrecht

{
    "type": "entry",
    "published": "2019-08-16 14:21-0700",
    "url": "http://tantek.com/2019/228/b1/indiewebcamps-timeline-amsterdam-utrecht",
    "name": "IndieWebCamps Timeline 2011-2019: Amsterdam to Utrecht",
    "content": {
        "text": "While not a post directly about IndieWeb Summit 2019, this post provides a bit of background and is certainly related, so I\u2019m including it in my series of posts about the Summit. Previous post in this series: Reflecting On IndieWeb Summit: A Start\n\n\nAt the beginning of IndieWeb Summit 2019, I gave a brief talk on \nState of the IndieWeb and mentioned that:\n\nWe've scheduled lots of IndieWebCamps this year and are on track to schedule a record number of different cities as well.\n\nI had conceived of a graphical representation of the growth of IndieWebCamps over the past nine years, both in number and across the world, but with everything else involved with setting up and running the Summit, ran out of time. However, the idea persisted, and finally this past week, with a little help from Aaron Parecki re-implementing Dopplr\u2019s algorithm for turning city names into colors, was able to put togther something pretty close to what I\u2019d envisioned:\n\nIstanbul\n\n\u00a0\n\nAmsterdam\n\n\u00a0\nUtrecht\n\n\u00a0\nN\u00fcrnberg\n\n\u00a0\n\u00a0\n\u00a0\n\nD\u00fcsseldorf\n\n\u00a0\n\u00a0\n\u00a0\n\u00a0\n\u00a0\nBerlin\n\n\u00a0\n\n\u00a0\n\u00a0\n\u00a0\n\u00a0\nEdinburgh\n\n\u00a0\n\nOxford\n\n\u00a0\n\u00a0\nBrighton\n\n\u00a0\n\u00a0\n\u00a0\n\u00a0\n\u00a0\n\n\u00a0\nNew Haven\n\n\u00a0\nBaltimore\n\n\u00a0\n\nCambridge\n\n\u00a0\n\u00a0\n\u00a0\n\nNew York\n\n\u00a0\n\n\u00a0\n\u00a0\n\u00a0\n\u00a0\nAustin\n\n\u00a0\n\n\u00a0\nBellingham\n\n\u00a0\n\nLos Angeles\n\n\u00a0\n\n\u00a0\n\nSan Francisco\n\n\u00a0\n\u00a0\n\n\u00a0\n\nPortland\n\u00a0\n\u00a0\n\u00a0\n\u00a0\n\u00a0\n\u00a0\n\u00a0\n\u00a0\n\u00a0\n\n2011\n2012\n2013\n2014\n2015\n2016\n2017\n2018\n2019\n\nI don\u2019t know of any tools to take something like this kind of locations vs years data and graph it as such. So I built an HTML table with a cell for each IndieWebCamp, as well as cells for the colspans of empty space. Each colored cell is hyperlinked to the IndieWebCamp for that city for that year.\n\n\n2011-2018 and over half of 2019 are IndieWebCamps (and Summits) that have already happened. 2019 includes bars for four upcoming IndieWebCamps, which are fully scheduled and open for sign-ups. \n\nThe table markup is copy pasted from the \nIndieWebCamp wiki template where I built it, and you can see the template working live in the context of the IndieWebCamp Cities page. I\u2019m sure the markup could be improved, suggestions welcome!",
        "html": "<p>\nWhile not a post directly about <a href=\"https://indieweb.org/2019/\">IndieWeb Summit 2019</a>, this post provides a bit of background and is certainly related, so I\u2019m including it in my series of posts about the Summit. Previous post in this series: <a href=\"https://tantek.com/2019/217/b1/indieweb-summit-2019-start\">Reflecting On IndieWeb Summit: A Start</a>\n</p>\n<p>\nAt the beginning of <a href=\"https://indieweb.org/2019/\">IndieWeb Summit 2019</a>, I gave a brief talk on \n<a href=\"https://indieweb.org/2019/state-of-the-indieweb\">State of the IndieWeb</a> and mentioned that:\n</p>\n<blockquote>We've scheduled lots of IndieWebCamps this year and are on track to schedule a record number of different cities as well.</blockquote>\n<p>\nI had conceived of a graphical representation of the growth of IndieWebCamps over the past nine years, both in number and across the world, but with everything else involved with setting up and running the Summit, ran out of time. However, the idea persisted, and finally this past week, with a little help from <a class=\"h-card\" href=\"https://aaronparecki.com/\">Aaron Parecki</a> re-implementing Dopplr\u2019s algorithm for turning city names into colors, was able to put togther something pretty close to what I\u2019d envisioned:\n</p>\n<a href=\"https://indieweb.org/Istanbul\" title=\"Istanbul\">Istanbul</a>\n\n<a href=\"https://indieweb.org/2017/Istanbul\" title=\"2017/Istanbul\">\u00a0</a>\n\n<a href=\"https://indieweb.org/Amsterdam\" title=\"Amsterdam\">Amsterdam</a>\n\n<a href=\"https://indieweb.org/2019/Amsterdam\" title=\"2019/Amsterdam\">\u00a0</a>\n<a href=\"https://indieweb.org/Utrecht\" title=\"Utrecht\">Utrecht</a>\n\n<a href=\"https://indieweb.org/2019/Utrecht\" title=\"2019/Utrecht\">\u00a0</a>\n<a href=\"https://indieweb.org/N%C3%BCrnberg\" title=\"N\u00fcrnberg\">N\u00fcrnberg</a>\n\n<a href=\"https://indieweb.org/2016/Nuremberg\" title=\"2016/Nuremberg\">\u00a0</a>\n<a href=\"https://indieweb.org/2017/Nuremberg\" title=\"2017/Nuremberg\">\u00a0</a>\n<a href=\"https://indieweb.org/2018/Nuremberg\" title=\"2018/Nuremberg\">\u00a0</a>\n\n<a href=\"https://indieweb.org/D%C3%BCsseldorf\" title=\"D\u00fcsseldorf\">D\u00fcsseldorf</a>\n\n<a href=\"https://indieweb.org/2015/D%C3%BCsseldorf\" title=\"2015/D\u00fcsseldorf\">\u00a0</a>\n<a href=\"https://indieweb.org/2016/D%C3%BCsseldorf\" title=\"2016/D\u00fcsseldorf\">\u00a0</a>\n<a href=\"https://indieweb.org/2017/D%C3%BCsseldorf\" title=\"2017/D\u00fcsseldorf\">\u00a0</a>\n<a href=\"https://indieweb.org/2018/D%C3%BCsseldorf\" title=\"2018/D\u00fcsseldorf\">\u00a0</a>\n<a href=\"https://indieweb.org/2019/D%C3%BCsseldorf\" title=\"2019/D\u00fcsseldorf\">\u00a0</a>\n<a href=\"https://indieweb.org/Berlin\" title=\"Berlin\">Berlin</a>\n\n<a href=\"https://indieweb.org/2014/Berlin\" title=\"2014/Berlin\">\u00a0</a>\n\n<a href=\"https://indieweb.org/2016/Berlin\" title=\"2016/Berlin\">\u00a0</a>\n<a href=\"https://indieweb.org/2017/Berlin\" title=\"2017/Berlin\">\u00a0</a>\n<a href=\"https://indieweb.org/2018/Berlin\" title=\"2018/Berlin\">\u00a0</a>\n<a href=\"https://indieweb.org/2019/Berlin\" title=\"2019/Berlin\">\u00a0</a>\n<a href=\"https://indieweb.org/Edinburgh\" title=\"Edinburgh\">Edinburgh</a>\n\n<a href=\"https://indieweb.org/2015/Edinburgh\" title=\"2015/Edinburgh\">\u00a0</a>\n\n<a href=\"https://indieweb.org/Oxford\" title=\"Oxford\">Oxford</a>\n\n<a href=\"https://indieweb.org/2018/Oxford\" title=\"2018/Oxford\">\u00a0</a>\n<a href=\"https://indieweb.org/2019/Oxford\" title=\"2019/Oxford\">\u00a0</a>\n<a href=\"https://indieweb.org/Brighton\" title=\"Brighton\">Brighton</a>\n\n<a href=\"https://indieweb.org/2012/Brighton\" title=\"2012/Brighton\">\u00a0</a>\n<a href=\"https://indieweb.org/2013/Brighton\" title=\"2013/Brighton\">\u00a0</a>\n<a href=\"https://indieweb.org/2014/Brighton\" title=\"2014/Brighton\">\u00a0</a>\n<a href=\"https://indieweb.org/2015/Brighton\" title=\"2015/Brighton\">\u00a0</a>\n<a href=\"https://indieweb.org/2016/Brighton\" title=\"2016/Brighton\">\u00a0</a>\n\n<a href=\"https://indieweb.org/2019/Brighton\" title=\"2019/Brighton\">\u00a0</a>\n<a href=\"https://indieweb.org/New_Haven\" title=\"New Haven\">New Haven</a>\n\n<a href=\"https://indieweb.org/2019/New_Haven\" title=\"2019/New Haven\">\u00a0</a>\n<a href=\"https://indieweb.org/Baltimore\" title=\"Baltimore\">Baltimore</a>\n\n<a href=\"https://indieweb.org/2018/Baltimore\" title=\"2018/Baltimore\">\u00a0</a>\n\n<a href=\"https://indieweb.org/Cambridge\" title=\"Cambridge\">Cambridge</a>\n\n<a href=\"https://indieweb.org/2014/Cambridge\" title=\"2014/Cambridge\">\u00a0</a>\n<a href=\"https://indieweb.org/2015/Cambridge\" title=\"2015/Cambridge\">\u00a0</a>\n<a href=\"https://indieweb.org/wiki/index.php?title=2016/Cambridge&amp;action=edit&amp;redlink=1\" title=\"2016/Cambridge (page does not exist)\">\u00a0</a>\n\n<a href=\"https://indieweb.org/New_York\" title=\"New York\">New York</a>\n\n<a href=\"https://indieweb.org/2014/NYC\" title=\"2014/NYC\">\u00a0</a>\n\n<a href=\"https://indieweb.org/2016/NYC\" title=\"2016/NYC\">\u00a0</a>\n<a href=\"https://indieweb.org/2017/NYC\" title=\"2017/NYC\">\u00a0</a>\n<a href=\"https://indieweb.org/2018/NYC\" title=\"2018/NYC\">\u00a0</a>\n<a href=\"https://indieweb.org/2019/NYC\" title=\"2019/NYC\">\u00a0</a>\n<a href=\"https://indieweb.org/Austin\" title=\"Austin\">Austin</a>\n\n<a href=\"https://indieweb.org/2017/Austin\" title=\"2017/Austin\">\u00a0</a>\n\n<a href=\"https://indieweb.org/2019/Austin\" title=\"2019/Austin\">\u00a0</a>\n<a href=\"https://indieweb.org/Bellingham\" title=\"Bellingham\">Bellingham</a>\n\n<a href=\"https://indieweb.org/2017/Bellingham\" title=\"2017/Bellingham\">\u00a0</a>\n\n<a href=\"https://indieweb.org/Los_Angeles\" title=\"Los Angeles\">Los Angeles</a>\n\n<a href=\"https://indieweb.org/wiki/index.php?title=2013/Los_Angeles&amp;action=edit&amp;redlink=1\" title=\"2013/Los Angeles (page does not exist)\">\u00a0</a>\n\n<a href=\"https://indieweb.org/2016/Santa_Monica\" title=\"2016/Santa Monica\">\u00a0</a>\n\n<a href=\"https://indieweb.org/San_Francisco\" title=\"San Francisco\">San Francisco</a>\n\n<a href=\"https://indieweb.org/2014/SF\" title=\"2014/SF\">\u00a0</a>\n<a href=\"https://indieweb.org/2015/SF\" title=\"2015/SF\">\u00a0</a>\n\n<a href=\"https://indieweb.org/2018/SF\" title=\"2018/SF\">\u00a0</a>\n\n<a href=\"https://indieweb.org/Portland\" title=\"Portland\">Portland</a>\n<a href=\"https://indieweb.org/2011\" title=\"2011\">\u00a0</a>\n<a href=\"https://indieweb.org/2012\" title=\"2012\">\u00a0</a>\n<a href=\"https://indieweb.org/2013\" title=\"2013\">\u00a0</a>\n<a href=\"https://indieweb.org/2014\" title=\"2014\">\u00a0</a>\n<a href=\"https://indieweb.org/2015\" title=\"2015\">\u00a0</a>\n<a href=\"https://indieweb.org/2016\" title=\"2016\">\u00a0</a>\n<a href=\"https://indieweb.org/2017\" title=\"2017\">\u00a0</a>\n<a href=\"https://indieweb.org/2018\" title=\"2018\">\u00a0</a>\n<a href=\"https://indieweb.org/2019\" title=\"2019\">\u00a0</a>\n\n<a href=\"https://indieweb.org/2011\" title=\"2011\">2011</a>\n<a href=\"https://indieweb.org/2012\" title=\"2012\">2012</a>\n<a href=\"https://indieweb.org/2013\" title=\"2013\">2013</a>\n<a href=\"https://indieweb.org/2014\" title=\"2014\">2014</a>\n<a href=\"https://indieweb.org/2015\" title=\"2015\">2015</a>\n<a href=\"https://indieweb.org/2016\" title=\"2016\">2016</a>\n<a href=\"https://indieweb.org/2017\" title=\"2017\">2017</a>\n<a href=\"https://indieweb.org/2018\" title=\"2018\">2018</a>\n<a href=\"https://indieweb.org/2019\" title=\"2019\">2019</a>\n<p>\nI don\u2019t know of any tools to take something like this kind of locations vs years data and graph it as such. So I built an HTML table with a cell for each IndieWebCamp, as well as cells for the colspans of empty space. Each colored cell is hyperlinked to the IndieWebCamp for that city for that year.\n</p>\n<p>\n2011-2018 and over half of 2019 are IndieWebCamps (and Summits) that have already happened. 2019 includes bars for <a href=\"https://tantek.com/2019/221/t1/four-indiewebcamps-open-sign-ups\">four upcoming IndieWebCamps, which are fully scheduled and open for sign-ups</a>. \n</p>\n<p>The table markup is copy pasted from the \n<a href=\"https://indieweb.org/Template:indiewebcamps-timeline\">IndieWebCamp wiki template</a> where I built it, and you can see the template working live in the context of the <a href=\"https://indieweb.org/cities\">IndieWebCamp Cities</a> page. I\u2019m sure the markup could be improved, suggestions welcome!\n</p>"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "article",
    "_id": "4920629",
    "_source": "1",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2019-08-16T14:54:56+02:00",
    "summary": "SemPress war das erste WordPress Theme (September 2002), das Microformats 2 unterst\u00fctzte und somit voll IndieWeb-kompatibel war. Seit ein paar Monaten/Jahren gibt es zwar weitere Themes die MF2 unterst\u00fctzen, aber SemPress ist seit fast 7 Jahren (Dezember 2002) immer noch das einzige, das \u00fcber WordPress.org installierbar (ist das ein Wort?) ist.\nPrateek Saxena arbeitet gerade daran, das zu \u00e4ndern! Sein Theme ist seit diesem Jahr auf WordPress.org und er arbeitet flei\u00dfig am MF2 Support.\n`war ne lange Zeit \ud83d\ude42",
    "url": "https://notiz.blog/2019/08/16/the-first-microformats2-wp-theme/",
    "content": {
        "text": "SemPress war das erste WordPress Theme (September 2002), das Microformats 2 unterst\u00fctzte und somit voll IndieWeb-kompatibel war. Seit ein paar Monaten/Jahren gibt es zwar weitere Themes die MF2 unterst\u00fctzen, aber SemPress ist seit fast 7 Jahren (Dezember 2002) immer noch das einzige, das \u00fcber WordPress.org installierbar (ist das ein Wort?) ist.\n\n\n\nPrateek Saxena arbeitet gerade daran, das zu \u00e4ndern! Sein Theme ist seit diesem Jahr auf WordPress.org und er arbeitet flei\u00dfig am MF2 Support.\n\n\n\n`war ne lange Zeit \ud83d\ude42",
        "html": "<p><a href=\"https://notiz.blog/projects/sempress/\">SemPress</a> war das erste WordPress Theme (<a href=\"https://notiz.blog/2012/09/06/ive-made-a-wordpress-theme-kind-of/\">September 2002</a>), das <a href=\"https://indieweb.org/microformats2\">Microformats 2</a> unterst\u00fctzte und somit voll IndieWeb-kompatibel war. Seit ein paar Monaten/Jahren gibt es zwar <a href=\"https://indieweb.org/WordPress/Themes#Themes_Supporting_Microformats\">weitere Themes die MF2 unterst\u00fctzen</a>, aber SemPress ist seit fast 7 Jahren (<a href=\"https://notiz.blog/2012/12/07/sempress-auf-wordpress-org/\">Dezember 2002</a>) immer noch das einzige, das \u00fcber <a href=\"https://wordpress.org/themes/sempress/\">WordPress.org</a> installierbar (ist das ein Wort?) ist.</p>\n\n\n\n<p><a href=\"https://prtksxna.com/\">Prateek Saxena</a> arbeitet gerade daran, das zu \u00e4ndern! Sein Theme ist seit diesem Jahr auf <a href=\"https://wordpress.org/themes/zuari/\">WordPress.org</a> und er arbeitet flei\u00dfig am <a href=\"https://github.com/prtksxna/zuari/commit/ff5374b062620635ce31e4e368980ed23d85b0c3\">MF2 Support</a>.</p>\n\n\n\n<p>`war ne lange Zeit \ud83d\ude42</p>"
    },
    "author": {
        "type": "card",
        "name": "Matthias Pfefferle",
        "url": "https://notiz.blog/author/matthias-pfefferle/",
        "photo": "https://secure.gravatar.com/avatar/75512bb584bbceae57dfc503692b16b2?s=40&d=https://notiz.blog/wp-content/plugins/semantic-linkbacks/img/mm.jpg&r=g"
    },
    "post-type": "note",
    "_id": "4915105",
    "_source": "206",
    "_is_read": true
}

Homebrew Website Club SF!

{
    "type": "event",
    "name": "Homebrew Website Club SF!",
    "summary": "Homebrew Website Club retro 1980s-style logo.\nTopics for this week: IndieWeb Summit Notes & Videos! Sign-up for Upcoming IndieWebCamps! \u274c IndieWebCamp Amsterdam \ud83c\udfeb IndieWebCamp Oxford \ud83d\uddfd IndieWebCamp New York City \ud83c\udfaa IndieWebCamp Brighton Demos of personal website breakthroughs Create or update your personal web site!\nJoin a community with like-minded interests. Bring friends that want a personal site, or are interested in a healthy, independent web!\nAny questions? Ask in #indieweb Slack or IRC\nMore information: IndieWeb Wiki Event Page\nRSVP: post an indie RSVP on your own site!",
    "published": "2019-08-15 18:51-0700",
    "start": "2019-08-21 17:30-0700",
    "end": "2019-08-21 18:30-0700",
    "url": "http://tantek.com/2019/233/e1/homebrew-website-club-sf",
    "location": [
        "https://wiki.mozilla.org/SF"
    ],
    "content": {
        "text": "When: 2019-08-21 17:30\u202618:30\nWhere: Mozilla San Francisco\n\nHost: Tantek \u00c7elik\n\n\n \nTopics for this week:\nIndieWeb Summit Notes & Videos!\nSign-up for Upcoming IndieWebCamps!\n\u274c  IndieWebCamp Amsterdam\n\ud83c\udfeb IndieWebCamp Oxford\n\ud83d\uddfd IndieWebCamp New York City\n\ud83c\udfaa IndieWebCamp Brighton\n\nDemos of personal website breakthroughs\nCreate or update your personal web site!\n\nJoin a community with like-minded interests. Bring friends that want a personal site, or are interested in a healthy, independent web!\n\n\nAny questions? Ask in \n#indieweb Slack or IRC\n\n\nMore information: \nIndieWeb Wiki Event Page\n\n\nRSVP:  post an indie RSVP on your own site!",
        "html": "<p>\nWhen: <time class=\"dt-start\">2019-08-21 17:30</time>\u2026<time class=\"dt-end\">18:30</time><span>\nWhere: <a class=\"u-location h-card\" href=\"https://wiki.mozilla.org/SF\">Mozilla San Francisco</a>\n</span>\nHost: <a class=\"u-organizer h-card\" href=\"http://tantek.com/\">Tantek \u00c7elik</a>\n</p>\n\n<p><img class=\"u-featured\" style=\"height:300px;\" src=\"https://aperture-media.p3k.io/indieweb.org/c24f7b1e711955ef818bde12e2a3e79708ecc9b106d95b460a9fefe93b0be723.jpg\" alt=\"Homebrew Website Club retro 1980s-style logo.\" /></p> \n<p>Topics for this week:</p>\n<ul><li>IndieWeb Summit <a href=\"https://indieweb.org/2019/Schedule\">Notes &amp; Videos</a>!</li>\n<li>Sign-up for Upcoming IndieWebCamps!\n<ul><li><a href=\"https://indieweb.org/2019/Amsterdam\">\u274c  IndieWebCamp Amsterdam</a></li>\n<li><a href=\"https://indieweb.org/2019/Oxford\">\ud83c\udfeb IndieWebCamp Oxford</a></li>\n<li><a href=\"https://indieweb.org/2019/NYC\">\ud83d\uddfd IndieWebCamp New York City</a></li>\n<li><a href=\"https://indieweb.org/2019/Brighton\">\ud83c\udfaa IndieWebCamp Brighton</a></li>\n</ul></li>\n<li>Demos of personal website breakthroughs</li>\n<li>Create or update your personal web site!</li>\n</ul><p>\nJoin a community with like-minded interests. Bring friends that want a personal site, or are interested in a healthy, independent web!\n</p>\n<p>\nAny questions? Ask in \n<a href=\"https://indieweb.org/discuss\">#indieweb Slack or IRC</a>\n</p>\n<p>\nMore information: \n<a class=\"u-url\" href=\"https://indieweb.org/events/2019-08-21-homebrew-website-club\">IndieWeb Wiki Event Page</a>\n</p>\n<p>\nRSVP:  post an <a href=\"https://indieweb.org/rsvp\">indie RSVP</a> on your own site!\n</p>"
    },
    "post-type": "event",
    "refs": {
        "https://wiki.mozilla.org/SF": {
            "type": "card",
            "name": "Mozilla San Francisco",
            "url": "https://wiki.mozilla.org/SF",
            "photo": null
        }
    },
    "_id": "4909533",
    "_source": "1",
    "_is_read": true
}

A journey to the underworld that is RDF

{
    "type": "entry",
    "author": {
        "name": "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/47c1a335655f3ed264b3b656498183412096113c/68747470733a2f2f70657465726d6f6c6e61722e6e65742f7765622d6f662d7468652d6d616368696e65732f7264662d69742d646f65732d6e6f742d737061726b2d6a6f792e6a7067\" title=\"rdf-it-does-not-spark-joy\" alt=\"rdf-it-does-not-spark-joy\" />\nworking with RDF - this one does not spark joy\n<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't 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'm 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'm 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't 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 was 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't 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're 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't 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 utilize 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're doing this for a search engine, stick to microdata, it's less prone to errors</li>\n<li>... or instead of both, 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...</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...\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... it's there. Line 13.\n<p>...but those errors then became ever more peculiar problems with RDFa...</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>... 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's 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're in hell.</em>). There's 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's 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's 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's still lacking a lot of definitions (<em>ever tried to represent a resume with it?</em>), it has weird quirks (<em>'follows' on a Person can only be another Person, it can't be a Brand, a WebSite, or a simple URL</em>) and it's 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>&lt;html lang=\"en\"  prefix=\"og: http://ogp.me/ns# article: http://ogp.me/ns/article#\"&gt;\n&lt;head&gt;\n    &lt;title&gt;A piece of Powerscourt Waterfall - petermolnar.net&lt;/title&gt;\n&lt;!-- JSON-LD as alternative --&gt;\n    &lt;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\" /&gt;\n&lt;!-- Open Graph vocabulary RDFa --&gt;\n    &lt;meta property=\"og:title\" content=\"A piece of Powerscourt Waterfall\" /&gt;\n    &lt;meta property=\"og:type\" content=\"article\" /&gt;\n    &lt;meta property=\"og:url\" content=\"https://petermolnar.net/a-piece-of-powerscourt-waterfall/\" /&gt;\n    &lt;meta property=\"og:description\" content=\"\" /&gt;\n    &lt;meta property=\"article:published_time\" content=\"2017-11-09T18:00:00+00:00\" /&gt;\n    &lt;meta property=\"article:modified_time\" content=\"2019-01-05T11:52:47.543053+00:00\" /&gt;\n    &lt;meta property=\"article:author\" content=\"Peter Molnar (mail@petermolnar.net)\" /&gt;\n    &lt;meta property=\"og:image\" content=\"https://petermolnar.net/a-piece-of-powerscourt-waterfall/a-piece-of-powerscourt-waterfall_b.jpg\" /&gt;\n    &lt;meta property=\"og:image:type\" content=\"image/jpeg\" /&gt;\n    &lt;meta property=\"og:image:width\" content=\"1280\" /&gt;\n    &lt;meta property=\"og:image:height\" content=\"847\" /&gt;\n&lt;!-- the rest of meta and header elements --&gt;\n&lt;!-- followed by the content, with microformats v1 and v2 markup --&gt;</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't know if Google will consume the JSON-LD alternate format, but it's there, and 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's simple, but compatible enough for most cases.</p>\n\n\n<ol><li><p><a href=\"http://web.archive.org/web/20190211232147/https:/twitter.com/csarven/status/1091314310465421312\">http://web.archive.org/web/20190211232147/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://github.com/petermolnar/nasg/commit/9c749f4591333744588bdf183b22ba638babcb20\">https://github.com/petermolnar/nasg/commit/9c749f4591333744588bdf183b22ba638babcb20</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://web.archive.org/web/20190203123749/https://twitter.com/RubenVerborgh/status/1092029740364587008\">https://web.archive.org/web/20190203123749/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 joy\nI want to say it all started with a rather offensive tweet1, but it wouldn't 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'm certain to say, quite useless. I got no pretty Google cards - maybe because I refuse to do AMP4, maybe because I'm 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't 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 was 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't 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're 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't 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 utilize 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're doing this for a search engine, stick to microdata, it's less prone to errors\n... or instead of both, 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...\n \n\nInteresting, it has some problems...\n \n\nit says URL for org is missing... it's there. Line 13.\n...but those errors then became ever more peculiar problems with RDFa...\n \n\nUndefined type, eh?\n \n\nwat\n... 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's surprisingly easy to represent data in JSON-LD with schema.org context (vocabulary, why on earth was vocabulary renamed to context?! Oh. Because we're in hell.). There's 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's 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's 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's still lacking a lot of definitions (ever tried to represent a resume with it?), it has weird quirks ('follows' on a Person can only be another Person, it can't be a Brand, a WebSite, or a simple URL) and it's 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't know if Google will consume the JSON-LD alternate format, but it's there, and 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's simple, but compatible enough for most cases.\n\n\nhttp://web.archive.org/web/20190211232147/https:/twitter.com/csarven/status/1091314310465421312\u21a9\nhttps://search.google.com/structured-data/testing-tool\u21a9\nhttps://github.com/petermolnar/nasg/commit/9c749f4591333744588bdf183b22ba638babcb20\u21a9\nhttps://www.ampproject.org/\u21a9\nhttps://web.archive.org/web/20190203123749/https://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": "4902212",
    "_source": "268",
    "_is_read": true
}

{
    "type": "entry",
    "author": {
        "name": "Kh\u00fcrt Williams",
        "url": "https://islandinthenet.com/",
        "photo": null
    },
    "url": "https://islandinthenet.com/automattic-to-acquire-tumblr/",
    "published": "2019-08-14T06:23:48-04:00",
    "content": {
        "html": "<a href=\"https://diaryofdennis.com/2019/08/13/tumblr-sold-to-automattic/\">Tumblr Sold to Automattic</a> <em>(Diary of Dennis)</em>\n<blockquote>What it means for WordPress.com users is not clear either. But if we start to speculate based on the term \u201cstandardize\u201d he used in his statement, it\u2019s likely that the company will enable sharing or reblogging across both services. It could also be that they bring registered users of both services closer together, which could also mean that it becomes easier for users of both services to comment and interact with each other. If we speculate further, it could become a reality that both services are integrated into the same feed or reader, which is how both communities could meet and interact with each other.</blockquote>\n\n<p>This was a surprise for me. I\u2019m not sure what any of this means for Tumblr or WordPress.com customers but I think it\u2019s an exciting development. Perhaps we\u2019ll get more Indieweb features such as Webmentions.</p>",
        "text": "Tumblr Sold to Automattic (Diary of Dennis)\nWhat it means for WordPress.com users is not clear either. But if we start to speculate based on the term \u201cstandardize\u201d he used in his statement, it\u2019s likely that the company will enable sharing or reblogging across both services. It could also be that they bring registered users of both services closer together, which could also mean that it becomes easier for users of both services to comment and interact with each other. If we speculate further, it could become a reality that both services are integrated into the same feed or reader, which is how both communities could meet and interact with each other.\n\nThis was a surprise for me. I\u2019m not sure what any of this means for Tumblr or WordPress.com customers but I think it\u2019s an exciting development. Perhaps we\u2019ll get more Indieweb features such as Webmentions."
    },
    "post-type": "note",
    "_id": "4888022",
    "_source": "242",
    "_is_read": true
}

Tumblr and… App.net

{
    "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/08/13/tumblr-and-appnet.html",
    "name": "Tumblr and\u2026 App.net",
    "content": {
        "html": "<p>Thanks to the \u201con this day\u201d feature <a href=\"https://github.com/cleverdevil/micromemories\">that Jonathan LaCour built</a> for Micro.blog-hosted blogs, I noticed that 7 years ago yesterday <a href=\"https://www.manton.org/2012/08/12/appnets-great-start.html\">I blogged about App.net reaching their funding goal</a>. I still get asked about App.net sometimes. It is easy to look back on something that didn\u2019t last and pick it apart. I\u2019d rather look at the good things that came out of App.net.</p>\n\n<p>When it was shutting down, I blogged <a href=\"https://www.manton.org/2017/01/06/thank-you-to.html\">my thanks to the App.net community</a>:</p>\n\n<blockquote>\n<p><a href=\"http://www.manton.org/2013/08/waiting_for_appnets.html\">I wrote in 2013</a> that it was not just a Twitter clone but an <em>amplifier</em> for applications that couldn\u2019t be built before. It came along at the right time, took off, and then faded. The App.net founders deserve significant credit and thanks for trying something risky and succeeding to grow a community that lasted so long.</p>\n</blockquote>\n\n<p>There is a guiding principle in Micro.blog that differentiates it from nearly every other platform. It\u2019s not only about creating an alternative social network. The foundation is around blogs and IndieWeb standards because that\u2019s <a href=\"https://manton.org/2018/09/07/the-way-out.html\">part of unrolling the damage caused by massive silos</a>.</p>\n\n<p>Micro.blog is also designed around blogs because it gives immediate value to the platform, insulating it against the network effect that drives the success or failure of most other social networks: not all your friends are there yet. Unlike ad-supported platforms, Micro.blog aligns its business model with customer needs. Subscriptions for blog hosting let us deliver the best features we can, and also help support the rest of the platform.</p>\n\n<p>Brent Simmons really <a href=\"https://inessential.com/2018/02/01/why_micro_blog_is_not_another_app_net\">said it best</a>:</p>\n\n<blockquote>\n<p>Micro.blog is not an alternative silo: instead, it\u2019s what you build when you believe that <em>the web itself</em> is the great social network.</p>\n</blockquote>\n\n<p>I often look back at this quote to help guide me as I evaluate the direction of Micro.blog. I believe that Micro.blog is the first platform of its kind. The closest competition might be Tumblr, <a href=\"https://photomatt.tumblr.com/post/186964618222/automattic-tumblr\">acquired yesterday by Automattic</a>.</p>\n\n<p>Of course it was coincidence that Automattic acquired Tumblr pretty much exactly 7 years after App.net was funded. No one is paying attention to those dates. And yet, now that I\u2019ve noticed it, there\u2019s a kind of symbolism to it. Tumblr is effectively being re-funded.</p>\n\n<p>Like Micro.blog, Tumblr is about making blogging easier. Like Micro.blog, Tumblr allows custom domain names for your blog, something no other major social network allows. Unlike Micro.blog, however, Tumblr\u2019s community is only Tumblr blogs. Micro.blog\u2019s community brings together not just Micro.blog-hosted blogs, but people using WordPress, Mastodon, or home-grown IndieWeb solutions.</p>\n\n<p>Matt Mullenweg and the Automattic team have a bunch of work ahead of them to integrate Tumblr into the WordPress ecosystem. I don\u2019t know how that\u2019s going to play out, but I know that preserving all the Tumblr blogs and giving them new life <em>is a good thing</em>.</p>\n\n<p>I wonder if Micro.blog and Automattic are on parallel tracks. Two companies wildly different in size and scope, but we can all learn from platforms that have come and gone, finding our own path to a shared vision of the future that embraces content ownership, supports healthy communities, and deemphasizes massive social networks. I\u2019m wishing the team at Automattic the best.</p>",
        "text": "Thanks to the \u201con this day\u201d feature that Jonathan LaCour built for Micro.blog-hosted blogs, I noticed that 7 years ago yesterday I blogged about App.net reaching their funding goal. I still get asked about App.net sometimes. It is easy to look back on something that didn\u2019t last and pick it apart. I\u2019d rather look at the good things that came out of App.net.\n\nWhen it was shutting down, I blogged my thanks to the App.net community:\n\n\nI wrote in 2013 that it was not just a Twitter clone but an amplifier for applications that couldn\u2019t be built before. It came along at the right time, took off, and then faded. The App.net founders deserve significant credit and thanks for trying something risky and succeeding to grow a community that lasted so long.\n\n\nThere is a guiding principle in Micro.blog that differentiates it from nearly every other platform. It\u2019s not only about creating an alternative social network. The foundation is around blogs and IndieWeb standards because that\u2019s part of unrolling the damage caused by massive silos.\n\nMicro.blog is also designed around blogs because it gives immediate value to the platform, insulating it against the network effect that drives the success or failure of most other social networks: not all your friends are there yet. Unlike ad-supported platforms, Micro.blog aligns its business model with customer needs. Subscriptions for blog hosting let us deliver the best features we can, and also help support the rest of the platform.\n\nBrent Simmons really said it best:\n\n\nMicro.blog is not an alternative silo: instead, it\u2019s what you build when you believe that the web itself is the great social network.\n\n\nI often look back at this quote to help guide me as I evaluate the direction of Micro.blog. I believe that Micro.blog is the first platform of its kind. The closest competition might be Tumblr, acquired yesterday by Automattic.\n\nOf course it was coincidence that Automattic acquired Tumblr pretty much exactly 7 years after App.net was funded. No one is paying attention to those dates. And yet, now that I\u2019ve noticed it, there\u2019s a kind of symbolism to it. Tumblr is effectively being re-funded.\n\nLike Micro.blog, Tumblr is about making blogging easier. Like Micro.blog, Tumblr allows custom domain names for your blog, something no other major social network allows. Unlike Micro.blog, however, Tumblr\u2019s community is only Tumblr blogs. Micro.blog\u2019s community brings together not just Micro.blog-hosted blogs, but people using WordPress, Mastodon, or home-grown IndieWeb solutions.\n\nMatt Mullenweg and the Automattic team have a bunch of work ahead of them to integrate Tumblr into the WordPress ecosystem. I don\u2019t know how that\u2019s going to play out, but I know that preserving all the Tumblr blogs and giving them new life is a good thing.\n\nI wonder if Micro.blog and Automattic are on parallel tracks. Two companies wildly different in size and scope, but we can all learn from platforms that have come and gone, finding our own path to a shared vision of the future that embraces content ownership, supports healthy communities, and deemphasizes massive social networks. I\u2019m wishing the team at Automattic the best."
    },
    "published": "2019-08-13T10:16:06-05:00",
    "post-type": "article",
    "_id": "4879676",
    "_source": "12",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2019-08-12T16:37:55-04:00",
    "url": "https://miklb.com/blog/2019/08/12/5203/",
    "syndication": [
        "https://twitter.com/miklb/status/1161013983907852289"
    ],
    "content": {
        "text": "MySpace with web standards and a personalized domain name that you can export anytime as html. Using webmentions & some form of oAuth. That\u2019s what is going to win.",
        "html": "<p>MySpace with web standards and a personalized domain name that you can export anytime as html. Using webmentions &amp; some form of oAuth. That\u2019s what is going to win.\n</p>"
    },
    "post-type": "note",
    "_id": "4867504",
    "_source": "42",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2019-08-12T11:25:20-0400",
    "rsvp": "yes",
    "url": "https://martymcgui.re/2019/08/12/112520/",
    "in-reply-to": [
        "https://2019.indieweb.org/nyc"
    ],
    "content": {
        "text": "I'm going!So excited to be co-organizing an IndieWebCamp in NYC!\n\nLooking to start your personal website? Want to take control of your social media content?\n\nJoin us at Pace University in downtown Manhattan on October 5th and 6th!",
        "html": "I'm going!<p>So excited to be co-organizing an IndieWebCamp in NYC!</p>\n\n<p>Looking to start your personal website? Want to take control of your social media content?</p>\n\n<p>Join us at Pace University in downtown Manhattan on October 5th and 6th!</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/nyc": {
            "type": "entry",
            "summary": "IndieWebCamp NYC 2019 is a two-day maker event for creating and/or improving your personal website. All levels welcome! One of several 2019 IndieWebCamps and the seventh IndieWebCamp in NYC!",
            "url": "https://2019.indieweb.org/nyc",
            "name": "IndieWebCamp NYC",
            "author": {
                "type": "card",
                "name": "2019.indieweb.org",
                "url": "http://2019.indieweb.org",
                "photo": null
            },
            "post-type": "note"
        }
    },
    "_id": "4864036",
    "_source": "175",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2019-08-11T02:46:53.10727-07:00",
    "url": "https://v2.jacky.wtf/post/56378800-23ed-42bf-b59c-983da0069fb6",
    "category": [
        "lwa",
        "itch"
    ],
    "in-reply-to": [
        "https://v2.jacky.wtf/post/88821979-b5ae-48bf-b2e9-844c4dfe11ff"
    ],
    "content": {
        "text": "And now https://lwa.black.af/ is up with some new copy. The reader link is valid but I took it off for now.\nWorking on the actual Microsub plumbing after I get the IndieAuth flow going",
        "html": "<p>And now <a href=\"https://lwa.black.af/\">https://lwa.black.af/</a> is up with some new copy. The reader link is valid but I took it off for now.<br />Working on the actual Microsub plumbing after I get the IndieAuth flow going</p>"
    },
    "post-type": "reply",
    "refs": {
        "https://v2.jacky.wtf/post/88821979-b5ae-48bf-b2e9-844c4dfe11ff": {
            "type": "entry",
            "url": "https://v2.jacky.wtf/post/88821979-b5ae-48bf-b2e9-844c4dfe11ff",
            "content": {
                "text": "I\u2019m up late because I got a red-eye. Going to use the time now to add some more copy to https://lwa.black.af then add some stuff like IndieAuth and Micropub support. Microsub will be the newest spec I have to implement. Very excited!",
                "html": "<p>I\u2019m up late because I got a red-eye. Going to use the time now to add some more copy to <a href=\"https://lwa.black.af\">https://lwa.black.af</a> then add some stuff like <a href=\"http://indieauth.spec.indieweb.org\">IndieAuth</a> and <a href=\"http://micropub.spec.indieweb.org\">Micropub</a> support. <a href=\"http://microsub.spec.indieweb.org\">Microsub</a> will be the newest spec I have to implement. </p><p>Very excited!</p>"
            },
            "post-type": "note"
        }
    },
    "_id": "4849908",
    "_source": "1886",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2019-08-11T02:23:55.43181-07:00",
    "url": "https://v2.jacky.wtf/post/88821979-b5ae-48bf-b2e9-844c4dfe11ff",
    "content": {
        "text": "I\u2019m up late because I got a red-eye. Going to use the time now to add some more copy to https://lwa.black.af then add some stuff like IndieAuth and Micropub support. Microsub will be the newest spec I have to implement. \nVery excited!",
        "html": "<p>I\u2019m up late because I got a red-eye. Going to use the time now to add some more copy to <a href=\"https://lwa.black.af\">https://lwa.black.af</a> then add some stuff like <a href=\"http://indieauth.spec.indieweb.org\">IndieAuth</a> and <a href=\"http://micropub.spec.indieweb.org\">Micropub</a> support. <a href=\"http://microsub.spec.indieweb.org\">Microsub</a> will be the newest spec I have to implement. </p>\n<p>Very excited!</p>"
    },
    "post-type": "note",
    "_id": "4849803",
    "_source": "1886",
    "_is_read": true
}

{
    "type": "entry",
    "author": {
        "name": "Kh\u00fcrt Williams",
        "url": "https://islandinthenet.com/",
        "photo": null
    },
    "url": "https://islandinthenet.com/2019-08-10-08-04-05/",
    "published": "2019-08-10T08:07:10-04:00",
    "content": {
        "html": "<a href=\"https://boffosocko.com/2017/12/15/threaded-replies-with-webmentions-in-wordpress/\">Threaded Replies and Comments with Webmentions in WordPress</a><em> (BoffoSocko)</em>\n<blockquote>This is how comments and replies on the internet were meant to be! You can now easily implement them in WordPress.</blockquote>\n\n<p>I see a bit of odd behaviour regarding Webmentions, Semantic Linkbacks and comments. There are five responses in <a href=\"https://micro.blog/khurtwilliams/4939635\">this thread</a> which started with a post from my blog that that was syndicated to micro.blog. Three of the responses show up under the <a href=\"https://islandinthenet.com/politically-motivated-violence-are-already-illegal/\">original blog post</a>. However, two show up under my <a href=\"https://islandinthenet.com/mentions/#comment-26054\">Webmentions collection page</a>.</p>\n<p>I am not using the <a href=\"https://github.com/pfefferle/wordpress-webmention-for-comments\">WordPress Webmention for Comments plugin</a>. Can you help?</p>\n<p>It also seems that it\u2019s no longer possible to change the Webmention type via Semantic Linkbacks.</p>",
        "text": "Threaded Replies and Comments with Webmentions in WordPress (BoffoSocko)\nThis is how comments and replies on the internet were meant to be! You can now easily implement them in WordPress.\n\nI see a bit of odd behaviour regarding Webmentions, Semantic Linkbacks and comments. There are five responses in this thread which started with a post from my blog that that was syndicated to micro.blog. Three of the responses show up under the original blog post. However, two show up under my Webmentions collection page.\nI am not using the WordPress Webmention for Comments plugin. Can you help?\nIt also seems that it\u2019s no longer possible to change the Webmention type via Semantic Linkbacks."
    },
    "post-type": "note",
    "_id": "4839812",
    "_source": "242",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2019-08-09 14:52-0700",
    "url": "http://tantek.com/2019/221/t1/four-indiewebcamps-open-sign-ups",
    "category": [
        "ViewSource",
        "MozFest",
        "indieweb",
        "openweb"
    ],
    "content": {
        "text": "IndieWebCamps open for sign-ups!\n\u274c Amsterdam 9/28-29 before #ViewSource https://indieweb.org/2019/Amsterdam\n\ud83c\udfeb Oxford 9/28 https://indieweb.org/2019/Oxford\n\ud83d\uddfd NYC 10/5-6 https://indieweb.org/2019/NYC\n\ud83c\udfaa Brighton 10/19-20 before #MozFest https://indieweb.org/2019/Brighton\n#indieweb #openweb",
        "html": "IndieWebCamps open for sign-ups!<br />\u274c Amsterdam 9/28-29 before #<span class=\"p-category\">ViewSource</span> <a href=\"https://indieweb.org/2019/Amsterdam\">https://indieweb.org/2019/Amsterdam</a><br />\ud83c\udfeb Oxford 9/28 <a href=\"https://indieweb.org/2019/Oxford\">https://indieweb.org/2019/Oxford</a><br />\ud83d\uddfd NYC 10/5-6 <a href=\"https://indieweb.org/2019/NYC\">https://indieweb.org/2019/NYC</a><br />\ud83c\udfaa Brighton 10/19-20 before #<span class=\"p-category\">MozFest</span> <a href=\"https://indieweb.org/2019/Brighton\">https://indieweb.org/2019/Brighton</a><br />#<span class=\"p-category\">indieweb</span> #<span class=\"p-category\">openweb</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": "4834361",
    "_source": "1",
    "_is_read": true
}

{
    "type": "entry",
    "author": {
        "name": "Kh\u00fcrt Williams",
        "url": "https://islandinthenet.com/",
        "photo": null
    },
    "url": "https://islandinthenet.com/2019-08-09-08-38-46/",
    "published": "2019-08-09T08:38:46-04:00",
    "content": {
        "html": "<blockquote><blockquote><p>huh. Thanks for the recommendation. I'll look at SemPress and see if replacing Independent Publisher is something I want to do :)</p>\u2014 Nitin Khanna (@nitinthewiz) <a href=\"https://twitter.com/nitinthewiz/status/1109257116395528194?ref_src=twsrc%5Etfw\">March 23, 2019</a></blockquote><a href=\"https://twitter.com/nitinthewiz/status/1109257116395528194\"></a></blockquote>\n\n<p>Take a look at <a href=\"https://github.com/dshanske/indieweb-publisher\">Indieweb Publisher</a> by @dshanske. It\u2019s a fork of Independent Publisher.</p>\nAlso on:<p><a href=\"https://brid.gy/publish/twitter\"> </a><a href=\"https://fed.brid.gy/\"> </a></p>",
        "text": "huh. Thanks for the recommendation. I'll look at SemPress and see if replacing Independent Publisher is something I want to do :)\u2014 Nitin Khanna (@nitinthewiz) March 23, 2019\n\nTake a look at Indieweb Publisher by @dshanske. It\u2019s a fork of Independent Publisher.\nAlso on:"
    },
    "post-type": "note",
    "_id": "4827078",
    "_source": "242",
    "_is_read": true
}

Register for Indie Web Camp Brighton 2019

{
    "type": "entry",
    "published": "2019-08-09T08:34:16Z",
    "url": "https://adactio.com/journal/15612",
    "category": [
        "indieweb",
        "brighton",
        "indiewebcamp",
        "events"
    ],
    "syndication": [
        "https://medium.com/@adactio/822f5ae96a22"
    ],
    "name": "Register for Indie Web Camp Brighton 2019",
    "content": {
        "text": "Back at the end of May, I wrote:\n\n\n  We\u2019re going to have an Indie Web Camp in Brighton on October 19th and 20th. I realise that\u2019s quite a way off, but I\u2019m giving you plenty of advance warning so you can block out that weekend (and plan travel if you\u2019re coming from outside Brighton).\n\n\nI hope you\u2019ve got those dates marked in your calendar. Now it\u2019s time for the next step: register for the event. Registration is free, but we need to know numbers in advance, so if you\u2019re planning to come, please grab yourself a ticket there.\n\nIt\u2019s going to be a lot of fun!\n\n\n  If you\u2019ve never been to an Indie Web Camp before, you should definitely come! It\u2019s indescribably fun and inspiring. The first day\u2014Saturday\u2014is a BarCamp-style day of discussions to really get the ideas flowing. Then the second day\u2014Sunday\u2014is all about designing, building, and making. The whole thing wraps up with demos.\n\n\nCheck out the previous Brighton Indie Web Camps:\n\n\n2014,\n\n2015, and \n\n2016.\nSee you at 68 Middle Street on Saturday, October 19th for Indie Web Camp Brighton 2019!",
        "html": "<p>Back at the end of May, <a href=\"https://adactio.com/journal/15254\">I wrote</a>:</p>\n\n<blockquote>\n  <p>We\u2019re going to have an <a href=\"https://indieweb.org/2019/Brighton\">Indie Web Camp in Brighton</a> on October 19th and 20th. I realise that\u2019s quite a way off, but I\u2019m giving you plenty of advance warning so you can block out that weekend (and plan travel if you\u2019re coming from outside Brighton).</p>\n</blockquote>\n\n<p>I hope you\u2019ve got those dates marked in your calendar. Now it\u2019s time for the next step: <a href=\"https://ti.to/adactio/indie-webcamp-brighton-2019\">register for the event</a>. Registration is free, but we need to know numbers in advance, so if you\u2019re planning to come, please grab yourself a ticket there.</p>\n\n<p>It\u2019s going to be a lot of fun!</p>\n\n<blockquote>\n  <p>If you\u2019ve never been to an Indie Web Camp before, you should definitely come! It\u2019s indescribably fun and inspiring. The first day\u2014Saturday\u2014is a BarCamp-style day of discussions to really get the ideas flowing. Then the second day\u2014Sunday\u2014is all about designing, building, and making. The whole thing wraps up with demos.</p>\n</blockquote>\n\n<p>Check out the previous Brighton Indie Web Camps:</p>\n\n<ul><li>\n<a href=\"https://adactio.com/journal/7434\">2014</a>,</li>\n<li>\n<a href=\"https://adactio.com/journal/9261\">2015</a>, and </li>\n<li>\n<a href=\"https://adactio.com/journal/11246\">2016</a>.</li>\n</ul><p>See you at <a href=\"http://68middle.st/\">68 Middle Street</a> on Saturday, October 19th for <a href=\"https://indieweb.org/2019/Brighton\">Indie Web Camp Brighton 2019</a>!</p>"
    },
    "author": {
        "type": "card",
        "name": "Jeremy Keith",
        "url": "https://adactio.com/",
        "photo": "https://aperture-proxy.p3k.io/bbbacdf0a064621004f2ce9026a1202a5f3433e0/68747470733a2f2f6164616374696f2e636f6d2f696d616765732f70686f746f2d3135302e6a7067"
    },
    "post-type": "article",
    "_id": "4826017",
    "_source": "2",
    "_is_read": true
}

Discrete replies

{
    "type": "entry",
    "published": "2019-08-08T18:23:37Z",
    "url": "https://adactio.com/journal/15610",
    "category": [
        "replies",
        "twitter",
        "responses",
        "indieweb",
        "homepage"
    ],
    "syndication": [
        "https://medium.com/@adactio/60a2869e7d92"
    ],
    "name": "Discrete replies",
    "content": {
        "text": "Earlier this year, at Indie Web Camp D\u00fcsseldorf, I got replies working on my own site. That is to say, I can host a reply on my site to something on another site.\n\nThe classic example is Twitter. In fact, if you look at all my replies, most of them are responding to tweets (I also syndicate these replies to Twitter so they show up there just like regular tweet replies).\n\nI\u2019m really, really glad I got replies working. I\u2019ve been using this functionality quite a bit, and it feels really good to own my content this way.\n\nAt the time, I wrote:\n\n\n  So I\u2019m owning my replies now. At the moment, they show up in my home page feed just like any other notes I post. I\u2019m not sure if I\u2019ll keep it that way. They don\u2019t make much sense out of context.\n\n\nI decided not to include them on my home page feed after all. You\u2019ll still see them if you go to the notes section of my site, but I decided that they were overwhelming my home page a bit. They also don\u2019t show up in my RSS feed.\n\nI\u2019m really happy that I\u2019m hosting my replies, and that I\u2019ve got URLs for all of them, but I don\u2019t think I want to give them the same priority as blog posts, links, and regular notes.",
        "html": "<p>Earlier this year, at Indie Web Camp D\u00fcsseldorf, <a href=\"https://adactio.com/journal/15212\">I got replies working on my own site</a>. That is to say, I can host a reply on my site to something on another site.</p>\n\n<p>The classic example is Twitter. In fact, if you look at <a href=\"https://adactio.com/notes/replies\">all my replies</a>, most of them are responding to tweets (I also syndicate these replies to Twitter so they show up there just like regular tweet replies).</p>\n\n<p>I\u2019m really, really glad I got replies working. I\u2019ve been using this functionality quite a bit, and it feels really good to own my content this way.</p>\n\n<p>At the time, <a href=\"https://adactio.com/journal/15212#At%20the%20moment\">I wrote</a>:</p>\n\n<blockquote>\n  <p>So I\u2019m owning my replies now. At the moment, they show up in my home page feed just like any other notes I post. I\u2019m not sure if I\u2019ll keep it that way. They don\u2019t make much sense out of context.</p>\n</blockquote>\n\n<p>I decided not to include them on my home page feed after all. You\u2019ll still see them if you go to <a href=\"https://adactio.com/notes\">the notes section of my site</a>, but I decided that they were overwhelming <a href=\"https://adactio.com/\">my home page</a> a bit. They also don\u2019t show up in <a href=\"https://adactio.com/rss/\">my RSS feed</a>.</p>\n\n<p>I\u2019m really happy that I\u2019m hosting my replies, and that I\u2019ve got URLs for all of them, but I don\u2019t think I want to give them the same priority as blog posts, links, and regular notes.</p>"
    },
    "author": {
        "type": "card",
        "name": "Jeremy Keith",
        "url": "https://adactio.com/",
        "photo": "https://aperture-proxy.p3k.io/bbbacdf0a064621004f2ce9026a1202a5f3433e0/68747470733a2f2f6164616374696f2e636f6d2f696d616765732f70686f746f2d3135302e6a7067"
    },
    "post-type": "article",
    "_id": "4819029",
    "_source": "2",
    "_is_read": true
}

Reflecting On IndieWeb Summit: A Start

{
    "type": "entry",
    "published": "2019-08-05 23:15-0700",
    "url": "http://tantek.com/2019/217/b1/indieweb-summit-2019-start",
    "featured": "https://live.staticflickr.com/65535/48208205337_1a270b118a_c.jpg",
    "name": "Reflecting On IndieWeb Summit: A Start",
    "content": {
        "text": "Over a month ago we organized the ninth annual IndieWeb Summit in Portland, Oregon, June 29-30. As frequently happens to organizers, the combination of follow-ups, subsequent holiday, and other events did not allow for much time to blog afterwards. On the other hand, it did allow for at least some reflection and appreciation.\n\n\nSomethings Sooner\n\nRather than feeling overwhelmed by the pressure of a thorough summary post about the entire Summit, I decided it would be better to write at least about one aspect, session, or portion there of, to get started. Something is better than nothing. Something sooner (even if it wasn\u2019t immediate) is better than a lot, later, or a lot later.\n\n\nDay 1 Badges, Pins, Shirts, And Breakfast!\n\n\nSaturday morning June 29th went relatively smoothly. We had everything setup in time. I finished preparing my \u201cstate of\u201d outline. Everyone signed-in when they arrived, got a badge, chose their color of lanyard (more on that later), pronoun pin(s), and an array of decorative stickers to customize their badge. \n\n\nFor the first time we had an anonymous donor who chipped in enough in addition to the minimal $10 registration fee for us to afford IndieWebCamp t-shirts in a couple of shapes and a variety of sizes. We had a warm breakfast (vegetarian and vegan) ready to go for participants.\n\n\nCaptions, Codes of Conduct, Safety, And Photo Policy!\n\n\nAnother first for any IndieWebCamp, we arranged a captioner who live-captioned the first two hours of Summit keynotes, introductions, and demos.\n\n\nAfter welcoming everyone and introducing co-organizers Tiara and Aaron, I showed & briefly summarized our codes of conduct for the Summit:\n\nIndieWeb Code of Conduct\nMozilla Community Participation Guidelines\n\nIn particular I emphasized the recent addition from XOXO 2018\u2019s Code of Conduct regarding safety vs. comfort, which is worth its own blog post.\n\n\nAnother Summit first, also inspired by XOXO (and other conferences like Open Source Bridge), color-coded lanyards for our photo policy. Which was a natural lead-in for the heads-up about session live-streaming and where to sit accordingly (based on personal preference). Lastly, pronoun pins and a huge thanks to Aaron Parecki for arranging the logistics of all those materials!\n\n\nI told people about the online tools that would help their Summit experience (chat, the wiki, Etherpad), summarized the day 1 schedule, and thanked the sponsors.\n\n\nVideo, Outline, And Always Aspiring\n\n\nHere\u2019s the 8 minute video of the Welcome. I think it went ok, especially with so many firsts for this Summit! In the future I\u2019d like to: reduce it to no more than 5 minutes (one or two rounds of practice & edit should help), and consider what else could or should be included (while staying under 5 minutes). That being said, I feel pretty good about our continuous improvement with organizing and welcoming to IndieWebCamps. As we\u2019ve learned from other inclusive conferences, I encourage all conference organizers to explicitly cover similar aspects (excerpted from the online outline I spoke from)\n\nCode(s) of conduct (with multiple organizers and contacts)\nPhoto policy (with clear indicators to self-select)\nPronoun pins (or stickers)\n\nConsider these a minimum baseline, a place to build from, more than goals. Ideally we should aspire to provide a safe and inclusive experience for an increasingly diverse community. Two more ways conference organizers can do so is by recognizing what the conference has done better this year, and by choosing keynote speakers to provide diverse perspectives. More on that with State of the IndieWeb, and the IndieWeb Summit 2019 invited keynote speakers.\n\nPhotos 1, 2, & 4 by Aaron Parecki",
        "html": "<p>\n<a href=\"https://www.flickr.com/photos/aaronpk/48208205337/in/album-72157709454588936/\"><img src=\"https://aperture-media.p3k.io/live.staticflickr.com/1b8fd514419234ad365a1ff2b14646ea36158045bec968bdf49b9ad4b2176ba6.jpg\" class=\"u-featured\" alt=\"Table of Firefox stickers, pronoun pins, IndieWebCamp &amp; microformats stickers\" style=\"float:left;padding-right:1em;\" /></a>\nOver a month ago we organized the <a href=\"https://indieweb.org/2019\">ninth annual IndieWeb Summit</a> in Portland, Oregon, June 29-30. As frequently happens to organizers, the combination of follow-ups, subsequent holiday, and other events did not allow for much time to blog afterwards. On the other hand, it did allow for at least some reflection and appreciation.\n</p>\n\n<h2>Somethings Sooner</h2>\n<p>\nRather than feeling overwhelmed by the pressure of a thorough summary post about the entire Summit, I decided it would be better to write at least about one aspect, session, or portion there of, to get started. Something is better than nothing. Something sooner (even if it wasn\u2019t immediate) is better than a lot, later, or a lot later.\n</p>\n<h2>\nDay 1 Badges, Pins, Shirts, And Breakfast!\n</h2>\n<p><a href=\"https://www.flickr.com/photos/aaronpk/48208143942/in/album-72157709454588936/\"><img src=\"https://aperture-media.p3k.io/live.staticflickr.com/6ba0f27eb13d2854bc866e62273b67348fe2d5352a2ef11270ff1c8b8d8852d3.jpg\" alt=\"IndieWebCamp t-shirts and Lillian\" style=\"float:left;padding-right:1em;\" /></a>\nSaturday morning June 29th went relatively smoothly. We had everything setup in time. I finished preparing my \u201cstate of\u201d outline. Everyone signed-in when they arrived, got a badge, chose their color of lanyard (more on that later), pronoun pin(s), and an array of decorative stickers to customize their badge. \n</p>\n<p><a href=\"https://indieweb.org/File:2019-06-29-iws-day1-breakfast.jpg\"><img src=\"https://aperture-media.p3k.io/indieweb.org/58fa22f4f2b17d881d3de44ec76836f625369e6c9463b0690024f250bc657dca.jpg\" alt=\"Breakfast buffet containers of scrambled eggs, potatoes, vegan scramble, etc.\" style=\"float:left;padding-right:1em;\" /></a>\nFor the first time we had an anonymous donor who chipped in enough in addition to the minimal $10 registration fee for us to afford IndieWebCamp t-shirts in a couple of shapes and a variety of sizes. We had a warm breakfast (vegetarian and vegan) ready to go for participants.\n</p>\n<h2>\nCaptions, Codes of Conduct, Safety, And Photo Policy!\n</h2>\n<p>\nAnother first for any <a href=\"https://indieweb.org/IndieWebCamps\">IndieWebCamp</a>, we arranged a captioner who live-captioned the first two hours of Summit keynotes, introductions, and demos.\n</p>\n<p>\nAfter welcoming everyone and introducing co-organizers Tiara and Aaron, I showed &amp; briefly summarized our codes of conduct for the Summit:\n</p>\n<ul><li><a href=\"https://indieweb.org/code-of-conduct\">IndieWeb Code of Conduct</a></li>\n<li><a href=\"https://www.mozilla.org/en-US/about/governance/policies/participation/\">Mozilla Community Participation Guidelines</a></li>\n</ul><p>\nIn particular I emphasized the recent addition from <a href=\"https://2018.xoxofest.com/conduct\">XOXO 2018\u2019s Code of Conduct</a> regarding safety vs. comfort, which is worth its own blog post.\n</p>\n<p><a href=\"https://www.flickr.com/photos/aaronpk/48208143867/in/album-72157709454588936/\"><img src=\"https://aperture-media.p3k.io/live.staticflickr.com/83d84c9c6eabb4443a55eb4d5686d4688d1ed1058d0fec79d092146c6e17548a.jpg\" alt=\"Tiara, photo policy lanyards of different colors, and policy summary\" style=\"float:left;padding-right:1em;\" /></a>\nAnother Summit first, also inspired by XOXO (and other conferences like Open Source Bridge), color-coded lanyards for our photo policy. Which was a natural lead-in for the heads-up about session live-streaming and where to sit accordingly (based on personal preference). Lastly, pronoun pins and a huge thanks to Aaron Parecki for arranging the logistics of all those materials!\n</p>\n<p>\nI told people about the online tools that would help their Summit experience (chat, the wiki, Etherpad), summarized the day 1 schedule, and thanked the sponsors.\n</p>\n<h2>\nVideo, Outline, And Always Aspiring\n</h2>\n<p>\nHere\u2019s the <a href=\"https://archive.org/details/indieweb-summit-2019-welcome\">8 minute video of the Welcome</a>. I think it went ok, especially with so many firsts for this Summit! In the future I\u2019d like to: reduce it to no more than 5 minutes (one or two rounds of practice &amp; edit should help), and consider what else could or should be included (while staying under 5 minutes). That being said, I feel pretty good about our continuous improvement with organizing and welcoming to IndieWebCamps. As we\u2019ve learned from other inclusive conferences, I encourage all conference organizers to explicitly cover similar aspects (excerpted from the <a href=\"https://indieweb.org/2019/Introduction#Day_1_Introduction\">online outline</a> I spoke from)\n</p>\n<ul><li>Code(s) of conduct (with multiple organizers and contacts)</li>\n<li>Photo policy (with clear indicators to self-select)</li>\n<li>Pronoun pins (or stickers)</li>\n</ul><p>\nConsider these a minimum baseline, a place to build from, more than goals. Ideally we should aspire to provide a safe and inclusive experience for an increasingly diverse community. Two more ways conference organizers can do so is by recognizing what the conference has done better this year, and by choosing keynote speakers to provide diverse perspectives. More on that with State of the IndieWeb, and the IndieWeb Summit 2019 invited keynote speakers.\n</p>\n<p>Photos 1, 2, &amp; 4 by <a class=\"h-card\" href=\"https://aaronparecki.com/\">Aaron Parecki</a></p>"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "article",
    "_id": "4781072",
    "_source": "1",
    "_is_read": true
}

{
    "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/08/05/reminder-that-theres.html",
    "content": {
        "html": "<p>Reminder that there\u2019s an IndieWeb Meetup (aka Homebrew Website Club) this Wednesday. I\u2019ll bring some Micro.blog stickers. 6:30pm at the tables outside at Mozart\u2019s. \u2615</p>",
        "text": "Reminder that there\u2019s an IndieWeb Meetup (aka Homebrew Website Club) this Wednesday. I\u2019ll bring some Micro.blog stickers. 6:30pm at the tables outside at Mozart\u2019s. \u2615"
    },
    "published": "2019-08-05T20:50:54-05:00",
    "post-type": "note",
    "_id": "4778948",
    "_source": "12",
    "_is_read": true
}

Space for the strange in digital urban planning

{
    "type": "entry",
    "author": {
        "name": "Neil Mather",
        "url": "https://doubleloop.net/",
        "photo": null
    },
    "url": "https://doubleloop.net/2019/08/03/space-for-the-strange-in-digital-urban-planning/",
    "published": "2019-08-03T19:40:18+00:00",
    "content": {
        "html": "In the frame of digital urban planning, I think this quote from Jane Jacobs (discovered via Future Histories) is very IndieWeb.\n<blockquote><p>\u201cWhat a wonderful challenge there is! Rarely has the citizen had such a chance to reshape the city, and to make it the kind of city that she likes and that others will too. If this means leaving room for the incongruous, or the vulgar or the strange, that is part of the challenge, not the problem. Designing a dream city is easy; rebuilding a living one takes imagination.\u201d</p></blockquote>\n<p>Says O\u2019Shea:</p>\n<blockquote><p>\u201cWe need to protect space in our minds for the vulgar and the strange, for the unpredictable experiences of living free from the influence of commercialism. Like the fl\u00e2neur or fl\u00e2neuse, we should aim to cultivate curiosity through this liberated lens.\u201d</p></blockquote>",
        "text": "In the frame of digital urban planning, I think this quote from Jane Jacobs (discovered via Future Histories) is very IndieWeb.\n\u201cWhat a wonderful challenge there is! Rarely has the citizen had such a chance to reshape the city, and to make it the kind of city that she likes and that others will too. If this means leaving room for the incongruous, or the vulgar or the strange, that is part of the challenge, not the problem. Designing a dream city is easy; rebuilding a living one takes imagination.\u201d\nSays O\u2019Shea:\n\u201cWe need to protect space in our minds for the vulgar and the strange, for the unpredictable experiences of living free from the influence of commercialism. Like the fl\u00e2neur or fl\u00e2neuse, we should aim to cultivate curiosity through this liberated lens.\u201d"
    },
    "name": "Space for the strange in digital urban planning",
    "post-type": "article",
    "_id": "4751084",
    "_source": "1895",
    "_is_read": true
}

Homebrew Website Club Teesside

{
    "type": "event",
    "name": "Homebrew Website Club Teesside",
    "summary": "A meeting for people who are making websites or want to",
    "published": "2019-08-02T18:39:34+0000",
    "start": "2019-08-07T17:30:00+00:00",
    "end": "2019-08-07T19:30:00+00:00",
    "url": "http://known.kevinmarks.com/2019/homebrew-website-club-teesside",
    "location": [
        "De Melo, 248 Linthorpe Rd, Middlesbrough TS1 3PQ"
    ],
    "content": {
        "text": "Are you building your own website? Indie reader? Personal publishing web app? Come on by and join a gathering of people with likeminded interests. Bring your friends who want to start a personal web site. Exchange information, swap ideas, talk shop, help work on a project...<br style=\"color:#1d2129;\" /><br style=\"color:#1d2129;\" />* Finish that blog post you\u2019ve been writing, contribute to the indieweb wiki!<br style=\"color:#1d2129;\" />* Demos of recent IndieWeb breakthroughs, share what you've gotten working!",
        "html": "<p><span style=\"color:#1d2129;\">Are you building your own website? Indie reader? Personal publishing web app? Come on by and join a gathering of people with likeminded interests. Bring your friends who want to start a personal web site. Exchange information, swap ideas, talk shop, help work on a project...</span><br style=\"color:#1d2129;\" /><br style=\"color:#1d2129;\" /><span style=\"color:#1d2129;\">* Finish that blog post you\u2019ve been writing, contribute to the indieweb wiki!</span><br style=\"color:#1d2129;\" /><span style=\"color:#1d2129;\">* Demos of recent IndieWeb breakthroughs, share what you've gotten working!</span></p>"
    },
    "post-type": "event",
    "_id": "4742068",
    "_source": "205",
    "_is_read": true
}

A little automation ...

{
    "type": "entry",
    "published": "2019-07-26T10:16:00+02:00",
    "summary": "Quite apart from the fact that I have barely written a thing here for almost a month, I thought it would be worthwhile to pick a low-hanging fruit. So I followed the very simple instructions at Automate your outgoing webmentions and now my hope is that I have removed one more piece of grit from wh...\nMore this way ...",
    "url": "https://www.jeremycherfas.net/blog/a-little-automation",
    "name": "A little automation ...",
    "content": {
        "text": "Quite apart from the fact that I have barely written a thing here for almost a month, I thought it would be worthwhile to pick a low-hanging fruit. So I followed the very simple instructions at Automate your outgoing webmentions and now my hope is that I have removed one more piece of grit from wh...\n            More this way ...",
        "html": "<p>Quite apart from the fact that I have barely written a thing here for almost a month, I thought it would be worthwhile to pick a low-hanging fruit. So I followed the very simple instructions at <a href=\"https://webmention.app/\">Automate your outgoing webmentions</a> and now my hope is that I have removed one more piece of grit from wh...</p>\n            <p><a href=\"https://www.jeremycherfas.net/blog/a-little-automation\">More this way ...</a></p>"
    },
    "post-type": "article",
    "_id": "4738204",
    "_source": "202",
    "_is_read": true
}