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

Untitled

{
    "type": "entry",
    "published": "2019-02-21T19:59:18+00:00",
    "url": "https://notiz.blog/2019/02/21/untitled/",
    "featured": "https://notiz.blog/wp-content/uploads/2019/02/no-title-feeds-900x486.png",
    "name": "Untitled",
    "content": {
        "text": "Die Art wie wir kommunizieren hat sich ver\u00e4ndert. Die Flut an Informationen wird immer gr\u00f6\u00dfer und wir nehmen uns immer weniger Zeit zum lesen und schreiben. Aus E-Mail wurde Messaging, aus Bloggen wurde Microbloggen und wir nutzen Emojis, Hashtags und andere Abk\u00fcrzungen um die, so schon kurzen Texte, noch weiter zu \u201eoptimieren\u201c.\n\n\n\nDas ist prinzipiell auch nichts schlimmes, da sich mit jeder neuen Kommunikationsform in der Regel auch das Medium, mit dem ich es konsumiere, \u00e4ndert. Messaging-Texte lese ich in Telegram und E-Mails kann ich weiterhin in meiner Mail-App lesen.\n\n\n\nKomisch wird es aber, wenn sich Medien vermischen, oder wenn Tools versuchen unterschiedliche Medien zu normalisieren. 2011 versuchte Facebook, beispielsweise E-Mails und Messaging/Chat zu verheiraten und \u00fcber eine Oberfl\u00e4che nutzbar zu machen.\n\n\n\n\nThere are no subject lines, no cc, no bcc, and you can send a message by hitting the Enter key. We modeled it more closely to chat and reduced the number of things you need to do to send a message.\nFacebook: See the Messages that Matter\n\n\n\n\nAuf Facebook hat das Vorhaben auch gut funktioniert, aber \u00fcber die klassiche Mail-App sah ein \u201eDiscussion-Thread\u201c nicht wirklich h\u00fcbsch aus, weshalb das Projekt auch (zum Gl\u00fcck) wieder eingestellt wurde.\n\n\n\nAber wie komme ich auf das Thema?\n\n\n\nAktuell sieht es in meinem Feed-Reader folgenderma\u00dfen aus:\n\n\n\nReeder (RSS-Reader) auf dem iPhone\n\n\n\nKeine \u00dcberschriften, komische \u00dcberschriften, nur das Datum oder sogar der ganze Text als \u00dcberschrift. Schuld daran ist, die Verschmelzung von Blogging und Microblogging. Oder besser: Die Nutzung eines Feed-Readers um Microblogs zu lesen.\n\n\n\nMicro.blog ist ein Microblogging-Dienst, der 2017 \u00fcber eine Kickstarter-Kampangne finanziert wurde. Micro.blog orientiert sich stark an der IndieWeb Community und unterst\u00fctz viele IndieWeb Protokolle, wie z.B. Webmentions und Micropub. Der Service unterst\u00fctzt au\u00dferdem das abonnieren von klassischen Blogs wie z.B. WordPress \u00fcber das gute alte RSS Format. Und hier vermischen sich die beiden Themen.\n\n\n\nAus der WordPress Doku von Micro.blog:\n\n\n\nPart of indie microblogging is getting back to the simplicity of title-less posts. When you\u2019re writing a microblog post in WordPress, just leave the title blank, and if necessary update the post template to not include the title in HTML or the RSS feed.\n\n\n\nDurch die IndieWeb Community ver\u00f6ffentlichen viele Personen in meinem Umfeld alle Arten von Texten und anderen Medien auf ihren eigenen Webseiten. Ein signifikanter Anteil von ihnen nutzen daf\u00fcr WordPress und ein Teil davon wiederum meine Themes. Das hei\u00dft ich bin letztendlich sogar dreifach von diesem \u201eTrend\u201c betroffen: als Konsument, als Entwickler und als Publisher.\n\n\n\nIch verstehe den Ansatz, den Micro.blog verfolgt durchaus:\n\n\n\n\nYou may find that some feed readers don\u2019t gracefully handle posts without titles, often inserting \u201cUntitled\u201d for the title because they expect something to be there. If you see this, the best solution is to email the developer and ask for them to address it. Working around the issue with fake titles \u2014 dates, numbers, or portions of the text \u2014 will only ensure that client developers never improve their apps to handle title-less posts.\n\n\n\n\n\nApple macht es ganz \u00e4hnlich, wenn sie bei neuen iPhones die Kopfh\u00f6rer-Buchse weg lassen oder bei Laptops nur noch USB-C Anschl\u00fcsse verbauen. Man k\u00f6nnte argumentieren, dass es der einzige Weg sei um den Fortschritt voran zu treiben, aber ich bin von den \u00c4nderungen meistens eher genervt! Ich bin n\u00e4mlich derjenige der wieder neue Kopfh\u00f6rer und einen &%$?\u00a7 voll Adapter braucht.\n\n\n\nEin \u00e4hnliches Gef\u00fchl habe ich gerade bei Microblogging \u00fcber WordPress und Micro.blog. Nicht die RSS-Reader werden gezwungen sich anzupassen, sondern ich muss schauen, wie ich meine Lese- bzw. Schreibgewohnheiten ver\u00e4ndere. Ich \u201emuss\u201c mein Theme anpassen, ich \u201emuss\u201c meine Schreibgewohnheiten anpassen und ich \u201emuss\u201c schauen wie ich meinen Feed-Reader wieder \u201esauber\u201c bekomme.\n\n\n\nIch w\u00fcrde mir w\u00fcnschen wenn Micro.blog nicht so restriktiv mit dem Interpretieren von RSS w\u00e4re und wenn es einen flie\u00dfenderen \u00dcbergang g\u00e4be.\n\n\n\nIch w\u00fcrde mich freuen, wenn ich weiterhin Titel schreiben d\u00fcrfte, denn Titel sind gut f\u00fcr den Feed-Reader, f\u00fcr die sprechenden Permalinks oder einfach nur damit ich meine Artikel \u00fcber die WordPress Oberfl\u00e4che schneller wieder finde.\n\n\n\nIch w\u00fcrde mir w\u00fcnschen, dass Micro.blog einfach immer den Text oder die Summary nutzen w\u00fcrde und den Titel nur als Fallback. Von mir aus auch abh\u00e4ngig vom Post-Type.\n\n\n\nAktuell gibt es f\u00fcr mich aber nur zwei M\u00f6glichkeiten:\n\n\n\nIch lasse den Titel weg -> Micro.blog zeigt den vollen Text an und im Feed-Reader siehts schei\u00dfe aus\nIch schreibe einen Titel -> Micro.blog zeigt nur den Titel an, aber im Feed-Reader siehts gut aus\nEs gibt nat\u00fcrlich auch noch andere L\u00f6sungen, aber die sind immer mit Arbeit verbunden: HTTP Agent auslesen und nur f\u00fcr Micro.blog den Titel ausblenden, extra Feed f\u00fcr Micro.blog, \u2026\n\n\n\nAm Schluss ist Micro.blog aber nur exemplarisch f\u00fcr eine generelle Entwicklung in der IndieWeb Community.\n\n\n\nPeter Molnar hat in einem \u00e4hnlichen Zusammenhang etwas sehr passendes dazu geschrieben:\n\n\n\n\nIf I look at my wall, my timeline, or any other stream, it\u2019s a mess  which I\u2019m not proud of. It\u2019s a never-ending scroll of things, without  structure, without separating the less important from the more  important, without me, without focus. \u201cregaining focus\u201d is becoming much of a buzzterm but there is truth behind it.\nI want the blogs back\n\n\n\n\n\nWahrscheinlich sind es nicht die fehlenden Titel die mich aufregen, sondern die Flut an unstrukturierten, zusammenhanglosen Microblogposts, die ich eigentlich gar nicht in meinem Feed-Reader haben will.\n\n\n\n\u2026aber das ist eine andere Geschichte.",
        "html": "<p>Die Art wie wir kommunizieren hat sich ver\u00e4ndert. Die Flut an Informationen wird immer gr\u00f6\u00dfer und wir nehmen uns immer weniger Zeit zum lesen und schreiben. Aus E-Mail wurde Messaging, aus Bloggen wurde Microbloggen und wir nutzen Emojis, Hashtags und <a href=\"https://notiz.blog/2017/10/04/readability/\">andere Abk\u00fcrzungen</a> um die, so schon kurzen Texte, noch weiter zu \u201eoptimieren\u201c.</p>\n\n\n\n<p>Das ist prinzipiell auch nichts schlimmes, da sich mit jeder neuen Kommunikationsform in der Regel auch das Medium, mit dem ich es konsumiere, \u00e4ndert. Messaging-Texte lese ich in Telegram und E-Mails kann ich weiterhin in meiner Mail-App lesen.</p>\n\n\n\n<p>Komisch wird es aber, wenn sich Medien vermischen, oder wenn Tools versuchen unterschiedliche Medien zu normalisieren. 2011 versuchte Facebook, beispielsweise <a href=\"https://www.facebook.com/notes/facebook/see-the-messages-that-matter/452288242130\">E-Mails und Messaging/Chat zu verheiraten</a> und \u00fcber eine Oberfl\u00e4che nutzbar zu machen.</p>\n\n\n\n<blockquote>\n<p>There are no subject lines, no cc, no bcc, and you can send a message by hitting the Enter key. We modeled it more closely to chat and reduced the number of things you need to do to send a message.</p>\nFacebook: <a href=\"https://www.facebook.com/notes/facebook/see-the-messages-that-matter/452288242130\">See the Messages that Matter</a>\n</blockquote>\n\n\n\n<p>Auf Facebook hat das Vorhaben auch gut funktioniert, aber \u00fcber die klassiche Mail-App sah ein \u201eDiscussion-Thread\u201c nicht wirklich h\u00fcbsch aus, weshalb <a href=\"https://www.theverge.com/2014/2/24/5443454/facebook-retires-its-email-service\">das Projekt auch (zum Gl\u00fcck) wieder eingestellt wurde</a>.</p>\n\n\n\n<p>Aber wie komme ich auf das Thema?</p>\n\n\n\n<p>Aktuell sieht es in meinem Feed-Reader folgenderma\u00dfen aus:</p>\n\n\n\n<img src=\"https://aperture-proxy.p3k.io/46d582d92ffcf2f8d5555fee435117c73bccbc90/68747470733a2f2f6e6f74697a2e626c6f672f77702d636f6e74656e742f75706c6f6164732f323031392f30322f7265656465722d6e6f2d7469746c65732d666565642d35373678313032342e706e67\" alt=\"\" />Reeder (RSS-Reader) auf dem iPhone\n\n\n\n<p>Keine \u00dcberschriften, komische \u00dcberschriften, nur das Datum oder sogar der ganze Text als \u00dcberschrift. Schuld daran ist, die Verschmelzung von Blogging und Microblogging. Oder besser: Die Nutzung eines Feed-Readers um Microblogs zu lesen.</p>\n\n\n\n<p><a href=\"https://micro.blog\">Micro.blog</a> ist ein Microblogging-Dienst, der 2017 \u00fcber eine Kickstarter-Kampangne finanziert wurde. Micro.blog orientiert sich stark an der IndieWeb Community und unterst\u00fctz viele IndieWeb Protokolle, wie z.B. Webmentions und Micropub. Der Service unterst\u00fctzt au\u00dferdem das abonnieren von klassischen Blogs wie z.B. WordPress \u00fcber das gute alte RSS Format. Und hier vermischen sich die beiden Themen.</p>\n\n\n\n<p>Aus der <a href=\"http://help.micro.blog/2018/setting-up-wordpress/#no-titles\">WordPress Doku von Micro.blog</a>:</p>\n\n\n\n<blockquote><p>Part of indie microblogging is getting back to the simplicity of title-less posts. When you\u2019re writing a microblog post in WordPress, just leave the title blank, and if necessary update the post template to not include the title in HTML or the RSS feed.</p></blockquote>\n\n\n\n<p>Durch die IndieWeb Community ver\u00f6ffentlichen viele Personen in meinem Umfeld alle Arten von Texten und anderen Medien auf ihren eigenen Webseiten. Ein signifikanter Anteil von ihnen nutzen daf\u00fcr WordPress und ein Teil davon wiederum meine Themes. Das hei\u00dft ich bin letztendlich sogar dreifach von diesem \u201eTrend\u201c betroffen: als Konsument, als Entwickler und als Publisher.</p>\n\n\n\n<p>Ich verstehe den Ansatz, den Micro.blog verfolgt durchaus:</p>\n\n\n\n<blockquote>\n<p>You may find that some feed readers don\u2019t gracefully handle posts without titles, often inserting \u201cUntitled\u201d for the title because they expect something to be there. If you see this, the best solution is to email the developer and ask for them to address it. Working around the issue with fake titles \u2014 dates, numbers, or portions of the text \u2014 will only ensure that client developers never improve their apps to handle title-less posts.</p>\n<p></p>\n</blockquote>\n\n\n\n<p>Apple macht es ganz \u00e4hnlich, wenn sie bei neuen iPhones die Kopfh\u00f6rer-Buchse weg lassen oder bei Laptops nur noch USB-C Anschl\u00fcsse verbauen. Man k\u00f6nnte argumentieren, dass es der einzige Weg sei um den Fortschritt voran zu treiben, aber ich bin von den \u00c4nderungen meistens eher genervt! Ich bin n\u00e4mlich derjenige der wieder neue Kopfh\u00f6rer und einen <strong><em>&amp;%$?\u00a7</em></strong> voll Adapter braucht.</p>\n\n\n\n<p>Ein \u00e4hnliches Gef\u00fchl habe ich gerade bei Microblogging \u00fcber WordPress und Micro.blog. Nicht die RSS-Reader werden gezwungen sich anzupassen, sondern ich muss schauen, wie ich meine Lese- bzw. Schreibgewohnheiten ver\u00e4ndere. <a href=\"https://micro.blog/MrHenko/170619\">Ich \u201emuss\u201c mein Theme anpassen</a>, <a href=\"https://github.com/pfefferle/wordpress-webmention/issues/166\">ich \u201emuss\u201c meine Schreibgewohnheiten anpassen</a> und ich \u201emuss\u201c schauen wie ich meinen Feed-Reader wieder \u201esauber\u201c bekomme.</p>\n\n\n\n<p>Ich w\u00fcrde mir w\u00fcnschen wenn Micro.blog nicht so restriktiv mit dem Interpretieren von RSS w\u00e4re und wenn es einen flie\u00dfenderen \u00dcbergang g\u00e4be.</p>\n\n\n\n<p>Ich w\u00fcrde mich freuen, wenn ich weiterhin Titel schreiben d\u00fcrfte, denn Titel sind gut f\u00fcr den Feed-Reader, f\u00fcr die sprechenden Permalinks oder einfach nur damit ich meine Artikel \u00fcber die WordPress Oberfl\u00e4che schneller wieder finde.</p>\n\n\n\n<p>Ich w\u00fcrde mir w\u00fcnschen, dass Micro.blog einfach immer den Text oder die Summary nutzen w\u00fcrde und den Titel nur als Fallback. Von mir aus auch abh\u00e4ngig vom <a href=\"https://www.w3.org/TR/post-type-discovery/\">Post-Type</a>.</p>\n\n\n\n<p>Aktuell gibt es f\u00fcr mich aber nur zwei M\u00f6glichkeiten:</p>\n\n\n\n<ul><li>Ich lasse den Titel weg -&gt; Micro.blog zeigt den vollen Text an und im Feed-Reader siehts schei\u00dfe aus</li>\n<li>Ich schreibe einen Titel -&gt; Micro.blog zeigt nur den Titel an, aber im Feed-Reader siehts gut aus</li>\n</ul><p>Es gibt nat\u00fcrlich auch noch andere L\u00f6sungen, aber die sind immer mit Arbeit verbunden: HTTP Agent auslesen und nur f\u00fcr Micro.blog den Titel ausblenden, <a href=\"https://github.com/glueckpress/micro.blog\">extra Feed f\u00fcr Micro.blog</a>, \u2026</p>\n\n\n\n<p>Am Schluss ist Micro.blog aber nur exemplarisch f\u00fcr eine generelle Entwicklung in der IndieWeb Community.</p>\n\n\n\n<p>Peter Molnar hat in einem <a href=\"https://petermolnar.net/i-want-the-blogs-back/\">\u00e4hnlichen Zusammenhang</a> etwas sehr passendes dazu geschrieben:</p>\n\n\n\n<blockquote>\n<p>If I look at my wall, my timeline, or any other stream, it\u2019s a mess  which I\u2019m not proud of. It\u2019s a never-ending scroll of things, without  structure, without separating the less important from the more  important, without me, without focus. <em>\u201cregaining focus\u201d is becoming much of a buzzterm but there is truth behind it.</em></p>\n<a href=\"https://petermolnar.net/i-want-the-blogs-back/index.html\">I want the blogs back</a>\n</blockquote>\n\n\n\n<p><br />Wahrscheinlich sind es nicht die fehlenden Titel die mich aufregen, sondern die Flut an unstrukturierten, zusammenhanglosen Microblogposts, die ich eigentlich gar nicht in meinem Feed-Reader haben will.</p>\n\n\n\n<p>\u2026aber das ist eine andere Geschichte.</p>"
    },
    "author": {
        "type": "card",
        "name": "Matthias Pfefferle",
        "url": "https://notiz.blog/author/matthias-pfefferle/",
        "photo": "https://secure.gravatar.com/avatar/75512bb584bbceae57dfc503692b16b2?s=40&d=https://notiz.blog/wp-content/plugins/semantic-linkbacks/img/mm.jpg&r=g"
    },
    "post-type": "note",
    "_id": "2262074",
    "_source": "206",
    "_is_read": true
}

