M.A. Matienzo
Over and in response to the last few months, I’ve been reflecting about intentionality, and how I spend my time creating things. I have tried to improve the indiewebbiness of my site, and understanding what it means to “scratch my own itch”. This resonates particularly lately because it’s leading me to mull over which parts should be hard and easy. Unsurprisingly, much of that is personal preference, and figuring out how I want to optimize from the perspective of user experience. Friction in UX can be a powerful tool, part of what I’m trying to find is where I want to retain friction as it helps me remain intentional.
{
"type": "entry",
"published": "2020-08-10T21:21:51-0700",
"summary": "Over and in response to the last few months, I\u2019ve been reflecting about intentionality, and how I spend my time creating things. I have tried to improve the indiewebbiness of my site, and understanding what it means to \u201cscratch my own itch\u201d. This resonates particularly lately because it\u2019s leading me to mull over which parts should be hard and easy. Unsurprisingly, much of that is personal preference, and figuring out how I want to optimize from the perspective of user experience. Friction in UX can be a powerful tool, part of what I\u2019m trying to find is where I want to retain friction as it helps me remain intentional.",
"url": "https://matienzo.org/2020/optimizing-friction/",
"category": [
"indieweb",
"music",
"plan9",
"food"
],
"syndication": [
"https://twitter.com/anarchivist/status/1293042174972563456",
"https://chaos.social/@anarchivist/104668872964686387",
"https://news.indieweb.org/en/matienzo.org/2020/optimizing-friction/"
],
"name": "Optimizing friction",
"author": {
"type": "card",
"name": "M.A. Matienzo",
"url": false,
"photo": "https://matienzo.org/images/matienzo.jpg"
},
"post-type": "article",
"_id": "33379119",
"_source": "7223",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Neil Mather",
"url": "https://doubleloop.net/",
"photo": null
},
"url": "https://doubleloop.net/2020/08/10/a-tapestry-of-humanity-and-what-we-know/",
"published": "2020-08-10T22:10:04+00:00",
"content": {
"html": "<blockquote><p>The World Wide Web was all about you create knowledge and how you create hyperlinks to different pieces of knowledge. So over time we kind of create this tapestry of humanity and what we know, which at another level of abstraction is kind of creating this meta-map of humanity. This meta-map of humanity is now controlled by these companies that are the ones who have access to the backend.</p>\n<p>\u2013 <a href=\"https://www.buzzsprout.com/1004689/4587590-the-global-south-holds-a-better-future-of-tech-w-juan-ortiz-freuler\">The Global South Holds a Better Future of Tech w/ Juan Ortiz Freuler</a></p></blockquote>\n<p>I love the phrase tapestry of humanity here. I like the <a href=\"https://commonplace.doubleloop.net/indieweb.html\">IndieWeb</a> and <a href=\"https://commonplace.doubleloop.net/wikis.html\">personal wikis</a> as a way of being part of the warp and weft of that tapestry.</p>",
"text": "The World Wide Web was all about you create knowledge and how you create hyperlinks to different pieces of knowledge. So over time we kind of create this tapestry of humanity and what we know, which at another level of abstraction is kind of creating this meta-map of humanity. This meta-map of humanity is now controlled by these companies that are the ones who have access to the backend.\n\u2013 The Global South Holds a Better Future of Tech w/ Juan Ortiz Freuler\nI love the phrase tapestry of humanity here. I like the IndieWeb and personal wikis as a way of being part of the warp and weft of that tapestry."
},
"name": "A tapestry of humanity and what we know",
"post-type": "article",
"_id": "13911719",
"_source": "1895",
"_is_read": true
}
I’m not explicitly sure but from the large demographic of people on Parler that seem to conflate the First Amendment to apply to social media companies and not who it’s intended for (the feds), I’d personally block that whole site from my IndieWeb setup.
{
"type": "entry",
"published": "2020-08-10T07:23:26.43947-07:00",
"url": "https://v2.jacky.wtf/post/5032f89e-dcb7-45b7-b958-7d242f72042a",
"in-reply-to": [
"https://twitter.com/Cambridgeport90/status/1292803078723219458"
],
"content": {
"text": "I\u2019m not explicitly sure but from the large demographic of people on Parler that seem to conflate the First Amendment to apply to social media companies and not who it\u2019s intended for (the feds), I\u2019d personally block that whole site from my IndieWeb setup.",
"html": "<p>I\u2019m not explicitly sure but from the large demographic of people on Parler that seem to conflate the First Amendment to apply to social media companies and not who it\u2019s intended for (the feds), I\u2019d personally block that whole site from my IndieWeb setup.</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "reply",
"refs": {
"https://twitter.com/Cambridgeport90/status/1292803078723219458": {
"type": "entry",
"url": "https://twitter.com/Cambridgeport90/status/1292803078723219458",
"author": {
"type": "card",
"name": "twitter.com",
"url": "https://twitter.com/Cambridgeport90/status/1292803078723219458",
"photo": null
},
"post-type": "note"
}
},
"_id": "13911704",
"_source": "1886",
"_is_read": true
}
{
"type": "entry",
"published": "2020-08-09T18:41:00+01:00",
"url": "https://www.jvt.me/mf2/2020/08/gedst/",
"category": [
"indieweb"
],
"bookmark-of": [
"http://cascadiainspired.com/excited-about-the-indie-web/"
],
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "bookmark",
"_id": "13881767",
"_source": "2169",
"_is_read": true
}
{
"type": "entry",
"published": "2020-08-08T09:54:43.51138-07:00",
"url": "https://v2.jacky.wtf/post/79cd622f-7ae5-47cd-a94e-e15bfaf6b4b1",
"category": [
"events"
],
"content": {
"text": "Currently at https://events.indieweb.org/2020/08/indieauth-1-1-identity-protocol-standards-session-6xlxgeCEMgv8 talking shop about http://indieauth.spec.indieweb.org/.",
"html": "<p>Currently at <a href=\"https://events.indieweb.org/2020/08/indieauth-1-1-identity-protocol-standards-session-6xlxgeCEMgv8\">https://events.indieweb.org/2020/08/indieauth-1-1-identity-protocol-standards-session-6xlxgeCEMgv8</a> talking shop about <a href=\"http://indieauth.spec.indieweb.org/\">http://indieauth.spec.indieweb.org/</a>.</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "note",
"_id": "13867702",
"_source": "1886",
"_is_read": true
}
going to part of the IndieAuth Pop-up Session
🗓 9:30-11:30am PDT, Sat 8/8
🎟 RSVP: https://events.indieweb.org/2020/08/indieauth-1-1-identity-protocol-standards-session-6xlxgeCEMgv8
#IndieAuth is the most implemented decentralized #identity #protocol, built on #OAuth 2.
#IndieWeb #OpenWeb #WebIdentity
#noBlockchain needed
{
"type": "entry",
"published": "2020-08-07 10:18-0700",
"rsvp": "yes",
"url": "http://tantek.com/2020/220/t1/",
"category": [
"IndieAuth",
"identity",
"protocol",
"OAuth",
"IndieWeb",
"OpenWeb",
"WebIdentity",
"noBlockchain"
],
"in-reply-to": [
"https://events.indieweb.org/2020/08/indieauth-1-1-identity-protocol-standards-session-6xlxgeCEMgv8"
],
"content": {
"text": "going to part of the IndieAuth Pop-up Session\n\ud83d\uddd3 9:30-11:30am PDT, Sat 8/8\n\ud83c\udf9f RSVP: https://events.indieweb.org/2020/08/indieauth-1-1-identity-protocol-standards-session-6xlxgeCEMgv8\n\n#IndieAuth is the most implemented decentralized #identity #protocol, built on #OAuth 2.\n\n#IndieWeb #OpenWeb #WebIdentity \n#noBlockchain needed",
"html": "going to part of the IndieAuth Pop-up Session<br />\ud83d\uddd3 9:30-11:30am PDT, Sat 8/8<br />\ud83c\udf9f RSVP: <a href=\"https://events.indieweb.org/2020/08/indieauth-1-1-identity-protocol-standards-session-6xlxgeCEMgv8\">https://events.indieweb.org/2020/08/indieauth-1-1-identity-protocol-standards-session-6xlxgeCEMgv8</a><br /><br />#<span class=\"p-category\">IndieAuth</span> is the most implemented decentralized #<span class=\"p-category\">identity</span> #<span class=\"p-category\">protocol</span>, built on #<span class=\"p-category\">OAuth</span> 2.<br /><br />#<span class=\"p-category\">IndieWeb</span> #<span class=\"p-category\">OpenWeb</span> #<span class=\"p-category\">WebIdentity</span> <br />#<span class=\"p-category\">noBlockchain</span> needed"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "http://tantek.com/",
"photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "rsvp",
"refs": {
"https://events.indieweb.org/2020/08/indieauth-1-1-identity-protocol-standards-session-6xlxgeCEMgv8": {
"type": "entry",
"url": "https://events.indieweb.org/2020/08/indieauth-1-1-identity-protocol-standards-session-6xlxgeCEMgv8",
"name": "an IndieWeb event",
"post-type": "article"
}
},
"_id": "13839016",
"_source": "1",
"_is_read": true
}
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
}