IndieWeb

Manton Reece www.manton.org

{
"type": "entry",
"author": {
"name": "Manton Reece",
"url": "https://www.manton.org/",
"photo": "https://aperture-proxy.p3k.io/907926e361383204bd1bc913c143c23e70ae69bb/68747470733a2f2f6d6963726f2e626c6f672f6d616e746f6e2f6176617461722e6a7067"
},
"url": "https://www.manton.org/2019/06/02/open-gardens.html",
"name": "Open gardens",
"content": {
"html": "In technology, the walled garden is a platform where one vendor controls distribution. If you want to make an iPhone app, your only choice is for Apple to approve it and sell it in the App Store. If you want to send a tweet, your only choice is to register on Twitter\u2019s platform.\n\nWalled gardens like the App Store are user-friendly and developer-hostile. They take power away from independent publishers and put it in the hands of gatekeepers. The problem is exclusivity: there is only one gate, and those stuck outside are unable to distribute the same content. You can make Android apps, but not iPhone apps. Nothing exists outside the walls that closely resembles what is inside.\n\nTwitter is also a walled garden. Like the App Store, it is a closed platform with proprietary formats and a limited API. The difference is that Twitter\u2019s garden is poorly curated and full of weeds. The walls are in such disrepair it\u2019s hard to even tell where they are.\n\n<a href=\"https://medium.com/@monteiro/merry-last-christmas-jack-dorsey-59f82c06f02b\">Mike Monteiro emphasized this frustration in a post</a> about the problems facing Twitter\u2019s leaders. He talked about meeting in person with Jack Dorsey:\n\n<blockquote>\nWe discussed Twitter\u2019s role in the world stage. And I admired his vision, but feared his approach. Jack, and to an extent Twitter\u2019s pet porg Biz Stone, have always believed that absolute free speech is the answer. They\u2019re blind to the voices silenced by hate and intimidation. The voices that need to be protected. But anyone who\u2019s ever tended a garden knows that for the good stuff to grow, you have to deal with the bad stuff. You can\u2019t let the weeds choke the vegetables.\n</blockquote>\n\nThe issue isn\u2019t that Twitter doesn\u2019t care. It\u2019s instead a design flaw in the platform. Because tweets don\u2019t exist outside of Twitter, when you\u2019re banned from Twitter, you need to start over with a new format or on a new social network. For this reason, and because their business depends on a large user base, Twitter is hesitant to throw anyone off their service. They\u2019re unwilling to tend the garden for fear of pulling too many weeds.\n\nIt doesn\u2019t matter who is guarding the walled garden\u2019s gate if increasingly no one wants to go inside. So there\u2019s a better word than \u201cgatekeeper\u201d to describe what we\u2019re really after in building a great community-focused platform. It\u2019s \u201ccurator\u201d. Someone who is responsible for maintaining the best experience for users.\n\nThe answer to a walled garden is not to create a platform without rules. It\u2019s not outsourcing decisions to algorithms, with recommended users and topics that can be gamed or lead new users astray. That\u2019s not enough for the challenges brought to us by massive, ad-based social networks, where fake news and hate can spread quickly.\n\nWe need a new approach. Not controlled only by algorithms, but also not a walled garden that limits distribution of content. We need a system that prioritizes curation while preserving the freedom to publish outside of silos, with APIs based on the <a href=\"https://indieweb.org/\">IndieWeb</a> that are open by default instead of locked down with developer registration.\n\nI think of this as an open garden. It\u2019s an open platform that also cares deeply about maintaining a healthy environment. Outside of the garden, the soil is the same and the same plants can grow, and you are free to copy flowers and trees from inside the garden and cultivate them yourself or let them grow wild. But inside is well-curated. Inside strives to be a high quality, safe environment.\n\nIn my Kickstarter video for Micro.blog, I talked about this for social networking and blogs:\n\n<blockquote>\nIf we start to separate the publishing from the social network, it unlocks something. It empowers writers to feel like they own their work, even if that\u2019s short posts. And it frees social networks to build a safe community, without worrying about censorship, because no matter what the networks do you can always post to a site with your name on it.\n</blockquote>\n\nThe fundamental problem in walled gardens like the App Store and Twitter is that they are closed. If they open up, they could in fact double-down on curation. There would be no need to loosen their quality standards because there\u2019s an easy path to publishing without review by using the open web.\n\nI first wrote about this in 2014 in the context of <a href=\"https://manton.org/2014/02/07/ending-the-app.html\">learning from Beats Music</a>. For Apple to deemphasize their algorithmic top 200 lists in the App Store they would need to focus on curation. Here\u2019s what Beats was doing:\n\n<blockquote>\nInstead, they have a bunch of people \u2014 musicians and writers who deeply care about music \u2014 curating playlists. The top 25 playlists in a genre are so buried in the app that I had to search them out just to write this blog post, because they seem to carry no more weight than any other playlist. Much more common are playlists like \u201cour top 20 of 2013\u201d. That\u2019s not a best-selling list; it\u2019s based on real people\u2019s favorites.\n</blockquote>\n\nAfter Apple acquired Beats Music, they brought some of those curation lessons over to Apple Music, and later redesigned the App Store with more featured apps and stories. There is only so much they can do, because the foundation of a walled garden is difficult to change.\n\nTwitter has likewise created an environment that ties their hands on curation, with discovery driven by trending hashtags and retweets. And for each rare time a popular account is banned for hate speech, there are still thousands of trolls who are making life miserable for users. Because there is no alternative, Twitter must allow nearly all content on their service. Because it exists apart from the open web, Twitter must give its worst users too much leeway before banning their account.\n\nThe open garden solves this problem. It\u2019s the same web inside a platform like Micro.blog as on the rest of the internet. By adopting open standards but also drawing a line across which we can apply community rules, it\u2019s possible to build features that protect users.\n\nBy encouraging the use of personal domain names, when Micro.blog does need to ask a member of the community to leave for violating our guidelines, that blogger can take their domain name and content with them, continuing to post to their own blog but blocked from interfering with the community. The curators of the platform have more freedom to block harassing posts because those problematic users can retreat to their own web site and leave everyone else in the community alone.\n\nTo summarize:\n\n<ul><li>Open gardens have curators instead of gatekeepers.</li>\n<li>Open gardens use standards so that the same formats exist inside and outside the platform.</li>\n</ul>This is only possible by embracing the open web. I believe it\u2019s an important part of <a href=\"https://manton.org/2018/09/07/the-way-out.html\">the way forward</a> for all great platforms.",
"text": "In technology, the walled garden is a platform where one vendor controls distribution. If you want to make an iPhone app, your only choice is for Apple to approve it and sell it in the App Store. If you want to send a tweet, your only choice is to register on Twitter\u2019s platform.\n\nWalled gardens like the App Store are user-friendly and developer-hostile. They take power away from independent publishers and put it in the hands of gatekeepers. The problem is exclusivity: there is only one gate, and those stuck outside are unable to distribute the same content. You can make Android apps, but not iPhone apps. Nothing exists outside the walls that closely resembles what is inside.\n\nTwitter is also a walled garden. Like the App Store, it is a closed platform with proprietary formats and a limited API. The difference is that Twitter\u2019s garden is poorly curated and full of weeds. The walls are in such disrepair it\u2019s hard to even tell where they are.\n\nMike Monteiro emphasized this frustration in a post about the problems facing Twitter\u2019s leaders. He talked about meeting in person with Jack Dorsey:\n\n\nWe discussed Twitter\u2019s role in the world stage. And I admired his vision, but feared his approach. Jack, and to an extent Twitter\u2019s pet porg Biz Stone, have always believed that absolute free speech is the answer. They\u2019re blind to the voices silenced by hate and intimidation. The voices that need to be protected. But anyone who\u2019s ever tended a garden knows that for the good stuff to grow, you have to deal with the bad stuff. You can\u2019t let the weeds choke the vegetables.\n\n\nThe issue isn\u2019t that Twitter doesn\u2019t care. It\u2019s instead a design flaw in the platform. Because tweets don\u2019t exist outside of Twitter, when you\u2019re banned from Twitter, you need to start over with a new format or on a new social network. For this reason, and because their business depends on a large user base, Twitter is hesitant to throw anyone off their service. They\u2019re unwilling to tend the garden for fear of pulling too many weeds.\n\nIt doesn\u2019t matter who is guarding the walled garden\u2019s gate if increasingly no one wants to go inside. So there\u2019s a better word than \u201cgatekeeper\u201d to describe what we\u2019re really after in building a great community-focused platform. It\u2019s \u201ccurator\u201d. Someone who is responsible for maintaining the best experience for users.\n\nThe answer to a walled garden is not to create a platform without rules. It\u2019s not outsourcing decisions to algorithms, with recommended users and topics that can be gamed or lead new users astray. That\u2019s not enough for the challenges brought to us by massive, ad-based social networks, where fake news and hate can spread quickly.\n\nWe need a new approach. Not controlled only by algorithms, but also not a walled garden that limits distribution of content. We need a system that prioritizes curation while preserving the freedom to publish outside of silos, with APIs based on the IndieWeb that are open by default instead of locked down with developer registration.\n\nI think of this as an open garden. It\u2019s an open platform that also cares deeply about maintaining a healthy environment. Outside of the garden, the soil is the same and the same plants can grow, and you are free to copy flowers and trees from inside the garden and cultivate them yourself or let them grow wild. But inside is well-curated. Inside strives to be a high quality, safe environment.\n\nIn my Kickstarter video for Micro.blog, I talked about this for social networking and blogs:\n\n\nIf we start to separate the publishing from the social network, it unlocks something. It empowers writers to feel like they own their work, even if that\u2019s short posts. And it frees social networks to build a safe community, without worrying about censorship, because no matter what the networks do you can always post to a site with your name on it.\n\n\nThe fundamental problem in walled gardens like the App Store and Twitter is that they are closed. If they open up, they could in fact double-down on curation. There would be no need to loosen their quality standards because there\u2019s an easy path to publishing without review by using the open web.\n\nI first wrote about this in 2014 in the context of learning from Beats Music. For Apple to deemphasize their algorithmic top 200 lists in the App Store they would need to focus on curation. Here\u2019s what Beats was doing:\n\n\nInstead, they have a bunch of people \u2014 musicians and writers who deeply care about music \u2014 curating playlists. The top 25 playlists in a genre are so buried in the app that I had to search them out just to write this blog post, because they seem to carry no more weight than any other playlist. Much more common are playlists like \u201cour top 20 of 2013\u201d. That\u2019s not a best-selling list; it\u2019s based on real people\u2019s favorites.\n\n\nAfter Apple acquired Beats Music, they brought some of those curation lessons over to Apple Music, and later redesigned the App Store with more featured apps and stories. There is only so much they can do, because the foundation of a walled garden is difficult to change.\n\nTwitter has likewise created an environment that ties their hands on curation, with discovery driven by trending hashtags and retweets. And for each rare time a popular account is banned for hate speech, there are still thousands of trolls who are making life miserable for users. Because there is no alternative, Twitter must allow nearly all content on their service. Because it exists apart from the open web, Twitter must give its worst users too much leeway before banning their account.\n\nThe open garden solves this problem. It\u2019s the same web inside a platform like Micro.blog as on the rest of the internet. By adopting open standards but also drawing a line across which we can apply community rules, it\u2019s possible to build features that protect users.\n\nBy encouraging the use of personal domain names, when Micro.blog does need to ask a member of the community to leave for violating our guidelines, that blogger can take their domain name and content with them, continuing to post to their own blog but blocked from interfering with the community. The curators of the platform have more freedom to block harassing posts because those problematic users can retreat to their own web site and leave everyone else in the community alone.\n\nTo summarize:\n\nOpen gardens have curators instead of gatekeepers.\nOpen gardens use standards so that the same formats exist inside and outside the platform.\nThis is only possible by embracing the open web. I believe it\u2019s an important part of the way forward for all great platforms."
},
"published": "2019-06-02T15:48:32-07:00",
"post-type": "note",
"_id": "3766260",
"_source": "12",
"_is_read": true
}