Manton Reece www.manton.org

Why attend IndieWebCamp

{
    "type": "entry",
    "author": {
        "name": "Manton Reece",
        "url": "https://www.manton.org/",
        "photo": "https://aperture-proxy.p3k.io/907926e361383204bd1bc913c143c23e70ae69bb/68747470733a2f2f6d6963726f2e626c6f672f6d616e746f6e2f6176617461722e6a7067"
    },
    "url": "https://www.manton.org/2019/02/21/why-attend-indiewebcamp.html",
    "name": "Why attend IndieWebCamp",
    "content": {
        "html": "<p>This weekend is IndieWebCamp Austin, an event for bloggers, web developers, designers, and anyone who wants to create something for their own web site, or to build tools based on IndieWeb standards. You can <a href=\"https://2019.indieweb.org/austin\">register here</a>. After my first IndieWebCamp, <a href=\"https://www.manton.org/2017/12/12/indiewebcamp-austin-wrapup.html\">I wrote</a>:</p>\n\n<blockquote>\n<p>There\u2019s nothing like meeting in person with other members of the community. I know this from attending Apple developer conferences, but the weekend in Austin only underscored that I should be more active in the larger web community as well.</p>\n</blockquote>\n\n<p>It\u2019s invaluable to chat with someone in person. This year, we\u2019ll have IndieWeb co-founders Tantek \u00c7elik and Aaron Parecki back in Austin. I\u2019m looking forward to hearing how the IndieWeb has moved forward in the last year.</p>\n\n<p><a href=\"https://www.manton.org/2017/12/09/session-planning-at.html\"><img src=\"https://aperture-proxy.p3k.io/6ac350d19c6ebe89e78a40624f743116806f9760/68747470733a2f2f7777772e6d616e746f6e2e6f72672f75706c6f6164732f323031382f616265623361666165662e6a7067\" width=\"150\" height=\"150\" alt=\"Sticky notes\" border=\"0\" align=\"right\" hspace=\"15\" vspace=\"5\" style=\"width:150px;max-width:150px;\" /></a> The first day of IndieWebCamp is for introductions and sessions. Topics for sessions are based on what attendees want to hear about, so the planning is done with sticky notes that can be rearranged to find a schedule that works for everyone. This is a photo I took from IndieWebCamp in 2017.</p>\n\n<p>I look at IndieWebCamp as a way to take a break from the day-to-day routine and get inspired again \u2014 to improve my own web site or discover a new part of Micro.blog to work on. As I was talking about with Daniel on <a href=\"https://coreint.org/361\">the latest Core Intuition</a>, because the 2nd day of IndieWebCamp is a hack day, it\u2019s also a great environment to work on something you\u2019ve had trouble finishing\u2026 or starting! There are other people around to help answer questions, and a nice block of time to focus on one thing.</p>\n\n<p>If you\u2019re in the Austin area, hope to see you there on Saturday! You can <a href=\"https://2019.indieweb.org/austin\">learn more here</a>.</p>",
        "text": "This weekend is IndieWebCamp Austin, an event for bloggers, web developers, designers, and anyone who wants to create something for their own web site, or to build tools based on IndieWeb standards. You can register here. After my first IndieWebCamp, I wrote:\n\n\nThere\u2019s nothing like meeting in person with other members of the community. I know this from attending Apple developer conferences, but the weekend in Austin only underscored that I should be more active in the larger web community as well.\n\n\nIt\u2019s invaluable to chat with someone in person. This year, we\u2019ll have IndieWeb co-founders Tantek \u00c7elik and Aaron Parecki back in Austin. I\u2019m looking forward to hearing how the IndieWeb has moved forward in the last year.\n\n The first day of IndieWebCamp is for introductions and sessions. Topics for sessions are based on what attendees want to hear about, so the planning is done with sticky notes that can be rearranged to find a schedule that works for everyone. This is a photo I took from IndieWebCamp in 2017.\n\nI look at IndieWebCamp as a way to take a break from the day-to-day routine and get inspired again \u2014 to improve my own web site or discover a new part of Micro.blog to work on. As I was talking about with Daniel on the latest Core Intuition, because the 2nd day of IndieWebCamp is a hack day, it\u2019s also a great environment to work on something you\u2019ve had trouble finishing\u2026 or starting! There are other people around to help answer questions, and a nice block of time to focus on one thing.\n\nIf you\u2019re in the Austin area, hope to see you there on Saturday! You can learn more here."
    },
    "published": "2019-02-21T11:03:20-06:00",
    "post-type": "article",
    "_id": "2260676",
    "_source": "12",
    "_is_read": true
}

