{
    "type": "entry",
    "author": {
        "name": "Kh\u00fcrt Williams",
        "url": "https://islandinthenet.com/",
        "photo": null
    },
    "url": "https://islandinthenet.com/2019-08-23-00-40-20/",
    "published": "2019-08-23T00:40:20-04:00",
    "content": {
        "html": "Might be attending <a href=\"https://2019.indieweb.org/nyc\">IndieWebCamp NYC</a>\n<blockquote>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!</blockquote>",
        "text": "Might be attending IndieWebCamp NYC\nIndieWebCamp 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!"
    },
    "post-type": "note",
    "_id": "4988405",
    "_source": "242",
    "_is_read": true
}

Jeremy Keith adactio.com

{
    "type": "entry",
    "published": "2019-08-22T03:17:15Z",
    "url": "https://adactio.com/links/15660",
    "category": [
        "indieweb",
        "personal",
        "publishing",
        "homepages",
        "websites",
        "independent",
        "inspiration",
        "ownership"
    ],
    "bookmark-of": [
        "https://99u.adobe.com/articles/64112/why-you-need-a-personal-website-and-tips-for-how-to-build-one"
    ],
    "content": {
        "text": "Why We All Need a Personal Website \u2013 Plus Practical Tips for How to Build One - Adobe 99U\n\n\n\n\n  The best time to make a personal website is 20 years ago. The second best time to make a personal website is now.\n\n\nChris offers some illustrated advice:\n\n\n  Define the purpose of your site\n  Organize your content\n  Look for inspiration\n  Own your own domain name\n  Build your website",
        "html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://99u.adobe.com/articles/64112/why-you-need-a-personal-website-and-tips-for-how-to-build-one\">\nWhy We All Need a Personal Website \u2013 Plus Practical Tips for How to Build One - Adobe 99U\n</a>\n</h3>\n\n<blockquote>\n  <p>The best time to make a personal website is 20 years ago. The second best time to make a personal website is now.</p>\n</blockquote>\n\n<p><a href=\"http://shiflett.org/\">Chris</a> offers some illustrated advice:</p>\n\n<blockquote>\n  <ul><li>Define the purpose of your site</li>\n  <li>Organize your content</li>\n  <li>Look for inspiration</li>\n  <li>Own your own domain name</li>\n  <li>Build your website</li>\n  </ul></blockquote>"
    },
    "author": {
        "type": "card",
        "name": "Jeremy Keith",
        "url": "https://adactio.com/",
        "photo": "https://aperture-proxy.p3k.io/bbbacdf0a064621004f2ce9026a1202a5f3433e0/68747470733a2f2f6164616374696f2e636f6d2f696d616765732f70686f746f2d3135302e6a7067"
    },
    "post-type": "bookmark",
    "_id": "4975501",
    "_source": "2",
    "_is_read": true
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2019-08-21 14:52-0700",
    "rsvp": "yes",
    "url": "http://tantek.com/2019/233/t1/hosting-homebrew-website-club-sf",
    "category": [
        "SF",
        "IndieWeb",
        "dweb",
        "openweb"
    ],
    "in-reply-to": [
        "https://tantek.com/2019/233/e1/homebrew-website-club-sf"
    ],
    "content": {
        "text": "hosting the Homebrew Website Club #SF #IndieWeb meetup tonight 17:30 @MozSF\nHope to see you there! Yes you @benwerd @dietrich @generativist @html5cat @NurtureGirl @feross @maira\ncc #dweb #openweb\n\nRSVP: https://tantek.com/2019/233/e1/homebrew-website-club-sf\nMore: https://indieweb.org/events/2019-08-21-homebrew-website-club#San_Francisco",
        "html": "hosting the Homebrew Website Club #<span class=\"p-category\">SF</span> #<span class=\"p-category\">IndieWeb</span> meetup tonight 17:30 <a class=\"h-cassis-username\" href=\"https://twitter.com/MozSF\">@MozSF</a><br />Hope to see you there! Yes you <a class=\"h-cassis-username\" href=\"https://twitter.com/benwerd\">@benwerd</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/dietrich\">@dietrich</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/generativist\">@generativist</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/html5cat\">@html5cat</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/NurtureGirl\">@NurtureGirl</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/feross\">@feross</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/maira\">@maira</a><br />cc #<span class=\"p-category\">dweb</span> #<span class=\"p-category\">openweb</span><br /><br />RSVP: <a href=\"https://tantek.com/2019/233/e1/homebrew-website-club-sf\">https://tantek.com/2019/233/e1/homebrew-website-club-sf</a><br />More: <a href=\"https://indieweb.org/events/2019-08-21-homebrew-website-club#San_Francisco\">https://indieweb.org/events/2019-08-21-homebrew-website-club#San_Francisco</a>"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "rsvp",
    "refs": {
        "https://tantek.com/2019/233/e1/homebrew-website-club-sf": {
            "type": "entry",
            "url": "https://tantek.com/2019/233/e1/homebrew-website-club-sf",
            "name": "Tantek\u2019s event",
            "post-type": "article"
        }
    },
    "_id": "4974517",
    "_source": "1",
    "_is_read": true
}

{
    "type": "entry",
    "author": {
        "name": "Neil Mather",
        "url": "https://doubleloop.net/",
        "photo": null
    },
    "url": "https://doubleloop.net/2019/08/21/showing-indieauth-and-micropub-at-hwclondon/",
    "published": "2019-08-21T18:37:56+00:00",
    "content": {
        "html": "Showing IndieAuth and Micropub at HWCLondon!",
        "text": "Showing IndieAuth and Micropub at HWCLondon!"
    },
    "post-type": "note",
    "_id": "4973134",
    "_source": "1895",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2019-08-21T13:52:01.50788-07:00",
    "url": "https://v2.jacky.wtf/post/7c5536af-9925-4675-92af-d0b77393e3fc",
    "in-reply-to": [
        "https://beesbuzz.biz/blog/chatter/8726-Re-Intermediate-auth-service"
    ],
    "content": {
        "text": "Haha, yup! That said, I\u2019ll definitely ping you (and drop it in the IndieWeb chat) when I get this base-line system going. Going to tear down what I have with https://fortress.black.af to focus on this.",
        "html": "<p>Haha, yup! That said, I\u2019ll definitely ping you (and drop it in the IndieWeb chat) when I get this base-line system going. Going to tear down what I have with <a href=\"https://fortress.black.af\">https://fortress.black.af</a> to focus on this.</p>"
    },
    "post-type": "reply",
    "refs": {
        "https://beesbuzz.biz/blog/chatter/8726-Re-Intermediate-auth-service": {
            "type": "entry",
            "url": "https://beesbuzz.biz/blog/chatter/8726-Re-Intermediate-auth-service",
            "name": "Re: Intermediate auth service",
            "post-type": "article"
        }
    },
    "_id": "4972100",
    "_source": "1886",
    "_is_read": true
}

Tantek Çelik tantek.com

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
}

