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><html lang=\"en\" prefix=\"og: http://ogp.me/ns# article: http://ogp.me/ns/article#\">\n<head>\n <title>A piece of Powerscourt Waterfall - petermolnar.net</title>\n<!-- JSON-LD as alternative -->\n <link rel=\"alternate\" type=\"application/json\" title=\"a-piece-of-powerscourt-waterfall JSON-LD\" href=\"https://petermolnar.net/a-piece-of-powerscourt-waterfall/index.json\" />\n<!-- Open Graph vocabulary RDFa -->\n <meta property=\"og:title\" content=\"A piece of Powerscourt Waterfall\" />\n <meta property=\"og:type\" content=\"article\" />\n <meta property=\"og:url\" content=\"https://petermolnar.net/a-piece-of-powerscourt-waterfall/\" />\n <meta property=\"og:description\" content=\"\" />\n <meta property=\"article:published_time\" content=\"2017-11-09T18:00:00+00:00\" />\n <meta property=\"article:modified_time\" content=\"2019-01-05T11:52:47.543053+00:00\" />\n <meta property=\"article:author\" content=\"Peter Molnar (mail@petermolnar.net)\" />\n <meta property=\"og:image\" content=\"https://petermolnar.net/a-piece-of-powerscourt-waterfall/a-piece-of-powerscourt-waterfall_b.jpg\" />\n <meta property=\"og:image:type\" content=\"image/jpeg\" />\n <meta property=\"og:image:width\" content=\"1280\" />\n <meta property=\"og:image:height\" content=\"847\" />\n<!-- the rest of meta and header elements -->\n<!-- followed by the content, with microformats v1 and v2 markup --></code></pre>\n<p>HTML provides an interesting functionality, the <code>rel=alternate</code>. This is meant to be the representation of the same data, but in another format. The most common use is links to RSS and Atom feeds.</p>\n<p>I don'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
}
Ten years ago today I started working with Mozilla on #webStandards.
https://tantek.com/2010/146/t1/work-with-mozilla-advancing-web-standards
https://twitter.com/t/status/14764431903
Still @Mozilla (now @W3C AC Rep), still working for a more #OpenWeb, and for an #IndieWeb that puts users in control instead of #BigTech.
https://tantek.com/2010/146/t1/work-with-mozilla-advancing-web-standards
https://twitter.com/t/status/14764431903
Still @Mozilla (now @W3C AC Rep), still working for a more #OpenWeb, and for an #IndieWeb that puts users in control instead of #BigTech.
{
"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
}
I need to fix my Webmentions. And once I do, I’ll 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.
{
"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
}
Reminder that tomorrow is #HomebrewWebsiteClub Nottingham tomorrow - hope to see you there! https://events.indieweb.org/2020/05/online-homebrew-website-club-nottingham-Rqs1Cfcxii4D
{
"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
}
Ah okay! This is something I was wondering for Lwa - having it look for a WebSub endpoint when it’s provided a feed and have it subscribe for changes so it can be more “push/pull”-y when it comes to this. That should give the feel of a whole complete “transaction” (though clients will need some way to be updated when a Microsub server is updated).
{
"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
}
I can’t tell if it’s aperture (I doubt it) but my feeds don’t seem to update quickly. This is me also assuming that aperture somehow knows about websub and uses that to update feeds. I’m guessing that’s not the case @aaronpk? How would a real time feed work with it?
{
"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 <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 <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><input name=\"home-street-address\" autocomplete=\"shipping home street-address\">\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><input name=\"url\" type=\"url\" autocomplete=\"url\">\n</code></pre>\n\n<p>Or more specifically, use your \"home\" (personal) URL:</p>\n\n<pre><code><input name=\"url\" type=\"url\" autocomplete=\"home url\">\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
}
No problem! I was curious about that too (I actually use that pattern in my indieweb Elixir library - I should move away from it).
{
"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
}
Liked On Owning Data Apps Use and the IndieWeb by Jacky Alciné
So I came across this post about owning data from apps we use a lot. As I'm reading it, my head's bopping up and down with agreement - I strongly believe that data sovereignty is a important human right; especially with large companies actively using it to dismantle facets of society. In the post, t...
{
"type": "entry",
"author": {
"name": "Neil Mather",
"url": "https://doubleloop.net/",
"photo": null
},
"url": "https://doubleloop.net/2020/05/24/6997/",
"published": "2020-05-24T07:36:00+00:00",
"content": {
"html": "Liked <a href=\"https://v2.jacky.wtf/post/494c3034-7ad0-4081-b4d2-825d4825d2ff\">On Owning Data Apps Use and the IndieWeb</a> by Jacky Alcin\u00e9\n<blockquote>So I came across this post about owning data from apps we use a lot. As I'm reading it, my head's bopping up and down with agreement - I strongly believe that data sovereignty is a important human right; especially with large companies actively using it to dismantle facets of society. In the post, t...</blockquote>",
"text": "Liked On Owning Data Apps Use and the IndieWeb by Jacky Alcin\u00e9\nSo I came across this post about owning data from apps we use a lot. As I'm reading it, my head's bopping up and down with agreement - I strongly believe that data sovereignty is a important human right; especially with large companies actively using it to dismantle facets of society. In the post, t..."
},
"post-type": "note",
"_id": "11832112",
"_source": "1895",
"_is_read": true
}
On Owning Data Apps Use and the IndieWeb
{
"type": "entry",
"published": "2020-05-24T00:17:10.86664-07:00",
"url": "https://v2.jacky.wtf/post/494c3034-7ad0-4081-b4d2-825d4825d2ff",
"category": [
"indieweb",
"thoughts"
],
"name": "On Owning Data Apps Use and the IndieWeb",
"content": {
"text": "So I came across this post about owning data from apps we use a lot. As I'm reading it, my head's bopping up and down with agreement - I strongly believe that data sovereignty is a important human right; especially with large companies actively using it to dismantle facets of society. In the post, there's a lot of things that companies like Google and Apple are inching towards implementing in their data warehouses to learn even more about you - something I am not an advocate of as someone who interfaces with activists who have to defend themselves against state actors and people who work at companies that are doing this vacuuming. However, the approach that the poster takes requires a bit of programming that might be not friendly for most people.Now, I don't mind writing code to get off the ground but I don't want to keep writing code to do things. I'd like to have some sort of plug-and-play approach to this and that's where I think the IndieWeb comes into play. Though still optimizing for personal use, the IndieWeb has a lot of people working on ways to track things around what they read, where they go and what they interact with on the Web. I know that I'd love to capture more information so I don't have to rely on companies to keep them up or eventually sell them to Google or Apple (FitBit and Dark Sky). This isn't easy though because of these platforms restricting the level of control people have over the devices in the name of \"security\".The original poster mentioned something that I actually use to this day to handle a lot of this stuff: OAuth (namely OAuth2). In the IndieWeb, we lean on an extension (with loosely scoping) of OAuth called IndieAuth. It gives you all of the security and reliability of OAuth2 while reversing the authority to your own choosing. We also use things like Micropub and Microsub to handle how we do storing of content (namely contacts, tags and posts) and what we subscribe to as well as what we follow. I use both of those daily to handle how I interact with the Web. The thing is, at least from the poster's perspective, most of this stuff requires way too much wiring and coding for people to even use. And I agree. There's no pressing interest in the community to get people who don't have a high comfort in writing code since this is not only a community-led effort but one without any big funding behind it. I think that initially can be a good thing because it prevents too much pollution by direction of funds but that's a different conversation.That post definitely felt like a form of validation that there's interest in this and that the stuff I'm working on can nudge people towards it. I want this to be as \"easy\" as it was to hop on sites like Tumblr or AIM and communicate with people you know or find new ones. Obviously, that ease of use came with years of work and research but most of that has been done and the hardest part now is the design and implementation - working on user-centric, people-first systems tends to remove the whole \"scale scale scale\" problem. I'm starting this with a \"plumbing level\" service and I'll work my way up to meet people with Lighthouse. What do you want to see?",
"html": "<p>So I came across this post about <a href=\"https://orndorffgrant.com/own-your-data-idea/\">owning data from apps we use a lot</a>. As I'm reading it, my head's bopping up and down with agreement - I strongly believe that data sovereignty is a important human right; especially with large companies actively using it to dismantle facets of society. In the post, there's a lot of things that companies like Google and Apple are inching towards implementing in their data warehouses to learn even more about you - something I am <strong>not</strong> an advocate of as someone who interfaces with activists who have to defend themselves against state actors <i>and</i> people who work at companies that are doing this vacuuming. However, the approach that the poster takes requires a bit of programming that might be not friendly for most people.</p><p>Now, I don't mind writing code to get off the ground but I don't want to keep writing code to do things. I'd like to have some sort of plug-and-play approach to this and that's where I think the IndieWeb comes into play. Though still optimizing for personal use, the IndieWeb has a lot of people working on ways to track things around what they read, where they go and what they interact with on the Web. I know that I'd love to capture more information so I don't have to rely on companies to keep them up or eventually sell them to Google or Apple (FitBit and Dark Sky). This isn't easy though because of these platforms restricting the level of control people have over the devices in the name of \"security\".</p><p>The original poster mentioned something that I actually use to this day to handle a lot of this stuff: OAuth (namely OAuth2). In the IndieWeb, we lean on an extension (with loosely scoping) of OAuth called <a href=\"https://indieauth.com/\">IndieAuth</a>. It gives you all of the security and reliability of OAuth2 while reversing the authority to your own choosing. We also use things like <a href=\"https://v2.jacky.wtf/micropub.net/\">Micropub</a> and <a href=\"https://indieweb.org/Microsub\">Microsub</a> to handle how we do storing of content (namely contacts, tags and posts) and what we subscribe to as well as what we follow. I use both of those daily to handle how I interact with the Web. The thing is, at least from the poster's perspective, most of this stuff requires <i>way too much</i> wiring and coding for people to even use. And I agree. There's no pressing interest in the community to get people who don't have a high comfort in writing code since this is not only a community-led effort but one without any big funding behind it. I think that initially can be a good thing because it prevents too much pollution by direction of funds but that's a different conversation.</p><p>That post definitely felt like a form of validation that there's interest in this and that the stuff I'm working on can nudge people towards it. I want this to be as \"easy\" as it was to hop on sites like Tumblr or AIM and communicate with people you know or find new ones. Obviously, that ease of use came with years of work and research but most of that has been done and the hardest part now is the design and implementation - working on user-centric, people-first systems tends to remove the whole \"scale scale scale\" problem. I'm starting this with a \"plumbing level\" service and I'll work my way up to meet people with <a href=\"https://lighthouse.black.af/\">Lighthouse</a>. What do you want to see?</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "article",
"_id": "11831242",
"_source": "1886",
"_is_read": true
}
Thinking more about this, the biggest problem with “/“ is querying for pages. As was mentioned in chat, you could have
q=sourceaccept an option to only match posts with a certain slug prefix, but it would often be faked because the “/“ is not necessarily included in the actual slug as stored in a database. So you’d have a backend system with logic like “if the parameter starts with a slash, do something completely different”.I’m fine with it if that’s the consensus. But it seems more like an implementation detail than a full feature of Micropub.
Yeah, this seems like it’d end up being an implementation detail. I’m deeply in favor though of the h=type approach because it’ll be also easier to do a full list dump against post types (and page types). I know for certain that I’ll be implementing that into my site and my client.
{
"type": "entry",
"published": "2020-05-23T18:37:29.89776-07:00",
"url": "https://v2.jacky.wtf/post/d0bd7253-f656-4bf3-9a89-47d99f7c0a30",
"in-reply-to": [
"https://github.com/indieweb/micropub-extensions/issues/25"
],
"content": {
"text": "Thinking more about this, the biggest problem with \u201c/\u201c is querying for pages. As was mentioned in chat, you could have q=source accept an option to only match posts with a certain slug prefix, but it would often be faked because the \u201c/\u201c is not necessarily included in the actual slug as stored in a database. So you\u2019d have a backend system with logic like \u201cif the parameter starts with a slash, do something completely different\u201d.\nI\u2019m fine with it if that\u2019s the consensus. But it seems more like an implementation detail than a full feature of Micropub.\nYeah, this seems like it\u2019d end up being an implementation detail. I\u2019m deeply in favor though of the h=type approach because it\u2019ll be also easier to do a full list dump against post types (and page types). I know for certain that I\u2019ll be implementing that into my site and my client.",
"html": "<blockquote>\n<p>Thinking more about this, the biggest problem with \u201c/\u201c is querying for pages. As was mentioned in chat, you could have <code>q=source</code> accept an option to only match posts with a certain slug prefix, but it would often be faked because the \u201c/\u201c is not necessarily included in the actual slug as stored in a database. So you\u2019d have a backend system with logic like \u201cif the parameter starts with a slash, do something completely different\u201d.</p>\n<p>I\u2019m fine with it if that\u2019s the consensus. But it seems more like an implementation detail than a full feature of Micropub.</p>\n</blockquote><p>Yeah, this seems like it\u2019d end up being an implementation detail. I\u2019m deeply in favor though of the <code>h=type</code> approach because it\u2019ll be also easier to do a full list dump against post types (and page types). I know for certain that I\u2019ll be implementing that into my site and my client.</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "reply",
"refs": {
"https://github.com/indieweb/micropub-extensions/issues/25": {
"type": "entry",
"url": "https://github.com/indieweb/micropub-extensions/issues/25",
"content": {
"text": "It is common on blogs to have both timestamped blog posts (articles, notes, and photos) as well as standalone pages that are included in the navigation. These pages are not tied to a specific date and are usually stored separately from blog posts. For example, \"About\", \"Contact Me\", or \"Resume\" pages.\nWordPress and Micro.blog both have this concept. Timestamped blog posts are called \"Posts\", and standalone pages are called \"Pages\".\nI'd like to be able to query for these pages from Micropub, create new ones, edit, and delete them.\nMicropub proposals #1 and #4 have a \"post type\" based on Post Type Discovery. There is no \"page\" post type that I'm aware of (and there would be no way to discovery the type based on its content).\nPossible solutions:\nFormalize a \"page\" post type. There would need to be a new parameter for passing this when creating a post. Everything else in Micropub remains basically the same.\nSplit off \"pages\" into their own set of API calls, such as q=pages for querying a list of pages.\nPrior art: WordPress has long supported pages in their XML-RPC API. I've also recently added support in Micro.blog's flavor of XML-RPC, which I've documented here. WordPress has further consolidated to use a post_type of \"page\" instead of separate API calls for pages.",
"html": "<p>It is common on blogs to have both timestamped blog posts (articles, notes, and photos) as well as standalone pages that are included in the navigation. These pages are not tied to a specific date and are usually stored separately from blog posts. For example, \"About\", \"Contact Me\", or \"Resume\" pages.</p>\n<p>WordPress and Micro.blog both have this concept. Timestamped blog posts are called \"Posts\", and standalone pages are called \"Pages\".</p>\n<p>I'd like to be able to query for these pages from Micropub, create new ones, edit, and delete them.</p>\n<p>Micropub proposals #1 and #4 have a \"post type\" based on Post Type Discovery. There is no \"page\" post type that I'm aware of (and there would be no way to discovery the type based on its content).</p>\n<p>Possible solutions:</p>\n<ul><li>Formalize a \"page\" post type. There would need to be a new parameter for passing this when creating a post. Everything else in Micropub remains basically the same.</li>\n<li>Split off \"pages\" into their own set of API calls, such as <code>q=pages</code> for querying a list of pages.</li>\n</ul><p>Prior art: WordPress has long supported pages in their XML-RPC API. I've also recently added support in Micro.blog's flavor of XML-RPC, which <a href=\"https://help.micro.blog/2020/xmlrpc-microblog/\">I've documented here</a>. WordPress has further consolidated to use a <code>post_type</code> of \"page\" instead of separate API calls for pages.</p>"
},
"author": {
"type": "card",
"name": "manton",
"url": "https://github.com/manton",
"photo": null
},
"post-type": "note"
}
},
"_id": "11827073",
"_source": "1886",
"_is_read": true
}
Difference and connection
{
"type": "entry",
"author": {
"name": "Neil Mather",
"url": "https://doubleloop.net/",
"photo": null
},
"url": "https://doubleloop.net/2020/05/23/difference-and-connection/",
"published": "2020-05-23T19:41:11+00:00",
"content": {
"html": "Listened to <a href=\"http://philosophizethis.org/deleuze-difference/\">Episode 129 \u2013 Deleuze pt. 5 \u2013 Difference</a> from <em>Philosophize This!</em>\n<blockquote>On this episode, we continue our discussion of the work of Gilles Deleuze.</blockquote>\n\n\n\n<p><a href=\"http://philosophizethis.org/deleuze-difference/\">Part five of the Deleuze & Guatarri Philosophize This! podcast</a> is great.</p>\n<p>They talk about this idea of becoming rather than being. We are better in a constant process of becoming. And that the way to facilitate becoming is through availability of links and connections, access to connections through the <a href=\"https://commonplace.doubleloop.net/20200523201658-rhizome.html\">rhizome</a> to discover new things.</p>\n<p>They also make the link between the connected nature of the rhizome and the connected nature of the city. If you segregate parts of the city, say this is the business district, this is the residential district, this is the shopping district, entertainment district etc. Then, it doesn\u2019t work, the city doesn\u2019t function. As per <a href=\"https://commonplace.doubleloop.net/20200404143533-jane_jacobs.html\">Jane Jacobs</a>.</p>\n<p>Cities function better when everything\u2019s mixed together, when diverse connections are easily made. And I think this applies to the online city, the web. We have Facebook and Twitter, huge districts of planned homogeneity locking in and blocking off certain paths.</p>\n<p>Constructing environments that allows for those connections to be made dovetails so nicely into some of the stuff I\u2019m interested in with regards to connections on the web. It would be better to have smaller communities of intermingled activities. The <a href=\"https://commonplace.doubleloop.net/indieweb.html\">IndieWeb</a>, the <a href=\"https://commonplace.doubleloop.net/20200321115911-fediverse.html\">fediverse</a>, the <a href=\"https://commonplace.doubleloop.net/20200523203153-weird_web.html\">weird web</a>, allowing unfettered connections between diverse entities. Perhaps we could do better at joining them up, but at least they\u2019re there to be joined.</p>",
"text": "Listened to Episode 129 \u2013 Deleuze pt. 5 \u2013 Difference from Philosophize This!\nOn this episode, we continue our discussion of the work of Gilles Deleuze.\n\n\n\nPart five of the Deleuze & Guatarri Philosophize This! podcast is great.\nThey talk about this idea of becoming rather than being. We are better in a constant process of becoming. And that the way to facilitate becoming is through availability of links and connections, access to connections through the rhizome to discover new things.\nThey also make the link between the connected nature of the rhizome and the connected nature of the city. If you segregate parts of the city, say this is the business district, this is the residential district, this is the shopping district, entertainment district etc. Then, it doesn\u2019t work, the city doesn\u2019t function. As per Jane Jacobs.\nCities function better when everything\u2019s mixed together, when diverse connections are easily made. And I think this applies to the online city, the web. We have Facebook and Twitter, huge districts of planned homogeneity locking in and blocking off certain paths.\nConstructing environments that allows for those connections to be made dovetails so nicely into some of the stuff I\u2019m interested in with regards to connections on the web. It would be better to have smaller communities of intermingled activities. The IndieWeb, the fediverse, the weird web, allowing unfettered connections between diverse entities. Perhaps we could do better at joining them up, but at least they\u2019re there to be joined."
},
"name": "Difference and connection",
"post-type": "article",
"_id": "11824859",
"_source": "1895",
"_is_read": true
}
I definitely need notifications back as well as a more tighter mobile interface. I’ve been tempted to “do it myself” with the latter but it’s not my strong suit. It’s probably more of a speed and feedback kind of thing. Like posting takes a few hundred milliseconds to one second and happens synchronously whereas silos can do it “instantly”. I can’t even safely prevent reposting on my site (yet). I think that first, I’d want to normalize some sort of status polling for posts in micropub clients to allow for async posting and then add it to clients I use.
{
"type": "entry",
"published": "2020-05-23T10:55:00.00000-07:00",
"url": "https://v2.jacky.wtf/post/874186f2-7bc8-49af-9983-d9d027b09c31",
"category": [
"micropub",
"indieweb"
],
"content": {
"text": "I definitely need notifications back as well as a more tighter mobile interface. I\u2019ve been tempted to \u201cdo it myself\u201d with the latter but it\u2019s not my strong suit. It\u2019s probably more of a speed and feedback kind of thing. Like posting takes a few hundred milliseconds to one second and happens synchronously whereas silos can do it \u201cinstantly\u201d. I can\u2019t even safely prevent reposting on my site (yet). I think that first, I\u2019d want to normalize some sort of status polling for posts in micropub clients to allow for async posting and then add it to clients I use.",
"html": "<p>I definitely need notifications back as well as a more tighter mobile interface. I\u2019ve been tempted to \u201cdo it myself\u201d with the latter but it\u2019s not my strong suit. It\u2019s probably more of a speed and feedback kind of thing. Like posting takes a few hundred milliseconds to one second and happens synchronously whereas silos can do it \u201cinstantly\u201d. I can\u2019t even safely prevent reposting on my site (yet). I think that first, I\u2019d want to normalize some sort of status polling for posts in micropub clients to allow for async posting and then add it to clients I use.</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "note",
"_id": "11819003",
"_source": "1886",
"_is_read": true
}
Definitely have a ways to go before I’m satisfied with the stuff that we can do in the IndieWeb. It’ll be tied to how much interest the community has in pushing the envelope as well as building more canonical tools for representing the capacities of the standards set out while maintaining interoperability with vanilla approaches.
{
"type": "entry",
"published": "2020-05-23T10:47:00.00000-07:00",
"url": "https://v2.jacky.wtf/post/d6b2bc7b-8a3a-4787-81a7-291ace032a9f",
"content": {
"text": "Definitely have a ways to go before I\u2019m satisfied with the stuff that we can do in the IndieWeb. It\u2019ll be tied to how much interest the community has in pushing the envelope as well as building more canonical tools for representing the capacities of the standards set out while maintaining interoperability with vanilla approaches.",
"html": "<p>Definitely have a ways to go before I\u2019m satisfied with the stuff that we can do in the IndieWeb. It\u2019ll be tied to how much interest the community has in pushing the envelope as well as building more canonical tools for representing the capacities of the standards set out while maintaining interoperability with vanilla approaches.</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "note",
"_id": "11818819",
"_source": "1886",
"_is_read": true
}
Now all I need to do is fix my Webmentions feed and I can do some work on theming.
{
"type": "entry",
"published": "2020-05-23T10:03:00.00000-07:00",
"url": "https://v2.jacky.wtf/post/85386fe0-d658-4c7b-a726-48c0d48c074c",
"content": {
"text": "Now all I need to do is fix my Webmentions feed and I can do some work on theming.",
"html": "<p>Now all I need to do is fix my Webmentions feed and I can do some work on theming.</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "note",
"_id": "11818012",
"_source": "1886",
"_is_read": true
}
Plaidophile: Stuff and things
{
"type": "entry",
"author": {
"name": "fluffy",
"url": "http://beesbuzz.biz/",
"photo": null
},
"url": "http://beesbuzz.biz/blog/6927-Stuff-and-things",
"published": "2020-05-20T15:27:05-07:00",
"content": {
"html": "<p>So, some updates of the things that have been going on in my life since the last update, because I\u2019m waiting for my car to get some overdue scheduled maintenance and I forgot to bring my Switch, so why not.</p>\n\n\n<p>I\u2019ve been on the blood thinners for\u2026 a week, now? I think? I still get occasional headaches and dizziness from them but it\u2019s starting to sort itself out. One of the interesting things I\u2019ve noticed is that ever since starting on them, I\u2019ve been having less constipation, like it\u2019s undoing that effect of the gabapentin. I wonder if there\u2019s something going on like increased circulation means better water delivery to the bowel or something. I dunno. Anyway the clot has definitely subsided and that\u2019s the main point to this.</p><p>Work\u2019s gotten a bit better. I decided to be the change I want to see in the world and started a serious effort to document stuff to make it less tricky. Other folks seem to be really appreciative of it, and maybe I can even get others to help out on this. Who knows! Anyway that\u2019s reduced my stress a lot. Also I figured out how to automate an onboarding step that was previously manual, but of course also documented what to do if it fails. The tool I found for doing this particular thing can also help to clean up a bunch of other processes.<a href=\"http://beesbuzz.biz/blog/6927-Stuff-and-things#d_e6927_fn1\">1</a></p><p>I haven\u2019t really been working on music for a while, but I\u2019ve finally done a pretty big thing on Publ: the ability to attach entries to other entries! In particular this makes it so I can finally import all my old <a href=\"http://ohnorobot.com/\">Oh No Robot</a> transcripts over, which I have done. At some point I\u2019ll also write a little crowdsourcing thing to make it so that people can help with transcribing <a href=\"http://beesbuzz.biz/comics/transcript-needed\">all the ones without transcripts</a>, and in the meantime I\u2019ve also made my comic publishing script prompt me to add a transcript myself when I add a new one.</p><p>If I do a crowdsourcing module I\u2019ll absolutely opensource it so that people can use it on their own Publ-based comic sites. (It will absolutely be Publ-specific, though.)</p><p>\u2026 Oh <em>heck</em>, I just realized this could also be used to implement a comment system. <em>And</em> server-side webmentions, and so many other things. Huh. I\u2019m gonna have to think about this. My original plan for server-side webmentions was to roll that into whatever I write for ActivityPub since I was going to build it as a more generic publish-subscribe hub (so I can also get myself off of <a href=\"https://webmention.io/\">webmention.io</a> and <a href=\"https://superfeedr.com/\">Superfeedr</a> and <a href=\"https://fed.brid.gy/\">Bridgy Fed</a>) and\u2026 well okay I don\u2019t think making comments/mentions/etc. into separate entries for each thing is necessarily the right way to go but it\u2019s still something to consider, and might be nice for someone who\u2019s building a site from the ground up.</p><p>Plus, there\u2019s always something nice about removing a database dependency and making the data more replicated, and pushing it closer to the edges. And there\u2019s no reason it has to be an entry per response, when they could be rolled up into a single responses entry or something.</p><p>But I\u2019m also not in a huge hurry to, say, rewrite <a href=\"https://posative.org/isso\">isso</a>, either. I\u2019d really rather just follow through on my plan to adding a better moderation system (or better yet a moderation <em>plugin</em> system, so it can use bogofilter or akismet or whatever) to it.</p><p>Hmm, what else. I guess I\u2019ve been having a lot more anxiety lately. I ended up taking a stress reduction and mindfulness seminar that was offered by <a href=\"https://onemedical.com/\">One Medical</a> and it was nice to get a refresher on stuff and learning a few more grounding techniques. I\u2019m also finding that the <a href=\"http://beesbuzz.biz/blog/7203-New-keyboard-tray\">new keyboard tray</a> has been helping my pain a lot. It\u2019s not a panacea, of course, but every little thing helps.</p><p>Anyway, I guess that\u2019s enough rambling for now. I still have half an hour left until my car is ready, so, time to figure out something else I can do from my iPad.</p>\n\n<ol><li><p>(Infrastructure lead trying to poach me onto his team intensifies) <a href=\"http://beesbuzz.biz/blog/6927-Stuff-and-things#r_e6927_fn1\">\u21a9</a></p></li></ol><p><a href=\"http://beesbuzz.biz/blog/6927-Stuff-and-things#comments\">comments</a></p>",
"text": "So, some updates of the things that have been going on in my life since the last update, because I\u2019m waiting for my car to get some overdue scheduled maintenance and I forgot to bring my Switch, so why not.\n\n\nI\u2019ve been on the blood thinners for\u2026 a week, now? I think? I still get occasional headaches and dizziness from them but it\u2019s starting to sort itself out. One of the interesting things I\u2019ve noticed is that ever since starting on them, I\u2019ve been having less constipation, like it\u2019s undoing that effect of the gabapentin. I wonder if there\u2019s something going on like increased circulation means better water delivery to the bowel or something. I dunno. Anyway the clot has definitely subsided and that\u2019s the main point to this.Work\u2019s gotten a bit better. I decided to be the change I want to see in the world and started a serious effort to document stuff to make it less tricky. Other folks seem to be really appreciative of it, and maybe I can even get others to help out on this. Who knows! Anyway that\u2019s reduced my stress a lot. Also I figured out how to automate an onboarding step that was previously manual, but of course also documented what to do if it fails. The tool I found for doing this particular thing can also help to clean up a bunch of other processes.1I haven\u2019t really been working on music for a while, but I\u2019ve finally done a pretty big thing on Publ: the ability to attach entries to other entries! In particular this makes it so I can finally import all my old Oh No Robot transcripts over, which I have done. At some point I\u2019ll also write a little crowdsourcing thing to make it so that people can help with transcribing all the ones without transcripts, and in the meantime I\u2019ve also made my comic publishing script prompt me to add a transcript myself when I add a new one.If I do a crowdsourcing module I\u2019ll absolutely opensource it so that people can use it on their own Publ-based comic sites. (It will absolutely be Publ-specific, though.)\u2026 Oh heck, I just realized this could also be used to implement a comment system. And server-side webmentions, and so many other things. Huh. I\u2019m gonna have to think about this. My original plan for server-side webmentions was to roll that into whatever I write for ActivityPub since I was going to build it as a more generic publish-subscribe hub (so I can also get myself off of webmention.io and Superfeedr and Bridgy Fed) and\u2026 well okay I don\u2019t think making comments/mentions/etc. into separate entries for each thing is necessarily the right way to go but it\u2019s still something to consider, and might be nice for someone who\u2019s building a site from the ground up.Plus, there\u2019s always something nice about removing a database dependency and making the data more replicated, and pushing it closer to the edges. And there\u2019s no reason it has to be an entry per response, when they could be rolled up into a single responses entry or something.But I\u2019m also not in a huge hurry to, say, rewrite isso, either. I\u2019d really rather just follow through on my plan to adding a better moderation system (or better yet a moderation plugin system, so it can use bogofilter or akismet or whatever) to it.Hmm, what else. I guess I\u2019ve been having a lot more anxiety lately. I ended up taking a stress reduction and mindfulness seminar that was offered by One Medical and it was nice to get a refresher on stuff and learning a few more grounding techniques. I\u2019m also finding that the new keyboard tray has been helping my pain a lot. It\u2019s not a panacea, of course, but every little thing helps.Anyway, I guess that\u2019s enough rambling for now. I still have half an hour left until my car is ready, so, time to figure out something else I can do from my iPad.\n\n(Infrastructure lead trying to poach me onto his team intensifies) \u21a9comments"
},
"name": "Plaidophile: Stuff and things",
"post-type": "article",
"_id": "11748780",
"_source": "3782",
"_is_read": true
}
IndieWeb NYC (aka Virtual HWC US East) Meetup 2020-05-20 Wrap-Up
{
"type": "entry",
"published": "2020-05-20T19:45:36-0400",
"url": "https://martymcgui.re/2020/05/20/indieweb-nyc-aka-virtual-hwc-us-east-meetup-2020-05-20-wrap-up/",
"category": [
"IndieWeb",
"meetup",
"HWC",
"NYC",
"virtual",
"vHWC",
"wrap-up"
],
"name": "IndieWeb NYC (aka Virtual HWC US East) Meetup 2020-05-20 Wrap-Up",
"content": {
"text": "IndieWeb NYC's meetup for May 2020 (also virtual Homebrew Website Club US East), met on Zoom from 6pm - 8pm EDT on May 20th.\nHere are some notes from the meeting!\n\n jmac.org \u2014 Moved to NYC and started attending local HWCs just before The Lockdown. Very interested in Webmention as a technology to connect websites to one another - but wants to improve the focus on how it can be used for real human interaction!\n \n\n\n martymcgui.re \u2014 Long-time IndieWeb and NYC organizer. Been working on lots of random projects. Currently thinking about turning his pile of \"read\" posts, largely dumped from GoodReads, into more usable pages about what he's reading now, reading next, and read recently.\n \n\ndavid.shanske.com \u2014 Long-time IndieWeb and NYC organizer. Been working on location features, aspirationally. Looking forward to a time when he can thrill audiences by reporting being in a location other than \"Home\".\nSandro \u2014 Has been building CMSes and more for years. Been working on some new stuff that works even offline!\nKevin \u2014 Worked w/ sandro at Limewire some years ago! Attended past HWC SF meetings in the Before Times. Has been calling into the West Coast virtual meetings, first time calling into East Coast. Wants his site (zootella.com) to publish to 3 places - webserver, local files, and Beaker Browser (just went 1.0!)\nMike \u2014 Did web development for years, then stopped, now back again! Learned about IndieWeb through Micro.blog community. Interested in making sure the software he develops is a \"good IndieWeb citizen\". Working on a kind of Meetup competitor.\njgregorymcverry.com \u2014 Long time IndieWeb and NYC organizer. Currently working on a website for a poetry radio show. Folks from all over the world can submit clips. It's wiki-based, but can also receive webmentions.\ngRegorLove.com \u2014 In San Diego, but joining East Coast to see some new faces. Been out of IndieWeb-land for a bit but dipping toes back in.\nkevinmarks.com \u2014 Long-time IndieWeb. Microformats co-founder with Tantek and has been blogging forever!\n\n Colin (vonexplaino.com) \u2014 From the east coast... of Australia! Been working in the web forever, new to IndieWeb. Recently been working on a lightbox that works without JavaScript.\n \n\nOther topics of discussion:\n\n Kevin showed a demo of his site running locally on his hard drive, on his website, and inside Beaker Browser. (Here's the Beaker 1.0 beta announcement)\n \n\n \n Talked a bit about how Beaker works. You make edits locally and then they are published from your own machine. Others on the Beaker network can share your site. Everything is signed with keys and content-addressable so you're the only one that can make changes to your published stuff.\n \n\n Beaker left behind DAT in the 1.0 release, breaking old URLs. They promise to never do this again, though?\n Kicks Condor did some good writing on Dat:// and how Beaker used it, as well as Duxtape, a tool that he built to share mixtapes over Dat.\n \n Kevin Marks has done a presentation on Dat, as well! Went through it in the Zoom. Compares to Web Packaging, including issues with content-addressability like trying to apply copyright takedowns and censor content.\n \n\n With so many tools, projects, protocols, and more available that solve different parts of the problems of self-publishing, how can we encourage more folks to pick them up and use them instead of silos?\n \n Owning your own content and publishing compared to organic foods. It's more involved and expensive, and some folks see it as niche or unnecessary, but you get benefits for the effort!\n \n\n Twitter rolled out a feature to control who can reply to specific tweets. Predictably, they were terribly smug about it.\n Context collapse is a problem everywhere on the web, but it's such a deep problem on Twitter that maybe they can't claw it back. So, this feature is a maybe almost-good idea that won't actually help the folks who receive the most abuse.\n There's a new microformats parser for JavaScript!Lots of interest in publishing it under an IndieWeb or Microformats umbrella to supersede the previous one (microformats-shiv?) which is some years out of date. Difficulty: need to track down who \"owns\" the Microformats account on NPM.\n \n It passes a lot of the newly updated tests, includes support for mf2 and mf1, and more! Thanks to Jason Garber for kicking off some recent work there.\n \n\n gRegor reviewed recent updates to php-mf2 that are very close to a new release!\n \n jmac.org working on a command line tool called Whim (link?) to allow folks to receive and process webmentions. Hopes to have something for folks to play with in the next month. This was kicked off by a friend trolling him by sending webmentions and nudging him to support posting short notes to his own site.\n \n\n \n kevinmarks.com is revisiting mention.tech to fix some issues with timing out on unresponsive pages.\n \n\nLeft-to-right, top-to-bottom: martymcgui.re, Kevin, david.shanske.com, kevinmarks.com, Colin, gRegorLove.com, Mike, kartikprabhu.com, jmac.orgThanks to all who joined us! We will see you all again at our next IndieWeb NYC (aka vHWC US East) meetup online on June 17th! Keep an eye on indieweb.nyc or events.indieweb.org/tag/nyc for the exact date, time, and online location!",
"html": "<p><a href=\"https://events.indieweb.org/2020/05/online-indieweb-meetup-nyc-vkY32vBfCTEJ\">IndieWeb NYC's meetup for May 2020 (also virtual Homebrew Website Club US East)</a>, met on Zoom from 6pm - 8pm EDT on May 20th.</p>\n<p>Here are some notes from the meeting!</p>\n<p>\n jmac.org \u2014 Moved to NYC and started attending local HWCs just before The Lockdown. Very interested in Webmention as a technology to connect websites to one another - but wants to improve the focus on how it can be used for real human interaction!\n <br /></p>\n<p>\n martymcgui.re \u2014 Long-time IndieWeb and NYC organizer. Been working on lots of random projects. Currently thinking about turning his pile of \"read\" posts, largely dumped from GoodReads, into more usable pages about what he's reading now, reading next, and read recently.\n <br /></p>\n<p>david.shanske.com \u2014 Long-time IndieWeb and NYC organizer. Been working on location features, aspirationally. Looking forward to a time when he can thrill audiences by reporting being in a location other than \"Home\".</p>\n<p>Sandro \u2014 Has been building CMSes and more for years. Been working on some new stuff that works even offline!</p>\n<p>Kevin \u2014 Worked w/ sandro at Limewire some years ago! Attended past HWC SF meetings in the Before Times. Has been calling into the West Coast virtual meetings, first time calling into East Coast. Wants his site (zootella.com) to publish to 3 places - webserver, local files, and Beaker Browser (just went 1.0!)</p>\n<p>Mike \u2014 Did web development for years, then stopped, now back again! Learned about IndieWeb through Micro.blog community. Interested in making sure the software he develops is a \"good IndieWeb citizen\". Working on a kind of Meetup competitor.</p>\n<p>jgregorymcverry.com \u2014 Long time IndieWeb and NYC organizer. Currently working on a website for a poetry radio show. Folks from all over the world can submit clips. It's wiki-based, but can also receive webmentions.</p>\n<p>gRegorLove.com \u2014 In San Diego, but joining East Coast to see some new faces. Been out of IndieWeb-land for a bit but dipping toes back in.</p>\n<p>kevinmarks.com \u2014 Long-time IndieWeb. Microformats co-founder with Tantek and has been blogging forever!</p>\n<p>\n Colin (vonexplaino.com) \u2014 From the east coast... of Australia! Been working in the web forever, new to IndieWeb. Recently been <a href=\"https://vonexplaino.com/blog/posts/article/2020/05/gallery-2020---mk-iv.html\">working on a lightbox that works without JavaScript</a>.\n <br /></p>\n<p>Other topics of discussion:</p>\n<ul><li>\n Kevin showed a demo of his site running locally on his hard drive, on his website, and inside <a href=\"https://beakerbrowser.com/\">Beaker Browser</a>. (Here's the <a href=\"https://beakerbrowser.com/2020/05/14/beaker-1-0-beta.html\">Beaker 1.0 beta announcement</a>)\n <br /></li>\n <li>\n Talked a bit about how Beaker works. You make edits locally and then they are published from your own machine. Others on the Beaker network can share your site. Everything is signed with keys and content-addressable so you're the only one that can make changes to your published stuff.\n <br /></li>\n <li>Beaker left behind DAT in the 1.0 release, breaking old URLs. They promise to never do this again, though?</li>\n <li>Kicks Condor did some good writing <a href=\"https://www.kickscondor.com/on-dat/\">on Dat://</a> and how Beaker used it, as well as <a href=\"https://github.com/kickscondor/duxtape\">Duxtape</a>, a tool that he built to share mixtapes over Dat.</li>\n <li>\n Kevin Marks has done <a href=\"http://slides.kevinmarks.com/dat.html#/\">a presentation on Dat</a>, as well! Went through it in the Zoom. Compares to <a href=\"https://github.com/WICG/webpackage\">Web Packaging</a>, including issues with content-addressability like trying to apply copyright takedowns and censor content.\n <br /></li>\n <li>With so many tools, projects, protocols, and more available that solve different parts of the problems of self-publishing, how can we encourage more folks to pick them up and use them instead of silos?</li>\n <li>\n Owning your own content and publishing compared to organic foods. It's more involved and expensive, and some folks see it as niche or unnecessary, but you get benefits for the effort!\n <br /></li>\n <li>Twitter rolled out a feature to control who can reply to specific tweets. Predictably, they were <a href=\"https://twitter.com/Twitter/status/1263203262968344576\">terribly</a> <a href=\"https://twitter.com/TwitterComms/status/1263209362845134848\">smug</a> about it.</li>\n <li>Context collapse is a problem everywhere on the web, but it's <a href=\"https://www.fastcompany.com/3063060/a-brief-history-of-the-angry-social-network\">such a deep problem on Twitter</a> that maybe they can't claw it back. So, this feature is a maybe almost-good idea that won't actually help the folks who receive the most abuse.</li>\n <li>There's a <a href=\"https://www.aimes.me.uk/2020/05/18/writing-microformats-parser/\">new microformats parser for JavaScript</a>!Lots of interest in publishing it under an IndieWeb or Microformats umbrella to supersede the previous one (microformats-shiv?) which is some years out of date. Difficulty: need to track down who \"owns\" the Microformats account on NPM.</li>\n <li>\n It passes a lot of the <a href=\"https://github.com/microformats/tests\">newly updated tests</a>, includes support for mf2 and mf1, and more! Thanks to <a href=\"https://sixtwothree.org/\">Jason Garber</a> for kicking off some recent work there.\n <br /></li>\n <li>gRegor reviewed recent updates to <a href=\"https://github.com/microformats/php-mf2\">php-mf2</a> that are very close to a new release!</li>\n <li>\n jmac.org working on a command line tool called Whim (<a href=\"https://jmac.org/whim\">link?</a>) to allow folks to receive and process webmentions. Hopes to have something for folks to play with in the next month. This was kicked off by a friend trolling him by sending webmentions and nudging him to support posting short notes to his own site.\n <br /></li>\n <li>\n kevinmarks.com is revisiting <a href=\"https://mention.tech/\">mention.tech</a> to fix some issues with timing out on unresponsive pages.\n <br /></li>\n</ul><img src=\"https://media.martymcgui.re/fb/3a/70/7f/2a560d9c898d604475776f8a6954255859fc89027b1be68585706347.jpg\" alt=\"\" />Left-to-right, top-to-bottom: martymcgui.re, Kevin, david.shanske.com, kevinmarks.com, Colin, gRegorLove.com, Mike, kartikprabhu.com, jmac.org<p>Thanks to all who joined us! We will see you all again at our <a href=\"https://events.indieweb.org/2020/06/online-indieweb-meetup-nyc-Vvg1d4IlQSKO\">next IndieWeb NYC (aka vHWC US East) meetup online on June 17th</a>! Keep an eye on <a href=\"https://indieweb.nyc/\">indieweb.nyc</a> or <a href=\"https://events.indieweb.org/tag/nyc\">events.indieweb.org/tag/nyc</a> for the exact date, time, and online location!\n</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "article",
"_id": "11746939",
"_source": "175",
"_is_read": true
}