Software Rots: SCUBA Edition

{
    "type": "entry",
    "published": "2019-02-06 00:54:23.464466",
    "url": "https://kongaloosh.com/e/2019/2/6/im-going-b",
    "name": "Software Rots: SCUBA Edition",
    "content": {
        "text": "I'm going back through my dive logbook after a three year diving hiatus. The software I use to track my dives has become an ungodly mess of company acquisitions and software maintenance. Turns out the company that made my dive-computer was bought out by scuba-pro.\nTo even get my hands on the software to open my dive-log file, I had to scour looking for a hidden link that would take me to the SmartTrak site. That wasn't even enough alone, I had to engage in browser witchcraft to coerce the site to not redirect me to scuba-pro's main site. The file is nowhere else, at least by my searching. Interesting that no one liked it enough to keep a mirror of it...\nOf course, the software didn't solve my problems. oh no. The dates were incorrect on some of my dives. Another example malady of poor software support: I could turn the background of dive profiles gradient olive green, but I could not edit basic dive info---e.g., the date and location of a dive. For the first-time in my life, I'm actually facing a deprecation of software that I need. It's important that I keep the data I collect when I'm diving.\nAfter going through old dev-forums and dive-forums, I found a converter which takes shameful SmartTrack files and converts them into a modified XML for use with SubSurface. At least I can coerce the file into being read as XML, rather than proprietary nonsense. More than that, not only does sub-surface allow me to edit the date of a dive in increments greater than 7, I can edit multiple dives at the same time. \nIt's the future.\nI can't help but feel that this is a sort of digital vagrancy. SubSurface seems great now, but what about in 3 years? 10 years? I know there's a trend of web-based dive-logs, but I don't want to have to shuffle around, converting what has no business being anything but XML or a CSV to bunch of proprietary, uninterpretable file formats. \nHaving been burnt by SmartTrack, I'm looking for robust export functionality. Luck for me, it seems sub-surface is able to export as CSVs. This seems like a clear candidate to make a stand and own my own data.\nIt's just screaming to be added to the blog. \nThen if something breaks, it's my own damn fault.\n        \n\n      \n\n        \n\n\n                                 \n                                            \n                \n                \n                \n                diving\n                \n                dev\n                \n                indieweb\n                \n                article",
        "html": "<p class=\"e-content\"></p><p>I'm going back through my dive logbook after a three year diving hiatus. The software I use to track my dives has become an ungodly mess of company acquisitions and software maintenance. Turns out the company that made my dive-computer was bought out by scuba-pro.</p>\n<p>To even get my hands on the software to open my dive-log file, I had to scour looking for a hidden link that would take me to the SmartTrak site. That wasn't even enough alone, I had to engage in browser witchcraft to coerce the site to not redirect me to scuba-pro's main site. The file is <em>nowhere else</em>, at least by my searching. Interesting that no one liked it enough to keep a mirror of it...</p>\n<p>Of course, the software didn't solve my problems. <em>oh no</em>. The dates were incorrect on some of my dives. Another example malady of poor software support: I could turn the background of dive profiles <em>gradient olive green</em>, but I could not edit basic dive info---e.g., the date and location of a dive. For the first-time in my life, I'm actually facing a deprecation of software that I <em>need</em>. It's important that I keep the data I collect when I'm diving.</p>\n<p>After going through old dev-forums and <a href=\"https://www.scubaboard.com/community/threads/smart-trak-to-logtrak-import.546613/page-2\">dive-forums</a>, I found <a href=\"https://thetheoreticaldiver.org/rch-cgi-bin/smtk2ssrf.pl\">a converter</a> which takes shameful SmartTrack files and converts them into a modified XML for use with <a href=\"https://subsurface-divelog.org/download/\">SubSurface</a>. At least I can coerce the file into being read as XML, rather than proprietary nonsense. More than that, not only does sub-surface allow me to edit the date of a dive in increments greater than 7, I can edit <em>multiple</em> dives at the same time. </p>\n<p>It's the future.</p>\n<p>I can't help but feel that this is a sort of digital vagrancy. SubSurface seems great now, but what about in 3 years? 10 years? I know there's a trend of web-based <a href=\"https://en.divelogs.de/\">dive-logs</a>, but I don't want to have to shuffle around, converting what has no business being anything but XML or a CSV to bunch of proprietary, uninterpretable file formats. </p>\n<p>Having been burnt by SmartTrack, I'm looking for robust export functionality. Luck for me, it seems sub-surface is able to export as CSVs. This seems like a clear candidate to make a stand and own my own data.</p>\n<p>It's just screaming to be added to the blog. \nThen if something breaks, it's my own damn fault.</p>\n        \n\n      \n\n        \n\n\n                                 \n                                            \n                \n                <i></i>\n                \n                <a href=\"https://kongaloosh.com/t/diving\">diving</a>\n                \n                <a href=\"https://kongaloosh.com/t/dev\">dev</a>\n                \n                <a href=\"https://kongaloosh.com/t/indieweb\">indieweb</a>\n                \n                <a href=\"https://kongaloosh.com/t/article\">article</a>"
    },
    "author": {
        "type": "card",
        "name": "Alex Kearney",
        "url": "http://kongaloosh.com",
        "photo": null
    },
    "post-type": "article",
    "_id": "2070368",
    "_source": "228",
    "_is_read": true
}

cdevroe cdevroe.com/author/cdevroe/

A new interview with Manton Reece of Micro.blog for 2019