Matthias Pfefferle notiz.blog/author/matthias-pfefferle/

{
    "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
}

Added Mastodon Autopost Plugin to WordPress Blog

{
    "type": "entry",
    "author": {
        "name": "Ton Zijlstra",
        "url": "https://www.zylstra.org/blog",
        "photo": null
    },
    "url": "https://www.zylstra.org/blog/2019/08/added-mastodon-autopost-plugin-to-wordpress-blog/",
    "published": "2019-08-14T15:49:53+02:00",
    "content": {
        "html": "<p>I\u2019ve added a plugin, <a href=\"https://wordpress.org/plugins/autopost-to-mastodon/\">Mastodon Autopost</a>, to crosspost from this blog to my Mastodon instance.<br />This won\u2019t bring back any reactions to this blog, unlike Twitter reactions which do get back to this blog through Webmention. For that I would need to use Bridgy Fed. However that has as a disadvantage that it would turn my blog into a separate ActivityPub account, an activitypub user in its own right. </p>\n<p>For now I\u2019d rather have a separate Mastodon account (on my personal instance). Not everything I post on my blog I want to post to Mastodon, and not everything I post on Mastodon I want to have in my blog (e.g. responses to or reposts of others). I can definitely see me using this blog as the one and only hub for my online communications, but for that to work, I want to be able to keep ephemeral postings outside my regular site and my rss feeds, and more importantly be able to determine intended audiences per posting. Another requirement is that I can post tweets about a blogpost without that tweet being a separate blogpost (now I use the post excerpt for that and send it to twitter)</p>\n<p>Currently I have <a href=\"https://m.tzyl.nl/@ton\">my Mastodon</a> (and <a href=\"https://twitter.com/tonzylstra\">my first Twitter account</a>) set to me needing to approve every follower. My audience for a message is somewhat known to me that way, and I can shape a message accordingly. We all talk differently to different people and have conversations in different settings and contexts. This is true for online conversations just as much as for offline conversations. <a href=\"https://micro.blog/ton\">My microblog</a> account does post everything from my blog but I also interact there independently from my blog.</p>\n<p>With this plugin, for each posting I can determine if it is cross posted to Mastodon. I already had a similar setting for Twitter (and Flickr, which I don\u2019t use). See the images.</p>\n<p><img src=\"https://aperture-proxy.p3k.io/2fa2350dba9fe262bc8541208abb113a08fc453b/68747470733a2f2f7777772e7a796c737472612e6f72672f77702f77702d636f6e74656e742f75706c6f6164732f323031392f30382f6d6173746f646f6e73657474696e672e706e67\" alt=\"\" /><img src=\"https://aperture-proxy.p3k.io/8f29beda26458260f199762780e5e16e397db5eb/68747470733a2f2f7777772e7a796c737472612e6f72672f77702f77702d636f6e74656e742f75706c6f6164732f323031392f30382f7477697474657273657474696e672d333030783136382e706e67\" alt=\"\" /></p>\n<p>[UPDATE]<br />It works as intended. I set the excerpt of this posting to \u201cIf all works as intended, this blogpost should show up in my Mastodon instance #wordpress #activitypub\u201d, and set the plugin to post title, excerpt and URL. </p>\n<p><img src=\"https://aperture-proxy.p3k.io/4838da347719797955857925c158ddd24fb50351/68747470733a2f2f7777772e7a796c737472612e6f72672f77702f77702d636f6e74656e742f75706c6f6164732f323031392f30382f66697273747770746f6f742d363430783335332e706e67\" alt=\"\" /><br />[/UPDATE]</p>",
        "text": "I\u2019ve added a plugin, Mastodon Autopost, to crosspost from this blog to my Mastodon instance.\nThis won\u2019t bring back any reactions to this blog, unlike Twitter reactions which do get back to this blog through Webmention. For that I would need to use Bridgy Fed. However that has as a disadvantage that it would turn my blog into a separate ActivityPub account, an activitypub user in its own right. \nFor now I\u2019d rather have a separate Mastodon account (on my personal instance). Not everything I post on my blog I want to post to Mastodon, and not everything I post on Mastodon I want to have in my blog (e.g. responses to or reposts of others). I can definitely see me using this blog as the one and only hub for my online communications, but for that to work, I want to be able to keep ephemeral postings outside my regular site and my rss feeds, and more importantly be able to determine intended audiences per posting. Another requirement is that I can post tweets about a blogpost without that tweet being a separate blogpost (now I use the post excerpt for that and send it to twitter)\nCurrently I have my Mastodon (and my first Twitter account) set to me needing to approve every follower. My audience for a message is somewhat known to me that way, and I can shape a message accordingly. We all talk differently to different people and have conversations in different settings and contexts. This is true for online conversations just as much as for offline conversations. My microblog account does post everything from my blog but I also interact there independently from my blog.\nWith this plugin, for each posting I can determine if it is cross posted to Mastodon. I already had a similar setting for Twitter (and Flickr, which I don\u2019t use). See the images.\n\n[UPDATE]\nIt works as intended. I set the excerpt of this posting to \u201cIf all works as intended, this blogpost should show up in my Mastodon instance #wordpress #activitypub\u201d, and set the plugin to post title, excerpt and URL. \n\n[/UPDATE]"
    },
    "name": "Added Mastodon Autopost Plugin to WordPress Blog",
    "post-type": "article",
    "_id": "4891194",
    "_source": "474",
    "_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
}

