For some reason specific to Bluebird, I can’t get the Microformats JavaScript library working. I can see how this would be a huge road block for anyone wanting to build IndieWeb stuff if a core component of it (Microformats) can’t be worked. Lemme see if I can reproduce this and figure out if it can be patched.
{
"type": "entry",
"published": "2020-08-07T08:05:00.00000-07:00",
"url": "https://v2.jacky.wtf/post/9b364ffa-bc81-4ce5-a77c-67ef02f1355b",
"category": [
"bugs",
"JavaScript"
],
"content": {
"text": "For some reason specific to Bluebird, I can\u2019t get the Microformats JavaScript library working. I can see how this would be a huge road block for anyone wanting to build IndieWeb stuff if a core component of it (Microformats) can\u2019t be worked. Lemme see if I can reproduce this and figure out if it can be patched.",
"html": "<p>For some reason specific to Bluebird, I can\u2019t get the Microformats JavaScript library working. I can see how this would be a huge road block for anyone wanting to build IndieWeb stuff if a core component of it (Microformats) can\u2019t be worked. Lemme see if I can reproduce this and figure out if it can be patched.</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "note",
"_id": "13832907",
"_source": "1886",
"_is_read": true
}
{
"type": "entry",
"published": "2020-08-06 13:08-0700",
"url": "http://tantek.com/2020/219/b2/",
"category": [
"backfeed"
],
"in-reply-to": [
"https://github.com/snarfed/bridgy/issues"
],
"name": "backfeed GitHub labels on your issues",
"content": {
"text": "On GitHub, project team members are able to add labels to your issues on a project. If your issue is a POSSE copy of an original post on your site, Bridgy should backfeed these as \"tag-of\" responses to the original post.\n\n\nBridgy Publish already \nsupports POSSEing tag-of posts in reply to GitHub issues, \nas labels on those issues, and this is the backfeed counterpart. Brainstormed here: \nhttps://indieweb.org/tag-reply#How_to_post_a_tag-reply.\n\n\nThis is similar to \nissue #776 \nwhich is the same backfeed feature request but for Flickr.\n\n\nThis is also the \u201clabeled\u201d specific subfeature of \nissue #833 \nwhich documents many more backfeed for GitHub requests.\n\n\nAnd similar to \nthis comment on #811 \n(original post) \nrequesting Bridgy Publish untag-of support, \nit\u2019s worth considering Bridgy Backfeed untag-of support \n(the \u201cunlabeled\u201d specific subfeature of #833), \nso when someone removes a label from your issue, your original issue post is notified. However, the \nbrainstorming of how to markup untagging \nis still ongoing, and thus may need to wait for more discussion before implementing.\n\n\nLabel: backfeed.",
"html": "<p>\nOn GitHub, project team members are able to add labels to your issues on a project. If your issue is a POSSE copy of an original post on your site, Bridgy should backfeed these as \"tag-of\" responses to the original post.\n</p>\n<p>\nBridgy Publish already \n<a href=\"https://github.com/snarfed/bridgy/issues/811\">supports POSSEing tag-of posts in reply to GitHub issues</a>, \nas labels on those issues, and this is the backfeed counterpart. Brainstormed here: \n<a href=\"https://indieweb.org/tag-reply#How_to_post_a_tag-reply\">https://indieweb.org/tag-reply#How_to_post_a_tag-reply</a>.\n</p>\n<p>\nThis is similar to \n<a href=\"https://github.com/snarfed/bridgy/issues/776\">issue #776</a> \nwhich is the same backfeed feature request but for Flickr.\n</p>\n<p>\nThis is also the \u201clabeled\u201d specific subfeature of \n<a href=\"https://github.com/snarfed/bridgy/issues/833\">issue #833</a> \nwhich documents many more backfeed for GitHub requests.\n</p>\n<p>\nAnd similar to \n<a href=\"https://github.com/snarfed/bridgy/issues/811#issuecomment-382469530\">this comment on #811</a> \n(<a href=\"https://tantek.com/2018/108/t2/untag-of-bridgy-publish-github-label\">original post</a>) \nrequesting Bridgy Publish untag-of support, \nit\u2019s worth considering Bridgy Backfeed untag-of support \n(the \u201cunlabeled\u201d specific subfeature of #833), \nso when someone removes a label from your issue, your original issue post is notified. However, the \n<a href=\"https://indieweb.org/untag#How_to_mark_up.3F\">brainstorming of how to markup untagging</a> \nis still ongoing, and thus may need to wait for more discussion before implementing.\n</p>\n<p>\nLabel: <span class=\"p-category\">backfeed</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": "13813244",
"_source": "1",
"_is_read": true
}
{
"type": "entry",
"published": "2020-08-06 11:46-0700",
"url": "http://tantek.com/2020/219/b1/",
"category": [
"enhancement",
"question",
"needs proposed resolution"
],
"in-reply-to": [
"https://github.com/microformats/microformats2-parsing/issues"
],
"name": "Should we specify a MIME type / Content-Type for canonical JSON from parsed mf2?",
"content": {
"text": "There has been some past brainstorming about possible MIME types for the JSON resulting from a compliant microformats2 parsing implementation:\nmicroformats2-mime-type. \nIt seems one in particular, application/mf2+json, has seen some adoption in the wild: https://indieweb.org/application/mf2+json.\nShould we specify an explicit MIME type for the parsed JSON result of an mf2 parser? And if so, should we adopt application/mf2+json or some other alternative?\n\n\nLabels: enhancement, \nquestion, \nneeds proposed resolution.",
"html": "<p>\nThere has been some past brainstorming about possible MIME types for the JSON resulting from a compliant microformats2 parsing implementation:\n<a href=\"https://microformats.org/wiki/microformats2-mime-type\">microformats2-mime-type</a>. \nIt seems one in particular, <code>application/mf2+json</code>, has seen some adoption in the wild: <a href=\"https://indieweb.org/application/mf2+json\">https://indieweb.org/application/mf2+json</a>.\nShould we specify an explicit MIME type for the parsed JSON result of an mf2 parser? And if so, should we adopt <code>application/mf2+json</code> or some other alternative?\n</p>\n<p>\nLabels: <span class=\"p-category\">enhancement</span>, \n<span class=\"p-category\">question</span>, \n<span class=\"p-category\">needs proposed resolution</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/microformats/microformats2-parsing/issues": {
"type": "entry",
"url": "https://github.com/microformats/microformats2-parsing/issues",
"name": "GitHub project \u201cmicroformats2-parsing\u201d",
"post-type": "article"
}
},
"_id": "13813245",
"_source": "1",
"_is_read": true
}
I’m thinking about Webmention feeds and I’m noticing now how special they might be compared to some other feeds. For example, if I wanted to do something that just spat out every Webmention I’ve received, that’d get noisy fast if I have a very busy stream of incoming Webmentions. I do want to consider generating a feed that’d resort itself based on the last recent activity but also provide context about the volume of activity that happened on said resource. Perhaps making the specific feed of activity of said resource be the target of the feed as well as linking to the resource in question would work. Lots of variability here to be honest and I’ve an interest in keeping the “how” this works very straight forward. This would be all stuff you’d see in a social reader, for some context.
{
"type": "entry",
"published": "2020-08-06T12:21:00.00000-07:00",
"url": "https://v2.jacky.wtf/post/464372b9-9221-4a92-b9f2-70a2e65208c8",
"content": {
"text": "I\u2019m thinking about Webmention feeds and I\u2019m noticing now how special they might be compared to some other feeds. For example, if I wanted to do something that just spat out every Webmention I\u2019ve received, that\u2019d get noisy fast if I have a very busy stream of incoming Webmentions. I do want to consider generating a feed that\u2019d resort itself based on the last recent activity but also provide context about the volume of activity that happened on said resource. Perhaps making the specific feed of activity of said resource be the target of the feed as well as linking to the resource in question would work. Lots of variability here to be honest and I\u2019ve an interest in keeping the \u201chow\u201d this works very straight forward. This would be all stuff you\u2019d see in a social reader, for some context.",
"html": "<p>I\u2019m thinking about Webmention feeds and I\u2019m noticing now how special they might be compared to some other feeds. For example, if I wanted to do something that just spat out every Webmention I\u2019ve received, that\u2019d get noisy fast if I have a very busy stream of incoming Webmentions. I do want to consider generating a feed that\u2019d resort itself based on the last recent activity but also provide context about the volume of activity that happened on said resource. Perhaps making the specific feed of activity of said resource be the target of the feed as well as linking to the resource in question would work. Lots of variability here to be honest and I\u2019ve an interest in keeping the \u201chow\u201d this works very straight forward. This would be all stuff you\u2019d see in a social reader, for some context.</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "note",
"_id": "13811330",
"_source": "1886",
"_is_read": true
}
I think I either want native “link quoting” / citations in my site and in Indigenous or someway to automatically do that. This hints back at a conversation in the IndieWeb channels about how posting interfaces have homogenized to be “intelligent” (in the sense that by setting certain fields, the post type can be inferred). I think it’s more constraint driven for sure but due to the hyper plurality of content types we’ve engaged with, it’s easier to throw users a kitchen sink versus providing more intelligent interfaces. We’re making strides towards that though!
{
"type": "entry",
"published": "2020-08-05T06:40:00.00000-07:00",
"url": "https://v2.jacky.wtf/post/299e4167-19f2-41bf-9dc2-7dc539feca79",
"category": [
"indieweb",
"thoughts"
],
"content": {
"text": "I think I either want native \u201clink quoting\u201d / citations in my site and in Indigenous or someway to automatically do that. This hints back at a conversation in the IndieWeb channels about how posting interfaces have homogenized to be \u201cintelligent\u201d (in the sense that by setting certain fields, the post type can be inferred). I think it\u2019s more constraint driven for sure but due to the hyper plurality of content types we\u2019ve engaged with, it\u2019s easier to throw users a kitchen sink versus providing more intelligent interfaces. We\u2019re making strides towards that though!",
"html": "<p>I <em>think</em> I either want native \u201clink quoting\u201d / citations in my site and in Indigenous <em>or</em> someway to automatically do that. This hints back at a conversation in the IndieWeb channels about how posting interfaces have homogenized to be \u201cintelligent\u201d (in the sense that by setting certain fields, the post type can be inferred). I think it\u2019s more constraint driven for sure but due to the hyper plurality of content types we\u2019ve engaged with, it\u2019s easier to throw users a kitchen sink versus providing more intelligent interfaces. We\u2019re making strides towards that though!</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "note",
"_id": "13775069",
"_source": "1886",
"_is_read": true
}
Own. Your. Nook. There’s power in owning your nook of the ‘net — your domain name, your design, your archives — and it’s easier than ever to do so, and run a crowdfunding campaign at the same time.
{
"type": "entry",
"published": "2020-08-05T09:53:42Z",
"url": "https://adactio.com/links/17246",
"category": [
"indieweb",
"independent",
"publishing",
"writing",
"books",
"crowdfunding",
"kickstarter",
"platforms",
"archives",
"longevity"
],
"bookmark-of": [
"https://craigmod.com/roden/042/"
],
"content": {
"text": "Kissa. Book. Launch. \u2014 Roden Explorers Archive\n\n\n\n\n Own. Your. Nook. There\u2019s power in owning your nook of the \u2018net \u2014 your domain name, your design, your archives \u2014 and it\u2019s easier than ever to do so, and run a crowdfunding campaign at the same time.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://craigmod.com/roden/042/\">\nKissa. Book. Launch. \u2014 Roden Explorers Archive\n</a>\n</h3>\n\n<blockquote>\n <p>Own. Your. Nook. There\u2019s power in owning your nook of the \u2018net \u2014 your domain name, your design, your archives \u2014 and it\u2019s easier than ever to do so, and run a crowdfunding campaign at the same time.</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": "13772679",
"_source": "2",
"_is_read": true
}
Patched Lighthouse so it can allow you to resend Webmentions for a particular URL when provided. I had a moment when I noticed some Webmentions weren’t sent (due to being queued) and this helped bump it on the list.
{
"type": "entry",
"published": "2020-08-04T15:00:31.90875-07:00",
"url": "https://v2.jacky.wtf/post/2af484c8-0674-4354-835d-dcaa5788fb6f",
"content": {
"text": "Patched Lighthouse so it can allow you to resend Webmentions for a particular URL when provided. I had a moment when I noticed some Webmentions weren\u2019t sent (due to being queued) and this helped bump it on the list.",
"html": "<p>Patched Lighthouse so it can allow you to resend Webmentions for a particular URL when provided. I had a moment when I noticed some Webmentions weren\u2019t sent (due to being queued) and this helped bump it on the list.</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "note",
"_id": "13760211",
"_source": "1886",
"_is_read": true
}
{
"type": "entry",
"published": "2020-08-04T18:56:48.114Z",
"url": "https://www.jvt.me/mf2/2020/08/kdjw1/",
"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/2020/08/online-homebrew-website-club-nottingham-qZ0U2nBYUpZT",
"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/2020/08/online-homebrew-website-club-nottingham-qZ0U2nBYUpZT\">https://events.indieweb.org/2020/08/online-homebrew-website-club-nottingham-qZ0U2nBYUpZT</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": "13757026",
"_source": "2169",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Manton Reece",
"url": "https://www.manton.org/",
"photo": "https://micro.blog/manton/avatar.jpg"
},
"url": "https://www.manton.org/2020/08/04/bringing-back-github.html",
"name": "Bringing back GitHub archiving",
"content": {
"html": "<p>Micro.blog used to have a feature that would mirror the HTML and photos for your blog to GitHub, so that you\u2019d always have an extra copy as a backup outside of Micro.blog. The initial version of this feature had some limitations that forced me to disable it over a year ago. I always hoped to bring it back in another form, and today I rolled out the replacement.</p>\n\n<p>The new version of GitHub archiving has a few changes:</p>\n\n<ul><li>It uses a new structure based on the Blog Archive Format. It is a single HTML file (with Microformats), a JSON Feed (with both HTML and original Markdown), and all your uploads, like photos, videos, and podcast episodes.</li>\n<li>It now has more limited access to your GitHub account for better security. It only works with your own public repositories. If you previously used this feature, I\u2019ve cleared any access that Micro.blog used to have.</li>\n<li>It is designed as an archive, not a live mirror, so it only sends changes to GitHub about once a week. You can enable it and then forget its there, and I can keep supporting it because it uses fewer server resources.</li>\n</ul><p>I\u2019ve updated <a href=\"https://help.micro.blog/2016/mirroring-to-github/\">the help page</a> to describe the new feature. It\u2019s available under Posts \u2192 Design.</p>",
"text": "Micro.blog used to have a feature that would mirror the HTML and photos for your blog to GitHub, so that you\u2019d always have an extra copy as a backup outside of Micro.blog. The initial version of this feature had some limitations that forced me to disable it over a year ago. I always hoped to bring it back in another form, and today I rolled out the replacement.\n\nThe new version of GitHub archiving has a few changes:\n\nIt uses a new structure based on the Blog Archive Format. It is a single HTML file (with Microformats), a JSON Feed (with both HTML and original Markdown), and all your uploads, like photos, videos, and podcast episodes.\nIt now has more limited access to your GitHub account for better security. It only works with your own public repositories. If you previously used this feature, I\u2019ve cleared any access that Micro.blog used to have.\nIt is designed as an archive, not a live mirror, so it only sends changes to GitHub about once a week. You can enable it and then forget its there, and I can keep supporting it because it uses fewer server resources.\nI\u2019ve updated the help page to describe the new feature. It\u2019s available under Posts \u2192 Design."
},
"published": "2020-08-04T14:01:43-05:00",
"category": [
"Essays"
],
"post-type": "article",
"_id": "13756854",
"_source": "12",
"_is_read": true
}
Need to patch Lighthouse to not have expiring tokens when attempting to send out Webmentions. I’m using JWTs (only because this inbuilt system is using that by default) and it’s a bit annoying to have this huge token string. Might consider implementing a simpler token that keeps data on the server so the client knows less
{
"type": "entry",
"published": "2020-08-04T03:09:00.00000-07:00",
"url": "https://v2.jacky.wtf/post/bf00f445-555e-4b55-98bd-5b36edc354f3",
"category": [
"bugs",
"lighthouse"
],
"content": {
"text": "Need to patch Lighthouse to not have expiring tokens when attempting to send out Webmentions. I\u2019m using JWTs (only because this inbuilt system is using that by default) and it\u2019s a bit annoying to have this huge token string. Might consider implementing a simpler token that keeps data on the server so the client knows less",
"html": "<p>Need to patch Lighthouse to not have expiring tokens when attempting to send out Webmentions. I\u2019m using JWTs (only because this inbuilt system is using that by default) and it\u2019s a bit annoying to have this huge token string. Might consider implementing a simpler token that keeps data on the server so the client knows less</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "note",
"_id": "13745686",
"_source": "1886",
"_is_read": true
}
So I’ve been working on Koype Publish and I learned quite a bit on it. I’ve managed to build a UI that can be self-composing on the client side so I can send whatever I need up to the server. It’ll translate it into a Microformats payload. The goal of this over the last month was to see if I can use it to build everything for my site (edit my homepage, adjust custom pages and even adjust the layout of a feed’s markup). I know it’s doable. But now, I need to look into adjusting the editor UX so it can adaptive depending on the URL provided versus having to “select” what you need - the way it should be.
{
"type": "entry",
"published": "2020-08-03T04:32:19.88007-07:00",
"url": "https://v2.jacky.wtf/post/24121330-ced3-4d59-b2e7-f9d4c0eba8d0",
"category": [
"micropub",
"koype publish"
],
"content": {
"text": "So I\u2019ve been working on Koype Publish and I learned quite a bit on it. I\u2019ve managed to build a UI that can be self-composing on the client side so I can send whatever I need up to the server. It\u2019ll translate it into a Microformats payload. The goal of this over the last month was to see if I can use it to build everything for my site (edit my homepage, adjust custom pages and even adjust the layout of a feed\u2019s markup). I know it\u2019s doable. But now, I need to look into adjusting the editor UX so it can adaptive depending on the URL provided versus having to \u201cselect\u201d what you need - the way it should be.",
"html": "<p>So I\u2019ve been working on Koype Publish and I learned quite a bit on it. I\u2019ve managed to build a UI that can be self-composing on the client side so I can send whatever I need up to the server. It\u2019ll translate it into a Microformats payload. The goal of this over the last month was to see if I can use it to build <em>everything</em> for my site (edit my homepage, adjust custom pages and even adjust the layout of a feed\u2019s markup). I know it\u2019s doable. But now, I need to look into adjusting the editor UX so it can adaptive depending on the URL provided versus having to \u201cselect\u201d what you need - the way it <em>should</em> be.</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "note",
"_id": "13719401",
"_source": "1886",
"_is_read": true
}
also hi again, couldn’t break my #IndieWeb addiction, Twitter’s not helping anymore
{
"type": "entry",
"published": "2020-08-02T04:50:05+00:00",
"url": "https://fireburn.ru/posts/1596343805",
"syndication": [
"https://twitter.com/kisik21/status/1289785536341671937"
],
"content": {
"text": "also hi again, couldn\u2019t break my #IndieWeb addiction, Twitter\u2019s not helping anymore",
"html": "<p>also hi again, couldn\u2019t break my #IndieWeb addiction, Twitter\u2019s not helping anymore</p>"
},
"author": {
"type": "card",
"name": "Vika",
"url": "https://fireburn.ru/",
"photo": "https://fireburn.ru/media/f1/5a/fb/9b/081efafb97b4ad59f5025cf2fd0678b8f3e20e4c292489107d52be09.png"
},
"post-type": "note",
"_id": "13695852",
"_source": "1371",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Neil Mather",
"url": "https://doubleloop.net/",
"photo": null
},
"url": "https://doubleloop.net/2020/07/31/finished-future-histories-by-lizzie-oshea/",
"published": "2020-07-31T19:50:23+00:00",
"content": {
"html": "<p>There\u2019s a lot to chew on in <a href=\"https://commonplace.doubleloop.net/20200404101748-future_histories.html\">Future Histories</a>. Thematically it is right up my street, in that it is linking leftist ideas from history to modern issues around digital technology and <a href=\"https://commonplace.doubleloop.net/20200721200101-technology_capitalism.html\">technology capitalism</a>. It is ultimately about how <a href=\"https://commonplace.doubleloop.net/liberatory-technology.html\">technology should be liberatory</a>, while warning against <a href=\"https://commonplace.doubleloop.net/20200731202417-techno_utopianism.html\">techno-utopianism</a>.</p>\n<blockquote><p>As the planet slides further toward a potential future of catastrophic climate change, and as society glorifies billionaires while billions languish in poverty, digital technology could be a tool for arresting capitalism\u2019s death drive and radically transforming the prospects of humanity. But this requires that we politically organize to demand something different.</p></blockquote>\n<img src=\"https://commonplace.doubleloop.net/images/future-histories.jpg\" alt=\"future-histories.jpg\" /><p><a href=\"https://commonplace.doubleloop.net/20200402210005-frantz_fanon.html\">Fanon</a> and his work on <a href=\"https://commonplace.doubleloop.net/20200404102232-colonialism.html\">colonialism</a> are used as a frame for <a href=\"https://commonplace.doubleloop.net/20200402213403-digital_self_determination.html\">digital self-determination</a>. The historial commons is linked to the <a href=\"https://commonplace.doubleloop.net/20200727180657-digital_commons.html\">digital commons</a>. <a href=\"https://commonplace.doubleloop.net/20200731201228-thomas_paine.html\">Thomas Paine</a> is a jumping off point for <a href=\"https://commonplace.doubleloop.net/20200404123527-universal_basic_income.html\">universal basic income</a> and <a href=\"https://commonplace.doubleloop.net/20200721194919-universal_basic_services.html\">services</a>. And lots of other interesting juxtapositions.</p>\n<p>It\u2019s full of ideas and statements that I agree with. It\u2019s so choc full of stuff that I\u2019m not sure that I\u2019ve come away from it with a coherent idea of what is to be done \u2013 it\u2019s more of a manifesto than a handbook. Each chapter does have broad strokes of ideas, just more long-term legislative or policy demands than immediate opportunities for praxis. But definitely good jumping off points. For example, <a href=\"https://commonplace.doubleloop.net/20200718193005-technological_decentralisation.html\">decentralisation</a>, <a href=\"https://commonplace.doubleloop.net/free-software.html\">libre software</a> and <a href=\"https://commonplace.doubleloop.net/indieweb.html\">IndieWeb</a> adjacent ideas (e.g. <a href=\"https://commonplace.doubleloop.net/20200322114126-solid.html\">Solid</a>) are mentioned for digital self-determination, although you\u2019ll be left to your own devices as to how you do something practical with those ideas.</p>\n<p>Anyway, it\u2019s something I will definitely return to when I circle round to particular ideas again.</p>",
"text": "There\u2019s a lot to chew on in Future Histories. Thematically it is right up my street, in that it is linking leftist ideas from history to modern issues around digital technology and technology capitalism. It is ultimately about how technology should be liberatory, while warning against techno-utopianism.\nAs the planet slides further toward a potential future of catastrophic climate change, and as society glorifies billionaires while billions languish in poverty, digital technology could be a tool for arresting capitalism\u2019s death drive and radically transforming the prospects of humanity. But this requires that we politically organize to demand something different.\nFanon and his work on colonialism are used as a frame for digital self-determination. The historial commons is linked to the digital commons. Thomas Paine is a jumping off point for universal basic income and services. And lots of other interesting juxtapositions.\nIt\u2019s full of ideas and statements that I agree with. It\u2019s so choc full of stuff that I\u2019m not sure that I\u2019ve come away from it with a coherent idea of what is to be done \u2013 it\u2019s more of a manifesto than a handbook. Each chapter does have broad strokes of ideas, just more long-term legislative or policy demands than immediate opportunities for praxis. But definitely good jumping off points. For example, decentralisation, libre software and IndieWeb adjacent ideas (e.g. Solid) are mentioned for digital self-determination, although you\u2019ll be left to your own devices as to how you do something practical with those ideas.\nAnyway, it\u2019s something I will definitely return to when I circle round to particular ideas again."
},
"name": "Finished Future Histories by Lizzie O\u2019Shea",
"post-type": "article",
"_id": "13666440",
"_source": "1895",
"_is_read": true
}
#100days 91 - Did a bunch of work on the PostrChild extension and made a lot of big improvements, including
- Loading the browser action popup way faster
- Editing support
- Restoring new posts from local cache
- Get contact suggestions from the micropub endpoint
So it's now significantly closer to being ready for use, but I did break the autosuggestion UI, so I need to fix that again.
{
"type": "entry",
"published": "2020-07-31T21:51:10.870Z",
"url": "https://grant.codes/2020/07/31/09-51-10",
"category": [
"100days"
],
"syndication": [
"https://t.me/Telegram/273"
],
"content": {
"text": "#100days 91 - Did a bunch of work on the PostrChild extension and made a lot of big improvements, includingLoading the browser action popup way faster\nEditing support\nRestoring new posts from local cache\nGet contact suggestions from the micropub endpoint\nSo it's now significantly closer to being ready for use, but I did break the autosuggestion UI, so I need to fix that again.",
"html": "<p>#100days 91 - Did a bunch of work on the PostrChild extension and made a lot of big improvements, including</p><ul><li>Loading the browser action popup way faster</li>\n<li>Editing support</li>\n<li>Restoring new posts from local cache</li>\n<li>Get contact suggestions from the micropub endpoint</li>\n</ul><p>So it's now significantly closer to being ready for use, but I did break the autosuggestion UI, so I need to fix that again.</p><p></p>"
},
"author": {
"type": "card",
"name": "Grant Richmond",
"url": "https://grant.codes",
"photo": "https://grant.codes/img/me.jpg"
},
"post-type": "note",
"_id": "13663474",
"_source": "11",
"_is_read": true
}
Matt has thoughts on RSS:
My sense is that RSS is having a mini resurgence. People are getting wary of the social media platforms and their rapacious appetite for data. We’re getting fatigued from notifications; our inboxes are overflowing. And people are saying that maybe, just maybe, RSS can help. So I’m seeing RSS being discussed more in 2020 than I have done for years. There are signs of life in the ecosystem.
{
"type": "entry",
"published": "2020-07-31T17:48:22Z",
"url": "https://adactio.com/links/17226",
"category": [
"rss",
"syndication",
"feeds",
"indieweb",
"blogs",
"blogging",
"publishing",
"indpendent",
"decentralised",
"decentralisation",
"reading"
],
"bookmark-of": [
"http://interconnected.org/home/2020/07/29/improving_rss"
],
"content": {
"text": "How would I improve RSS? Three ideas (Interconnected)\n\n\n\nMatt has thoughts on RSS:\n\n\n My sense is that RSS is having a mini resurgence. People are getting wary of the social media platforms and their rapacious appetite for data. We\u2019re getting fatigued from notifications; our inboxes are overflowing. And people are saying that maybe, just maybe, RSS can help. So I\u2019m seeing RSS being discussed more in 2020 than I have done for years. There are signs of life in the ecosystem.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"http://interconnected.org/home/2020/07/29/improving_rss\">\nHow would I improve RSS? Three ideas (Interconnected)\n</a>\n</h3>\n\n<p>Matt has thoughts on RSS:</p>\n\n<blockquote>\n <p><strong>My sense is that RSS is having a mini resurgence.</strong> People are getting wary of the social media platforms and their rapacious appetite for data. We\u2019re getting fatigued from notifications; our inboxes are overflowing. And people are saying that maybe, just <em>maybe</em>, RSS can help. So I\u2019m seeing RSS being discussed more in 2020 than I have done for years. There are signs of life in the ecosystem.</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": "13657831",
"_source": "2",
"_is_read": true
}
But aren’t blogs dead? · Um, nope. For every discipline-with-depth that I care about (software/Internet, politics, energy economics, physics), if you want to find out what’s happening and you want to find out from first-person practitioners, you end up reading a blog.
Dense information from real experts, delivered fast. Why would you want any other kind?
{
"type": "entry",
"published": "2020-07-31T14:54:12Z",
"url": "https://adactio.com/links/17224",
"category": [
"blogs",
"blogging",
"writing",
"publishing",
"indieweb",
"sharing"
],
"bookmark-of": [
"https://www.tbray.org/ongoing/When/202x/2020/05/13/Meta-Blog#p-2"
],
"content": {
"text": "ongoing by Tim Bray \u00b7 Meta Blog\n\n\n\n\n But aren\u2019t blogs dead? \u00b7 Um, nope. For every discipline-with-depth that I care about (software/Internet, politics, energy economics, physics), if you want to find out what\u2019s happening and you want to find out from first-person practitioners, you end up reading a blog.\n \n Dense information from real experts, delivered fast. Why would you want any other kind?",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://www.tbray.org/ongoing/When/202x/2020/05/13/Meta-Blog#p-2\">\nongoing by Tim Bray \u00b7 Meta Blog\n</a>\n</h3>\n\n<blockquote>\n <p><strong>But aren\u2019t blogs dead?</strong> \u00b7 Um, nope. For every discipline-with-depth that I care about (software/Internet, politics, energy economics, physics), if you want to find out what\u2019s happening and you want to find out from first-person practitioners, you end up reading a blog.</p>\n \n <p>Dense information from real experts, delivered fast. Why would you want any other kind?</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": "13653655",
"_source": "2",
"_is_read": true
}
Some good blogging advice.
Building a blog for the long run? Avoid Medium.
{
"type": "entry",
"published": "2020-07-31T09:48:15Z",
"url": "https://adactio.com/links/17220",
"category": [
"writing",
"publishing",
"blogging",
"medium",
"blogs",
"indieweb",
"posse",
"syndication",
"platforms",
"silos"
],
"bookmark-of": [
"https://hulry.com/medium-vs-own-blog/"
],
"content": {
"text": "Why Medium is Not the Home for Your Ideas \u2013 The Hulry\n\n\n\nSome good blogging advice.\n\n\n Building a blog for the long run? Avoid Medium.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://hulry.com/medium-vs-own-blog/\">\nWhy Medium is Not the Home for Your Ideas \u2013 The Hulry\n</a>\n</h3>\n\n<p>Some good blogging advice.</p>\n\n<blockquote>\n <p>Building a blog for the long run? Avoid Medium.</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": "13648405",
"_source": "2",
"_is_read": true
}
{
"type": "entry",
"published": "2020-07-30T17:19:55+10:00",
"url": "https://mblaney.xyz/2020-07-30-Subscribe_to_your_Twitter_feed",
"category": [
"https://news.indieweb.org/en"
],
"name": "Subscribe to your Twitter feed",
"content": {
"text": "I've wanted to have a look at the Twitter API ever since the untimely demise of twitter-atom.appspot.com. This is still a great service from @Ryan Barrett but unfortunately it's no longer possible to sign up thanks to Twitter developer account changes.\n\n\nWhen I was working on i.haza.website I was hoping to make that part of the platform, so I've had a go at my own instead. What I ended up with was a Twitter home timeline to h-feed converter that I could drop in as a replacement. I needed a hub that can sign up as a Twitter app, and then produce feeds for each authorized user, so I set that up using my reader at unicyclic.com. You can sign in there with a regular account or via IndieAuth, and if you authorize your Twitter account it will create a feed for you.\n\n\nThe other way it works is via Microsub on your own website. That's how I'm using it now, so authorizing my Twitter account from my reader on my own site subscribes me to my Twitter timeline. This works because my site was configured to use unicyclic.com as a Microsub server when it was created on i.haza.website. (You can use it as a server from your own site too!) That's getting pretty jargony so here's some pictures of how it works:\n\n\n\n\nEither from your own website or via an account on unicyclic.com, there are some new options under Manage Feeds. Clicking the Authorize button will take you to Twitter.\n\n\n\n\nTwitter shows you what Unicyclic has access to, at the moment it's just reading your home timeline. Having access to the Twitter API in the reader does allow for some interesting new features though, for instance I would like to be able to follow people who are retweeted from inside my reader.\n\n\n\n\nOnce you authorize the app, the callback takes you to unicyclic.com. You don't need to be logged in, there's enough information provided to add the feed to your account. If you started the process from your own website it offers to take you back there.\n\n\n\n\nOnce back at your reader you should see the new feed subscription. It won't have a channel set, I usually have the default set to 'silos' because I don't check it that often. My favourite part of the reader is being able to set the channel per author. It's like creating Twitter lists from your own website, except you can mix them in with other feeds if you want.\n\n\n\n\nAuthors have hovercards in the reader which lets you change the channel. At the end of the day it all pretty much works the same as before! I'm not sure if this app will be allowed to exist forever, so it is a case of use at your own risk. (I will also be holding on to my old API key for twitter-atom.appspot.com just in case.)",
"html": "I've wanted to have a look at the Twitter API ever since the untimely demise of <a href=\"https://twitter-atom.appspot.com/\">twitter-atom.appspot.com</a>. This is still a great service from <a href=\"https://snarfed.org\">@Ryan Barrett</a> but unfortunately it's no longer possible to sign up thanks to Twitter developer account changes.<br /><br />\nWhen I was working on <a href=\"https://i.haza.website/\">i.haza.website</a> I was hoping to make that part of the platform, so I've had a go at my own instead. What I ended up with was a Twitter home timeline to h-feed converter that I could drop in as a replacement. I needed a hub that can sign up as a Twitter app, and then produce feeds for each authorized user, so I set that up using my reader at <a href=\"https://unicyclic.com\">unicyclic.com</a>. You can sign in there with a regular account or via IndieAuth, and if you authorize your Twitter account it will create a feed for you.<br /><br />\nThe other way it works is via Microsub on your own website. That's how I'm using it now, so authorizing my Twitter account from my reader on my own site subscribes me to my Twitter timeline. This works because my site was configured to use <a href=\"https://unicyclic.com\">unicyclic.com</a> as a Microsub server when it was created on <a href=\"https://i.haza.website/\">i.haza.website</a>. (You can <a href=\"https://mblaney.xyz/2020-01-13-unicycliccom_as_a_general_purpose_Microsub_server\">use it as a server</a> from your own site too!) That's getting pretty jargony so here's some pictures of how it works:<br /><br /><img alt=\"\" src=\"https://mblaney.xyz/public/ManageFeeds.png\" /><br /><br />\nEither from your own website or via an account on <a href=\"https://unicyclic.com\">unicyclic.com</a>, there are some new options under <strong>Manage Feeds</strong>. Clicking the Authorize button will take you to Twitter.<br /><br /><img alt=\"\" src=\"https://mblaney.xyz/public/TwitterAuth.png\" /><br /><br />\nTwitter shows you what Unicyclic has access to, at the moment it's just reading your home timeline. Having access to the Twitter API in the reader does allow for some interesting new features though, for instance I would like to be able to follow people who are retweeted from inside my reader.<br /><br /><img alt=\"\" src=\"https://mblaney.xyz/public/TwitterUnicyclic.png\" /><br /><br />\nOnce you authorize the app, the callback takes you to <a href=\"https://unicyclic.com\">unicyclic.com</a>. You don't need to be logged in, there's enough information provided to add the feed to your account. If you started the process from your own website it offers to take you back there.<br /><br /><img alt=\"\" src=\"https://mblaney.xyz/public/TwitterFeed.png\" /><br /><br />\nOnce back at your reader you should see the new feed subscription. It won't have a channel set, I usually have the default set to 'silos' because I don't check it that often. My favourite part of the reader is being able to set the channel <em>per author</em>. It's like creating Twitter lists from your own website, except you can mix them in with other feeds if you want.<br /><br /><img alt=\"\" src=\"https://mblaney.xyz/public/TwitterChannels.png\" /><br /><br />\nAuthors have hovercards in the reader which lets you change the channel. At the end of the day it all pretty much works the same as before! I'm not sure if this app will be allowed to exist forever, so it is a case of use at your own risk. (I will also be holding on to my old API key for <a href=\"https://twitter-atom.appspot.com/\">twitter-atom.appspot.com</a> just in case.)"
},
"author": {
"type": "card",
"name": "Malcolm Blaney",
"url": "https://mblaney.xyz",
"photo": "https://mblaney.xyz/public/profile_thumb.png"
},
"post-type": "article",
"_id": "13618291",
"_source": "3708",
"_is_read": true
}
I'm going!Mo’ IndieWeb specs, mo’ pop-ups!
{
"type": "entry",
"published": "2020-07-29T10:59:02-0400",
"rsvp": "yes",
"url": "https://martymcgui.re/2020/07/29/105902/",
"in-reply-to": [
"https://events.indieweb.org/2020/08/indieauth-pop-up-session-6xlxgeCEMgv8"
],
"content": {
"text": "I'm going!Mo\u2019 IndieWeb specs, mo\u2019 pop-ups!",
"html": "I'm going!<p>Mo\u2019 IndieWeb specs, mo\u2019 pop-ups!</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "rsvp",
"refs": {
"https://events.indieweb.org/2020/08/indieauth-pop-up-session-6xlxgeCEMgv8": {
"type": "entry",
"summary": "IndieAuth is a decentralized identity protocol built on top of OAuth 2.0.",
"url": "https://events.indieweb.org/2020/08/indieauth-pop-up-session-6xlxgeCEMgv8",
"photo": [
"https://res.cloudinary.com/schmarty/image/fetch/w_960,c_fill/https://events.indieweb.org/storage/events/20200714-sff83XIg3Y3uKlGhPdRDUumBYgsl7O.jpg"
],
"name": "IndieAuth Pop-Up Session",
"author": {
"type": "card",
"name": "events.indieweb.org",
"url": "http://events.indieweb.org",
"photo": null
},
"post-type": "photo"
}
},
"_id": "13598474",
"_source": "175",
"_is_read": true
}
{
"type": "entry",
"published": "2020-07-28T15:09:31+02:00",
"url": "https://notiz.blog/2020/07/28/working-draft-revision-435/",
"name": "Working Draft 435",
"content": {
"text": "Ich war, zusammen mit Sebastian Lasse, zu Gast beim Working Draft und wir haben mit Peter Kr\u00f6ner ein wenig \u00fcber das \u201eOpen, Decentralized, Federated und Indie\u201e-Web gesprochen.\n\n\n\nDownload MP3 | Apple Podcast | Spotify\n\n\n\nDie Folge ist ein sch\u00f6ner Rundumschlag von ActivityPub bis Zot (naja, Zot hatten wir nicht wirklich angesprochen, aber es passt einfach so sch\u00f6n \ud83d\ude09 ) geworden:\n\n\n\nBeginnend mit einem Versuch, die Begriffe Open, Decentralized, Federated, Indie etc. zu definieren steigen wir, wie die Nerds die wir sind, recht bald in die technischen Untiefen herab. Neben Protkollen wie ATOM, RSS und ActivityPub sind auch die solche Protokolle nutzenden Software wie Mastodon, Diaspora, oStatus, Identica, Status.net, Tent.io, Friendica ein Thema. Dezentral betriebene Software-Instanzen mit konpatiblen Protokollen bilden das Fediverse, dessen technische Inkompatibilit\u00e4ten (u.A. betreffend Peer Tube und WebFinger, registerProtocolHandler) ebenso wie nichttechnische Aspekte (unter anderem Monetarisierung, Gouvernance, Nazis, Fake News (siehe Eunomia), End-User-Features wie den universellen Follow-Button und F\u00f6rderungsm\u00f6glichkeiten) durchgekaut werden. Gegen Ende legen wir den Fokus auf das IndieWeb (komplett mit IndieWebCamps und Homebrew Website Clubs), Self-Hosting und wagen R\u00fcckgriffe auf das Web 2.0 mit Bestandteilen wie Flickr, Ping- und Trackbacks (in neu und cool: Webmention) und die von uns erst k\u00fcrzlich abf\u00e4llig betrachteten Microformats. Zuletzt darf der Verweis auf die mehrfacht erw\u00e4hnte Offizielle ActivityPub Konferenz 2020 nicht fehlen\u00a0\u2013 die Anmeldungs-Phase l\u00e4uft! Ceterum censeo faciem liber esse delendam.\n\n\n\n(Ein paar Links in den Shownotes von Working Draft wurden von mir nachtr\u00e4glich ge\u00e4ndert)",
"html": "<p>Ich war, zusammen mit <a href=\"https://mastodon.social/@sl007\">Sebastian Lasse</a>, zu Gast beim <a href=\"https://workingdraft.de/\">Working Draft</a> und wir haben mit <a href=\"https://www.peterkroener.de/\">Peter Kr\u00f6ner</a> ein wenig \u00fcber das \u201e<a href=\"https://workingdraft.de/435/\">Open, Decentralized, Federated und Indie</a>\u201e-Web gesprochen.</p>\n\n\n\n<p><a href=\"https://workingdraft.de/podpress_trac/web/4780/0/wd-435.mp3\">Download MP3</a> | <a href=\"https://podcasts.apple.com/de/podcast/revision-435-open-decentralized-federated-und-indie/id402204581?i=1000486353869\">Apple Podcast</a> | <a href=\"https://open.spotify.com/episode/7eq8Hw2lFtwJieB2BNFAQl\">Spotify</a></p>\n\n\n\n<p>Die Folge ist ein sch\u00f6ner Rundumschlag von <a href=\"https://www.w3.org/TR/activitypub/\">ActivityPub</a> bis <a href=\"https://www.w3.org/community/zot/\">Zot</a> (naja, Zot hatten wir nicht wirklich angesprochen, aber es passt einfach so sch\u00f6n \ud83d\ude09 ) geworden:</p>\n\n\n\n<blockquote><p>Beginnend mit einem Versuch, die Begriffe Open, Decentralized, Federated, Indie etc. zu definieren steigen wir, wie die Nerds die wir sind, recht bald in die technischen Untiefen herab. Neben Protkollen wie <a href=\"http://www.atomenabled.org/\">ATOM</a>, <a href=\"https://de.wikipedia.org/wiki/RSS\">RSS</a> und <a href=\"https://www.w3.org/TR/activitypub/\">ActivityPub</a> sind auch die solche Protokolle nutzenden Software wie <a href=\"https://mastodon.social/about\">Mastodon</a>, <a href=\"https://diasporafoundation.org/\">Diaspora</a>, oStatus, Identica, Status.net, Tent.io, Friendica ein Thema. Dezentral betriebene Software-Instanzen mit konpatiblen Protokollen bilden das <strong>Fediverse</strong>, dessen technische Inkompatibilit\u00e4ten (u.A. betreffend <a href=\"https://joinpeertube.org/\">Peer Tube</a> und <a href=\"https://webfinger.net/\">WebFinger</a>, <a href=\"https://developer.mozilla.org/de/docs/Web/API/Navigator/registerProtocolHandler\">registerProtocolHandler</a>) ebenso wie nichttechnische Aspekte (unter anderem Monetarisierung, Gouvernance, Nazis, Fake News (siehe <a href=\"https://eunomia.social/\">Eunomia</a>), End-User-Features wie den <a href=\"https://blog.mozilla.org/webdev/2010/07/26/registerprotocolhandler-enhancing-the-federated-web/\">universellen Follow-Button</a> und F\u00f6rderungsm\u00f6glichkeiten) durchgekaut werden. Gegen Ende legen wir den Fokus auf das <a href=\"https://indieweb.org/\">IndieWeb</a> (komplett mit <a href=\"https://indieweb.org/IndieWebCamps\">IndieWebCamps</a> und <a href=\"https://indieweb.org/Homebrew_Website_Club\">Homebrew Website Clubs</a>), Self-Hosting und wagen R\u00fcckgriffe auf das Web 2.0 mit Bestandteilen wie Flickr, Ping- und Trackbacks (in neu und cool: <a href=\"https://indieweb.org/Webmention\">Webmention</a>) und die von uns erst <a href=\"https://workingdraft.de/426/\">k\u00fcrzlich abf\u00e4llig betrachteten</a> <a href=\"http://microformats.org/wiki/microformats-2\">Microformats</a>. Zuletzt darf der Verweis auf die mehrfacht erw\u00e4hnte <a href=\"https://conf.activitypub.rocks\"><strong>Offizielle ActivityPub Konferenz 2020</strong></a> nicht fehlen\u00a0\u2013 die Anmeldungs-Phase l\u00e4uft! Ceterum censeo faciem liber esse delendam.</p></blockquote>\n\n\n\n<p>(Ein paar Links in den Shownotes von Working Draft wurden von mir nachtr\u00e4glich ge\u00e4ndert)</p>"
},
"author": {
"type": "card",
"name": "Matthias Pfefferle",
"url": "https://notiz.blog/author/matthias-pfefferle/",
"photo": "https://secure.gravatar.com/avatar/75512bb584bbceae57dfc503692b16b2?s=40&d=mm&r=g"
},
"post-type": "article",
"_id": "13575097",
"_source": "206",
"_is_read": true
}