{
    "type": "entry",
    "author": {
        "name": "cdevroe",
        "url": "http://cdevroe.com/author/cdevroe/",
        "photo": "http://0.gravatar.com/avatar/c248217e9cdc83ce95acc615199ce57f?s=512&d=http://cdevroe.com/wp-content/plugins/semantic-linkbacks/img/mm.jpg&r=g"
    },
    "url": "http://cdevroe.com/2019/02/05/manton-interview-2019/",
    "name": "A new interview with Manton Reece of Micro.blog for 2019",
    "content": {
        "html": "<p>Last year, around this time, <a href=\"http://cdevroe.com/2018/01/19/interview-manton/\">I published an interview</a> with <a href=\"http://manton.org\">Manton Reece</a> \u2013 founder of <a href=\"http://micro.blog\">Micro.blog</a> (M.b) \u2013 about how the platform was growing and what the goals for 2018 were. It was such a great interview and it helped me to understand the direction that M.b was going that I knew I had to interview him again to check in for 2019.</p>\n\n\n\n<p>Answering these questions isn\u2019t easy. Manton and I have been volleying back and forth for about 60 days for this interview to come to this point. So before we jump into the interview I just want to take a moment to thank Manton for taking the time to thoughtfully respond to my questions. I hope the entire M.b community enjoys this interview and it helps to give an idea of what is happening there and where the community and platform are headed.</p>\n\n\n\n<p>I\u2019ve tried to include links to most everything we mention so that you\u2019re able to find all of the little tidbits. If I missed anything, leave a comment or reply on M.b and I\u2019ll try to track down what you\u2019re looking for.</p>\n\n\n\n<p>Now, onto the interview:</p>\n\n\n\n<p><strong>Thank you again Manton for taking some time to answer my questions. <a href=\"http://cdevroe.com/2018/01/19/interview-manton/\">Last year\u2019s interview</a> was fun so I thought it\u2019d be a good idea to revisit a few of the topics in it and also catch up with you on how Micro.blog is doing and see where it is headed in 2019. Last year you mentioned that most of the growth on the team would come in the form of curators or support. Has the team grown? If so, what does the team look like today and what will it look like in 2019?</strong></p>\n\n\n\n<p><strong>Manton:</strong> Great to talk to you again! The size of the team has not grown since last year, but I think we\u2019ve done more with the people we have. <a href=\"https://micro.blog/macgenie\">Jean MacDonald</a> has hosted over 40 episodes of our <a href=\"https://monday.micro.blog/\">Micro Monday podcast</a>, and <a href=\"https://micro.blog/cheesemaker\">Jon Hays</a> has lead recent improvements to our iOS app and new apps <a href=\"https://sunlit.io/\">Sunlit</a> and <a href=\"https://help.micro.blog/2018/wavelength/\">Wavelength</a>. I still expect the growth to be on the curation side and hope that can be a focus of 2019. Where the other big social networks try to use algorithms to solve problems, we think if you want a great community, humans need to be actively involved \u2014 featuring content, listening for problems, and thinking about the impact of new features.</p>\n\n\n\n<p>Customer support and system administration are the other areas that I\u2019m looking forward to getting help with, but as the platform evolves it\u2019s still valuable for me to be handling most of that myself. I hear from customers every day about what they love and what features are missing. Since we last talked, I\u2019ve also moved <a href=\"http://manton.org\">my primary blog</a> with thousands of posts from WordPress to Micro.blog hosting, and that has been a great way to prioritize improvements to the hosting part of the platform. Blog hosting is the actual business of Micro.blog and enables us to do everything else we want to do for the social network and community.</p>\n\n\n\n<p><strong>From an outsider\u2019s perspective, I don\u2019t know how you\u2019re able to do as much as you do! You are coding Micro.blog, keeping up with the infrastructure software/hardware, dealing with support, paying the bills\u2026 the list goes on and on. Then, on top of all that, you\u2019re building a few iOS apps like Sunlit and Wavelength. You also have your own podcast called <a href=\"https://timetable.manton.org/\">Timetable</a> and a long-running podcast called <a href=\"https://coreint.org/\">Core Intuition</a>. Not to mention your personal blog, <a href=\"http://help.micro.blog/\">help documents for Micro.blog</a>, and keeping up with the community and <a href=\"https://micro.blog/slack\">the Slack channel</a>.</strong></p>\n\n\n\n<p><strong>How do you prioritize all of this? Is one project more important than another?</strong></p>\n\n\n\n<p><strong>Manton:</strong> I think good things can come from trying to do a little too much, but it\u2019s not usually sustainable. Eventually it catches up with you and you have to simplify and wrap up or delegate some tasks. We are in that kind of period right now with Micro.blog. We will continue to do a lot, but some parts of the platform \u2014 like the iOS apps \u2014 can reach a point of maturity where we work on stability improvements and polishing existing features rather than adding brand new features.</p>\n\n\n\n<p>Android is another good example. Many people ask for an official Android app for Micro.blog. Because I don\u2019t have much Android experience myself, I know I would be stretched too thin right now to tackle it, so we are encouraging third-party solutions instead. There\u2019s a new version of <a href=\"https://dialogapp.net/\">Dialog</a> for Android which has full support for the Micro.blog timeline, posting, replying, the Discover sections, and more. I\u2019m really excited about it.</p>\n\n\n\n<p>The most important project is the Micro.blog web platform, because without that foundation nothing else is possible. Improving <a href=\"https://help.micro.blog/2018/api-overview/\">the API</a> and blog hosting will always be something we work on, alongside other priorities that come and go.</p>\n\n\n\n<p><strong>I for one am very happy that Dialog exists. I\u2019m also happy that it is pretty good too. What other third-party projects have you come across that more people should know about? And, what haven\u2019t you seen made on top of Micro.blog that you wish existed?</strong></p>\n\n\n\n<p><strong>Manton:</strong> People should keep an eye on <a href=\"https://vincentritter.com/apps\">Gluon</a>, which is in development now for iOS and Android. I\u2019ve enjoyed reading developer <a href=\"https://vincentritter.com/2019/01/29/gluon-a-new-beginning\">Vincent Ritter\u2019s blog post updates</a> about working on it \u2014 the early choices he made on how to build the app and later decisions to update the UI and rewrite portions of it.</p>\n\n\n\n<p>Integrating other platforms is another area that is great for third-party apps. For example, IndieWeb-compatible tools like <a href=\"https://ownyourgram.com/\">OwnYourGram</a> (for copying Instagram posts to your blog) or <a href=\"https://indiebookclub.biz/\">IndieBookClub</a> (for posting about books you\u2019re reading or want to read). Having so many third-party apps that can supplement the basic features on Micro.blog means that we can keep the primary experience as streamlined as possible, because the goal is to make blogging easier. I\u2019d love to see more advanced tools for managing posts as well, such as batch editing posts or for import and export.</p>\n\n\n\n<p><strong>Switching gears for a moment to Micro.blog\u2019s long term financial sustainability. I know at first there was a funding push related to the Kickstarter campaign, and of course there are those that pay a few dollars per year for the hosted service or other features like cross posting. What does long term sustainability look like for Micro.blog? Does there need to be a lot of growth in the customer base? How else can people like me, who use Micro.blog daily but are not currently paying, help keep Micro.blog funded?</strong></p>\n\n\n\n<p><strong>Manton:</strong> Kickstarter was perfect to get us started, but paid subscriptions are better long term. I want to build features that are valuable and worth paying for. So we\u2019ll keep making our blog hosting more compelling so that it\u2019s good for people who are just getting started with a new blog, or people who want to migrate from other platforms. We often see people who might have a primary blog on WordPress \u2014 and a secondary microblog or photo blog on Micro.blog \u2014 decide that it\u2019s simpler to just consolidate everything to Micro.blog, importing their WordPress posts. We don\u2019t expect all the millions of bloggers who host on WordPress to move over to Micro.blog, but even a relatively small number moving to Micro.blog will make the platform more sustainable.</p>\n\n\n\n<p>We just rolled out several major new features for blog hosting, including categories and custom themes, so you can have full control over the HTML, CSS, and JavaScript on your site. You don\u2019t need to be a designer or developer to use Micro.blog, but it\u2019s nice to allow some more flexibility for those people who do want to tinker with their site. And now <a href=\"https://www.manton.org/2019/01/30/custom-templates-categories.html\">web developers can create custom themes for Micro.blog</a> that can be used by other members of the community.</p>\n\n\n\n<p>As for supporting Micro.blog if you aren\u2019t a paying customer, the best way is to tell people about it. All our growth right now is from word of mouth. It\u2019s great when people invite their friends from other social networks, or when they post about why they like Micro.blog on their own blog or talk about it on their podcast. You don\u2019t need to have a large audience to make a big difference.</p>\n\n\n\n<p><strong>I\u2019d be remiss to not mention the apparent resurgence of blogging. If not in action then in the collective consciousness. It seems many people are talking and writing about blogging lately. With Medium changing its policies, Tumblr being owned by Oath/Verizon/Aol, Twitter being a hive of villainy, Facebook selling our fears to our captors, and Instagram growing up to be like\u2019s its parent\u2026 it seems that blogging is poised to have a huge comeback. Are you doing anything at all to capture that momentum? Or, are you just trying to keep on your roadmap as usual?</strong></p>\n\n\n\n<p><strong>Manton:</strong> It feels like everything we\u2019ve been working toward for a few years is starting to come together, as more people realize the downsides of these massive, centralized platforms. Whether someone is quitting Facebook tomorrow or a year from now, I want Micro.blog to be a great default choice for reclaiming ownership of your content and getting in the habit of writing or posting photos regularly. When Basecamp recently migrated their long-running blog Signal v. Noise away from Medium, <a href=\"https://m.signalvnoise.com/signal-v-noise-exits-medium/\">they summed up the change just like we see it</a>: \u201cTraditional blogs might have swung out of favor,\u00a0as we all discovered the benefits of social media and aggregating platforms, but we think they\u2019re about to swing back in style, as we all discover the\u00a0real costs and problems brought by such centralization.\u201d</p>\n\n\n\n<p>The other part of this is to have a safe, welcoming community. I hate to see people get discouraged from blogging because \u201cno one\u201d is reading, so it helps that we have the Micro.blog timeline and replies where a blog post can start a conversation, or new posts can be featured in the Discover section.\u00a0I think 2019 is going to be great for blogging. Micro.blog differentiates itself because it offers a solution for both blog hosting and a great community.</p>\n\n\n\n<p><strong>Professional blogging; whether that be funded by advertisers, subscribers, fans \u2013 is a big business. What are your thoughts on how Micro.blog helps or ignores people or businesses that may want to use the platform to share their content and earn a living from it?</strong></p>\n\n\n\n<p><strong>Manton:</strong> Micro.blog was designed for people, not \u201cbrands\u201d, but there\u2019s no reason it can\u2019t be used for businesses as well. Toward the end of last year I wrote a \u201c12 days of microblogging\u201d blog post series, and on one day <a href=\"https://manton.org/2018/12/10/days-of-microblogging.html\">highlighted how businesses can use Micro.blog</a>.</p>\n\n\n\n<p>Personal blogs can evolve into a revenue source as well, like offering subscriptions or sponsorships. But Micro.blog will never have ads and we aren\u2019t likely to add features specifically for people to make money from their content in the way that Medium is trying to do. We want to focus on helping people discover blog posts, and whether someone monetizes their blog or uses it for occasional self-promotion is up to them. It\u2019s okay if most blogs are personal and non-commercial because that lends itself to authenticity, and there\u2019s great value in just having a space of your own to publish to.</p>\n\n\n\n<p>We also think podcasting is only going to get bigger, which is why our first new <a href=\"https://help.micro.blog/2018/pricing/\">paid plan</a> was microcast hosting for short-form podcasts. We keep increasing the limits and now you can publish even hour-long episodes to Micro.blog. Like personal blogs, podcasts could be sponsored, or they could be just for fun, or they could indirectly benefit your business, such as supplementing a blog or helping promote something else you\u2019re working on.</p>\n\n\n\n<p><strong>I believe you\u2019ve touched on open source regarding Micro.blog in the past. Some of your own projects, like JSON Feed, are open source. Will you be open sourcing Micro.blog or any pieces of it?</strong></p>\n\n\n\n<p><strong>Manton:</strong> I don\u2019t plan to open source all of Micro.blog in the near future. It\u2019s a complicated project with several components across multiple servers, so it\u2019s not really suitable for just \u201crunning yourself\u201d right now. However, I\u2019d love to open source more of it, especially when there\u2019s an immediate benefit to people. For example, for the new custom themes feature, I rewrote all of the themes to use the Hugo blogging engine, and <a href=\"https://github.com/microdotblog\">we\u2019ve shared all our changes on GitHub</a>. That\u2019s something people can use right away. Jon Hays also wrote a framework called <a href=\"https://github.com/microdotblog/snippets\">\u201cSnippets\u201d for the Micro.blog API and Micropub API</a> that we\u2019ll be using in our iOS apps, and we\u2019ve open sourced that as well. I think there is more in our iOS apps (including Wavelength for podcasts and Sunlit for photos) that would be great to open source.</p>\n\n\n\n<p><strong>I think I catch myself looking for a search feature on Micro.blog at least twice a week. For instance, I\u2019m big into houseplants lately and I wanted to find some people on M.b that were as well. And I can\u2019t figure out how to do that. Is search coming?</strong></p>\n\n\n\n<p>We now have <a href=\"https://micro.blog/discover/search?q=devroe\">a basic search on the web</a> version of Micro.blog under <a href=\"https://micro.blog/discover\">Discover</a>. This currently searches any post that has been included in Discover. We have plans to add search to the native apps so that it\u2019s easier to access, and expand it so that it searches even more posts on Micro.blog. However, one of the early design goals with Micro.blog was to launch without a full search index, because I didn\u2019t like how Twitter\u2019s search and especially trending topics could be gamed or expose the worst conversations on the platform, even in some cases being a place for more abusive, hateful replies. So we\u2019re going a little slowly with search to make sure that we don\u2019t recreate any of those problems.</p>\n\n\n\n<p><strong>I know I\u2019m only scratching the surface for the questions that the community is likely curious about. I hope I did an OK job asking the important ones. Are there any topics I left off that you wish I had asked you about? Or anything you\u2019d like to highlight?</strong></p>\n\n\n\n<p>Your questions were great. Thank you! I\u2019d like to mention again what Jean MacDonald has done with our podcast <a href=\"https://monday.micro.blog/\">Micro Monday</a>. This podcast didn\u2019t exist when you interviewed me last year, and now we have a great archive of episodes highlighting members of the community \u2014 how they got started blogging and what they are interested in, whether that\u2019s related to Micro.blog or something else. It helps people understand Micro.blog while at the same time featuring stories from the community. I\u2019m always inspired hearing what people are up to, and it\u2019s a weekly reminder to me of how important it is that people have a voice on the web with their own blog.</p>\n\n\n\n<p>What a fun interview! Until next year\u2026<br /></p>",
        "text": "Last year, around this time, I published an interview with Manton Reece &#8211; founder of Micro.blog (M.b) &#8211; about how the platform was growing and what the goals for 2018 were. It was such a great interview and it helped me to understand the direction that M.b was going that I knew I had to interview him again to check in for 2019.\n\n\n\nAnswering these questions isn&#8217;t easy. Manton and I have been volleying back and forth for about 60 days for this interview to come to this point. So before we jump into the interview I just want to take a moment to thank Manton for taking the time to thoughtfully respond to my questions. I hope the entire M.b community enjoys this interview and it helps to give an idea of what is happening there and where the community and platform are headed.\n\n\n\nI&#8217;ve tried to include links to most everything we mention so that you&#8217;re able to find all of the little tidbits. If I missed anything, leave a comment or reply on M.b and I&#8217;ll try to track down what you&#8217;re looking for.\n\n\n\nNow, onto the interview:\n\n\n\nThank you again Manton for taking some time to answer my questions. Last year\u2019s interview was fun so I thought it\u2019d be a good idea to revisit a few of the topics in it and also catch up with you on how Micro.blog is doing and see where it is headed in 2019. Last year you mentioned that most of the growth on the team would come in the form of curators or support. Has the team grown? If so, what does the team look like today and what will it look like in 2019?\n\n\n\nManton: Great to talk to you again! The size of the team has not grown since last year, but I think we&#8217;ve done more with the people we have. Jean MacDonald has hosted over 40 episodes of our Micro Monday podcast, and Jon Hays has lead recent improvements to our iOS app and new apps Sunlit and Wavelength. I still expect the growth to be on the curation side and hope that can be a focus of 2019. Where the other big social networks try to use algorithms to solve problems, we think if you want a great community, humans need to be actively involved \u2014 featuring content, listening for problems, and thinking about the impact of new features.\n\n\n\nCustomer support and system administration are the other areas that I&#8217;m looking forward to getting help with, but as the platform evolves it&#8217;s still valuable for me to be handling most of that myself. I hear from customers every day about what they love and what features are missing. Since we last talked, I&#8217;ve also moved my primary blog with thousands of posts from WordPress to Micro.blog hosting, and that has been a great way to prioritize improvements to the hosting part of the platform. Blog hosting is the actual business of Micro.blog and enables us to do everything else we want to do for the social network and community.\n\n\n\nFrom an outsider\u2019s perspective, I don\u2019t know how you\u2019re able to do as much as you do! You are coding Micro.blog, keeping up with the infrastructure software/hardware, dealing with support, paying the bills\u2026 the list goes on and on. Then, on top of all that, you\u2019re building a few iOS apps like Sunlit and Wavelength. You also have your own podcast called Timetable and a long-running podcast called Core Intuition. Not to mention your personal blog, help documents for Micro.blog, and keeping up with the community and the Slack channel.\n\n\n\nHow do you prioritize all of this? Is one project more important than another?\n\n\n\nManton: I think good things can come from trying to do a little too much, but it&#8217;s not usually sustainable. Eventually it catches up with you and you have to simplify and wrap up or delegate some tasks. We are in that kind of period right now with Micro.blog. We will continue to do a lot, but some parts of the platform \u2014 like the iOS apps \u2014 can reach a point of maturity where we work on stability improvements and polishing existing features rather than adding brand new features.\n\n\n\nAndroid is another good example. Many people ask for an official Android app for Micro.blog. Because I don&#8217;t have much Android experience myself, I know I would be stretched too thin right now to tackle it, so we are encouraging third-party solutions instead. There&#8217;s a new version of Dialog for Android which has full support for the Micro.blog timeline, posting, replying, the Discover sections, and more. I&#8217;m really excited about it.\n\n\n\nThe most important project is the Micro.blog web platform, because without that foundation nothing else is possible. Improving the API and blog hosting will always be something we work on, alongside other priorities that come and go.\n\n\n\nI for one am very happy that Dialog exists. I\u2019m also happy that it is pretty good too. What other third-party projects have you come across that more people should know about? And, what haven\u2019t you seen made on top of Micro.blog that you wish existed?\n\n\n\nManton: People should keep an eye on Gluon, which is in development now for iOS and Android. I&#8217;ve enjoyed reading developer Vincent Ritter&#8217;s blog post updates about working on it \u2014 the early choices he made on how to build the app and later decisions to update the UI and rewrite portions of it.\n\n\n\nIntegrating other platforms is another area that is great for third-party apps. For example, IndieWeb-compatible tools like OwnYourGram (for copying Instagram posts to your blog) or IndieBookClub (for posting about books you&#8217;re reading or want to read). Having so many third-party apps that can supplement the basic features on Micro.blog means that we can keep the primary experience as streamlined as possible, because the goal is to make blogging easier. I&#8217;d love to see more advanced tools for managing posts as well, such as batch editing posts or for import and export.\n\n\n\nSwitching gears for a moment to Micro.blog\u2019s long term financial sustainability. I know at first there was a funding push related to the Kickstarter campaign, and of course there are those that pay a few dollars per year for the hosted service or other features like cross posting. What does long term sustainability look like for Micro.blog? Does there need to be a lot of growth in the customer base? How else can people like me, who use Micro.blog daily but are not currently paying, help keep Micro.blog funded?\n\n\n\nManton: Kickstarter was perfect to get us started, but paid subscriptions are better long term. I want to build features that are valuable and worth paying for. So we&#8217;ll keep making our blog hosting more compelling so that it&#8217;s good for people who are just getting started with a new blog, or people who want to migrate from other platforms. We often see people who might have a primary blog on WordPress \u2014 and a secondary microblog or photo blog on Micro.blog \u2014 decide that it&#8217;s simpler to just consolidate everything to Micro.blog, importing their WordPress posts. We don&#8217;t expect all the millions of bloggers who host on WordPress to move over to Micro.blog, but even a relatively small number moving to Micro.blog will make the platform more sustainable.\n\n\n\nWe just rolled out several major new features for blog hosting, including categories and custom themes, so you can have full control over the HTML, CSS, and JavaScript on your site. You don&#8217;t need to be a designer or developer to use Micro.blog, but it&#8217;s nice to allow some more flexibility for those people who do want to tinker with their site. And now web developers can create custom themes for Micro.blog that can be used by other members of the community.\n\n\n\nAs for supporting Micro.blog if you aren&#8217;t a paying customer, the best way is to tell people about it. All our growth right now is from word of mouth. It&#8217;s great when people invite their friends from other social networks, or when they post about why they like Micro.blog on their own blog or talk about it on their podcast. You don&#8217;t need to have a large audience to make a big difference.\n\n\n\nI\u2019d be remiss to not mention the apparent resurgence of blogging. If not in action then in the collective consciousness. It seems many people are talking and writing about blogging lately. With Medium changing its policies, Tumblr being owned by Oath/Verizon/Aol, Twitter being a hive of villainy, Facebook selling our fears to our captors, and Instagram growing up to be like\u2019s its parent\u2026 it seems that blogging is poised to have a huge comeback. Are you doing anything at all to capture that momentum? Or, are you just trying to keep on your roadmap as usual?\n\n\n\nManton: It feels like everything we&#8217;ve been working toward for a few years is starting to come together, as more people realize the downsides of these massive, centralized platforms. Whether someone is quitting Facebook tomorrow or a year from now, I want Micro.blog to be a great default choice for reclaiming ownership of your content and getting in the habit of writing or posting photos regularly. When Basecamp recently migrated their long-running blog Signal v. Noise away from Medium, they summed up the change just like we see it: &#8220;Traditional blogs might have swung out of favor,&nbsp;as we all discovered the benefits of social media and aggregating platforms, but we think they\u2019re about to swing back in style, as we all discover the&nbsp;real costs and problems brought by such centralization.&#8221;\n\n\n\nThe other part of this is to have a safe, welcoming community. I hate to see people get discouraged from blogging because &#8220;no one&#8221; is reading, so it helps that we have the Micro.blog timeline and replies where a blog post can start a conversation, or new posts can be featured in the Discover section.&nbsp;I think 2019 is going to be great for blogging. Micro.blog differentiates itself because it offers a solution for both blog hosting and a great community.\n\n\n\nProfessional blogging; whether that be funded by advertisers, subscribers, fans \u2013 is a big business. What are your thoughts on how Micro.blog helps or ignores people or businesses that may want to use the platform to share their content and earn a living from it?\n\n\n\nManton: Micro.blog was designed for people, not &#8220;brands&#8221;, but there&#8217;s no reason it can&#8217;t be used for businesses as well. Toward the end of last year I wrote a &#8220;12 days of microblogging&#8221; blog post series, and on one day highlighted how businesses can use Micro.blog.\n\n\n\nPersonal blogs can evolve into a revenue source as well, like offering subscriptions or sponsorships. But Micro.blog will never have ads and we aren&#8217;t likely to add features specifically for people to make money from their content in the way that Medium is trying to do. We want to focus on helping people discover blog posts, and whether someone monetizes their blog or uses it for occasional self-promotion is up to them. It&#8217;s okay if most blogs are personal and non-commercial because that lends itself to authenticity, and there&#8217;s great value in just having a space of your own to publish to.\n\n\n\nWe also think podcasting is only going to get bigger, which is why our first new paid plan was microcast hosting for short-form podcasts. We keep increasing the limits and now you can publish even hour-long episodes to Micro.blog. Like personal blogs, podcasts could be sponsored, or they could be just for fun, or they could indirectly benefit your business, such as supplementing a blog or helping promote something else you&#8217;re working on.\n\n\n\nI believe you\u2019ve touched on open source regarding Micro.blog in the past. Some of your own projects, like JSON Feed, are open source. Will you be open sourcing Micro.blog or any pieces of it?\n\n\n\nManton: I don&#8217;t plan to open source all of Micro.blog in the near future. It&#8217;s a complicated project with several components across multiple servers, so it&#8217;s not really suitable for just &#8220;running yourself&#8221; right now. However, I&#8217;d love to open source more of it, especially when there&#8217;s an immediate benefit to people. For example, for the new custom themes feature, I rewrote all of the themes to use the Hugo blogging engine, and we&#8217;ve shared all our changes on GitHub. That&#8217;s something people can use right away. Jon Hays also wrote a framework called &#8220;Snippets&#8221; for the Micro.blog API and Micropub API that we&#8217;ll be using in our iOS apps, and we&#8217;ve open sourced that as well. I think there is more in our iOS apps (including Wavelength for podcasts and Sunlit for photos) that would be great to open source.\n\n\n\nI think I catch myself looking for a search feature on Micro.blog at least twice a week. For instance, I\u2019m big into houseplants lately and I wanted to find some people on M.b that were as well. And I can\u2019t figure out how to do that. Is search coming?\n\n\n\nWe now have a basic search on the web version of Micro.blog under Discover. This currently searches any post that has been included in Discover. We have plans to add search to the native apps so that it&#8217;s easier to access, and expand it so that it searches even more posts on Micro.blog. However, one of the early design goals with Micro.blog was to launch without a full search index, because I didn&#8217;t like how Twitter&#8217;s search and especially trending topics could be gamed or expose the worst conversations on the platform, even in some cases being a place for more abusive, hateful replies. So we&#8217;re going a little slowly with search to make sure that we don&#8217;t recreate any of those problems.\n\n\n\nI know I\u2019m only scratching the surface for the questions that the community is likely curious about. I hope I did an OK job asking the important ones. Are there any topics I left off that you wish I had asked you about? Or anything you\u2019d like to highlight?\n\n\n\nYour questions were great. Thank you! I&#8217;d like to mention again what Jean MacDonald has done with our podcast Micro Monday. This podcast didn&#8217;t exist when you interviewed me last year, and now we have a great archive of episodes highlighting members of the community \u2014 how they got started blogging and what they are interested in, whether that&#8217;s related to Micro.blog or something else. It helps people understand Micro.blog while at the same time featuring stories from the community. I&#8217;m always inspired hearing what people are up to, and it&#8217;s a weekly reminder to me of how important it is that people have a voice on the web with their own blog.\n\n\n\n\n\n\n\nWhat a fun interview! Until next year&#8230;"
    },
    "published": "2019-02-05T13:47:10-05:00",
    "updated": "2019-02-05T14:56:04-05:00",
    "category": [
        "android",
        "blogging",
        "dialog",
        "gluon",
        "interview",
        "ios",
        "jean macdonald",
        "manton reece",
        "medium",
        "micro.blog",
        "podcasting",
        "recommended",
        "sunlit",
        "vincent ritter",
        "wavelength",
        "wordpress"
    ],
    "post-type": "article",
    "_id": "2065407",
    "_source": "236",
    "_is_read": true
}

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/02/04/i-still-cant.html",
    "content": {
        "html": "<p>I still can\u2019t believe it\u2019s February! IndieWebCamp Austin is coming up in just a few weeks. <a href=\"http://2019.indieweb.org/austin\">You can register here</a> for $5. It\u2019s a great time to learn more about the open web or get help with your own site.</p>",
        "text": "I still can\u2019t believe it\u2019s February! IndieWebCamp Austin is coming up in just a few weeks. You can register here for $5. It\u2019s a great time to learn more about the open web or get help with your own site."
    },
    "published": "2019-02-04T13:59:53-06:00",
    "post-type": "note",
    "_id": "2052698",
    "_source": "12",
    "_is_read": true
}

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/02/02/fixed-posting-from.html",
    "content": {
        "html": "<p>Fixed posting from IndieWeb-compatible apps (such as OwnYourGram or IndieBookClub) if they sent categories along with the new post. I didn\u2019t realize that <a href=\"https://ownyourgram.com/\">OwnYourGram</a> will automatically convert Instagram hashtags into blog post categories. Neat!</p>",
        "text": "Fixed posting from IndieWeb-compatible apps (such as OwnYourGram or IndieBookClub) if they sent categories along with the new post. I didn\u2019t realize that OwnYourGram will automatically convert Instagram hashtags into blog post categories. Neat!"
    },
    "published": "2019-02-02T14:46:21-06:00",
    "post-type": "note",
    "_id": "2029853",
    "_source": "12",
    "_is_read": true
}