Marty McGuire martymcgui.re

HWC NYC Wrap-Up 2019-02-20

{
    "type": "entry",
    "published": "2019-02-20T19:34:24-0500",
    "url": "https://martymcgui.re/2019/02/20/hwc-nyc-wrap-up-2019-02-20/",
    "featured": "https://res.cloudinary.com/schmarty/image/fetch/w_960,c_fill/https://media.martymcgui.re/ed/98/c1/3c/c033fce095c2dac16912a9d6410d0fc60e722aef4275bc29d3eb5ecf.jpg",
    "category": [
        "HWC",
        "NYC",
        "IndieWeb",
        "wrap-up"
    ],
    "name": "HWC NYC Wrap-Up 2019-02-20",
    "content": {
        "text": "New York City's second Homebrew Website Club of February met at The Bean at Cooper Union on February 20th, organized by Tiara Miller and myself.\n  \n\nHere are some notes from the \"broadcast\" portion of the meetup!\n\n  rootedfromnature.com \u2014 Finished a Python lab assignment! Felt like she was overthinking it. Also doesn't like that the particular problems are more math problem than coding problem. Plans to sign up for actual coding classes to get more practical coding experience.\n  \n\n\n  dmitri.shuralyov.com \u2014 Wants to visualize notifications from GitHub and Gerrit. He collects the data (sometimes by processing emails!) on his own site and wants to expose it. Spent some time thinking / brainstorming about how to design those things. Asked some fellow Go programmers about known ways to handle emails w/ Go. Wants it to work \"forever\" (the next decade) so is being careful about the design.\n  \n\n\n  martymcgui.re \u2014 Played with layouts for his new /listens page. Looked at Pinterest and Dribbble and other design sites for \"timeline\" layouts and was pretty unhappy with what he found. Lots of \"draw a line with labels and draw lines extending off to things.\" So, took some time to start extracting \"listen\" bits like podcast art, episode title, audio links, into simpler blocks to start playing with layouts.\n  \n\nOther discussions:\nThings that Go is really good at. Like being an http2 server!\n  This new location! It... seems fine? It was crowded when we came in but we eventually got a table. No outlets handy as far as we could find. We'll keep looking for new venues!\n  IndieWebCamp Austin is this weekend!\n  \n    IndieWebCamp Online is also only a couple of weekends away!\n    \n\n  \n    IndieWebCamp New Haven is at the end of March and planning is getting scrambly! There are wiki pages to create but there's a lot of missing information and content yet! Tiara has been co-organizing w/ wiki stuff. Marty volunteered to help, too. Being remote, we need Greg to fill in with his local knowledge about the area and venue though!\n    \n\n  \n    What about IWC NYC! Yeah we'll do one too. Later in the year, though.\n    \n\nLeft-to-right: dmitri.shuralyov.com, martymcgui.re, rootedfromnature.com\nPanoramic view of the venueThanks to everyone who came out! We look forward to seeing you at our next meetup on Wednesday, March 6th at 6:30pm!",
        "html": "<p>\n  New York City's second <a href=\"https://indieweb.org/events/2019-02-20-homebrew-website-club-nyc\">Homebrew Website Club of February</a> met at <a href=\"https://www.thebeannyc.com/location/the-bean-3rd-ave/\">The Bean at Cooper Union</a> on February 20th, organized by <a href=\"https://rootedfromnature.com/\">Tiara Miller</a> and myself.\n  <br /></p>\n<p>Here are some notes from the \"broadcast\" portion of the meetup!</p>\n<p>\n  rootedfromnature.com \u2014 Finished a Python lab assignment! Felt like she was overthinking it. Also doesn't like that the particular problems are more math problem than coding problem. Plans to sign up for actual coding classes to get more practical coding experience.\n  <br /></p>\n<p>\n  dmitri.shuralyov.com \u2014 Wants to visualize notifications from GitHub and Gerrit. He collects the data (sometimes by processing emails!) on his own site and wants to expose it. Spent some time thinking / brainstorming about how to design those things. Asked some fellow Go programmers about known ways to handle emails w/ Go. Wants it to work \"forever\" (the next decade) so is being careful about the design.\n  <br /></p>\n<p>\n  martymcgui.re \u2014 Played with layouts for his new /listens page. Looked at Pinterest and Dribbble and other design sites for \"timeline\" layouts and was pretty unhappy with what he found. Lots of \"draw a line with labels and draw lines extending off to things.\" So, took some time to start extracting \"listen\" bits like podcast art, episode title, audio links, into simpler blocks to start playing with layouts.\n  <br /></p>\n<p>Other discussions:</p>\n<ul><li>Things that <a href=\"https://golang.org/\">Go</a> is really good at. Like being an http2 server!</li>\n  <li>This new location! It... seems fine? It was crowded when we came in but we eventually got a table. No outlets handy as far as we could find. We'll keep looking for new venues!</li>\n  <li>IndieWebCamp Austin is this weekend!</li>\n  <li>\n    IndieWebCamp Online is also only a couple of weekends away!\n    <br /></li>\n  <li>\n    IndieWebCamp New Haven is at the end of March and planning is getting scrambly! There are wiki pages to create but there's a lot of missing information and content yet! Tiara has been co-organizing w/ wiki stuff. Marty volunteered to help, too. Being remote, we need Greg to fill in with his local knowledge about the area and venue though!\n    <br /></li>\n  <li>\n    What about IWC NYC! Yeah we'll do one too. Later in the year, though.\n    <br /></li>\n</ul><img class=\"u-featured\" alt=\"HWC NYC participants\" src=\"https://res.cloudinary.com/schmarty/image/fetch/w_960,c_fill/https://media.martymcgui.re/ed/98/c1/3c/c033fce095c2dac16912a9d6410d0fc60e722aef4275bc29d3eb5ecf.jpg\" />Left-to-right: dmitri.shuralyov.com, martymcgui.re, rootedfromnature.com<a href=\"https://media.martymcgui.re/b1/db/60/97/8801aa275477aa03ef0a2de19e321cb9e7a5f4cf063114a75a9441dc.jpg\"><img alt=\"Very wide photo of the venue with lots of tables and chairs, patrons, and our three HWC attendees.\" src=\"https://aperture-proxy.p3k.io/16b8bbede8a09dedd8df6090ad91312b834e1152/68747470733a2f2f6d656469612e6d617274796d636775692e72652f32332f66652f38372f32322f31343433313865386562333531303333383330636161623165373763306562643461613163373736303331376638636335363834343730372e6a7067\" /></a>\nPanoramic view of the venue<p>Thanks to everyone who came out! We look forward to seeing you at our next meetup on Wednesday, March 6th at 6:30pm! </p>"
    },
    "author": {
        "type": "card",
        "name": "Marty McGuire",
        "url": "https://martymcgui.re/",
        "photo": "https://aperture-proxy.p3k.io/8275f85e3a389bd0ae69f209683436fc53d8bad9/68747470733a2f2f6d617274796d636775692e72652f696d616765732f6c6f676f2e6a7067"
    },
    "post-type": "article",
    "_id": "2253376",
    "_source": "175",
    "_is_read": true
}

