At tonight's #HomebrewWebsiteClub, I managed to implement listing all my site's posts, using Micropub Query for All Posts - which is consumable with Indigenous for Android
{
"type": "entry",
"published": "2020-07-08T18:39:03.941Z",
"url": "https://www.jvt.me/mf2/2020/07/chvxl/",
"category": [
"www.jvt.me",
"homebrew-website-club"
],
"photo": [
"https://media.jvt.me/5a9abbb797.png"
],
"content": {
"text": "At tonight's #HomebrewWebsiteClub, I managed to implement listing all my site's posts, using Micropub Query for All Posts - which is consumable with Indigenous for Android",
"html": "<p>At tonight's <a href=\"https://www.jvt.me/tags/homebrew-website-club/\">#HomebrewWebsiteClub</a><a class=\"u-mention\" href=\"https://events.indieweb.org/2020/07/online-homebrew-website-club-nottingham-xZ25kFM3qUYx\"></a>, I managed to implement listing all my site's posts, using <a href=\"https://github.com/indieweb/micropub-extensions/issues/4\">Micropub Query for All Posts</a> - which is consumable with <a href=\"https://indigenous.realize.be/\">Indigenous for Android</a></p>"
},
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "photo",
"_id": "13058632",
"_source": "2169",
"_is_read": true
}
So I mentioned the idea of making my homepage more dynamic. I don’t want it to be too difficult to do though. I have a concept of theming on my site. Since I can completely control the theme, this makes for a very interesting situation where, by leveraging Microformats JSON, I can dynamically render things on a page. For example, in this screenshot of my future site, I can have each section be determined by a property of a larger h-entry. The main text could be the e-summary, the headline text being p-name and the changelog region be a p-x-changelog that’d hold a list of embedded h-cites to other content that I’ve created!
As far as I know, there’s no such compatibility availability in a Micropub client for editing like this; they focus on providing particular post types and don’t seem to allow for “custom’ properties. However, the needed part is really just being able to push arbitrary properties to one’s post. The basis of this (for fetching) is already available thanks to q=source&url= in Micropub; you can fetch the MF2 representation of a post. This is enough to push new properties to a post.
My goal is to take Koype Publish and improve it to support this functionality of compositional content. Right now, it servers as a way for me to create long-form content and nothing more. This would allow me to do so much with my site. Some ideas I had was working on a “stack page” that’d serve as a h-entry with children for each thing that I can move around and adjust as if it was in a WYSIWYG setup.
What does the community think about such editing styles?
{
"type": "entry",
"published": "2020-07-07T20:54:50.48939-07:00",
"url": "https://v2.jacky.wtf/post/40c9ef2b-3984-4e7c-b05f-8092a51adba7",
"category": [
"micropub",
"koype",
"itches"
],
"content": {
"text": "So I mentioned the idea of making my homepage more dynamic. I don\u2019t want it to be too difficult to do though. I have a concept of theming on my site. Since I can completely control the theme, this makes for a very interesting situation where, by leveraging Microformats JSON, I can dynamically render things on a page. For example, in this screenshot of my future site, I can have each section be determined by a property of a larger h-entry. The main text could be the e-summary, the headline text being p-name and the changelog region be a p-x-changelog that\u2019d hold a list of embedded h-cites to other content that I\u2019ve created!As far as I know, there\u2019s no such compatibility availability in a Micropub client for editing like this; they focus on providing particular post types and don\u2019t seem to allow for \u201ccustom\u2019 properties. However, the needed part is really just being able to push arbitrary properties to one\u2019s post. The basis of this (for fetching) is already available thanks to q=source&url= in Micropub; you can fetch the MF2 representation of a post. This is enough to push new properties to a post.My goal is to take Koype Publish and improve it to support this functionality of compositional content. Right now, it servers as a way for me to create long-form content and nothing more. This would allow me to do so much with my site. Some ideas I had was working on a \u201cstack page\u201d that\u2019d serve as a h-entry with children for each thing that I can move around and adjust as if it was in a WYSIWYG setup.What does the community think about such editing styles?",
"html": "<p>So I mentioned the idea of making my homepage more dynamic. I don\u2019t want it to be too difficult to do though. I have a concept of theming on my site. Since I can completely control the theme, this makes for a very interesting situation where, by leveraging Microformats JSON, I can dynamically render things on a page. For example, <a href=\"https://v2.jacky.wtf/post/563632ee-5c4b-4dd0-a765-48f081d5c6b4\">in this screenshot of my future site</a>, I can have each section be determined by a property of a larger <code>h-entry</code>. The main text could be the <code>e-summary</code>, the headline text being <code>p-name</code> and the changelog region be a <code>p-x-changelog</code> that\u2019d hold a list of embedded <code>h-cite</code>s to other content that I\u2019ve created!</p><p>As far as I know, there\u2019s no such compatibility availability in a Micropub client for editing like this; they focus on providing particular post types and don\u2019t seem to allow for \u201ccustom\u2019 properties. However, the needed part is really just being able to push arbitrary properties to one\u2019s post. The basis of this (for fetching) is already available thanks to <code>q=source&url=</code> in Micropub; you can fetch the MF2 representation of a post. This is enough to push new properties to a post.</p><p>My goal is to take <a href=\"https://publish.koype.net\">Koype Publish</a> and improve it to support this functionality of compositional content. Right now, it servers as a way for me to create long-form content and nothing more. This would allow me to do <em>so</em> much with my site. Some ideas I had was working on a \u201cstack page\u201d that\u2019d serve as a <code>h-entry</code> with children for each thing that I can move around and adjust as if it was in a WYSIWYG setup.</p><p>What does the community think about such editing styles?</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "note",
"_id": "13039796",
"_source": "1886",
"_is_read": true
}
{
"type": "entry",
"published": "2020-07-07T16:02:59.595Z",
"url": "https://www.jvt.me/mf2/2020/07/10yzb/",
"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/07/online-homebrew-website-club-nottingham-xZ25kFM3qUYx",
"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/07/online-homebrew-website-club-nottingham-xZ25kFM3qUYx\">https://events.indieweb.org/2020/07/online-homebrew-website-club-nottingham-xZ25kFM3qUYx</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": "13024971",
"_source": "2169",
"_is_read": true
}
Liked Changes To IndieWeb Organizing, Brief Words At IndieWebCamp West by 
Tantek Çelik
A week ago Saturday morning co-organizer Chris Aldrich opened IndieWebCamp West and introduced the keynote speakers. After their inspiring talks he asked me to say a few words about changes we’re making in the IndieWeb community around organizing. This is an edited version of those words, rewritte...
{
"type": "entry",
"author": {
"name": "Neil Mather",
"url": "https://doubleloop.net/",
"photo": null
},
"url": "https://doubleloop.net/2020/07/06/6926/",
"published": "2020-07-06T12:29:00+00:00",
"content": {
"html": "Liked <a href=\"https://tantek.com/2020/187/b1/changes-indieweb-organizing-indiewebcamp-west\">Changes To IndieWeb Organizing, Brief Words At IndieWebCamp West</a> by <a href=\"https://tantek.com/\"><img src=\"https://doubleloop.net/Array\" alt=\"Tantek \u00c7elik\" />Tantek \u00c7elik</a>\n<blockquote>A week ago Saturday morning co-organizer Chris Aldrich opened IndieWebCamp West and introduced the keynote speakers. After their inspiring talks he asked me to say a few words about changes we\u2019re making in the IndieWeb community around organizing. This is an edited version of those words, rewritte...</blockquote>",
"text": "Liked Changes To IndieWeb Organizing, Brief Words At IndieWebCamp West by Tantek \u00c7elik\nA week ago Saturday morning co-organizer Chris Aldrich opened IndieWebCamp West and introduced the keynote speakers. After their inspiring talks he asked me to say a few words about changes we\u2019re making in the IndieWeb community around organizing. This is an edited version of those words, rewritte..."
},
"post-type": "note",
"_id": "12992192",
"_source": "1895",
"_is_read": true
}
{
"type": "entry",
"published": "2020-07-05 23:59-0700",
"url": "http://tantek.com/2020/187/b1/changes-indieweb-organizing-indiewebcamp-west",
"name": "Changes To IndieWeb Organizing, Brief Words At IndieWebCamp West",
"content": {
"text": "A week ago Saturday morning co-organizer \nChris Aldrich opened \nIndieWebCamp West \nand introduced the keynote speakers. After their inspiring talks he asked me to say a few words about changes we\u2019re making in the IndieWeb community around organizing. This is an edited version of those words, rewritten for clarity and context. \u2014 Tantek\n\n\nChris mentioned that one of his favorite parts of \nour code of conduct \nis that we \nprioritize marginalized people\u2019s safety above privileged folks\u2019s comfort.\n\n\nThat was a change we deliberately made last year, announced at last year\u2019s summit. It was well received, but it\u2019s only one minor change.\n\n\nThose of us that have organized and have been organizing our all-volunteer IndieWebCamps and other IndieWeb events have been thinking a lot about the events of the past few months, especially in the United States. We met the day before IndieWebCamp West and discussed our roles in the IndieWeb community and what can we do to to examine the structural barriers and systemic racism and or sexism that exists even in our own community. We have been asking, what can we do to explicitly dismantle those?\n\n\nWe have done a bunch of things. Rather, we as a community have improved things organically, in a distributed way, sharing with each other, rather than any explicit top-down directives. Some improvements are smaller, such as renaming things like whitelist & blacklist to allowlist & blocklist (though we had documented \nblocklist since 2016, allowlist since this past January, and only added whitelist/blacklist as redirects afterwards).\n\n\nMany of these changes have been part of larger quieter waves already happening in the technology and specifically open source and standards communities for quite some time. Waves of changes that are now much more glaringly obviously important to many more people than before. Choosing and changing terms to reinforce our intentions, not legacy systemic white supremacy.\n\n\nPart of our role & responsibility as organizers (as anyone who has any power or authority, implied or explicit, in any organization or community), is to work to dismantle any aspect or institution or anything that contributes to white supremacy or to patriarchy, even in our own volunteer-based community.\n\n\nWe\u2019re not going to get everything right. We\u2019re going to make mistakes. An important part of the process is acknowledging when that happens, making corrections, and moving forward; keep listening and keep learning.\n\n\nThe most recent change we\u2019ve made has to do with Organizers Meetups that we have been doing for several years, usually a half day logistics & community issues meeting the day before an IndieWebCamp. Or Organizers Summits a half day before our annual IndieWeb Summits; in 2019 that\u2019s when we made that aforementioned update to our Code of Conduct to prioritize marginalized people\u2019s safety.\n\n\nTypically we have asked people to have some experience with organizing in order to participate in organizers meetups. Since the community actively helps anyone who wants to put in the work to become an organizer, and provides instructions, guidelines, and tips for successfully doing so, this seemed like a reasonable requirement. It also kept organizers meetups very focused on both pragmatic logistics, and dedicated time for continuous community improvement, learning from other events and our own IndieWebCamps, and improving future IndieWebCamps accordingly.\n\n\nHowever, we must acknowledge that our community, like a lot of online, open communities, volunteer communities, unfortunately reflects a very privileged demographic. If you look at the photos from Homebrew Website Clubs, they\u2019re mostly white individuals, mostly male, mostly apparently cis. Mostly white cis males. This does not represent the users of the Web. For that matter, it does not represent the demographics of the society we're in.\n\n\nOne of our ideals, I believe, is to better reflect in the IndieWeb community, both the demographic of everyone that uses the Web, and ideally, everyone in society.\nWhile we don't expect to solve all the problems of the Web (or society) by ourselves, we believe we can take steps towards dismantling white supremacy and patriarchy where we encounter them.\n\n\nOne step we are taking, effective immediately, is making all of our organizers meetups forward-looking for those who want to organize a Homebrew Website Club or IndieWebCamp. We still suggest people have experience organizing. We also explicitly recognize that any kind of requirement of experience may serve to reinforce existing systemic biases that we have no interest in reinforcing. \n\n\nWe have \nupdated our Organizers page with a new statement of who should participate, our recognition of broader systemic inequalities, and an explicit:\n\n\u2026 welcome to Organizers Meetups all individuals who identify as BIPOC, non-male, non-cis, or any marginalized identity, independent of any organizing experience.\n\nThis is one step. As organizers, we\u2019re all open to listening, learning, and doing more work. That's something that we encourage everyone to adopt. We think this is an important aspect of maintaining a healthy community and frankly, just being the positive force that that we want the IndieWeb to be on the Web and hopefully for society as a whole.\n\n\nIf folks have questions, I or any other organizers are happy to answer them, either \nin chat or privately, however anyone feels comfortable discussing these changes.\n\n\nThanks. \u2014 Tantek",
"html": "<p>\nA week ago Saturday morning co-organizer \n<a href=\"https://boffosocko.com/\">Chris Aldrich</a> opened \n<a href=\"https://indieweb.org/2020/West\">IndieWebCamp West</a> \nand introduced the keynote speakers. After their inspiring talks he asked me to say a few words about changes we\u2019re making in the IndieWeb community around organizing. This is an edited version of those words, rewritten for clarity and context. \u2014 Tantek\n</p>\n<p>\nChris mentioned that one of his favorite parts of \n<a href=\"https://indieweb.org/code-of-conduct\">our code of conduct</a> \nis that we \n<a href=\"https://indieweb.org/code-of-conduct#prioritizes_marginalized_people\">prioritize marginalized people\u2019s safety above privileged folks\u2019s comfort</a>.\n</p>\n<p>\nThat was a change we deliberately made last year, announced at last year\u2019s summit. It was well received, but it\u2019s only one minor change.\n</p>\n<p>\nThose of us that have organized and have been organizing our all-volunteer IndieWebCamps and other IndieWeb events have been thinking a lot about the events of the past few months, especially in the United States. We met the day before IndieWebCamp West and discussed our roles in the IndieWeb community and what can we do to to examine the structural barriers and systemic racism and or sexism that exists even in our own community. We have been asking, what can we do to explicitly dismantle those?\n</p>\n<p>\nWe have done a bunch of things. Rather, we as a community have improved things organically, in a distributed way, sharing with each other, rather than any explicit top-down directives. Some improvements are smaller, such as renaming things like whitelist & blacklist to allowlist & blocklist (though we had documented \n<a href=\"https://indieweb.org/blocklist\">blocklist</a> since 2016, <a href=\"https://indieweb.org/allowlist\">allowlist</a> since this past January, and only added whitelist/blacklist as redirects afterwards).\n</p>\n<p>\nMany of these changes have been part of larger quieter waves already happening in the technology and specifically open source and standards communities for quite some time. Waves of changes that are now much more glaringly obviously important to many more people than before. Choosing and changing terms to reinforce our intentions, not legacy systemic white supremacy.\n</p>\n<p>\nPart of our role & responsibility as organizers (as anyone who has any power or authority, implied or explicit, in any organization or community), is to work to dismantle any aspect or institution or anything that contributes to white supremacy or to patriarchy, even in our own volunteer-based community.\n</p>\n<p>\nWe\u2019re not going to get everything right. We\u2019re going to make mistakes. An important part of the process is acknowledging when that happens, making corrections, and moving forward; keep listening and keep learning.\n</p>\n<p>\nThe most recent change we\u2019ve made has to do with Organizers Meetups that we have been doing for several years, usually a half day logistics & community issues meeting the day before an IndieWebCamp. Or Organizers Summits a half day before our annual IndieWeb Summits; in 2019 that\u2019s when we made that aforementioned update to our Code of Conduct to prioritize marginalized people\u2019s safety.\n</p>\n<p>\nTypically we have asked people to have some experience with organizing in order to participate in organizers meetups. Since the community actively helps anyone who wants to put in the work to become an organizer, and provides instructions, guidelines, and tips for successfully doing so, this seemed like a reasonable requirement. It also kept organizers meetups very focused on both pragmatic logistics, and dedicated time for continuous community improvement, learning from other events and our own IndieWebCamps, and improving future IndieWebCamps accordingly.\n</p>\n<p>\nHowever, we must acknowledge that our community, like a lot of online, open communities, volunteer communities, unfortunately reflects a very privileged demographic. If you look at the photos from Homebrew Website Clubs, they\u2019re mostly white individuals, mostly male, mostly apparently cis. Mostly white cis males. This does not represent the users of the Web. For that matter, it does not represent the demographics of the society we're in.\n</p>\n<p>\nOne of our ideals, I believe, is to better reflect in the IndieWeb community, both the demographic of everyone that uses the Web, and ideally, everyone in society.\nWhile we don't expect to solve all the problems of the Web (or society) by ourselves, we believe we can take steps towards dismantling white supremacy and patriarchy where we encounter them.\n</p>\n<p>\nOne step we are taking, effective immediately, is making all of our organizers meetups forward-looking for those who want to organize a Homebrew Website Club or IndieWebCamp. We still suggest people have experience organizing. We also explicitly recognize that any kind of requirement of experience may serve to reinforce existing systemic biases that we have no interest in reinforcing. \n</p>\n<p>\nWe have \n<a href=\"https://indieweb.org/Organizers\">updated our Organizers page</a> with a new statement of who should participate, our recognition of broader systemic inequalities, and an explicit:\n</p>\n<blockquote>\u2026 welcome to Organizers Meetups all individuals who identify as BIPOC, non-male, non-cis, or any marginalized identity, independent of any organizing experience.</blockquote>\n<p>\nThis is one step. As organizers, we\u2019re all open to listening, learning, and doing more work. That's something that we encourage everyone to adopt. We think this is an important aspect of maintaining a healthy community and frankly, just being the positive force that that we want the IndieWeb to be on the Web and hopefully for society as a whole.\n</p>\n<p>\nIf folks have questions, I or any other organizers are happy to answer them, either \n<a href=\"https://chat.indieweb.org/meta\">in chat</a> or privately, however anyone feels comfortable discussing these changes.\n</p>\n<p>\nThanks. \u2014 Tantek\n</p>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "http://tantek.com/",
"photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "article",
"_id": "12990892",
"_source": "1",
"_is_read": true
}
I shouldn’t call it a “blog” engine. It’ll be more than that. There’s a lot I want to do with my personal space that’s heavily influenced by stuff in the IndieWeb space as well as the Dat world and the setups today would require a LOT of tinkering to get there.
{
"type": "entry",
"published": "2020-07-05T19:53:01.70913-07:00",
"url": "https://v2.jacky.wtf/post/bbdb37b6-2e2e-44d0-9922-eb96dcc988b7",
"in-reply-to": [
"https://twitter.com/jackyalcine/status/1279967709157978113?s=20"
],
"content": {
"text": "I shouldn\u2019t call it a \u201cblog\u201d engine. It\u2019ll be more than that. There\u2019s a lot I want to do with my personal space that\u2019s heavily influenced by stuff in the IndieWeb space as well as the Dat world and the setups today would require a LOT of tinkering to get there.",
"html": "<p>I shouldn\u2019t call it a \u201cblog\u201d engine. It\u2019ll be more than that. There\u2019s a lot I want to do with my personal space that\u2019s heavily influenced by stuff in the IndieWeb space as well as the Dat world and the setups today would require a LOT of tinkering to get there.</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "reply",
"refs": {
"https://twitter.com/jackyalcine/status/1279967709157978113?s=20": {
"type": "entry",
"url": "https://twitter.com/jackyalcine/status/1279967709157978113?s=20",
"author": {
"type": "card",
"name": "twitter.com",
"url": "https://twitter.com/jackyalcine/status/1279967709157978113?s=20",
"photo": null
},
"post-type": "note"
}
},
"_id": "12983268",
"_source": "1886",
"_is_read": true
}
When I say Lighthouse here, I’m referring to a Webmention service I’m working on (https://lighthouse.black.af). Not the other thing.
{
"type": "entry",
"published": "2020-07-05T16:32:27.07529-07:00",
"url": "https://v2.jacky.wtf/post/81554256-8564-4495-9b1c-124e541d17ff",
"in-reply-to": [
"https://v2.jacky.wtf/post/1e74261d-3e7e-441a-ba23-84c79e358106"
],
"content": {
"text": "When I say Lighthouse here, I\u2019m referring to a Webmention service I\u2019m working on (https://lighthouse.black.af). Not the other thing.",
"html": "<p>When I say Lighthouse here, I\u2019m referring to a Webmention service I\u2019m working on (<a href=\"https://lighthouse.black.af\">https://lighthouse.black.af</a>). Not the other thing.</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "reply",
"refs": {
"https://v2.jacky.wtf/post/1e74261d-3e7e-441a-ba23-84c79e358106": {
"type": "entry",
"url": "https://v2.jacky.wtf/post/1e74261d-3e7e-441a-ba23-84c79e358106",
"photo": [
"https://v2.jacky.wtf/media/image/entry%241e74261d-3e7e-441a-ba23-84c79e358106/Screenshot_20200705_162257.png?v=original"
],
"content": {
"text": "So this is something on Lighthouse\u2019s dashboard; but the fact that the buttons are the same background color but still LOOK different is so trippy lol. What is this phenomenon called?",
"html": "<p>So this is something on <a href=\"https://lighthouse.black.af\">Lighthouse\u2019s</a> dashboard; but the fact that the buttons are the same background color but still LOOK different is so trippy lol. What is this phenomenon called?</p>"
},
"author": {
"type": "card",
"name": "Jacky Alcin\u00e9",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "photo"
}
},
"_id": "12980328",
"_source": "1886",
"_is_read": true
}
Interesting to see Webmentions mentioned on this list of concepts around digital gardens! https://github.com/MaggieAppleton/digital-gardeners
{
"type": "entry",
"published": "2020-07-05T14:03:42.64541-07:00",
"url": "https://v2.jacky.wtf/post/778c9144-184e-4c8a-be88-1daddcbb2c9b",
"content": {
"text": "Interesting to see Webmentions mentioned on this list of concepts around digital gardens! https://github.com/MaggieAppleton/digital-gardeners",
"html": "<p>Interesting to see Webmentions mentioned on this list of concepts around digital gardens! <a href=\"https://github.com/MaggieAppleton/digital-gardeners\">https://github.com/MaggieAppleton/digital-gardeners</a></p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "note",
"_id": "12977744",
"_source": "1886",
"_is_read": true
}
The community part is something that’s still being worked on. We get through it by having something akin to planets that people can follow (try subscribing to https://stream.indieweb.org/ for example! check out https://indieweb.xyz!) but there’s definitely more that can be done. What kind of ideas do you have in mind?
I personally want to work towards having me define my community on my site (internally, of course) and let my tooling for subscribing to people adapt that and grow from there. That way, my site is always the authority to who and what I want to engage with.
{
"type": "entry",
"published": "2020-07-05T12:29:18.32181-07:00",
"url": "https://v2.jacky.wtf/post/064d6695-d43c-4501-a6c6-a35a0e419d31",
"in-reply-to": [
"https://biglizardbooks.net/index.php/2020/07/05/indieweb-the-good-and-the-bad/"
],
"content": {
"text": "The community part is something that\u2019s still being worked on. We get through it by having something akin to planets that people can follow (try subscribing to https://stream.indieweb.org/ for example! check out https://indieweb.xyz!) but there\u2019s definitely more that can be done. What kind of ideas do you have in mind?I personally want to work towards having me define my community on my site (internally, of course) and let my tooling for subscribing to people adapt that and grow from there. That way, my site is always the authority to who and what I want to engage with.",
"html": "<p>The community part is something that\u2019s still being worked on. We get through it by having something akin to planets that people can follow (try subscribing to <a href=\"https://stream.indieweb.org/\">https://stream.indieweb.org/</a> for example! check out <a href=\"https://indieweb.xyz\">https://indieweb.xyz</a>!) but there\u2019s definitely more that can be done. What kind of ideas do you have in mind?</p><p>I personally want to work towards having me define my community on my site (internally, of course) and let my tooling for subscribing to people adapt that and grow from there. That way, my site is always the authority to who and what I want to engage with.</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "reply",
"refs": {
"https://biglizardbooks.net/index.php/2020/07/05/indieweb-the-good-and-the-bad/": {
"type": "entry",
"url": "https://biglizardbooks.net/index.php/2020/07/05/indieweb-the-good-and-the-bad/",
"photo": [
"https://biglizardbooks.net/wp-content/uploads/2020/07/cropped-Faerie-dragon-icon-2.png"
],
"syndication": [
"https://twitter.com/XandraPenclaw/status/1279754857939902466",
"https://yiff.life/@xandra/104461258816465790"
],
"name": "Indieweb: the Good and the Bad",
"content": {
"text": "Obviously I like having my own website quite a bit. And I like indieweb and micropub, and the idea that I can use my own website as a hub for my social activity. And I\u2019ve just gotten started with this stuff, so I\u2019m still learning all the ins and outs. But there are a few problems with indieweb culture that I\u2019m starting to notice.\nThe biggest is the fact that you need your own personal website for most of this stuff, and free hosting will not do. That\u2019s not a problem for me, but it is a barrier to entry for a lot of folks. Heck, even micro.blog lacks a free version. Maybe as time goes on we will find a way around this obstacle and more people will be able to take advantage of this cool way of interacting with the web.\nAnother problem is that indieweb seems to be very individualist focused. The idea is to \u201cown\u201d your data and content and keep it out of corporate hands. With noted exceptions, however, I haven\u2019t found much in the way of community building resources outside of a few forums dedicated to indieweb stuff. I personally find that a bit unnerving. Community is very important to me. I\u2019m mainly on the web to make friends. Of course integrating my blog and social media profiles seems to be helping that, but the idea of \u201cowning\u201d my data doesn\u2019t appeal to me. I\u2019d rather no one own my info.\nThat being said, there\u2019s a lot with indieweb to like. The fact that I can choose what sites to syndicate to makes me feel like I consent to how my data flows. There is a lot of stuff here that an anarchist can get behind. The startup cost is still an issue, but I don\u2019t think its an insurmountable one. And I\u2019d like to see more indieweb people focus on accessibility.\nOverall I like this suite of features and will continue to use it, but I hope that these issues get addressed eventually. I would like to be able to recommend indieweb functionality to my friends, but at the moment it is still something that requires an investment of both time and money.",
"html": "<p>Obviously I like having my own website quite a bit. And I like indieweb and micropub, and the idea that I can use my own website as a hub for my social activity. And I\u2019ve just gotten started with this stuff, so I\u2019m still learning all the ins and outs. But there are a few problems with indieweb culture that I\u2019m starting to notice.</p>\n<p>The biggest is the fact that you need your own personal website for most of this stuff, and free hosting will not do. That\u2019s not a problem for me, but it is a barrier to entry for a lot of folks. Heck, even micro.blog lacks a free version. Maybe as time goes on we will find a way around this obstacle and more people will be able to take advantage of this cool way of interacting with the web.</p>\n<p>Another problem is that indieweb seems to be very individualist focused. The idea is to \u201cown\u201d your data and content and keep it out of corporate hands. With noted exceptions, however, I haven\u2019t found much in the way of community building resources outside of a few forums dedicated to indieweb stuff. I personally find that a bit unnerving. Community is very important to me. I\u2019m mainly on the web to make friends. Of course integrating my blog and social media profiles seems to be helping that, but the idea of \u201cowning\u201d my data doesn\u2019t appeal to me. I\u2019d rather <em>no one </em>own my info.</p>\n<p>That being said, there\u2019s a lot with indieweb to like. The fact that I can choose what sites to syndicate to makes me feel like I consent to how my data flows. There is a lot of stuff here that an anarchist can get behind. The startup cost is still an issue, but I don\u2019t think its an insurmountable one. And I\u2019d like to see more indieweb people focus on accessibility.</p>\n<p>Overall I like this suite of features and will continue to use it, but I hope that these issues get addressed eventually. I would like to be able to recommend indieweb functionality to my friends, but at the moment it is still something that requires an investment of both time and money.</p>\n<ul><li><a class=\"u-syndication\" href=\"https://twitter.com/XandraPenclaw/status/1279754857939902466\"> </a></li>\n<li><a class=\"u-syndication\" href=\"https://yiff.life/@xandra/104461258816465790\"> </a></li>\n</ul>"
},
"post-type": "photo"
}
},
"_id": "12976119",
"_source": "1886",
"_is_read": true
}
Okay so I’ve managed to give Lighthouse a means of rendering a Microformats2 JSON (JF2) feed for incoming Webmentions and a h-feed. I want to hook this up to some sort of WebSub system so it can be polled against in “real time”. I have to clean up the dashboard so this information is more discoverable. I also need to work on making a help center of sorts.
{
"type": "entry",
"published": "2020-07-04T16:18:39.94911-07:00",
"url": "https://v2.jacky.wtf/post/ffaf948b-5d55-4766-8fae-03b0b5c8ebf8",
"content": {
"text": "Okay so I\u2019ve managed to give Lighthouse a means of rendering a Microformats2 JSON (JF2) feed for incoming Webmentions and a h-feed. I want to hook this up to some sort of WebSub system so it can be polled against in \u201creal time\u201d. I have to clean up the dashboard so this information is more discoverable. I also need to work on making a help center of sorts.",
"html": "<p>Okay so I\u2019ve managed to give Lighthouse a means of rendering a Microformats2 JSON (JF2) feed for incoming Webmentions and a h-feed. I want to hook this up to some sort of WebSub system so it can be polled against in \u201creal time\u201d. I have to clean up the dashboard so this information is more discoverable. I also need to work on making a help center of sorts.</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "note",
"_id": "12958170",
"_source": "1886",
"_is_read": true
}
{
"type": "entry",
"published": "2020-07-04T16:58:51Z",
"url": "https://adactio.com/journal/17095",
"category": [
"rss",
"feeds",
"subscriptions",
"syndication",
"indieweb",
"blogs",
"blogging",
"personal",
"publishing",
"blogrolls"
],
"syndication": [
"https://medium.com/@adactio/424f2a0a4410"
],
"name": "Feeds",
"content": {
"text": "A little while back, Marcus Herrmann wrote about making RSS more visible again with a /feeds page. Here\u2019s his feeds page. Here\u2019s Remy\u2019s.\n\nSeems like a good idea to me. I\u2019ve made mine:\n\nadactio.com/feeds\n\nAs well as linking to the usual RSS feeds (blog posts, links, notes), it\u2019s also got an explanation of how you can subscribe to a customised RSS feed using tags.\n\nThen, earlier today, I was chatting with Matt on Twitter and he asked:\n\n\n btw do you share your blogroll anywhere?\n\n\nSo now I\u2019ve added another URL:\n\nadactio.com/feeds/subscriptions\n\nThat\u2019s got a link to my OPML file, exported from my feed reader, and a list of the (current) RSS feeds that I\u2019m subscribed to.\n\nI like the idea of blogrolls making a comeback. And webrings.",
"html": "<p>A little while back, Marcus Herrmann wrote about <a href=\"https://marcus.io/blog/making-rss-more-visible-again-with-slash-feeds\">making RSS more visible again with a <code>/feeds</code> page</a>. Here\u2019s <a href=\"https://marcus.io/feeds\">his feeds page</a>. Here\u2019s <a href=\"https://remysharp.com/feeds\">Remy\u2019s</a>.</p>\n\n<p>Seems like a good idea to me. I\u2019ve made mine:</p>\n\n<p><a href=\"https://adactio.com/feeds\">adactio.com/feeds</a></p>\n\n<p>As well as linking to the usual RSS feeds (blog posts, links, notes), it\u2019s also got an explanation of how <a href=\"https://adactio.com/journal/14120\">you can subscribe to a customised RSS feed using tags</a>.</p>\n\n<p>Then, earlier today, I was chatting with <a href=\"http://interconnected.org/\">Matt</a> on Twitter and <a href=\"https://twitter.com/genmon/status/1279406341988237314\">he asked</a>:</p>\n\n<blockquote>\n <p>btw do you share your blogroll anywhere?</p>\n</blockquote>\n\n<p>So now I\u2019ve added another URL:</p>\n\n<p><a href=\"https://adactio.com/feeds/subscriptions\">adactio.com/feeds/subscriptions</a></p>\n\n<p>That\u2019s got a link to <a href=\"https://adactio.com/feeds/subscriptions/adactio.opml\">my OPML file</a>, exported from <a href=\"https://ranchero.com/netnewswire/\">my feed reader</a>, and a list of the (current) RSS feeds that I\u2019m subscribed to.</p>\n\n<p>I like the idea of blogrolls making a comeback. <a href=\"https://weirdwidewebring.net/\">And webrings</a>.</p>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "article",
"_id": "12951318",
"_source": "2",
"_is_read": true
}
I don’t have refs used in the IndieWeb Elixir yet but I’m in favor of shorter keys!
{
"type": "entry",
"published": "2020-07-04T00:46:30.47978-07:00",
"url": "https://v2.jacky.wtf/post/6fb712f9-9e03-4b71-ac3d-eb2d4d6fa382",
"in-reply-to": [
"https://github.com/indieweb/jf2/issues/41"
],
"content": {
"text": "I don\u2019t have refs used in the IndieWeb Elixir yet but I\u2019m in favor of shorter keys!",
"html": "<p>I don\u2019t have <code>refs</code> used in the IndieWeb Elixir yet but I\u2019m in favor of shorter keys!</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "reply",
"refs": {
"https://github.com/indieweb/jf2/issues/41": {
"type": "entry",
"url": "https://github.com/indieweb/jf2/issues/41",
"content": {
"text": "Not sure how this happened, but XRay, Monocle, Together and others are using the property called refs instead of references.",
"html": "<p>Not sure how this happened, but XRay, Monocle, Together and others are using the property called <code>refs</code> instead of <code>references</code>.</p>"
},
"author": {
"type": "card",
"name": "aaronpk",
"url": "https://github.com/aaronpk",
"photo": null
},
"post-type": "note"
}
},
"_id": "12942772",
"_source": "1886",
"_is_read": true
}
{
"type": "entry",
"published": "2020-07-03 18:04-0700",
"url": "http://tantek.com/2020/185/b1/meetable-redirect-tag-tags",
"in-reply-to": [
"https://github.com/aaronpk/Meetable/issues"
],
"name": "Meetable should redirect /tag to /tags",
"content": {
"text": "Currently meetable supports tag browsing pages like: https://events.indieweb.org/tag/hwc\n\n\nHowever if you trim the last segment, you get a 404: https://events.indieweb.org/tag/ or https://events.indieweb.org/tag\n\n\nMeetable should instead redirect those to: https://events.indieweb.org/tags\n\n\nAdditionally, Meetable should consider redirecting https://events.indieweb.org/tags/ with the trailing slash to https://events.indieweb.org/tags without the trailing slash instead of serving duplicate content at those two URLs.",
"html": "<p>\nCurrently meetable supports tag browsing pages like: https://events.indieweb.org/tag/hwc\n</p>\n<p>\nHowever if you trim the last segment, you get a 404: https://events.indieweb.org/tag/ or https://events.indieweb.org/tag\n</p>\n<p>\nMeetable should instead redirect those to: https://events.indieweb.org/tags\n</p>\n<p>\nAdditionally, Meetable should consider redirecting https://events.indieweb.org/tags/ with the trailing slash to https://events.indieweb.org/tags without the trailing slash instead of serving duplicate content at those two URLs.\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/aaronpk/Meetable/issues": {
"type": "entry",
"url": "https://github.com/aaronpk/Meetable/issues",
"name": "GitHub project \u201cMeetable\u201d",
"post-type": "article"
}
},
"_id": "12937951",
"_source": "1",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Neil Mather",
"url": "https://doubleloop.net/",
"photo": null
},
"url": "https://doubleloop.net/2020/07/03/resisting-the-feudal-internet/",
"published": "2020-07-03T19:24:47+00:00",
"content": {
"html": "Via <a href=\"https://twitter.com/pfrazee\">@pfrazee</a>\u2018s <a href=\"https://infocivics.com/\">article</a> on <a href=\"https://commonplace.doubleloop.net/20200703195401-information_civics.html\">information civics</a>, came across this old <a href=\"http://en.collaboratory.de/w/Power_in_the_Age_of_the_Feudal_Internet\">article of Bruce Schneier</a>\u2018s on what he calls the <a href=\"https://commonplace.doubleloop.net/20200703195230-feudal_internet.html\">feudal internet</a>.\n<p>In his analogy, we\u2019re the peasants who have traded in freedom for some convenience and protection.</p>\n<blockquote><p>Users pledge allegiance to more powerful companies who, in turn, promise to protect them from both sysadmin duties and security threats.</p></blockquote>\n<p>He sees the two big power centres of the feudal lords as data and devices.</p>\n<blockquote><p>On the corporate side, power is consolidating around both vendor-managed user devices and large personal-data aggregators.</p></blockquote>\n<p>We no longer have control of our data:</p>\n<blockquote><p>Our e-mail, photos, calendar, address book, messages, and documents are on servers belonging to Google, Apple, Microsoft, Facebook, and so on.</p></blockquote>\n<p>I see the <a href=\"https://commonplace.doubleloop.net/indieweb.html\">IndieWeb</a>, <a href=\"https://commonplace.doubleloop.net/20200524104248-beaker_browser.html\">Beaker</a>, etc as means of resisting this.</p>\n<p>And we\u2019re no longer in control of our devices:</p>\n<blockquote><p>And second, the rise of vendor-managed platforms means that we no longer have control of our computing devices. We\u2019re increasingly accessing our data using iPhones, iPads, Android phones, Kindles, ChromeBooks, and so on.</p></blockquote>\n<p>I see the <a href=\"https://commonplace.doubleloop.net/20200308230733-right_to_repair.html\">right to repair</a> as a means of resisting this. Allowing us to do what we wish with our own devices \u2013 including putting whatever software on them that we want.</p>\n<p>One big omission from the article I find is that Schneier focuses on the disbenefits to the users of these devices and platforms \u2013 the <a href=\"https://commonplace.doubleloop.net/20200628115311-manufactured_islaves.html\">manufactured iSlaves</a>, in Jack Qiu\u2019s terminology. He doesn\u2019t mention (at least in this particular article) those exploited in the creation and upkeep of these \u2013 the <a href=\"https://commonplace.doubleloop.net/20200628114916-manufacturing_islaves.html\">manufacturing iSlaves</a>. That\u2019s just as big, if not bigger, a reason for challenging these power structures.</p>",
"text": "Via @pfrazee\u2018s article on information civics, came across this old article of Bruce Schneier\u2018s on what he calls the feudal internet.\nIn his analogy, we\u2019re the peasants who have traded in freedom for some convenience and protection.\nUsers pledge allegiance to more powerful companies who, in turn, promise to protect them from both sysadmin duties and security threats.\nHe sees the two big power centres of the feudal lords as data and devices.\nOn the corporate side, power is consolidating around both vendor-managed user devices and large personal-data aggregators.\nWe no longer have control of our data:\nOur e-mail, photos, calendar, address book, messages, and documents are on servers belonging to Google, Apple, Microsoft, Facebook, and so on.\nI see the IndieWeb, Beaker, etc as means of resisting this.\nAnd we\u2019re no longer in control of our devices:\nAnd second, the rise of vendor-managed platforms means that we no longer have control of our computing devices. We\u2019re increasingly accessing our data using iPhones, iPads, Android phones, Kindles, ChromeBooks, and so on.\nI see the right to repair as a means of resisting this. Allowing us to do what we wish with our own devices \u2013 including putting whatever software on them that we want.\nOne big omission from the article I find is that Schneier focuses on the disbenefits to the users of these devices and platforms \u2013 the manufactured iSlaves, in Jack Qiu\u2019s terminology. He doesn\u2019t mention (at least in this particular article) those exploited in the creation and upkeep of these \u2013 the manufacturing iSlaves. That\u2019s just as big, if not bigger, a reason for challenging these power structures."
},
"name": "Resisting the feudal Internet",
"post-type": "article",
"_id": "12934599",
"_source": "1895",
"_is_read": true
}
This is what happens when you accidentally feed incorrect post data to #Blogblaze and the h-entry template rendering fails. #webdevelopment #frontend #Deno #webdesign #IndieWeb
{
"type": "entry",
"published": "2020-07-03T18:02:27+00:00",
"url": "https://fireburn.ru/posts/1593799347",
"category": [
"Blogblaze",
"webdevelopment",
"frontend",
"Deno",
"webdesign",
"IndieWeb"
],
"photo": [
"https://fireburn.ru/media/c5/ea/e7/07/6ff1e054cd8aa0a7e8e04b9ee1f095805c7f9394eccbf9e04713e8f3.png"
],
"syndication": [
"https://twitter.com/kisik21/status/1279113315222986753"
],
"content": {
"text": "This is what happens when you accidentally feed incorrect post data to #Blogblaze and the h-entry template rendering fails. #webdevelopment #frontend #Deno #webdesign #IndieWeb",
"html": "<p>This is what happens when you accidentally feed incorrect post data to #Blogblaze and the h-entry template rendering fails. #webdevelopment #frontend #Deno #webdesign #IndieWeb</p>"
},
"author": {
"type": "card",
"name": "Vika",
"url": "https://fireburn.ru/",
"photo": "https://fireburn.ru/media/f1/5a/fb/9b/081efafb97b4ad59f5025cf2fd0678b8f3e20e4c292489107d52be09.png"
},
"post-type": "photo",
"_id": "12930314",
"_source": "1371",
"_is_read": true
}
{
"type": "entry",
"published": "2020-07-03T13:27:37Z",
"url": "https://adactio.com/journal/17086",
"category": [
"",
"css",
"colours",
"schemes",
"styles",
"switcher",
"toggle",
"light",
"dark",
"modes",
"indiewebcamp",
"styling",
"images",
"frontend",
"development",
"design"
],
"syndication": [
"https://medium.com/@adactio/194630f97c43"
],
"name": "Dark mode revisited",
"content": {
"text": "I added a dark mode to my website a while back. It was a fun thing to do during Indie Web Camp Amsterdam last year.\n\nI tied the colour scheme to the operating system level. If you choose a dark mode in your OS, my website will adjust automatically thanks to the prefers-color-scheme: dark media query.\n\nBut I\u2019ve seen notes from a few friends, not about my site specifically, but about how they like having an explicit toggle for dark mode (as well as the media query). Whenever I read those remarks, I\u2019d think \u201cI\u2019m really not sure I\u2019ve got time to deal with adding that kind of toggle to my site.\u201d\n\nBut then I realised, \u201cJeremy, you absolute muffin! You\u2019ve had a theme switcher on your website for almost two decades now!\u201d\n\nDoh! I had forgotten about that theme switcher. It dates back to the early days of CSS. I wanted my site to be a demonstration of how you could apply different styles to the same underlying markup (this was before the CSS Zen Garden came along). Those themes are very dated now, but if you like you can view my site with a Zeldman theme or a sci-fi theme.\n\nTo offer a dark-mode theme for my site, all I had to do was take the default stylesheet, pull out the custom properties from the prefers-color-scheme: dark media query, and done. It took less than five minutes.\n\nSo if you want to view my site in dark mode, it\u2019s one of the options in the \u201cCustomise\u201d dropdown on every page of the website.",
"html": "<p><a href=\"https://adactio.com/journal/15941\">I added a dark mode to my website a while back</a>. It was a fun thing to do during Indie Web Camp Amsterdam last year.</p>\n\n<p>I tied the colour scheme to the operating system level. If you choose a dark mode in your OS, my website will adjust automatically thanks to the <code>prefers-color-scheme: dark</code> media query.</p>\n\n<p>But I\u2019ve seen notes from a few friends, not about my site specifically, but about how they like having an explicit toggle for dark mode (as well as the media query). Whenever I read those remarks, I\u2019d think \u201cI\u2019m really not sure I\u2019ve got time to deal with adding that kind of toggle to my site.\u201d</p>\n\n<p>But then I realised, \u201cJeremy, you absolute muffin! You\u2019ve had a theme switcher on your website for almost two decades now!\u201d</p>\n\n<p>Doh! I had forgotten about that theme switcher. It dates back to the early days of CSS. I wanted my site to be a demonstration of how you could apply different styles to the same underlying markup (this was before the CSS Zen Garden came along). Those themes are very dated now, but if you like you can view my site with <a href=\"https://adactio.com/?skin=zeldman\">a Zeldman theme</a> or <a href=\"https://adactio.com/?skin=sci-fi\">a sci-fi theme</a>.</p>\n\n<p>To offer a dark-mode theme for my site, all I had to do was take the default stylesheet, pull out the custom properties from the <code>prefers-color-scheme: dark</code> media query, and done. It took less than five minutes.</p>\n\n<p>So if you want to view my site <a href=\"https://adactio.com/?skin=dark\">in dark mode</a>, it\u2019s one of the options in the \u201cCustomise\u201d dropdown on every page of the website.</p>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "article",
"_id": "12923943",
"_source": "2",
"_is_read": true
}
Catching up on a couple of the sessions I missed at IndieWebCamp West. All the videos are linked on the schedule page here.
{
"type": "entry",
"author": {
"name": "Manton Reece",
"url": "https://www.manton.org/",
"photo": "https://micro.blog/manton/avatar.jpg"
},
"url": "https://www.manton.org/2020/07/02/catching-up-on.html",
"content": {
"html": "<p>Catching up on a couple of the sessions I missed at IndieWebCamp West. All the videos are linked <a href=\"https://indieweb.org/2020/West/Schedule\">on the schedule page here</a>.</p>",
"text": "Catching up on a couple of the sessions I missed at IndieWebCamp West. All the videos are linked on the schedule page here."
},
"published": "2020-07-02T15:03:22-05:00",
"post-type": "note",
"_id": "12908389",
"_source": "12",
"_is_read": true
}
{
"type": "entry",
"published": "2020-07-01 18:00-0700",
"rsvp": "yes",
"url": "http://tantek.com/2020/183/t1/homebrew-website-club-west-coast",
"in-reply-to": [
"https://events.indieweb.org/2020/07/homebrew-website-club-west-coast-gIN0wgZCOdeP"
],
"content": {
"text": "hosting Homebrew Website Club West Coast NOW!\n\ud83d\uddd3 started at 18:00, seven of us here, hop on Zoom and say hi!\nhttps://events.indieweb.org/2020/07/homebrew-website-club-west-coast-gIN0wgZCOdeP\n@brb_irl @Kongaloosh @AllAboutGeorge @JackyAlcine @AndiGalpern @indirect @generativist @BenWerd @pvh @aaronpk",
"html": "hosting Homebrew Website Club West Coast NOW!<br />\ud83d\uddd3 started at 18:00, seven of us here, hop on Zoom and say hi!<br /><a href=\"https://events.indieweb.org/2020/07/homebrew-website-club-west-coast-gIN0wgZCOdeP\">https://events.indieweb.org/2020/07/homebrew-website-club-west-coast-gIN0wgZCOdeP</a><br /><a class=\"h-cassis-username\" href=\"https://twitter.com/brb_irl\">@brb_irl</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/Kongaloosh\">@Kongaloosh</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/AllAboutGeorge\">@AllAboutGeorge</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/JackyAlcine\">@JackyAlcine</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/AndiGalpern\">@AndiGalpern</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/indirect\">@indirect</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/generativist\">@generativist</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/BenWerd\">@BenWerd</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/pvh\">@pvh</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/aaronpk\">@aaronpk</a>"
},
"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/07/homebrew-website-club-west-coast-gIN0wgZCOdeP": {
"type": "entry",
"url": "https://events.indieweb.org/2020/07/homebrew-website-club-west-coast-gIN0wgZCOdeP",
"name": "an IndieWeb event",
"post-type": "article"
}
},
"_id": "12887511",
"_source": "1",
"_is_read": true
}
For all of y’all who make Twitter threads, now you can do that and then publish it BACK to your site using a standard in publishing content on the Web: Micropub! https://twitter.com/threadreaderapp/status/1276635958708862976
{
"type": "entry",
"published": "2020-07-01T16:30:26.78885-07:00",
"url": "https://v2.jacky.wtf/post/f141c646-507a-431b-8984-7443a03b60f5",
"content": {
"text": "For all of y\u2019all who make Twitter threads, now you can do that and then publish it BACK to your site using a standard in publishing content on the Web: Micropub! https://twitter.com/threadreaderapp/status/1276635958708862976",
"html": "<p>For all of y\u2019all who make Twitter threads, now you can do that and then publish it BACK to your site using a standard in publishing content on the Web: Micropub! <a href=\"https://twitter.com/threadreaderapp/status/1276635958708862976\">https://twitter.com/threadreaderapp/status/1276635958708862976</a></p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "note",
"_id": "12883589",
"_source": "1886",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Neil Mather",
"url": "https://doubleloop.net/",
"photo": null
},
"url": "https://doubleloop.net/2020/07/01/control-of-computing-infrastructure/",
"published": "2020-07-01T20:48:01+00:00",
"content": {
"html": "<p>I had not really thought much about the tech firms in this light before \u2013 of the undue control they have on computing infrastructure. (I think the author here including both hardware and software platforms in \u2018infrastructure\u2019).</p>\n<blockquote><p>In all the global crises, pandemics and social upheavals that may yet come, those in control of the computers, not those with the largest datasets, have the best visibility and the best \u2013 and perhaps the scariest \u2014 ability to change the world.</p>\n<p>\u2013 <a href=\"https://www.theguardian.com/commentisfree/2020/jul/01/apple-google-contact-tracing-app-tech-giant-digital-rights\">Privacy is not the problem with the Apple-Google contact-tracing toolkit</a></p></blockquote>\n<p>I don\u2019t know if it\u2019s a bigger problem or not than <a href=\"https://commonplace.doubleloop.net/surveillance-capitalism.html\">surveillance capitalism</a> though. They both seem like big problems, in tandem.</p>\n<p>The distinction between harvesting data and running the platform seems pretty neglible, too. Unless maybe he\u2019s talking about things like Amazon Web Services more than things like Facebook?</p>\n<p>Dunno. Regardless, cool to see both <a href=\"https://commonplace.doubleloop.net/20200308230733-right_to_repair.html\">right to repair</a> and <a href=\"https://commonplace.doubleloop.net/indieweb.html\">IndieWeb</a>-adjacent stuff mentioned together as modes of resistance against big tech.</p>",
"text": "I had not really thought much about the tech firms in this light before \u2013 of the undue control they have on computing infrastructure. (I think the author here including both hardware and software platforms in \u2018infrastructure\u2019).\nIn all the global crises, pandemics and social upheavals that may yet come, those in control of the computers, not those with the largest datasets, have the best visibility and the best \u2013 and perhaps the scariest \u2014 ability to change the world.\n\u2013 Privacy is not the problem with the Apple-Google contact-tracing toolkit\nI don\u2019t know if it\u2019s a bigger problem or not than surveillance capitalism though. They both seem like big problems, in tandem.\nThe distinction between harvesting data and running the platform seems pretty neglible, too. Unless maybe he\u2019s talking about things like Amazon Web Services more than things like Facebook?\nDunno. Regardless, cool to see both right to repair and IndieWeb-adjacent stuff mentioned together as modes of resistance against big tech."
},
"name": "Control of computing infrastructure",
"post-type": "article",
"_id": "12882091",
"_source": "1895",
"_is_read": true
}
