Why is @twitter lockeddown!!!!? I need a haircut!!!!
{
"type": "entry",
"published": "2020-07-15T18:53:38-04:00",
"url": "https://kartikprabhu.com/notes/twitter-lockdown-haircut",
"category": [
"indieweb",
"web",
"lockdown"
],
"syndication": [
"https://twitter.com/kartik_prabhu/status/1283535491900551179"
],
"content": {
"text": "Why is @twitter lockeddown!!!!? I need a haircut!!!!"
},
"author": {
"type": "card",
"name": "Kartik Prabhu",
"url": "https://kartikprabhu.com/about#me",
"photo": "https://kartikprabhu.com/static/images/avatar.jpg"
},
"post-type": "note",
"_id": "13249058",
"_source": "204",
"_is_read": true
}
Sure, I never made a note of that being the direction though. That’s the fallacy of Mastodon since it wanted to replicate Tweetdeck (kinda understandably). The IndieWeb doesn’t have this problem though.
{
"type": "entry",
"published": "2020-07-15T14:58:00.00000-07:00",
"url": "https://v2.jacky.wtf/post/96da1e62-f6fa-4371-a719-8a148d9d3338",
"in-reply-to": [
"https://twitter.com/smudgethefirst/status/1283520581762256901"
],
"content": {
"text": "Sure, I never made a note of that being the direction though. That\u2019s the fallacy of Mastodon since it wanted to replicate Tweetdeck (kinda understandably). The IndieWeb doesn\u2019t have this problem though.",
"html": "<p>Sure, I never made a note of that being the direction though. That\u2019s the fallacy of Mastodon since it wanted to replicate Tweetdeck (kinda understandably). The IndieWeb doesn\u2019t have this problem though.</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "reply",
"refs": {
"https://twitter.com/smudgethefirst/status/1283520581762256901": {
"type": "entry",
"url": "https://twitter.com/smudgethefirst/status/1283520581762256901",
"author": {
"type": "card",
"name": "twitter.com",
"url": "https://twitter.com/smudgethefirst/status/1283520581762256901",
"photo": null
},
"post-type": "note"
}
},
"_id": "13245965",
"_source": "1886",
"_is_read": true
}
{
"type": "entry",
"published": "2020-07-09T10:23:36-0400",
"url": "https://martymcgui.re/2020/07/09/my-notes-from-hwc-west-coast-2020-07-08/",
"category": [
"IndieWeb",
"meetup",
"HWC",
"virtual",
"vHWC",
"west-coast",
"wrap-up"
],
"name": "My notes from HWC West Coast 2020-07-08",
"content": {
"text": "Yesterday I joined in the West Coast Homebrew Website Club via Zoom. I was worried I'd be too tired to join - it was held 9-10:30pm my time - but after a nice dinner and wind-down from the day I was in a pretty good place.\nJacky shared some demos, reading, and brainstorming (go check 'em out). And, as captured in Tantek's notes, we also got into some good discussion about community onboarding prompted by Sarah.\nA recurring theme as new folks join the IndieWeb community is that the wiki is an amazing resource but also a source of crippling information overload. In recent years we have discussed ways to (re-)organize content for folks geting their own site started. On his own, Jason has begun writing guided intros for developers on topics like Webmention. But as Sarah pointed out, IndieWeb is much more than just developer documentation or guides for folks setting up their own websites. IndieWeb is also an active community with frequent live events, 24/7 discussions, and a long-term memory of observations and ideas and projects and participants. So, perhaps it's worth thinking about onboarding from a perspective of introducing new folks to this community, what they can expect, and how to successfully engage.\nFor my part, I continued research into the cursed project that I've been noodling on for years and finally started during IndieWebCamp 2020 West. My goal is to give folks a free way to dip their toes into the IndieWeb without needing to understand the building blocks first, but with on-ramps to understanding, customizing, and improving any part of it. While I am learning a lot from projects like Postr, I think I will end up actually making my own version of building blocks like authorization, token, and micropub endpoints. By way of being careful, I would like to be able to test that each one works properly. So that's how I ended up volunteering to help build out the IndieAuth.rocks test suite. \ud83d\ude05\n\n I really enjoy and appreciate these meetups and I look forward to joining the next one!",
"html": "<p>Yesterday I joined in the <a href=\"https://events.indieweb.org/2020/07/homebrew-website-club-west-coast-ZObv0hlGOdR5\">West Coast Homebrew Website Club</a> via Zoom. I was worried I'd be too tired to join - it was held 9-10:30pm my time - but after a nice dinner and wind-down from the day I was in a pretty good place.</p>\n<p><a href=\"https://v2.jacky.wtf/post/41319324-8a31-41aa-a61a-6851fdf78a6c\">Jacky shared some demos, reading, and brainstorming</a> (go check 'em out). And, as captured in <a href=\"https://tantek.com/2020/190/t2/homebrew-website-club-west\">Tantek's notes</a>, we also got into some good discussion about community onboarding prompted by <a href=\"http://sarah-hibner.com/\">Sarah</a>.</p>\n<p>A recurring theme as new folks join the IndieWeb community is that <a href=\"https://indieweb.org/\">the wiki</a> is an amazing resource but also a source of crippling information overload. In recent years we have discussed ways to <a href=\"https://indieweb.org/2019/homepage\">(re-)organize content for folks geting their own site started</a>. On his own, <a href=\"https://jmac.org/\">Jason</a> has begun writing <a href=\"https://jmac.org/webmention/\">guided intros for developers on topics like Webmention</a>. But as Sarah pointed out, IndieWeb is much more than just developer documentation or guides for folks setting up their own websites. IndieWeb is also an active community with <a href=\"https://events.indieweb.org/\">frequent live events</a>, <a href=\"https://indieweb.org/discuss\">24/7 discussions</a>, and a <a href=\"https://indieweb.org/\">long-term memory</a> of observations and ideas and projects and participants. So, perhaps it's worth thinking about onboarding from a perspective of introducing new folks to this community, what they can expect, and how to successfully engage.</p>\n<p>For my part, I continued research into <a href=\"https://indieweb.org/User:Martymcgui.re/IndieWeb-Sandbox\">the cursed project</a> that I've been noodling on for years and finally started during IndieWebCamp 2020 West. My goal is to give folks a free way to dip their toes into the IndieWeb <i>without</i> needing to understand the building blocks first, but with on-ramps to understanding, customizing, and improving any part of it. While I am learning a lot from projects like <a href=\"https://github.com/grantcodes/postr\">Postr</a>, I think I will end up actually making my own version of building blocks like authorization, token, and micropub endpoints. By way of being careful, I would like to be able to test that each one works properly. So that's how I ended up volunteering to help build out the <a href=\"https://indieauth.rocks/\">IndieAuth.rocks</a> test suite. \ud83d\ude05</p>\n<p>\n I really enjoy and appreciate these meetups and I look forward to joining the next one!\n <br /></p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "article",
"_id": "13241091",
"_source": "175",
"_is_read": true
}
A post with a bit of preamble about how link backs work and a release of a plugin for Pelican for sending Webmentions.
{
"type": "entry",
"published": "2020-07-15T11:38:15.56704-07:00",
"url": "https://v2.jacky.wtf/post/4b5e2a14-5bd4-4bfb-80fb-667f6dd99ab1",
"bookmark-of": [
"https://chezsoi.org/lucas/blog/pelican-pingback-and-webmentions.html"
],
"content": {
"text": "A post with a bit of preamble about how link backs work and a release of a plugin for Pelican for sending Webmentions.",
"html": "<p>A post with a bit of preamble about how link backs work and a release of a plugin for <a href=\"https://blog.getpelican.com/\">Pelican</a> for sending Webmentions.</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "bookmark",
"refs": {
"https://chezsoi.org/lucas/blog/pelican-pingback-and-webmentions.html": {
"type": "entry",
"url": "https://chezsoi.org/lucas/blog/pelican-pingback-and-webmentions.html",
"author": {
"type": "card",
"name": "Lucas Cimon",
"url": "https://v2.jacky.wtf/stream",
"photo": null
},
"post-type": "note"
}
},
"_id": "13240676",
"_source": "1886",
"_is_read": true
}
#100days 70 - Readded a token endpoint to my site letting me publish to it and log into indieauth enabled services again like Together
{
"type": "entry",
"published": "2020-07-14T18:39:53.790Z",
"url": "https://grant.codes/2020/07/14/06-39-53",
"category": [
"100days"
],
"content": {
"text": "#100days 70 - Readded a token endpoint to my site letting me publish to it and log into indieauth enabled services again like Together",
"html": "<p>#100days 70 - Readded a token endpoint to my site letting me publish to it and log into indieauth enabled services again like <a href=\"https://alltogethernow.io\">Together</a></p>"
},
"post-type": "note",
"_id": "13234737",
"_source": "11",
"_is_read": true
}
{
"type": "entry",
"published": "2020-07-13T21:29:46+0000",
"url": "http://www.funwhilelost.com/2020/posting-to-the-fediverse-from-my-indieweb-site",
"name": "Posting to the Fediverse from my IndieWeb site",
"content": {
"text": "Hopefully this gets picked up and Webmentioned to brid.gy's cool Mastodon POSSE!\u00a0\u00a0",
"html": "<p>Hopefully this gets picked up and Webmentioned to brid.gy's cool Mastodon POSSE!</p><p>\u00a0</p><p>\u00a0</p>"
},
"author": {
"type": "card",
"name": "Andy Jacobs",
"url": "http://www.funwhilelost.com/profile/funwhilelost",
"photo": "http://www.funwhilelost.com/file/fa79187640f271e6a8584ac106c82f5e/thumb.jpg"
},
"post-type": "article",
"_id": "13191147",
"_source": "232",
"_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/07/13/sneak-peek-at.html",
"name": "Sneak peek at Sunlit 3.0",
"content": {
"html": "<p>Our app Sunlit has an interesting history. Jonathan Hays and I came up with <a href=\"https://www.manton.org/2014/01/15/why-we-built.html\">the original concept</a> for the app way back in 2012. The app changed form a couple times, first building off of App.net, and then adapted for blogging. Along the way, it accumulated a lot of baggage \u2014\u00a0old code and old designs that made it difficult to keep improving the app.</p>\n\n<p>Today I\u2019d like to give a sneak peek at what\u2019s next for Sunlit: version 3.0, a complete rewrite, sharing essentially no code with previous versions. Jon has been working on this for a while, leading development while I focus most of my time on Micro.blog itself. We are taking what we\u2019ve learned and trying to build an app that can appeal to people looking for an Instagram alternative, as well as people who want more control over publishing blog posts with multiple photos.</p>\n\n<p>Here are a couple screenshots:</p>\n\n<p><img src=\"https://www.manton.org/uploads/2020/af4b460ce7.png\" alt=\"Sunlit 3.0 screenshots\" border=\"0\" width=\"620\" height=\"650\" /></p>\n\n<p>The app will also be <em>completely open source</em>. It can publish to Micro.blog, WordPress, or via Micropub to IndieWeb blogs. It\u2019s written in Swift. There\u2019s no release date yet, but there will be a public beta, and we hope to take the time to get it right.</p>",
"text": "Our app Sunlit has an interesting history. Jonathan Hays and I came up with the original concept for the app way back in 2012. The app changed form a couple times, first building off of App.net, and then adapted for blogging. Along the way, it accumulated a lot of baggage \u2014\u00a0old code and old designs that made it difficult to keep improving the app.\n\nToday I\u2019d like to give a sneak peek at what\u2019s next for Sunlit: version 3.0, a complete rewrite, sharing essentially no code with previous versions. Jon has been working on this for a while, leading development while I focus most of my time on Micro.blog itself. We are taking what we\u2019ve learned and trying to build an app that can appeal to people looking for an Instagram alternative, as well as people who want more control over publishing blog posts with multiple photos.\n\nHere are a couple screenshots:\n\n\n\nThe app will also be completely open source. It can publish to Micro.blog, WordPress, or via Micropub to IndieWeb blogs. It\u2019s written in Swift. There\u2019s no release date yet, but there will be a public beta, and we hope to take the time to get it right."
},
"published": "2020-07-13T11:03:37-05:00",
"category": [
"Photos",
"Essays"
],
"post-type": "article",
"_id": "13179249",
"_source": "12",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Neil Mather",
"url": "https://doubleloop.net/",
"photo": null
},
"url": "https://doubleloop.net/2020/07/11/massively-multiplayer-open-computing/",
"published": "2020-07-11T22:02:08+00:00",
"content": {
"html": "A video by <a href=\"https://commonplace.doubleloop.net/20200711220816-paul_frazee.html\">Paul Frazee</a> about <a href=\"https://commonplace.doubleloop.net/20200524104248-beaker_browser.html\">Beaker Browser</a>.\n<ul><li><a href=\"https://invidio.us/watch?v=x3ShGXYCPWQ\">invidio.us/watch?v=x3ShGXYCPWQ</a></li>\n</ul><p>Paul states some of the goals of Beaker:</p>\n<ul><li>more software freedom (no code hidden away on a server)</li>\n<li>lowering the barriers to creating and publishing an app or a website</li>\n<li>more opportunity</li>\n<li>having fun \u2013 keeping the web individual and diverse</li>\n</ul><p>It\u2019s very adjacent to <a href=\"https://commonplace.doubleloop.net/indieweb.html\">IndieWeb</a> to me. Everyone has their own profile drive, which is kind of like your personal website. All the data is yours \u2013 it\u2019s attached to your hyperdrive. <a href=\"https://commonplace.doubleloop.net/20200711222606-own_your_data.html\">Own your data</a>. And apps access the data in your hyperdrive, you don\u2019t send anything to them.</p>\n<p>One very nice thing with Beaker, you get your Beaker profile just by running the browser \u2013 you don\u2019t need to set up and maintain a server. (<a href=\"https://commonplace.doubleloop.net/20200711224933-no_servers_no_admins.html\">No Servers! No Admins!</a>) You also get an easy to maintain address book, where you can basically follow other people.</p>\n<p>I like the idea of being able to fork apps easily, too. It\u2019s as if you were using Facebook, but you wanted to change part of the interface, and you could, because you have immediate access to the source and can just fork it and tweak it.</p>",
"text": "A video by Paul Frazee about Beaker Browser.\ninvidio.us/watch?v=x3ShGXYCPWQ\nPaul states some of the goals of Beaker:\nmore software freedom (no code hidden away on a server)\nlowering the barriers to creating and publishing an app or a website\nmore opportunity\nhaving fun \u2013 keeping the web individual and diverse\nIt\u2019s very adjacent to IndieWeb to me. Everyone has their own profile drive, which is kind of like your personal website. All the data is yours \u2013 it\u2019s attached to your hyperdrive. Own your data. And apps access the data in your hyperdrive, you don\u2019t send anything to them.\nOne very nice thing with Beaker, you get your Beaker profile just by running the browser \u2013 you don\u2019t need to set up and maintain a server. (No Servers! No Admins!) You also get an easy to maintain address book, where you can basically follow other people.\nI like the idea of being able to fork apps easily, too. It\u2019s as if you were using Facebook, but you wanted to change part of the interface, and you could, because you have immediate access to the source and can just fork it and tweak it."
},
"name": "Massively multiplayer open computing",
"post-type": "article",
"_id": "13139389",
"_source": "1895",
"_is_read": true
}
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
}