Manton Reece www.manton.org

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
}

Marty McGuire martymcgui.re

{
    "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
}

Week Notes 19#32

{
    "type": "entry",
    "author": {
        "name": "Ton Zijlstra",
        "url": "https://www.zylstra.org/blog",
        "photo": null
    },
    "url": "https://www.zylstra.org/blog/2019/08/week-notes-1932/",
    "published": "2019-08-11T19:40:19+02:00",
    "content": {
        "html": "<p>A pretty regular week, albeit with interrupted nights, so fatigue level rose steadily over the week.</p>\n<ul><li>Further discussions of contracts for an upcoming project in SE-Asia. Worried that these discussions are now eroding the time for execution of the projects first phase (completion date for that phase is a fixed element), meaning compression of work and planning problems.</li>\n<li>Spent ample time on a project for a province that started last week.</li>\n<li>Decided on the <a href=\"https://www.zylstra.org/blog/2019/08/codam-will-host-indiewebcamp-amsterdam/\">location</a> for <a href=\"https://indiewebcamp.nl/\">IndieWebCamp Amsterdam</a>, and opened <a href=\"https://www.eventbrite.com/e/indiewebcamp-amsterdam-tickets-68004881431\">registration</a> for it</li>\n<li>Did a little bit of work on a tender with a EU wide consortium, but much less than I wanted.</li>\n<li>Worked on the energy poverty project and a circular economy project for a province</li>\n<li>Discussed a 2yr data governance program for provincial level governments with colleagues, in which socio-economic impact, digital transformation, ethics, it choices and data management are approached as the interconnected and interdependent things they are</li>\n<li>Was <a href=\"https://www.zylstra.org/blog/2019/08/preparing-for-energie-digital/\">interviewed</a> for an upcoming speaking gig in Germany next month. The <a href=\"https://www.zylstra.org/blog/2019/08/open-data-used-for-energy-transition/\">video</a> has been published already.</li>\n</ul><p><a href=\"https://www.flickr.com/photos/taramarie/14147432710/\"><img src=\"https://aperture-proxy.p3k.io/b19dc58262010cd2b314822f37c93481819ae8ed/68747470733a2f2f6c6976652e737461746963666c69636b722e636f6d2f333839362f31343134373433323731305f323264313861366233632e6a7067\" alt=\"32\" /></a><br /><em>32, by Tara Schmidt, license CC BY</em></p>",
        "text": "A pretty regular week, albeit with interrupted nights, so fatigue level rose steadily over the week.\nFurther discussions of contracts for an upcoming project in SE-Asia. Worried that these discussions are now eroding the time for execution of the projects first phase (completion date for that phase is a fixed element), meaning compression of work and planning problems.\nSpent ample time on a project for a province that started last week.\nDecided on the location for IndieWebCamp Amsterdam, and opened registration for it\nDid a little bit of work on a tender with a EU wide consortium, but much less than I wanted.\nWorked on the energy poverty project and a circular economy project for a province\nDiscussed a 2yr data governance program for provincial level governments with colleagues, in which socio-economic impact, digital transformation, ethics, it choices and data management are approached as the interconnected and interdependent things they are\nWas interviewed for an upcoming speaking gig in Germany next month. The video has been published already.\n\n32, by Tara Schmidt, license CC BY"
    },
    "name": "Week Notes 19#32",
    "post-type": "article",
    "_id": "4854479",
    "_source": "474",
    "_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
}

