{
    "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/01/09/homebrew-website-club.html",
    "content": {
        "html": "<p>Homebrew Website Club is tonight in Austin! 6:30pm at Mozart\u2019s Coffee. Join us for a coffee and chat about the IndieWeb and plans for IndieWebCamp Austin. (Which will be February 23-24\u2026 Registration open soon.)</p>",
        "text": "Homebrew Website Club is tonight in Austin! 6:30pm at Mozart\u2019s Coffee. Join us for a coffee and chat about the IndieWeb and plans for IndieWebCamp Austin. (Which will be February 23-24\u2026 Registration open soon.)"
    },
    "published": "2019-01-09T13:54:34-06:00",
    "post-type": "note",
    "_id": "1775095",
    "_source": "12",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2019-01-08 23:16-0800",
    "url": "http://tantek.com/2019/008/t1/re-activate-flickr-pro",
    "content": {
        "text": "Decided to re-activate my @Flickr Pro.\nNew owner @SmugMug has been around for years and is passionate about photos. They\u2019ve responded well to criticisms & suggestions (preserving CC photos). @DonMacAskill did an AMA recently that showed a lot of care and thoughtfulness: https://www.reddit.com/r/photography/comments/a71mh3/hi_my_name_is_don_macaskill_and_im_the_cofounder/\n\nOne example: \u201cWe are actively saving accounts for photographers who are no longer with us\u201d.\n\nDear @Flickr, here are a few more to save. I lost a good friend last year (flic.kr/cindyli @CindyLi enwp.org/Cindy_Li), another the year before (flic.kr/bmindful @tedr), and another years ago (flic.kr/thebrad). I\u2019m sure there are many more early Flickr users who have since passed away. Please speak-up if you know of any.\n\nFlickr already has the best API of any photo site, and thus has the best Brid.gy support for IndieWeb sites wanting to syndicate to Flickr, and backfeed responses.\n\nI have more positive thoughts about @Flickr\u2019s future potential with its new owners, especially with respect to even better IndieWeb integration. \u00a0More on that later. For now, see the additional research and links being collected and documented by the IndieWeb Community:\n\nhttps://indieweb.org/Flickr\n\nAnd if you also decide to upgrade your Flickr account to Pro, there\u2019s a 15% off code (FLICKRPRO15) that\u2019s good until 2019-015.",
        "html": "Decided to re-activate my <a class=\"h-cassis-username\" href=\"https://twitter.com/Flickr\">@Flickr</a> Pro.<br />New owner <a class=\"h-cassis-username\" href=\"https://twitter.com/SmugMug\">@SmugMug</a> has been around for years and is passionate about photos. They\u2019ve responded well to criticisms &amp; suggestions (preserving CC photos). <a class=\"h-cassis-username\" href=\"https://twitter.com/DonMacAskill\">@DonMacAskill</a> did an AMA recently that showed a lot of care and thoughtfulness: <a href=\"https://www.reddit.com/r/photography/comments/a71mh3/hi_my_name_is_don_macaskill_and_im_the_cofounder/\">https://www.reddit.com/r/photography/comments/a71mh3/hi_my_name_is_don_macaskill_and_im_the_cofounder/</a><br /><br />One example: \u201cWe are actively saving accounts for photographers who are no longer with us\u201d.<br /><br />Dear <a class=\"h-cassis-username\" href=\"https://twitter.com/Flickr\">@Flickr</a>, here are a few more to save. I lost a good friend last year (<a href=\"http://flic.kr/cindyli\">flic.kr/cindyli</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/CindyLi\">@CindyLi</a> <a href=\"http://enwp.org/Cindy_Li\">enwp.org/Cindy_Li</a>), another the year before (<a href=\"http://flic.kr/bmindful\">flic.kr/bmindful</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/tedr\">@tedr</a>), and another years ago (<a href=\"http://flic.kr/thebrad\">flic.kr/thebrad</a>). I\u2019m sure there are many more early Flickr users who have since passed away. Please speak-up if you know of any.<br /><br />Flickr already has the best API of any photo site, and thus has the best <a href=\"http://Brid.gy\">Brid.gy</a> support for IndieWeb sites wanting to syndicate to Flickr, and backfeed responses.<br /><br />I have more positive thoughts about <a class=\"h-cassis-username\" href=\"https://twitter.com/Flickr\">@Flickr</a>\u2019s future potential with its new owners, especially with respect to even better IndieWeb integration. \u00a0More on that later. For now, see the additional research and links being collected and documented by the IndieWeb Community:<br /><br /><a href=\"https://indieweb.org/Flickr\">https://indieweb.org/Flickr</a><br /><br />And if you also decide to upgrade your Flickr account to Pro, there\u2019s a 15% off code (FLICKRPRO15) that\u2019s good until 2019-015."
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "note",
    "_id": "1770051",
    "_source": "1",
    "_is_read": true
}

zwanzigachtzehn

{
    "type": "entry",
    "published": "2019-01-08T20:40:38+00:00",
    "url": "https://notiz.blog/2019/01/08/zwanzigachtzehn/",
    "featured": "https://notiz.blog/wp-content/uploads/2019/01/rip-2018-900x274.png",
    "name": "zwanzigachtzehn",
    "content": {
        "text": "2018 war ein durchwachsenes Jahr!\n\n\n\nMein privates \u201eIch\u201c hat letztes Jahr sehr viel Raum eingenommen und auch beruflich hat sich viel ver\u00e4ndert.\n\n\n\nDas hei\u00dft ich hatte generell wenig Zeit f\u00fcr mein online \u201eIch\u201c und wenn ich doch etwas Zeit hatte, war das Ergebnis meistens eher frustrierend.\n\n\n\nPfefferles OpenWeb\n\n\n\nIch habe f\u00fcr das SCREENGUIDE/Webstandards-Magazin in den letzten 10 Jahren 36 mal \u201ePfefferles OpenWeb\u201c, 3 Artikel, 1 Titelthema und 1 Interview geschrieben! Letztes Jahr musste der Verlag das Magazin aus \u201ewirtschaftlichen Gr\u00fcnden\u201c leider einstellen und ich hab es nicht einmal geschafft dar\u00fcber zu schreiben!\n\n\n\nnotiz.Blog\n\n\n\nIch hab es nicht mal geschafft die gewonnene freie Zeit mit bloggen zu verbringen! Wenn ich dieses Jahr so weiter mache, muss ich mir meinen selbstvergebenen Titel als \u201eChronist des OpenWebs\u201c wieder selbst aberkennen!\n\n\n\n\nIndieWeb\n\n\n\nDas IndieWeb w\u00e4chst und das ist prinzipiell auch gut so. Neben den ganzen Nerds und Geeks interessieren sich auch immer mehr Blogger und Journalisten f\u00fcr das Thema. In der Community spricht man von der 2. Generation.\n\n\n\nAuch das Interesse an WordPress w\u00e4chst. Das ist nicht verwunderlich, immerhin geht es um die Berufsgruppe der Schreibenden und deren Seiten werden, mit einer Wahrscheinlichkeit von 30%, mit WordPress betrieben.\n\n\n\nDieses Interesse bei\u00dft sich aber leider mit meinen M\u00f6glichkeiten. Von Anfang an verfolge ich folgende Grunds\u00e4tze des IndieWebs:\n\n\n\n\nScratch Your Own Itches. Make tools, templates, etc. for yourself first, not for all of your friends or \u201deveryone\u201c.\n\n\n\n\n\nund:\n\n\n\n\nUse what you make! Whatever you build you should actively use. If you aren\u2019t depending on it, why should anybody else?\n\n\n\n\n\nIch baue (mittlerweile) ausschlie\u00dflich Plugins die ich f\u00fcr sinnvoll erachte und ich baue sie so, dass sie f\u00fcr mich funktionieren. Das mag erstmal egoistisch klingen, es ist f\u00fcr mich aber die einzige M\u00f6glichkeit dieses \u201eHobby\u201c \u00fcberhaupt zu betreiben.\n\n\n\nIch verstehe, dass Anwender teilweise \u00fcberfordert sind, meine Plugins zu benutzen, kann sie aber nicht in dem Umfang optimieren, der n\u00f6tig w\u00e4re. Ideal ist wahrscheinlich ein gro\u00dfes IndieWeb Plugin, welches alle Features bereit stellt und, am besten ohne viel Einstellungen, einfach funktioniert. Aktuell nutze ich 50% aller, vom IndieWeb vorgeschlagenen WordPress Plugins, eine allumfassende Plugin Suite w\u00fcrde dann also nicht mehr meinen Anforderungen entsprechen.\n\n\n\nIch habe aktuell keine Ahnung wie ich aus diesem Dilemma heraus kommen soll. Es gibt Plugins die will ich nicht aus der Hand geben und Plugins die ich an die Community \u00fcbergeben habe, werden aus Mangel an Entwicklern nicht weiter gepflegt. Aktuell arbeiten maximal 3 Personen (mich inbegriffen) an \u00fcber 10 unterschiedlichen Plugins.\n\n\n\n\u2026und wenn das noch nicht genug w\u00e4re, kommt das \u201eMicroformats Problem\u201c noch on top.\n\n\n\n\nMicroformats\n\n\n\nMicroformats2 und WordPress scheinen nicht kompatibel zu sein und das ist schade, immerhin sind Microformats DER Building-Block des IndieWebs. Mehr noch: Microformats sind die API des IndieWebs!\n\n\n\nIch habe in den letzten Jahren viel ausprobiert um das Problem zu l\u00f6sen, aber es gibt keine generische M\u00f6glichkeit, ein WordPress Theme mit Microformats2 auszustatten.\n\n\n\nBenutzt man ein Plugin, um \u00fcber Hooks einige zentrale Elemente (wie z.B. den Titel) Semantisch auszuzeichnen, bekommt man nette Effekte, mit Themes die ihre Ausgabe \u201eescapen\u201c:\n\n\n\nAfter activating the last version (1.1.0) of your plugin on WordPress 4.9.8 with understrap theme my meta entry become : Posted on September 12, 2018 by <span class='p-author h-card'>Author</span> instead of :  Posted on September 12, 2018 by Author for fun I look into the code and I think the error is here but since I\u2019m totally not a PHP developer I\u2019ll pass on the potential PR\n\n\n\nVersucht man es mit einer Art Microformats Feed, bekommt man Probleme, alle Meta-Daten zu integrieren. Schlimmer noch, man arbeitet gegen einen Grundsatz der Microformats:\n\n\n\nDesign for humans first, machines second\n\n\n\nZusammengefasst: Microformats geh\u00f6ren ins Theme, es gibt aber keine generische L\u00f6sung. Eine generische API ist m\u00f6glich, widerspricht aber der Microformats-Idee.\n\n\n\nAktuell gibt es drei WordPress Themes die Microformats2 voll unterst\u00fctzen und um sein Blog wirklich IndieWeb tauglich zu machen, muss man eines dieser drei Themes benutzen oder selber HTML bzw. ein Theme schreiben.\n\n\n\nDas ist frustrierend! Au\u00dferdem liefen die Diskussionen (meines Erachtens) etwas aus dem Ruder, weshalb ich mich letztes Jahr entschieden habe, mich aus dem Microformats-Thema komplett heraus zu nehmen.\n\n\n\nOStatus\n\n\n\nOStatus ist das zentrale Protokoll, \u00fcber das identi.ca, status.net, gnu.social und friendi.ca sprechen. Es ist arsch-alt, funktioniert aber immer noch pr\u00e4chtig!\n\n\n\nIch hab mich wie bolle gefreut als OStatus mit Mastodon wieder frischen Wind bekam, hab mein altes OStatus Plugin ein wenig aufpoliert und wollte gerade freudig dar\u00fcber berichten, als Eugen Rochko, der Macher hinter Mastodon, einen meiner Bugs, mit folgenden Worten schloss:\n\n\n\nClosing on the grounds that OStatus is no longer our primary mechanism and will be deprecated in the future.\n\n\n\nMein vorbereiteter Blogpost hatte den Titel \u201eMy Blog is my Social-Network\u201c und der erste Abschnitt lautete:\n\n\n\nIch habe in den letzte Woche an einem Update f\u00fcr ein WordPress Plugin gearbeitet, das ich seit 6 Jahren nicht anger\u00fchrt habe\u2026 Nicht dass das Plugin an sich nicht mehr funktioniert h\u00e4tte, aber PHP und WordPress haben sich weiter entwickelt.\n\n\n\nSchade!\n\n\n\nActivityPub\n\n\n\nAber dann kam ActivityPub! ActivityPub ist der hei\u00dfe Shit im Fediverse. So zu sagen OStatus in neu und besser! Was AtomPub f\u00fcr Atom ist, ist ActivityPub f\u00fcr ActivityStreams\u2026 und noch ein bisschen mehr.\n\n\n\nActivityPub ist au\u00dferdem der erste, vom W3C ver\u00f6ffentlicht, \u201eStandard\u201c (abh\u00e4ngig davon wie man \u201eStandard\u201c definiert), der versucht ein dezentrales, soziales Netzwerke zu definieren.\n\n\n\nNaiv wie ich bin, dachte ich, ich geb\u2018 dem Ganzen eine Chance. Die Spezifikation ist relativ simpel und ein \u201eStandard\u201c ist \u201ewohl definiert\u201c, das hei\u00dft es gibt nur einen Weg um ihn zu implementieren!\n\n\n\nDas Ergebnis (Trommelwirbel): ein ActivityPub Plugin f\u00fcr WordPress!\n\n\n\nWar es so einfach wie ich gedacht habe? Nat\u00fcrlich nicht! Es hat nat\u00fcrlich doch wieder jede Plattform seine extra Wurst, aber im Gegensatz zu Microformats2, basiert ActivityPub auf einer \u201eechten\u201c API und l\u00e4sst sich somit relativ leicht in WordPress integrieren.\n\n\n\nActivityPub und das Plugin waren definitiv das Highlight des Jahres, immerhin ist WordPress jetzt offiziell ein Teil des Fediverse:\n\n\n\nhttps://fediverse.network/wordpress\nhttps://the-federation.info/wordpress\nhttps://fediverse.party/en/miscellaneous/\nund laut dem \u201e2018 Report\u201c von fediverse.network sogar auf Platz 8 von 13.\n\n\n\nFazit\n\n\n\nDie Arbeit an ActivityPub hat eigentlich Spa\u00df gemacht und ich werde mich wahrscheinlich auch 2019 haupts\u00e4chlich mit ActivityPub besch\u00e4ftigen!\n\n\n\n2018 war nicht so dolle, 2019 kann nur besser werden!",
        "html": "<p>2018 war ein durchwachsenes Jahr!</p>\n\n\n\n<p>Mein privates \u201eIch\u201c hat letztes Jahr sehr viel Raum eingenommen und auch beruflich hat sich viel ver\u00e4ndert.</p>\n\n\n\n<p>Das hei\u00dft ich hatte generell wenig Zeit f\u00fcr mein online \u201eIch\u201c und wenn ich doch etwas Zeit hatte, war das Ergebnis meistens eher frustrierend.</p>\n\n\n\n<h2>Pfefferles OpenWeb</h2>\n\n\n\n<img src=\"https://aperture-proxy.p3k.io/bd34c4cfc1d870119b3d858fa41f3104354ad8b0/68747470733a2f2f6e6f74697a2e626c6f672f77702d636f6e74656e742f75706c6f6164732f323031382f30312f73637265656e67756964652d6b6f6c756d6e652d393030783630302e6a7067\" alt=\"Bilder von &quot;Pfefferles OpenWeb&quot; Artikeln\" /><p>Ich habe f\u00fcr das SCREENGUIDE/Webstandards-Magazin in den letzten 10 Jahren 36 mal \u201ePfefferles OpenWeb\u201c, 3 Artikel, 1 Titelthema und 1 Interview geschrieben! Letztes Jahr musste der Verlag das Magazin aus \u201ewirtschaftlichen Gr\u00fcnden\u201c leider einstellen und ich hab es nicht einmal geschafft dar\u00fcber zu schreiben!</p>\n\n\n\n<h2>notiz.Blog</h2>\n\n\n\n<p>Ich hab es nicht mal geschafft die gewonnene freie Zeit mit bloggen zu verbringen! Wenn ich dieses Jahr so weiter mache, muss ich mir meinen selbstvergebenen Titel als \u201e<em>Chronist des OpenWebs</em>\u201c wieder selbst aberkennen!<br /></p>\n\n\n\n<h2>IndieWeb</h2>\n\n\n\n<p>Das IndieWeb w\u00e4chst und das ist prinzipiell auch gut so. Neben den ganzen Nerds und Geeks interessieren sich auch immer mehr Blogger und Journalisten f\u00fcr das Thema. In der Community spricht man von der <a href=\"https://indieweb.org/generations\">2. Generation</a>.</p>\n\n\n\n<p>Auch das Interesse an WordPress w\u00e4chst. Das ist nicht verwunderlich, immerhin geht es um die Berufsgruppe der Schreibenden und deren Seiten werden, mit einer Wahrscheinlichkeit von <a href=\"https://thenextweb.com/dd/2018/03/05/30-of-the-web-now-runs-on-wordpress/\">30%</a>, mit WordPress betrieben.</p>\n\n\n\n<p>Dieses Interesse bei\u00dft sich aber leider mit meinen M\u00f6glichkeiten. Von Anfang an verfolge ich folgende <a href=\"https://indieweb.org/principles\">Grunds\u00e4tze des IndieWebs</a>:</p>\n\n\n\n<blockquote>\n<p><strong><a href=\"https://indieweb.org/scratch_your_own_itch\">Scratch Your Own Itches</a></strong>. Make tools, templates, etc. for yourself first, not for all of your friends or \u201deveryone\u201c.</p>\n<p></p>\n</blockquote>\n\n\n\n<p>und:</p>\n\n\n\n<blockquote>\n<p><strong>Use what you make!</strong> Whatever you build you should actively use. If you aren\u2019t depending on it, why should anybody else?</p>\n<p></p>\n</blockquote>\n\n\n\n<p>Ich baue (mittlerweile) ausschlie\u00dflich Plugins die ich f\u00fcr sinnvoll erachte und ich baue sie so, dass sie f\u00fcr mich funktionieren. Das mag erstmal egoistisch klingen, es ist f\u00fcr mich aber die einzige M\u00f6glichkeit dieses \u201eHobby\u201c \u00fcberhaupt zu betreiben.</p>\n\n\n\n<p>Ich verstehe, dass Anwender teilweise \u00fcberfordert sind, meine Plugins zu benutzen, kann sie aber nicht in dem Umfang optimieren, der n\u00f6tig w\u00e4re. Ideal ist wahrscheinlich ein gro\u00dfes IndieWeb Plugin, welches alle Features bereit stellt und, am besten ohne viel Einstellungen, einfach funktioniert. Aktuell nutze ich 50% aller, vom IndieWeb vorgeschlagenen WordPress Plugins, eine allumfassende Plugin Suite w\u00fcrde dann also nicht mehr meinen Anforderungen entsprechen.</p>\n\n\n\n<p>Ich habe aktuell keine Ahnung wie ich aus diesem Dilemma heraus kommen soll. Es gibt Plugins die will ich nicht aus der Hand geben und Plugins die ich an die Community \u00fcbergeben habe, werden aus Mangel an Entwicklern nicht weiter gepflegt. Aktuell arbeiten maximal 3 Personen (mich inbegriffen) an \u00fcber 10 unterschiedlichen Plugins.</p>\n\n\n\n<p>\u2026und wenn das noch nicht genug w\u00e4re, kommt das \u201eMicroformats Problem\u201c noch on top.<br /></p>\n\n\n\n<h2>Microformats</h2>\n\n\n\n<img src=\"https://aperture-proxy.p3k.io/60c4fb2466bb4eba068df1b7f13e319ba5080c99/68747470733a2f2f6e6f74697a2e626c6f672f77702d636f6e74656e742f75706c6f6164732f323030372f30332f6d662d77686974652e706e67\" alt=\"\" />\n\n\n\n<p>Microformats2 und WordPress scheinen nicht kompatibel zu sein und das ist schade, immerhin sind Microformats <strong>DER</strong> <a href=\"https://indieweb.org/Category:building-blocks\">Building-Block</a> des IndieWebs. Mehr noch: Microformats sind die API des IndieWebs!</p>\n\n\n\n<p>Ich habe in den letzten Jahren viel ausprobiert um das Problem zu l\u00f6sen, aber es gibt keine generische M\u00f6glichkeit, ein WordPress Theme mit <a href=\"http://microformats.org/wiki/microformats2\">Microformats2</a> auszustatten.</p>\n\n\n\n<p>Benutzt man ein <a href=\"https://github.com/indieweb/wordpress-uf2\">Plugin</a>, um \u00fcber Hooks einige zentrale Elemente (wie z.B. den Titel) Semantisch auszuzeichnen, bekommt man <a href=\"https://github.com/indieweb/wordpress-uf2/issues/41\">nette Effekte</a>, mit Themes die ihre Ausgabe \u201eescapen\u201c:</p>\n\n\n\n<blockquote><p>After activating the last version (1.1.0) of your plugin on WordPress 4.9.8 with understrap theme my meta entry become : <code>Posted on September 12, 2018 by &lt;span class='p-author h-card'&gt;Author&lt;/span&gt;</code> instead of : <code> Posted on September 12, 2018 by Author</code> for fun I look into the code and I think the error is here but since I\u2019m totally not a PHP developer I\u2019ll pass on the potential PR</p></blockquote>\n\n\n\n<p>Versucht man es mit einer Art <a href=\"https://github.com/indieweb/wordpress-mf2-feed\">Microformats Feed</a>, bekommt man Probleme, alle Meta-Daten zu integrieren. Schlimmer noch, man arbeitet gegen einen Grundsatz der Microformats:</p>\n\n\n\n<blockquote><p>Design for humans first, machines second</p></blockquote>\n\n\n\n<p>Zusammengefasst: Microformats geh\u00f6ren ins Theme, es gibt aber keine generische L\u00f6sung. Eine generische API ist m\u00f6glich, widerspricht aber der Microformats-Idee.</p>\n\n\n\n<p>Aktuell gibt es <a href=\"https://indieweb.org/WordPress/Themes\">drei WordPress Themes</a> die Microformats2 voll unterst\u00fctzen und um sein Blog wirklich IndieWeb tauglich zu machen, muss man eines dieser drei Themes benutzen oder selber HTML bzw. ein Theme schreiben.</p>\n\n\n\n<p>Das ist frustrierend! Au\u00dferdem liefen die Diskussionen (meines Erachtens) etwas aus dem Ruder, weshalb ich mich letztes Jahr entschieden habe, mich aus dem Microformats-Thema komplett heraus zu nehmen.</p>\n\n\n\n<h2>OStatus</h2>\n\n\n\n<p><a href=\"https://github.com/OStatus\">OStatus</a> ist das zentrale Protokoll, \u00fcber das identi.ca, status.net, gnu.social und friendi.ca sprechen. Es ist arsch-alt, funktioniert aber immer noch pr\u00e4chtig!</p>\n\n\n\n<p>Ich hab mich wie bolle gefreut als OStatus mit Mastodon wieder frischen Wind bekam, hab mein altes OStatus Plugin ein wenig aufpoliert und wollte gerade freudig dar\u00fcber berichten, als Eugen Rochko, der Macher hinter Mastodon, <a href=\"https://github.com/tootsuite/mastodon/issues/4696\">einen meiner Bugs</a>, mit folgenden Worten schloss:</p>\n\n\n\n<blockquote><p>Closing on the grounds that OStatus is no longer our primary mechanism and will be deprecated in the future.</p></blockquote>\n\n\n\n<p>Mein vorbereiteter Blogpost hatte den Titel \u201eMy Blog is my Social-Network\u201c und der erste Abschnitt lautete:</p>\n\n\n\n<blockquote><p>Ich habe in den letzte Woche an einem Update f\u00fcr ein WordPress Plugin gearbeitet, das ich seit 6 Jahren nicht anger\u00fchrt habe\u2026 Nicht dass das Plugin an sich nicht mehr funktioniert h\u00e4tte, aber PHP und WordPress haben sich weiter entwickelt.</p></blockquote>\n\n\n\n<p>Schade!</p>\n\n\n\n<h2>ActivityPub</h2>\n\n\n\n<p>Aber dann kam ActivityPub! ActivityPub ist <strong>der</strong> hei\u00dfe Shit im <a href=\"https://de.wikipedia.org/wiki/Fediverse\">Fediverse</a>. So zu sagen OStatus in neu und besser! Was <a href=\"https://tools.ietf.org/html/rfc5023\">AtomPub</a> f\u00fcr <a href=\"https://tools.ietf.org/html/rfc4287\">Atom</a> ist, ist <a href=\"https://www.w3.org/TR/activitypub/\">ActivityPub</a> f\u00fcr <a href=\"https://www.w3.org/TR/activitystreams-core/\">ActivityStreams</a>\u2026 und noch ein bisschen mehr.</p>\n\n\n\n<img src=\"https://aperture-proxy.p3k.io/50fb4c289b93660fbea2492536ebb67cd906749e/68747470733a2f2f6e6f74697a2e626c6f672f77702d636f6e74656e742f75706c6f6164732f323031392f30312f61637469766974797075622d666c6f772e706e67\" alt=\"Ein Schaubild des ActivitPub flows\" /><p>ActivityPub ist au\u00dferdem der erste, vom W3C ver\u00f6ffentlicht, \u201eStandard\u201c (abh\u00e4ngig davon wie man \u201eStandard\u201c definiert), der versucht ein dezentrales, soziales Netzwerke zu definieren.</p>\n\n\n\n<p>Naiv wie ich bin, dachte ich, ich geb\u2018 dem Ganzen eine Chance. Die Spezifikation ist relativ simpel und ein \u201eStandard\u201c ist \u201ewohl definiert\u201c, das hei\u00dft es gibt nur <strong>einen</strong> Weg um ihn zu implementieren!</p>\n\n\n\n<p>Das Ergebnis (Trommelwirbel): <a href=\"https://github.com/pfefferle/wordpress-activitypub\">ein ActivityPub Plugin f\u00fcr WordPress</a>!</p>\n\n\n\n<p>War es so einfach wie ich gedacht habe? Nat\u00fcrlich nicht! Es hat nat\u00fcrlich doch wieder jede Plattform seine extra Wurst, aber im Gegensatz zu Microformats2, basiert ActivityPub auf einer \u201eechten\u201c API und l\u00e4sst sich somit relativ leicht in WordPress integrieren.</p>\n\n\n\n<p>ActivityPub und das Plugin waren definitiv das Highlight des Jahres, immerhin ist WordPress jetzt offiziell ein Teil des Fediverse:</p>\n\n\n\n<ul><li><a href=\"https://fediverse.network/wordpress\">https://fediverse.network/wordpress</a></li>\n<li><a href=\"https://the-federation.info/wordpress\">https://the-federation.info/wordpress</a></li>\n<li><a href=\"https://fediverse.party/en/miscellaneous/\">https://fediverse.party/en/miscellaneous/</a></li>\n</ul><p>und laut dem \u201e<a href=\"https://fediverse.network/reports/2018\">2018 Report</a>\u201c von fediverse.network sogar auf Platz 8 von 13.</p>\n\n\n\n<h2>Fazit</h2>\n\n\n\n<p>Die Arbeit an ActivityPub hat eigentlich Spa\u00df gemacht und ich werde mich wahrscheinlich auch 2019 haupts\u00e4chlich mit ActivityPub besch\u00e4ftigen!</p>\n\n\n\n<p><a href=\"https://notiz.blog/2018/\">2018</a> war nicht so dolle, 2019 kann nur besser werden!<br /></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": "article",
    "_id": "1768248",
    "_source": "206",
    "_is_read": true
}

Bridgy publish should support POSSEing tag reply to Flickr

{
    "type": "entry",
    "published": "2019-01-07 13:28-0800",
    "url": "http://tantek.com/2019/007/b1/bridgy-support-tag-reply-flickr",
    "category": [
        "publish"
    ],
    "in-reply-to": [
        "https://github.com/snarfed/bridgy/issues/"
    ],
    "name": "Bridgy publish should support POSSEing tag reply to Flickr",
    "content": {
        "text": "Similar to https://github.com/snarfed/bridgy/issues/786 (but broader for any tag reply, and for Flickr instead of Facebook):\n\n\nThis is a feature request for POSSEing tag reply posts to Flickr.\n\n\nI.e. if I post a tag reply on my own site, like documented here:\n\n\nhttps://indieweb.org/tag-reply#How_to_simple_tag-reply\n\n\nwhere one (or more) of the reply-to URLs is to a Flickr permalink post (likely others's photos, but could be my own that I'm adding tags to after I published it), Bridgy Publish (of my tag reply) should propagate that tag reply to that Flickr permalink.\n\n\nThis is the publish equivalent of the following backfeed features, and may be easier to start with (consider implementing publish before implementing backfeed for equivalent interaction)\n776\n488\n\nLabels: \npublish",
        "html": "<p>\nSimilar to https://github.com/snarfed/bridgy/issues/786 (but broader for any tag reply, and for Flickr instead of Facebook):\n</p>\n<p>\nThis is a feature request for POSSEing tag reply posts to Flickr.\n</p>\n<p>\nI.e. if I post a <a href=\"https://indieweb.org/tag-reply\">tag reply</a> on my own site, like documented here:\n</p>\n<p>\n<a href=\"https://indieweb.org/tag-reply#How_to_simple_tag-reply\">https://indieweb.org/tag-reply#How_to_simple_tag-reply</a>\n</p>\n<p>\nwhere one (or more) of the reply-to URLs is to a Flickr permalink post (likely others's photos, but could be my own that I'm adding tags to after I published it), Bridgy Publish (of my tag reply) should propagate that tag reply to that Flickr permalink.\n</p>\n<p>\nThis is the publish equivalent of the following backfeed features, and may be easier to start with (consider implementing publish before implementing backfeed for equivalent interaction)</p>\n<ul><li><a href=\"https://github.com/snarfed/bridgy/issues/776\">776</a></li>\n<li><a href=\"https://github.com/snarfed/bridgy/issues/488\">488</a></li>\n</ul><p>\nLabels: \n<span class=\"p-category\">publish</span>\n</p>"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "reply",
    "refs": {
        "https://github.com/snarfed/bridgy/issues/": {
            "type": "entry",
            "url": "https://github.com/snarfed/bridgy/issues/",
            "name": "GitHub project \u201cbridgy\u201d",
            "post-type": "article"
        }
    },
    "_id": "1760375",
    "_source": "1",
    "_is_read": true
}

Homebrew Website Club SF!

{
    "type": "event",
    "name": "Homebrew Website Club SF!",
    "summary": "17:30: Optional writing hour and quiet socializing\n18:30: IndieWeb demos and hack night!\n\nHomebrew Website Club retro 1980s-style logo\nTopics for this week: First Homebrew Website Club meetup of 2019! Year-end hack projects 2018 IndieWeb Challenge completed! Flickr with new owner \u2014 aligning with IndieWeb principles? Demos of personal website breakthroughs Create or update your personal web site!\nJoin a community with like-minded interests. Bring friends that want a personal site, or are interested in a healthy, independent web!\nAny questions? Ask in #indieweb Slack or IRC\nMore information: IndieWeb Wiki Event Page\nRSVP: post an indie RSVP on your own site!",
    "published": "2018-01-07 10:31-0800",
    "start": "2019-01-09 17:30-0800",
    "end": "2019-01-09 19:30-0800",
    "url": "http://tantek.com/2019/009/e1/homebrew-website-club-sf",
    "location": [
        "https://wiki.mozilla.org/SF"
    ],
    "content": {
        "text": "When: 2019-01-09 17:30\u202619:30\nWhere: Mozilla San Francisco\n\nHost: Tantek \u00c7elik\n\n\n\n17:30: Optional writing hour and quiet socializing\n\n18:30: IndieWeb demos and hack night!\n\n\nTopics for this week:\nFirst Homebrew Website Club meetup of 2019!\nYear-end hack projects\n\n2018 IndieWeb Challenge completed!\nFlickr with new owner \u2014 aligning with IndieWeb principles?\nDemos of personal website breakthroughs\nCreate or update your personal web site!\n\nJoin a community with like-minded interests. Bring friends that want a personal site, or are interested in a healthy, independent web!\n\n\nAny questions? Ask in \n#indieweb Slack or IRC\n\n\nMore information: \nIndieWeb Wiki Event Page\n\n\nRSVP:  post an indie RSVP on your own site!",
        "html": "<p>\nWhen: <time class=\"dt-start\">2019-01-09 17:30</time>\u2026<time class=\"dt-end\">19:30</time><span>\nWhere: <a class=\"u-location h-card\" href=\"https://wiki.mozilla.org/SF\">Mozilla San Francisco</a>\n</span>\nHost: <a class=\"u-organizer h-card\" href=\"http://tantek.com/\">Tantek \u00c7elik</a>\n</p>\n\n<p>\n17:30: Optional writing hour and quiet socializing<br />\n18:30: IndieWeb demos and hack night!<br /></p>\n<p><img class=\"u-featured\" style=\"height:300px;\" src=\"https://aperture-media.p3k.io/indieweb.org/c24f7b1e711955ef818bde12e2a3e79708ecc9b106d95b460a9fefe93b0be723.jpg\" alt=\"Homebrew Website Club retro 1980s-style logo\" /></p>\n<p>Topics for this week:</p>\n<ul><li>First Homebrew Website Club meetup of 2019!</li>\n<li><a href=\"https://indieweb.org/2019-01-01-commitments\">Year-end hack projects</a></li>\n<li>\n<a href=\"https://indieweb.org/2018-12-indieweb-challenge\">2018 IndieWeb Challenge</a> completed!</li>\n<li>Flickr with new owner \u2014 aligning with IndieWeb principles?</li>\n<li>Demos of personal website breakthroughs</li>\n<li>Create or update your personal web site!</li>\n</ul><p>\nJoin a community with like-minded interests. Bring friends that want a personal site, or are interested in a healthy, independent web!\n</p>\n<p>\nAny questions? Ask in \n<a href=\"https://indieweb.org/discuss\">#indieweb Slack or IRC</a>\n</p>\n<p>\nMore information: \n<a class=\"u-url\" href=\"https://indieweb.org/events/2019-01-09-homebrew-website-club\">IndieWeb Wiki Event Page</a>\n</p>\n<p>\nRSVP:  post an <a href=\"https://indieweb.org/rsvp\">indie RSVP</a> on your own site!\n</p>"
    },
    "post-type": "event",
    "refs": {
        "https://wiki.mozilla.org/SF": {
            "type": "card",
            "name": "Mozilla San Francisco",
            "url": "https://wiki.mozilla.org/SF",
            "photo": null
        }
    },
    "_id": "1757631",
    "_source": "1",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2019-01-07 00:51:32.647558",
    "url": "https://kongaloosh.com/e/2019/1/7/i-often-fo",
    "photo": [
        "https://aperture-proxy.p3k.io/3937e2ebddd797d08743c0dd32af634446d77d39/68747470733a2f2f6b6f6e67616c6f6f73682e636f6d2f646174612f323031392f312f372f494d475f323631322e6a7067"
    ],
    "syndication": [
        "https://twitter.com/kongaloosh/status/1082152754007687168"
    ],
    "content": {
        "text": "I often focus on the scenes in travel photography, cutting out people wherever possible; however, after binge-reviewing my old albums, I've noticed that the best photos are always ones where people are interacting with the environment--even when they're tourists!\n        \n                                 \n                                            \n                \n                    \n                    \n                    note\n                    \n                    indieweb\n                    \n                    dev\n                    \n                    photos\n                    \n                    albums",
        "html": "<a href=\"https://kongaloosh.com/e/2019/1/7/i-often-fo\">\n        </a>\n        \n        \n        <p class=\"e-content\"></p><p>I often focus on the scenes in travel photography, cutting out people wherever possible; however, after binge-reviewing my old albums, I've noticed that the best photos are always ones where people are interacting with the environment--even when they're tourists!</p>\n        \n                                 \n                                            \n                \n                    <i></i>\n                    \n                    <a href=\"https://kongaloosh.com/t/note\">note</a>\n                    \n                    <a href=\"https://kongaloosh.com/t/indieweb\">indieweb</a>\n                    \n                    <a href=\"https://kongaloosh.com/t/dev\">dev</a>\n                    \n                    <a href=\"https://kongaloosh.com/t/photos\">photos</a>\n                    \n                    <a href=\"https://kongaloosh.com/t/albums\">albums</a>"
    },
    "author": {
        "type": "card",
        "name": "Alex Kearney",
        "url": "http://kongaloosh.com",
        "photo": null
    },
    "post-type": "photo",
    "_id": "1752085",
    "_source": "228",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2019-01-07 00:51:32.647558",
    "url": "https://kongaloosh.com/e/2019/1/7/today-i-bi",
    "syndication": [
        "https://twitter.com/kongaloosh/status/1082152754007687168"
    ],
    "content": {
        "text": "Today I bit the data management bullet and started reviewing old photos. Geeze, I've forgotten how tedious it can be reviewing photos en masse: selecting them, editing them, exporting them, properly arranging them into albums..,\nI've not been great at photo management since Google nuked Picassa--a sort of light-weight version of Adobe's lightroom. I spent hours today untangling a mess of folders and directories housing photos from many computers ago. These photos are now largely sorted in Light Room, waiting for editing. I'm hoping their final resting place will be here on my server (with some redundancies, of course).\n        \n                                 \n                                            \n                \n                    \n                    \n                    note\n                    \n                    indieweb\n                    \n                    dev\n                    \n                    photos\n                    \n                    albums",
        "html": "<p class=\"e-content\"></p><p>Today I bit the data management bullet and started reviewing old photos. Geeze, I've forgotten how tedious it can be reviewing photos en masse: selecting them, editing them, exporting them, properly arranging them into albums..,</p>\n<p>I've not been great at photo management since Google nuked <a href=\"https://picasa.google.com/\">Picassa</a>--a sort of light-weight version of Adobe's lightroom. I spent hours today untangling a mess of folders and directories housing photos from <em>many</em> computers ago. These photos are now largely sorted in Light Room, waiting for editing. I'm hoping their final resting place will be here on my server (with some redundancies, of course).</p>\n        \n                                 \n                                            \n                \n                    <i></i>\n                    \n                    <a href=\"https://kongaloosh.com/t/note\">note</a>\n                    \n                    <a href=\"https://kongaloosh.com/t/indieweb\">indieweb</a>\n                    \n                    <a href=\"https://kongaloosh.com/t/dev\">dev</a>\n                    \n                    <a href=\"https://kongaloosh.com/t/photos\">photos</a>\n                    \n                    <a href=\"https://kongaloosh.com/t/albums\">albums</a>"
    },
    "author": {
        "type": "card",
        "name": "Alex Kearney",
        "url": "http://kongaloosh.com",
        "photo": null
    },
    "post-type": "note",
    "_id": "1751940",
    "_source": "228",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2019-01-06T00:39:50+0000",
    "url": "http://known.kevinmarks.com/2019/i-have-made-an-indieweb-friendly-hugo",
    "in-reply-to": [
        "https://calumryan.com/note/2327"
    ],
    "content": {
        "text": "I have made an indieweb friendly Hugo theme with microformats that might suit a docs project https://github.com/ChristopherA/LifeWithAlacrityBlog/tree/master/blog/themes/indie-tufte",
        "html": "I have made an indieweb friendly Hugo theme with microformats that might suit a docs project <a href=\"https://github.com/ChristopherA/LifeWithAlacrityBlog/tree/master/blog/themes/indie-tufte\">https://github.com/ChristopherA/LifeWithAlacrityBlog/tree/master/blog/themes/indie-tufte</a>"
    },
    "author": {
        "type": "card",
        "name": "Kevin Marks",
        "url": "http://known.kevinmarks.com/profile/kevinmarks",
        "photo": "https://aperture-proxy.p3k.io/ed7979fd10a648fc253eae0b54e66fb36e57d3d4/687474703a2f2f6b6e6f776e2e6b6576696e6d61726b732e636f6d2f66696c652f3932353536353636363931373362373836376162383339656536353536663965"
    },
    "post-type": "reply",
    "_id": "1743975",
    "_source": "205",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2019-01-06T01:30:34+00:00",
    "url": "https://cleverdevil.io/2019/-huzzah-i-now-have-my-trakt",
    "category": [
        "OwnYourData",
        "IndieWeb"
    ],
    "syndication": [
        "https://twitter.com/cleverdevil/status/1081724685082071040"
    ],
    "content": {
        "text": "\ud83c\udf89 Huzzah! I now have my Trakt watch history publishing automatically to my website. I can mark an episode of a TV show or a movie as watched in Trakt, and a record will be created on my website! See \u2013 https://cleverdevil.io/2019/spider-man-into-the-spider-verse-2018  #OwnYourData #IndieWeb",
        "html": "\ud83c\udf89 Huzzah! I now have my Trakt watch history publishing automatically to my website. I can mark an episode of a TV show or a movie as watched in Trakt, and a record will be created on my website! See \u2013 <a href=\"https://cleverdevil.io/2019/spider-man-into-the-spider-verse-2018\">https://cleverdevil.io/2019/spider-man-into-the-spider-verse-2018</a>  <a href=\"https://cleverdevil.io/tag/OwnYourData\" class=\"p-category\">#OwnYourData</a> <a href=\"https://cleverdevil.io/tag/IndieWeb\" class=\"p-category\">#IndieWeb</a>"
    },
    "author": {
        "type": "card",
        "name": "Jonathan LaCour",
        "url": "https://cleverdevil.io/profile/cleverdevil",
        "photo": "https://aperture-proxy.p3k.io/77e5d6e5871324c43aebf2e3e7a5553e14578f66/68747470733a2f2f636c65766572646576696c2e696f2f66696c652f66646263373639366135663733383634656131316138323863383631653133382f7468756d622e6a7067"
    },
    "post-type": "note",
    "_id": "1743244",
    "_source": "71",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2019-01-05T19:07:45+00:00",
    "url": "https://cleverdevil.io/2019/vossco-i-take-a-similar-approach-to",
    "in-reply-to": [
        "https://blog.voss.co/2019/consuming-instagram-differently"
    ],
    "content": {
        "text": "@voss.co I take a similar approach to following people on Instagram. I wrote a little script that uses the private Instagram API to load my timeline and then I generate an h-feed out of it, which I subscribe to in my Microsub server. Works a treat!"
    },
    "author": {
        "type": "card",
        "name": "Jonathan LaCour",
        "url": "https://cleverdevil.io/profile/cleverdevil",
        "photo": "https://aperture-proxy.p3k.io/77e5d6e5871324c43aebf2e3e7a5553e14578f66/68747470733a2f2f636c65766572646576696c2e696f2f66696c652f66646263373639366135663733383634656131316138323863383631653133382f7468756d622e6a7067"
    },
    "post-type": "reply",
    "_id": "1741252",
    "_source": "71",
    "_is_read": true
}

Homebrew Website Club – Karlsruhe

{
    "type": "entry",
    "published": "2019-01-04T14:49:45+00:00",
    "url": "https://notiz.blog/2019/01/04/homebrew-website-club-karlsruhe/",
    "featured": "https://notiz.blog/wp-content/uploads/2019/01/HWC-banner-900x644.jpg",
    "name": "Homebrew Website Club \u2013 Karlsruhe",
    "content": {
        "text": "Wir starten am 23.01. um 19:00 Uhr (GMT) einen Karlsruher Homebrew Website Club im Caf\u00e9 NUN.\n\n\n\nWas ist ein Homebrew Website Club?\n\n\n\n\nHomebrew Website Club is a  bi-weekly meetup of people passionate about or interested in creating,  improving, building, designing their own website, in the same structure  as the classic Homebrew Computer Club meetings.\nhttps://indieweb.org/Homebrew_Website_Club\n\n\n\n\nWir versuchen den HWC eher ungezwungen und frei zu gestalten und wollen den ersten Termin dazu nutzen, uns kennen zu lernen und den weiteren Ablauf zu besprechen.\n\n\n\nVielen Dank an Daniel f\u00fcr das Organisieren der Lokation und vielen Dank dem Caf\u00e9 NUN f\u00fcr das Bereitstellen der Lokation \ud83d\ude42\n\n\n\nWer sonst noch Lust hat, einfach vorbei kommen!",
        "html": "<p>Wir starten am 23.01. um 19:00 Uhr (GMT) einen <a href=\"https://indieweb.org/events/2019-01-23-homebrew-website-club#Karlsruhe\">Karlsruher </a><em><a href=\"https://indieweb.org/events/2019-01-23-homebrew-website-club#Karlsruhe\">Homebrew Website Club</a></em> im <a href=\"https://www.nun.cafe/\">Caf\u00e9 NUN</a>.</p>\n\n\n\n<p>Was ist ein <em>Homebrew Website Club</em>?</p>\n\n\n\n<blockquote>\n<p><strong>Homebrew Website Club</strong> is a  bi-weekly meetup of people passionate about or interested in creating,  improving, building, designing their own website, in the same structure  as the <a href=\"https://en.wikipedia.org/wiki/Homebrew_Computer_Club\">classic Homebrew Computer Club</a> meetings.</p>\n<a href=\"https://indieweb.org/Homebrew_Website_Club\">https://indieweb.org/Homebrew_Website_Club</a>\n</blockquote>\n\n\n\n<p>Wir versuchen den HWC eher ungezwungen und frei zu gestalten und wollen den ersten Termin dazu nutzen, uns kennen zu lernen und den weiteren Ablauf zu besprechen.</p>\n\n\n\n<p>Vielen Dank an <a href=\"https://depone.net/\">Daniel</a> f\u00fcr das Organisieren der Lokation und vielen Dank dem <a href=\"https://www.nun.cafe/\">Caf\u00e9 NUN</a> f\u00fcr das Bereitstellen der Lokation \ud83d\ude42</p>\n\n\n\n<p>Wer sonst noch Lust hat, einfach vorbei kommen!</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": "article",
    "_id": "1731843",
    "_source": "206",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2019-01-01T11:10:11+0000",
    "url": "https://seblog.nl/2019/01/01/1/mullennium-bug",
    "category": [
        "indieweb"
    ],
    "content": {
        "text": "My site broke, because the /2019 folder in my storage did not yet exist, and somewhere over the last year I added code that relied on that. So 19 years in, the Millennium bug is still active.",
        "html": "<p>My site broke, because the /2019 folder in my storage did not yet exist, and somewhere over the last year I added code that relied on that. So 19 years in, the Millennium bug is still active.</p>"
    },
    "author": {
        "type": "card",
        "name": "Sebastiaan Andeweg",
        "url": "https://seblog.nl/",
        "photo": "https://aperture-proxy.p3k.io/10e8aeca31d1cd146999fcacc07a8eb9ad47c813/68747470733a2f2f7365626c6f672e6e6c2f70686f746f2e6a7067"
    },
    "post-type": "note",
    "_id": "1726003",
    "_source": "1366",
    "_is_read": true
}

2019-01-03 13.31.56

{
    "type": "entry",
    "author": {
        "name": "Kh\u00fcrt Williams",
        "url": "https://islandinthenet.com/",
        "photo": null
    },
    "url": "https://islandinthenet.com/2019-01-03-13-31-56/",
    "published": "2019-01-03T18:31:56+00:00",
    "content": {
        "html": "<p>It\u2019s not a long time but I\u2019ve just realized that I\u2019ve been using Webmentions and other IndieWeb technologies on WordPress for over a year now.</p>",
        "text": "It\u2019s not a long time but I\u2019ve just realized that I\u2019ve been using Webmentions and other IndieWeb technologies on WordPress for over a year now."
    },
    "name": "2019-01-03 13.31.56",
    "post-type": "article",
    "_id": "1723686",
    "_source": "242",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2019-01-01T12:07:38+0000",
    "url": "http://known.kevinmarks.com/2019/i-updated-mentiontech-to-output-webmentionio-compatible",
    "category": [
        "indieweb"
    ],
    "in-reply-to": [
        "https://beesbuzz.biz/blog/3743-More-fun-with-Webmentions"
    ],
    "content": {
        "text": "I updated mention.tech to output webmention.io compatible JSON for mentions eg https://mention.tech/listmentions?target=https%3A%2F%2Ftumblelog.xyz&json=on and modified fluffy's script to show them on https://tumblelog.xyz/  at https://tumblelog.xyz/webmention.js #indieweb",
        "html": "I updated mention.tech to output webmention.io compatible JSON for mentions eg <a href=\"https://mention.tech/listmentions?target=https%3A%2F%2Ftumblelog.xyz&amp;json=on\">https://mention.tech/listmentions?target=https%3A%2F%2Ftumblelog.xyz&amp;json=on</a> and modified fluffy's script to show them on <a href=\"https://tumblelog.xyz/\">https://tumblelog.xyz/</a>  at <a href=\"https://tumblelog.xyz/webmention.js\">https://tumblelog.xyz/webmention.js</a> <a href=\"http://known.kevinmarks.com/tag/indieweb\" class=\"p-category\">#indieweb</a>"
    },
    "author": {
        "type": "card",
        "name": "Kevin Marks",
        "url": "http://known.kevinmarks.com/profile/kevinmarks",
        "photo": "https://aperture-proxy.p3k.io/ed7979fd10a648fc253eae0b54e66fb36e57d3d4/687474703a2f2f6b6e6f776e2e6b6576696e6d61726b732e636f6d2f66696c652f3932353536353636363931373362373836376162383339656536353536663965"
    },
    "post-type": "reply",
    "_id": "1723612",
    "_source": "205",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2018-12-31T23:45:56+0000",
    "url": "http://known.kevinmarks.com/2018/happy-new-year",
    "category": [
        "indieweb"
    ],
    "photo": [
        "https://aperture-proxy.p3k.io/b02b2f7ea5c45be555a7310df32c91eb5a57cfdb/687474703a2f2f6b6e6f776e2e6b6576696e6d61726b732e636f6d2f66696c652f38626239383431353236656434386236343734333263303533633834643461342f41464c2e737667"
    ],
    "content": {
        "text": "Via svgshare.com\u00a0#indieweb\u00a0",
        "html": "<a href=\"http://known.kevinmarks.com/2018/happy-new-year\"></a>\n            \n            <p>Via <a href=\"https://www.svgshare.com/s/AFL\">svgshare.com</a>\u00a0<a href=\"http://known.kevinmarks.com/tag/indieweb\" class=\"p-category\">#indieweb</a>\u00a0</p>"
    },
    "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": "1723613",
    "_source": "205",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2018-12-30 22:38-0800",
    "url": "http://tantek.com/2018/364/t4/microformats2-parsing-parse-html-id-attribute",
    "category": [
        "microformats2"
    ],
    "content": {
        "text": "#microformats2 parsing spec updated: http://microformats.org/wiki/index.php?title=microformats2-parsing&diff=66967&oldid=66965\n* parse HTML id attribute per https://github.com/microformats/microformats2-parsing/issues/44\nImplemented in current versions of parsers:\n* phpmf2\n* mf2py",
        "html": "#<span class=\"p-category\">microformats2</span> parsing spec updated: <a href=\"http://microformats.org/wiki/index.php?title=microformats2-parsing&amp;diff=66967&amp;oldid=66965\">http://microformats.org/wiki/index.php?title=microformats2-parsing&amp;diff=66967&amp;oldid=66965</a><br />* parse HTML id attribute per <a href=\"https://github.com/microformats/microformats2-parsing/issues/44\">https://github.com/microformats/microformats2-parsing/issues/44</a><br />Implemented in current versions of parsers:<br />* phpmf2<br />* mf2py"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "note",
    "_id": "1723294",
    "_source": "1",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2018-12-30 21:48-0800",
    "url": "http://tantek.com/2018/364/t2/",
    "in-reply-to": [
        "https://github.com/microformats/microformats2-parsing/issues/2#issuecomment-392608361"
    ],
    "content": {
        "text": "I\u2019ve incorporated the proposed issue 2 spec changes (see diff: http://microformats.org/wiki/index.php?title=microformats2-parsing&diff=66965&oldid=66956), please review \"PROPOSED\" text in:\n* http://microformats.org/wiki/microformats2-parsing#parsing_a_u-_property\n* http://microformats.org/wiki/microformats2-parsing#parsing_for_implied_properties\n* http://microformats.org/wiki/microformats2-parsing#parse_an_img_element_for_src_and_alt",
        "html": "I\u2019ve incorporated the proposed issue 2 spec changes (see diff: <a href=\"http://microformats.org/wiki/index.php?title=microformats2-parsing&amp;diff=66965&amp;oldid=66956\">http://microformats.org/wiki/index.php?title=microformats2-parsing&amp;diff=66965&amp;oldid=66956</a>), please review \"PROPOSED\" text in:<br />* <a href=\"http://microformats.org/wiki/microformats2-parsing#parsing_a_u-_property\">http://microformats.org/wiki/microformats2-parsing#parsing_a_u-_property</a><br />* <a href=\"http://microformats.org/wiki/microformats2-parsing#parsing_for_implied_properties\">http://microformats.org/wiki/microformats2-parsing#parsing_for_implied_properties</a><br />* <a href=\"http://microformats.org/wiki/microformats2-parsing#parse_an_img_element_for_src_and_alt\">http://microformats.org/wiki/microformats2-parsing#parse_an_img_element_for_src_and_alt</a>"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "reply",
    "refs": {
        "https://github.com/microformats/microformats2-parsing/issues/2#issuecomment-392608361": {
            "type": "entry",
            "url": "https://github.com/microformats/microformats2-parsing/issues/2#issuecomment-392608361",
            "name": "a comment on issue 2 of GitHub project \u201cmicroformats2-parsing\u201d",
            "post-type": "article"
        }
    },
    "_id": "1723297",
    "_source": "1",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2018-12-30 09:46-0800",
    "url": "http://tantek.com/2018/364/t1/sixth-reason-post-positive-things-promptly",
    "in-reply-to": [
        "http://tantek.com/2018/357/t3/five-reasons-post-positive-things-promptly"
    ],
    "content": {
        "text": "Sixth Reason To Post Positive Things Promptly\n\n6. Post about something positive the same day it happens so it will show up automatically in future \"On This Day\" reminder posts. https://indieweb.org/on_this_day\n\nPreviously: tantek.com/2018/357/t3/five-reasons-post-positive-things-promptly",
        "html": "Sixth Reason To Post Positive Things Promptly<br /><br />6. Post about something positive the same day it happens so it will show up automatically in future \"On This Day\" reminder posts. <a href=\"https://indieweb.org/on_this_day\">https://indieweb.org/on_this_day</a><br /><br />Previously: <a href=\"http://tantek.com/2018/357/t3/five-reasons-post-positive-things-promptly\">tantek.com/2018/357/t3/five-reasons-post-positive-things-promptly</a>"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "reply",
    "refs": {
        "http://tantek.com/2018/357/t3/five-reasons-post-positive-things-promptly": {
            "type": "entry",
            "url": "http://tantek.com/2018/357/t3/five-reasons-post-positive-things-promptly",
            "name": "tantek.com\u2019s post",
            "post-type": "article"
        }
    },
    "_id": "1723299",
    "_source": "1",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2018-12-26 16:31-0800",
    "url": "http://tantek.com/2018/360/t1/cancelling-homebrew-website-club-sf",
    "in-reply-to": [
        "http://tantek.com/2018/360/e1/homebrew-website-club-sf"
    ],
    "content": {
        "text": "Apologies for the late notice, cancelling Homebrew Website Club SF tonight.\n\nNot feeling 100%, and checked with Jacky to see if we could do a virtual one on Mumble so we\u2019re going to try that.\n\nSee https://chat.indieweb.org/ for more or to join virtually!",
        "html": "Apologies for the late notice, cancelling Homebrew Website Club SF tonight.<br /><br />Not feeling 100%, and checked with Jacky to see if we could do a virtual one on Mumble so we\u2019re going to try that.<br /><br />See <a href=\"https://chat.indieweb.org/\">https://chat.indieweb.org/</a> for more or to join virtually!"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "reply",
    "refs": {
        "http://tantek.com/2018/360/e1/homebrew-website-club-sf": {
            "type": "entry",
            "url": "http://tantek.com/2018/360/e1/homebrew-website-club-sf",
            "name": "tantek.com\u2019s post",
            "post-type": "article"
        }
    },
    "_id": "1723301",
    "_source": "1",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2018-12-31 21:54-0800",
    "url": "http://tantek.com/2018/365/t5/microformats2-parsing-always-parse-alt-with-src",
    "category": [
        "microformats2"
    ],
    "content": {
        "text": "#microformats2 parsing spec updated: http://microformats.org/wiki/index.php?title=microformats2-parsing&diff=66969&oldid=66967\n* always parse alt with img src for accessibility info by default https://github.com/microformats/microformats2-parsing/issues/2\nImplemented in current version of:\n* mf2py - behind flag, in use by Brid.gy\nThis is a pretty big change, likely to require updates to parsers and calling code, however, the better access to accessibility info on img elements by default is a big improvement for all.",
        "html": "#<span class=\"p-category\">microformats2</span> parsing spec updated: <a href=\"http://microformats.org/wiki/index.php?title=microformats2-parsing&amp;diff=66969&amp;oldid=66967\">http://microformats.org/wiki/index.php?title=microformats2-parsing&amp;diff=66969&amp;oldid=66967</a><br />* always parse alt with img src for accessibility info by default <a href=\"https://github.com/microformats/microformats2-parsing/issues/2\">https://github.com/microformats/microformats2-parsing/issues/2</a><br />Implemented in current version of:<br />* mf2py - behind flag, in use by <a href=\"http://Brid.gy\">Brid.gy</a><br />This is a pretty big change, likely to require updates to parsers and calling code, however, the better access to accessibility info on img elements by default is a big improvement for all."
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "note",
    "_id": "1723288",
    "_source": "1",
    "_is_read": true
}