Yes! I have been thinking about this a lot as well. Having hosted lots of IndieWeb events on my site (including HWC Baltimore and some of my improv shows), I increasingly feel like those event pages belong somewhere on the web associated with those communities.
I will of course keep my own RSVPs, photos, and recap write-ups on my site, but would gladly syndicate them to the community event page. If the event page supports IndieWeb building blocks like microformats2 and webmention, I wouldn’t even have to do anything special for them to show up there!
{
"type": "entry",
"published": "2019-01-21T11:51:21-0500",
"url": "https://martymcgui.re/2019/01/21/115121/",
"in-reply-to": [
"https://percolator.today/episode/23"
],
"content": {
"text": "Yes! I have been thinking about this a lot as well. Having hosted lots of IndieWeb events on my site (including HWC Baltimore and some of my improv shows), I increasingly feel like those event pages belong somewhere on the web associated with those communities.\n\nI will of course keep my own RSVPs, photos, and recap write-ups on my site, but would gladly syndicate them to the community event page. If the event page supports IndieWeb building blocks like microformats2 and webmention, I wouldn\u2019t even have to do anything special for them to show up there!",
"html": "<p>Yes! I have been thinking about this a lot as well. Having hosted lots of IndieWeb events on my site (including HWC Baltimore and some of my improv shows), I increasingly feel like those event pages belong somewhere on the web associated with those communities.</p>\n\n<p>I will of course keep my own RSVPs, photos, and recap write-ups on my site, but would gladly syndicate them to the community event page. If the event page supports IndieWeb building blocks like microformats2 and webmention, I wouldn\u2019t even have to do anything special for them to show up there!</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://aperture-proxy.p3k.io/8275f85e3a389bd0ae69f209683436fc53d8bad9/68747470733a2f2f6d617274796d636775692e72652f696d616765732f6c6f676f2e6a7067"
},
"post-type": "reply",
"refs": {
"https://percolator.today/episode/23": {
"type": "entry",
"published": "2019-01-19T00:00:00+0000",
"summary": "Watch the video version at https://youtu.be/1Faq5tENu7Y",
"url": "https://percolator.today/episode/23",
"audio": [
"https://percolator.today/redirect.php?url=https%3A%2F%2Fpercolator.today%2Fmedia%2FEpisode_23.mp3"
],
"name": "Episode 23: Thinking about a Website for Events",
"author": {
"type": "card",
"name": "Percolator",
"url": "https://percolator.today",
"photo": "https://res.cloudinary.com/schmarty/image/fetch/w_60,c_fill/https://percolator.today/images/avatar.jpg"
},
"post-type": "audio"
}
},
"_id": "1888809",
"_source": "175",
"_is_read": true
}
Got a colourful new refresh of my #indieweb site online: https://grant.codes
{
"type": "entry",
"published": "2017-10-18T18:58:52.541Z",
"url": "https://grant.codes/2017/10/18/59e7a46c8191f2590727801a",
"syndication": [
"https://twitter.com/grantcodes/status/920726584071479296",
"https://www.facebook.com/grant.codes/posts/1918323681518772"
],
"content": {
"text": "Got a colourful new refresh of my #indieweb site online: https://grant.codes",
"html": "<p>Got a colourful new refresh of my #indieweb site online: <a href=\"https://grant.codes\">https://grant.codes</a></p>"
},
"author": {
"type": "card",
"name": "Grant Richmond",
"url": "https://grant.codes",
"photo": "https://aperture-proxy.p3k.io/be31049af9884a65289b2d14300adafc0e4030c6/68747470733a2f2f6772616e742e636f6465732f696d672f6d652e6a7067"
},
"post-type": "note",
"_id": "1875465",
"_source": "11",
"_is_read": true
}
An IndieWeb(ring) Directory
{
"type": "entry",
"published": "2019-01-19T12:36:07-0500",
"url": "https://martymcgui.re/2019/01/19/an-indiewebring-directory/",
"category": [
"\ud83d\udd78\ud83d\udc8d",
"webring",
"indieweb",
"update",
"directory"
],
"name": "An IndieWeb(ring) Directory",
"content": {
"text": "Members of the \ud83d\udd78\ud83d\udc8d IndieWeb Webring now have a new way to find one another, and show off!\n\n Screenshot sample of profiles in this IndieWeb Webring directory including photo, name, URL, and bio note.\n That\u2019s right, this \ud83d\udd78\ud83d\udc8d IndieWeb Webring now has a directory showcasing profiles of active sites in the ring! Where possible, it shows name, photo, and short bio in addition to the site\u2019s URL (and of course their potentially problematic cute emoji ID).\n \n\nThese profiles are possible when people publish personal particulars on their page as a microformats2 representative h-card.\nThat is a bunch of jargon, to be sure, but what it means is that you with a few tweaks to your homepage, you can make info like your name, photo, and a bio \u2013 which is probably already displayed for people to see \u2013 readable by machines that understand microformats2, like this one!\nFated-to-be Asked Questions\nHow do I get my site to show up in the directory?\nVisit the your \ud83d\udd78\ud83d\udc8d webring dashboard (you\u2019ll need to log in) and click the \u201cCheck for updated profile\u201d button.\nI updated my profile, but it\u2019s not working!\nTry out your page in the indiewebify.me validator. If it shows you that it found a \u201crepresentative h-card\u201d, then your page should work for the webring directory!\nWait a sec, my site is already in the directory!\nI went ahead and pre-loaded the profile info for all registered and active sites! I don\u2019t plan to do that again.\nMy site is in the directory but I don\u2019t want to be listed!\nSorry about that! You can remove yourself by visiting your \ud83d\udd78\ud83d\udc8d webring dashboard (you\u2019ll need to log in) and click the \u201cRemove my profile\u201d button.\nWhy did you do this?\nI was inspired by Grant\u2019s IndieWeb Directory, Aaron\u2019s Microcast.club, this \ud83d\udd78\ud83d\udc8d review by Brad Enslen, and more. Basically: surfing around a webring with next and previous links is good fun, and it\u2019s even more fun to see so many folks excited about the IndieWeb in one place!\nIs there anything else?\n\nYes! There are also now individual profile pages, if that\u2019s something you want to link to. My webring emoji ID is \ud83d\udeaf, so my profile can be found at: \ud83d\udd78\ud83d\udc8d.ws/\ud83d\udeaf\nI don\u2019t know yet how these pages might evolve so I welcome your feedback!\n\nCan I ask you a different question or give you feedback?\nOf course! Please do! You can reply to this post on your own site or via Twitter, or feel free to drop me a line in the #indieweb chat (I\u2019m schmarty there).",
"html": "<p></p><p>Members of the <a href=\"https://xn--sr8hvo.ws\">\ud83d\udd78\ud83d\udc8d</a> IndieWeb Webring now have a new way to find one another, and show off!</p>\n<a href=\"https://xn--sr8hvo.ws/directory\"><img src=\"https://aperture-proxy.p3k.io/9e9bca9810c158e83b4d3375fd0f16603e0818d3/68747470733a2f2f6d656469612e6d617274796d636775692e72652f61332f35372f39632f62332f37653438363534353335393932333163343865636238653833616264616238363936343836396135373938376663666665333261386135322e6a7067\" alt=\"\" /></a>\n Screenshot sample of profiles in this IndieWeb Webring directory including photo, name, URL, and bio note.<p>\n That\u2019s right, this \ud83d\udd78\ud83d\udc8d IndieWeb Webring now has <a href=\"https://xn--sr8hvo.ws/directory\">a directory showcasing profiles of active sites in the ring</a>! Where possible, it shows name, photo, and short bio in addition to the site\u2019s URL (and of course their <del>potentially problematic</del> cute emoji ID).\n <br /></p>\n<p>These profiles are possible when people publish personal particulars on their page as a <a href=\"http://microformats.org/wiki/microformats2\">microformats2</a> <a href=\"http://microformats.org/wiki/representative-h-card-authoring\">representative</a> <a href=\"http://microformats.org/wiki/h-card\">h-card</a>.</p>\n<p>That is a bunch of jargon, to be sure, but what it means is that you with a few tweaks to your homepage, you can make info like your name, photo, and a bio \u2013 which is probably already displayed for people to see \u2013 readable by machines that understand microformats2, like this one!</p>\n<h2>Fated-to-be Asked Questions</h2>\nHow do I get my site to show up in the directory?\n<p>Visit the your <a href=\"https://xn--sr8hvo.ws/dashboard\">\ud83d\udd78\ud83d\udc8d webring dashboard</a> (you\u2019ll need to log in) and click the \u201cCheck for updated profile\u201d button.</p>\nI updated my profile, but it\u2019s not working!\n<p>Try out your page in the <a href=\"https://indiewebify.me/validate-h-card/\">indiewebify.me validator</a>. If it shows you that it found a \u201crepresentative h-card\u201d, then your page should work for the webring directory!</p>\nWait a sec, my site is already in the directory!\n<p>I went ahead and pre-loaded the profile info for all registered and active sites! I don\u2019t plan to do that again.</p>\nMy site is in the directory but I don\u2019t want to be listed!\n<p>Sorry about that! You can remove yourself by visiting your <a href=\"https://xn--sr8hvo.ws/dashboard\">\ud83d\udd78\ud83d\udc8d webring dashboard</a> (you\u2019ll need to log in) and click the \u201cRemove my profile\u201d button.</p>\nWhy did you do this?\n<p>I was inspired by <a href=\"https://grant.codes/\">Grant\u2019s</a> <a href=\"https://indieweb-directory.glitch.me/\">IndieWeb Directory</a>, <a href=\"https://aaronparecki.com/\">Aaron\u2019s</a> <a href=\"https://microcast.club/\">Microcast.club</a>, <a href=\"https://ramblinggit.com/2018/08/coroners-report-webrings-are-dead-part-ii/\">this \ud83d\udd78\ud83d\udc8d review</a> by <a href=\"https://ramblinggit.com/\">Brad Enslen</a>, and more. Basically: surfing around a webring with next and previous links is good fun, and it\u2019s even more fun to see so many folks excited about the IndieWeb in one place!</p>\nIs there anything else?\n\n<p>Yes! There are also now individual profile pages, if that\u2019s something you want to link to. My webring emoji ID is \ud83d\udeaf, so my profile can be found at: <a href=\"https://xn--sr8hvo.ws/%F0%9F%9A%AF\">\ud83d\udd78\ud83d\udc8d.ws/\ud83d\udeaf</a></p>\n<p>I don\u2019t know yet how these pages might evolve so I welcome your feedback!</p>\n\nCan I ask you a different question or give you feedback?\n<p>Of course! Please do! You can <a href=\"https://indieweb.org/reply\">reply</a> to this post on your own site or via Twitter, or feel free to drop me a line in the <a href=\"https://chat.indieweb.org/\">#indieweb chat</a> (I\u2019m <code>schmarty</code> there).</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://aperture-proxy.p3k.io/8275f85e3a389bd0ae69f209683436fc53d8bad9/68747470733a2f2f6d617274796d636775692e72652f696d616765732f6c6f676f2e6a7067"
},
"post-type": "article",
"_id": "1868458",
"_source": "175",
"_is_read": true
}
@meyerweb the latter taught me a lot about the value of better naming.
* undohtml.css — no one remembers (tantek.com/log/2004/09.html#d06t2354 & your follow-up https://meyerweb.com/eric/thoughts/2004/09/15/emreallyem-undoing-htmlcss/)
* reset.css — everyone uses (http://meyerweb.com/eric/thoughts/2007/04/18/reset-reasoning/ ~3 years later too!)
Name things (tools especially) by value/function to the user, rather than literal plumbing functionality.
Hey at least our permalink slugs have improved. :)
https://indieweb.org/URL_design#Topic
* undohtml.css — no one remembers (tantek.com/log/2004/09.html#d06t2354 & your follow-up https://meyerweb.com/eric/thoughts/2004/09/15/emreallyem-undoing-htmlcss/)
* reset.css — everyone uses (http://meyerweb.com/eric/thoughts/2007/04/18/reset-reasoning/ ~3 years later too!)
Name things (tools especially) by value/function to the user, rather than literal plumbing functionality.
Hey at least our permalink slugs have improved. :)
https://indieweb.org/URL_design#Topic
{
"type": "entry",
"published": "2019-01-18 11:32-0800",
"url": "http://tantek.com/2019/018/t1/value-better-naming-undohtml-reset-css",
"in-reply-to": [
"https://twitter.com/meyerweb/status/1086236598713413632"
],
"content": {
"text": "@meyerweb the latter taught me a lot about the value of better naming.\n\n* undohtml.css \u2014 no one remembers (tantek.com/log/2004/09.html#d06t2354 & your follow-up https://meyerweb.com/eric/thoughts/2004/09/15/emreallyem-undoing-htmlcss/)\n* reset.css \u2014 everyone uses (http://meyerweb.com/eric/thoughts/2007/04/18/reset-reasoning/ ~3 years later too!)\n\nName things (tools especially) by value/function to the user, rather than literal plumbing functionality.\n\nHey at least our permalink slugs have improved. :)\nhttps://indieweb.org/URL_design#Topic",
"html": "<a class=\"h-cassis-username\" href=\"https://twitter.com/meyerweb\">@meyerweb</a> the latter taught me a lot about the value of better naming.<br /><br />* undohtml.css \u2014 no one remembers (<a href=\"http://tantek.com/log/2004/09.html#d06t2354\">tantek.com/log/2004/09.html#d06t2354</a> & your follow-up <a href=\"https://meyerweb.com/eric/thoughts/2004/09/15/emreallyem-undoing-htmlcss/\">https://meyerweb.com/eric/thoughts/2004/09/15/emreallyem-undoing-htmlcss/</a>)<br />* reset.css \u2014 everyone uses (<a href=\"http://meyerweb.com/eric/thoughts/2007/04/18/reset-reasoning/\">http://meyerweb.com/eric/thoughts/2007/04/18/reset-reasoning/</a> ~3 years later too!)<br /><br />Name things (tools especially) by value/function to the user, rather than literal plumbing functionality.<br /><br />Hey at least our permalink slugs have improved. :)<br /><a href=\"https://indieweb.org/URL_design#Topic\">https://indieweb.org/URL_design#Topic</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://twitter.com/meyerweb/status/1086236598713413632": {
"type": "entry",
"url": "https://twitter.com/meyerweb/status/1086236598713413632",
"name": "@meyerweb\u2019s tweet",
"post-type": "article"
}
},
"_id": "1859501",
"_source": "1",
"_is_read": true
}
I set up automatic podcast episode importing for my website based on my podcasts' RSS feeds today. You can check out the script here, it's tools like microformats, Micropub, RSS, etc that make me love having a website nowadays!
{
"type": "entry",
"published": "2019-01-17T17:21:45-05:00",
"url": "https://eddiehinkle.com/2019/01/17/10/note/",
"category": [
"tech"
],
"syndication": [
"https://micro.blog/EddieHinkle",
"https://twitter.com/eddiehinkle"
],
"content": {
"text": "I set up automatic podcast episode importing for my website based on my podcasts' RSS feeds today. You can check out the script here, it's tools like microformats, Micropub, RSS, etc that make me love having a website nowadays!",
"html": "I set up automatic podcast episode importing for my website based on my podcasts' RSS feeds today. <a href=\"https://eddiehinkle.com/2019/01/17/9/code/\">You can check out the script here</a>, it's tools like microformats, Micropub, RSS, etc that make me love having a website nowadays!"
},
"author": {
"type": "card",
"name": "Eddie Hinkle",
"url": "https://eddiehinkle.com/",
"photo": "https://aperture-proxy.p3k.io/cc9591b69c2c835fa2c6e23745b224db4b4b431f/68747470733a2f2f656464696568696e6b6c652e636f6d2f696d616765732f70726f66696c652e6a7067"
},
"post-type": "note",
"_id": "1846931",
"_source": "226",
"_is_read": true
}
All of the posts on my website going forward will now contain a snapshot of the current weather at my location. Hidden in the raw metadata, I’ll include detailed weather and location info. #IndieWeb
{
"type": "entry",
"published": "2019-01-17T03:18:54+00:00",
"url": "https://cleverdevil.io/2019/all-of-the-posts-on-my-website",
"category": [
"IndieWeb"
],
"syndication": [
"https://twitter.com/cleverdevil/status/1085738212134473728",
"https://mastodon.social/@cleverdevil/101429748547631151"
],
"content": {
"text": "All of the posts on my website going forward will now contain a snapshot of the current weather at my location. Hidden in the raw metadata, I\u2019ll include detailed weather and location info. #IndieWeb",
"html": "All of the posts on my website going forward will now contain a snapshot of the current weather at my location. Hidden in the raw metadata, I\u2019ll include detailed weather and location info. <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": "1836802",
"_source": "71",
"_is_read": true
}
I'm going!
Looking forward to my first Homebrew Website Club since moving to NYC!
{
"type": "entry",
"published": "2019-01-16T13:11:28-0500",
"rsvp": "yes",
"url": "https://martymcgui.re/2019/01/16/131128/",
"category": [
"NYC",
"IndieWeb",
"HWC"
],
"in-reply-to": [
"https://indieweb.org/events/2019-01-23-homebrew-website-club-nyc"
],
"content": {
"text": "I'm going!Looking forward to my first Homebrew Website Club since moving to NYC!",
"html": "I'm going!<p>Looking forward to my first Homebrew Website Club since moving to NYC!</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://aperture-proxy.p3k.io/8275f85e3a389bd0ae69f209683436fc53d8bad9/68747470733a2f2f6d617274796d636775692e72652f696d616765732f6c6f676f2e6a7067"
},
"post-type": "rsvp",
"refs": {
"https://indieweb.org/events/2019-01-23-homebrew-website-club-nyc": {
"type": "entry",
"summary": "Join us for an evening of IndieWeb personal site demos and discussions!",
"url": "https://indieweb.org/events/2019-01-23-homebrew-website-club-nyc",
"photo": [
"https://res.cloudinary.com/schmarty/image/fetch/w_960,c_fill/https://indieweb.org/images/b/b1/2017-hwc-80s-retro.jpg"
],
"name": "\ud83d\uddfd Homebrew Website Club NYC",
"author": {
"type": "card",
"name": "indieweb.org",
"url": "http://indieweb.org",
"photo": null
},
"post-type": "photo"
}
},
"_id": "1832598",
"_source": "175",
"_is_read": true
}
Configure Indiepaper with IndieAuth
{
"type": "entry",
"author": {
"name": "Kh\u00fcrt Williams",
"url": "https://islandinthenet.com/",
"photo": null
},
"url": "https://islandinthenet.com/configure-indiepaper-with-indieauth/",
"published": "2019-01-16T05:28:48+00:00",
"content": {
"html": "<img src=\"https://aperture-proxy.p3k.io/da79a4ab8a449617e96a66de6456d389cec7e58a/68747470733a2f2f7777772e696e64696570617065722e696f2f696d616765732f696e646965617574682d6c6f676f2d636f6c6f722e706e67\" alt=\"IndieAuth Logo\" /> \nLink posted to:<p><a href=\"https://www.indiepaper.io/indieauth.html?success=true\"> indiepaper.io</a></p>",
"text": "Link posted to: indiepaper.io"
},
"name": "Configure Indiepaper with IndieAuth",
"post-type": "article",
"_id": "1825033",
"_source": "242",
"_is_read": true
}
Signal v Noise exits Medium – Signal v. Noise
Traditional blogs might have swung out of favor, as we all discovered the benefits of social media and aggregating platforms, but we think they’re about to swing back in style, as we all discover the real costs and problems brought by such centralization.
{
"type": "entry",
"published": "2019-01-16T00:03:55Z",
"url": "https://adactio.com/links/14698",
"category": [
"blogging",
"medium",
"indieweb",
"writing",
"publishing",
"sharing",
"signalvnoise",
"platforms",
"blogs"
],
"bookmark-of": [
"https://m.signalvnoise.com/signal-v-noise-exits-medium/"
],
"content": {
"text": "Signal v Noise exits Medium \u2013 Signal v. Noise\n\n\n\n\n Traditional blogs might have swung out of favor, as we all discovered the benefits of social media and aggregating platforms, but we think they\u2019re about to swing back in style, as we all discover the real costs and problems brought by such centralization.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://m.signalvnoise.com/signal-v-noise-exits-medium/\">\nSignal v Noise exits Medium \u2013 Signal v. Noise\n</a>\n</h3>\n\n<blockquote>\n <p>Traditional blogs might have swung out of favor, as we all discovered the benefits of social media and aggregating platforms, but we think they\u2019re about to swing back in style, as we all discover the real costs and problems brought by such centralization.</p>\n</blockquote>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://aperture-proxy.p3k.io/bbbacdf0a064621004f2ce9026a1202a5f3433e0/68747470733a2f2f6164616374696f2e636f6d2f696d616765732f70686f746f2d3135302e6a7067"
},
"post-type": "bookmark",
"_id": "1822522",
"_source": "2",
"_is_read": true
}
Indie Communities and Making Your Audience Known
{
"type": "entry",
"published": "2019-01-14T16:49:14+00:00",
"url": "https://werd.io/2019/indie-communities-and-making-your-audience-known",
"name": "Indie Communities and Making Your Audience Known",
"content": {
"text": "It sounds ludicrous now, but back in 2014, when I cofounded\u00a0Known as a startup, a lot of people were questioning whether a business even needed a website. Pockets of people - for example in the indieweb community, which I enthusiastically joined - were pointing out how short-sighted this was, but it was a minority opinion. There was Facebook and Twitter! Why would you want to have any kind of property that you fully controlled on the internet?Fast forward to today, and most companies have seen the flaws in that argument. If your digital presence is how most of your customers find and interact with you, giving it over to some third party company with its own agenda is not going to serve you well. This morning, CNN's digital chief Meredith Artley says as much in an interview with Kara Swisher: going where your users are was a counterproductive startegy. You have to reach out to them and make spaces that they want to visit.But my hypothesis with Known wasn't just that people would want to own their own websites again, and that we should make it as easy to publish on their own site as it is to publish on social media. It was part of it, but I had something bigger in mind.Anyone who's building any kind of business - whether it's a media property, a brick and mortar store, a startup, or a food truck - knows that you have to understand your customers and meet their needs if you want to be successful. For most people, that means talking to them, again and again. When the New York Times first went online as part of AOL - before it even launched a website - the team took the opportunity to sit in the chat rooms and talk to people. The internet is a conversation, not a one-way broadcast medium, which\u00a0the Cluetrain Manifesto tried to tell us 20 years ago. And businesses all over the world are doing their best to talk to people on social media.But the same ownership principle applies. Just as companies realized that they need to own their online presence, they will begin realizing that the conversations they're having on third party social media platforms are templated for the benefit of those platforms. If they want to have deeper conversations, build trust and loyalty, and have a greater influence over the form of the discussion, then they need to own the conversation spaces, too. (And there's a lot to be said for not giving companies like Facebook all that insight data.)Tools that allow companies to build their own social spaces as easily as they can build their own websites are important. It's something I learned when I built Elgg, although that platform is very bound in the desktop-based MySpace era. Anyone should be able to start a space to have a social conversation in 5 minutes, in a way that they own the data and can customize it for their needs. But while existing tools like Mighty Networks (and Slack) or forum tools like Discourse are great for what they do, there aren't any great platforms that let people actually build a site that directly fits the community they want to build. All online communities tend to look the same. If we know that the form of a converation influences its content - and it does - then it becomes clear how counter-productive a one size fits all approach really is.And then the bigger picture is that if this idea is successful, moving from one monopolistic social network to lots of smaller communities loosely joined will make for a healthier internet.That was the vision for Known: to let anyone build easy to use social spaces that they control, and liberate online conversation in the process. First as a startup, and now as an open source project. We were a little early, and made some (recoverable) mistakes. But it's still a mission I believe in.",
"html": "<p>It sounds ludicrous now, but back in 2014, when I cofounded\u00a0<a href=\"https://withknown.com\">Known</a> as a startup, a lot of people were questioning whether a business even needed a website. Pockets of people - for example in <a href=\"https://indieweb.org\">the indieweb community</a>, which I enthusiastically joined - were pointing out how short-sighted this was, but it was a minority opinion. There was Facebook and Twitter! Why would you want to have any kind of property that you fully controlled on the internet?</p><p>Fast forward to today, and most companies have seen the flaws in that argument. If your digital presence is how most of your customers find and interact with you, giving it over to some third party company with its own agenda is not going to serve you well. This morning, <a href=\"https://www.recode.net/2019/1/14/18179291/meredith-artley-cnn-digital-facts-first-trump-media-kara-swisher-decode-podcast\">CNN's digital chief Meredith Artley says as much in an interview with Kara Swisher</a>: going where your users are was a counterproductive startegy. You have to reach out to them and make spaces that they want to visit.</p><p>But my hypothesis with Known wasn't just that people would want to own their own websites again, and that we should make it as easy to publish on their own site as it is to publish on social media. It was part of it, but I had something bigger in mind.</p><p>Anyone who's building any kind of business - whether it's a media property, a brick and mortar store, a startup, or a food truck - knows that you have to understand your customers and meet their needs if you want to be successful. For most people, that means talking to them, again and again. When the New York Times first went online as part of AOL - before it even launched a website - the team took the opportunity to sit in the chat rooms and talk to people. The internet is a conversation, not a one-way broadcast medium, which\u00a0<a href=\"http://www.cluetrain.com/\">the Cluetrain Manifesto</a> tried to tell us 20 years ago. And businesses all over the world are doing their best to talk to people on social media.</p><p>But the same ownership principle applies. Just as companies realized that they need to own their online presence, they will begin realizing that the conversations they're having on third party social media platforms are templated for the benefit of those platforms. If they want to have deeper conversations, build trust and loyalty, and have a greater influence over the <em>form</em> of the discussion, then they need to own the conversation spaces, too. (And there's a lot to be said for not giving companies like Facebook all that insight data.)</p><p>Tools that allow companies to build their own social spaces as easily as they can build their own websites are important. It's something I learned when I built Elgg, although that platform is very bound in the desktop-based MySpace era. Anyone should be able to start a space to have a social conversation in 5 minutes, in a way that they own the data and can customize it for their needs. But while existing tools like Mighty Networks (and Slack) or forum tools like Discourse are great for what they do, there aren't any great platforms that let people actually build a site that directly fits the community they want to build. All online communities tend to look the same. If we know that the form of a converation influences its content - and it does - then it becomes clear how counter-productive a one size fits all approach really is.</p><p>And then the bigger picture is that if this idea is successful, moving from one monopolistic social network to lots of smaller communities loosely joined will make for a healthier internet.</p><p>That was the vision for Known: to let anyone build easy to use social spaces that they control, and liberate online conversation in the process. First as a startup, <a href=\"https://github.com/idno/known\">and now as an open source project</a>. We were a little early, and made some (recoverable) mistakes. But it's still a mission I believe in.</p>"
},
"author": {
"type": "card",
"name": "Ben Werdm\u00fcller",
"url": "https://werd.io/profile/benwerd",
"photo": "https://aperture-proxy.p3k.io/78fd5896b799926517b28cef89e270537a205537/68747470733a2f2f776572642e696f2f66696c652f3536633462383138626564376465356235303766613261352f7468756d622e6a7067"
},
"post-type": "article",
"_id": "1812597",
"_source": "191",
"_is_read": true
}
This inline website editor by Grant is looking very exciting! Powered entirely by IndieWeb building blocks: microformats (to understand the content on your page) and micropub (to make new posts and edits).
{
"type": "entry",
"published": "2019-01-14T10:41:34-0500",
"url": "https://martymcgui.re/2019/01/14/104134/",
"category": [
"indieweb",
"publishing",
"tools"
],
"content": {
"text": "This inline website editor by Grant is looking very exciting! Powered entirely by IndieWeb building blocks: microformats (to understand the content on your page) and micropub (to make new posts and edits).\n\nhttps://grant.codes/2019/01/11/my-new-posting-workflow",
"html": "<p>This inline website editor by <a href=\"https://grant.codes/\">Grant</a> is looking very exciting! Powered entirely by <a href=\"https://indieweb.org/\">IndieWeb</a> building blocks: <a href=\"https://indieweb.org/microformats\">microformats</a> (to understand the content on your page) and <a href=\"https://indieweb.org/Micropub\">micropub</a> (to make new posts and edits).</p>\n\n<p><a href=\"https://grant.codes/2019/01/11/my-new-posting-workflow\">https://grant.codes/2019/01/11/my-new-posting-workflow</a></p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://aperture-proxy.p3k.io/8275f85e3a389bd0ae69f209683436fc53d8bad9/68747470733a2f2f6d617274796d636775692e72652f696d616765732f6c6f676f2e6a7067"
},
"post-type": "note",
"_id": "1811559",
"_source": "175",
"_is_read": true
}
My New Posting Workflow
Inline editing on my own website
{
"type": "entry",
"published": "2019-01-11T01:13:26.459Z",
"summary": "Inline editing on my own website",
"url": "https://grant.codes/2019/01/11/my-new-posting-workflow",
"syndication": [
"https://news.indieweb.org/en",
"https://twitter.com/grantcodes/status/1084574378845790208"
],
"name": "My New Posting Workflow",
"content": {
"text": "So I have been working away on some new features on my site for quite a while now and it looks like everything is about ready.Honestly I don't particularly enjoy writing long-form content, so it is kind of strange that I have really enjoyed working on this new functionality.The InspirationI was rather inspired by the new block editor in WordPress (a.k.a. Gutenberg), there has been a lot of talk about it - with many varying opinions. But what I think can be almost universally agreed on is that an editor that is a bit more flexible than just a single rich text box leads to much more engaging content.So with that in mind I set about first updating my own site to support long form articles in a much richer manner.The ArticlesSetting up an article view for my site was fairly straightforward. I wanted it to be about as simple as you could get.So this view you are looking at is pretty close to the default post view with a few changes:No topography background (cool, but distracting when reading)\nHidden navigation (minimalism ftw)\nThe content is centered and a bit wider than normal.\nAfter that I knew I wanted to support at least wide and full aligned content - much like WordPress, so I borrowed their .alignfull and .alignwide class names and added support for them on this view.The EditorNow here is the real challenge! I wanted a feature rich editor to run on the frontend of my site, and it turned out I was able to make an editor that has the potential to work for anyone with an indieweb site thanks to microformats.The editor looks for the microformats .p-name and .e-content classes, and injects itself into those elements.Core FeaturesInline editingYou can load the editor on you own site and uses the styles of your websiteMarkdown ShortcutsIf you start a paragraph with ### and a space it will turn that block into a h3, if you start with a > you get a blockquote, etc.BlocksThe editor has a fairly loose idea of blocks. They can be added using a / in a empty paragraph or some are automatically made when you drop a file into the editor. At the moment I have kept them fairly simple:Image block\nAudio block\nVideo block\nEmbed block\nAlignmentBlocks can be wide or full aligned (if you have the right css styles)MentionsYou can @mention IndieWeb people. Currently it is only people from the IndieWeb Directory, but in the future I'd like to make it work with users personal nickname caches.Other Micropub PropertiesI've enabled a decent set of other micropub properties in the sidebar.The FutureAlthough the PostrChild extension is fairly usable right now, I think it is a long way from complete, I've had a bunch of ideas I'd like to at least look into:Using nickname caches for mentions\nPotentially more block types - a code snippet and raw html block would probably be useful\nAuto saving posts as drafts\nMaybe a UI to list posts or drafts via micropub queries\nAbility to create a new post / reply from anywhere, without first needing to visit your site\nImprove user on-boarding\nFix some UX issues, like scrolling the cursor into view when at the bottom of the page and always having a blank paragraph available to type in.",
"html": "<p>So I have been working away on some new features on my site for quite a while now and it looks like everything is about ready.</p><p>Honestly I don't particularly enjoy writing long-form content, so it is kind of strange that I have really enjoyed working on this new functionality.</p><h2>The Inspiration</h2><p>I was rather inspired by the new block editor in WordPress (a.k.a. Gutenberg), there has been a lot of talk about it - with many varying opinions. But what I think can be almost universally agreed on is that an editor that is a bit more flexible than just a single rich text box leads to much more engaging content.</p><p>So with that in mind I set about first updating my own site to support long form articles in a much richer manner.</p><h2>The Articles</h2><p>Setting up an article view for my site was fairly straightforward. I wanted it to be about as simple as you could get.</p><p>So this view you are looking at is pretty close to the default post view with a few changes:</p><ul><li>No topography background (cool, but distracting when reading)</li>\n<li>Hidden navigation (minimalism ftw)</li>\n<li>The content is centered and a bit wider than normal.</li>\n</ul><p>After that I knew I wanted to support at least wide and full aligned content - much like WordPress, so I borrowed their .alignfull and .alignwide class names and added support for them on this view.</p><h2>The Editor</h2><p>Now here is the real challenge! I wanted a feature rich editor to run on the frontend of my site, and it turned out I was able to make an editor that has the potential to work for anyone with an indieweb site thanks to microformats.</p><p>The editor looks for the microformats .p-name and .e-content classes, and injects itself into those elements.</p><h3>Core Features</h3><h4>Inline editing</h4><p>You can load the editor on you own site and uses the styles of your website</p><h4>Markdown Shortcuts</h4><p>If you start a paragraph with ### and a space it will turn that block into a h3, if you start with a > you get a blockquote, etc.</p><img alt=\"\" src=\"https://aperture-proxy.p3k.io/2a7d02b191f1d67f414459c117fcf5e8e54ba295/68747470733a2f2f6772616e742e636f6465732f6d656469612f323031392f30312f31332f6d61726b646f776e2d73686f7274637574732e676966\" /><h4>Blocks</h4><p>The editor has a fairly loose idea of blocks. They can be added using a / in a empty paragraph or some are automatically made when you drop a file into the editor. At the moment I have kept them fairly simple:</p><ol><li>Image block</li>\n<li>Audio block</li>\n<li>Video block</li>\n<li>Embed block</li>\n</ol><img alt=\"\" src=\"https://aperture-proxy.p3k.io/6d88a815a9af7922260fb190a5c3f2446c48d386/68747470733a2f2f6772616e742e636f6465732f6d656469612f323031392f30312f31332f6f656d6265642d626c6f636b2d312e676966\" /><h4>Alignment</h4><p>Blocks can be wide or full aligned (if you have the right css styles)</p><img alt=\"\" src=\"https://aperture-proxy.p3k.io/dcb769315166a1339670efd951530288a1d6dddd/68747470733a2f2f6772616e742e636f6465732f6d656469612f323031392f30312f31332f616c69676e6d656e742e676966\" /><h4>Mentions</h4><p>You can @mention IndieWeb people. Currently it is only people from the IndieWeb Directory, but in the future I'd like to make it work with users personal nickname caches.</p><img alt=\"\" src=\"https://aperture-proxy.p3k.io/f2d8313a31707f46239f51243815cacc2df393b5/68747470733a2f2f6772616e742e636f6465732f6d656469612f323031392f30312f31332f6d656e74696f6e732e676966\" /><h4>Other Micropub Properties</h4><p>I've enabled a decent set of other micropub properties in the sidebar.</p><h3>The Future</h3><p>Although the PostrChild extension is fairly usable right now, I think it is a long way from complete, I've had a bunch of ideas I'd like to at least look into:</p><ul><li>Using nickname caches for mentions</li>\n<li>Potentially more block types - a code snippet and raw html block would probably be useful</li>\n<li>Auto saving posts as drafts</li>\n<li>Maybe a UI to list posts or drafts via micropub queries</li>\n<li>Ability to create a new post / reply from anywhere, without first needing to visit your site</li>\n<li>Improve user on-boarding</li>\n<li>Fix some UX issues, like scrolling the cursor into view when at the bottom of the page and always having a blank paragraph available to type in.</li>\n</ul>"
},
"author": {
"type": "card",
"name": "Grant Richmond",
"url": "https://grant.codes",
"photo": "https://aperture-proxy.p3k.io/be31049af9884a65289b2d14300adafc0e4030c6/68747470733a2f2f6772616e742e636f6465732f696d672f6d652e6a7067"
},
"post-type": "article",
"_id": "1805260",
"_source": "11",
"_is_read": true
}
Tracking My Movie, TV, and Podcast Activity
{
"type": "entry",
"published": "2019-01-13T21:27:40+00:00",
"url": "https://cleverdevil.io/2019/tracking-my-movie-tv-and-podcast-activity",
"category": [
"IndieWeb",
"indienews",
"https://news.indieweb.org/en"
],
"syndication": [
"https://twitter.com/cleverdevil/status/1084563105080844291"
],
"name": "Tracking My Movie, TV, and Podcast Activity",
"content": {
"text": "As part of my continuing efforts to preserve and capture my memories, I\u2019ve been spending some energy adding more capabilities to my website. I already capture photos, recipes, blog posts, status updates, and other more traditional types of content. In addition, I\u2019ve been privately tracking my own location continuously for months now, including the ability to see some current details about my location and status. I also use the excellent OwnYourSwarm service from Aaron Parecki to record check-ins at specific locations on my site.Last week, I realized that I was missing some data on my website that would add additional context when exploring my memories: my TV and movie watching history, and a record of what podcasts I listen to. As of today, I am now automatically tracking all of this data, and I\u2019m happy to share a bit about how I made it happen.Movies and TVLet\u2019s start with how I am tracking what movies and TV shows I watch. As it turns out, there is already a wonderful service out there for tracking this data called Trakt, which is a startup based out of San Diego. Trakt has done the hard part for me, with an extensive and complete database of movies and TV shows for me to pull from, and a host of great apps that use its powerful API to help users put data into their Trakt account. I am personally using the Watcht app for iOS to manually ad TV episodes and movies to my watch history on Trakt, and to show me a calendar of upcoming TV episodes for my favorite shows.But, being an IndieWeb community member, I want to make sure that my memories don\u2019t get lost in the event that Trakt goes away one day. In addition, I want to be able to see my TV and movie history in the context of the rest of my website\u2019s content. So, I needed to find a way to automatically sync that data to my website.At first, I thought about using the extremely capable Trakt API to periodically sync to my website, but then I noticed that Trakt Pro members get access to an Atom feed of their watch history. Working with a custom REST API takes a lot of effort, while integrating with a standard feed format is extremely easy. So, I happily paid for a Trakt Pro subscription!I created a Python script which periodically parses my Trakt feed and then creates entries on my website for each movie and TV episode I watch. It only took me about an hour to put the whole thing together.Sidebar: Automatic Tracking from PlexAs you may already know, I have a great collection of digital movies and TV shows. I use the outstanding Plex Media Server to enable me to stream and sync content to all my devices. As Eddie, my co-host from Two Dads Talking, recently mused, tracking activity automatically is much more reliable than remembering to manually track activity. Trakt provides a Plex plugin that automatically syncs your Plex history to Trakt, and once I had that installed, a significant chunk of my activity is now automatically synced!I still have to manually track content watched outside of Plex, like live TV from Hulu, and content consumed on Netflix, but it\u2019s a good start.PodcastsI\u2019m not only a podcaster with a microcast and a podcast, I\u2019m also an avid podcast listener. I listen to podcasts on my daily commute, to relax after work, and to kill time on airplanes. Wouldn\u2019t it be great to have that history tracked on my website as well? As I mentioned above, tracking that history automatically is greatly preferable to manually having to log every episode I listen to. With that in mind, I set out to see if I could capture my activity.I use the wonderful Overcast podcast app for iOS. Overcast is created by Marco Arment, who is also a prolific podcaster. It\u2019s a fantastic and pleasant app to use, and is perhaps my favorite iOS app ever. Overcast has a sync service and web frontend available for users at overcast.fm. Not only can you listen to podcasts in your web browser on overcast.fm, you can also export an extended OPML file that contains all details about your account, including a listing of all podcast episodes you\u2019ve ever listened to. Bingo!I whipped up a script that logs into my account at Overcast.fm, then downloads a copy of this OPML file, and uses it to sync my history to my website. It works a treat, but I will caution that Marco seems to be rate limiting that OPML export pretty aggressively. For the time being, I\u2019ve limited my sync to once daily, and I\u2019ve also contacted Marco to get his input on how I am using his service. In an ideal world, I\u2019d love to see Marco add a standard RSS, Atom, or JSON Feed for Overcast paid subscribers similar to what Trakt has done for Trakt Pro users. In the meantime, I\u2019ll be conservative about how often I sync and await a reply from Marco.Why Track Activity?You may be wondering why I want to track all of this information. Eddie and I briefly touched on the topic in the last episode of Two Dads Talking, but it really comes down to the fact that our memories are precious, and the more context I have when looking back on my life, the richer my appreciation will be for the life I\u2019ve been blessed to live.During the process of adding these new types of memories to my website, I also have added a monthly \u201crecap\u201d feature which has been one of my all time favorite enhancements. I like them so much, I\u2019ve added links to the last twelve monthly summaries to my home page to surface them. My favorite examples of monthly summaries so far:\nJanuary 2018, which marked my departure from DreamHost, the beginning of a new chapter in my career, and my second viewing of my favorite musical of all time.\n\nJuly 2018, which includes travel all over the globe, some progress on my Indiepaper project, and outdoor movies in my front yard with my kids.\n\nNovember 2017, which includes a trip to Australia, the acquisition of the best car I\u2019ve ever owned, and my son\u2019s first ever NFL football game.\nI\u2019m delighted to continue enriching my database of memories, and really happy with the way my movie, TV, and podcast tracking is shaping up so far.#IndieWeb#indienews",
"html": "<p>As part of my continuing efforts to preserve and capture my memories, I\u2019ve been spending some energy adding more capabilities to my website. I already capture <a href=\"https://cleverdevil.io/photos\">photos</a>, <a href=\"https://cleverdevil.io/content/recipes/\">recipes</a>, <a href=\"https://cleverdevil.io/content/posts/\">blog posts</a>, <a href=\"https://cleverdevil.io/content/statusupdates/\">status updates</a>, and other more traditional types of content. In addition, I\u2019ve been privately tracking my own location continuously for months now, including the ability to see some <a href=\"https://cleverdevil.io/now\">current details about my location and status</a>. I also use the excellent <a href=\"https://ownyourswarm.p3k.io\">OwnYourSwarm</a> service from <a href=\"https://aaronparecki.com\">Aaron Parecki</a> to record <a href=\"https://cleverdevil.io/content/locations/\">check-ins at specific locations on my site</a>.</p><p>Last week, I realized that I was missing some data on my website that would add additional context when exploring my memories: my TV and movie watching history, and a record of what podcasts I listen to. As of today, I am now automatically tracking all of this data, and I\u2019m happy to share a bit about how I made it happen.</p><h2>Movies and TV</h2><p>Let\u2019s start with how I am tracking what movies and TV shows I watch. As it turns out, there is already a wonderful service out there for tracking this data called <a href=\"https://trakt.tv/\">Trakt</a>, which is a startup based out of San Diego. Trakt has done the hard part for me, with an extensive and complete database of movies and TV shows for me to pull from, and a <a href=\"https://trakt.tv/apps\">host of great apps</a> that use its <a href=\"https://trakt.docs.apiary.io/\">powerful API</a> to help users put data into their Trakt account. I am personally using the <a href=\"https://itunes.apple.com/us/app/watcht/id1396920723\">Watcht app for iOS</a> to manually ad TV episodes and movies to my watch history on Trakt, and to show me a calendar of upcoming TV episodes for my favorite shows.</p><p>But, being an <a href=\"https://indieweb.org\">IndieWeb</a> community member, I want to make sure that my memories don\u2019t get lost in the event that Trakt goes away one day. In addition, I want to be able to see my TV and movie history in the context of the rest of my website\u2019s content. So, I needed to find a way to automatically sync that data to my website.</p><p>At first, I thought about using the extremely capable Trakt API to periodically sync to my website, but then I noticed that Trakt Pro members get access to an Atom feed of their watch history. Working with a custom REST API takes a lot of effort, while integrating with a standard feed format is extremely easy. So, I happily paid for a Trakt Pro subscription!</p><p>I created <a href=\"https://gist.github.com/cleverdevil/d6290a023c28bd8f6aee4ef136a3ba98\">a Python script which periodically parses my Trakt feed and then creates entries on my website</a> for each movie and TV episode I watch. It only took me about an hour to put the whole thing together.</p><h3>Sidebar: Automatic Tracking from Plex</h3><p>As you may already know, I have a great collection of digital movies and TV shows. I use the outstanding <a href=\"https://www.plex.tv\">Plex Media Server</a> to enable me to stream and sync content to all my devices. As <a href=\"https://eddiehinkle.com\">Eddie</a>, my co-host from <a href=\"https://twodads.fm\">Two Dads Talking</a>, recently mused, <a href=\"https://eddiehinkle.com/2019/01/11/30/article/\">tracking activity automatically is much more reliable than remembering to manually track activity</a>. <a href=\"https://github.com/trakt/Plex-Trakt-Scrobbler\">Trakt provides a Plex plugin that automatically syncs your Plex history to Trakt</a>, and once I had that installed, a significant chunk of my activity is now automatically synced!</p><p>I still have to manually track content watched outside of Plex, like live TV from Hulu, and content consumed on Netflix, but it\u2019s a good start.</p><h2>Podcasts</h2><p>I\u2019m not only a podcaster with a <a href=\"http://cleverca.st\">microcast</a> and a <a href=\"https://twodads.fm\">podcast</a>, I\u2019m also an avid podcast listener. I listen to podcasts on my daily commute, to relax after work, and to kill time on airplanes. Wouldn\u2019t it be great to have that history tracked on my website as well? As I mentioned above, tracking that history automatically is greatly preferable to manually having to log every episode I listen to. With that in mind, I set out to see if I could capture my activity.</p><p>I use the wonderful <a href=\"https://overcast.fm\">Overcast podcast app for iOS</a>. Overcast is created by <a href=\"https://marco.org\">Marco Arment</a>, who is also a prolific podcaster. It\u2019s a fantastic and pleasant app to use, and is perhaps my favorite iOS app ever. Overcast has a sync service and web frontend available for users at <a href=\"https://overcast.fm\">overcast.fm</a>. Not only can you listen to podcasts in your web browser on overcast.fm, you can also export an extended OPML file that contains all details about your account, including a listing of all podcast episodes you\u2019ve ever listened to. Bingo!</p><p>I whipped up <a href=\"https://gist.github.com/cleverdevil/a8215850420493c1ee06364161e281c0\">a script that logs into my account at Overcast.fm, then downloads a copy of this OPML file, and uses it to sync my history to my website</a>. It works a treat, but I will caution that Marco seems to be rate limiting that OPML export pretty aggressively. For the time being, I\u2019ve limited my sync to once daily, and I\u2019ve also contacted Marco to get his input on how I am using his service. In an ideal world, I\u2019d love to see Marco add a standard RSS, Atom, or JSON Feed for Overcast paid subscribers similar to what Trakt has done for Trakt Pro users. In the meantime, I\u2019ll be conservative about how often I sync and await a reply from Marco.</p><h2>Why Track Activity?</h2><p>You may be wondering why I want to track all of this information. Eddie and I briefly touched on the topic in the <a href=\"https://twodads.fm/2019/01/10/episode-im-not.html\">last episode of Two Dads Talking</a>, but it really comes down to the fact that our memories are precious, and the more context I have when looking back on my life, the richer my appreciation will be for the life I\u2019ve been blessed to live.</p><p>During the process of adding these new types of memories to my website, I also have added a monthly \u201crecap\u201d feature which has been one of my all time favorite enhancements. I like them so much, I\u2019ve added links to the last twelve monthly summaries to my home page to surface them. My favorite examples of monthly summaries so far:</p><ul><li>\n<a href=\"https://cleverdevil.io/summary/2018/1\">January 2018</a>, which marked my departure from DreamHost, the beginning of a new chapter in my career, and my second viewing of my favorite musical of all time.</li>\n<li>\n<a href=\"https://cleverdevil.io/summary/2018/7\">July 2018</a>, which includes travel all over the globe, some progress on my Indiepaper project, and outdoor movies in my front yard with my kids.</li>\n<li>\n<a href=\"https://cleverdevil.io/summary/2017/11\">November 2017</a>, which includes a trip to Australia, the acquisition of the best car I\u2019ve ever owned, and my son\u2019s first ever NFL football game.</li>\n</ul><p>I\u2019m delighted to continue enriching my database of memories, and really happy with the way my movie, TV, and podcast tracking is shaping up so far.</p><p><a href=\"https://cleverdevil.io/tag/IndieWeb\" class=\"p-category\">#IndieWeb</a></p><p><a class=\"u-category\" href=\"https://news.indieweb.org/en\"></a><a href=\"https://cleverdevil.io/tag/indienews\" class=\"p-category\">#indienews</a></p>"
},
"author": {
"type": "card",
"name": "Jonathan LaCour",
"url": "https://cleverdevil.io/profile/cleverdevil",
"photo": "https://aperture-proxy.p3k.io/77e5d6e5871324c43aebf2e3e7a5553e14578f66/68747470733a2f2f636c65766572646576696c2e696f2f66696c652f66646263373639366135663733383634656131316138323863383631653133382f7468756d622e6a7067"
},
"post-type": "article",
"_id": "1804243",
"_source": "71",
"_is_read": true
}
Registration is open for IndieWebCamp Austin. February 23-24.
{
"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/11/registration-is-open.html",
"content": {
"html": "<p><a href=\"https://2019.indieweb.org/austin\">Registration is open</a> for IndieWebCamp Austin. February 23-24.</p>",
"text": "Registration is open for IndieWebCamp Austin. February 23-24."
},
"published": "2019-01-11T17:03:35-06:00",
"post-type": "note",
"_id": "1793205",
"_source": "12",
"_is_read": true
}
Disappearing content makes me depressed
{
"type": "entry",
"published": "2019-01-09T22:22:42+03:00",
"url": "https://fireburn.ru/post/1547061762",
"category": [
"indieweb",
"corporateweb",
"stories"
],
"name": "Disappearing content makes me depressed",
"content": {
"text": "Recently I've noticed that all sorts of ephemeral content (that is gaining traction in the current world, sadly) - be it Instagram Stories (especially videos since they can't be just screenshoot), Snapchat messages (it's its selling point) or some weird stuff like MTS's \"\u0414\u043e\u0441\u0442\u0443\u043f\" (\"Access\") exhibit and its ads (about content with limited access that may disappear or something) littering the infospace and my VKontakte feed (the only service besides Instagram I still access directly rather than via my reader) clutters up my mind with anxiety. I like content. I like good content. But I'm anxious about losing data and losing access to that content.\nFear of losing something is a part of human psychology (and as I seem to be one of Homo Sapiens, it affects me too). And disappearing content stimulates that fear, leading to more engagement with corporate apps that guard access to the content. Take Instagram stories, for example - there is no API, there is no way to read these in a user-controlled environment, and all of it disappears within 24 hours of being posted! The lack of API seems to be exactly for enforcing these rules - because if Instagram would let others hit its API (which does not exist at all right now - thank you Facebook) - oh no, they could save a story on their hard drives! or even archive them somewhere! oh no this is so scary! (it isn't)\nThis drives users to constantly check their Instagram app for people's new stories. What if Instagram set the \"story\" content lifetime to only one hour? It would drive you mad, wouldn't it? so thanks people who invented that concept for at least not driving users completely insane. But it still does bad things (at least with me).\nThere could be a solution - do not use stories at all! But then you'll miss things because other people do use \"stories\"\u00a0to get their content online. So for now in this struggle around this \"feature\"\u00a0the only winners are corporations.\nPlease don't use stories. Don't help corporations drive people like me insane.",
"html": "<p>Recently I've noticed that all sorts of ephemeral content (that is gaining traction in the current world, sadly) - be it Instagram Stories (especially videos since they can't be just screenshoot), Snapchat messages (it's its selling point) or some weird stuff like MTS's \"\u0414\u043e\u0441\u0442\u0443\u043f\" (\"Access\") exhibit and its ads (about content with limited access that may disappear or something) littering the infospace and my VKontakte feed (the only service besides Instagram I still access directly rather than via my reader) clutters up my mind with anxiety. I like content. I like good content. But I'm anxious about losing data and losing access to that content.</p>\n<p>Fear of losing something is a part of human psychology (and as I seem to be one of <i>Homo Sapiens</i>, it affects me too). And disappearing content stimulates that fear, leading to more engagement with corporate apps that guard access to the content. Take Instagram stories, for example - there is no API, there is no way to read these in a user-controlled environment, and all of it disappears within 24 hours of being posted! The lack of API seems to be exactly for enforcing these rules - because if Instagram would let others hit its API (which does not exist at all right now - <i>thank you Facebook</i>) - oh no, they could save a story on their hard drives! or even archive them somewhere! <i>oh no this is so scary! (it isn't)</i></p>\n<p>This drives users to constantly check their Instagram app for people's new stories. What if Instagram set the \"story\" content lifetime to only one hour? It would drive you mad, wouldn't it? so thanks people who invented that concept for at least not driving users completely insane. But it still does bad things (at least with me).</p>\n<p>There could be a solution - do not use stories at all! But then you'll miss things because other people <b>do use \"stories\"</b>\u00a0to get their content online. So for now in this struggle around this <i>\"feature\"</i>\u00a0the only winners are corporations.</p>\n<p>Please don't use stories. Don't help corporations drive people like me insane.</p>"
},
"author": {
"type": "card",
"name": "Vika",
"url": "https://fireburn.ru/",
"photo": "https://aperture-proxy.p3k.io/3baa9a034ae34d783c6de676c0304b7640673c03/68747470733a2f2f666972656275726e2e72752f617661746172732f76696b612e706e67"
},
"post-type": "article",
"_id": "1775444",
"_source": "1371",
"_is_read": true
}
Homebrew Website Club is tonight in Austin! 6:30pm at Mozart’s Coffee. Join us for a coffee and chat about the IndieWeb and plans for IndieWebCamp Austin. (Which will be February 23-24… Registration open soon.)
{
"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
}
Decided to re-activate my @Flickr Pro.
New owner @SmugMug has been around for years and is passionate about photos. They’ve 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/
One example: “We are actively saving accounts for photographers who are no longer with us”.
Dear @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’m sure there are many more early Flickr users who have since passed away. Please speak-up if you know of any.
Flickr 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.
I have more positive thoughts about @Flickr’s future potential with its new owners, especially with respect to even better IndieWeb integration. More on that later. For now, see the additional research and links being collected and documented by the IndieWeb Community:
https://indieweb.org/Flickr
And if you also decide to upgrade your Flickr account to Pro, there’s a 15% off code (FLICKRPRO15) that’s good until 2019-015.
New owner @SmugMug has been around for years and is passionate about photos. They’ve 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/
One example: “We are actively saving accounts for photographers who are no longer with us”.
Dear @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’m sure there are many more early Flickr users who have since passed away. Please speak-up if you know of any.
Flickr 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.
I have more positive thoughts about @Flickr’s future potential with its new owners, especially with respect to even better IndieWeb integration. More on that later. For now, see the additional research and links being collected and documented by the IndieWeb Community:
https://indieweb.org/Flickr
And if you also decide to upgrade your Flickr account to Pro, there’s a 15% off code (FLICKRPRO15) that’s good until 2019-015.
{
"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 & 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 "Pfefferles OpenWeb" 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 <span class='p-author h-card'>Author</span></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!
17:30: Optional writing hour and quiet socializing
18:30: IndieWeb demos and hack night!
Homebrew Website Club retro 1980s-style logo
Topics for this week: First Homebrew Website Club meetup of 2019! Year-end hack projects 2018 IndieWeb Challenge completed! Flickr with new owner — aligning with IndieWeb principles? Demos of personal website breakthroughs Create or update your personal web site!
Join a community with like-minded interests. Bring friends that want a personal site, or are interested in a healthy, independent web!
Any questions? Ask in #indieweb Slack or IRC
More information: IndieWeb Wiki Event Page
RSVP: post an indie RSVP on your own site!
{
"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
}