Eddie Hinkle eddiehinkle.com

{
    "type": "entry",
    "published": "2019-02-20T17:09:08-05:00",
    "url": "https://eddiehinkle.com/2019/02/20/20/note/",
    "category": [
        "indieweb-meetup",
        "indieweb"
    ],
    "syndication": [
        "https://micro.blog/EddieHinkle",
        "https://twitter.com/eddiehinkle"
    ],
    "content": {
        "text": "The Virtual IndieWeb Meetup Americas is tonight! Come join us while we hang out and chat about our websites, what we're blogging about or what we'd like to post in the future.",
        "html": "The <a href=\"https://eddiehinkle.com/2019/02/20/1/event/\">Virtual IndieWeb Meetup Americas is tonight</a>! Come <a href=\"https://eddiehinkle.com/2019/02/20/1/event/\">join us</a> while we hang out and chat about our websites, what we're blogging about or what we'd like to post in the future."
    },
    "author": {
        "type": "card",
        "name": "Eddie Hinkle",
        "url": "https://eddiehinkle.com/",
        "photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
    },
    "post-type": "note",
    "_id": "2251226",
    "_source": "226",
    "_is_read": true
}

Manton Reece www.manton.org

{
    "type": "entry",
    "author": {
        "name": "Manton Reece",
        "url": "https://www.manton.org/",
        "photo": "https://aperture-proxy.p3k.io/907926e361383204bd1bc913c143c23e70ae69bb/68747470733a2f2f6d6963726f2e626c6f672f6d616e746f6e2f6176617461722e6a7067"
    },
    "url": "https://www.manton.org/2019/02/20/doors-open-for.html",
    "content": {
        "html": "<p>Doors open for IndieWebCamp Austin at 9am on Saturday. We\u2019ll have coffee and breakfast tacos. Full schedule and registration details: <a href=\"https://2019.indieweb.org/austin\">2019.indieweb.org/austin</a> \u2615</p>",
        "text": "Doors open for IndieWebCamp Austin at 9am on Saturday. We\u2019ll have coffee and breakfast tacos. Full schedule and registration details: 2019.indieweb.org/austin \u2615"
    },
    "published": "2019-02-20T15:10:51-06:00",
    "post-type": "note",
    "_id": "2249623",
    "_source": "12",
    "_is_read": true
}

Manton Reece www.manton.org

{
    "type": "entry",
    "author": {
        "name": "Manton Reece",
        "url": "https://www.manton.org/",
        "photo": "https://aperture-proxy.p3k.io/907926e361383204bd1bc913c143c23e70ae69bb/68747470733a2f2f6d6963726f2e626c6f672f6d616e746f6e2f6176617461722e6a7067"
    },
    "url": "https://www.manton.org/2019/02/20/we-just-posted.html",
    "content": {
        "html": "<p>We just posted <a href=\"https://coreint.org/2019/02/episode-361-this-is-an-opportunity/\">Core Intuition 361</a>. Looking forward to IndieWebCamp Austin and talking about whether new Marzipan rumors will influence our plans this year.</p>",
        "text": "We just posted Core Intuition 361. Looking forward to IndieWebCamp Austin and talking about whether new Marzipan rumors will influence our plans this year."
    },
    "published": "2019-02-20T14:12:03-06:00",
    "post-type": "note",
    "_id": "2248905",
    "_source": "12",
    "_is_read": true
}

Marty McGuire martymcgui.re

Site Updates: /listens and /photos pages

{
    "type": "entry",
    "published": "2019-02-19T17:53:18-0500",
    "url": "https://martymcgui.re/2019/02/19/site-updates-listens-and-photos-pages/",
    "category": [
        "listen",
        "read",
        "IndieWeb",
        "site-update"
    ],
    "name": "Site Updates: /listens and /photos pages",
    "content": {
        "text": "Inspired by Jonathan LaCour's January post about tracking his podcast listening habits, I recently decided to bring in my own listening history into my website.\nLike Jonathan, I use Overcast to listen to podcasts on my phone, and I was surprised and delighted to learn that Overcast has an \"All data\" export option on the accounts page that includes per-episode details such as whether you listened to an ep, and when you last interacted with it!\nI took a look at Jonathan's script to automatically log in and import his Overcast data and figured I could make something a little more minimal that would work with my Hugo site.\nMy process follows three steps: download the overcast.opml full export file, run a script to generate the Hugo posts, and run a script to grab extra podcast metadata like cover art.\nYou can find my scripts in this gist if you're interested in learning more, but they may not be that useful for anyone without my exact Hugo config.\n\n  You may notice in the scripts that I have a \"block list\" of podcast URLs I can add. That's because I wanted my listen posts to helpfully link to and embed audio whenever possible. However, some of the feeds I subscribe to contain private or for-pay content - particularly a couple of podcasts I support on Patreon. I do want to track my listening habits for these podcasts, so I will likely start handling them differently by leaving out the embedded audio and linking directly to Patreon pages where possible.\n  \n\nRunning the script, I was able to happily show everything I listened to as just another type of post on my site. However, it turns out I had (and keep making) a lot of listen posts. Visually they were drowning out all my other activity on my site.\nSo I have sequestered them on a new Listens page where you can only follow my podcast consumption history, keeping it out of my main feeds.\nSimilarly, I have been interested in having a nice Instagram-like page that shows off my photos in a grid. So I made a Photos page to show off those posts.\nBoth of these pages have microformats2 feed information embedded, so if you have an Indie reader, you might be interested in following just those pages!",
        "html": "<p>Inspired by <a href=\"https://cleverdevil.io/2019/tracking-my-movie-tv-and-podcast-activity\">Jonathan LaCour's January post about tracking his podcast listening habits</a>, I recently decided to bring in my own listening history into my website.</p>\n<p>Like Jonathan, I use <a href=\"https://overcast.fm/\">Overcast</a> to listen to podcasts on my phone, and I was surprised and delighted to learn that Overcast has an \"All data\" <a href=\"https://overcast.fm/account\">export option on the accounts page</a> that includes per-episode details such as whether you listened to an ep, and when you last interacted with it!</p>\n<p>I took a look at Jonathan's <a href=\"https://gist.github.com/cleverdevil/a8215850420493c1ee06364161e281c0\">script to automatically log in and import his Overcast data </a>and figured I could make something a little more minimal that would work with my Hugo site.</p>\n<p>My process follows three steps: download the overcast.opml full export file, run a script to generate the Hugo posts, and run a script to grab extra podcast metadata like cover art.</p>\n<p>You can find my <a href=\"https://gist.github.com/martymcguire/57bc398d74557904d1eea5ebc01c8c3e\">scripts in this gist</a> if you're interested in learning more, but they may not be that useful for anyone without my exact Hugo config.</p>\n<p>\n  You may notice in the scripts that I have a \"block list\" of podcast URLs I can add. That's because I wanted my listen posts to helpfully link to and embed audio whenever possible. However, some of the feeds I subscribe to contain private or for-pay content - particularly a couple of podcasts I support on Patreon. I do want to track my listening habits for these podcasts, so I will likely start handling them differently by leaving out the embedded audio and linking directly to Patreon pages where possible.\n  <br /></p>\n<p>Running the script, I was able to happily show everything I listened to as just another type of post on my site. However, it turns out I had (and keep making) a <i>lot of listen posts</i>. Visually they were drowning out all my other activity on my site.</p>\n<p>So I have sequestered them on a new <a href=\"https://martymcgui.re/listens/\">Listens page</a> where you can only follow my podcast consumption history, keeping it out of my main feeds.</p>\n<p>Similarly, I have been interested in having a nice Instagram-like page that shows off my photos in a grid. So I made a <a href=\"https://martymcgui.re/photos/\">Photos page</a> to show off those posts.</p>\n<p>Both of these pages have <a href=\"http://microformats.org/wiki/h-feed\">microformats2 feed</a> information embedded, so if you have an <a href=\"https://indieweb.org/reader\">Indie reader</a>, you might be interested in following just those pages!</p>"
    },
    "author": {
        "type": "card",
        "name": "Marty McGuire",
        "url": "https://martymcgui.re/",
        "photo": "https://aperture-proxy.p3k.io/8275f85e3a389bd0ae69f209683436fc53d8bad9/68747470733a2f2f6d617274796d636775692e72652f696d616765732f6c6f676f2e6a7067"
    },
    "post-type": "article",
    "_id": "2239887",
    "_source": "175",
    "_is_read": true
}

Manton Reece www.manton.org

{
    "type": "entry",
    "author": {
        "name": "Manton Reece",
        "url": "https://www.manton.org/",
        "photo": "https://aperture-proxy.p3k.io/907926e361383204bd1bc913c143c23e70ae69bb/68747470733a2f2f6d6963726f2e626c6f672f6d616e746f6e2f6176617461722e6a7067"
    },
    "url": "https://www.manton.org/2019/02/19/indiewebcamp-austin-is.html",
    "content": {
        "html": "<p>IndieWebCamp Austin is this weekend! You can still <a href=\"https://2019.indieweb.org/austin\">register here</a>.</p>",
        "text": "IndieWebCamp Austin is this weekend! You can still register here."
    },
    "published": "2019-02-19T15:25:26-06:00",
    "post-type": "note",
    "_id": "2238184",
    "_source": "12",
    "_is_read": true
}