As I've embraced indie post types, such as reposts, I've noticed that actually I've been using them wrong. Looking at https://indieweb.org/bookmark#Repost it appears I've been conflating a "retweet" on Twitter with a "repost", thinking they were the same. Alas, they are not, and it makes more sense to be a bookmark. I've since updated the posts using the wrong type and will get things right next time!

#indieweb

June 2, 2019 2:21pm +01:00

{
    "type": "entry",
    "published": "2019-06-02 14:21:04 +0100 BST",
    "url": "https://www.jvt.me/notes/d6ee82bb-479a-4f98-bc7c-01ad38e286bd/",
    "category": [
        "indieweb"
    ],
    "content": {
        "text": "As I've embraced indie post types, such as reposts, I've noticed that actually I've been using them wrong. Looking at https://indieweb.org/bookmark#Repost it appears I've been conflating a \"retweet\" on Twitter with a \"repost\", thinking they were the same. Alas, they are not, and it makes more sense to be a bookmark. I've since updated the posts using the wrong type and will get things right next time!"
    },
    "post-type": "note",
    "_id": "3759382",
    "_source": "2169",
    "_is_read": true
}

Neil Mather doubleloop.net

Third and fourth industrial revolutions for liberatory ends

June 1, 2019 6:11pm +00:00

{
    "type": "entry",
    "author": {
        "name": "Neil Mather",
        "url": "https://doubleloop.net/",
        "photo": null
    },
    "url": "https://doubleloop.net/2019/06/01/third-and-fourth-industrial-revolutions-for-liberatory-ends/",
    "published": "2019-06-01T18:11:00+00:00",
    "content": {
        "html": "Read <a href=\"http://www.socialisteconomist.com/2018/10/the-fourth-industrial-revolution-wont.html\">The Fourth Industrial Revolution Won\u2019t Trickle Down, Under Capitalism</a> by Aabid Firdausi <em>(Socialist Economist)</em>\n<blockquote>Most economists suffer from misplaced optimism about the oncoming Fourth Industrial Revolution. Some reskilling here and there would suffice to spread its benefits to all workers. They ignore how capitalism invents and employs technology for profits, not people.</blockquote>\n\n<p>I first came across the idea of the third and fourth industrial revolutions (3IR and 4IR) in <a href=\"https://cooperationjackson.org/announcementsblog/2017/9/21/new-book-jackson-rising-the-struggle-for-economic-democracy-and-black-self-determination-in-jackson-mississippi\">Jackson Rising</a>, where the technologies of these present and upcoming revolutions were seen as potentially liberatory, if used in the right way.  The possibilities are exciting, with (amongst other things) fablabs enabling manufacture to move local, and an open web allowing information resources to be shared globally.</p>\n<p>Unsurprisingly though, there\u2019s a very capitalist potential outcome of 3IR and 4IR too.</p>\n<p>Like the previous revolutions, it *could* be liberatory, or it *could* as easily reinforce existing inequalities. The historical record isn\u2019t too great in terms of global equality and liberation.</p>\n<p>This article makes the argument for ensuring these revolutions are for liberatory ends.</p>\n<blockquote><p>\u201chow technology is put to use fundamentally remains a social choice and a \u201cglobal network of resistance\u201d to the way the emerging technologies are utilised \u201cis both necessary and feasible.\u201d</p></blockquote>\n<p>To me that\u2019s a given really \u2013 shame the article doesn\u2019t go into much detail on actual strategy. (Which Cooperation Jackson do in great detail.)</p>\n<p>There\u2019s much more to 3/4IR, but selectively quoting from the connectivity and communication parts, as they piqued my IndieWeb interest:</p>\n<blockquote><p>\u201cWhile social networking provides relatively open spaces for public expression, the immense wealth that is generated by the techno-capitalists shows us that even public spaces can become a profitable business model.\u201d</p>\n<p>\u201cnecessitates the need for resistance against the tendencies of capitalism in general that has historically encroached upon public spaces for profit.\u201d</p></blockquote>\n<p>Here\u2019s to being part of a global network of resistance.</p>",
        "text": "Read The Fourth Industrial Revolution Won\u2019t Trickle Down, Under Capitalism by Aabid Firdausi (Socialist Economist)\nMost economists suffer from misplaced optimism about the oncoming Fourth Industrial Revolution. Some reskilling here and there would suffice to spread its benefits to all workers. They ignore how capitalism invents and employs technology for profits, not people.\n\nI first came across the idea of the third and fourth industrial revolutions (3IR and 4IR) in Jackson Rising, where the technologies of these present and upcoming revolutions were seen as potentially liberatory, if used in the right way.  The possibilities are exciting, with (amongst other things) fablabs enabling manufacture to move local, and an open web allowing information resources to be shared globally.\nUnsurprisingly though, there\u2019s a very capitalist potential outcome of 3IR and 4IR too.\nLike the previous revolutions, it *could* be liberatory, or it *could* as easily reinforce existing inequalities. The historical record isn\u2019t too great in terms of global equality and liberation.\nThis article makes the argument for ensuring these revolutions are for liberatory ends.\n\u201chow technology is put to use fundamentally remains a social choice and a \u201cglobal network of resistance\u201d to the way the emerging technologies are utilised \u201cis both necessary and feasible.\u201d\nTo me that\u2019s a given really \u2013 shame the article doesn\u2019t go into much detail on actual strategy. (Which Cooperation Jackson do in great detail.)\nThere\u2019s much more to 3/4IR, but selectively quoting from the connectivity and communication parts, as they piqued my IndieWeb interest:\n\u201cWhile social networking provides relatively open spaces for public expression, the immense wealth that is generated by the techno-capitalists shows us that even public spaces can become a profitable business model.\u201d\n\u201cnecessitates the need for resistance against the tendencies of capitalism in general that has historically encroached upon public spaces for profit.\u201d\nHere\u2019s to being part of a global network of resistance."
    },
    "name": "Third and fourth industrial revolutions for liberatory ends",
    "post-type": "article",
    "_id": "3748636",
    "_source": "1895",
    "_is_read": true
}

