đź”– Bookmarked How I turned my Goodreads data into a self-hosted website with Eleventy https://hiddedevries.nl/en/blog/2021-01-04-how-i-turned-my-goodreads-data-into-a-self-hosted-website-with-eleventy
{
"type": "entry",
"published": "2021-01-07T18:17:46-0500",
"summary": "\ud83d\udd16 Bookmarked How I turned my Goodreads data into a self-hosted website with Eleventy https://hiddedevries.nl/en/blog/2021-01-04-how-i-turned-my-goodreads-data-into-a-self-hosted-website-with-eleventy",
"url": "https://martymcgui.re/2021/01/07/how-i-turned-my-goodreads-data-into-a-self-hosted-website-with-eleventy/",
"category": [
"goodreads",
"IndieWeb",
"ownyourdata"
],
"bookmark-of": [
"https://hiddedevries.nl/en/blog/2021-01-04-how-i-turned-my-goodreads-data-into-a-self-hosted-website-with-eleventy"
],
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "bookmark",
"_id": "17567148",
"_source": "175",
"_is_read": true
}
{
"type": "entry",
"published": "2021-01-06T10:13:25-08:00",
"url": "https://aaronparecki.com/2021/01/06/7/indieweb",
"category": [
"indieweb"
],
"syndication": [
"https://twitter.com/aaronpk/status/1346882587000664064"
],
"content": {
"text": "Live now! \ud83c\udf99 @allie_nimmons and @DavidWolfpaw chatting all about the #IndieWeb! https://youtu.be/i6Ixyi_I9g4",
"html": "Live now! \ud83c\udf99 <a href=\"https://twitter.com/allie_nimmons\">@allie_nimmons</a> and <a href=\"https://twitter.com/DavidWolfpaw\">@DavidWolfpaw</a> chatting all about the <a href=\"https://aaronparecki.com/tag/indieweb\">#IndieWeb</a>! <a href=\"https://youtu.be/i6Ixyi_I9g4\"><span>https://</span>youtu.be/i6Ixyi_I9g4</a>"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/41061f9de825966faa22e9c42830e1d4a614a321213b4575b9488aa93f89817a.jpg"
},
"post-type": "note",
"_id": "17527851",
"_source": "16",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": null,
"url": "https://dri.es/",
"photo": null
},
"url": "https://dri.es/can-someone-add-some-more-html-tags-please",
"published": "2021-01-06T04:39:12-05:00",
"content": {
"html": "<p>Every day, millions of new web pages are added to the internet. Most of them are unstructured, uncategorized, and nearly impossible for software to understand. It irks me.</p>\n\n<p>Look no further than <a href=\"https://en.wikipedia.org/wiki/Tim_Berners-Lee\">Sir Tim Berners-Lee's Wikipedia page</a>:</p>\n\n\n<img src=\"https://dri.es/files/images/blog/wikipedia-timbl-markup.png\" alt=\"The markup for Tim Berners-Lee's Wikipedia page; it's complex and inconsistent\" title=\"Tim Berners-Lee's Wikipedia page: HMTL code\" /><em>What Wikipedia editors write (<a href=\"https://en.wikipedia.org/w/index.php?title=Tim_Berners-Lee&action=edit\">source</a>).</em><img src=\"https://dri.es/files/images/blog/wikipedia-timbl-page.png\" alt=\"The browser output for Tim Berners-Lee's Wikipedia page\" title=\"Tim Berners-Lee's Wikipedia page: rendered page\" /><em>What visitors of Wikipedia see.</em><p>At first glance, there is <a href=\"http://blog.spencermounta.in/2019/wikipedias-in-trouble/index.html\">no rhyme or reason to Wikipedia's markup</a>. (Wikipedia also has <a href=\"https://en.wikipedia.org/wiki/Help:WikiHiero_syntax\">custom markup for hieroglyphs</a>, which admittedly <em>is</em> pretty cool.)</p>\n\n<p>The problem? Wikipedia is the world's largest source of knowledge. It's a top 10 website in the world. Yet, Wikipedia's markup language is <a href=\"http://blog.spencermounta.in/2019/wikipedias-in-trouble/index.html\">nearly impossible to parse</a>, Tim Berners-Lee's Wikipedia page has <a href=\"https://validator.w3.org/nu/?doc=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FTim_Berners-Lee\">almost 100 HTML validation errors</a>, and the page's generated HTML output is not very semantic. It's hard to use or re-use with other software.</p>\n\n<p>I bet it irks Sir Tim Berners-Lee too.</p>\n\n\n<img src=\"https://dri.es/files/images/blog/wikipedia-timbl-markup.png\" alt=\"The markup for Tim Berners-Lee's Wikipedia page; it's complex and inconsistent\" title=\"Tim Berners-Lee's Wikipedia page: HMTL code\" /><em>What Wikipedia editors write (<a href=\"https://en.wikipedia.org/w/index.php?title=Tim_Berners-Lee&action=edit\">source</a>).</em><img src=\"https://dri.es/files/images/blog/wikipedia-timbl-html.png\" alt=\"The generated HTML code for Tim Berners-Lee's Wikipedia page; it could be more semantic\" title=\"Tim Berners-Lee's Wikipedia page: generated HTML code\" /><em>What the browser sees; the HTML code Wikipedia (MediaWiki) generates.</em><p>It's not just Wikipedia. Every site is still messing around with custom <code>s for a table of contents, footnotes, logos, and more. I could think of a dozen new HTML tags that would make web pages, including Wikipedia, easier to write and reuse: , , , and many more.\n\n</code></p><p><code>A good approach would be to take the most successful <a href=\"https://en.wikipedia.org/wiki/Schema.org\">Schema.org schemas</a>, <a href=\"http://microformats.org/\">Microformats</a> and <a href=\"https://en.wikipedia.org/wiki/Web_Components\">Web Components</a>, and incorporate their functionality into the <a href=\"https://html.spec.whatwg.org/\">official HTML specification</a>.</code></p><code>\n\n</code><p><code>Adding new semantic markup options to <em>the</em> HTML specification is the surest way to improve the semantic web, improve content reuse, and advance content authoring tools.</code></p><code> \n\n</code><p><code>Unfortunately, I don't see new tags being introduced. I don't see experiments with <a href=\"https://en.wikipedia.org/wiki/Web_Components\">Web Components</a> being promoted to official standards. I hope I'm wrong! (<a href=\"https://meta.wikimedia.org/wiki/Cunningham%27s_Law\">Cunningham's Law</a> states that <q>the best way to get the right answer on the internet is not to ask a question; it's to post the wrong answer</q>. If I'm wrong, I'll update this poost.)</code></p><code>\n \n</code><p><code>If you want to help make the web better, you could literally start with <a href=\"https://en.wikipedia.org/wiki/Tim_Berners-Lee\">Sir Tim Berners-Lee's Wikipedia page</a>, and use it as the basis to spend a decade <a href=\"https://github.com/whatwg/html/commits\">pushing for HTML markup improvements</a>. It could be the <a href=\"http://1997.webhistory.org/www.lists/www-talk.1993q1/0182.html\">start of a long and successful career</a>.</code></p><code></code>",
"text": "Every day, millions of new web pages are added to the internet. Most of them are unstructured, uncategorized, and nearly impossible for software to understand. It irks me.\n\nLook no further than Sir Tim Berners-Lee's Wikipedia page:\n\n\nWhat Wikipedia editors write (source).What visitors of Wikipedia see.At first glance, there is no rhyme or reason to Wikipedia's markup. (Wikipedia also has custom markup for hieroglyphs, which admittedly is pretty cool.)\n\nThe problem? Wikipedia is the world's largest source of knowledge. It's a top 10 website in the world. Yet, Wikipedia's markup language is nearly impossible to parse, Tim Berners-Lee's Wikipedia page has almost 100 HTML validation errors, and the page's generated HTML output is not very semantic. It's hard to use or re-use with other software.\n\nI bet it irks Sir Tim Berners-Lee too.\n\n\nWhat Wikipedia editors write (source).What the browser sees; the HTML code Wikipedia (MediaWiki) generates.It's not just Wikipedia. Every site is still messing around with custom s for a table of contents, footnotes, logos, and more. I could think of a dozen new HTML tags that would make web pages, including Wikipedia, easier to write and reuse: , , , and many more.\n\nA good approach would be to take the most successful Schema.org schemas, Microformats and Web Components, and incorporate their functionality into the official HTML specification.\n\nAdding new semantic markup options to the HTML specification is the surest way to improve the semantic web, improve content reuse, and advance content authoring tools. \n\nUnfortunately, I don't see new tags being introduced. I don't see experiments with Web Components being promoted to official standards. I hope I'm wrong! (Cunningham's Law states that the best way to get the right answer on the internet is not to ask a question; it's to post the wrong answer. If I'm wrong, I'll update this poost.)\n \nIf you want to help make the web better, you could literally start with Sir Tim Berners-Lee's Wikipedia page, and use it as the basis to spend a decade pushing for HTML markup improvements. It could be the start of a long and successful career."
},
"name": "Can someone add some more HTML tags, please?",
"post-type": "article",
"_id": "17522110",
"_source": "238",
"_is_read": true
}
{
"type": "entry",
"published": "2021-01-05T12:26:11.552Z",
"url": "https://www.jvt.me/mf2/2021/01/iniue/",
"category": [
"homebrew-website-club"
],
"content": {
"text": "Reminder that it's #HomebrewWebsiteClub Nottingham tomorrow! I hope to see you there at 1730 for some website stuff! https://events.indieweb.org/2021/01/homebrew-website-club-nottingham-rVrKwhxmCz4D",
"html": "<p>Reminder that it's <a href=\"https://www.jvt.me/tags/homebrew-website-club/\">#HomebrewWebsiteClub</a> Nottingham tomorrow! I hope to see you there at 1730 for some website stuff! <a href=\"https://events.indieweb.org/2021/01/homebrew-website-club-nottingham-rVrKwhxmCz4D\">https://events.indieweb.org/2021/01/homebrew-website-club-nottingham-rVrKwhxmCz4D</a></p>"
},
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "note",
"_id": "17496520",
"_source": "2169",
"_is_read": true
}
A rant from Robin. I share his frustration and agree with his observations.
I wonder how we can get the best of both worlds here: the ease of publishing newsletters, with all the beauty and archivability of websites.
{
"type": "entry",
"published": "2021-01-04T18:29:51Z",
"url": "https://adactio.com/links/17735",
"category": [
"newsletters",
"publishing",
"indieweb",
"rss",
"notifications",
"payments",
"subscriptions",
"writing",
"sharing",
"rant"
],
"bookmark-of": [
"https://www.robinrendle.com/essays/newsletters"
],
"content": {
"text": "Robin Rendle \u203a Newsletters\n\n\n\nA rant from Robin. I share his frustration and agree with his observations.\n\n\n I wonder how we can get the best of both worlds here: the ease of publishing newsletters, with all the beauty and archivability of websites.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://www.robinrendle.com/essays/newsletters\">\nRobin Rendle \u203a Newsletters\n</a>\n</h3>\n\n<p>A rant from Robin. I share his frustration and agree with his observations.</p>\n\n<blockquote>\n <p>I wonder how we can get the best of both worlds here: the ease of publishing newsletters, with all the beauty and archivability of websites.</p>\n</blockquote>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "bookmark",
"_id": "17481383",
"_source": "2",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "fluffy",
"url": "http://beesbuzz.biz/",
"photo": null
},
"url": "http://beesbuzz.biz/blog/11795-2021-goals",
"published": "2021-01-01T13:14:19-08:00",
"content": {
"html": "<p>Let\u2019s not call them resolutions.</p><p>One year ago I <a href=\"http://beesbuzz.biz/blog/7306-Happy-2020\">set out some goals for the next decade</a>. They\u2019re all pretty good goals. But here\u2019s some specific things I\u2019d like to accomplish over the next year:</p>\n<ul><li>Get my voice to a spot where people don\u2019t misgender me quite so much</li>\n<li>Get my fibromyalgia and ADHD meds dialed in (so far so good)</li>\n<li>Actually finish my next non-Novembeat album<a href=\"http://beesbuzz.biz/blog/11795-2021-goals#d_e11795_fn1\">1</a></li>\n<li><a href=\"https://plaidweb.site/\">PlaidWeb</a> things, such as:\n\n<ul><li>An online post editor</li>\n<li>A self-hosted notification engine (for webmention, activitypub, websub, etc.)</li>\n<li>Maybe actually write some actual <em>code</em> for Subl?</li>\n<li>Also maybe actually put a dang site together for PlaidWeb</li>\n</ul></li>\n<li>Rebuild my broken social life</li>\n<li>Get my home clean, and <em>keep</em> it clean</li>\n<li>Start drawing comics regularly again</li>\n<li>And the ever-present goal of losing, say, 15 pounds</li>\n</ul><p>Kind of ambitious, I know, but it\u2019s better to aim for the stars and hit the moon than to never even leave the ground.</p>\n\n\n\n\n<ol><li><p>I've been meaning to finish this album \"real soon\" for the last 5 years so I'm not terribly optimistic about this one <a href=\"http://beesbuzz.biz/blog/11795-2021-goals#r_e11795_fn1\">\u21a9</a></p></li></ol><p><a href=\"http://beesbuzz.biz/blog/11795-2021-goals#comments\">comments</a></p>",
"text": "Let\u2019s not call them resolutions.One year ago I set out some goals for the next decade. They\u2019re all pretty good goals. But here\u2019s some specific things I\u2019d like to accomplish over the next year:\nGet my voice to a spot where people don\u2019t misgender me quite so much\nGet my fibromyalgia and ADHD meds dialed in (so far so good)\nActually finish my next non-Novembeat album1\nPlaidWeb things, such as:\n\nAn online post editor\nA self-hosted notification engine (for webmention, activitypub, websub, etc.)\nMaybe actually write some actual code for Subl?\nAlso maybe actually put a dang site together for PlaidWeb\n\nRebuild my broken social life\nGet my home clean, and keep it clean\nStart drawing comics regularly again\nAnd the ever-present goal of losing, say, 15 pounds\nKind of ambitious, I know, but it\u2019s better to aim for the stars and hit the moon than to never even leave the ground.\n\n\n\n\nI've been meaning to finish this album \"real soon\" for the last 5 years so I'm not terribly optimistic about this one \u21a9comments"
},
"name": "fluffy rambles: 2021 goals",
"post-type": "article",
"_id": "17432127",
"_source": "3782",
"_is_read": true
}
{
"type": "entry",
"published": "2020-12-31T17:03:52Z",
"url": "https://adactio.com/journal/17727",
"category": [
"2020",
"writing",
"blogging",
"publishing",
"words",
"sharing",
"indieweb"
],
"syndication": [
"https://adactio.medium.com/c85d9760048"
],
"name": "2020 in numbers",
"content": {
"text": "I posted to adactio.com 1442 times in 2020. sparkline\n\nMarch was the busiest month with 184 posts. sparkline\n\nThis month, December, was the quietest with 68 posts. sparkline\n\nOverall I published:\n\n\n2 articles,\n\n110 blog posts, sparkline\n\n518 links, sparkline\n\n812 notes. sparkline\nIn amongst those notes are 128 photos. But the number I\u2019m happiest with is 200. From to March 18th to October 3rd, I posted a tune a day for 200 days straight.\n\nElsewhere in 2020:\n\nI huffduffed 187 pieces of audio,\nmade 1,139 contributions on Github, and\npublished 6 episodes of the Clearleft podcast.\nFor obvious reasons, in 2020 I had far fewer check ins, did far less speaking and almost no travel.",
"html": "<p>I posted to adactio.com <a href=\"https://adactio.com/archive/2020\">1442 times in 2020</a>. sparkline</p>\n\n<p>March was the busiest month with <a href=\"https://adactio.com/archive/2020/03\">184 posts</a>. sparkline</p>\n\n<p>This month, December, was the quietest with <a href=\"https://adactio.com/archive/2020/12\">68 posts</a>. sparkline</p>\n\n<p>Overall I published:</p>\n\n<ul><li>\n<a href=\"https://adactio.com/articles#in2020\">2 articles</a>,</li>\n<li>\n<a href=\"https://adactio.com/journal/archive/2020/\">110 blog posts</a>, sparkline</li>\n<li>\n<a href=\"https://adactio.com/links/archive/2020\">518 links</a>, sparkline</li>\n<li>\n<a href=\"https://adactio.com/notes/archive/2020\">812 notes</a>. sparkline</li>\n</ul><p>In amongst those notes are <a href=\"https://adactio.com/notes/photos/2020\">128 photos</a>. But the number I\u2019m happiest with is <a href=\"https://adactio.com/journal/17489\">200</a>. From to <a href=\"https://adactio.com/notes/16547\">March 18th</a> to <a href=\"https://adactio.com/notes/17487\">October 3rd</a>, I posted <a href=\"https://adactio.com/notes/tunes\">a tune a day for 200 days straight</a>.</p>\n\n<p>Elsewhere in 2020:</p>\n\n<ul><li>I huffduffed <a href=\"https://huffduffer.com/adactio\">187 pieces of audio</a>,</li>\n<li>made <a href=\"https://github.com/adactio?tab=overview&from=2020-01-01&to=2020-12-31\">1,139 contributions on Github</a>, and</li>\n<li>published <a href=\"https://podcast.clearleft.com/season01/\">6 episodes of the Clearleft podcast</a>.</li>\n</ul><p>For obvious reasons, in 2020 I had far fewer <a href=\"https://adactio.com/notes/checkins/2020\">check ins</a>, did far less <a href=\"https://adactio.com/about/speaking/#in2020\">speaking</a> and almost no <a href=\"https://adactio.com/notes/travel/2020\">travel</a>.</p>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "article",
"_id": "17407151",
"_source": "2",
"_is_read": true
}
{
"type": "entry",
"published": "2020-12-31T09:59:53Z",
"url": "https://adactio.com/journal/17723",
"category": [
"2020",
"writing",
"blogging",
"publishing",
"words",
"sharing",
"indieweb"
],
"syndication": [
"https://adactio.medium.com/543ab10f53f9"
],
"name": "Words I wrote in 2020",
"content": {
"text": "Once again I wrote over a hundred blog posts this year. While lots of other activities dropped off significantly while my main focus was to just keep on keepin\u2019 on, I still found solace and reward in writing and publishing. Like I said early on in The Situation, my website is an outlet for me:\n\n\n While you\u2019re stuck inside, your website is not just a place you can go to, it\u2019s a place you can control, a place you can maintain, a place you can tidy up, a place you can expand. Most of all, it\u2019s a place you can lose yourself in, even if it\u2019s just for a little while.\n\n\nHere are some blog posts that turned out alright:\n\n\nArchitects, gardeners, and design systems. Citing Frank Chimero, Debbie Chachra, and Lisa O\u2019Neill. \n\nHydration. Progressive enhancement. I do not think it means what you think it means.\n\nLiving Through The Future. William Gibson, Arthur C.Clarke, Daniel Dafoe, Stephen King, Emily St. John Mandel, John Wyndham, Martin Cruz-Smith, Marina Koren and H.G. Wells.\n\nPrinciples and priorities. Using design principles to embody your priorities.\n\nHard to break. Brittleness is the opposite of resilience. But they both share something in common.\n\nIntent. Black lives matter.\n\nAccessibility. Making the moral argument.\n\nT E N \u018e T. A spoiler-filled look at the new Christopher Nolan film.\n\nPortals and giant carousels. Trying to understand why people think they need to make single page apps.\n\nClean advertising. The greatest trick the devil ever pulled was convincing the world that behavioural advertising is more effective than contextual advertising.\nI find it strangely comforting that even in a year as shitty as 2020, I can look back and see that there were some decent blog posts in there. Whatever 2021 may bring, I hope to keep writing and publishing through it all. I hope you will too.",
"html": "<p><a href=\"https://adactio.com/journal/16270\">Once again</a> I wrote <a href=\"https://adactio.com/journal/archive/2020/\">over a hundred blog posts this year</a>. While lots of other activities dropped off significantly while my main focus was to just keep on keepin\u2019 on, I still found solace and reward in writing and publishing. Like I said early on in The Situation, <a href=\"https://adactio.com/journal/16585\">my website is an outlet for me</a>:</p>\n\n<blockquote>\n <p>While you\u2019re stuck inside, your website is not just a place you can go to, it\u2019s a place you can control, a place you can maintain, a place you can tidy up, a place you can expand. Most of all, it\u2019s a place you can lose yourself in, even if it\u2019s just for a little while.</p>\n</blockquote>\n\n<p>Here are some blog posts that turned out alright:</p>\n\n<ul><li>\n<a href=\"https://adactio.com/journal/16369\">Architects, gardeners, and design systems</a>. Citing Frank Chimero, Debbie Chachra, and Lisa O\u2019Neill. </li>\n<li>\n<a href=\"https://adactio.com/journal/16404\">Hydration</a>. Progressive enhancement. I do not think it means what you think it means.</li>\n<li>\n<a href=\"https://adactio.com/journal/16655\">Living Through The Future</a>. William Gibson, Arthur C.Clarke, Daniel Dafoe, Stephen King, Emily St. John Mandel, John Wyndham, Martin Cruz-Smith, Marina Koren and H.G. Wells.</li>\n<li>\n<a href=\"https://adactio.com/journal/16811\">Principles and priorities</a>. Using design principles to embody your priorities.</li>\n<li>\n<a href=\"https://adactio.com/journal/16910\">Hard to break</a>. Brittleness is the opposite of resilience. But they both share something in common.</li>\n<li>\n<a href=\"https://adactio.com/journal/16986\">Intent</a>. Black lives matter.</li>\n<li>\n<a href=\"https://adactio.com/journal/17132\">Accessibility</a>. Making the moral argument.</li>\n<li>\n<a href=\"https://adactio.com/journal/17379\">T E N \u018e T</a>. A spoiler-filled look at the new Christopher Nolan film.</li>\n<li>\n<a href=\"https://adactio.com/journal/17573\">Portals and giant carousels</a>. Trying to understand why people think they need to make single page apps.</li>\n<li>\n<a href=\"https://adactio.com/journal/17658\">Clean advertising</a>. The greatest trick the devil ever pulled was convincing the world that behavioural advertising is more effective than contextual advertising.</li>\n</ul><p>I find it strangely comforting that even in a year as shitty as 2020, I can look back and see that there were some decent blog posts in there. Whatever 2021 may bring, I hope to keep writing and publishing through it all. I hope you will too.</p>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "article",
"_id": "17400748",
"_source": "2",
"_is_read": true
}
I’ve decided. My website is in need of an overhaul. I like the concept of cultivating a digital garden whilst also combining some of the social aspects of the IndieWeb, so in the New Year I’ll don my gloves, a trowel and see how I get on!
{
"type": "entry",
"author": {
"name": "Scott Mallinson",
"url": "https://scottmallinson.com",
"photo": "https://www.gravatar.com/avatar/d4b20e750343ea81591989575e3b762b?s=96&d=https%3A%2F%2Fmicro.blog%2Fimages%2Fblank_avatar.png"
},
"url": "https://scottmallinson.com/blog/2020/12/30/im-going-to-start-gardening-in-the-new-year/",
"content": {
"html": "<p>I\u2019ve decided. <a href=\"https://scottmallinson.com\">My website</a> is in need of an overhaul. I like the concept of cultivating a <a href=\"https://maggieappleton.com/garden-history\">digital garden</a>\u00a0whilst also combining some of the social aspects of the <a href=\"https://indieweb.org/\">IndieWeb</a>, so in the New Year I\u2019ll don my gloves, a trowel and see how I get on!</p>",
"text": "I\u2019ve decided. My website is in need of an overhaul. I like the concept of cultivating a digital garden\u00a0whilst also combining some of the social aspects of the IndieWeb, so in the New Year I\u2019ll don my gloves, a trowel and see how I get on!"
},
"published": "2020-12-30T15:41:22+00:00",
"post-type": "note",
"_id": "33380032",
"_source": "7224",
"_is_read": true
}
I couldn't sleep so got up for a drink and did a little more work on the non-WordPress version of the.
It's still intrinsically linked to WordPress because it currently just retrieves the post sections from the database that are created within the main site but, ultimately, I'd like to make it a fully self-contained system.
I'll need to sort out some kind of functionality for logging in and will need to rethink posting and how sections are stored. What will be a little more problematic is working out commenting should I decide to include it.
I would also lose webmentions because my coding skills really don't extend as far as rolling my own solution for that. This, in turn, means that I would lose the current "related posts" feature.
I'm not entirely sure where I'm going with all of this, or what compromises I'm willing to make, but it would be nice to be able to say I use my own blogging engine.
{
"type": "entry",
"author": {
"name": "Colin Walker",
"url": "https://colinwalker.blog/",
"photo": null
},
"url": "https://colinwalker.blog/27-12-2020-0717/",
"published": "2020-12-27T07:17:00+00:00",
"content": {
"html": "<p>I couldn't sleep so got up for a drink and did a little more work on the <a href=\"https://colinwalker.blog/blog.php\">non-WordPress version of the</a>.</p>\n<p>It's still intrinsically linked to WordPress because it currently just retrieves the post sections from the database that are created within the main site but, ultimately, I'd like to make it a fully self-contained system.</p>\n<p>I'll need to sort out some kind of functionality for logging in and will need to rethink posting and how sections are stored. What will be a little more problematic is working out commenting should I decide to include it.</p>\n<p>I would also lose webmentions because my coding skills really don't extend as far as rolling my own solution for that. This, in turn, means that I would lose the current \"related posts\" feature.</p>\n<p>I'm not entirely sure where I'm going with all of this, or what compromises I'm willing to make, but it would be nice to be able to say I use my own blogging engine.</p>",
"text": "I couldn't sleep so got up for a drink and did a little more work on the non-WordPress version of the.\nIt's still intrinsically linked to WordPress because it currently just retrieves the post sections from the database that are created within the main site but, ultimately, I'd like to make it a fully self-contained system.\nI'll need to sort out some kind of functionality for logging in and will need to rethink posting and how sections are stored. What will be a little more problematic is working out commenting should I decide to include it.\nI would also lose webmentions because my coding skills really don't extend as far as rolling my own solution for that. This, in turn, means that I would lose the current \"related posts\" feature.\nI'm not entirely sure where I'm going with all of this, or what compromises I'm willing to make, but it would be nice to be able to say I use my own blogging engine."
},
"post-type": "note",
"_id": "17324483",
"_source": "237",
"_is_read": true
}
I’ve released version 0.0.3 of mf2 to iCalendar, a library to convert h-event microformats into iCalendar.
It no longer throws an Exception if no h-event microformats are found. Instead it will generate a minimal, “empty” iCalendar. I had run into an instance where an upcoming events page was empty and the URL for the iCalendar was returning the Exception message.
I also changed the default domain to example.com, did some minor code cleanup, and renamed the git master branch to main.
Previously
{
"type": "entry",
"published": "2020-12-23 11:40-0800",
"url": "https://gregorlove.com/2020/12/ive-released-version/",
"category": [
"indieweb",
"microformats"
],
"content": {
"text": "I\u2019ve released version 0.0.3 of mf2 to iCalendar, a library to convert h-event microformats into iCalendar.\n\nIt no longer throws an Exception if no h-event microformats are found. Instead it will generate a minimal, \u201cempty\u201d iCalendar. I had run into an instance where an upcoming events page was empty and the URL for the iCalendar was returning the Exception message.\n\nI also changed the default domain to example.com, did some minor code cleanup, and renamed the git master branch to main.\n\nPreviously",
"html": "<p>I\u2019ve released version 0.0.3 of <a href=\"https://github.com/gRegorLove/mf2-to-iCalendar\">mf2 to iCalendar</a>, a library to convert h-event microformats into iCalendar.</p>\n\n<p>It no longer throws an Exception if no h-event microformats are found. Instead it will generate a minimal, \u201cempty\u201d iCalendar. I had run into an instance where an upcoming events page was empty and the URL for the iCalendar was returning the Exception message.</p>\n\n<p>I also changed the default domain to example.com, did some minor code cleanup, and renamed the git master branch to main.</p>\n\n<p><a href=\"https://gregorlove.com/2018/03/new-release-of-mf2-to-icalendar/\">Previously</a></p>"
},
"author": {
"type": "card",
"name": "gRegor Morrill",
"url": "https://gregorlove.com/",
"photo": "https://gregorlove.com/site/assets/files/3473/profile-2016-med.jpg"
},
"post-type": "note",
"_id": "17270699",
"_source": "95",
"_is_read": true
}
{
"type": "entry",
"published": "2020-12-21T00:13:24+00:00",
"url": "https://werd.io/2020/a-known-update",
"category": [
"https://news.indieweb.org/en"
],
"name": "A Known update",
"content": {
"text": "I believe in the independent web - which was born thirty years ago today - more than any other technology.Earlier today, I shared an update with collaborators, advisors, and investors in Known. Here's what's up:Recently, I filed paperwork to officially dissolve Known, Inc, the Delaware C-Corporation. It is expected that this will be complete by the end of the year. It was one of the most personally rewarding journeys of my life, and I\u2019m grateful for every moment. But it\u2019s long past time to shut down the company.I\u2019ve come to an arrangement where I will purchase all of the intellectual property currently held by Known, Inc. As well as source code, the name, websites, domain names, logos, etc, this includes the hosted service, which has not taken revenue or new users in years, but continues to support a modest number of bloggers. I will take more of a direct role in keeping that online, at least until there is a viable, self-serve offramp for users to move to other providers. I hope to work with the open source community to create this.I\u2019ll also spend more of my time working on the open source project. The rise of platforms like Substack - and Medium\u2019s recent transformation - indicates a need for a platform for people to host their own content online. WordPress is a website builder with an ecommerce industry built around it; Ghost has become focused on corporate and commercial blogging; I\u2019m excited for Known to be a more personal platform for hobbyists and enthusiasts.Honestly, I\u2019m also excited to work on it without any pressure to make money or find sustainability. Known will not be my job or a source of any income. In fact, I expect to donate more to the Open Collective monetarily as well as spending more of my time. I'm excited to concentrate on supporting the needs of the community.(As well as import / export, my priorities include ditching Bootstrap, revisiting the interface, improving indieweb interoperability, and experimenting with how to better bring the principles of human-centered design into the open source development process. But that\u2019ll be a conversation for elsewhere.)Cross-posted to IndieNews.",
"html": "<p>I believe in the independent web - which was born thirty years ago today - more than any other technology.</p><p>Earlier today, I shared an update with collaborators, advisors, and investors in Known. Here's what's up:</p><p>Recently, I filed paperwork to officially dissolve Known, Inc, the Delaware C-Corporation. It is expected that this will be complete by the end of the year. It was one of the most personally rewarding journeys of my life, and I\u2019m grateful for every moment. But it\u2019s long past time to shut down the company.</p><p>I\u2019ve come to an arrangement where I will purchase all of the intellectual property currently held by Known, Inc. As well as source code, the name, websites, domain names, logos, etc, this includes the hosted service, which has not taken revenue or new users in years, but continues to support a modest number of bloggers. I will take more of a direct role in keeping that online, at least until there is a viable, self-serve offramp for users to move to other providers. I hope to work with the open source community to create this.</p><p>I\u2019ll also spend more of my time working on the open source project. The rise of platforms like Substack - and Medium\u2019s recent transformation - indicates a need for a platform for people to host their own content online. WordPress is a website builder with an ecommerce industry built around it; Ghost has become focused on corporate and commercial blogging; I\u2019m excited for Known to be a more personal platform for hobbyists and enthusiasts.</p><p>Honestly, I\u2019m also excited to work on it without any pressure to make money or find sustainability. Known will not be my job or a source of any income. In fact, I expect to donate more to the Open Collective monetarily as well as spending more of my time. I'm excited to concentrate on supporting the needs of the community.</p><p>(As well as import / export, my priorities include ditching Bootstrap, revisiting the interface, improving indieweb interoperability, and experimenting with how to better bring the principles of human-centered design into the open source development process. But that\u2019ll be a conversation for elsewhere.)</p><p><a class=\"u-category\" href=\"https://news.indieweb.org/en\">Cross-posted to IndieNews.</a></p>"
},
"author": {
"type": "card",
"name": "Ben Werdm\u00fcller",
"url": "https://werd.io/profile/benwerd",
"photo": "https://werd.io/file/5d388c5fb16ea14aac640912/thumb.jpg"
},
"post-type": "article",
"_id": "17208256",
"_source": "191",
"_is_read": true
}
{
"type": "entry",
"published": "2020-12-19T19:09:34-0500",
"url": "https://martymcgui.re/2020/12/19/a-slightly-messy-visit-to-the-decentralized-web/",
"category": [
"decentralized-web",
"web",
"DWeb",
"Beaker",
"Agregore",
"IPFS",
"Namecoin",
"DAT",
"hyper"
],
"name": "A slightly messy visit to the decentralized web",
"content": {
"text": "Maybe closing some tabs will help with what feels to be an unending anxiety?\nHere goes a few.\nAt the beginning of December the Internet Archive hosted a Decentralized Web (aka DWeb) Meetup online with lightning talks from 12 different groups / projects.\nYou can find the full video of the event at archive.org and one of the attendees captured some notes covering their takeaways.\nHere are some of the highlights, from my perspective.\nBeaker is now 1.0!\nThe Beaker Browser has been through some major changes and is now at 1.0. They've fully migrated from dat:// URLs (and some related under-the-hood tech) to hyper:// URLs (and under-the-hood tech). There's a migration tool to move dat:// sites to hyper:// but it seems like several of the APIs will have changed, so while it makes these tools accessible at hyper:// URLs, many of them won't work without some rewriting.\nPaul Frazee gave the Beaker lightning talk at the DWeb Meetup spent most of the time talking about what did not ship in 1.0. For a while the Beaker team has been working on building in social features including profiles and microblogs and much more and in the end they decided to rip it all out in order to focus on a simpler experience - being good at creating decentralized websites. The plan seems to be to let those features move into their own apps, possibly at the hands of the community.\nOne thing that stood out to me was a comment that the team seemed to hit some barriers with the underlying approach they were taking to build these social features: merging files from lots of shared and synced \"drives\" into a singular experience. I have yet to dip my toes into the waters of building on hyper, but from the little bits I've absorbed, this is one of the few approaches that I think I understand and if its creators are having performance issues I don't have high hopes of figuring it out myself. There was mention of a new approach called hyperbee, but it still feels very Computer Science to me at the moment. I look forward to seeing some new stuff built on it, though! \nThese details and many more are discussed in the videos from the summer DAT Conference, including an earlier talk about Beaker, and a great interactive workshop on building stuff with Dat-SDK by Mauve.\nIn general I am excited about stuff that is happening in DAT / hyper, but I think a few things are stopping me from getting into it. Beaker seems, to me, to be a kind of flagship experience for DAT and hyper and the big leap they just made to hyper left an unknown number of projects behind. That's a big filter, and it doesn't give me confidence in the longevity of any new project I might build at the moment.\nHello Agregore!\n\n At both the DWeb Meetup and the summer's DAT Conference, Mauve gave some great introductions to Agregore, \"a minimal web browser for the distributed web\".\n \n\nI am infatuated with this project, which I will attempt to explain here, badly. Agregore is a browser that focuses on making it easy to build and use apps based on distributed web technologies like hyper, IPFS, and many, many more. This is made possible through a plugin-based architecture that makes it easy to add new protocols to the browser, and by a set of libraries which abstract away the complexities of each protocol behind an HTTP-like interface.\n\n What I find really fun about this is it encourages mashing up these different technologies. You can link freely between regular HTTP sites and sites on decentralized protocols. You could build a web app on hyper:// that offloads large media files onto IPFS. Heck, even though IPFS has been getting money and hype for years, I think Agregore was the first app I was able to just download and immediately access IPFS content. It's even got a protocol handler for Gemini, a kind of baffling (to me) alternate universe version of Markdown blogs on Gopher. And more protocols \u2014 and related alternative tech like DNS via .eth domains (maybe someday .bit and .onion?) \u2014 are in the works.\n \n\n\n I can hardly think of a better web sandbox. I love the focus on \"web apps\" because HTML, CSS, JavaScript, and media in a browser are super flexible. The ability to make apps that bridge across the classic web, decentralized protocols, and maybe even local files, feels like it opens up new worlds of possibilities.\n \n\nI still have lots of questions about how to make things stick around on protocols like hyper:// and ipfs:// and ipns:// and I don't think I'll be doing much more than tinkering until I understand those features better.\nSpeaking of Sticking Around\n\n Through the IndieWeb chat I caught a reference to a blog series on decentralized web tech that is now a few years out of date at decentralized.blog. In a series called \"blockchain train journal\", the author sets out to build their blog on decentralized tech, evaluates several of the technologies available at the time (in 2017), and discusses some experiments on publishing.\n \n\nI found this one post, trying out a handful of ways of making human-friendly names for content on IPFS, particularly interesting. In that post, and others, the author makes reference to the URLs of several bits of content that they had published via IPFS and IPNS, including some experiments on resolving IPFS content via regular DNS.\n\n A couple of years later and... that content seems to be gone. I haven't been able to resolve any of the IPFS or IPNS versions of any of these blog posts. There seems to be no DNS entry pointing to an IPFS/IPNS content. One of the main \"features\" of decentralized networks like IPFS, hyper (and many more) is that they forget content extremely quickly. If you're not paying a service to host it for you, or taking care to host it yourself, it simply fades away.\n \n\n\n However, the blog continues to be available on the plain-old web \u2014 at https://decentralized.blog/ \u2014 with one interesting caveat. When I visited decentralized.blog for the first time my browser warned me that the connection was not secure because the certificate that it uses to encrypt HTTPS traffic and assert its identity has expired. It seems that the site is configured to redirect plain HTTP traffic to HTTPS. Thankfully my browser, for now, allows me to ignore this warning and read the site, despite the author failing to pay this HTTPS admin tax.\n \n\nAnd on my own forgetting...\nThe decentralized.blog writeup on .bit domains and Namecoin reminded me that, at about the same time this blogger was exploring IPFS and more, I was excited about a sort of Beaker-competitor called ZeroNet. I had made a simple demo site for myself, played around with making profiles on the demo sites which kind of emulated Twitter, Reddit, and more.\nI even got around to figuring out how to buy some Namecoin and register and configured my own domain. So you could find my little test site at schmarty.bit.\nHowever, beyond the initial configuration, Namecoin also has some upkeep requirements! Every 5-6 months (ish) I would have to open up my Namecoin wallet and let it sync the last 5-6 months of transactions before spending a tiny amount of the coin in my wallet to keep the record up to date.\nOf course, my focus eventually moved to other things. I got a new laptop and stopped using the one with my Namecoin wallet, and I eventually let it expire. It took about 8 months before a spammer grabbed it to advertise bitcoin services. About 8 months after that it was updated to note that it was being squatted and available for purchase.\nI doubt I'll get around to trying to negotiate for its return. Something about the whole thing feels a little hopeless to me.\n\n But it's on a blockchain, so you can go revisit the story of schmarty.bit any time you like. For as long as people keep mining Namecoin.",
"html": "<p>Maybe closing some tabs will help with what feels to be an unending anxiety?</p>\n<p>Here goes a few.</p>\n<p>At the beginning of December the Internet Archive hosted a Decentralized Web (aka DWeb) Meetup online with lightning talks from 12 different groups / projects.</p>\n<p>You can find the <a href=\"https://archive.org/details/dweb-meetup-dec-2020-dweb-lightning-talks\">full video of the event at archive.org</a> and one of the attendees captured some <a href=\"https://horacioh.github.io/braindump/2020-12-dweb-meetup\">notes covering their takeaways</a>.</p>\n<p>Here are some of the highlights, from my perspective.</p>\n<h2>Beaker is now 1.0!</h2>\n<p>The <a href=\"https://beakerbrowser.com/\">Beaker Browser</a> has been through some major changes and is now at 1.0. They've fully migrated from dat:// URLs (and some related under-the-hood tech) to hyper:// URLs (and under-the-hood tech). There's a migration tool to move dat:// sites to hyper:// but it seems like several of the APIs will have changed, so while it makes these tools accessible at hyper:// URLs, many of them won't work without some rewriting.</p>\n<p>Paul Frazee gave the Beaker lightning talk at the DWeb Meetup spent most of the time talking about what <i>did not</i> ship in 1.0. For a while the Beaker team has been working on building in social features including profiles and microblogs and much more and in the end they decided to rip it all out in order to focus on a simpler experience - being good at creating decentralized websites. The plan seems to be to let those features move into their own apps, possibly at the hands of the community.</p>\n<p>One thing that stood out to me was a comment that the team seemed to hit some barriers with the underlying approach they were taking to build these social features: merging files from lots of shared and synced \"drives\" into a singular experience. I have yet to dip my toes into the waters of building on hyper, but from the little bits I've absorbed, this is one of the few approaches that I think I understand and if its creators are having performance issues I don't have high hopes of figuring it out myself. There was mention of a new approach called <a href=\"https://github.com/mafintosh/hyperbee\">hyperbee</a>, but it still feels very Computer Science to me at the moment. I look forward to seeing some new stuff built on it, though! </p>\n<p>These details and many more are discussed in the <a href=\"https://events.dat.foundation/2020/stream/\">videos from the summer DAT Conference</a>, including an <a href=\"https://www.youtube.com/watch?list=PL7sG5SCUNyeYx8wnfMOUpsh7rM_g0w_cu&v=BswvvptLYrU&feature=youtu.be\">earlier talk about Beaker</a>, and a great interactive workshop on <a href=\"https://www.youtube.com/watch?v=HyHk4aImd_I&list=PL7sG5SCUNyeYx8wnfMOUpsh7rM_g0w_cu&index=20\">building stuff with Dat-SDK by Mauve</a>.</p>\n<p>In general I am excited about stuff that is happening in DAT / hyper, but I think a few things are stopping me from getting into it. Beaker seems, to me, to be a kind of flagship experience for DAT and hyper and the big leap they just made to hyper left an unknown number of projects behind. That's a big filter, and it doesn't give me confidence in the longevity of any new project I might build at the moment.</p>\n<h2>Hello Agregore!</h2>\n<p>\n At both the DWeb Meetup and the summer's DAT Conference, <a href=\"https://ranger.mauve.moe/\">Mauve</a> gave some great introductions to <a href=\"https://agregore.mauve.moe/\">Agregore</a>, \"a minimal web browser for the distributed web\".\n <br /></p>\n<p>I am<i> infatuated</i> with this project, which I will attempt to explain here, badly. Agregore is a browser that focuses on making it easy to build and use apps based on distributed web technologies like hyper, IPFS, and many, many more. This is made possible through a plugin-based architecture that makes it easy to add new protocols to the browser, and by a set of libraries which abstract away the complexities of each protocol behind an HTTP-like interface.</p>\n<p>\n What I find really fun about this is it encourages <i>mashing up </i>these different technologies. You can link freely between regular HTTP sites and sites on decentralized protocols. You could build a web app on hyper:// that offloads large media files onto IPFS. Heck, even though IPFS has been getting money and hype for years, I think Agregore was the first app I was able to just <a href=\"https://github.com/AgregoreWeb/agregore-browser/releases\">download</a> and immediately access IPFS content. It's even got a protocol handler for <a href=\"https://gemini.circumlunar.space/\">Gemini</a>, a kind of baffling (to me) alternate universe version of Markdown blogs on Gopher. And more protocols \u2014 and related alternative tech like DNS via .eth domains (maybe someday .bit and .onion?) \u2014 are in the works.\n <br /></p>\n<p>\n I can hardly think of a better web sandbox. I love the focus on \"web apps\" because HTML, CSS, JavaScript, and media in a browser are super flexible. The ability to make apps that bridge across the classic web, decentralized protocols, and maybe even local files, feels like it opens up new worlds of possibilities.\n <br /></p>\n<p>I still have lots of questions about how to make things <i>stick around</i> on protocols like hyper:// and ipfs:// and ipns:// and I don't think I'll be doing much more than tinkering until I understand those features better.</p>\n<h2>Speaking of Sticking Around</h2>\n<p>\n Through the <a href=\"https://indieweb.org/discuss\">IndieWeb chat</a> I caught a reference to a blog series on decentralized web tech that is now a few years out of date at <a href=\"https://decentralized.blog/\">decentralized.blog</a>. In a series called \"blockchain train journal\", the author sets out to build their blog on decentralized tech, evaluates several of the technologies available at the time (in 2017), and discusses some experiments on publishing.\n <br /></p>\n<p>I found this one post, <a href=\"https://decentralized.blog/ten-terrible-attempts-to-make-ipfs-human-friendly.html\">trying out a handful of ways of making human-friendly names for content on IPFS</a>, particularly interesting. In that post, and others, the author makes reference to the URLs of several bits of content that they had published via IPFS and IPNS, including some experiments on resolving IPFS content via regular DNS.</p>\n<p>\n A couple of years later and... that content seems to be gone. I haven't been able to resolve any of the IPFS or IPNS versions of any of these blog posts. There seems to be no DNS entry pointing to an IPFS/IPNS content. One of the main \"features\" of decentralized networks like IPFS, hyper (and many more) is that they forget content extremely quickly. If you're not paying a service to host it for you, or taking care to host it yourself, it simply fades away.\n <br /></p>\n<p>\n However, the blog continues to be available on the plain-old web \u2014 at https://decentralized.blog/ \u2014 with one interesting caveat. When I visited decentralized.blog for the first time my browser warned me that the connection was not secure because the certificate that it uses to encrypt HTTPS traffic and assert its identity has expired. It seems that the site is configured to redirect plain HTTP traffic to HTTPS. Thankfully my browser, for now, allows me to ignore this warning and read the site, despite the author failing to pay this HTTPS <a href=\"https://indieweb.org/admin_tax\">admin tax</a>.\n <br /></p>\n<h3>And on my own forgetting...</h3>\n<p>The decentralized.blog writeup on .bit domains and Namecoin reminded me that, at about the same time this blogger was exploring IPFS and more, I was excited about a sort of Beaker-competitor called <a href=\"https://zeronet.io/\">ZeroNet</a>. I had made a simple demo site for myself, played around with making profiles on the demo sites which kind of emulated Twitter, Reddit, and more.</p>\n<p>I even got around to figuring out how to buy some Namecoin and register and configured my own domain. So you could find my little test site at schmarty.bit.</p>\n<p>However, beyond the initial configuration, Namecoin also has some upkeep requirements! Every 5-6 months (ish) I would have to open up my Namecoin wallet and let it sync the last 5-6 months of transactions before spending a tiny amount of the coin in my wallet to keep the record up to date.</p>\n<p>Of course, my focus eventually moved to other things. I got a new laptop and stopped using the one with my Namecoin wallet, and I eventually let it expire. It took about 8 months before a spammer grabbed it to advertise bitcoin services. About 8 months after that it was updated to note that it was being squatted and available for purchase.</p>\n<p>I doubt I'll get around to trying to negotiate for its return. Something about the whole thing feels a little hopeless to me.</p>\n<p>\n But it's on a blockchain, so you can go revisit <a href=\"https://namecha.in/name/d/schmarty\">the story of schmarty.bit</a> any time you like. For as long as people keep mining Namecoin.\n <br /></p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "article",
"_id": "17192027",
"_source": "175",
"_is_read": true
}
Tending this website keeps me sane. I think of it as a digital garden, a kind of sanctuary. … And if my site is a kind of garden, then I see myself as both gardener and architect, in so much as I make plans and prepare the ground, then sow things that grow in all directions. Some things die, but others thrive, and that’s how my garden grows. And I tend it for me; visitors are a bonus.
A thoughtful and impassioned plea from Colly for more personal publishing:
I know that social media deprived the personal site of oxygen, but you are not your Twitter profile, nor are you your LinkedIn profile. You are not your Medium page. You are not your tiny presence on the company’s About page. If you are, then you look just like everyone else, and that’s not you at all. Right?
{
"type": "entry",
"published": "2020-12-17T11:50:21Z",
"url": "https://adactio.com/links/17703",
"category": [
"indieweb",
"personal",
"publishing",
"websites",
"design",
"expression",
"writing",
"sharing",
"web",
"history",
"creativity"
],
"bookmark-of": [
"https://colly.com/articles/this-used-to-be-our-playground"
],
"content": {
"text": "Simon Collison | This used to be our playground\n\n\n\n\n Tending this website keeps me sane. I think of it as a digital garden, a kind of sanctuary. \u2026 And if my site is a kind of garden, then I see myself as both gardener and architect, in so much as I make plans and prepare the ground, then sow things that grow in all directions. Some things die, but others thrive, and that\u2019s how my garden grows. And I tend it for me; visitors are a bonus.\n\n\nA thoughtful and impassioned plea from Colly for more personal publishing:\n\n\n I know that social media deprived the personal site of oxygen, but you are not your Twitter profile, nor are you your LinkedIn profile. You are not your Medium page. You are not your tiny presence on the company\u2019s About page. If you are, then you look just like everyone else, and that\u2019s not you at all. Right?",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://colly.com/articles/this-used-to-be-our-playground\">\nSimon Collison | This used to be our playground\n</a>\n</h3>\n\n<blockquote>\n <p>Tending this website keeps me sane. I think of it as a digital garden, a kind of sanctuary. \u2026 And if my site is a kind of garden, then I see myself as both gardener and architect, in so much as I make plans and prepare the ground, then sow things that grow in all directions. Some things die, but others thrive, and that\u2019s how my garden grows. And I tend it for me; visitors are a bonus.</p>\n</blockquote>\n\n<p>A thoughtful and impassioned plea from Colly for more personal publishing:</p>\n\n<blockquote>\n <p>I know that social media deprived the personal site of oxygen, but you are not your Twitter profile, nor are you your LinkedIn profile. You are not your Medium page. You are not your tiny presence on the company\u2019s About page. If you are, then you look just like everyone else, and that\u2019s not you at all. Right?</p>\n</blockquote>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "bookmark",
"_id": "17135483",
"_source": "2",
"_is_read": true
}
{
"type": "entry",
"published": "2020-12-14T21:56:29Z",
"url": "https://barryfrost.com/2020/12/micropublish-indieauth",
"category": [
"micropublish",
"indieauth",
"indieweb"
],
"name": "Micropublish: IndieAuth updates and supported properties feature",
"content": {
"text": "Yesterday I pushed a new release of Micropublish to include recent updates for clients to the IndieAuth specification, as summarised in Aaron Parecki\u2019s IndieAuth 2020 write-up. Read\u00a0full\u00a0post\u2026",
"html": "<p>Yesterday I pushed a new release of <a href=\"https://micropublish.net\">Micropublish</a> to include recent updates for clients to the <a href=\"https://indieauth.spec.indieweb.org/\">IndieAuth specification</a>, as summarised in <a href=\"https://aaronparecki.com\">Aaron Parecki</a>\u2019s <a href=\"https://aaronparecki.com/2020/12/03/1/indieauth-2020\">IndieAuth 2020 write-up</a>.</p> <a href=\"https://barryfrost.com/2020/12/micropublish-indieauth\">Read\u00a0full\u00a0post\u2026</a>"
},
"author": {
"type": "card",
"name": "Barry Frost",
"url": "https://barryfrost.com/",
"photo": "https://barryfrost.com/barryfrost.jpg"
},
"post-type": "article",
"_id": "17078951",
"_source": "189",
"_is_read": true
}
Indieweb - Restoring people's control over their online presence improvingthe.net
{
"type": "entry",
"author": {
"name": "Greg Back",
"url": "https://improvingthe.net/",
"photo": "https://www.gravatar.com/avatar/79b6f9e5e0f3229bf8e1c9d03e116805?s=96&d=https%3A%2F%2Fmicro.blog%2Fimages%2Fblank_avatar.png"
},
"url": "https://improvingthe.net/2020/12/12/indieweb-restoring-peoples.html",
"content": {
"html": "Indieweb - Restoring people's control over their online presence <a href=\"https://improvingthe.net/2020/12/12/indieweb-restoring-peoples.html\">improvingthe.net</a>",
"text": "Indieweb - Restoring people's control over their online presence improvingthe.net"
},
"published": "2020-12-13T01:58:24+00:00",
"post-type": "note",
"_id": "33380033",
"_source": "7224",
"_is_read": true
}
On your personal website, you own your work. You decide what and when to publish. You decide when to delete things. You are in control. Your work, your rules, your freedom.
{
"type": "entry",
"published": "2020-12-12T08:37:05Z",
"url": "https://adactio.com/links/17681",
"category": [
"personal",
"publishing",
"indieweb",
"independent",
"sharing"
],
"bookmark-of": [
"https://css-tricks.com/make-it-personal/"
],
"content": {
"text": "Make it Personal | CSS-Tricks\n\n\n\n\n On your personal website, you own your work. You decide what and when to publish. You decide when to delete things. You are in control. Your work, your rules, your freedom.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://css-tricks.com/make-it-personal/\">\nMake it Personal | CSS-Tricks\n</a>\n</h3>\n\n<blockquote>\n <p>On your personal website, you own your work. You decide what and when to publish. You decide when to delete things. You are in control. Your work, your rules, your freedom.</p>\n</blockquote>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "bookmark",
"_id": "17026454",
"_source": "2",
"_is_read": true
}
đź”– Bookmarked Personal Data Warehouses: Reclaiming Your Data https://simonwillison.net/2020/Nov/14/personal-data-warehouses/
{
"type": "entry",
"published": "2020-12-11T11:11:24-0500",
"summary": "\ud83d\udd16 Bookmarked Personal Data Warehouses: Reclaiming Your Data https://simonwillison.net/2020/Nov/14/personal-data-warehouses/",
"url": "https://martymcgui.re/2020/12/11/personal-data-warehouses-reclaiming-your-data/",
"category": [
"indieweb",
"ownyourdata",
"datasette",
"dogsheep"
],
"bookmark-of": [
"https://simonwillison.net/2020/Nov/14/personal-data-warehouses/"
],
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "bookmark",
"_id": "17016739",
"_source": "175",
"_is_read": true
}
Amber describes how she implemented webmentions on her (static) site. More important, she describes why!
{
"type": "entry",
"published": "2020-12-10T09:38:43Z",
"url": "https://adactio.com/links/17678",
"category": [
"webmentions",
"indieweb",
"personal",
"independent",
"publishing",
"eleventy",
"ssg",
"static",
"sharing",
"community"
],
"bookmark-of": [
"https://amberwilson.co.uk/blog/grow-the-indieweb-with-webmentions/"
],
"content": {
"text": "Grow the IndieWeb with Webmentions | Amber Wilson\n\n\n\nAmber describes how she implemented webmentions on her (static) site. More important, she describes why!",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://amberwilson.co.uk/blog/grow-the-indieweb-with-webmentions/\">\nGrow the IndieWeb with Webmentions | Amber Wilson\n</a>\n</h3>\n\n<p>Amber describes how she implemented webmentions on her (static) site. More important, she describes <em>why</em>!</p>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "bookmark",
"_id": "16980641",
"_source": "2",
"_is_read": true
}
Announcing the release of my personal IndieAuth server, and what I've spent my time on.
{
"type": "entry",
"published": "2020-12-09 11:49:48 +0000 UTC",
"summary": "Announcing the release of my personal IndieAuth server, and what I've spent my time on.",
"url": "https://www.jvt.me/posts/2020/12/09/personal-indieauth-server/",
"category": [
"www.jvt.me",
"indieauth.jvt.me",
"indieauth"
],
"name": "Creating a Personal IndieAuth Server",
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "article",
"_id": "16958674",
"_source": "2169",
"_is_read": true
}