Malcolm Blaney unicyclic.com/mal

The things we do to read 💩 emoji

{
    "type": "entry",
    "published": "2019-02-18T13:35:46+10:00",
    "url": "https://unicyclic.com/mal/2019-02-18-The_things_we_do_to_read__emoji",
    "category": [
        "indieweb"
    ],
    "name": "The things we do to read \ud83d\udca9 emoji",
    "content": {
        "text": "Ok I totally stole the title from this article, which was really good and help me fix my problems so I wanted to link to it.\n\n\nI recently upgraded all my servers from Jessie to Stretch, which was long overdue. The catalyst being that certbot from Let's Encrypt started complaining about the security I was using to fetch new certificates. (It complained in a very nice way and helped fix the problem, I should add.)\n\n\nAnyway the upgrades went fine, Debian is very good at that. The problem was that part of the upgrade was switching from MySQL 5 to MariaDB, and all my tables were using an old character set and collation type. This showed up as emoji not rendering properly in my reader. Easy fix: switch the reader items table to the utf8mb4 character set and collation type to utf8mb4_unicode_ci. Problem solved.\n\n\nThis is where the fun really started though, and where my desire to understand the inner workings of databases started fading... My reader became so slow at loading items that it was unusable. The rest of the site worked fine, so I isolated the problem down to one database query. Due to the way I now have channels set up, this was a particularly complicated query running on the largest table in my database, reader_items which was 400k rows and growing. I delved deeper into the murky world of database performance, learning about sargable queries and how to keep your indexes fast.\n\n\nMaking sure all the tables joined in the same query have a matching collation type seemed to do the trick. My query which had blown out to over a minute was now running in a couple of seconds. A good reminder to look after your indexes! Since I was well and truly into database tuning now though, I decided I could get more performance improvements out of my reader.\n\n\nThe problem with adding new feed items to the same table is that you generally only want to read the new stuff. It's great to have fast indexes, but most of the time I really just need smaller tables. To do that my reader needed to be able to look up items in an arbitrary number of tables, but optimised to find new items in the first table it reads from. It can now do that, and the data partitioning process is automated to keep the items tables small. It can also handle reading across tables to return the correct number of items requested.\n\n\nThe problematic query now returns in less than a second for the optimised case. (I would measure it but it's not a noticeable part of using the reader any more.) My plan to fix the performance issues before making this change was to increase the specs of the server it's running on, which are pretty modest for all the work it's doing. I do however like the idea of improving the efficiency of code rather than throwing more hardware at a poorly running solution.",
        "html": "Ok I totally stole the title from <a href=\"https://mathiasbynens.be/notes/mysql-utf8mb4\">this article</a>, which was really good and help me fix my problems so I wanted to link to it.<br /><br />\nI recently upgraded all my servers from Jessie to Stretch, which was long overdue. The catalyst being that certbot from Let's Encrypt started complaining about the security I was using to fetch new certificates. (It complained in a very nice way and helped fix the problem, I should add.)<br /><br />\nAnyway the upgrades went fine, Debian is very good at that. The problem was that part of the upgrade was switching from MySQL 5 to MariaDB, and all my tables were using an old character set and collation type. This showed up as emoji not rendering properly in my reader. Easy fix: switch the reader items table to the utf8mb4 character set and collation type to utf8mb4_unicode_ci. Problem solved.<br /><br />\nThis is where the fun really started though, and where my desire to understand the inner workings of databases started fading... My reader became so slow at loading items that it was unusable. The rest of the site worked fine, so I isolated the problem down to one database query. Due to the way I now have channels set up, this was a particularly complicated query running on the largest table in my database, reader_items which was 400k rows and growing. I delved deeper into the murky world of database performance, learning about <em>sargable queries</em> and how to keep your indexes fast.<br /><br />\nMaking sure all the tables joined in the same query have a matching collation type seemed to do the trick. My query which had blown out to over a minute was now running in a couple of seconds. A good reminder to look after your indexes! Since I was well and truly into database tuning now though, I decided I could get more performance improvements out of my reader.<br /><br />\nThe problem with adding new feed items to the same table is that you generally only want to read the new stuff. It's great to have fast indexes, but most of the time I really just need smaller tables. To do that my reader needed to be able to look up items in an arbitrary number of tables, but optimised to find new items in the first table it reads from. It can now do that, and the data partitioning process is automated to keep the items tables small. It can also handle reading across tables to return the correct number of items requested.<br /><br />\nThe problematic query now returns in less than a second for the optimised case. (I would measure it but it's not a noticeable part of using the reader any more.) My plan to fix the performance issues before making this change was to increase the specs of the server it's running on, which are pretty modest for all the work it's doing. I do however like the idea of improving the efficiency of code rather than throwing more hardware at a poorly running solution."
    },
    "author": {
        "type": "card",
        "name": "Malcolm Blaney",
        "url": "https://unicyclic.com/mal",
        "photo": "https://aperture-proxy.p3k.io/4f46272c0027449ced0d7cf8de31ea1bec37210e/68747470733a2f2f756e696379636c69632e636f6d2f6d616c2f7075626c69632f70726f66696c655f736d616c6c5f7468756d622e706e67"
    },
    "post-type": "article",
    "_id": "2217414",
    "_source": "243",
    "_is_read": true
}

Manton Reece www.manton.org

{
    "type": "entry",
    "author": {
        "name": "Manton Reece",
        "url": "https://www.manton.org/",
        "photo": "https://aperture-proxy.p3k.io/907926e361383204bd1bc913c143c23e70ae69bb/68747470733a2f2f6d6963726f2e626c6f672f6d616e746f6e2f6176617461722e6a7067"
    },
    "url": "https://www.manton.org/2019/02/16/just-posted-the.html",
    "content": {
        "html": "<p>Just posted <a href=\"http://coreint.org/360\">the new Core Intuition</a>. More about WWDC travel, IndieWebCamp Austin, and Daniel considering dropping Blogger from MarsEdit.</p>",
        "text": "Just posted the new Core Intuition. More about WWDC travel, IndieWebCamp Austin, and Daniel considering dropping Blogger from MarsEdit."
    },
    "published": "2019-02-16T18:21:22-06:00",
    "post-type": "note",
    "_id": "2207651",
    "_source": "12",
    "_is_read": true
}

Manton Reece www.manton.org

{
    "type": "entry",
    "author": {
        "name": "Manton Reece",
        "url": "https://www.manton.org/",
        "photo": "https://aperture-proxy.p3k.io/907926e361383204bd1bc913c143c23e70ae69bb/68747470733a2f2f6d6963726f2e626c6f672f6d616e746f6e2f6176617461722e6a7067"
    },
    "url": "https://www.manton.org/2019/02/15/indiewebcamp-austin-is.html",
    "content": {
        "html": "<p><a href=\"https://2019.indieweb.org/austin\">IndieWebCamp Austin</a> is coming up in a week at Capital Factory. Bunch of IndieWeb-related things I want to think about for Micro.blog that weekend. Everyone\u2019s welcome!</p>",
        "text": "IndieWebCamp Austin is coming up in a week at Capital Factory. Bunch of IndieWeb-related things I want to think about for Micro.blog that weekend. Everyone\u2019s welcome!"
    },
    "published": "2019-02-15T17:10:56-06:00",
    "post-type": "note",
    "_id": "2194339",
    "_source": "12",
    "_is_read": true
}

Grant Richmond grant.codes

{
    "type": "entry",
    "published": "2019-02-14T16:26:17.467Z",
    "url": "https://grant.codes/2019/02/14/awesome-lets-try-to-get-you",
    "syndication": [
        "https://twitter.com/grantcodes/status/1096083218669936641"
    ],
    "content": {
        "text": "Awesome! Let's try to get you on there! So I think your issue is that your authorization endpoint is set to indiecert.net which doesn't seem to exist. You might want to use indieauth.com instead?",
        "html": "<p>Awesome! Let's try to get you on there! So I think your issue is that your authorization endpoint is set to indiecert.net which doesn't seem to exist. You might want to use indieauth.com instead?</p>"
    },
    "author": {
        "type": "card",
        "name": "Grant Richmond",
        "url": "https://grant.codes",
        "photo": "https://aperture-proxy.p3k.io/be31049af9884a65289b2d14300adafc0e4030c6/68747470733a2f2f6772616e742e636f6465732f696d672f6d652e6a7067"
    },
    "post-type": "note",
    "_id": "2176337",
    "_source": "11",
    "_is_read": true
}

Kevin Marks known.kevinmarks.com/profile/kevinmarks

Pixellated Microformats SVG button to celebrate the 15th anniversary of Microformats being shown off at ETCON 2004 by Tantek and myself.

