A journey to the underworld that is RDF

{
    "type": "entry",
    "author": {
        "name": null,
        "url": "https://petermolnar.net/",
        "photo": null
    },
    "url": "https://petermolnar.net/article/web-of-the-machines/",
    "published": "2019-02-10T20:10:00+00:00",
    "content": {
        "html": "<img src=\"https://petermolnar.net/article/web-of-the-machines/rdf-it-does-not-spark-joy.jpg\" title=\"rdf-it-does-not-spark-joy.jpg\" alt=\"working with RDF - this one does not spark joy\" />\n    working 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/#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/#fn2\">2</a>. Last year, in August, I added microdata<a href=\"https://petermolnar.net/#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/#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/#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<img src=\"https://petermolnar.net/article/web-of-the-machines/gsdtt_microdata_error_01.png\" title=\"gsdtt_microdata_error_01.png\" alt=\"Interesting, it has some problems...\" />\n    Interesting, it has some problems...\n<img src=\"https://petermolnar.net/article/web-of-the-machines/gsdtt_microdata_error_02.png\" title=\"gsdtt_microdata_error_02.png\" alt=\"it says URL for org is missing... it's there. Line 13.\" />\n    it 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<img src=\"https://petermolnar.net/article/web-of-the-machines/gsdtt_rdfa_error_01.png\" title=\"gsdtt_rdfa_error_01.png\" alt=\"Undefined type, eh?\" />\n    Undefined type, eh?\n<img src=\"https://petermolnar.net/article/web-of-the-machines/gsdtt_rdfa_error_02.png\" title=\"gsdtt_rdfa_error_02.png\" alt=\"wat\" />\n    wat\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/#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<h2>Footnotes</h2>\n<p>Out of the blue, Maria from 3WhiteHats pinged me with an article of their on how to do structured data on your site<a href=\"https://petermolnar.net/#fn7\">7</a> - it's useful, and it's good, especially the troubleshooting at the bottom of the entry.</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/#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/#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/#fnref3\">\u21a9</a></p></li>\n<li><p><a href=\"https://www.ampproject.org/\">https://www.ampproject.org/</a><a href=\"https://petermolnar.net/#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/#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/#fnref6\">\u21a9</a></p></li>\n<li><p><a href=\"https://www.3whitehats.co.nz/knowledge/guide-to-structured-data-seo/\">https://www.3whitehats.co.nz/knowledge/guide-to-structured-data-seo/</a><a href=\"https://petermolnar.net/#fnref7\">\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    Interesting, it has some problems...\n\n    it 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    Undefined type, eh?\n\n    wat\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.\nFootnotes\nOut of the blue, Maria from 3WhiteHats pinged me with an article of their on how to do structured data on your site7 - it's useful, and it's good, especially the troubleshooting at the bottom of the entry.\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\nhttps://www.3whitehats.co.nz/knowledge/guide-to-structured-data-seo/\u21a9"
    },
    "name": "A journey to the underworld that is RDF",
    "post-type": "article",
    "_id": "12055272",
    "_source": "268",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-05-30T20:51:53.51990-07:00",
    "url": "https://v2.jacky.wtf/post/b17e4a23-44d9-4c8f-9f6a-4e4cf9d2e5b5",
    "in-reply-to": [
        "https://twitter.com/Cambridgeport90/status/1266939257618403329"
    ],
    "content": {
        "text": "Well, the IndieWeb doesn\u2019t necessarily have like a devrel team to help build out things for each language / stack - it\u2019s been mostly on what people are coming in with. Like I was lucky to find a microformats2 parsing library in Elixir but I\u2019ve had to write everything else if I wanted it to be in Elixir as well.",
        "html": "<p>Well, the IndieWeb doesn\u2019t necessarily have like a devrel team to help build out things for each language / stack - it\u2019s been mostly on what people are coming in with. Like I was lucky to find a microformats2 parsing library in Elixir but I\u2019ve had to write everything else if I wanted it to be in Elixir as well.</p>"
    },
    "author": {
        "type": "card",
        "name": "",
        "url": "https://v2.jacky.wtf",
        "photo": null
    },
    "post-type": "reply",
    "refs": {
        "https://twitter.com/Cambridgeport90/status/1266939257618403329": {
            "type": "entry",
            "url": "https://twitter.com/Cambridgeport90/status/1266939257618403329",
            "content": {
                "text": "I find it odd ... just the fact that through it's history, the #IndieWeb has pretty much ignored #dotnet. I understand why at the beginning, but not now."
            },
            "author": {
                "type": "card",
                "name": "",
                "url": "https://v2.jacky.wtf/stream",
                "photo": null
            },
            "post-type": "note"
        }
    },
    "_id": "12021126",
    "_source": "1886",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-05-30T20:44:55.46330-07:00",
    "url": "https://v2.jacky.wtf/post/084c1c15-76f4-4384-850b-ceaf81a22c54",
    "category": [
        "",
        "-adjacent"
    ],
    "in-reply-to": [
        "https://twitter.com/Cambridgeport90/status/1266905514027474949"
    ],
    "content": {
        "text": "If that does end up happening, let me know. I\u2019m comfortable with C# and would love to help see a C#-adjacent library for IndieWeb stuff come to light.",
        "html": "<p>If that does end up happening, let me know. I\u2019m comfortable with C<strong class=\"p-category\">#</strong> and would love to help see a C<strong class=\"p-category\">#-adjacent</strong> library for IndieWeb stuff come to light.</p>"
    },
    "author": {
        "type": "card",
        "name": "",
        "url": "https://v2.jacky.wtf",
        "photo": null
    },
    "post-type": "reply",
    "refs": {
        "https://twitter.com/Cambridgeport90/status/1266905514027474949": {
            "type": "entry",
            "url": "https://twitter.com/Cambridgeport90/status/1266905514027474949",
            "content": {
                "text": "I have a funny feeling that in order for whatever I end up using to have all required #IndieWeb features, it's going to end up being something custom. And hopefully #dotnet, as well."
            },
            "author": {
                "type": "card",
                "name": "",
                "url": "https://v2.jacky.wtf/stream",
                "photo": null
            },
            "post-type": "note"
        }
    },
    "_id": "12021127",
    "_source": "1886",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-05-30T14:08:47-07:00",
    "url": "https://aaronparecki.com/2020/05/30/22/pineblog",
    "category": [
        "webmention",
        "indieweb"
    ],
    "content": {
        "text": "This is fantastic! Pine.blog can now receive webmentions for you, and it'll show them to you in the timeline! This is probably the best option for static sites now! https://blog.pine.blog/2020/05/bring-us-your-static-sites-yearning-to-breathe-free/",
        "html": "This is fantastic! Pine.blog can now receive webmentions for you, and it'll show them to you in the timeline! This is probably the best option for static sites now! <a href=\"https://blog.pine.blog/2020/05/bring-us-your-static-sites-yearning-to-breathe-free/\"><span>https://</span>blog.pine.blog/2020/05/bring-us-your-static-sites-yearning-to-breathe-free/</a>"
    },
    "author": {
        "type": "card",
        "name": "Aaron Parecki",
        "url": "https://aaronparecki.com/",
        "photo": "https://aperture-media.p3k.io/aaronparecki.com/41061f9de825966faa22e9c42830e1d4a614a321213b4575b9488aa93f89817a.jpg"
    },
    "post-type": "note",
    "_id": "12013156",
    "_source": "16",
    "_is_read": true
}