Vika fireburn.ru

{
    "type": "entry",
    "published": "2019-01-31T21:21:34+03:00",
    "url": "https://fireburn.ru/note/1548958894",
    "category": [
        "indieweb",
        "domains",
        "security",
        "None://fireburn.ru/tags/indieweb",
        "None://fireburn.ru/tags/domains",
        "None://fireburn.ru/tags/security"
    ],
    "syndication": [
        "https://twitter.com/kisik21/status/1091038824514445314"
    ],
    "content": {
        "text": "Today you may have seen SSL errors on my domain. No, my private keys are safe. It's just that my domain was put on parking since I have forgot to renew it. Thankfully, the issue is resolved. Long live my #indieweb site! #domains #security",
        "html": "<p>Today you may have seen SSL errors on my domain. No, my private keys are safe. It's just that my domain was put on parking since I have forgot to renew it. Thankfully, the issue is resolved. Long live my <a class=\"u-category\">#indieweb</a> site! <a class=\"u-category\">#domains</a> <a class=\"u-category\">#security</a></p>"
    },
    "author": {
        "type": "card",
        "name": "Vika",
        "url": "https://fireburn.ru/",
        "photo": "https://aperture-proxy.p3k.io/3baa9a034ae34d783c6de676c0304b7640673c03/68747470733a2f2f666972656275726e2e72752f617661746172732f76696b612e706e67"
    },
    "post-type": "note",
    "_id": "2020855",
    "_source": "1371",
    "_is_read": true
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2019-02-01 15:25-0800",
    "url": "http://tantek.com/2019/032/t2/simpler-more-inclusive-accessible-indieweb",
    "category": [
        "microformats",
        "indieweb",
        "microformats2"
    ],
    "in-reply-to": [
        "https://mxb.at/blog/on-simplicity/"
    ],
    "content": {
        "text": "Great @mxbck post On Simplicity https://mxb.at/blog/on-simplicity/ via @adactio\n\nAdditionally: simpler approaches are more inclusive & accessible, e.g. #microformats & #indieweb\n\nFewer abstractions = less to learn before getting started.\n\nSimpler = less time cost on plumbing, tooling; faster to build something more useful.\n\nLess time required = more tinkerable by more people, especially those with less spare time on the margins = more inclusive and accessible.\n\nThe @microformats and @indiewebcamp communities have deliberately chosen explicitly simpler approaches:\n* microformats.org/wiki/start-simple\n* making #microformats2 even simpler: microformats.org/wiki/microformats2-origins#can_we_make_the_simplest_case_simpler\n* The IndieWeb Building Blocks approach (https://indieweb.org/building-blocks) rather than a monolithic \"Stack\"\n\nChoosing explicitly simpler approaches is more than just being smart & efficient, it\u2019s ethically the right thing to do.\n\nSimpler is a sociopolitical choice to deliberately provide more creative agency to more people. Beyond just more usable by more people, simpler technologies enable more people to build, adapt, alter, evolve their own tools of creation, rather than depending on a select privileged few to do so.\n\nPreviously, previously:\n* tantek.com/2018/309/t1/complexity-reinforces-privilege\n* tantek.com/2010/034/t3/simplicity",
        "html": "Great <a class=\"h-cassis-username\" href=\"https://twitter.com/mxbck\">@mxbck</a> post On Simplicity <a href=\"https://mxb.at/blog/on-simplicity/\">https://mxb.at/blog/on-simplicity/</a> via <a class=\"h-cassis-username\" href=\"https://twitter.com/adactio\">@adactio</a><br /><br />Additionally: simpler approaches are more inclusive &amp; accessible, e.g. #<span class=\"p-category\">microformats</span> &amp; #<span class=\"p-category\">indieweb</span><br /><br />Fewer abstractions = less to learn before getting started.<br /><br />Simpler = less time cost on plumbing, tooling; faster to build something more useful.<br /><br />Less time required = more tinkerable by more people, especially those with less spare time on the margins = more inclusive and accessible.<br /><br />The <a class=\"h-cassis-username\" href=\"https://twitter.com/microformats\">@microformats</a> and <a class=\"h-cassis-username\" href=\"https://twitter.com/indiewebcamp\">@indiewebcamp</a> communities have deliberately chosen explicitly simpler approaches:<br />* <a href=\"http://microformats.org/wiki/start-simple\">microformats.org/wiki/start-simple</a><br />* making #<span class=\"p-category\">microformats2</span> even simpler: <a href=\"http://microformats.org/wiki/microformats2-origins#can_we_make_the_simplest_case_simpler\">microformats.org/wiki/microformats2-origins#can_we_make_the_simplest_case_simpler</a><br />* The IndieWeb Building Blocks approach (<a href=\"https://indieweb.org/building-blocks\">https://indieweb.org/building-blocks</a>) rather than a monolithic \"Stack\"<br /><br />Choosing explicitly simpler approaches is more than just being smart &amp; efficient, it\u2019s ethically the right thing to do.<br /><br />Simpler is a sociopolitical choice to deliberately provide more creative agency to more people. Beyond just more usable by more people, simpler technologies enable more people to build, adapt, alter, evolve their own tools of creation, rather than depending on a select privileged few to do so.<br /><br />Previously, previously:<br />* <a href=\"http://tantek.com/2018/309/t1/complexity-reinforces-privilege\">tantek.com/2018/309/t1/complexity-reinforces-privilege</a><br />* <a href=\"http://tantek.com/2010/034/t3/simplicity\">tantek.com/2010/034/t3/simplicity</a>"
    },
    "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://mxb.at/blog/on-simplicity/": {
            "type": "entry",
            "url": "https://mxb.at/blog/on-simplicity/",
            "name": "mxb.at\u2019s post",
            "post-type": "article"
        }
    },
    "_id": "2020845",
    "_source": "1",
    "_is_read": true
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2019-02-01 14:13-0800",
    "url": "http://tantek.com/2019/032/t1/any-photos-wizardstower2019",
    "category": [
        "wizardstower2019",
        "IndieWeb"
    ],
    "in-reply-to": [
        "https://twitter.com/dustyweb/status/1091293951569641473"
    ],
    "content": {
        "text": "@dustyweb @sl007 great! Always awesome when hackathon demos work!\nAny photos from y\u2019all or the demo(s) at #wizardstower2019? \n\nIf you can post or link one in the next 30 min we should be able to get it into the This Week In The #IndieWeb newsletter.",
        "html": "<a class=\"h-cassis-username\" href=\"https://twitter.com/dustyweb\">@dustyweb</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/sl007\">@sl007</a> great! Always awesome when hackathon demos work!<br />Any photos from y\u2019all or the demo(s) at #<span class=\"p-category\">wizardstower2019</span>? <br /><br />If you can post or link one in the next 30 min we should be able to get it into the This Week In The #<span class=\"p-category\">IndieWeb</span> newsletter."
    },
    "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/dustyweb/status/1091293951569641473": {
            "type": "entry",
            "url": "https://twitter.com/dustyweb/status/1091293951569641473",
            "name": "@dustyweb\u2019s tweet",
            "post-type": "article"
        }
    },
    "_id": "2019767",
    "_source": "1",
    "_is_read": true
}