Sebastiaan Andeweg seblog.nl

Private posts: the move of the checkins

#indieweb #privateposts

June 1, 2019 10:27am +00:00

{
    "type": "entry",
    "published": "2019-06-01T10:27:14+0000",
    "url": "https://seblog.nl/2019/06/01/1/private-posts-move-of-checkins",
    "category": [
        "indieweb",
        "privateposts"
    ],
    "syndication": [
        "https://news.indieweb.org/en/seblog.nl/2019/06/01/1/private-posts-move-of-checkins"
    ],
    "name": "Private posts: the move of the checkins",
    "content": {
        "text": "Can I tell you a secret about writing software? We all just wing it. We all try to write the code as beautiful, readable and maintainable as we can, but in the end of the day, the business wants our projects to be done yesterday, not in three weeks. So despite best intentions, corners are cut and things that should not know about other things are calling each other. Some call this spaghetti.\nI will also not lie to you: the codebase of this here weblog, at least in it\u2019s current form, is not free of spaghetti or mess. Corners were cut in a time where I did not know there even were corners to begin with. I improved the code many times, all in different directions, because you\u2019re always learning better ways to do it (and I still do). Some call this a legacy codebase.\nBecause of the shape the code is in, I did not want to add large features anymore. I wanted to rewrite it, of all of it. But as Martin Fowler said somewhere: the only thing you will get from a Big Bang Rewrite, is a big bang. It\u2019s better to incrementally improve your application, so I tried. I tried to come up with clever strategies to do so, to keep parts of my site running on old code while the rest was fresh and new. In all those strategies, my blog entries would be last, because they are with 9000+ and need to be moved all at once.\nIn order to support private posts, however, it is precisely the code that serves my blog entries that needs work. This means that, while I have private posts very high on my wishlist, I postponed it to after The Rewrite. And I kept attempting to get there, but since it\u2019s a big project for sparetime hours, private posts where impossible for a long time.\nThe year of the private posts?\nRecently, the call for private posts became louder again. Aaron Parecki is trying to get a group of people together to exchange private posts between Readers. I would like to be one of them. In some regard I\u2019m already \u2018ahead\u2019 of the game, because I do support private posts on my site already since 2017. The thing is: you need to know the URL of the post to actually read it.\nI\u2019ve attended both IndieWebCamp D\u00fcsseldorf and Utrecht last month. At the first one, we had a very good session about the UI side of private posts. The blogpost I wrote about it unfortunately stayed in draft. The summary: I used to denote private posts by adding the word \u2018priv\u00e9\u2019 in bold below the post, next to the timestamp. Since the hackday I now show a sort-of header with a lock icon, and a text telling you that only you can see the post, or you and others, if that\u2019s the case.\nA big takeaway from D\u00fcsseldorf was that I don\u2019t need to do it all at once. To me, the first step to private posts is letting people login to your site. This can be done with IndieAuth, or by using IndieAuth.com (which will move to IndieLogin.com at some point). The second step is to mark a post as private in your storage, and only serve it to people who are logged in. The third step is to add a list of people who can see the post, and only show it to those people. This is the place where I was at.\nThe fourth step should then be: show those private-for-all posts in your feed, for anyone logged in. The fifth step is to also show those private-for-you posts in their feed, which is tricker but not impossible. The sixth step would then finally be letting the user\u2019s Reader log into your site on their behalf. I feel like I have seen that sixth step as the next step for way to long. By making it the sixth step, it is now only about authentication / authorization, not about what to show to who (because you got that already).\nA bonus step could then be to add groups, so you can more easily share posts with certain groups of people. I have wrote about the queries involved before. This is a bonus step, because it\u2019s making your life easier as maintainer of the site, but it is invisible to the outside world. (I would prefer not to share to people which groups they are in, nor the names of the groups the post was shared with. Those groups are purely for my own convenience.)\nOf course, you can take different steps, in a different order. But to me, this is the path to where I want private posts to be.\nChanneling my inner Business Stakeholder\nAfter breaking it down into these nice steps, I\u2019m still left with a legacy codebase. My biggest takeaway from Utrecht, was that I should be more pragmatic about it. The code quality of my site is only visible to me, what matters is the functionality. And I want this private post functionality.\nI still did some refactoring that could be useful to future versions of this site, but I won\u2019t bore you with that. I decided that it was not worth the wait, and that private post feeds should be part of this version of my blog.\nLast Tuesday, there was yet another chat about private posts and how to do it. There was a question about the progress, whether or not something was decided at the recent EU-IWCs. But there is no decision, there is no permission, there is no plan to be carried out. There is just us, wanting to use this feature that does not exist yet. The only way to actually get there, is to build it ourselves and see what works and what doesn\u2019t.\nSo I hacked it together, in my existing code. I believe I broke things, but I have fixed some. If you see more, please tell me. But I got the functionality, and that is what counts.\nMarking all my checkins private\nThere is this app called Swarm. Some members of the IndieWeb Community use it, because it\u2019s fun. I would call it the Guilty Pleasure of the IndieWeb, the last Silo. I use it too, especially when I\u2019m in a city for IndieWebCamp. It\u2019s almost impossible not to use it then: the people I\u2019m with are checking me in anyway.\nI like having a log of every bar, restaurant, shop I have been, and I see value in sharing it. But it also creeps my out to have all that information about me on a public place like this. Even on Swarm, checkins are only shared with friends (and advertisers), not the public. It seems to me that my checkins, then, are the perfect place to start with private posts.\nSo that is what I made: I marked all my checkins as private-for-all. This means they are still public at the moment, but you need to log in, which currently rules out bots and practically every visior. But chances are you know how to use IndieAuth, or have a Twitter account. You can then login to my site by clicking the link in the upper right corner. After you logged in, you will see all my checkins appear in the main feed, each of them with a message that it\u2019s only visible to logged in users.\nIn addition, there is a new page: /private. The link will appear in the menu when you are logged in. This page shows you all the private posts that are specificly shared with you. Some of you might actually see a post there.\nSteps\nOne part of me says \u201cbut is private-for-all private enough for my checkins?\u201d Another part of me says \u201cit\u2019s nice that you support the feature, but no-one is going to log into your site.\u201d Yet another part of me says \u201cwhat is it worth, writing more code in this codebase you want to get rid of anyway?\u201d But it\u2019s fine. I made a step, that\u2019s what\u2019s important. From here, I can look into AutoAuth, and maybe, maybe, we can get some private feed fetching to work before IndieWebSummit.\nBut in the worst case: I own my checkins, and I control who sees them. And that\u2019s a very nice place to be in.",
        "html": "<p>Can I tell you a secret about writing software? We all just wing it. We all try to write the code as beautiful, readable and maintainable as we can, but in the end of the day, the business wants our projects to be done yesterday, not in three weeks. So despite best intentions, corners are cut and things that should not know about other things are calling each other. Some call this spaghetti.</p>\n<p>I will also not lie to you: the codebase of this here weblog, at least in it\u2019s current form, is not free of spaghetti or mess. Corners were cut in a time where I did not know there even were corners to begin with. I improved the code many times, all in different directions, because you\u2019re always learning better ways to do it (and I still do). Some call this a legacy codebase.</p>\n<p>Because of the shape the code is in, I did not want to add large features anymore. I wanted to rewrite it, of all of it. But as <a href=\"https://martinfowler.com\">Martin Fowler</a> said somewhere: the only thing you will get from a Big Bang Rewrite, is a big bang. It\u2019s better to incrementally improve your application, so I tried. I tried to come up with clever strategies to do so, to keep parts of my site running on old code while the rest was fresh and new. In all those strategies, my blog entries would be last, because they are with 9000+ and need to be moved all at once.</p>\n<p>In order to support private posts, however, it is precisely the code that serves my blog entries that needs work. This means that, while I have private posts very high on my wishlist, I postponed it to after The Rewrite. And I kept attempting to get there, but since it\u2019s a big project for sparetime hours, private posts where impossible for a long time.</p>\n<h2>The year of the private posts?</h2>\n<p>Recently, the call for private posts became louder again. <a href=\"https://aaronparecki.com\">Aaron Parecki</a> is trying to get a group of people together to exchange private posts between <a href=\"https://indieweb.org/reader\">Readers</a>. I would like to be one of them. In some regard I\u2019m already \u2018ahead\u2019 of the game, because I do support private posts on my site already <a href=\"https://seblog.nl/2017/02/11/3/day-27-private-posts\">since 2017</a>. The thing is: you need to know the URL of the post to actually read it.</p>\n<p>I\u2019ve attended both <a href=\"https://indieweb.org/2019/D%C3%BCsseldorf\">IndieWebCamp D\u00fcsseldorf</a> and <a href=\"https://indieweb.org/2019/Utrecht\">Utrecht</a> last month. At the first one, we had a very good session about the UI side of private posts. The blogpost I wrote about it unfortunately stayed in draft. The summary: I used to denote private posts by adding the word \u2018priv\u00e9\u2019 in bold below the post, next to the timestamp. Since the hackday I now show a sort-of header with a lock icon, and a text telling you that only you can see the post, or you and others, if that\u2019s the case.</p>\n<p>A big takeaway from D\u00fcsseldorf was that I don\u2019t need to do it all at once. To me, the first step to private posts is letting people login to your site. This can be done with IndieAuth, or by using <a href=\"https://indieauth.com\">IndieAuth.com</a> (which will move to <a href=\"https://indielogin.com\">IndieLogin.com</a> at some point). The second step is to mark a post as private in your storage, and only serve it to people who are logged in. The third step is to add a list of people who can see the post, and only show it to those people. This is the place where I was at.</p>\n<p>The fourth step should then be: show those private-for-all posts in your feed, for anyone logged in. The fifth step is to also show those private-for-you posts in their feed, which is tricker but not impossible. The sixth step would then finally be letting the user\u2019s Reader log into your site on their behalf. I feel like I have seen that sixth step as the next step for way to long. By making it the sixth step, it is now only about authentication / authorization, not about what to show to who (because you got that already).</p>\n<p>A bonus step could then be to add groups, so you can more easily share posts with certain groups of people. I have wrote about <a href=\"https://seblog.nl/2018/11/06/3/exploring-queries-for-private-feeds\">the queries involved</a> before. This is a bonus step, because it\u2019s making your life easier as maintainer of the site, but it is invisible to the outside world. (I would prefer not to share to people which groups they are in, nor the names of the groups the post was shared with. Those groups are purely for my own convenience.)</p>\n<p>Of course, you can take different steps, in a different order. But to me, this is the path to where I want private posts to be.</p>\n<h2>Channeling my inner Business Stakeholder</h2>\n<p>After breaking it down into these nice steps, I\u2019m still left with a legacy codebase. My biggest takeaway from Utrecht, was that I should be more pragmatic about it. The code quality of my site is only visible to me, what matters is the functionality. And I want this private post functionality.</p>\n<p>I still did some refactoring that could be useful to future versions of this site, but I won\u2019t bore you with that. I decided that it was not worth the wait, and that private post feeds should be part of this version of my blog.</p>\n<p>Last Tuesday, there was yet another chat about private posts and how to do it. There was a question about the progress, whether or not something was decided at the recent EU-IWCs. But there is no decision, there is no permission, there is no plan to be carried out. There is just us, wanting to use this feature that does not exist yet. The only way to actually get there, is to build it ourselves and see what works and what doesn\u2019t.</p>\n<p>So I hacked it together, in my existing code. I believe I broke things, but I have fixed some. If you see more, please tell me. But I got the functionality, and that is what counts.</p>\n<h2>Marking all my checkins private</h2>\n<p>There is this app called <a href=\"https://swarmapp.com\">Swarm</a>. Some members of the IndieWeb Community use it, because it\u2019s fun. I would call it the Guilty Pleasure of the IndieWeb, the last Silo. I use it too, especially when I\u2019m in a city for IndieWebCamp. It\u2019s almost impossible not to use it then: the people I\u2019m with are checking me in anyway.</p>\n<p>I like having a log of every bar, restaurant, shop I have been, and I see value in sharing it. But it also creeps my out to have all that information about me on a public place like this. Even on Swarm, checkins are only shared with friends (and advertisers), not the public. It seems to me that my checkins, then, are the perfect place to start with private posts.</p>\n<p>So that is what I made: I marked all my checkins as private-for-all. This means they are still public at the moment, but you need to log in, which currently rules out bots and practically every visior. But chances are you know how to use IndieAuth, or have a Twitter account. You can then login to my site by clicking the link in the upper right corner. After you logged in, you will see all my checkins appear in the main feed, each of them with a message that it\u2019s only visible to logged in users.</p>\n<p>In addition, there is a new page: <a href=\"https://seblog.nl/private\">/private</a>. The link will appear in the menu when you are logged in. This page shows you all the private posts that are specificly shared with you. Some of you might actually see a post there.</p>\n<h2>Steps</h2>\n<p>One part of me says \u201cbut is private-for-all private enough for my checkins?\u201d Another part of me says \u201cit\u2019s nice that you support the feature, but no-one is going to log into your site.\u201d Yet another part of me says \u201cwhat is it worth, writing more code in this codebase you want to get rid of anyway?\u201d But it\u2019s fine. I made a step, that\u2019s what\u2019s important. From here, I can look into <a href=\"https://indieweb.org/AutoAuth\">AutoAuth</a>, and maybe, maybe, we can get some private feed fetching to work before <a href=\"https://2019.indieweb.org/summit\">IndieWebSummit</a>.</p>\n<p>But in the worst case: I own my checkins, and I control who sees them. And that\u2019s a very nice place to be in.</p>"
    },
    "author": {
        "type": "card",
        "name": "Sebastiaan Andeweg",
        "url": "https://seblog.nl/",
        "photo": "https://aperture-proxy.p3k.io/10e8aeca31d1cd146999fcacc07a8eb9ad47c813/68747470733a2f2f7365626c6f672e6e6c2f70686f746f2e6a7067"
    },
    "post-type": "article",
    "_id": "3743495",
    "_source": "1366",
    "_is_read": true
}