ThreadReader app via Micropub to blog

{
    "type": "entry",
    "author": {
        "name": "<span class='p-author h-card'>allaboutgeorge</span>",
        "url": "https://www.allaboutgeorge.com/",
        "photo": null
    },
    "url": "https://www.allaboutgeorge.com/2020/05/29/threadreader-app-via-micropub-to-blog/",
    "published": "2020-05-29T19:08:41-08:00",
    "content": {
        "html": "<a href=\"https://boffosocko.com/2020/05/28/threadreaderapp-micropub-to-blog/\">ThreadReaderApp now has beta support for the Micropub Spec so you can publish Twitter threads directly to your blog</a> by <a href=\"https://boffosocko.com/\"><img src=\"https://secure.gravatar.com/avatar/d5fb4e498fe609cc29b04e5b7ad688c4?s=96&amp;d=identicon&amp;r=pg\" alt=\"Chris Aldrich\" />Chris Aldrich</a>\n<blockquote>So\u2026 a while back I tweeted about a bit of functionality I\u2019ve long thought would be a cool one to have for Twitter:\nhttps://twitter.com/ChrisAldrich/status/1236046889054654465\nI would often see people post tweetstorms, long threads of related tweets, to tell an extended story.\nInvariably people s...</blockquote>\n\nThis is cool, and an important reminder (of all weeks) that ways to share on Twitter needn\u2019t stay there",
        "text": "ThreadReaderApp now has beta support for the Micropub Spec so you can publish Twitter threads directly to your blog by Chris Aldrich\nSo\u2026 a while back I tweeted about a bit of functionality I\u2019ve long thought would be a cool one to have for Twitter:\nhttps://twitter.com/ChrisAldrich/status/1236046889054654465\nI would often see people post tweetstorms, long threads of related tweets, to tell an extended story.\nInvariably people s...\n\nThis is cool, and an important reminder (of all weeks) that ways to share on Twitter needn\u2019t stay there"
    },
    "name": "ThreadReader app via Micropub to blog",
    "post-type": "article",
    "_id": "11994389",
    "_source": "4592",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-05-28T17:53:54.16049-07:00",
    "url": "https://v2.jacky.wtf/post/29362930-b34b-44de-8dd4-e0834fbbf2e8",
    "content": {
        "text": "Going to go live in about 10 minutes at https://jacky.wtf/twitch. Focusing on working on code coverage for my IndieWeb library for Elixir so definitely going to be either looking to splunk on good Elixir practices and what the IndieWeb suggests for behavior! Pull up in 10!",
        "html": "<p>Going to go live in about 10 minutes at <a href=\"https://jacky.wtf/twitch\">https://jacky.wtf/twitch</a>. Focusing on working on code coverage for my IndieWeb library for Elixir so definitely going to be either looking to splunk on good Elixir practices and what the IndieWeb suggests for behavior! Pull up in 10!</p>"
    },
    "author": {
        "type": "card",
        "name": "",
        "url": "https://v2.jacky.wtf",
        "photo": null
    },
    "post-type": "note",
    "_id": "11985920",
    "_source": "1886",
    "_is_read": true
}

Es ging nie um Matrix