Tantek Çelik tantek.com

{
    "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
}

CODAM Will Host IndieWebCamp Amsterdam

{
    "type": "entry",
    "author": {
        "name": "Ton Zijlstra",
        "url": "https://www.zylstra.org/blog",
        "photo": null
    },
    "url": "https://www.zylstra.org/blog/2019/08/codam-will-host-indiewebcamp-amsterdam/",
    "published": "2019-08-06T09:16:44+02:00",
    "content": {
        "html": "<p>Yesterday I visited <a href=\"http://codam.nl/\">CODAM</a>, a new Amsterdam coding college. It\u2019s part of the <a href=\"https://42.fr/\">42</a> network, which originated in France, and offers a free 4 year curriculum to learn how to code (one or more of unix, graphics, machine learning). The education is free, and aimed at those who didn\u2019t fit or couldn\u2019t afford the regular educational options, dropped out or never had the opportunity to opt-in. The commitment is however large. The first month is a heavy filter, expecting students to keep a steady rhythm, and afterwards a high attendance is expected (some 50 hours per week).</p>\n<p>CODAM\u2019s mission of allowing students from all backgrounds to increase their capabilities, using coding skills as a path to agency, has a good overlap with the IndieWeb\u2019s ambition of allowing people to own their own on-line identity, be in control of what they publish and share, and  connect and interact outside the silos. </p>\n<p>A month ago CODAM\u2019s Lisa Stamm, the community and communications person, offered CODAM as a venue for <a href=\"https://indiewebcamp.nl/\">IndieWebCamp Amsterdam</a>. Yesterday I had the opportunity to visit their location on the old Amsterdam naval yard, near Central Station. CODAM and their location are a good fit with IndieWebCamp\u2019s needs, so the conclusion was easy: </p>\n<p>IndieWebCamp Amsterdam will take place at CODAM on September 28th and 29th. </p>\n<p><a href=\"https://www.eventbrite.com/e/indiewebcamp-amsterdam-tickets-68004881431\">Registration is already open</a>, and free of charge. Both the <a href=\"https://2019.viewsourceconf.org/\">View Source conference</a> and the <a href=\"https://fronteers.nl/congres\">Fronteers conference</a> take place in the days after, so if you\u2019re in web dev you could turn it into a full week in Amsterdam.</p>\n<p>Some pictures of the CODAM venue, and its surroundings below</p>\n<p><a href=\"https://www.flickr.com/photos/tonz/48461436717/in/datetaken/\"><img src=\"https://aperture-proxy.p3k.io/c2c5c556645d5a3f43b8343bf698b3738ad1b54c/68747470733a2f2f6c6976652e737461746963666c69636b722e636f6d2f36353533352f34383436313433363731375f396233643533373434345f7a2e6a7067\" alt=\"20190805_095105\" /></a></p>\n<p><a href=\"https://www.flickr.com/photos/tonz/48461278291/in/datetaken/\"><img src=\"https://aperture-proxy.p3k.io/4765aa9b6d1bc7b136b3d7057881c8135b7ac469/68747470733a2f2f6c6976652e737461746963666c69636b722e636f6d2f36353533352f34383436313237383239315f343834666162383064335f6e2e6a7067\" alt=\"20190805_103445\" /></a> <a href=\"https://www.flickr.com/photos/tonz/48461444882/in/datetaken/\"><img src=\"https://aperture-proxy.p3k.io/e334c9795ef0aeccb60568f0c022b296cc28c9d3/68747470733a2f2f6c6976652e737461746963666c69636b722e636f6d2f36353533352f34383436313434343838325f326230663734396333375f6e2e6a7067\" alt=\"20190805_103758\" /></a></p>\n<p><a href=\"https://www.flickr.com/photos/tonz/48461275306/in/datetaken/\"><img src=\"https://aperture-proxy.p3k.io/c4338efb623fe92b78319b444493f0448e9f77bb/68747470733a2f2f6c6976652e737461746963666c69636b722e636f6d2f36353533352f34383436313237353330365f356138353465346664615f6e2e6a7067\" alt=\"20190805_095556\" /></a> <a href=\"https://www.flickr.com/photos/tonz/48461442402/in/datetaken/\"><img src=\"https://aperture-proxy.p3k.io/f04030fdbf8c6a5df665b55b3d3b9844deb72a2b/68747470733a2f2f6c6976652e737461746963666c69636b722e636f6d2f36353533352f34383436313434323430325f383965666464396139355f6e2e6a7067\" alt=\"20190805_103420\" /></a></p>\n<p><a href=\"https://www.flickr.com/photos/tonz/48461277511/in/datetaken/\"><img src=\"https://aperture-proxy.p3k.io/f0538c1dbe111cd74d03e4d47dd27352410e05f6/68747470733a2f2f6c6976652e737461746963666c69636b722e636f6d2f36353533352f34383436313237373531315f653061653538616234645f6e2e6a7067\" alt=\"20190805_103358\" /></a> <a href=\"https://www.flickr.com/photos/tonz/48461443727/in/datetaken/\"><img src=\"https://aperture-proxy.p3k.io/55eba606f086e928cf7328fa6e24f8ee05e9047d/68747470733a2f2f6c6976652e737461746963666c69636b722e636f6d2f36353533352f34383436313434333732375f613762393562346264645f6e2e6a7067\" alt=\"20190805_103624\" /></a></p>\n<p><a href=\"https://www.flickr.com/photos/tonz/48461445702/in/datetaken/\"><img src=\"https://aperture-proxy.p3k.io/03e451936df50c604337970c16fcf66997749278/68747470733a2f2f6c6976652e737461746963666c69636b722e636f6d2f36353533352f34383436313434353730325f313035666531346435325f7a2e6a7067\" alt=\"20190805_105423\" /></a></p>",
        "text": "Yesterday I visited CODAM, a new Amsterdam coding college. It\u2019s part of the 42 network, which originated in France, and offers a free 4 year curriculum to learn how to code (one or more of unix, graphics, machine learning). The education is free, and aimed at those who didn\u2019t fit or couldn\u2019t afford the regular educational options, dropped out or never had the opportunity to opt-in. The commitment is however large. The first month is a heavy filter, expecting students to keep a steady rhythm, and afterwards a high attendance is expected (some 50 hours per week).\nCODAM\u2019s mission of allowing students from all backgrounds to increase their capabilities, using coding skills as a path to agency, has a good overlap with the IndieWeb\u2019s ambition of allowing people to own their own on-line identity, be in control of what they publish and share, and  connect and interact outside the silos. \nA month ago CODAM\u2019s Lisa Stamm, the community and communications person, offered CODAM as a venue for IndieWebCamp Amsterdam. Yesterday I had the opportunity to visit their location on the old Amsterdam naval yard, near Central Station. CODAM and their location are a good fit with IndieWebCamp\u2019s needs, so the conclusion was easy: \nIndieWebCamp Amsterdam will take place at CODAM on September 28th and 29th. \nRegistration is already open, and free of charge. Both the View Source conference and the Fronteers conference take place in the days after, so if you\u2019re in web dev you could turn it into a full week in Amsterdam.\nSome pictures of the CODAM venue, and its surroundings below"
    },
    "name": "CODAM Will Host IndieWebCamp Amsterdam",
    "post-type": "article",
    "_id": "4832325",
    "_source": "474",
    "_is_read": true
}