Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2020-07-15 16:04-0700",
    "url": "http://tantek.com/2020/197/t2/good-indieweb-reminder",
    "category": [
        "IndieWeb",
        "BlueChecks"
    ],
    "content": {
        "text": "Good #IndieWeb reminder from @brentsimmons: https://inessential.com/2020/07/15/zillion_times_easier (https://twitter.com/brentsimmons/status/1283534944493502470)\n\nAnd #BlueChecks appear to be frozen, unable to tweet, only retweet.\n\nSo of course this exists: @EveryWord",
        "html": "Good #<span class=\"p-category\">IndieWeb</span> reminder from <a class=\"h-cassis-username\" href=\"https://twitter.com/brentsimmons\">@brentsimmons</a>: <a href=\"https://inessential.com/2020/07/15/zillion_times_easier\">https://inessential.com/2020/07/15/zillion_times_easier</a> (<a href=\"https://twitter.com/brentsimmons/status/1283534944493502470\">https://twitter.com/brentsimmons/status/1283534944493502470</a>)<br /><br />And #<span class=\"p-category\">BlueChecks</span> appear to be frozen, unable to tweet, only retweet.<br /><br />So of course this exists: <a class=\"h-cassis-username\" href=\"https://twitter.com/EveryWord\">@EveryWord</a>"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "note",
    "_id": "13252640",
    "_source": "1",
    "_is_read": true
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2020-07-15 14:57-0700",
    "url": "http://tantek.com/2020/197/t1/twitterhacked-bitcoin-blockchain",
    "category": [
        "TwitterHacked",
        "Bitcoin",
        "blockchain",
        "dweb",
        "IndieWeb"
    ],
    "content": {
        "text": "#TwitterHacked. What she said https://twitter.com/AOC/status/1283513914597298178 via @b_cavello\n\nY\u2019all know:\n#Bitcoin is a coal-burning CO2 producing currency for organized crime\n#blockchain is mostly #dweb snakeoil (singleton, OSS monoculture)\n\nGo #IndieWeb or SSB for the real: https://indieweb.org/",
        "html": "#<span class=\"p-category\">TwitterHacked</span>. What she said <a href=\"https://twitter.com/AOC/status/1283513914597298178\">https://twitter.com/AOC/status/1283513914597298178</a> via <a class=\"h-cassis-username\" href=\"https://twitter.com/b_cavello\">@b_cavello</a><br /><br />Y\u2019all know:<br />#<span class=\"p-category\">Bitcoin</span> is a coal-burning CO2 producing currency for organized crime<br />#<span class=\"p-category\">blockchain</span> is mostly #<span class=\"p-category\">dweb</span> snakeoil (singleton, OSS monoculture)<br /><br />Go #<span class=\"p-category\">IndieWeb</span> or SSB for the real: <a href=\"https://indieweb.org/\">https://indieweb.org/</a>"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "note",
    "_id": "13252641",
    "_source": "1",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-07-15T18:14:00.00000-07:00",
    "url": "https://v2.jacky.wtf/post/e915caaa-787d-43b9-ab3a-aaa43c256acf",
    "content": {
        "text": "Currently!!! https://events.indieweb.org/2020/07/homebrew-website-club-west-coast-UWgdEMwxDSQI",
        "html": "<p>Currently!!! <a href=\"https://events.indieweb.org/2020/07/homebrew-website-club-west-coast-UWgdEMwxDSQI\">https://events.indieweb.org/2020/07/homebrew-website-club-west-coast-UWgdEMwxDSQI</a></p>"
    },
    "author": {
        "type": "card",
        "name": "",
        "url": "https://v2.jacky.wtf",
        "photo": null
    },
    "post-type": "note",
    "_id": "13250938",
    "_source": "1886",
    "_is_read": true
}

Marty McGuire martymcgui.re

{
    "type": "entry",
    "published": "2020-07-15T20:35:27-0400",
    "rsvp": "yes",
    "url": "https://martymcgui.re/2020/07/15/203527/",
    "in-reply-to": [
        "https://events.indieweb.org/2020/07/homebrew-website-club-west-coast-UWgdEMwxDSQI"
    ],
    "content": {
        "text": "I'm going!Looking forward to some IndieWeb thinking and chatting!",
        "html": "I'm going!<p>Looking forward to some IndieWeb thinking and chatting!</p>"
    },
    "author": {
        "type": "card",
        "name": "Marty McGuire",
        "url": "https://martymcgui.re/",
        "photo": "https://martymcgui.re/images/logo.jpg"
    },
    "post-type": "rsvp",
    "refs": {
        "https://events.indieweb.org/2020/07/homebrew-website-club-west-coast-UWgdEMwxDSQI": {
            "type": "entry",
            "summary": "Any questions? Ask in the IndieWeb chat!",
            "url": "https://events.indieweb.org/2020/07/homebrew-website-club-west-coast-UWgdEMwxDSQI",
            "photo": [
                "https://res.cloudinary.com/schmarty/image/fetch/w_960,c_fill/https://events.indieweb.org/storage/events/20200406-lBWNp28qEePEUsAbCI8YvPtFVX5CSy.jpg"
            ],
            "name": "Homebrew Website Club West Coast",
            "author": {
                "type": "card",
                "name": "events.indieweb.org",
                "url": "http://events.indieweb.org",
                "photo": null
            },
            "post-type": "photo"
        }
    },
    "_id": "13250414",
    "_source": "175",
    "_is_read": true
}

Marty McGuire martymcgui.re

What we talk about when we're talking about "Webmentions"

{
    "type": "entry",
    "published": "2020-07-15T19:31:31-0400",
    "url": "https://martymcgui.re/2020/07/15/what-we-talk-about-when-were-talking-about-webmentions/",
    "category": [
        "IndieWeb",
        "Webmention",
        "rant"
    ],
    "name": "What we talk about when we're talking about \"Webmentions\"",
    "content": {
        "text": "I have a great fondness for IndieWeb building blocks and Webmention is a wonderful meta-building-block that connects so many individual websites together.\n\n  Obligatory \"what is Webmention?\": it's a specification that describes a way to \"tell\" a website that some document out on the web links to one of the pages on that site. \n  \n\nSound simple? It is! Perhaps even suspiciously simple. Webmention enables whole new kinds of interactions between sites (some great examples in this A List Apart piece). Unfortunately, almost all of the coordination to support these interactions happen outside of the \"Webmention\" spec itself.\nSo, when I see blog post titles like these I am not sure exactly what to expect:\nIntegrating Webmention with my blog\n  Pelican, Pingback and Webmentions\n  Webmention for TiddlyWiki to enable website to website notifications and communication\n  and this clickbait sensation: Add Webmention support to your website in ten minutes\n\n\n  There are many more like this, I just grabbed a handful off the last few pages of news.indieweb.org.\n  \n\nThese examples and many more are referring to the most talked-about use of Webmention: enabling site-to-site comments and responses, like a souped-up independent alternative to terrible embeds like Disqus.\nThis may sound like a simple feature! We might expect it to look like this:\nYou see a post on the web that you like. Let's call that \"their post\".\n  On your own site, you make a post that links to theirs with some comment like \"Nice post!\". We'll call that \"your post\".\n  \n    Assuming that you both \"have Webmention support\", you might check their post a little later and see a nice summary of your post as a comment below their content.\n    \n\n However, for a webmention to \"succeed\", a lot of coordination needs to happen.\n\n  On your side:\n  \n\n\n    You publish \"your post\" which links to \"their post\". So far, so good, you probably publish links to your site all the time.\n    \n\n  When that post is live, you can try to send a webmention. How do you do that? It depends.\n\n  From here, it's pretty much out of your hands. On their side:\n  \n\n\n    Their post needs to advertise the URL of a service that will accept them.\n    \n\n  \n    That service checks that your post is a real post on the web, and that it contains a link to their post and it ... stores it somewhere. Maybe it goes into a moderation queue?\n    \n\nSo then they have the webmention, but to actually display it, their site must:\nPull your post out of wherever their webmentions are stored.\n  Somehow understand what your post \"is\".\n  \n    Render that into their page.\n    \n\nWhen I see folks posting \"I added Webmentions to my site\" I want to believe that they have some version of all of the bullet points above. But, there are lots of incompletes.\n\n  A list, without references, of partial Webmention support I have seen\n  \n\nThe Junk Drawer\nSigning up for a receiving service like webmention.io ... and that's it. Often announced alongside a sentence like \"Next up I'll figure out how to display them!\" This brings to mind with images of the warehouse at the end of Raiders of the Lost Ark, or a house filled to the ceiling with stacks of moldy newspapers.\n\n  There are, I recognize, lots of good reasons not to display webmentions, beyond some of the technical speedbumps and pitfalls I talk about below. For example there are a lot of unanswered questions and not-yet-built tools and services for dealing with moderation and abuse.\n  \n\n\"Why didn't my reply show up on your site?\"\n\n  Static sites are back and I love it. But if there's one thing that static sites do extremely poorly it is responding dynamically to outside events. Some static sites (including my own!) will save webmentions as the come in, but won't display them until the next time a post is added or modified on the site.\n  \n\n\n  \"Why does my reply look weird on your site?\"\n  \n\nFrom services to command line tools to fancy build hooks on your fancy hosting service, there are many ways to automate sending webmentions. But unless the receiving end can understand the content of your post, it might not show up as you intended, or at all, on the receiving end. Current best practices would have you add some extra markup to your post so that the receiver can know that it is a reply, or a like, or an RSVP, or something else. This is a hard coordination problem between your site and theirs! In fact there is a whole community and standards process for figuring out how to do these things!\nMaking sure your posts have the \"correct\" markup to look like you want can be difficult even for developers writing their own HTML. Tools like indiewebify.me, Monocle's preview, and microformats.io can help if you are getting your hands dirty. It's much harder for folks that just redesigned their site with a new WordPress theme.\n\n  Bridgy Over Troubled Waters\n  \n\nBridgy is an absolutely incredible suite of services provided by Ryan, also for free, for the community.\nWith the power of Bridgy Backfeed you can use Webmention to feed replies, likes, and reposts from your Twitter tweets to their corresponding post on your own site! This works despite the fact that twitter.com does not link to your website because Bridgy generates little \"bridge\" pages for which to send webmentions. And it's just a little bit of tweaking to have your Webmention display handle the quirks.\nWith the power of Bridge Publish you can use Webmention to automatically copy posts from your website directly to social media silos like Twitter! You do this by hiding a link to Bridgy in your post, which sends a Webmention to Bridgy, and then Bridgy parses your post to understand it and figure out which bits to tweet. And then Bridgy responds with info about your new tweet. And it's just a little bit of tweaking to have your Webmention sender handle those quirks and update your post with that link.\n\n  With the power of Bridge Fed you can use Webmention to automatically copy posts from your website directly into The Fediverse where yadda yadda yadda. And it's just a bit of tweaking to have your Webmention yadda yadda yadda yadda. \ud83d\ude29 I've tired myself out.\n  \n\n\n  These are all fantastic things that are build on top of Webmention but that I often feel are conflated with Webmention.\n  \n\n\"Just let JavaScript do it!\"\nThis one is a bit... unfair on my part. In fact, I think this setup is the best you can get for the least effort, and I encourage folks to go for it. It looks like this:\nRegister with webmention.io to receive, verify, and store your webmentions.\n  Put webmention.js in the template for your posts.\n\n  I love webmention.io and use it myself. It is an amazing community resource run by Aaron at no charge! Kevin's mention.tech is another great tool, as is VoxPelli's webmention.herokuapp.com. By configuring one of them to accept webmentions on your behalf you save a lot of trouble. They provide APIs that let you pull out the mentions for pages across your site.\n  \n\nSimilarly, webmention.js is a really great tool by fluffy that hides a lot of complexity and forethought about how to display webmentions with a single JavaScript include.\n\n  All that said, I have some issues with this particular combo long-term because all the fetching and display of webmentions happens in the browser of the person viewing your post.\n  \n\n\n  If 1,000 people visit your post, that's 1,000 requests to webmention.io, putting load on a service being run by one individual for free.\n  \n\nThis setup also means that the webmentions for a post aren't included in the original HTML. So, if your site sends a webmention and wants to check back automatically to see if it's shown up, but their site only displays webmentions via JavaScript, your site will never see it. Likewise, it becomes much harder to keep track of reply chains, for example.\nWhy are you being such a downer about this?\nDespite, apparently, being a bit salty today, I really do get excited about Webmention, how it's being used in so many ways to connect independent sites, and new ways it can be used in the future.\nI'm worried, a bit, that \"Webmention\" is starting to lose its meaning in conversation. It's starting to feel like a shorthand that hides important details.\nMaybe Webmention can be thought of as less of a \"building block\" and more like a glue. You can do so many things with glue, like combining a bunch of planks into a table, or building a parade float sculpture with papier-m\u00e2ch\u00e9, or doctoring the photo in a passport!\n\n  You wouldn't call them all \"glue\".",
        "html": "<p>I have a great fondness for <a href=\"https://indieweb.org/building-blocks\">IndieWeb building blocks</a> and <a href=\"https://indieweb.org/Webmention\">Webmention</a> is a wonderful meta-building-block that connects so many individual websites together.</p>\n<p>\n  Obligatory \"what is Webmention?\": it's a <a href=\"https://www.w3.org/TR/webmention/\">specification</a> that describes a way to \"tell\" a website that some document out on the web links to one of the pages on that site. \n  <br /></p>\n<p>Sound simple? It is! Perhaps even <i>suspiciously simple</i>. Webmention enables whole new kinds of interactions between sites (some <a href=\"https://alistapart.com/article/webmentions-enabling-better-communication-on-the-internet/\">great examples in this A List Apart piece</a>). Unfortunately, almost all of the coordination to support these interactions happen <i>outside</i> of the \"Webmention\" spec itself.</p>\n<p>So, when I see blog post titles like these I am not sure exactly what to expect:</p>\n<ul><li><a href=\"https://www.kappawingman.com/posts/webdev/2020/07/15/integrating-webmention-with-my-blog/\">Integrating Webmention with my blog</a></li>\n  <li><a href=\"https://chezsoi.org/lucas/blog/pelican-pingback-and-webmentions.html\">Pelican, Pingback and Webmentions</a></li>\n  <li><a href=\"https://boffosocko.com/2020/04/14/webmention-for-tiddlywiki-to-enable-website-to-website-notifications-and-communication/\">Webmention for TiddlyWiki to enable website to website notifications and communication</a></li>\n  <li>and this clickbait sensation: <a href=\"https://www.ctrl.blog/entry/setup-webmention.html\">Add Webmention support to your website in ten minutes</a>\n</li>\n</ul><p>\n  There are many more like this, I just grabbed a handful off the last few pages of <a href=\"https://news.indieweb.org/en\">news.indieweb.org</a>.\n  <br /></p>\n<p>These examples and many more are referring to the most talked-about use of Webmention: enabling site-to-site comments and responses, like a <a href=\"https://nicolas-hoizey.com/articles/2017/07/27/so-long-disqus-hello-webmentions/\">souped-up independent alternative to terrible embeds like Disqus</a>.</p>\n<p>This may sound like a simple feature! We might expect it to look like this:</p>\n<ul><li>You see a post on the web that you like. Let's call that \"their post\".</li>\n  <li>On your own site, you make a post that links to theirs with some comment like \"Nice post!\". We'll call that \"your post\".</li>\n  <li>\n    Assuming that you both \"have Webmention support\", you might check their post a little later and see a nice summary of your post as a comment below their content.\n    <br /></li>\n</ul><p> However, for a webmention to \"succeed\", a lot of coordination needs to happen.</p>\n<p>\n  On your side:\n  <br /></p>\n<ul><li>\n    You publish \"your post\" which links to \"their post\". So far, so good, you probably publish links to your site all the time.\n    <br /></li>\n  <li>When that post is live, you can try to send a webmention. How do you do that? <i>It depends</i>.</li>\n</ul><p>\n  From here, it's pretty much out of your hands. On their side:\n  <br /></p>\n<ul><li>\n    Their post needs to advertise the URL of a service that will accept them.\n    <br /></li>\n  <li>\n    That service checks that your post is a real post on the web, and that it contains a link to their post and it ... stores it somewhere. Maybe it goes into a moderation queue?\n    <br /></li>\n</ul><p>So then they <i>have</i> the webmention, but to actually <i>display </i>it, their site must:</p>\n<ul><li>Pull your post out of wherever their webmentions are stored.</li>\n  <li>Somehow <i>understand</i> what your post \"<i>is</i>\".</li>\n  <li>\n    Render that into their page.\n    <br /></li>\n</ul><p>When I see folks posting \"I added Webmentions to my site\" I want to believe that they have some version of all of the bullet points above. But, there are lots of incompletes.</p>\n<h2>\n  A list, without references, of partial Webmention support I have seen\n  <br /></h2>\n<h3>The Junk Drawer</h3>\n<p>Signing up for a receiving service like <a href=\"https://webmention.io/\">webmention.io</a> ... and that's it. Often announced alongside a sentence like \"Next up I'll figure out how to display them!\" This brings to mind with images of the warehouse at the end of Raiders of the Lost Ark, or a house filled to the ceiling with stacks of moldy newspapers.</p>\n<p>\n  There are, I recognize, lots of good reasons <i>not</i> to display webmentions, beyond some of the technical speedbumps and pitfalls I talk about below. For example there are a lot of unanswered questions and not-yet-built tools and services for dealing with moderation and abuse.\n  <br /></p>\n<h3>\"Why didn't my reply show up on your site?\"</h3>\n<p>\n  <a href=\"https://mxb.dev/blog/the-return-of-the-90s-web/\">Static sites are back</a> and I love it. But if there's one thing that static sites do extremely poorly it is responding dynamically to outside events. Some static sites (including my own!) will save webmentions as the come in, but won't display them until the next time a post is added or modified on the site.\n  <br /></p>\n<h3>\n  \"Why does my reply look weird on your site?\"\n  <br /></h3>\n<p>From <a href=\"https://webmention.app/\">services</a> to <a href=\"https://jmac.org/whim/\">command line tools</a> to <a href=\"https://www.jvt.me/posts/2019/09/10/webmentions-on-deploy/\">fancy build hooks on your fancy hosting service</a>, there are many ways to automate sending webmentions. But unless the receiving end can understand the content of your post, it might not show up as you intended, or at all, on the receiving end. Current best practices would have you <a href=\"https://aaronparecki.com/2018/06/30/11/your-first-webmention\">add some extra markup to your post</a> so that the receiver can know that it is a reply, or a like, or an RSVP, or something else. This is a hard coordination problem between your site and theirs! In fact <a href=\"http://microformats.org/\">there is a whole community and standards process for figuring out how to do these things</a>!</p>\n<p>Making sure your posts have the \"correct\" markup to look like you want can be difficult even for developers writing their own HTML. Tools like <a href=\"https://indiewebify.me/\">indiewebify.me</a>, <a href=\"https://monocle.p3k.io/preview\">Monocle's preview</a>, and <a href=\"https://microformats.io/\">microformats.io</a> can help if you are getting your hands dirty. It's much harder for folks that just redesigned their site with a new WordPress theme.</p>\n<h3>\n  Bridgy Over Troubled Waters\n  <br /></h3>\n<p><a href=\"https://brid.gy/\">Bridgy</a> is an <i>absolutely incredible</i> suite of services provided by <a href=\"https://snarfed.org/\">Ryan</a>, also for free, for the community.</p>\n<p>With the power of Bridgy Backfeed you can use Webmention to feed replies, likes, and reposts from your Twitter tweets to their corresponding post on your own site! This works despite the fact that twitter.com <i>does not link to your website</i> because Bridgy generates little \"bridge\" pages for which to send webmentions. And it's just a little bit of tweaking to have your Webmention display handle the quirks.</p>\n<p>With the power of Bridge Publish you can use Webmention to automatically copy posts from your website directly to social media silos like Twitter! You do this by hiding a link to Bridgy in your post, which sends a Webmention to Bridgy, and then Bridgy parses your post to <i>understand</i> it and figure out which bits to tweet. And then Bridgy responds with info about your new tweet. And it's just a little bit of tweaking to have your Webmention sender handle those quirks and update your post with that link.</p>\n<p>\n  With the power of Bridge Fed you can use Webmention to automatically copy posts from your website directly into The Fediverse where yadda yadda yadda. And it's just a bit of tweaking to have your Webmention yadda yadda yadda yadda. \ud83d\ude29 I've tired myself out.\n  <br /></p>\n<p>\n  These are all fantastic things that are build <i>on top of Webmention</i> but that I often feel are <i>conflated with Webmention</i>.\n  <br /></p>\n<h3>\"Just let JavaScript do it!\"</h3>\n<p>This one is a bit... unfair on my part. In fact, I think this setup is the best you can get for the least effort, and I encourage folks to go for it. It looks like this:</p>\n<ul><li>Register with webmention.io to receive, verify, and store your webmentions.</li>\n  <li>Put <a href=\"https://github.com/PlaidWeb/webmention.js/\">webmention.js</a> in the template for your posts.</li>\n</ul><p>\n  I love webmention.io and use it myself. It is an amazing community resource run by <a href=\"https://aaronparecki.com/\">Aaron</a> at no charge! <a href=\"http://www.kevinmarks.com/\">Kevin</a>'s <a href=\"http://mention.tech/\">mention.tech</a> is another great tool, as is <a href=\"http://voxpelli.com/\">VoxPelli</a>'s <a href=\"https://webmention.herokuapp.com/\">webmention.herokuapp.com</a>. By configuring one of them to accept webmentions on your behalf you save a lot of trouble. They provide APIs that let you pull out the mentions for pages across your site.\n  <br /></p>\n<p>Similarly, webmention.js is a really great tool by <a href=\"https://beesbuzz.biz/\">fluffy</a> that hides a lot of complexity and forethought about how to display webmentions with a single JavaScript include.</p>\n<p>\n  All that said, I have some issues with this particular combo long-term because all the fetching and display of webmentions happens in the browser of the person viewing your post.\n  <br /></p>\n<p>\n  If 1,000 people visit your post, that's 1,000 requests to webmention.io, putting load on a service being run by <a href=\"https://indieweb.org/single_point_of_aaron\">one individual</a> for free.\n  <br /></p>\n<p>This setup also means that the webmentions for a post aren't included in the original HTML. So, if your site sends a webmention and wants to check back automatically to see if it's shown up, but their site only displays webmentions via JavaScript, your site will never see it. Likewise, it becomes much harder to keep track of <a href=\"https://indieweb.org/reply-chain\">reply chains</a>, for example.</p>\n<h2>Why are you being such a downer about this?</h2>\n<p>Despite, apparently, being <i>a bit salty</i> today, I really do get excited about Webmention, how it's being used in so many ways to connect independent sites, and new ways it can be used in the future.</p>\n<p>I'm worried, a bit, that \"Webmention\" is starting to lose its meaning in conversation. It's starting to feel like a shorthand that hides important details.</p>\n<p>Maybe Webmention can be thought of as less of a \"building block\" and more like a glue. You can do so many things with glue, like combining a bunch of planks into a table, or building a parade float sculpture with papier-m\u00e2ch\u00e9, or doctoring the photo in a passport!</p>\n<p>\n  You wouldn't call them all \"glue\".\n  <br /></p>"
    },
    "author": {
        "type": "card",
        "name": "Marty McGuire",
        "url": "https://martymcgui.re/",
        "photo": "https://martymcgui.re/images/logo.jpg"
    },
    "post-type": "article",
    "_id": "13250415",
    "_source": "175",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-07-15T17:35:00.00000-07:00",
    "url": "https://v2.jacky.wtf/post/e366bb1f-694a-4f78-aaa4-6e6a66f88123",
    "category": [
        "hwc"
    ],
    "content": {
        "text": "I need to make sure I grab something to eat and finish my demo before the homebrew website club tonight! https://events.indieweb.org/2020/07/homebrew-website-club-west-coast-UWgdEMwxDSQI",
        "html": "<p>I need to make sure I grab something to eat and finish my demo before the homebrew website club tonight! <a href=\"https://events.indieweb.org/2020/07/homebrew-website-club-west-coast-UWgdEMwxDSQI\">https://events.indieweb.org/2020/07/homebrew-website-club-west-coast-UWgdEMwxDSQI</a></p>"
    },
    "author": {
        "type": "card",
        "name": "",
        "url": "https://v2.jacky.wtf",
        "photo": null
    },
    "post-type": "note",
    "_id": "13249806",
    "_source": "1886",
    "_is_read": true
}

{
    "type": "entry",
    "published": "2020-07-15T17:26:20.66818-07:00",
    "url": "https://v2.jacky.wtf/post/a55de486-144e-4012-8836-37c98220b984",
    "in-reply-to": [
        "https://twitter.com/toyinariyo66/status/1283556875871690752"
    ],
    "content": {
        "text": "The IndieWeb doesn\u2019t have \u201cusers\u201d, lol. It\u2019s all people. No VC fluff, no \u201cwe gotta hit the KPI!\u201d. People-centric and driven.But nah, these events are moments to study and reflect on. Smugness helps no one (since again, we\u2019re focused on people).",
        "html": "<p>The IndieWeb doesn\u2019t have \u201cusers\u201d, lol. It\u2019s all people. No VC fluff, no \u201cwe gotta hit the KPI!\u201d. People-centric and driven.</p><p>But nah, these events are moments to study and reflect on. Smugness helps no one (since again, we\u2019re focused on people).</p>"
    },
    "author": {
        "type": "card",
        "name": "",
        "url": "https://v2.jacky.wtf",
        "photo": null
    },
    "post-type": "reply",
    "refs": {
        "https://twitter.com/toyinariyo66/status/1283556875871690752": {
            "type": "entry",
            "url": "https://twitter.com/toyinariyo66/status/1283556875871690752",
            "author": {
                "type": "card",
                "name": "twitter.com",
                "url": "https://twitter.com/toyinariyo66/status/1283556875871690752",
                "photo": null
            },
            "post-type": "note"
        }
    },
    "_id": "13249652",
    "_source": "1886",
    "_is_read": true
}

Kartik Prabhu kartikprabhu.com/about#me

{
    "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
}

{
    "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
}

Marty McGuire martymcgui.re

My notes from HWC West Coast 2020-07-08

{
    "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
}

{
    "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
}

{
    "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
}

Andy Jacobs www.funwhilelost.com/profile/funwhilelost

Posting to the Fediverse from my IndieWeb site

{
    "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
}

Manton Reece www.manton.org

Sneak peek at Sunlit 3.0

{
    "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
}

Massively multiplayer open computing

{
    "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
}

Jamie Tanna www.jvt.me

{
    "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
}

{
    "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&amp;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
}

Jamie Tanna www.jvt.me

{
    "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...

Read More

{
    "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
}

Tantek Çelik tantek.com

Changes To IndieWeb Organizing, Brief Words At IndieWebCamp West

{
    "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 &amp; blacklist to allowlist &amp; 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 &amp; 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 &amp; 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
}