Manton Reece www.manton.org

Custom templates, categories, new theme, and more

{
    "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/01/30/custom-templates-categories.html",
    "name": "Custom templates, categories, new theme, and more",
    "content": {
        "html": "<p>We are launching several <em>major new features</em> for blog hosting on Micro.blog today. Any one of these features alone is a big change, and together I hope they will serve as a great foundation for years to come. The goal was to make blog hosting faster and more flexible for new features.</p>\n\n<p><strong>Custom templates:</strong> All the themes have been rewritten with extensibility in mind. As some of you may know, Micro.blog-hosted blogs <a href=\"https://www.manton.org/2016/07/06/building-on-jekyll.html\">were originally built on Jekyll</a>. They now use <a href=\"https://gohugo.io/\">Hugo</a>. There\u2019s an interface in Micro.blog for editing any of the built-in templates, or adding new ones for your own HTML or CSS. Click Posts \u2192 Design \u2192 Edit Themes.</p>\n\n<p><img src=\"https://aperture-proxy.p3k.io/99cfe38ee8192821625a53e5ae386dc2c5e25594/68747470733a2f2f7777772e6d616e746f6e2e6f72672f75706c6f6164732f323031392f666465356139646435342e706e67\" width=\"500\" height=\"232\" alt=\"Editing screenshot\" /></p>\n\n<p><strong>Categories:</strong> You can create a new category for your blog under Posts \u2192 Categories, and those categories will appear when editing a post or when creating a longer post with a title. We hide the category options be default when you are composing a short post, but in the new macOS app you can show the categories by choosing View \u2192 Categories. A list of your categories will appear at the top of Archive on your blog for readers to browse.</p>\n\n<p><img src=\"https://aperture-proxy.p3k.io/2bf5a90fd47560e11f9ebf3fbbec0d1e8e5e659b/68747470733a2f2f7777772e6d616e746f6e2e6f72672f75706c6f6164732f323031392f323962303039343861312e706e67\" width=\"500\" height=\"131\" alt=\"Checkboxes screenshot\" /></p>\n\n<p><strong>Auto-filter photos into a category:</strong> If you create a category like \u201cPhotos\u201d or \u201cPhotography\u201d, Micro.blog will offer to automatically assign this category when posting a new photo. Behind the scenes this is based on a new filtering system that will enable more features for other types of content in the future.</p>\n\n<p><img src=\"https://aperture-proxy.p3k.io/6812633fe6e60bac94fe8d03e2d483311f992d90/68747470733a2f2f7777772e6d616e746f6e2e6f72672f75706c6f6164732f323031392f656531313864666633372e706e67\" width=\"500\" height=\"300\" alt=\"Categories screenshot\" /></p>\n\n<p><strong>API for categories:</strong> I\u2019ve added categories support to both the MetaWeblog XML-RPC API and the Micropub API. This means that categories work great with <a href=\"https://red-sweater.com/marsedit/\">MarsEdit</a>. Categories are also included in your default JSON Feed in the \u201ctags\u201d field.</p>\n\n<p><img src=\"https://aperture-proxy.p3k.io/191759c5480cf68ec0529344836356479c8b2594/68747470733a2f2f7777772e6d616e746f6e2e6f72672f75706c6f6164732f323031392f333266396263663830362e706e67\" width=\"400\" height=\"271\" alt=\"MarsEdit screenshot\" /></p>\n\n<p><strong>Sharing themes:</strong> When creating a new custom theme, you can choose to clone it from an existing GitHub repository. This will allow someone to create a completely custom theme and share it with other members of the community. There\u2019s a \u201cBlank\u201d design if you are starting from scratch with your own templates.</p>\n\n<p><strong>New theme:</strong> I used the open source theme Arabica when testing these new features, and it\u2019s now an option under Posts \u2192 Design. It\u2019s a clean, simple design ported from Ghost.</p>\n\n<p><strong>Open source changes:</strong> All our themes for Micro.blog are available <a href=\"https://github.com/microdotblog\">on GitHub</a>. I have decided to keep the forked Jekyll repositories and completely replace the files with the Hugo version. I have mixed feelings about this, since the themes have diverged so much that they are no longer useful to the original authors, but I felt this was the best way to give credit to them for the designs, in addition to our credits page on Micro.blog.</p>\n\n<p><strong>Moving special pages:</strong> Micro.blog has some special pages like \u201cAbout\u201d and \u201cArchive\u201d. You can now re-order or even delete these under Posts \u2192 Pages. Combined with custom themes, this gives much more flexibility in customizing the navigation for your site.</p>\n\n<p>We\u2019ll be writing more about these new features in blog posts and the help site. If you notice any problems, please let me know. Thank you!</p>",
        "text": "We are launching several major new features for blog hosting on Micro.blog today. Any one of these features alone is a big change, and together I hope they will serve as a great foundation for years to come. The goal was to make blog hosting faster and more flexible for new features.\n\nCustom templates: All the themes have been rewritten with extensibility in mind. As some of you may know, Micro.blog-hosted blogs were originally built on Jekyll. They now use Hugo. There\u2019s an interface in Micro.blog for editing any of the built-in templates, or adding new ones for your own HTML or CSS. Click Posts \u2192 Design \u2192 Edit Themes.\n\n\n\nCategories: You can create a new category for your blog under Posts \u2192 Categories, and those categories will appear when editing a post or when creating a longer post with a title. We hide the category options be default when you are composing a short post, but in the new macOS app you can show the categories by choosing View \u2192 Categories. A list of your categories will appear at the top of Archive on your blog for readers to browse.\n\n\n\nAuto-filter photos into a category: If you create a category like \u201cPhotos\u201d or \u201cPhotography\u201d, Micro.blog will offer to automatically assign this category when posting a new photo. Behind the scenes this is based on a new filtering system that will enable more features for other types of content in the future.\n\n\n\nAPI for categories: I\u2019ve added categories support to both the MetaWeblog XML-RPC API and the Micropub API. This means that categories work great with MarsEdit. Categories are also included in your default JSON Feed in the \u201ctags\u201d field.\n\n\n\nSharing themes: When creating a new custom theme, you can choose to clone it from an existing GitHub repository. This will allow someone to create a completely custom theme and share it with other members of the community. There\u2019s a \u201cBlank\u201d design if you are starting from scratch with your own templates.\n\nNew theme: I used the open source theme Arabica when testing these new features, and it\u2019s now an option under Posts \u2192 Design. It\u2019s a clean, simple design ported from Ghost.\n\nOpen source changes: All our themes for Micro.blog are available on GitHub. I have decided to keep the forked Jekyll repositories and completely replace the files with the Hugo version. I have mixed feelings about this, since the themes have diverged so much that they are no longer useful to the original authors, but I felt this was the best way to give credit to them for the designs, in addition to our credits page on Micro.blog.\n\nMoving special pages: Micro.blog has some special pages like \u201cAbout\u201d and \u201cArchive\u201d. You can now re-order or even delete these under Posts \u2192 Pages. Combined with custom themes, this gives much more flexibility in customizing the navigation for your site.\n\nWe\u2019ll be writing more about these new features in blog posts and the help site. If you notice any problems, please let me know. Thank you!"
    },
    "published": "2019-01-30T16:34:48-06:00",
    "post-type": "article",
    "_id": "1997683",
    "_source": "12",
    "_is_read": true
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2019-01-30 11:25-0800",
    "url": "http://tantek.com/2019/030/t1/indieweb-summit-portland-planned",
    "category": [
        "IndieWeb"
    ],
    "in-reply-to": [
        "https://twitter.com/orlandomediaco/status/1090530156501000192"
    ],
    "content": {
        "text": "@splorp @orlandomediaco we do have the #IndieWeb Summit planned for June 29-30 in Portland, Oregon, a bit closer to you. Join us! Would be great to have you!\n\nhttps://indieweb.org/2019\n\nChat in https://chat.indieweb.org/ if you have any questions!",
        "html": "<a class=\"h-cassis-username\" href=\"https://twitter.com/splorp\">@splorp</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/orlandomediaco\">@orlandomediaco</a> we do have the #<span class=\"p-category\">IndieWeb</span> Summit planned for June 29-30 in Portland, Oregon, a bit closer to you. Join us! Would be great to have you!<br /><br /><a href=\"https://indieweb.org/2019\">https://indieweb.org/2019</a><br /><br />Chat in <a href=\"https://chat.indieweb.org/\">https://chat.indieweb.org/</a> if you have any questions!"
    },
    "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/orlandomediaco/status/1090530156501000192": {
            "type": "entry",
            "url": "https://twitter.com/orlandomediaco/status/1090530156501000192",
            "name": "@orlandomediaco\u2019s tweet",
            "post-type": "article"
        }
    },
    "_id": "1992998",
    "_source": "1",
    "_is_read": true
}