{
    "type": "entry",
    "published": "2019-02-13T19:27:29+0000",
    "url": "http://known.kevinmarks.com/2019/pixellated-microformats-svg-button-to-celebrate-the-15th-anniversary-of",
    "photo": [
        "https://aperture-proxy.p3k.io/ba096a689cab072e9308f2a034805b89dfebe14f/687474703a2f2f6b6e6f776e2e6b6576696e6d61726b732e636f6d2f66696c652f63613830613630393264366262626537373764306161653934363864666262652f6d6963726f666f726d6174732e737667"
    ],
    "name": "Pixellated Microformats SVG button to celebrate the 15th anniversary of Microformats being shown off at ETCON 2004 by Tantek and myself.",
    "author": {
        "type": "card",
        "name": "Kevin Marks",
        "url": "http://known.kevinmarks.com/profile/kevinmarks",
        "photo": "https://aperture-proxy.p3k.io/ed7979fd10a648fc253eae0b54e66fb36e57d3d4/687474703a2f2f6b6e6f776e2e6b6576696e6d61726b732e636f6d2f66696c652f3932353536353636363931373362373836376162383339656536353536663965"
    },
    "post-type": "photo",
    "_id": "2167724",
    "_source": "205",
    "_is_read": true
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2019-02-13 00:29-0800",
    "url": "http://tantek.com/2019/044/t1/15-years-ago-introduced-microformats",
    "category": [
        "microformats",
        "RDFa",
        "microdata",
        "HTMLFirst",
        "CSS"
    ],
    "content": {
        "text": "15 years ago @KevinMarks & I introduced #microformats @oreillymedia ETech 2004 \u201creal world semantics\u201d session, before #RDFa #microdata etc., with <15k #HTMLFirst + inline #CSS+#JS: tantek.com/presentations/2004etech/realworldsemanticspres.html (faster than JS-only slides)\n\nPreviously: tantek.com/t4UY2 (https://twitter.com/t/status/433494367601717248)\n\nSince then:\n* drop the (X), just HTML\n* meta tags still web alchemy, even more bloated DRY rot\n* h-entry superceded hAtom/hentry/rel=\"bookmark\" - microformats.org/wiki/h-entry\n* recommendations: hReview still more reliable than anything from Google (https://aaronparecki.com/2016/12/17/8/owning-my-reviews). Use h-review today microformats.org/wiki/h-review\n* syndication: h-feed publishing/consuming growing rapidly. microformats.org/wiki/h-feed\n* music playlists still unsolved for any cross-site/service use-cases\n\nBlogged 15 years ago:\n* tantek.com/log/2004/02.html#d12t0012",
        "html": "15 years ago <a class=\"h-cassis-username\" href=\"https://twitter.com/KevinMarks\">@KevinMarks</a> &amp; I introduced #<span class=\"p-category\">microformats</span> <a class=\"h-cassis-username\" href=\"https://twitter.com/oreillymedia\">@oreillymedia</a> ETech 2004 \u201creal world semantics\u201d session, before #<span class=\"p-category\">RDFa</span> #<span class=\"p-category\">microdata</span> etc., with &lt;15k #<span class=\"p-category\">HTMLFirst</span> + inline #<span class=\"p-category\">CSS</span>+#JS: <a href=\"http://tantek.com/presentations/2004etech/realworldsemanticspres.html\">tantek.com/presentations/2004etech/realworldsemanticspres.html</a> (faster than JS-only slides)<br /><br />Previously: <a href=\"http://tantek.com/t4UY2\">tantek.com/t4UY2</a> (<a href=\"https://twitter.com/t/status/433494367601717248\">https://twitter.com/t/status/433494367601717248</a>)<br /><br />Since then:<br />* drop the (X), just HTML<br />* meta tags still web alchemy, even more bloated DRY rot<br />* h-entry superceded hAtom/hentry/rel=\"bookmark\" - <a href=\"http://microformats.org/wiki/h-entry\">microformats.org/wiki/h-entry</a><br />* recommendations: hReview still more reliable than anything from Google (<a href=\"https://aaronparecki.com/2016/12/17/8/owning-my-reviews\">https://aaronparecki.com/2016/12/17/8/owning-my-reviews</a>). Use h-review today <a href=\"http://microformats.org/wiki/h-review\">microformats.org/wiki/h-review</a><br />* syndication: h-feed publishing/consuming growing rapidly. <a href=\"http://microformats.org/wiki/h-feed\">microformats.org/wiki/h-feed</a><br />* music playlists still unsolved for any cross-site/service use-cases<br /><br />Blogged 15 years ago:<br />* <a href=\"http://tantek.com/log/2004/02.html#d12t0012\">tantek.com/log/2004/02.html#d12t0012</a>"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "note",
    "_id": "2161499",
    "_source": "1",
    "_is_read": true
}

Aaron Parecki aaronparecki.com

{
    "type": "entry",
    "published": "2019-02-06T18:36:48-05:00",
    "url": "https://aaronparecki.com/2019/02/06/17/",
    "category": [
        "indieweb"
    ],
    "photo": [
        "https://aperture-media.p3k.io/aaronparecki.com/9b60fa3b557ba24eaa2528404f8f202a1141e74e111840337c5d3fee8bc6ea59.jpg"
    ],
    "video": [
        "https://aperture-media.p3k.io/aaronparecki.com/f28d688ebf24a13ce82ae405100640a5672e365a5229c0baeaad2200fa60fbe6.quicktime"
    ],
    "content": {
        "text": "Hello from Homebrew Website Club NYC! #indieweb",
        "html": "Hello from Homebrew Website Club NYC! <a href=\"https://aaronparecki.com/tag/indieweb\">#<span class=\"p-category\">indieweb</span></a>"
    },
    "author": {
        "type": "card",
        "name": "Aaron Parecki",
        "url": "https://aaronparecki.com/",
        "photo": "https://aperture-media.p3k.io/aaronparecki.com/2b8e1668dcd9cfa6a170b3724df740695f73a15c2a825962fd0a0967ec11ecdc.jpg"
    },
    "post-type": "video",
    "_id": "2158239",
    "_source": "16",
    "_is_read": true
}

Eddie Hinkle eddiehinkle.com

{
    "type": "entry",
    "published": "2019-02-12T11:54:20-05:00",
    "url": "https://eddiehinkle.com/2019/02/12/5/rsvp/",
    "category": [
        "indieweb-meetup"
    ],
    "syndication": [
        "https://micro.blog/EddieHinkle",
        "https://twitter.com/eddiehinkle"
    ],
    "in-reply-to": [
        "https://eddiehinkle.com/2019/02/20/1/event/"
    ],
    "content": {
        "text": "I'm hosting a Virtual IndieWeb Meetup next week. Want to talk about things you've recently done with your website or brainstorm ideas about what you want to do next with it. Come join us for a friendly night about your presence on the internet.",
        "html": "I'm hosting a Virtual IndieWeb Meetup next week. Want to talk about things you've recently done with your website or brainstorm ideas about what you want to do next with it. Come <a href=\"https://eddiehinkle.com/2019/02/20/1/event/\">join us</a> for a friendly night about your presence on the internet."
    },
    "author": {
        "type": "card",
        "name": "Eddie Hinkle",
        "url": "https://eddiehinkle.com/",
        "photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
    },
    "post-type": "reply",
    "_id": "2153070",
    "_source": "226",
    "_is_read": true
}

gRegor Morrill gregorlove.com

{
    "type": "entry",
    "published": "2019-02-11 13:46-0800",
    "url": "https://gregorlove.com/2019/02/hey-david-are-you-still/",
    "syndication": [
        "https://twitter.com/gRegorLove/status/1095076753310183424"
    ],
    "content": {
        "text": "@davemillar Hey, David, are you still planning on coming to IndieWebCamp Austin? Would be great to see you there! https://2019.indieweb.org/austin",
        "html": "<p>@davemillar Hey, David, are you still planning on coming to IndieWebCamp Austin? Would be great to see you there! <a href=\"https://2019.indieweb.org/austin\">https://2019.indieweb.org/austin</a></p>"
    },
    "author": {
        "type": "card",
        "name": "gRegor Morrill",
        "url": "https://gregorlove.com/",
        "photo": "https://aperture-proxy.p3k.io/929c8777d059069a2a16a064d96f4c29b65548f8/68747470733a2f2f677265676f726c6f76652e636f6d2f736974652f6173736574732f66696c65732f333437332f70726f66696c652d323031362d6d65642e6a7067"
    },
    "post-type": "note",
    "_id": "2142290",
    "_source": "95",
    "_is_read": true
}

A journey to the underworld that is RDF

{
    "type": "entry",
    "author": {
        "name": "mail@petermolnar.net (Peter Molnar)",
        "url": "https://petermolnar.net/feed/",
        "photo": null
    },
    "url": "https://petermolnar.net/web-of-the-machines/",
    "published": "2019-02-10T20:10:00+00:00",
    "content": {
        "html": "<img src=\"https://aperture-proxy.p3k.io/8bd62c333e30a6b45914afd4cc43b3912857b305/68747470733a2f2f70657465726d6f6c6e61722e6e65742f666565642f7264662d69742d646f65732d6e6f742d737061726b2d6a6f792e6a7067\" alt=\"working with RDF - this one does not spark joy\" />working with RDF - this one does not spark joy<p>I want to say it all started with a rather offensive tweet<a href=\"https://petermolnar.net/feed/#fn1\">1</a>, but it wouldn\u2019t be true. No, it all started with my curiosity to please the Google Structured Data testing tool<a href=\"https://petermolnar.net/feed/#fn2\">2</a>. Last year, in August, I added microdata<a href=\"https://petermolnar.net/feed/#fn3\">3</a> to my website - it was more or less straightforward to do so.</p>\n<p>Except it was ugly, and, after half a year, I\u2019m certain to say, quite useless. I got no pretty Google cards - maybe because I refuse to do AMP<a href=\"https://petermolnar.net/feed/#fn4\">4</a>, maybe because I\u2019m not important enough, who knows. But by the time I was reaching this conclusion, that aforementioned tweet happened, and I got caught up in Semantic Hell, also known as arguing about RDF.</p>\n<p>The first time I heard about the Semantic Web collided with the dawn of the web 2.0 hype, so it wasn\u2019t hard to dismiss it when so much was happening. I was rather new to the whole web thing, and most of the academic discussions were not even available in Hungarian.</p>\n<p>In that thread, it pointed out to me that what I have on my site is microdata, not RDFa - I genuinely thought they are more or less interchangeable: both can use the same vocabulary, so it shouldn\u2019t really matter which HTML properties I use, should it? Well, it does, but I believe the basis for my confusion can be found in the microdata description: it was an initiative to make RDF simple enough for people making websites.</p>\n<p>If you\u2019re just as confused as I was, in my own words:</p>\n<ul><li><strong>RDF</strong> is a ruleset framework, which is <strong>only used to describe sets of rules</strong></li>\n<li>these rules are named <strong>vocabularies</strong>: Schema.org, Dublin Core, Open Graph (<em>the not-invented-here is strong in Facebook</em>), FOAF (<em>for the sake of your own sanity, don\u2019t read the FOAF doc, unless you already know how to greet Shub-Niggurath or what geekcode is/was</em>), etc</li>\n<li>if you try to use multiple vocabularies at once - which you can -, it will be incredibly hard to remember when to use what</li>\n<li>a vocabulary is what you can actually add to your data - machines then go to the RDF definition of the vocabulary make databases out of the data</li>\n<li><strong>microdata</strong> is <code>itemprop</code>, <code>itemscope</code>, <code>itemtype</code> and <code>itemref</code> HTML5 attributes</li>\n<li>whereas <strong>RDFa</strong> is <code>vocab</code>, <code>typeof</code>, <code>property</code> HTML5 attributes</li>\n<li>if you want to please academics or some sort of internal tool that is built to utlize RDF, use RDFa - I keep asking if RDFa vocabularies, such as Dublin Core, are consumed by anything on the public internet, but I keep getting answers<a href=\"https://petermolnar.net/feed/#fn5\">5</a> with no actual answers</li>\n<li>if you\u2019re doing this for a search engine, stick to microdata, it\u2019s less prone to errors\u2026</li>\n<li>.. or just do <strong>JSON-LD</strong>, which is JSON with special keys: <code>@context</code>, which points to a vocabulary, and <code>@type</code>, which points you to a vocabulary element, and these two define what your data keys should be named and what kind of data they might contain</li>\n</ul><p>With all this now known, I tried to turn mark up my content as microformats v1, microformats v2, and RDFa.</p>\n<p>I already had errors with microdata\u2026</p>\n<a href=\"https://petermolnar.net/web-of-the-machines/gsdtt_microdata_error_01_b.png\"> <img src=\"https://aperture-proxy.p3k.io/ac2aee208cce936e718df92f11e04a4e38a3c059/68747470733a2f2f70657465726d6f6c6e61722e6e65742f7765622d6f662d7468652d6d616368696e65732f67736474745f6d6963726f646174615f6572726f725f30312e706e67\" title=\"gsdtt_microdata_error_01\" alt=\"gsdtt_microdata_error_01\" /></a>\n\nInteresting, it has some problems\u2026\n<a href=\"https://petermolnar.net/web-of-the-machines/gsdtt_microdata_error_02_b.png\"> <img src=\"https://aperture-proxy.p3k.io/370f10a7e762e6ccaf4328b04e30a76b1225a8cb/68747470733a2f2f70657465726d6f6c6e61722e6e65742f7765622d6f662d7468652d6d616368696e65732f67736474745f6d6963726f646174615f6572726f725f30322e706e67\" title=\"gsdtt_microdata_error_02\" alt=\"gsdtt_microdata_error_02\" /></a>\n\nit says URL for org is missing\u2026 it\u2019s there. Line 13.\n<p>\u2026but those errors then became ever more peculiar problems with RDFa\u2026</p>\n<a href=\"https://petermolnar.net/web-of-the-machines/gsdtt_rdfa_error_01_b.png\"> <img src=\"https://aperture-proxy.p3k.io/2607fbcfb0443d64c6e219c30c26bc397bf8276c/68747470733a2f2f70657465726d6f6c6e61722e6e65742f7765622d6f662d7468652d6d616368696e65732f67736474745f726466615f6572726f725f30312e706e67\" title=\"gsdtt_rdfa_error_01\" alt=\"gsdtt_rdfa_error_01\" /></a>\n\nUndefined type, eh?\n<a href=\"https://petermolnar.net/web-of-the-machines/gsdtt_rdfa_error_02_b.png\"> <img src=\"https://aperture-proxy.p3k.io/c8a01ebee0bdc161376d425b7fe921e926836a27/68747470733a2f2f70657465726d6f6c6e61722e6e65742f7765622d6f662d7468652d6d616368696e65732f67736474745f726466615f6572726f725f30322e706e67\" title=\"gsdtt_rdfa_error_02\" alt=\"gsdtt_rdfa_error_02\" /></a>\n\nwat\n<p>\u2026 while microformats v1 was parsed without any glitches. <em>Sidenote: <strong>microformats</strong> (v1 and v2), unlike the previous things, are extra HTML <code>class</code> data, and v1 is still parsed by most search engines.</em></p>\n<p><strong>At this point I gave up on RDFa and moved over to test JSON-LD.</strong></p>\n<p>It\u2019s surprisingly easy to represent data in JSON-LD with schema.org context (<em>vocabulary, why on earth was vocabulary renamed to context?! Oh. Because we\u2019re in hell.</em>). There\u2019s a long entry about why JSON-LD happened<a href=\"https://petermolnar.net/feed/#fn6\">6</a> and it has a lot of reasonable points.</p>\n<p>What it forgets to talk about is that JSON-LD is an invisible duplication of what is either already or what should be in HTML. It\u2019s a decent way to store data, to exchange data, but not to present it to someone on the other end of the cable.</p>\n<p>The most common JSON-LD vocabulary, Schema.org has it\u2019s own interesting world of problems. It wants to be a single point of entry, one gigantic vocabulary, for anything web, a humongous task and noble goal. However, it\u2019s still lacking a lot of definitions (<em>ever tried to represent a resume with it?</em>), it has weird quirks (<em>\u2018follows\u2019 on a Person can only be another Person, it can\u2019t be a Brand, a WebSite, or a simple URL</em>) and it\u2019s driven heavily by Google (<em>most people working on it are working at Google</em>).</p>\n<p>I ended up with compromises.</p>\n<pre><code>&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\u2019t know if Google will consume the JSON-LD alternate format, but it\u2019s there, any anyone can easily use it.</p>\n<p>As for RDFa, I turned to <code>meta</code> elements. Unlike with JSON-LD, I decided to use the extremely simple vocabulary of Open Graph - at least Facebook is known to consume that.</p>\n<p><strong>The tragedy of this whole story: HTML5 has so many tags that is should be possible to do structured data without any need for any of the things above.</strong></p>\n<p>My content is now:</p>\n<ul><li>microformats v1 and v2 within the visible content</li>\n<li>a minimal RDFa in <code>meta</code> tags</li>\n<li>a sidecar JSON-LD version</li>\n</ul><p>This way it\u2019s simple, but compatible enough for most cases.</p>\n\n\n<ol><li><p><a href=\"https://twitter.com/csarven/status/1091314310465421312\">https://twitter.com/csarven/status/1091314310465421312</a><a href=\"https://petermolnar.net/feed/#fnref1\">\u21a9</a></p></li>\n<li><p><a href=\"https://search.google.com/structured-data/testing-tool\">https://search.google.com/structured-data/testing-tool</a><a href=\"https://petermolnar.net/feed/#fnref2\">\u21a9</a></p></li>\n<li><p><a href=\"https://twitter.com/csarven/status/1091314310465421312\">https://twitter.com/csarven/status/1091314310465421312</a><a href=\"https://petermolnar.net/feed/#fnref3\">\u21a9</a></p></li>\n<li><p><a href=\"https://www.ampproject.org/\">https://www.ampproject.org/</a><a href=\"https://petermolnar.net/feed/#fnref4\">\u21a9</a></p></li>\n<li><p><a href=\"https://twitter.com/RubenVerborgh/status/1092029740364587008\">https://twitter.com/RubenVerborgh/status/1092029740364587008</a><a href=\"https://petermolnar.net/feed/#fnref5\">\u21a9</a></p></li>\n<li><p><a href=\"http://manu.sporny.org/2014/json-ld-origins-2/\">http://manu.sporny.org/2014/json-ld-origins-2/</a><a href=\"https://petermolnar.net/feed/#fnref6\">\u21a9</a></p></li>\n</ol>",
        "text": "working with RDF - this one does not spark joyI want to say it all started with a rather offensive tweet1, but it wouldn\u2019t be true. No, it all started with my curiosity to please the Google Structured Data testing tool2. Last year, in August, I added microdata3 to my website - it was more or less straightforward to do so.\nExcept it was ugly, and, after half a year, I\u2019m certain to say, quite useless. I got no pretty Google cards - maybe because I refuse to do AMP4, maybe because I\u2019m not important enough, who knows. But by the time I was reaching this conclusion, that aforementioned tweet happened, and I got caught up in Semantic Hell, also known as arguing about RDF.\nThe first time I heard about the Semantic Web collided with the dawn of the web 2.0 hype, so it wasn\u2019t hard to dismiss it when so much was happening. I was rather new to the whole web thing, and most of the academic discussions were not even available in Hungarian.\nIn that thread, it pointed out to me that what I have on my site is microdata, not RDFa - I genuinely thought they are more or less interchangeable: both can use the same vocabulary, so it shouldn\u2019t really matter which HTML properties I use, should it? Well, it does, but I believe the basis for my confusion can be found in the microdata description: it was an initiative to make RDF simple enough for people making websites.\nIf you\u2019re just as confused as I was, in my own words:\nRDF is a ruleset framework, which is only used to describe sets of rules\nthese rules are named vocabularies: Schema.org, Dublin Core, Open Graph (the not-invented-here is strong in Facebook), FOAF (for the sake of your own sanity, don\u2019t read the FOAF doc, unless you already know how to greet Shub-Niggurath or what geekcode is/was), etc\nif you try to use multiple vocabularies at once - which you can -, it will be incredibly hard to remember when to use what\na vocabulary is what you can actually add to your data - machines then go to the RDF definition of the vocabulary make databases out of the data\nmicrodata is itemprop, itemscope, itemtype and itemref HTML5 attributes\nwhereas RDFa is vocab, typeof, property HTML5 attributes\nif you want to please academics or some sort of internal tool that is built to utlize RDF, use RDFa - I keep asking if RDFa vocabularies, such as Dublin Core, are consumed by anything on the public internet, but I keep getting answers5 with no actual answers\nif you\u2019re doing this for a search engine, stick to microdata, it\u2019s less prone to errors\u2026\n.. or just do JSON-LD, which is JSON with special keys: @context, which points to a vocabulary, and @type, which points you to a vocabulary element, and these two define what your data keys should be named and what kind of data they might contain\nWith all this now known, I tried to turn mark up my content as microformats v1, microformats v2, and RDFa.\nI already had errors with microdata\u2026\n \n\nInteresting, it has some problems\u2026\n \n\nit says URL for org is missing\u2026 it\u2019s there. Line 13.\n\u2026but those errors then became ever more peculiar problems with RDFa\u2026\n \n\nUndefined type, eh?\n \n\nwat\n\u2026 while microformats v1 was parsed without any glitches. Sidenote: microformats (v1 and v2), unlike the previous things, are extra HTML class data, and v1 is still parsed by most search engines.\nAt this point I gave up on RDFa and moved over to test JSON-LD.\nIt\u2019s surprisingly easy to represent data in JSON-LD with schema.org context (vocabulary, why on earth was vocabulary renamed to context?! Oh. Because we\u2019re in hell.). There\u2019s a long entry about why JSON-LD happened6 and it has a lot of reasonable points.\nWhat it forgets to talk about is that JSON-LD is an invisible duplication of what is either already or what should be in HTML. It\u2019s a decent way to store data, to exchange data, but not to present it to someone on the other end of the cable.\nThe most common JSON-LD vocabulary, Schema.org has it\u2019s own interesting world of problems. It wants to be a single point of entry, one gigantic vocabulary, for anything web, a humongous task and noble goal. However, it\u2019s still lacking a lot of definitions (ever tried to represent a resume with it?), it has weird quirks (\u2018follows\u2019 on a Person can only be another Person, it can\u2019t be a Brand, a WebSite, or a simple URL) and it\u2019s driven heavily by Google (most people working on it are working at Google).\nI ended up with compromises.\n<html lang=\"en\"  prefix=\"og: http://ogp.me/ns# article: http://ogp.me/ns/article#\">\n<head>\n    <title>A piece of Powerscourt Waterfall - petermolnar.net</title>\n<!-- JSON-LD as alternative -->\n    <link rel=\"alternate\" type=\"application/json\" title=\"a-piece-of-powerscourt-waterfall JSON-LD\" href=\"https://petermolnar.net/a-piece-of-powerscourt-waterfall/index.json\" />\n<!-- Open Graph vocabulary RDFa -->\n    <meta property=\"og:title\" content=\"A piece of Powerscourt Waterfall\" />\n    <meta property=\"og:type\" content=\"article\" />\n    <meta property=\"og:url\" content=\"https://petermolnar.net/a-piece-of-powerscourt-waterfall/\" />\n    <meta property=\"og:description\" content=\"\" />\n    <meta property=\"article:published_time\" content=\"2017-11-09T18:00:00+00:00\" />\n    <meta property=\"article:modified_time\" content=\"2019-01-05T11:52:47.543053+00:00\" />\n    <meta property=\"article:author\" content=\"Peter Molnar (mail@petermolnar.net)\" />\n    <meta property=\"og:image\" content=\"https://petermolnar.net/a-piece-of-powerscourt-waterfall/a-piece-of-powerscourt-waterfall_b.jpg\" />\n    <meta property=\"og:image:type\" content=\"image/jpeg\" />\n    <meta property=\"og:image:width\" content=\"1280\" />\n    <meta property=\"og:image:height\" content=\"847\" />\n<!-- the rest of meta and header elements -->\n<!-- followed by the content, with microformats v1 and v2 markup -->\nHTML provides an interesting functionality, the rel=alternate. This is meant to be the representation of the same data, but in another format. The most common use is links to RSS and Atom feeds.\nI don\u2019t know if Google will consume the JSON-LD alternate format, but it\u2019s there, any anyone can easily use it.\nAs for RDFa, I turned to meta elements. Unlike with JSON-LD, I decided to use the extremely simple vocabulary of Open Graph - at least Facebook is known to consume that.\nThe tragedy of this whole story: HTML5 has so many tags that is should be possible to do structured data without any need for any of the things above.\nMy content is now:\nmicroformats v1 and v2 within the visible content\na minimal RDFa in meta tags\na sidecar JSON-LD version\nThis way it\u2019s simple, but compatible enough for most cases.\n\n\nhttps://twitter.com/csarven/status/1091314310465421312\u21a9\nhttps://search.google.com/structured-data/testing-tool\u21a9\nhttps://twitter.com/csarven/status/1091314310465421312\u21a9\nhttps://www.ampproject.org/\u21a9\nhttps://twitter.com/RubenVerborgh/status/1092029740364587008\u21a9\nhttp://manu.sporny.org/2014/json-ld-origins-2/\u21a9"
    },
    "name": "A journey to the underworld that is RDF",
    "post-type": "article",
    "_id": "2123955",
    "_source": "268",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2019-02-10T14:02:26-05:00",
    "url": "https://miklb.com/blog/2019/02/10/4719/",
    "syndication": [
        "https://twitter.com/miklb/status/1094672976925069312"
    ],
    "content": {
        "text": "Just had a thought. I know you can run arbitrary Jekyll plugins in a GitHub action\u2013I bet you can send/receive webmentions too!",
        "html": "<p>Just had a thought. I know you can run arbitrary Jekyll plugins in a GitHub action\u2013I bet you can send/receive webmentions too!\n</p>"
    },
    "post-type": "note",
    "_id": "2123080",
    "_source": "42",
    "_is_read": true
}

Jeremy Keith adactio.com

{
    "type": "entry",
    "published": "2019-02-09T17:24:41Z",
    "url": "https://adactio.com/links/14780",
    "category": [
        "fansites",
        "webrings",
        "fun",
        "enjoyment",
        "making",
        "creating",
        "sharing",
        "publishing",
        "indieweb"
    ],
    "bookmark-of": [
        "https://bryanlrobinson.com/blog/2019/02/07/bring-fansites-back-to-the-web/"
    ],
    "content": {
        "text": "Let\u2019s bring Fan Sites and webrings back! - bryanlrobinson.com\n\n\n\n\n  As the commercial viability of the web grew, we saw more and more users become consumers and not creators. Many consumers see websites as black boxes full of magic that they could never understand. Because of this, they would never think to try to create something.\n  \n  This is a shame. We lost a little piece of the magic of the web when this culture came about.\n\n\nA call to action to create a fan site about something you love. It would be an unmonetisable enthusiasm. But it\u2019s still worth doing:\n\n\n  The act of creation itself is fun!\n  Sharing something you love with the world is worthwhile.\n  You\u2019ll learn something.\n  \n\nSo here\u2019s the challenge:\n\n\n  Create a Fan Site.\n  Help someone create a Fan Site.\n  Create a webring.",
        "html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://bryanlrobinson.com/blog/2019/02/07/bring-fansites-back-to-the-web/\">\nLet\u2019s bring Fan Sites and webrings back! - bryanlrobinson.com\n</a>\n</h3>\n\n<blockquote>\n  <p>As the commercial viability of the web grew, we saw more and more users become consumers and not creators. Many consumers see websites as black boxes full of magic that they could never understand. Because of this, they would never think to try to create something.</p>\n  \n  <p>This is a shame. We lost a little piece of the magic of the web when this culture came about.</p>\n</blockquote>\n\n<p>A call to action to create a fan site about something you love. It would be an <a href=\"https://www.wired.co.uk/article/obsessive-depth-of-the-internet\">unmonetisable enthusiasm</a>. But it\u2019s still worth doing:</p>\n\n<blockquote>\n  <ol><li>The act of creation itself is fun!</li>\n  <li>Sharing something you love with the world is worthwhile.</li>\n  <li>You\u2019ll learn something.</li>\n  </ol></blockquote>\n\n<p>So here\u2019s the challenge:</p>\n\n<blockquote>\n  <ol><li>Create a Fan Site.</li>\n  <li>Help someone create a Fan Site.</li>\n  <li>Create a webring.</li>\n  </ol></blockquote>"
    },
    "author": {
        "type": "card",
        "name": "Jeremy Keith",
        "url": "https://adactio.com/",
        "photo": "https://aperture-proxy.p3k.io/bbbacdf0a064621004f2ce9026a1202a5f3433e0/68747470733a2f2f6164616374696f2e636f6d2f696d616765732f70686f746f2d3135302e6a7067"
    },
    "post-type": "bookmark",
    "_id": "2112084",
    "_source": "2",
    "_is_read": true
}