{
    "type": "entry",
    "published": "2020-05-29T20:54:13+02:00",
    "url": "https://notiz.blog/2020/05/29/es-ging-nie-um-matrix/",
    "name": "Es ging nie um Matrix",
    "content": {
        "text": "Meine letzten beiden Blogposts wurden glaube ich etwas falsch verstanden, deshalb hier eine kleine Richtigstellung.\n\n\n\nIch hatte mich sehr gefreut (als ich f\u00e4lschlicherweise dachte hoffte), dass WordPress vielleicht Matrix kompatibel wird und ich hatte mich etwas ge\u00e4rgert, als sich dann herausstellte, dass es nie darum ging WordPress in die Matrix zu bringen.\n\n\n\nFrank hat mir dann auf Twitter geschrieben, dass es ja auch andere Wege gibt um ans gleiche Ziel zu kommen.\n\n\n\nIch ne, vielleicht per Trac in den core bringen.\n\n\n\n\u2026und Stefan hat es dann in den Kommentaren noch etwas konkretisiert.\n\n\n\nGenau! WordPress ist OpenSource. Was hindert uns dem Wunsch zur Vaterschaft zu verhelfen?!\n\n\n\nMacht Sinn! WordPress ist OpenSource Software und hat eine ziemlich umfassende Plugin API\u2026\n\n\n\nWarum also nicht einfach selber machen?\n\n\n\n\u2026und genau das ist die entscheidende Frage!\n\n\n\nMir ging es nie darum, dass speziell Matrix in WordPress integriert wird und ich war auch nie wirklich traurig, dass es nur ein Missverst\u00e4ndnis war. Ich bin nicht mal ein gro\u00dfer Fan von Matrix und es gibt eine ganze Reihe an Protokollen die ich viel liebe integriert sehen w\u00fcrde.\n\n\n\nIch hatte statt dessen gehofft, dass sich eine Firma wie Automattic f\u00fcr das Thema dezentrale Netze, Fediverse, IndieWeb, oder wie auch immer man es nennen will, interessieren k\u00f6nnte und sogar Geld in die Hand nehmen w\u00fcrde um WordPress zu einem Teil dieser Bewegung zu machen.\n\n\n\n\u201eSelber machen\u201c probiere ich jetzt seit DataPortability.org (also seit ungef\u00e4hr 2007/2008) mit nur m\u00e4\u00dfigem Erfolg. F\u00fcr ein Side-Project ist das Thema einfach zu gro\u00df und investieren will leider auch niemand so wirklich.\n\n\n\nNaja\u2026 vielleicht zieht ja irgendwann mein geheimer Masterplan \ud83d\ude09",
        "html": "<p>Meine letzten beiden Blogposts wurden glaube ich etwas falsch verstanden, deshalb hier eine kleine Richtigstellung.</p>\n\n\n\n<p><a href=\"https://notiz.blog/2020/05/24/wordpress-in-der-matrix/\">Ich hatte mich sehr gefreut</a> (als ich f\u00e4lschlicherweise dachte hoffte), dass WordPress vielleicht Matrix kompatibel wird und <a href=\"https://notiz.blog/2020/05/26/egal-matrix-is-eh-doof/\">ich hatte mich etwas ge\u00e4rgert</a>, als sich dann herausstellte, dass es nie darum ging WordPress in die Matrix zu bringen.</p>\n\n\n\n<p><a href=\"https://twitter.com/bueltge/status/1265355452927348737\">Frank</a> hat mir dann auf Twitter geschrieben, dass es ja auch andere Wege gibt um ans gleiche Ziel zu kommen.</p>\n\n\n\n<blockquote><p>Ich ne, vielleicht per Trac in den core bringen.</p></blockquote>\n\n\n\n<p>\u2026und <a href=\"https://notiz.blog/2020/05/26/egal-matrix-is-eh-doof/#comment-1168849\">Stefan</a> hat es dann in den Kommentaren noch etwas konkretisiert.</p>\n\n\n\n<blockquote><p>Genau! WordPress ist OpenSource. Was hindert uns dem Wunsch zur Vaterschaft zu verhelfen?!</p></blockquote>\n\n\n\n<p>Macht Sinn! WordPress ist OpenSource Software und hat eine ziemlich umfassende Plugin API\u2026</p>\n\n\n\n<p>Warum also nicht einfach selber machen?</p>\n\n\n\n<p><strong>\u2026und genau das ist die entscheidende Frage!</strong></p>\n\n\n\n<img src=\"https://notiz.blog/wp-content/uploads/2019/09/FediverseDiagram-700x709.png\" alt=\"\" width=\"350\" height=\"355\" />\n\n\n\n<p>Mir ging es nie darum, dass speziell <strong>Matrix</strong> in WordPress integriert wird und ich war auch nie wirklich traurig, dass es nur ein Missverst\u00e4ndnis war. Ich bin nicht mal ein gro\u00dfer Fan von Matrix und es gibt eine ganze Reihe an Protokollen die ich viel liebe integriert sehen w\u00fcrde.</p>\n\n\n\n<p>Ich hatte statt dessen gehofft, dass sich eine Firma wie Automattic f\u00fcr das Thema <em>dezentrale Netze</em>, <em>Fediverse</em>, <em>IndieWeb</em>, <em>oder wie auch immer man es nennen will</em>, interessieren k\u00f6nnte und sogar Geld in die Hand nehmen w\u00fcrde um WordPress zu einem Teil dieser Bewegung zu machen.</p>\n\n\n\n<p>\u201eSelber machen\u201c probiere ich jetzt seit <a href=\"https://notiz.blog/2007/11/19/dataportabilityorg/\">DataPortability.org</a> (also seit ungef\u00e4hr 2007/2008) mit nur m\u00e4\u00dfigem Erfolg. F\u00fcr ein Side-Project ist das Thema einfach zu gro\u00df und investieren will leider auch niemand so wirklich.</p>\n\n\n\n<p>Naja\u2026 vielleicht zieht ja irgendwann mein geheimer Masterplan \ud83d\ude09</p>"
    },
    "author": {
        "type": "card",
        "name": "Matthias Pfefferle",
        "url": "https://notiz.blog/author/matthias-pfefferle/",
        "photo": "https://secure.gravatar.com/avatar/75512bb584bbceae57dfc503692b16b2?s=40&d=mm&r=g"
    },
    "post-type": "article",
    "_id": "11983099",
    "_source": "206",
    "_is_read": true
}

Closing the microblogging Slack