Malcolm Blaney unicyclic.com/mal

oooh I just saw this on twitter and now I want indiepay.me to do it too....

Read More

{
    "type": "entry",
    "published": "2019-01-30T12:04:15+10:00",
    "url": "https://unicyclic.com/mal/2019-01-30-oooh_I_just_saw_this_on_twitter_and_now_I_want_ind",
    "category": [
        "indieweb"
    ],
    "content": {
        "text": "oooh I just saw this on twitter and now I want indiepay.me to do it too....",
        "html": "oooh I just saw this on twitter and now I want <a href=\"https://indiepay.me\">indiepay.me</a> to do it too....<br /><br /><img alt=\"\" src=\"https://aperture-proxy.p3k.io/643cd12aa58805d90f5e45b486dc4cc8b5109dc3/68747470733a2f2f756e696379636c69632e636f6d2f6d616c2f7075626c69632f746970626f742e706e67\" />"
    },
    "author": {
        "type": "card",
        "name": "Malcolm Blaney",
        "url": "https://unicyclic.com/mal",
        "photo": "https://aperture-proxy.p3k.io/4f46272c0027449ced0d7cf8de31ea1bec37210e/68747470733a2f2f756e696379636c69632e636f6d2f6d616c2f7075626c69632f70726f66696c655f736d616c6c5f7468756d622e706e67"
    },
    "post-type": "note",
    "_id": "1987262",
    "_source": "243",
    "_is_read": true
}

Homebrew Website Club SF!

{
    "type": "event",
    "name": "Homebrew Website Club SF!",
    "summary": "17:30: Optional writing hour and quiet socializing\n18:30: IndieWeb demos and hack night!\n\nHomebrew Website Club retro 1980s-style logo\nTopics for this week: Year-end hack projects 2018 IndieWeb Challenge completed! Demos of personal website breakthroughs Create or update your personal web site!\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-01-29 19:29-0800",
    "start": "2019-02-06 17:30-0800",
    "end": "2019-02-06 19:30-0800",
    "url": "http://tantek.com/2019/037/e1/homebrew-website-club-sf",
    "location": [
        "https://wiki.mozilla.org/SF"
    ],
    "content": {
        "text": "When: 2019-02-06 17:30\u202619:30\nWhere: Mozilla San Francisco\n\nHost: Tantek \u00c7elik\n\n\n\n17:30: Optional writing hour and quiet socializing\n\n18:30: IndieWeb demos and hack night!\n\n\nTopics for this week:\nYear-end hack projects\n\n2018 IndieWeb Challenge completed!\nDemos of personal website breakthroughs\nCreate or update your personal web site!\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-02-06 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 quiet 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><a href=\"https://indieweb.org/2019-01-01-commitments\">Year-end hack projects</a></li>\n<li>\n<a href=\"https://indieweb.org/2018-12-indieweb-challenge\">2018 IndieWeb Challenge</a> completed!</li>\n<li>Demos of personal website breakthroughs</li>\n<li>Create or update your personal web site!</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-02-06-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": "1985284",
    "_source": "1",
    "_is_read": true
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2019-01-29 14:47-0800",
    "url": "http://tantek.com/2019/029/t1/talk-indieweb-bridging-open-web-social-media",
    "category": [
        "IndieWeb"
    ],
    "in-reply-to": [
        "https://jackjamieson.net/3262-2/"
    ],
    "content": {
        "text": "@jackjamieson awesome! I added your talk on bridging open web and social media to the #IndieWeb wiki events page: https://indieweb.org/Events#jackjamieson-2019-030\nFeel free to create its own wiki page.\n\nRemember to take photos of the group, ask folks to take photos of your talk!",
        "html": "<a class=\"h-cassis-username\" href=\"https://twitter.com/jackjamieson\">@jackjamieson</a> awesome! I added your talk on bridging open web and social media to the #<span class=\"p-category\">IndieWeb</span> wiki events page: <a href=\"https://indieweb.org/Events#jackjamieson-2019-030\">https://indieweb.org/Events#jackjamieson-2019-030</a><br />Feel free to create its own wiki page.<br /><br />Remember to take photos of the group, ask folks to take photos of your talk!"
    },
    "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://jackjamieson.net/3262-2/": {
            "type": "entry",
            "url": "https://jackjamieson.net/3262-2/",
            "name": "jackjamieson.net\u2019s post",
            "post-type": "article"
        }
    },
    "_id": "1983647",
    "_source": "1",
    "_is_read": true
}

Matthias Pfefferle notiz.blog/author/matthias-pfefferle/

Farewell Screenguide