twitter.com/TrevorFSmith/status/1000940615431933954

Tantek Çelik tantek.com

@TrevorFSmith 1 year later notification from your like!
@Timoni #IndieWeb folks are building & using their sites as memexes, with unique personal features.
Twitter is not anyone’s memex but theirs; we POSSE copies there to invite others to explore ours.

#IndieWeb

May 31, 2019 11:18pm -07:00

{
    "type": "entry",
    "published": "2019-05-31 23:18-0700",
    "url": "http://tantek.com/2019/151/t4/",
    "category": [
        "IndieWeb"
    ],
    "in-reply-to": [
        "https://twitter.com/TrevorFSmith/status/1000940615431933954"
    ],
    "content": {
        "text": "@TrevorFSmith 1 year later notification from your like!\n@Timoni #IndieWeb folks are building & using their sites as memexes, with unique personal features.\nTwitter is not anyone\u2019s memex but theirs; we POSSE copies there to invite others to explore ours.",
        "html": "<a class=\"h-cassis-username\" href=\"https://twitter.com/TrevorFSmith\">@TrevorFSmith</a> 1 year later notification from your like!<br /><a class=\"h-cassis-username\" href=\"https://twitter.com/Timoni\">@Timoni</a> #<span class=\"p-category\">IndieWeb</span> folks are building &amp; using their sites as memexes, with unique personal features.<br />Twitter is not anyone\u2019s memex but theirs; we POSSE copies there to invite others to explore ours."
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "reply",
    "refs": {
        "https://twitter.com/TrevorFSmith/status/1000940615431933954": {
            "type": "entry",
            "url": "https://twitter.com/TrevorFSmith/status/1000940615431933954",
            "name": "@TrevorFSmith\u2019s tweet",
            "post-type": "article"
        }
    },
    "_id": "3741350",
    "_source": "1",
    "_is_read": true
}

Neil Mather doubleloop.net

I feel like the IndieWeb is a great example of commons-based peer production, as per Benkler’s definition:

radically decentralized, collaborative, and nonproprietary; based on sharing resources and outputs among widely distributed, loosely connected individuals who cooperate with each other without relying on either market signals or managerial commands.

May 31, 2019 9:14pm +00:00

{
    "type": "entry",
    "author": {
        "name": "Neil Mather",
        "url": "https://doubleloop.net/",
        "photo": null
    },
    "url": "https://doubleloop.net/2019/05/31/5646/",
    "published": "2019-05-31T21:14:47+00:00",
    "content": {
        "html": "<p>I feel like the IndieWeb is a great example of <a href=\"https://en.wikipedia.org/wiki/Commons-based_peer_production\">commons-based peer production</a>, as per <a href=\"http://yupnet.org/benkler/archives/12\">Benkler\u2019s definition</a>:</p>\n<blockquote><p>radically decentralized, collaborative, and nonproprietary; based on sharing resources and outputs among widely distributed, loosely connected individuals who cooperate with each other without relying on either market signals or managerial commands.</p></blockquote>",
        "text": "I feel like the IndieWeb is a great example of commons-based peer production, as per Benkler\u2019s definition:\nradically decentralized, collaborative, and nonproprietary; based on sharing resources and outputs among widely distributed, loosely connected individuals who cooperate with each other without relying on either market signals or managerial commands."
    },
    "post-type": "note",
    "_id": "3737770",
    "_source": "1895",
    "_is_read": true
}

www.stackbit.com/medium/

Jeremy Keith adactio.com

Medium | Stackbit

This is very handy! Export your data from Ev’s blog and then import it into a static site generator of your choice.

You may have noticed the recent movement of people looking to get off Medium. Most of us are motivated by a desire to own our content, have data portability and get more control over how/where our content is displayed and monetized. Most importantly many of us consider our blog/site to be a core part of our online identity and while Medium offers a fantastic writing experience it sacrifices other important values. Luckily there’s a modern approach to running your blog which aligns with these ideals, its called the JAMstack and its all around us.

#medium #export #import #data #transfer #ownership #indieweb #static #ssg #netlify #stackbit #jamstack

May 31, 2019 9:46pm +00:00

{
    "type": "entry",
    "published": "2019-05-31T21:46:16Z",
    "url": "https://adactio.com/links/15263",
    "category": [
        "medium",
        "export",
        "import",
        "data",
        "transfer",
        "ownership",
        "indieweb",
        "static",
        "ssg",
        "netlify",
        "stackbit",
        "jamstack"
    ],
    "bookmark-of": [
        "https://www.stackbit.com/medium/"
    ],
    "content": {
        "text": "Medium | Stackbit\n\n\n\nThis is very handy! Export your data from Ev\u2019s blog and then import it into a static site generator of your choice.\n\n\n  You may have noticed the recent movement of people looking to get off Medium. Most of us are motivated by a desire to own our content, have data portability and get more control over how/where our content is displayed and monetized. Most importantly many of us consider our blog/site to be a core part of our online identity and while Medium offers a fantastic writing experience it sacrifices other important values. Luckily there\u2019s a modern approach to running your blog which aligns with these ideals, its called the JAMstack and its all around us.",
        "html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://www.stackbit.com/medium/\">\nMedium | Stackbit\n</a>\n</h3>\n\n<p>This is very handy! Export your data from <a href=\"https://medium.com/\">Ev\u2019s blog</a> and then import it into a static site generator of your choice.</p>\n\n<blockquote>\n  <p>You may have noticed the recent movement of people looking to get off Medium. Most of us are motivated by a desire to own our content, have data portability and get more control over how/where our content is displayed and monetized. Most importantly many of us consider our blog/site to be a core part of our online identity and while Medium offers a fantastic writing experience it sacrifices other important values. Luckily there\u2019s a modern approach to running your blog which aligns with these ideals, its called the JAMstack and its all around us.</p>\n</blockquote>"
    },
    "author": {
        "type": "card",
        "name": "Jeremy Keith",
        "url": "https://adactio.com/",
        "photo": "https://aperture-proxy.p3k.io/bbbacdf0a064621004f2ce9026a1202a5f3433e0/68747470733a2f2f6164616374696f2e636f6d2f696d616765732f70686f746f2d3135302e6a7067"
    },
    "post-type": "bookmark",
    "_id": "3736276",
    "_source": "2",
    "_is_read": true
}

chris www.stillbreathing.co.uk

Designing in the open

May 30, 2019 6:38pm +00:00

{
    "type": "entry",
    "author": {
        "name": "chris",
        "url": "https://www.stillbreathing.co.uk/",
        "photo": null
    },
    "url": "https://www.stillbreathing.co.uk/2019/05/30/designing-in-the-open",
    "published": "2019-05-30T18:38:02+00:00",
    "content": {
        "html": "<p>It\u2019s been a while since I last redesigned (or should I say, <a href=\"https://alistapart.com/article/redesignrealign/\">realigned</a>) this site. Six years, in fact. My regular visitor, if they are still regular, will have noticed that this site has been somewhat broked for a week or so.</p>\n\n\n\n<p>I\u2019m not sure what I did, but I clearly mangled something. Anyway, it\u2019s an excuse to realign.</p>\n\n\n\n<p>This time I have some simple requirements for myself:</p>\n\n\n\n<ol><li>Mobile first. The reality is that most browsing is done on a mobile device of some kind, so I want to primarily cater to those constraints. That means mobile-first CSS, Service Workers, small images only where necessary etc etc.</li><li>Performance second. Closely related to the mobile thing, good performance is a must. I\u2019m aiming for sub-second render times. I also want to use no JavaScript. This is a content site, why would I need it?</li><li>More emphasis on the IndieWeb. I\u2019ve started doing this, by pulling in my tweets. But I want to go much further down that road.</li></ol><p>And I\u2019m doing all this in the open, live on the site. I may fail completely, in which case it will be a public humiliation. But maybe it will force me to get on with it!</p>",
        "text": "It\u2019s been a while since I last redesigned (or should I say, realigned) this site. Six years, in fact. My regular visitor, if they are still regular, will have noticed that this site has been somewhat broked for a week or so.\n\n\n\nI\u2019m not sure what I did, but I clearly mangled something. Anyway, it\u2019s an excuse to realign.\n\n\n\nThis time I have some simple requirements for myself:\n\n\n\nMobile first. The reality is that most browsing is done on a mobile device of some kind, so I want to primarily cater to those constraints. That means mobile-first CSS, Service Workers, small images only where necessary etc etc.Performance second. Closely related to the mobile thing, good performance is a must. I\u2019m aiming for sub-second render times. I also want to use no JavaScript. This is a content site, why would I need it?More emphasis on the IndieWeb. I\u2019ve started doing this, by pulling in my tweets. But I want to go much further down that road.And I\u2019m doing all this in the open, live on the site. I may fail completely, in which case it will be a public humiliation. But maybe it will force me to get on with it!"
    },
    "name": "Designing in the open",
    "post-type": "article",
    "_id": "3721169",
    "_source": "235",
    "_is_read": true
}

Jeremy Keith adactio.com

Indie web events in Brighton

#indieweb #homebrew #website #club #brighton #indiewebcamp #events

May 30, 2019 5:35pm +00:00

{
    "type": "entry",
    "published": "2019-05-30T17:35:29Z",
    "url": "https://adactio.com/journal/15254",
    "category": [
        "indieweb",
        "homebrew",
        "website",
        "club",
        "brighton",
        "indiewebcamp",
        "events"
    ],
    "syndication": [
        "https://medium.com/@adactio/ba72ab56bca2"
    ],
    "name": "Indie web events in Brighton",
    "content": {
        "text": "Homebrew Website Club is a regular gathering of people getting together to tinker on their own websites. It\u2019s a play on the original Homebrew Computer Club from the \u201970s. It shares a similar spirit of sharing and collaboration.\n\nHomebrew Website Clubs happen at various locations: London, San Francisco, Portland, Nuremberg, and more. Usually there on every second Wednesday.\n\nI started running Homebrew Website Club Brighton a while back. I tried the \u201cevery second Wednesday\u201d thing, but it was tricky to make that work. People found it hard to keep track of which Wednesdays were Homebrew days and which weren\u2019t. And if you missed one, then it would potentially be weeks between attending.\n\nSo I\u2019ve made it a weekly gathering. On Thursdays. That\u2019s mostly because Thursdays work for me: that\u2019s one of the evenings when Jessica has her ballet class, so it\u2019s the perfect time for me to spend a while in the company of fellow website owners.\n\nIf you\u2019re in Brighton and you have your own website (or you want to have your own website), you should come along. It\u2019s every Thursday from 6pm to 7:30pm \u2018round at the Clearleft studio on 68 Middle Street. Add it to your calendar.\n\nThere might be a Thursday when I\u2019m not around, but it\u2019s highly likely that Homebrew Website Club Brighton will happen anyway because either Trys, Benjamin or Cassie will be here.\n\n(I\u2019m at Homebrew Website Club Brighton right now, writing this. Remy is here too, working on some very cool webmention stuff.)\n\nThere\u2019s something else you should add to your calendar. We\u2019re going to have an Indie Web Camp in Brighton on October 19th and 20th. I realise that\u2019s quite a way off, but I\u2019m giving you plenty of advance warning so you can block out that weekend (and plan travel if you\u2019re coming from outside Brighton).\n\nIf you\u2019ve never been to an Indie Web Camp before, you should definitely come! It\u2019s indescribably fun and inspiring. The first day\u2014Saturday\u2014is a BarCamp-style day of discussions to really get the ideas flowing. Then the second day\u2014Sunday\u2014is all about designing, building, and making. The whole thing wraps up with demos.\n\nIt\u2019s been a while since we\u2019ve had an Indie Web Camp in Brighton. You can catch up on the Brighton Indie Web Camps we had in 2014, 2015, and 2016. Since then I\u2019ve been to Indie Web Camps in Berlin, Nuremberg, and D\u00fcsseldorf, but it\u2019s going to be really nice to bring it back home.\n\n\n\n\n\nThe event will be free to attend, but I\u2019ll set up an official ticket page on Ti.to to keep track of who\u2019s coming. I\u2019ll let you know when that\u2019s up and ready. In the meantime, you can register your interest in attending on the 2019 Indie Webcamp Brighton page on the Indie Web wiki.",
        "html": "<p><a href=\"https://indieweb.org/Homebrew_Website_Club\">Homebrew Website Club</a> is a regular gathering of people getting together to tinker on their own websites. It\u2019s a play on the original <a href=\"https://en.wikipedia.org/wiki/Homebrew_Computer_Club\">Homebrew Computer Club</a> from the \u201970s. It shares a similar spirit of sharing and collaboration.</p>\n\n<p>Homebrew Website Clubs happen at various locations: London, San Francisco, Portland, Nuremberg, and more. Usually there on every second Wednesday.</p>\n\n<p>I started running <a href=\"https://indieweb.org/2019/Brighton\">Homebrew Website Club Brighton</a> a while back. I tried the \u201cevery second Wednesday\u201d thing, but it was tricky to make that work. People found it hard to keep track of which Wednesdays were Homebrew days and which weren\u2019t. And if you missed one, then it would potentially be weeks between attending.</p>\n\n<p>So I\u2019ve made it a weekly gathering. On Thursdays. That\u2019s mostly because Thursdays work for me: that\u2019s one of the evenings when <a href=\"https://wordridden.com\">Jessica</a> has her ballet class, so it\u2019s the perfect time for me to spend a while in the company of fellow website owners.</p>\n\n<p>If you\u2019re in Brighton and you have your own website (or you want to have your own website), you should come along. It\u2019s every Thursday from 6pm to 7:30pm \u2018round at the <a href=\"https://clearleft.com\">Clearleft</a> studio on <a href=\"http://68middle.st/\">68 Middle Street</a>. Add it to your calendar.</p>\n\n<p>There might be a Thursday when I\u2019m not around, but it\u2019s highly likely that Homebrew Website Club Brighton will happen anyway because either <a href=\"https://www.trysmudford.com/\">Trys</a>, <a href=\"https://benjamin.parry.is/\">Benjamin</a> or <a href=\"https://clearleft.com/team/cassie-evans\">Cassie</a> will be here.</p>\n\n<p>(I\u2019m at Homebrew Website Club Brighton right now, writing this. <a href=\"https://remysharp.com/\">Remy</a> is here too, working on some very cool webmention stuff.)</p>\n\n<p>There\u2019s something else you should add to your calendar. We\u2019re going to have an <a href=\"https://indieweb.org/2019/Brighton\">Indie Web Camp in Brighton</a> on October 19th and 20th. I realise that\u2019s quite a way off, but I\u2019m giving you plenty of advance warning so you can block out that weekend (and plan travel if you\u2019re coming from outside Brighton).</p>\n\n<p>If you\u2019ve never been to an Indie Web Camp before, you should definitely come! It\u2019s indescribably fun and inspiring. The first day\u2014Saturday\u2014is a BarCamp-style day of discussions to really get the ideas flowing. Then the second day\u2014Sunday\u2014is all about designing, building, and making. The whole thing wraps up with demos.</p>\n\n<p>It\u2019s been a while since we\u2019ve had an Indie Web Camp in Brighton. You can catch up on the Brighton Indie Web Camps we had in <a href=\"https://adactio.com/journal/7434\">2014</a>, <a href=\"https://adactio.com/journal/9261\">2015</a>, and <a href=\"https://adactio.com/journal/11246\">2016</a>. Since then I\u2019ve been to Indie Web Camps in Berlin, Nuremberg, and D\u00fcsseldorf, but it\u2019s going to be really nice to bring it back home.</p>\n\n<p><a href=\"https://adactio.com/journal/7434\"><img src=\"https://aperture-proxy.p3k.io/de7f8a5a8096034444d1ab362f817525a0e7eadc/68747470733a2f2f696e64696577656263616d702e636f6d2f696d616765732f7468756d622f322f32352f4957435f554b5f323031345f67726f75705f70686f746f2e6a70672f37323070782d4957435f554b5f323031345f67726f75705f70686f746f2e6a7067\" alt=\"Indie Web Camp UK attendees\" /></a>\n<a href=\"https://adactio.com/journal/9261\"><img src=\"https://aperture-proxy.p3k.io/076606547305c0d6ac4554754c3a30cb8e69446b/68747470733a2f2f6661726d312e737461746963666c69636b722e636f6d2f3238312f31383939323036363136335f383039643931363865395f7a5f642e6a7067\" alt=\"Indie Web Camp Brighton group photo\" /></a>\n<a href=\"https://adactio.com/journal/11246\"><img src=\"https://aperture-proxy.p3k.io/214599f8e1048ec796b5d36212612c74ead8b4a5/68747470733a2f2f6661726d382e737461746963666c69636b722e636f6d2f373532332f32393931343334363939355f383036663437343662635f7a5f642e6a7067\" alt=\"IndieWebCampBrighton2016\" /></a></p>\n\n<p>The event will be free to attend, but I\u2019ll set up an official ticket page on Ti.to to keep track of who\u2019s coming. I\u2019ll let you know when that\u2019s up and ready. In the meantime, you can register your interest in attending on <a href=\"https://indieweb.org/2019/Brighton\">the 2019 Indie Webcamp Brighton page</a> on the Indie Web wiki.</p>"
    },
    "author": {
        "type": "card",
        "name": "Jeremy Keith",
        "url": "https://adactio.com/",
        "photo": "https://aperture-proxy.p3k.io/bbbacdf0a064621004f2ce9026a1202a5f3433e0/68747470733a2f2f6164616374696f2e636f6d2f696d616765732f70686f746f2d3135302e6a7067"
    },
    "post-type": "article",
    "_id": "3716988",
    "_source": "2",
    "_is_read": true
}

github.com/chrisdavidmills/mdn-and-frameworks/issues/1

Tantek Çelik tantek.com

https://github.com/flaki your understanding is correct. microformats2 (specifically microformats.org/wiki/h-entry for a https://indieweb.org/reply ) would work well to mark-up such useful asides and other notes / comments regarding MDN pages, notifying those pages using Webmention, and handling them accordingly via moderation etc.

How those asides or notes are displayed on the MDN page is up to the design of the MDN page.

In addition Webmention also allows for easily submitting updates to such asides, notes, and comments and having them handled automatically for accepted submissions, or again via a moderation step.

May 30, 2019 9:33am -07:00

{
    "type": "entry",
    "published": "2019-05-30 09:33-0700",
    "url": "http://tantek.com/2019/150/t2/",
    "in-reply-to": [
        "https://github.com/chrisdavidmills/mdn-and-frameworks/issues/1"
    ],
    "content": {
        "text": "https://github.com/flaki your understanding is correct. microformats2 (specifically microformats.org/wiki/h-entry for a https://indieweb.org/reply ) would work well to mark-up such useful asides and other notes / comments regarding MDN pages, notifying those pages using Webmention, and handling them accordingly via moderation etc.\n\nHow those asides or notes are displayed on the MDN page is up to the design of the MDN page.\n\nIn addition Webmention also allows for easily submitting updates to such asides, notes, and comments and having them handled automatically for accepted submissions, or again via a moderation step.",
        "html": "<a href=\"https://github.com/flaki\">https://github.com/flaki</a> your understanding is correct. microformats2 (specifically <a href=\"http://microformats.org/wiki/h-entry\">microformats.org/wiki/h-entry</a> for a <a href=\"https://indieweb.org/reply\">https://indieweb.org/reply</a> ) would work well to mark-up such useful asides and other notes / comments regarding MDN pages, notifying those pages using Webmention, and handling them accordingly via moderation etc.<br /><br />How those asides or notes are displayed on the MDN page is up to the design of the MDN page.<br /><br />In addition Webmention also allows for easily submitting updates to such asides, notes, and comments and having them handled automatically for accepted submissions, or again via a moderation step."
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "reply",
    "refs": {
        "https://github.com/chrisdavidmills/mdn-and-frameworks/issues/1": {
            "type": "entry",
            "url": "https://github.com/chrisdavidmills/mdn-and-frameworks/issues/1",
            "name": "issue 1 of GitHub project \u201cmdn-and-frameworks\u201d",
            "post-type": "article"
        }
    },
    "_id": "3716399",
    "_source": "1",
    "_is_read": true
}

twitter.com/triblondon/status/1133980818496479232

Jeremy Keith adactio.com

None of these are “surely a good thing” if you look at them from the perspective of a user:

https://ourincrediblejourney.tumblr.com/

https://indieweb.org/site-deaths

May 30, 2019 7:57am +00:00

{
    "type": "entry",
    "published": "2019-05-30T07:57:54Z",
    "url": "https://adactio.com/notes/15247",
    "syndication": [
        "https://twitter.com/adactio/status/1134006004943937536"
    ],
    "in-reply-to": [
        "https://twitter.com/triblondon/status/1133980818496479232"
    ],
    "content": {
        "text": "None of these are \u201csurely a good thing\u201d if you look at them from the perspective of a user:\n\nhttps://ourincrediblejourney.tumblr.com/\n\nhttps://indieweb.org/site-deaths",
        "html": "<p>None of these are \u201csurely a good thing\u201d if you look at them from the perspective of a user:</p>\n\n<p><a href=\"https://ourincrediblejourney.tumblr.com/\">https://ourincrediblejourney.tumblr.com/</a></p>\n\n<p><a href=\"https://indieweb.org/site-deaths\">https://indieweb.org/site-deaths</a></p>"
    },
    "author": {
        "type": "card",
        "name": "Jeremy Keith",
        "url": "https://adactio.com/",
        "photo": "https://aperture-proxy.p3k.io/bbbacdf0a064621004f2ce9026a1202a5f3433e0/68747470733a2f2f6164616374696f2e636f6d2f696d616765732f70686f746f2d3135302e6a7067"
    },
    "post-type": "reply",
    "_id": "3709296",
    "_source": "2",
    "_is_read": true
}

Homebrew Website Club SF!

17:30: Optional writing hour and socializing 18:30: IndieWeb demos and hack night! Homebrew Website Club retro 1980s-style logo Topics for this week: Recent IndieWebCamps! IndieWebCamp Berlin IndieWebCamp Düsseldorf IndieWebCamp Utrecht Take Back Your Web talk at Beyond Tellerand Düsseldorf The New Yorker: Can Indie Social Media Save Us Demos of personal website breakthroughs Create or update your personal web site! Sign-up for the 2019 IndieWeb Summit! Join a community with like-minded interests. Bring friends that want a personal site, or are interested in a healthy, independent web! Any questions? Ask in #indieweb Slack or IRC More information: IndieWeb Wiki Event Page RSVP: post an indie RSVP on your own site!

May 29, 2019 11:59pm -07:00

{
    "type": "event",
    "name": "Homebrew Website Club SF!",
    "summary": "17:30: Optional writing hour and socializing\n18:30: IndieWeb demos and hack night!\n\nHomebrew Website Club retro 1980s-style logo\nTopics for this week: Recent IndieWebCamps! IndieWebCamp Berlin IndieWebCamp D\u00fcsseldorf IndieWebCamp Utrecht Take Back Your Web talk at Beyond Tellerand D\u00fcsseldorf The New Yorker: Can Indie Social Media Save Us Demos of personal website breakthroughs Create or update your personal web site! Sign-up for the 2019 IndieWeb Summit!\nJoin a community with like-minded interests. Bring friends that want a personal site, or are interested in a healthy, independent web!\nAny questions? Ask in #indieweb Slack or IRC\nMore information: IndieWeb Wiki Event Page\nRSVP: post an indie RSVP on your own site!",
    "published": "2019-05-29 23:59-0700",
    "start": "2019-06-12 17:30-0700",
    "end": "2019-06-12 19:30-0700",
    "url": "http://tantek.com/2019/163/e1/homebrew-website-club-sf",
    "location": [
        "https://wiki.mozilla.org/SF"
    ],
    "content": {
        "text": "When: 2019-06-12 17:30\u202619:30\nWhere: Mozilla San Francisco\n\nHost: Tantek \u00c7elik\n\n\n\n17:30: Optional writing hour and socializing\n\n18:30: IndieWeb demos and hack night!\n\n\nTopics for this week:\nRecent IndieWebCamps!\nIndieWebCamp Berlin\nIndieWebCamp D\u00fcsseldorf\nIndieWebCamp Utrecht\n\n\nTake Back Your Web talk at Beyond Tellerand D\u00fcsseldorf\nThe New Yorker: Can Indie Social Media Save Us\nDemos of personal website breakthroughs\nCreate or update your personal web site!\nSign-up for the 2019 IndieWeb Summit!\n\n\nJoin a community with like-minded interests. Bring friends that want a personal site, or are interested in a healthy, independent web!\n\n\nAny questions? Ask in \n#indieweb Slack or IRC\n\n\nMore information: \nIndieWeb Wiki Event Page\n\n\nRSVP:  post an indie RSVP on your own site!",
        "html": "<p>\nWhen: <time class=\"dt-start\">2019-06-12 17:30</time>\u2026<time class=\"dt-end\">19:30</time><span>\nWhere: <a class=\"u-location h-card\" href=\"https://wiki.mozilla.org/SF\">Mozilla San Francisco</a>\n</span>\nHost: <a class=\"u-organizer h-card\" href=\"http://tantek.com/\">Tantek \u00c7elik</a>\n</p>\n\n<p>\n17:30: Optional writing hour and socializing<br />\n18:30: IndieWeb demos and hack night!<br /></p>\n<p><img class=\"u-featured\" style=\"height:300px;\" src=\"https://aperture-media.p3k.io/indieweb.org/c24f7b1e711955ef818bde12e2a3e79708ecc9b106d95b460a9fefe93b0be723.jpg\" alt=\"Homebrew Website Club retro 1980s-style logo\" /></p>\n<p>Topics for this week:</p>\n<ul><li>Recent IndieWebCamps!\n<ul><li><a href=\"https://indieweb.org/2019/Berlin\">IndieWebCamp Berlin</a></li>\n<li><a href=\"https://indieweb.org/2019/D%C3%BCsseldorf\">IndieWebCamp D\u00fcsseldorf</a></li>\n<li><a href=\"https://indieweb.org/2019/Utrecht\">IndieWebCamp Utrecht</a></li>\n</ul></li>\n<li>\n<a href=\"https://vimeo.com/336343886\">Take Back Your Web</a> talk at Beyond Tellerand D\u00fcsseldorf</li>\n<li><a href=\"https://www.newyorker.com/tech/annals-of-technology/can-indie-social-media-save-us\">The New Yorker: Can Indie Social Media Save Us</a></li>\n<li>Demos of personal website breakthroughs</li>\n<li>Create or update your personal web site!</li>\n<li>Sign-up for the <a href=\"https://2019.indieweb.org/summit\">2019 IndieWeb Summit!</a>\n</li>\n</ul><p>\nJoin a community with like-minded interests. Bring friends that want a personal site, or are interested in a healthy, independent web!\n</p>\n<p>\nAny questions? Ask in \n<a href=\"https://indieweb.org/discuss\">#indieweb Slack or IRC</a>\n</p>\n<p>\nMore information: \n<a class=\"u-url\" href=\"https://indieweb.org/events/2019-06-12-homebrew-website-club\">IndieWeb Wiki Event Page</a>\n</p>\n<p>\nRSVP:  post an <a href=\"https://indieweb.org/rsvp\">indie RSVP</a> on your own site!\n</p>"
    },
    "post-type": "event",
    "refs": {
        "https://wiki.mozilla.org/SF": {
            "type": "card",
            "name": "Mozilla San Francisco",
            "url": "https://wiki.mozilla.org/SF",
            "photo": null
        }
    },
    "_id": "3708544",
    "_source": "1",
    "_is_read": true
}

www.meetup.com/Summer-Of-Hacks-Oxford/events/261075078/

I'm looking forward to attending my first IndieWebCamp!

#indie-web-camp

May 18, 2019 9:08am +01:00

{
    "type": "entry",
    "published": "2019-05-18 09:08:09 +0100 BST",
    "rsvp": "yes",
    "url": "https://www.jvt.me/rsvps/c7c2c71e-b972-4990-851d-d814d943b173/",
    "category": [
        "indie-web-camp"
    ],
    "in-reply-to": [
        "https://www.meetup.com/Summer-Of-Hacks-Oxford/events/261075078/"
    ],
    "content": {
        "text": "I'm looking forward to attending my first IndieWebCamp!"
    },
    "post-type": "rsvp",
    "_id": "3705198",
    "_source": "2169",
    "_is_read": true
}

Kevin Marks known.kevinmarks.com/profile/kevinmarks

Renaming selfdogfooding to "eat what you cook" #indieweb

May 29, 2019 5:50pm +00:00

{
    "type": "entry",
    "published": "2019-05-29T17:50:08+0000",
    "url": "http://known.kevinmarks.com/2019/renaming-selfdogfooding-to-eat-what-you-cook-indieweb",
    "photo": [
        "https://aperture-proxy.p3k.io/b6297d9f1397a0793fa8e2daa2a28dfc69487c25/687474703a2f2f6b6e6f776e2e6b6576696e6d61726b732e636f6d2f66696c652f32333839633266353135343266333862646439376165666164623734373664642f7468756d622e6a7067"
    ],
    "name": "Renaming selfdogfooding to \"eat what you cook\" #indieweb",
    "author": {
        "type": "card",
        "name": "Kevin Marks",
        "url": "http://known.kevinmarks.com/profile/kevinmarks",
        "photo": "https://aperture-proxy.p3k.io/ed7979fd10a648fc253eae0b54e66fb36e57d3d4/687474703a2f2f6b6e6f776e2e6b6576696e6d61726b732e636f6d2f66696c652f3932353536353636363931373362373836376162383339656536353536663965"
    },
    "post-type": "photo",
    "refs": {
        "https://aperture-proxy.p3k.io/b6297d9f1397a0793fa8e2daa2a28dfc69487c25/687474703a2f2f6b6e6f776e2e6b6576696e6d61726b732e636f6d2f66696c652f32333839633266353135343266333862646439376165666164623734373664642f7468756d622e6a7067": {
            "type": "image",
            "ratio": 0.75,
            "bytes": 89795
        }
    },
    "_id": "3702799",
    "_source": "205",
    "_is_read": true
}

Book progress and interview

mathieudutour/medium-to-own-blog: Switch from Medium to your own blog in a few minutes

Khoi Vinh on How His Blog Amplified His Work and Career – Own Your Content

HWC NYC 2019-05-11 Wrap-Up

Open gardens

Third and fourth industrial revolutions for liberatory ends

Private posts: the move of the checkins

Medium | Stackbit

Designing in the open

Indie web events in Brighton

Homebrew Website Club SF!

Renaming selfdogfooding to "eat what you cook" #indieweb