{
    "type": "entry",
    "author": {
        "name": "Manton Reece",
        "url": "https://www.manton.org/",
        "photo": "https://micro.blog/manton/avatar.jpg"
    },
    "url": "https://www.manton.org/2020/05/28/closing-the-microblogging.html",
    "name": "Closing the microblogging Slack",
    "content": {
        "html": "<p>Three years ago I created microblogging.slack.com to chat about indie microblogging and Micro.blog. There have been many great discussions in that time, and I appreciate everyone who has contributed or helped other members of the Micro.blog community. But to continue to improve Micro.blog regularly, I need to focus on fewer support channels.</p>\n\n<p>Daniel Jalkut and I talked about this <a href=\"https://coreint.org/2020/05/episode-421-replacing-it-with-nothing/\">on Core Intuition 421</a>. It is not sustainable for me to work on new Micro.blog features at the current pace as well as be responsive in Slack. If someone has a question about Micro.blog, I want to point them to the best place to get a thorough answer, and that\u2019s email.</p>\n\n<p>Slack also has a couple problems:</p>\n\n<ul><li>It\u2019s a proprietary platform that doesn\u2019t fit well with our goals for Micro.blog. For example, you can\u2019t have your own domain name for Slack, which makes migrating away very difficult.</li>\n<li>Because the search is limited to only recent messages, it is less useful as a resource to new members.</li>\n</ul><p>Last year, Jean MacDonald and I considered replacing Slack with Discourse. We may still do that, or it may be that forums around microblogging should best be run by the community rather than an official channel of Micro.blog. There is also a great <a href=\"https://chat.indieweb.org/\">IndieWeb chat</a> accessible via Slack.</p>\n\n<p>This weekend, I\u2019ll be closing the current Slack. I will export all the data for backup \u2014 just in case we want to rebuild it in the future, or make the messages searchable \u2014 and then I\u2019ll completely delete the Slack account, unless I can find a more elegant way to handle shutting it down or pausing it.</p>\n\n<p>Thanks again to everyone who has participated in the Slack community, sending feature requests, helping others with Hugo theme questions, and just being supportive of the mission of Micro.blog. See you on Micro.blog!</p>",
        "text": "Three years ago I created microblogging.slack.com to chat about indie microblogging and Micro.blog. There have been many great discussions in that time, and I appreciate everyone who has contributed or helped other members of the Micro.blog community. But to continue to improve Micro.blog regularly, I need to focus on fewer support channels.\n\nDaniel Jalkut and I talked about this on Core Intuition 421. It is not sustainable for me to work on new Micro.blog features at the current pace as well as be responsive in Slack. If someone has a question about Micro.blog, I want to point them to the best place to get a thorough answer, and that\u2019s email.\n\nSlack also has a couple problems:\n\nIt\u2019s a proprietary platform that doesn\u2019t fit well with our goals for Micro.blog. For example, you can\u2019t have your own domain name for Slack, which makes migrating away very difficult.\nBecause the search is limited to only recent messages, it is less useful as a resource to new members.\nLast year, Jean MacDonald and I considered replacing Slack with Discourse. We may still do that, or it may be that forums around microblogging should best be run by the community rather than an official channel of Micro.blog. There is also a great IndieWeb chat accessible via Slack.\n\nThis weekend, I\u2019ll be closing the current Slack. I will export all the data for backup \u2014 just in case we want to rebuild it in the future, or make the messages searchable \u2014 and then I\u2019ll completely delete the Slack account, unless I can find a more elegant way to handle shutting it down or pausing it.\n\nThanks again to everyone who has participated in the Slack community, sending feature requests, helping others with Hugo theme questions, and just being supportive of the mission of Micro.blog. See you on Micro.blog!"
    },
    "published": "2020-05-28T13:56:13-05:00",
    "category": [
        "Essays",
        "Podcasts"
    ],
    "post-type": "article",
    "_id": "11954306",
    "_source": "12",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-05-27T23:23:03.68477-07:00",
    "url": "https://v2.jacky.wtf/post/979f783b-9aa7-49f7-b21d-0d4999f95744",
    "content": {
        "text": "I\u2019m getting an odd joy by working more on indieweb stuff because I feel that I can help people divest from environments that extract from us (our pain, our joy, anything) with little given back. Like I can see how this can help.",
        "html": "<p>I\u2019m getting an odd joy by working more on indieweb stuff because I feel that I can help people divest from environments that extract from us (our pain, our joy, anything) with little given back. Like I can see how this can help.</p>"
    },
    "author": {
        "type": "card",
        "name": "",
        "url": "https://v2.jacky.wtf",
        "photo": null
    },
    "post-type": "note",
    "_id": "11935683",
    "_source": "1886",
    "_is_read": true
}

A journey to the underworld that is RDF