{
    "type": "entry",
    "published": "2019-01-28T22:41:14+00:00",
    "url": "https://notiz.blog/2019/01/28/farewell-screenguide/",
    "featured": "https://notiz.blog/wp-content/uploads/2019/01/screenguides-900x675.jpg",
    "name": "Farewell Screenguide",
    "content": {
        "text": "\ufeff\u2026farewell \u201ePfefferles OpenWeb\u201c!\n\n\n\nDas SCREENGUIDE Magazin wurde \u201eaus wirtschaftlichen Gr\u00fcnden\u201c eingestellt und Heft 39 war somit die letzte Ausgabe \ud83d\ude22\n\n\n\n\n\nSchlechte Nachrichten. Leider m\u00fcssen wir die Screenguide aus wirtschaftlichen Gr\u00fcnden einstellen. Das Magazin tr\u00e4gt sich mit seinen Abo-Ums\u00e4tzen nicht mehr selbst. Das hei\u00dft, die aktuelle Ausgabe 39 ist damit auch die letzte Ausgabe.\u2014 SCREENGUIDE (@screengui_de) July 13, 2018\n\nDas ganze ist jetzt zwar schon eine ganze Weile her, ich hab aber trotzdem das Bed\u00fcrfnis noch einmal in Erinnerungen zu schwelgen\u2026\n\n\n\nVor 10 Jahren schrieb ich meinen ersten Print-Artikel f\u00fcr die erste Ausgabe des Magazins, damals noch Webstandards-Magazin. Seit dem war ich in jeder Ausgabe (naja, eine hab\u2018 ich ausgelassen) mit mindestens einem Artikel vertreten.\n\n\n\nZusammengefasst sind das:\n\n\n\n\n36 Kolumnen\n10 Jahre\n3 Artikel\n1 Titelthema\n1 Interview\n\nSemantic Surfing\n\n\n\nIn meinem ersten Artikel vom Februar 2009 hab ich versucht den Mehrwert von Microformats zu beschreiben. Die Webstandards-Redaktion hat mir den Einstieg ins Schreiben dabei sehr einfach gemacht. Ansgar Hein (Chefredakteur) und Sylvia Egger (Redakteurin) waren tolle, freundliche Antreiber und Lektoren, das Thema war absolute Komfort-Zone und mit Michael Jendrischik (Autor) hatte ich einen erfahrenen Sparringspartner.\n\n\n\nMichael Jendryschik schrieb \u00fcber RDFa und ich \u00fcber Microformats (Semantic Surfing) und da beide Themen sehr nah beieinander lagen, haben wir uns viel ausgetauscht. Das half mir zum Einen beim schreiben und zum Anderen hatten wir so die M\u00f6glichkeit den jeweils anderen Artikel zu referenzieren. Dadurch entstand eine Art \u201eprinted Hyperlinking\u201c!\n\n\n\nAnsgar Hein hat das Ergebnis in einer Folge des Technikw\u00fcrze Podcasts folgenderma\u00dfen beschrieben:\n\n\n\nTechnikw\u00fcrze 136: Ansgar Hein und David Maciejewski sprechen \u00fcber beide ArtikelAuch wenn er nicht gleich auf meinen Namen kam \ud83d\ude42\n\n\n\nDanke Sylvia, dass du mich damals angeschrieben hast!\n\n\n\nIndieWeb \u2013 Die Daten sind wir!\n\n\n\nEs freut mich immernoch sehr, dass das SCREENGUIDE Magazin im Allgemeinen, und Nicolai (Projektleiter) im Speziellen, der IndieWeb Idee so viel Platz einger\u00e4umt haben!\n\n\n\nDas IndieWeb war damals (2015) wie heute eher ein Nischen-Thema und trotzdem hat das Magazin eine Titel-Story daraus gemacht. Mit mehr als 7 Seiten war der Artikel auch mit Abstand der l\u00e4ngste den ich bisher f\u00fcr ein Print-Magazin geschrieben habe.\n\n\n\nKurz nach der Ver\u00f6ffentlichung kam \u00fcbrigens auch ein Schwester-Magazin auf mich zu, ob ich den Artikel nicht auf 2 Seiten zusammenfassen k\u00f6nne und so hat sogar das eher antiquierte PC-Magazin \u00fcber das IndieWeb berichtet \ud83d\ude42\n\n\n\nWebsemantics\n\n\n\nFast genau 8 Jahre nach dem ersten Artikel durfte ich 2017 noch einmal \u00fcber Websemantics schreiben. Im Gegensatz zu Semantic Surfing, wo es ausschlie\u00dflich um Microformats ging, gibt Websemantics eher einen groben \u00dcberblick, in dem aber auch Microformats ihren \u201eAuftritt\u201c hatten.\n\n\n\n\nH\u00e4tte ich das damals gewusst, dass mein erster und letzter Artikel das gleiche Thema behandeln, h\u00e4tte ich es nat\u00fcrlich in den Text einflie\u00dfen lassen \ud83d\ude42\n\n\n\nWebstandards W\u00fcrze / Pfefferles OpenWeb\n\n\n\nDank Sylvia Egger (und wahrscheinlich dem OpenWebPodcast) durfte ich seit 2009 die Kolumne Pfefferles OpenWeb schreiben, in der ich einmal im Quartal \u00fcber die Neuigkeiten im OpenWeb berichtete.\n\n\n\nDanke hier auch nochmal an Ansgar Hein, J\u00f6rg Morsbach (Redakteur) und Nicolai Schwarz, dass ich die Kolumne so lange schreiben durfte und das nahezu ohne jegliche Vorgaben oder Einschr\u00e4nkungen.\n\n\n\nIch habe die letzten 10 Jahre lang, jedes Quartal \u00fcber OpenID, OAuth, Microformats, IndieWeb, OpenWeb, W3C, Fediverse, OStatus, RDFa, HTML5, OpenGraph, Facebook, DSGVO, BrowserID, DataPortability, Open Social, Diaspora, DiSo, Microblogging, Websemantics, Twitter Cards, Schema.org, Microdata, Single-Sign-on, AMP, OEmbed, Ind.ie, Google, Twitter, Blogs, Ello, WhatsApp, RSS, Webmentions, Pingbacks, App.net, Synaptic Web, Online Identity, Persona, Mozilla, Open Stack und Portable Contacts berichtet.\n\n\n\nDas hei\u00dft, ich hab \u00fcber/durch/mit Pfefferles OpenWeb eine ganze Menge gelernt. Das schwierigste war das Schreiben an sich, dazu kam dann noch der Anspruch immer neue und vor allem aktuelle Themen zu behandeln.\n\n\n\nEs freut mich, dass ich damit auch nicht immer ganz falsch lag:\n\n\n\n\n\nhat eben ein Abo f\u00fcr das Webstandards Magazin abgeschlossen, um mehr von @pfefferle zu lesen! \ud83d\ude09 https://www.webstandards-magazin.de/\u2014 dickelippe (@dickelippe) November 25, 2009\n\n\n\nSchade, dass die letzte Kolumne von @pfefferle nur f\u00fcr K\u00e4ufer der @screengui_de zu haben ist. Sehr lesenswert! #indiephone\u2014 Christian Richter (@chRi____) July 29, 2015\n\n\n\nTolle Kolumne von @pfefferle in der neuen @screengui_de  #sg13-92\u2014 Matthias Gutjahr (@mattsches) March 15, 2012\n\n\n\nam besten gefallen im aktuellen @webstandardsmag @pfefferle Kolumne #wsm0911-86\u2014 Sylvia Egger (@sprungmarkers) March 29, 2011\n\n\n\n@pfefferle gerne \u2013 informativ und pointiert \u2013 so soll ne Kolumne sein\u2014 Sylvia Egger (@sprungmarkers) March 29, 2011\n\n\n\nfinde die Kolumne vom @pfefferle im  Webstandarts-Magazin super..\u2014 Christian (@weyandch) September 24, 2009\n\nDie Schreiberei hat mir jedenfalls eine Menge Spa\u00df gemacht und die Kolumne wird mir sehr fehlen!\n\n\n\nSollte jemand zuf\u00e4llig ein neues Zuhause f\u00fcr Pfefferles OpenWeb haben, kann er sich nat\u00fcrlich gerne bei mir melden!",
        "html": "<p><strong>\ufeff\u2026farewell <em>\u201ePfefferles OpenWeb\u201c</em>!</strong></p>\n\n\n\n<p>Das SCREENGUIDE Magazin wurde \u201eaus wirtschaftlichen Gr\u00fcnden\u201c eingestellt und Heft 39 war somit die letzte Ausgabe \ud83d\ude22</p>\n\n\n\n\n<blockquote>\n<p lang=\"de\" dir=\"ltr\" xml:lang=\"de\">Schlechte Nachrichten. Leider m\u00fcssen wir die Screenguide aus wirtschaftlichen Gr\u00fcnden einstellen. Das Magazin tr\u00e4gt sich mit seinen Abo-Ums\u00e4tzen nicht mehr selbst. Das hei\u00dft, die aktuelle Ausgabe 39 ist damit auch die letzte Ausgabe.</p>\u2014 SCREENGUIDE (@screengui_de) <a href=\"https://twitter.com/screengui_de/status/1017736191515463680?ref_src=twsrc%5Etfw\">July 13, 2018</a>\n</blockquote>\n<p>Das ganze ist jetzt zwar schon eine <a href=\"https://notiz.blog/2019/01/08/zwanzigachtzehn/\">ganze Weile her</a>, ich hab aber trotzdem das Bed\u00fcrfnis noch einmal in Erinnerungen zu schwelgen\u2026</p>\n\n\n\n<p>Vor 10 Jahren schrieb ich meinen <a href=\"https://notiz.blog/2009/03/27/webstandards-magazin-und-microformats/\">ersten Print-Artikel</a> f\u00fcr die erste Ausgabe des Magazins, damals noch <a href=\"https://notiz.blog/tag/webstandards-magazin/\">Webstandards-Magazin</a>. Seit dem war ich in jeder Ausgabe (naja, eine hab\u2018 ich ausgelassen) mit mindestens einem Artikel vertreten.</p>\n\n\n\n<p>Zusammengefasst sind das:<br /></p>\n\n\n\n<ul><li><a href=\"https://notiz.blog/tag/kolumne/\">36 Kolumnen</a></li>\n<li>10 Jahre</li>\n<li>3 Artikel</li>\n<li><a href=\"https://notiz.blog/2015/04/02/indieweb-die-daten-sind-wir/\">1 Titelthema</a></li>\n<li>1 Interview<br /></li>\n</ul><h2>Semantic Surfing</h2>\n\n\n\n<p>In meinem ersten Artikel vom Februar 2009 hab ich versucht den Mehrwert von Microformats zu beschreiben. Die Webstandards-Redaktion hat mir den Einstieg ins Schreiben dabei sehr einfach gemacht. Ansgar Hein (Chefredakteur) und Sylvia Egger (Redakteurin) waren tolle, freundliche Antreiber und Lektoren, das Thema war absolute Komfort-Zone und mit Michael Jendrischik (Autor) hatte ich einen erfahrenen Sparringspartner.</p>\n\n\n\n<img src=\"https://aperture-proxy.p3k.io/c4365a1562943145cdb388f6720c88518e30789f/68747470733a2f2f6e6f74697a2e626c6f672f77702d636f6e74656e742f75706c6f6164732f323031392f30312f7765627374616e64617264732d6d6167617a696e2d6d6963726f666f726d6174732d393030783637352e6a7067\" alt=\"\" /><p><a href=\"http://jendryschik.de/\">Michael Jendryschik</a> schrieb \u00fcber RDFa und ich \u00fcber Microformats (<em><a href=\"https://notiz.blog/2009/03/27/webstandards-magazin-und-microformats/\">Semantic Surfing</a></em>) und da beide Themen sehr nah beieinander lagen, haben wir uns viel ausgetauscht. Das half mir zum Einen beim schreiben und zum Anderen hatten wir so die M\u00f6glichkeit den jeweils anderen Artikel zu referenzieren. Dadurch entstand eine Art \u201eprinted Hyperlinking\u201c!</p>\n\n\n\n<p>Ansgar Hein hat das Ergebnis in einer Folge des <a href=\"http://technikwuerze.de/podcast/technikwuerze136/\">Technikw\u00fcrze Podcasts</a> folgenderma\u00dfen beschrieben:</p>\n\n\n\nTechnikw\u00fcrze 136: Ansgar Hein und David Maciejewski sprechen \u00fcber beide Artikel<p>Auch wenn er nicht gleich auf meinen Namen kam \ud83d\ude42</p>\n\n\n\n<p>Danke Sylvia, dass du mich damals angeschrieben hast!</p>\n\n\n\n<h2>IndieWeb \u2013 Die Daten sind wir!</h2>\n\n\n\n<img src=\"https://aperture-proxy.p3k.io/68e5f6e818d5071420dcd9f127ac355504d0908c/68747470733a2f2f6e6f74697a2e626c6f672f77702d636f6e74656e742f75706c6f6164732f323031352f30342f726973652d6f662d7468652d696e6469657765622d363030783530392e706e67\" alt=\"\" /><p>Es freut mich immernoch sehr, dass das <a href=\"https://abo.screengui.de/einzelhefte/screenguide-26.html\">SCREENGUIDE Magazin</a> im Allgemeinen, und <a href=\"http://nicolaischwarz.de/\">Nicolai</a> (Projektleiter) im Speziellen, der IndieWeb Idee so viel Platz einger\u00e4umt haben!</p>\n\n\n\n<p>Das IndieWeb war damals (<a href=\"https://notiz.blog/2015/04/02/indieweb-die-daten-sind-wir/\">2015</a>) wie heute eher ein Nischen-Thema und trotzdem hat das Magazin eine Titel-Story daraus gemacht. Mit mehr als 7 Seiten war der Artikel auch mit Abstand der l\u00e4ngste den ich bisher f\u00fcr ein Print-Magazin geschrieben habe.</p>\n\n\n\n<p>Kurz nach der Ver\u00f6ffentlichung kam \u00fcbrigens auch ein Schwester-Magazin auf mich zu, ob ich den Artikel nicht auf 2 Seiten zusammenfassen k\u00f6nne und so hat sogar das eher antiquierte PC-Magazin \u00fcber das IndieWeb berichtet \ud83d\ude42</p>\n\n\n\n<h2>Websemantics</h2>\n\n\n\n<p>Fast genau 8 Jahre nach dem ersten Artikel durfte ich 2017 noch einmal \u00fcber Websemantics schreiben. Im Gegensatz zu <em>Semantic Surfing</em>, wo es ausschlie\u00dflich um Microformats ging, gibt <em>Websemantics</em> eher einen groben \u00dcberblick, in dem aber auch Microformats ihren \u201eAuftritt\u201c hatten.<br /></p>\n\n\n\n<p>H\u00e4tte ich das damals gewusst, dass mein erster und letzter Artikel das gleiche Thema behandeln, h\u00e4tte ich es nat\u00fcrlich in den Text einflie\u00dfen lassen \ud83d\ude42</p>\n\n\n\n<h2>Webstandards W\u00fcrze / Pfefferles OpenWeb</h2>\n\n\n\n<p>Dank <a href=\"https://twitter.com/sprungmarkers\">Sylvia Egger</a> (und wahrscheinlich dem <a href=\"http://openwebpodcast.de\">OpenWebPodcast</a>) durfte ich seit 2009 die Kolumne <strong><em>Pfefferles OpenWeb</em></strong> schreiben, in der ich einmal im Quartal \u00fcber die Neuigkeiten im <a href=\"https://notiz.blog/tag/openweb/\">OpenWeb</a> berichtete.</p>\n\n\n\n<p>Danke hier auch nochmal an Ansgar Hein, J\u00f6rg Morsbach (Redakteur) und <a href=\"http://nicolaischwarz.de\">Nicolai Schwarz</a>, dass ich die Kolumne so lange schreiben durfte und das nahezu ohne jegliche Vorgaben oder Einschr\u00e4nkungen.</p>\n\n\n\n<img src=\"https://aperture-proxy.p3k.io/bd34c4cfc1d870119b3d858fa41f3104354ad8b0/68747470733a2f2f6e6f74697a2e626c6f672f77702d636f6e74656e742f75706c6f6164732f323031382f30312f73637265656e67756964652d6b6f6c756d6e652d393030783630302e6a7067\" alt=\"\" /><p>Ich habe die letzten 10 Jahre lang, jedes Quartal \u00fcber OpenID, OAuth, Microformats, IndieWeb, OpenWeb, W3C, Fediverse, OStatus, RDFa, HTML5, OpenGraph, Facebook, DSGVO, BrowserID, DataPortability, Open Social, Diaspora, DiSo, Microblogging, Websemantics, Twitter Cards, Schema.org, Microdata, Single-Sign-on, AMP, OEmbed, Ind.ie, Google, Twitter, Blogs, Ello, WhatsApp, RSS, Webmentions, Pingbacks, App.net, Synaptic Web, Online Identity, Persona, Mozilla, Open Stack und Portable Contacts berichtet.</p>\n\n\n\n<p>Das hei\u00dft, ich hab \u00fcber/durch/mit <strong><em>Pfefferles OpenWeb</em></strong> eine ganze Menge gelernt. Das schwierigste war das Schreiben an sich, dazu kam dann noch der Anspruch immer neue und vor allem aktuelle Themen zu behandeln.</p>\n\n\n\n<p>Es freut mich, dass ich damit auch nicht immer ganz falsch lag:</p>\n\n\n\n\n<blockquote>\n<p lang=\"de\" dir=\"ltr\" xml:lang=\"de\">hat eben ein Abo f\u00fcr das Webstandards Magazin abgeschlossen, um mehr von <a href=\"https://twitter.com/pfefferle?ref_src=twsrc%5Etfw\">@pfefferle</a> zu lesen! \ud83d\ude09 https://www.webstandards-magazin.de/</p>\u2014 dickelippe (@dickelippe) <a href=\"https://twitter.com/dickelippe/status/6064875222?ref_src=twsrc%5Etfw\">November 25, 2009</a>\n</blockquote>\n\n<blockquote>\n<p lang=\"de\" dir=\"ltr\" xml:lang=\"de\">Schade, dass die letzte Kolumne von <a href=\"https://twitter.com/pfefferle?ref_src=twsrc%5Etfw\">@pfefferle</a> nur f\u00fcr K\u00e4ufer der <a href=\"https://twitter.com/screengui_de?ref_src=twsrc%5Etfw\">@screengui_de</a> zu haben ist. Sehr lesenswert! <a href=\"https://twitter.com/hashtag/indiephone?src=hash&amp;ref_src=twsrc%5Etfw\">#indiephone</a></p>\u2014 Christian Richter (@chRi____) <a href=\"https://twitter.com/chRi____/status/626428856652722176?ref_src=twsrc%5Etfw\">July 29, 2015</a>\n</blockquote>\n\n<blockquote>\n<p lang=\"de\" dir=\"ltr\" xml:lang=\"de\">Tolle Kolumne von <a href=\"https://twitter.com/pfefferle?ref_src=twsrc%5Etfw\">@pfefferle</a> in der neuen <a href=\"https://twitter.com/screengui_de?ref_src=twsrc%5Etfw\">@screengui_de</a>  <a href=\"https://twitter.com/hashtag/sg13?src=hash&amp;ref_src=twsrc%5Etfw\">#sg13</a>-92</p>\u2014 Matthias Gutjahr (@mattsches) <a href=\"https://twitter.com/mattsches/status/180378154911793153?ref_src=twsrc%5Etfw\">March 15, 2012</a>\n</blockquote>\n\n<blockquote>\n<p lang=\"de\" dir=\"ltr\" xml:lang=\"de\">am besten gefallen im aktuellen <a href=\"https://twitter.com/webstandardsmag?ref_src=twsrc%5Etfw\">@webstandardsmag</a> <a href=\"https://twitter.com/pfefferle?ref_src=twsrc%5Etfw\">@pfefferle</a> Kolumne <a href=\"https://twitter.com/hashtag/wsm0911?src=hash&amp;ref_src=twsrc%5Etfw\">#wsm0911</a>-86</p>\u2014 Sylvia Egger (@sprungmarkers) <a href=\"https://twitter.com/sprungmarkers/status/52636198895751168?ref_src=twsrc%5Etfw\">March 29, 2011</a>\n</blockquote>\n\n<blockquote>\n<p lang=\"de\" dir=\"ltr\" xml:lang=\"de\"><a href=\"https://twitter.com/pfefferle?ref_src=twsrc%5Etfw\">@pfefferle</a> gerne \u2013 informativ und pointiert \u2013 so soll ne Kolumne sein</p>\u2014 Sylvia Egger (@sprungmarkers) <a href=\"https://twitter.com/sprungmarkers/status/52707288112300032?ref_src=twsrc%5Etfw\">March 29, 2011</a>\n</blockquote>\n\n<blockquote>\n<p lang=\"de\" dir=\"ltr\" xml:lang=\"de\">finde die Kolumne vom <a href=\"https://twitter.com/pfefferle?ref_src=twsrc%5Etfw\">@pfefferle</a> im  Webstandarts-Magazin super..</p>\u2014 Christian (@weyandch) <a href=\"https://twitter.com/weyandch/status/4341912336?ref_src=twsrc%5Etfw\">September 24, 2009</a>\n</blockquote>\n<p>Die Schreiberei hat mir jedenfalls eine Menge Spa\u00df gemacht und die Kolumne wird mir sehr fehlen!</p>\n\n\n\n<p>Sollte jemand zuf\u00e4llig ein neues Zuhause f\u00fcr <strong><em>Pfefferles OpenWeb</em></strong> haben, kann er sich nat\u00fcrlich gerne bei mir <a href=\"https://notiz.blog/kontakt/\">melden</a>!</p>"
    },
    "author": {
        "type": "card",
        "name": "Matthias Pfefferle",
        "url": "https://notiz.blog/author/matthias-pfefferle/",
        "photo": "https://secure.gravatar.com/avatar/75512bb584bbceae57dfc503692b16b2?s=40&d=https://notiz.blog/wp-content/plugins/semantic-linkbacks/img/mm.jpg&r=g"
    },
    "post-type": "article",
    "_id": "1971100",
    "_source": "206",
    "_is_read": true
}

Vika fireburn.ru

{
    "type": "entry",
    "published": "2019-01-29T01:53:22+03:00",
    "url": "https://fireburn.ru/note/1548716002",
    "category": [
        "wtf",
        "homelab",
        "indieweb",
        "python",
        "server",
        "raspberrypi",
        "flask",
        "None://fireburn.ru/tags/wtf",
        "None://fireburn.ru/tags/homelab",
        "None://fireburn.ru/tags/indieweb",
        "None://fireburn.ru/tags/python",
        "None://fireburn.ru/tags/server",
        "None://fireburn.ru/tags/raspberrypi",
        "None://fireburn.ru/tags/flask"
    ],
    "syndication": [
        "https://twitter.com/kisik21/status/1090020048335458305"
    ],
    "content": {
        "text": "My website daemon ate almost half of the Raspberry Pi RAM... #wtf #homelab #indieweb #python #server #raspberrypi #flask",
        "html": "<p>My website daemon ate almost half of the Raspberry Pi RAM... <a class=\"u-category\">#wtf</a> <a class=\"u-category\">#homelab</a> <a class=\"u-category\">#indieweb</a> <a class=\"u-category\">#python</a> <a class=\"u-category\">#server</a> <a class=\"u-category\">#raspberrypi</a> <a class=\"u-category\">#flask</a></p>"
    },
    "author": {
        "type": "card",
        "name": "Vika",
        "url": "https://fireburn.ru/",
        "photo": "https://aperture-proxy.p3k.io/3baa9a034ae34d783c6de676c0304b7640673c03/68747470733a2f2f666972656275726e2e72752f617661746172732f76696b612e706e67"
    },
    "post-type": "note",
    "_id": "1969633",
    "_source": "1371",
    "_is_read": true
}

Malcolm Blaney unicyclic.com/mal

Changing my reading habits