{
    "type": "entry",
    "published": "2019-02-10T20:10:00+00:00",
    "url": "https://petermolnar.net/article/web-of-the-machines/",
    "name": "A journey to the underworld that is RDF",
    "content": {
        "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:\n\nRDF is a ruleset framework, which is only used to describe sets of rules\n\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\n\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...\nInteresting, it has some problems...\nit says URL for org is missing... it's there. Line 13.\n...but those errors then became ever more peculiar problems with RDFa...\nUndefined type, eh?\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.\nFootnotes\nOut of the blue, Maria from 3WhiteHats pinged me with an article of their on how to do structured data on your site7 - it's useful, and it's good, especially the troubleshooting at the bottom of the entry.\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\nhttps://www.3whitehats.co.nz/knowledge/guide-to-structured-data-seo/\u21a9",
        "html": "<img src=\"https://petermolnar.net/article/web-of-the-machines/rdf-it-does-not-spark-joy.jpg\" title=\"rdf-it-does-not-spark-joy.jpg\" alt=\"working with RDF - this one does not spark joy\" width=\"720\" height=\"342\" /><span>working with RDF - this one does not spark joy</span>\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>\n<strong>RDF</strong> is a ruleset framework, which is <strong>only used to describe sets of rules</strong>\n</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>\n<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<img src=\"https://petermolnar.net/article/web-of-the-machines/gsdtt_microdata_error_01.png\" title=\"gsdtt_microdata_error_01.png\" alt=\"Interesting, it has some problems...\" width=\"720\" height=\"391\" /><span>Interesting, it has some problems...</span>\n<img src=\"https://petermolnar.net/article/web-of-the-machines/gsdtt_microdata_error_02.png\" title=\"gsdtt_microdata_error_02.png\" alt=\"it says URL for org is missing... it's there. Line 13.\" width=\"720\" height=\"391\" /><span>it says URL for org is missing... it's there. Line 13.</span>\n<p>...but those errors then became ever more peculiar problems with RDFa...</p>\n<img src=\"https://petermolnar.net/article/web-of-the-machines/gsdtt_rdfa_error_01.png\" title=\"gsdtt_rdfa_error_01.png\" alt=\"Undefined type, eh?\" width=\"720\" height=\"391\" /><span>Undefined type, eh?</span>\n<img src=\"https://petermolnar.net/article/web-of-the-machines/gsdtt_rdfa_error_02.png\" title=\"gsdtt_rdfa_error_02.png\" alt=\"wat\" width=\"720\" height=\"391\" /><span>wat</span>\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<h2>Footnotes</h2>\n<p>Out of the blue, Maria from 3WhiteHats pinged me with an article of their on how to do structured data on your site<a href=\"https://petermolnar.net/feed/#fn7\">7</a> - it's useful, and it's good, especially the troubleshooting at the bottom of the entry.</p>\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<li><p><a href=\"https://www.3whitehats.co.nz/knowledge/guide-to-structured-data-seo/\">https://www.3whitehats.co.nz/knowledge/guide-to-structured-data-seo/</a><a href=\"https://petermolnar.net/feed/#fnref7\">\u21a9</a></p></li>\n</ol>"
    },
    "post-type": "article",
    "_id": "11917010",
    "_source": "268",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-05-26 13:24-0700",
    "url": "http://tantek.com/2020/147/t1/ten-years-mozilla-web-standards",
    "category": [
        "webStandards",
        "OpenWeb",
        "IndieWeb",
        "BigTech"
    ],
    "content": {
        "text": "Ten years ago today I started working with Mozilla on #webStandards.\n\nhttps://tantek.com/2010/146/t1/work-with-mozilla-advancing-web-standards\nhttps://twitter.com/t/status/14764431903\n\nStill @Mozilla (now @W3C AC Rep), still working for a more #OpenWeb, and for an #IndieWeb that puts users in control instead of #BigTech.",
        "html": "Ten years ago today I started working with Mozilla on #<span class=\"p-category\">webStandards</span>.<br /><br /><a href=\"https://tantek.com/2010/146/t1/work-with-mozilla-advancing-web-standards\">https://tantek.com/2010/146/t1/work-with-mozilla-advancing-web-standards</a><br /><a href=\"https://twitter.com/t/status/14764431903\">https://twitter.com/t/status/14764431903</a><br /><br />Still <a class=\"h-cassis-username\" href=\"https://twitter.com/Mozilla\">@Mozilla</a> (now <a class=\"h-cassis-username\" href=\"https://twitter.com/W3C\">@W3C</a> AC Rep), still working for a more #<span class=\"p-category\">OpenWeb</span>, and for an #<span class=\"p-category\">IndieWeb</span> that puts users in control instead of #<span class=\"p-category\">BigTech</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": "11901184",
    "_source": "1",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-05-26T13:21:09.87644-07:00",
    "url": "https://v2.jacky.wtf/post/d0dfa4b6-2f5b-4fae-b18e-86e844279484",
    "content": {
        "text": "I need to fix my Webmentions. And once I do, I\u2019ll go back to https://lighthouse.black.af; port the code over and move my site to lean on that instead of doing it internally so I can iterate faster, lol.",
        "html": "<p>I need to fix my Webmentions. And once I do, I\u2019ll go back to <a href=\"https://lighthouse.black.af\">https://lighthouse.black.af</a>; port the code over and move my site to lean on that instead of doing it internally so I can iterate faster, lol.</p>"
    },
    "author": {
        "type": "card",
        "name": "",
        "url": "https://v2.jacky.wtf",
        "photo": null
    },
    "post-type": "note",
    "_id": "11895274",
    "_source": "1886",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-05-26T18:52:05.16Z",
    "url": "https://www.jvt.me/mf2/2020/05/a7fhh/",
    "category": [
        "homebrew-website-club"
    ],
    "content": {
        "text": "Reminder that tomorrow is #HomebrewWebsiteClub Nottingham tomorrow - hope to see you there! https://events.indieweb.org/2020/05/online-homebrew-website-club-nottingham-Rqs1Cfcxii4D",
        "html": "<p>Reminder that tomorrow is <a href=\"https://www.jvt.me/tags/homebrew-website-club/\">#HomebrewWebsiteClub</a> Nottingham tomorrow - hope to see you there! <a href=\"https://events.indieweb.org/2020/05/online-homebrew-website-club-nottingham-Rqs1Cfcxii4D\">https://events.indieweb.org/2020/05/online-homebrew-website-club-nottingham-Rqs1Cfcxii4D</a></p>"
    },
    "author": {
        "type": "card",
        "name": "Jamie Tanna",
        "url": "https://www.jvt.me",
        "photo": "https://www.jvt.me/img/profile.png"
    },
    "post-type": "note",
    "_id": "11894089",
    "_source": "2169",
    "_is_read": true
}

Egal, Matrix is eh doof!

{
    "type": "entry",
    "published": "2020-05-26T20:13:35+02:00",
    "url": "https://notiz.blog/2020/05/26/egal-matrix-is-eh-doof/",
    "name": "Egal, Matrix is eh doof!",
    "content": {
        "text": "WordPress und Matrix \u201eheiraten\u201c wohl doch nicht, wie ich im vorherigen Post gehofft hatte \ud83d\ude41\n\n\n\nCaspar hat mich in den Kommentaren auf einen Tweet von Matt Mullenweg hingewiesen, in dem er das nochmal klar stellt.\n\n\n\n\nThe same way that WP folks mix up New Vector, Modular, Riot, and Matrix, people outside our community sometimes mix up .org and .com, Automattic and WordPress. I think the intention there was to mean .com, as it would be difficult for most shared hosts to run Matrix.\nMatt Mullenweg auf Twitter\n\n\n\n\nJetzt wo ich den Matrix Blogpost noch einmal lese, h\u00e4tte man es auch wirklich so verstehen k\u00f6nnen, wie es Matt noch einmal betont.\n\n\n\n\n[\u2026] turns out that Automattic already runs a XMPP bridge for wordpress.com over at im.wordpress.com![\u2026]. Imagine there was an excellent Matrix client available as a WordPress plugin for embedding realtime chat into your site?\nWelcoming Automattic to Matrix!\n\n\n\n\nDa war wohl der Wunsch der Vater des Gedankens.\n\n\n\nStatt einem dezentralen WordPress bekommen wir also ein WordPress.com mit einer weiteren Chat Integration.\n\n\n\nWoohooo!\n\n\n\nZumindest werden dadurch mein WordPress ActivityPub und meine IndieWeb Plugins nicht \u00fcberfl\u00fcssig.",
        "html": "<p>WordPress und Matrix \u201eheiraten\u201c wohl doch nicht, wie ich <a href=\"https://notiz.blog/2020/05/24/wordpress-in-der-matrix/\">im vorherigen Post</a> gehofft hatte \ud83d\ude41</p>\n\n\n\n<p><a href=\"https://caspar.blog/\">Caspar</a> hat mich <a href=\"https://notiz.blog/2020/05/24/wordpress-in-der-matrix/#comment-1167555\">in den Kommentaren</a> auf einen Tweet von Matt Mullenweg hingewiesen, in dem er das nochmal klar stellt.</p>\n\n\n\n<blockquote>\n<p>The same way that WP folks mix up New Vector, Modular, Riot, and Matrix, people outside our community sometimes mix up .org and .com, Automattic and WordPress. I think the intention there was to mean .com, as it would be difficult for most shared hosts to run Matrix.</p>\n<a href=\"https://twitter.com/photomatt/status/1263876235140218886\">Matt Mullenweg auf Twitter</a>\n</blockquote>\n\n\n\n<p>Jetzt wo ich den Matrix Blogpost noch einmal lese, h\u00e4tte man es auch wirklich so verstehen k\u00f6nnen, wie es Matt noch einmal betont.</p>\n\n\n\n<blockquote>\n<p>[\u2026] turns out that Automattic already runs a XMPP bridge for wordpress.com over at <a href=\"https://im.wordpress.com\">im.wordpress.com</a>![\u2026]. Imagine there was an excellent Matrix client available as a WordPress plugin for embedding realtime chat into your site?</p>\n<a href=\"https://matrix.org/blog/2020/05/21/welcoming-automattic-to-matrix\">Welcoming Automattic to Matrix!</a>\n</blockquote>\n\n\n\n<p>Da war wohl der Wunsch der Vater des Gedankens.</p>\n\n\n\n<p>Statt einem <strong>dezentralen WordPress</strong> bekommen wir also ein WordPress.com mit einer weiteren Chat Integration.</p>\n\n\n\n<p><strong>Woohooo!</strong></p>\n\n\n\n<p>Zumindest werden dadurch mein WordPress <a href=\"https://wordpress.org/plugins/activitypub/\">ActivityPub</a> und meine <a href=\"https://wordpress.org/plugins/search/indieweb/\">IndieWeb Plugins</a> nicht \u00fcberfl\u00fcssig.</p>"
    },
    "author": {
        "type": "card",
        "name": "Matthias Pfefferle",
        "url": "https://notiz.blog/author/matthias-pfefferle/",
        "photo": "https://secure.gravatar.com/avatar/75512bb584bbceae57dfc503692b16b2?s=40&d=mm&r=g"
    },
    "post-type": "article",
    "_id": "11892577",
    "_source": "206",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-05-25T18:53:54.64161-07:00",
    "url": "https://v2.jacky.wtf/post/28e9696e-1ead-42fb-adf0-715c4fe9ab44",
    "in-reply-to": [
        "https://aaronparecki.com/2020/05/25/17/"
    ],
    "content": {
        "text": "Ah okay! This is something I was wondering for Lwa - having it look for a WebSub endpoint when it\u2019s provided a feed and have it subscribe for changes so it can be more \u201cpush/pull\u201d-y when it comes to this. That should give the feel of a whole complete \u201ctransaction\u201d (though clients will need some way to be updated when a Microsub server is updated).",
        "html": "<p>Ah okay! This is something I was wondering for Lwa - having it look for a WebSub endpoint when it\u2019s provided a feed and have it subscribe for changes so it can be more \u201cpush/pull\u201d-y when it comes to this. That <em>should</em> give the feel of a whole complete \u201ctransaction\u201d (though clients will need some way to be updated when a Microsub server is updated).</p>"
    },
    "author": {
        "type": "card",
        "name": "",
        "url": "https://v2.jacky.wtf",
        "photo": null
    },
    "post-type": "reply",
    "refs": {
        "https://aaronparecki.com/2020/05/25/17/": {
            "type": "entry",
            "url": "https://aaronparecki.com/2020/05/25/17/",
            "content": {
                "text": "I still haven't implemented WebSub in Aperture yet. I think I might end up rolling all the feed fetching logic into Aperture instead of having it split out in Watchtower. \n\nRight now, it polls feeds more often if it sees them change often, so your feeds may be updated at significantly different speeds.",
                "html": "I still haven't implemented WebSub in Aperture yet. I think I might end up rolling all the feed fetching logic into Aperture instead of having it split out in Watchtower. <br /><br />Right now, it polls feeds more often if it sees them change often, so your feeds may be updated at significantly different speeds."
            },
            "author": {
                "type": "card",
                "name": "Aaron Parecki",
                "url": "https://aaronparecki.com/",
                "photo": null
            },
            "post-type": "note"
        }
    },
    "_id": "11874576",
    "_source": "1886",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-05-25T18:08:00.00000-07:00",
    "url": "https://v2.jacky.wtf/post/cf30b07e-0514-4c3a-a379-8dc9e6c1f96f",
    "content": {
        "text": "I can\u2019t tell if it\u2019s aperture (I doubt it) but my feeds don\u2019t seem to update quickly. This is me also assuming that aperture somehow knows about websub and uses that to update feeds. I\u2019m guessing that\u2019s not the case @aaronpk? How would a real time feed work with it?",
        "html": "<p>I can\u2019t tell if it\u2019s aperture (I doubt it) but my feeds don\u2019t seem to update quickly. This is me also assuming that aperture somehow knows about websub and uses that to update feeds. I\u2019m guessing that\u2019s not the case @aaronpk? How would a real time feed work with it?</p>"
    },
    "author": {
        "type": "card",
        "name": "",
        "url": "https://v2.jacky.wtf",
        "photo": null
    },
    "post-type": "note",
    "_id": "11873840",
    "_source": "1886",
    "_is_read": true
}

A hole in browser Autofill support

{
    "type": "entry",
    "published": "2020-05-25T15:21:58-0400",
    "url": "https://martymcgui.re/2020/05/25/a-hole-in-browser-autofill-support/",
    "category": [
        "IndieWeb",
        "webdev",
        "forms",
        "autocomplete",
        "autofill"
    ],
    "name": "A hole in browser Autofill support",
    "content": {
        "text": "If you've ever seen your browser automatically fill in your shipping address, or seen your iPhone offer to scan a credit card on an e-commerce site, you're seeing Autofill in action.\nAutofill has been part of the WHATWG HTML Standard for some years now. This 2016 write-up by Jason Grigsby gives a pretty good sense of what can be done with it.\nThe spec describes ways that an HTML <input> element can use the \"autocomplete\" attribute to hint to the browser that it should offer to fill it with specific Autofill data, if the browser has it and if Autofill is enabled. There's a long list of values related to names, addresses, phone numbers, dates, and more. Additionally, since users might have more than one of a thing, these can be scoped with values like \"home\", \"work\", etc. It's possible to further group addresses by \"shipping\" and \"billing\", and even to group larger chunks of forms by named sections.\n\n  An example might look like:\n\n\n<input name=\"home-street-address\" autocomplete=\"shipping home street-address\">\n\n\nAn IndieWeb use-case for Autofill\nWeb sign-in is a very IndieWeb concept where you sign into websites using your personal web address, rather than an email address or username.\nThe sign-in form for webmention.io asks you to sign in using a URL.\n  As with any repetitive tasks, typing my site\u2019s URL into these login forms gets annoying. My main browser (Firefox) is pretty smart. Autocomplete kicks in after I type a few characters from my URL and it will offer to fill in URLs that I\u2019ve typed before. However, since most URLs start with \u201chttps://\u201c, autocomplete suggestions aren\u2019t very useful until I\u2019ve typed out 9 or more characters (or if I start typing from somewhere in the middle).\n\n\n  Helpfully, \u201curl\u201d is one of the many attributes in the WHATWG Autofill spec! It\u2019s described like so:\n\n\n  Home page or other Web page corresponding to the company, person, address, or contact information in the other fields associated with this field\n\nIn theory, it should be possible for sites with Web Sign-in to improve this process with the help of the browser and Autofill. For example:\n\n<input name=\"url\" type=\"url\" autocomplete=\"url\">\n\n\nOr more specifically, use your \"home\" (personal) URL:\n\n<input name=\"url\" type=\"url\" autocomplete=\"home url\">\n\n\n\n  It's my thinking that, with this in place, a browser should automatically suggest my URL without me typing anything at all!\n\n\n  A URL-shaped hole in Autofill\n\nI tried this out by setting up url autocomplete suggestions on two different apps with Web Sign-in. (Specifically, my personal instance of Aperture, and the IndieWeb webring).\nI then tried signing in and out several times to both sites, using the same URL each time. Browsers tested include Firefox, Chromium, and iOS Safari, all with Autofill enabled.\n\n  I am sad to report that none of the tested browsers attempted to automatically fill in the URL value. The extra autocomplete attribute didn't break the default autocompletion, but I still see it suggest every URL it knows about rather than learning one.\n\nI have had trouble finding documentation on how specific browsers implement Autofill. One note in Jason's 2016 article suggests that browsers may need multiple \"hints\" before it will decide that a particular input is part of a group which should be auto-filled.\nAnother hint comes from Chromium's settings for managing Autofill data. This is what the form looks like for adding a new address:\nChromium address dialog with fields for name, street address, and more. There is no field for URL.\n  Notice a field that isn't there?",
        "html": "<p>If you've ever seen your browser automatically fill in your shipping address, or seen your iPhone offer to scan a credit card on an e-commerce site, you're seeing Autofill in action.</p>\n<p><a href=\"https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#autofill\">Autofill has been part of the WHATWG HTML Standard</a> for some years now. <a href=\"https://cloudfour.com/thinks/autofill-what-web-devs-should-know-but-dont/\">This 2016 write-up by Jason Grigsby</a> gives a pretty good sense of what can be done with it.</p>\n<p>The spec describes ways that an HTML &lt;input&gt; element can use the \"autocomplete\" attribute to hint to the browser that it should offer to fill it with specific Autofill data, if the browser has it and if Autofill is enabled. There's a <a href=\"https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#attr-fe-autocomplete-name\">long list of values related to names, addresses, phone numbers, dates, and more</a>. Additionally, since users might have more than one of a thing, these can be <a href=\"https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#attr-fe-autocomplete-home\">scoped with values like \"home\", \"work\", etc</a>. It's possible to further group addresses by \"shipping\" and \"billing\", and even to group larger chunks of forms by named sections.</p>\n<p>\n  An example might look like:\n</p>\n\n<pre><code>&lt;input name=\"home-street-address\" autocomplete=\"shipping home street-address\"&gt;\n</code></pre>\n\n<p></p><h2>An IndieWeb use-case for Autofill</h2>\n<p><a href=\"https://indieweb.org/Web_sign-in\">Web sign-in</a> is a very <a href=\"https://indieweb.org/\">IndieWeb</a> concept where you sign into websites using your personal web address, rather than an email address or username.</p>\n<img src=\"https://media.martymcgui.re/ad/9e/2e/de/d420bc668f1b6467b0df88d59e438c294e35dd822a287c18b8b25de9.png\" alt=\"\" />The sign-in form for webmention.io asks you to sign in using a URL.<p>\n  As with any repetitive tasks, typing my site\u2019s URL into these login forms gets <i>annoying</i>. My main browser (Firefox) is pretty smart. Autocomplete kicks in after I type a few characters from my URL and it will offer to fill in URLs that I\u2019ve typed before. However, since most URLs start with \u201chttps://\u201c, autocomplete suggestions aren\u2019t very useful until I\u2019ve typed out 9 or more characters (or if I start typing from somewhere in the middle).\n</p>\n<p>\n  Helpfully, <a href=\"https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#attr-fe-autocomplete-url\">\u201curl\u201d is one of the many attributes in the WHATWG Autofill spec</a>! It\u2019s described like so:\n</p>\n<blockquote>\n  Home page or other Web page corresponding to the company, person, address, or contact information in the other fields associated with this field\n</blockquote>\n<p>In theory, it should be possible for sites with Web Sign-in to improve this process with the help of the browser and Autofill. For example:</p>\n\n<pre><code>&lt;input name=\"url\" type=\"url\" autocomplete=\"url\"&gt;\n</code></pre>\n\n<p>Or more specifically, use your \"home\" (personal) URL:</p>\n\n<pre><code>&lt;input name=\"url\" type=\"url\" autocomplete=\"home url\"&gt;\n</code></pre>\n\n<p>\n  It's my thinking that, with this in place, a browser <i>should</i> automatically suggest my URL without me typing anything at all!\n</p>\n<h2>\n  A URL-shaped hole in Autofill\n</h2>\n<p>I tried this out by setting up url autocomplete suggestions on two different apps with Web Sign-in. (Specifically, my personal instance of <a href=\"https://indieweb.org/Aperture\">Aperture</a>, and the <a href=\"https://xn--sr8hvo.ws/\">IndieWeb webring</a>).</p>\n<p>I then tried signing in and out several times to both sites, using the same URL each time. Browsers tested include Firefox, Chromium, and iOS Safari, all with Autofill enabled.</p>\n<p>\n  I am sad to report that <em>none of the tested browsers attempted to automatically fill in the URL value</em>. The extra autocomplete attribute didn't <em>break</em> the default autocompletion, but I still see it suggest every URL it knows about rather than learning one.\n</p>\n<p>I have had trouble finding documentation on how specific browsers implement Autofill. One note in <a href=\"https://cloudfour.com/thinks/autofill-what-web-devs-should-know-but-dont/\">Jason's 2016 article</a> suggests that browsers may need multiple \"hints\" before it will decide that a particular input is part of a group which should be auto-filled.</p>\n<p>Another hint comes from Chromium's settings for managing Autofill data. This is what the form looks like for adding a new address:</p>\n<img src=\"https://media.martymcgui.re/bb/14/1e/63/3fed51cf5416979e149256b8dce4e709807a1c1bcb5f547d74d9c313.png\" alt=\"\" />Chromium address dialog with fields for name, street address, and more. There is no field for URL.<p>\n  Notice a field that <i>isn't</i> there?\n</p>"
    },
    "author": {
        "type": "card",
        "name": "Marty McGuire",
        "url": "https://martymcgui.re/",
        "photo": "https://martymcgui.re/images/logo.jpg"
    },
    "post-type": "article",
    "_id": "11867935",
    "_source": "175",
    "_is_read": true
}

News Outlets vs. Authors and Blogs

{
    "type": "entry",
    "published": "2020-05-25T05:00:55+00:00",
    "url": "https://fireburn.ru/posts/1590382855",
    "category": [
        "https://news.indieweb.org"
    ],
    "syndication": [
        "https://twitter.com/kisik21/status/1264783504115666944"
    ],
    "name": "News Outlets vs. Authors and Blogs",
    "content": {
        "text": "When scrolling through news on Google Now feed (or is it called Discover now?) I started to realize the fact that most news outlets are utterly useless.\nIn age of information all that a company has to do to announce something is publish an article on their own website. If someone made something, they post in a blog.\nThe news outlets (tech news are especially guilty of it) just wrap the real news in what we Russians call water - often losing a lot of original meaning behind the post by confusing terminology and trying to explain something to a person who doesn\u2019t understand tech. And while the last objective seems great, the news don\u2019t do a great job at that.\nNowadays all I see in news are crude retellings of press releases and clickbait titles. Newspapers have become a bubble, an enterprise existing only to show ads to users. When I scroll through news, I see adverts each three paragraphs, taking more space on my screen than the content I came for. (That\u2019s why I use adblockers) Is this the media we wanted? No. Definitely not.\nWe want free media. Freedom of expression, non-intrusive ads (if ads at all, but come on, I ain\u2019t got money for subscribing to a thousand different newspapers) and original content. Maybe the concept of IndieWeb could provide all of that? I think so!\nAnd if you still want to provide a useful outlet for the content on a single topic, make a syndication hub that will pull blog posts from authors\u2019 websites if they want to be featured. In fact, we already have one - IndieNews - a news feed for everything IndieWeb-related. Just post a webmention if you wanna get featured!",
        "html": "<p>When scrolling through news on Google Now feed (or is it called Discover now?) I started to realize the fact that most news outlets are utterly useless.</p>\n<p>In age of information all that a company has to do to announce something is publish an article on their own website. If someone made something, they post in a blog.</p>\n<p>The news outlets (tech news are especially guilty of it) just wrap the real news in what we Russians call water - often losing a lot of original meaning behind the post by confusing terminology and trying to explain something to a person who doesn\u2019t understand tech. And while the last objective seems great, the news don\u2019t do a great job at that.</p>\n<p>Nowadays all I see in news are crude retellings of press releases and clickbait titles. Newspapers have become a bubble, an enterprise existing only to show ads to users. When I scroll through news, I see adverts each three paragraphs, taking more space on my screen than the content I came for. (That\u2019s why I use adblockers) Is this the media we wanted? No. Definitely not.</p>\n<p>We want free media. Freedom of expression, non-intrusive ads (if ads at all, but come on, I ain\u2019t got money for subscribing to a thousand different newspapers) and <strong>original content</strong>. Maybe the concept of <a href=\"https://IndieWeb.org\">IndieWeb</a> could provide all of that? I think so!</p>\n<p>And if you still want to provide a useful outlet for the content on a single topic, make a syndication hub that will pull blog posts from authors\u2019 websites if they want to be featured. In fact, we already have one - <a href=\"https://news.indieweb.org\" class=\"u-category\">IndieNews</a> - a news feed for everything IndieWeb-related. Just post a webmention if you wanna get featured!</p>"
    },
    "author": {
        "type": "card",
        "name": "Vika",
        "url": "https://fireburn.ru/",
        "photo": "https://fireburn.ru/media/f1/5a/fb/9b/081efafb97b4ad59f5025cf2fd0678b8f3e20e4c292489107d52be09.png"
    },
    "post-type": "article",
    "_id": "11853905",
    "_source": "1371",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-05-24T14:04:10.97849-07:00",
    "url": "https://v2.jacky.wtf/post/c798efe2-fc6a-4f98-8500-9d44c877d975",
    "in-reply-to": [
        "https://github.com/ckruse/microformats2-elixir/pull/12#issuecomment-633208284"
    ],
    "content": {
        "text": "No problem! I was curious about that too (I actually use that pattern in my indieweb Elixir library - I should move away from it).",
        "html": "<p>No problem! I was curious about that too (I actually use that pattern in my <code>indieweb</code> Elixir library - I should move away from it).</p>"
    },
    "author": {
        "type": "card",
        "name": "",
        "url": "https://v2.jacky.wtf",
        "photo": null
    },
    "post-type": "reply",
    "refs": {
        "https://github.com/ckruse/microformats2-elixir/pull/12#issuecomment-633208284": {
            "type": "entry",
            "url": "https://github.com/ckruse/microformats2-elixir/pull/12#issuecomment-633208284",
            "content": {
                "text": "Make use of normalized key to atomize keys. by jalcine \u00b7 Pull Request #12 \u00b7 ckruse/microformats2-..."
            },
            "author": {
                "type": "card",
                "name": "",
                "url": "https://v2.jacky.wtf/stream",
                "photo": null
            },
            "post-type": "note"
        }
    },
    "_id": "11845412",
    "_source": "1886",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-05-24T10:03:00+01:00",
    "url": "https://www.jvt.me/mf2/2020/05/kwhlm/",
    "category": [
        "indieweb"
    ],
    "bookmark-of": [
        "https://v2.jacky.wtf/post/494c3034-7ad0-4081-b4d2-825d4825d2ff"
    ],
    "author": {
        "type": "card",
        "name": "Jamie Tanna",
        "url": "https://www.jvt.me",
        "photo": "https://www.jvt.me/img/profile.png"
    },
    "post-type": "bookmark",
    "_id": "11834697",
    "_source": "2169",
    "_is_read": true
}