{
    "type": "entry",
    "published": "2019-01-27T13:12:35+10:00",
    "url": "https://unicyclic.com/mal/2019-01-27-Changing_my_reading_habits",
    "category": [
        "https://news.indieweb.org/en"
    ],
    "photo": [
        "https://aperture-proxy.p3k.io/cffba028b2f76967b226c4f296d179711caa4be4/68747470733a2f2f756e696379636c69632e636f6d2f6d616c2f7075626c69632f6368616e6e656c5f746f6f6c7469702e706e67"
    ],
    "syndication": [
        "https://twitter.com/malcolmblaney/status/1089360559819108357"
    ],
    "name": "Changing my reading habits",
    "content": {
        "text": "It's been over a month since I added channels to my reader, but I didn't use them initially. I've added some new features though which have changed my reading habits completely!\n\n\nWhat I really wanted was to split silo feeds into different channels based on author. Without this I would mostly be viewing the silos channel since that gets such a large number of posts. To do that, I've added hovercards to authors so I can set their channel while reading. You can see from the screenshot that @letsencrypt has been added to the tech channel, instead of it's default in the silos channel for the rest of the twitter feed.\n\n\nI've gone through my silo authors and added them to tech, news or friends and this simple breakdown has been great so far. The other thing I've added is unread status, it doesn't have to show a count to highlight that there are unread items, which is configurable per channel. I like that it's quite simple, when you change channels the unread count resets, it doesn't save unread status per item.\n\n\nNow that the underlying structure is in place the next step is to finish adding Microsub support.",
        "html": "It's been <a href=\"https://unicyclic.com/mal/2018-12-16-Some_reader_progress_channels_are_now_working_I\">over a month</a> since I added channels to my reader, but I didn't use them initially. I've added some new features though which have changed my reading habits completely!<br /><br />\nWhat I really wanted was to split silo feeds into different channels based on author. Without this I would mostly be viewing the silos channel since that gets such a large number of posts. To do that, I've added hovercards to authors so I can set their channel while reading. You can see from the screenshot that <a href=\"https://twitter.com/letsencrypt\">@letsencrypt</a> has been added to the tech channel, instead of it's default in the silos channel for the rest of the twitter feed.<br /><br />\nI've gone through my silo authors and added them to tech, news or friends and this simple breakdown has been great so far. The other thing I've added is unread status, it doesn't have to show a count to highlight that there are unread items, which is configurable per channel. I like that it's quite simple, when you change channels the unread count resets, it doesn't save unread status per item.<br /><br />\nNow that the underlying structure is in place the next step is to finish adding Microsub support.<a href=\"https://brid.gy/publish/twitter\"></a><a href=\"https://twitter.com/malcolmblaney/status/1089360559819108357\" class=\"u-syndication\"></a>"
    },
    "author": {
        "type": "card",
        "name": "Malcolm Blaney",
        "url": "https://unicyclic.com/mal",
        "photo": "https://aperture-proxy.p3k.io/4f46272c0027449ced0d7cf8de31ea1bec37210e/68747470733a2f2f756e696379636c69632e636f6d2f6d616c2f7075626c69632f70726f66696c655f736d616c6c5f7468756d622e706e67"
    },
    "post-type": "photo",
    "_id": "1949174",
    "_source": "243",
    "_is_read": true
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2019-01-25 17:33-0800",
    "rsvp": "yes",
    "url": "http://tantek.com/2019/025/t2/grand-public-domain-community-microformats-indieweb",
    "category": [
        "microformats.org",
        "indieweb.org",
        "PublicDomainDay"
    ],
    "in-reply-to": [
        "https://blog.archive.org/2018/12/05/join-us-for-a-grand-re-opening-of-the-public-domain-january-25-2019/"
    ],
    "content": {
        "text": "attending A Grand Re-Opening of the Public Domain @InternetArchive! Great talks by @lessig @han @brewster_kahle @doctorow & more! \n\nProud of public domain community work:\n#microformats.org ^1 \n#indieweb.org since founding^2 \n\n#PublicDomainDay\n\n^1 Since 2007-12-29: microformats.org/2007/12/29/making-open-standards-as-open-as-possible\n^2 Since founding in 2011! https://indieweb.org/IndieWeb:Copyrights",
        "html": "attending A Grand Re-Opening of the Public Domain <a class=\"h-cassis-username\" href=\"https://twitter.com/InternetArchive\">@InternetArchive</a>! Great talks by <a class=\"h-cassis-username\" href=\"https://twitter.com/lessig\">@lessig</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/han\">@han</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/brewster_kahle\">@brewster_kahle</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/doctorow\">@doctorow</a> &amp; more! <br /><br />Proud of public domain community work:<br />#<span class=\"p-category\"><a href=\"http://microformats.org\">microformats.org</a></span> ^1 <br />#<span class=\"p-category\"><a href=\"http://indieweb.org\">indieweb.org</a></span> since founding^2 <br /><br />#<span class=\"p-category\">PublicDomainDay</span><br /><br />^1 Since 2007-12-29: <a href=\"http://microformats.org/2007/12/29/making-open-standards-as-open-as-possible\">microformats.org/2007/12/29/making-open-standards-as-open-as-possible</a><br />^2 Since founding in 2011! <a href=\"https://indieweb.org/IndieWeb:Copyrights\">https://indieweb.org/IndieWeb:Copyrights</a>"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "rsvp",
    "refs": {
        "https://blog.archive.org/2018/12/05/join-us-for-a-grand-re-opening-of-the-public-domain-january-25-2019/": {
            "type": "entry",
            "url": "https://blog.archive.org/2018/12/05/join-us-for-a-grand-re-opening-of-the-public-domain-january-25-2019/",
            "name": "blog.archive.org\u2019s post",
            "post-type": "article"
        }
    },
    "_id": "1938094",
    "_source": "1",
    "_is_read": true
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2019-01-25 11:23-0800",
    "url": "http://tantek.com/2019/025/t1/microformats-worth-valid-microformats",
    "category": [
        "microformats2",
        "indieweb",
        "webmentions"
    ],
    "in-reply-to": [
        "https://twitter.com/emilylewis/status/1086279710298931211"
    ],
    "content": {
        "text": "@tw2113 @microformats still worth it (search engines still support), and valid!\n\nFor new sites, also include #microformats2 markup; it\u2019s even more useful for #indieweb support, #webmentions etc.\n\n@emilylewis perhaps time for a 2nd ed. with microformats2? Happy to tech edit :0\n\nSee also: microformats.org/wiki/faq#When_should_I_use_microformats2_or_microformats1",
        "html": "<a class=\"h-cassis-username\" href=\"https://twitter.com/tw2113\">@tw2113</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/microformats\">@microformats</a> still worth it (search engines still support), and valid!<br /><br />For new sites, also include #<span class=\"p-category\">microformats2</span> markup; it\u2019s even more useful for #<span class=\"p-category\">indieweb</span> support, #<span class=\"p-category\">webmentions</span> etc.<br /><br /><a class=\"h-cassis-username\" href=\"https://twitter.com/emilylewis\">@emilylewis</a> perhaps time for a 2nd ed. with microformats2? Happy to tech edit :0<br /><br />See also: <a href=\"http://microformats.org/wiki/faq#When_should_I_use_microformats2_or_microformats1\">microformats.org/wiki/faq#When_should_I_use_microformats2_or_microformats1</a>"
    },
    "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/emilylewis/status/1086279710298931211": {
            "type": "entry",
            "url": "https://twitter.com/emilylewis/status/1086279710298931211",
            "name": "@emilylewis\u2019s tweet",
            "post-type": "article"
        }
    },
    "_id": "1934117",
    "_source": "1",
    "_is_read": true
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2019-01-23 17:59-0800",
    "rsvp": "yes",
    "url": "http://tantek.com/2019/023/t1/one-year-ago-w3c-indieauth-websub",
    "category": [
        "SF",
        "IndieWeb",
        "IndieAuth",
        "W3C",
        "WebSub",
        "pubsubhubbub"
    ],
    "in-reply-to": [
        "http://tantek.com/2019/023/e1/homebrew-website-club-sf"
    ],
    "content": {
        "text": "hosting Homebrew Website Club #SF @MozSF tonight!\n\nOne year ago today: #IndieWeb building blocks published @W3C:\n* #IndieAuth #W3C Note: https://www.w3.org/TR/2018/NOTE-indieauth-20180123/\n* #WebSub W3C Recommendation! https://twitter.com/t/status/956354767596539904 (formerly @pubsubhubbub #pubsubhubbub)",
        "html": "hosting Homebrew Website Club #<span class=\"p-category\">SF</span> <a class=\"h-cassis-username\" href=\"https://twitter.com/MozSF\">@MozSF</a> tonight!<br /><br />One year ago today: #<span class=\"p-category\">IndieWeb</span> building blocks published <a class=\"h-cassis-username\" href=\"https://twitter.com/W3C\">@W3C</a>:<br />* #<span class=\"p-category\">IndieAuth</span> #<span class=\"p-category\">W3C</span> Note: <a href=\"https://www.w3.org/TR/2018/NOTE-indieauth-20180123/\">https://www.w3.org/TR/2018/NOTE-indieauth-20180123/</a><br />* #<span class=\"p-category\">WebSub</span> W3C Recommendation! <a href=\"https://twitter.com/t/status/956354767596539904\">https://twitter.com/t/status/956354767596539904</a> (formerly <a class=\"h-cassis-username\" href=\"https://twitter.com/pubsubhubbub\">@pubsubhubbub</a> #<span class=\"p-category\">pubsubhubbub</span>)"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "rsvp",
    "refs": {
        "http://tantek.com/2019/023/e1/homebrew-website-club-sf": {
            "type": "entry",
            "url": "http://tantek.com/2019/023/e1/homebrew-website-club-sf",
            "name": "Tantek\u2019s event",
            "post-type": "article"
        }
    },
    "_id": "1913796",
    "_source": "1",
    "_is_read": true
}

Aaron Parecki aaronparecki.com

{
    "type": "entry",
    "published": "2019-01-23T18:57:26-08:00",
    "url": "https://aaronparecki.com/2019/01/23/23/",
    "category": [
        "IndieAuth",
        "indieauth"
    ],
    "syndication": [
        "https://twitter.com/aaronpk/status/1088269523864567808"
    ],
    "content": {
        "text": "It's already been a year since #IndieAuth was published as a @W3C Note! Support from new services and some new plugins as well! https://aaronparecki.com/2019/01/23/22/indieauth",
        "html": "It's already been a year since <a href=\"https://aaronparecki.com/tag/indieauth\">#<span class=\"p-category\">IndieAuth</span></a> was published as a <a href=\"https://twitter.com/W3C\">@W3C</a> Note! Support from new services and some new plugins as well! <a href=\"https://aaronparecki.com/2019/01/23/22/indieauth\"><span>https://</span>aaronparecki.com/2019/01/23/22/indieauth</a>"
    },
    "author": {
        "type": "card",
        "name": "Aaron Parecki",
        "url": "https://aaronparecki.com/",
        "photo": "https://aperture-media.p3k.io/aaronparecki.com/2b8e1668dcd9cfa6a170b3724df740695f73a15c2a825962fd0a0967ec11ecdc.jpg"
    },
    "post-type": "note",
    "_id": "1912740",
    "_source": "16",
    "_is_read": true
}

Aaron Parecki aaronparecki.com

IndieAuth: One Year Later

{
    "type": "entry",
    "published": "2019-01-23T18:51:01-08:00",
    "url": "https://aaronparecki.com/2019/01/23/22/indieauth",
    "featured": "https://aaronparecki.com/2019/01/23/22/indieauth-featured.jpg",
    "category": [
        "indieauth",
        "indieweb",
        "w3c"
    ],
    "syndication": [
        "https://news.indieweb.org/en/aaronparecki.com/2019/01/23/22/indieauth"
    ],
    "name": "IndieAuth: One Year Later",
    "content": {
        "text": "It's already been a year since IndieAuth was published as a W3C Note! A lot has happened in that time! There's been several new plugins and services launch support for IndieAuth, and it's even made appearances at several events around the world!\n\n\nMicro.blog added native support for IndieAuth, so your hosted micro.blog account is now also an IndieAuth provider\n  \nDobrado launched native support for IndieAuth\n  The\u00a0IndieAuth Plugin for Drupal\u00a0launched in the beginning of the year, and has had several releases since then\n  The\u00a0IndieAuth Plugin for Grav\u00a0adds support to your Grav site by delegating to indieauth.com\n  The\u00a0IndieAuth Plugin for WordPress\u00a0had a major rewrite and supports IndieAuth natively now\nI presented IndieAuth at the\u00a0W3C Workshop on Strong Authentication & Identity in December, and even published a video of the talk\u00a0afterwards!\n\nphoto by Karen MyersAt API Days Global, oauth.io presented a session including IndieAuth.\n\nJosh Hawxwell gave a talk at NottsJS called Indie What?\u00a0where he covered several IndieWeb building blocks including IndieAuth.\n\nphoto by @NottsJSIn July, I wrote a blog post called OAuth for the Open Web, where I detailed the technical solutions IndieAuth provides on top of OAuth to enable it to work in a more open and less corporate environment.\nIn October, I published Dweb: Identity for the Decentralized Web with IndieAuth on the Mozilla Hacks Blog.\nSo here's to a productive year for IndieAuth in 2018! Looking forward to seeing what new developments come up in 2019!",
        "html": "<p>\n  It's already been a year since <a href=\"https://indieauth.net\">IndieAuth</a> was published as a <a href=\"https://www.w3.org/TR/indieauth/\">W3C Note</a>! A lot has happened in that time! There's been several new plugins and services launch support for IndieAuth, and it's even made appearances at several events around the world!\n</p>\n\n<img src=\"https://aperture-media.p3k.io/aaronparecki.com/2c71eeae36192e89d05a7359fb2bc0bbf09f6201a9df5ea585d009d80bb11398.jpg\" alt=\"\" class=\"u-featured\" /><ul><li>Micro.blog <a href=\"http://manton.micro.blog/2018/07/02/indieauth-for-microblog.html\">added native support for IndieAuth</a>, so your hosted micro.blog account is now also an IndieAuth provider</li>\n  <li>\n<a href=\"https://dobrado.net/documentation\">Dobrado</a> launched native support for IndieAuth</li>\n  <li>The\u00a0<a href=\"https://www.drupal.org/project/indieweb\">IndieAuth Plugin for Drupal</a>\u00a0launched in the beginning of the year, and has had several releases since then</li>\n  <li>The\u00a0<a href=\"https://github.com/metbril/grav-plugin-indieauth\">IndieAuth Plugin for Grav</a>\u00a0adds support to your Grav site by delegating to indieauth.com</li>\n  <li>The\u00a0<a href=\"https://wordpress.org/plugins/indieauth/\">IndieAuth Plugin for WordPress</a>\u00a0had a <a href=\"https://david.shanske.com/2018/04/07/indieauth-for-wordpress/\">major rewrite</a> and supports IndieAuth natively now</li>\n</ul><p>I presented IndieAuth at the\u00a0<a href=\"https://indieweb.org/events/2018-12-10-w3c-workshop-authentication-identity\">W3C Workshop on Strong Authentication &amp; Identity</a> in December, and even published a <a href=\"https://www.youtube.com/watch?v=EeCNlB7v08I\">video of the talk</a>\u00a0afterwards!</p>\n\n<img src=\"https://aperture-media.p3k.io/aaronparecki.com/9eea0ab37b3bad20b45a24258d71037b3f364f00ae0f26af92852ae792d263be.jpg\" alt=\"\" /><a href=\"https://twitter.com/ConnectorKaren/status/1072224287744974848\">photo by Karen Myers</a><p>At API Days Global, oauth.io <a href=\"https://twitter.com/OAuth_io/status/1023746803395514368\">presented a session</a> including IndieAuth.</p>\n\n<p>Josh Hawxwell gave a talk at NottsJS called <a href=\"https://www.meetup.com/NottsJS/events/qhnpfqyzcblb/\">Indie What?</a>\u00a0where he covered several IndieWeb building blocks including IndieAuth.</p>\n\n<img src=\"https://aperture-media.p3k.io/aaronparecki.com/34c3236f9f507c3916ce6f6ee63669d44ac7d2d8fad3803dda8da1182ccdc15f.jpg\" alt=\"\" /><a href=\"https://twitter.com/nottsjs/status/1082709269873594368\">photo by @NottsJS</a><p>In July, I wrote a blog post called <a href=\"https://aaronparecki.com/2018/07/07/7/oauth-for-the-open-web\">OAuth for the Open Web</a>, where I detailed the technical solutions IndieAuth provides on top of OAuth to enable it to work in a more open and less corporate environment.</p>\n<p>In October, I published <a href=\"https://hacks.mozilla.org/2018/10/dweb-identity-for-the-decentralized-web-with-indieauth/\">Dweb: Identity for the Decentralized Web with IndieAuth</a> on the Mozilla Hacks Blog.</p>\n<p>So here's to a productive year for IndieAuth in 2018! Looking forward to seeing what new developments come up in 2019!</p>"
    },
    "author": {
        "type": "card",
        "name": "Aaron Parecki",
        "url": "https://aaronparecki.com/",
        "photo": "https://aperture-media.p3k.io/aaronparecki.com/2b8e1668dcd9cfa6a170b3724df740695f73a15c2a825962fd0a0967ec11ecdc.jpg"
    },
    "post-type": "article",
    "_id": "1912684",
    "_source": "16",
    "_is_read": true
}