{
"type": "entry",
"published": "2020-04-16T15:16:45.83134-07:00",
"url": "https://v2.jacky.wtf/post/c688adb8-4971-482c-a542-ff0c431f4e85",
"content": {
"text": "This is more-or-less what the IndieWeb is about but with HTML instead of Atom/RSS https://fosstodon.org/@alexbuzzbee/104010481623432265",
"html": "<p>This is more-or-less what the IndieWeb is about but with HTML instead of Atom/RSS <a href=\"mailto:https://fosstodon.org/@alexbuzzbee/104010481623432265\">https://fosstodon.org/@alexbuzzbee/104010481623432265</a></p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "note",
"_id": "10814614",
"_source": "1886",
"_is_read": true
}
{
"type": "entry",
"published": "2020-04-15T19:09:49.635+02:00",
"url": "https://www.jvt.me/mf2/2020/04/1w57q/",
"in-reply-to": [
"https://twitter.com/paulienuh/status/1250405998432567296"
],
"content": {
"text": "Webmentions are great! They're how I handle all my interactions with my site i.e. https://www.jvt.me/posts/2020/01/11/homebrew-website-club-nottingham-url/ under Interactions with this post and there's great support for WordPress and many static sites, among others!",
"html": "<p>Webmentions are great! They're how I handle all my interactions with my site i.e. <a href=\"https://www.jvt.me/posts/2020/01/11/homebrew-website-club-nottingham-url/\">https://www.jvt.me/posts/2020/01/11/homebrew-website-club-nottingham-url/</a> under <code>Interactions with this post</code> and there's great support for WordPress and many static sites, among others!</p>"
},
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "reply",
"_id": "10772732",
"_source": "2169",
"_is_read": true
}
{
"type": "entry",
"published": "2020-04-14T07:43:00+01:00",
"url": "https://www.jvt.me/mf2/2020/04/l04ka/",
"category": [
"homebrew-website-club"
],
"content": {
"text": "It's #HomebrewWebsiteClub Nottingham tomorrow, which again will only be available for Nottingham folks - apologies in advance! The Zoom link will be available on the Tech Nottingham slack before the event https://events.indieweb.org/2020/04/online-homebrew-website-club-nottingham-h2HHF0o7NPtg",
"html": "<p>It's <a href=\"https://www.jvt.me/tags/homebrew-website-club/\">#HomebrewWebsiteClub</a> Nottingham tomorrow, which again will only be available for Nottingham folks - apologies in advance! The Zoom link will be available on the Tech Nottingham slack before the event <a href=\"https://events.indieweb.org/2020/04/online-homebrew-website-club-nottingham-h2HHF0o7NPtg\">https://events.indieweb.org/2020/04/online-homebrew-website-club-nottingham-h2HHF0o7NPtg</a></p>"
},
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "note",
"_id": "10726682",
"_source": "2169",
"_is_read": true
}
{
"type": "entry",
"published": "2020-04-13T23:29:27.142+02:00",
"url": "https://www.jvt.me/mf2/2020/04/srktw/",
"category": [
"www.jvt.me",
"micropub"
],
"content": {
"text": "Woo! Got #Micropub edit functionality working \ud83d\ude4c https://gitlab.com/jamietanna/jvt.me/-/commit/fda688f955c351000095a7e5c8ee294513afad6b is my first update through the API. Next will be getting my syndication links auto updated once syndication is reported as successful, but not one to do tonight",
"html": "<p>Woo! Got <a href=\"https://www.jvt.me/tags/micropub/\">#Micropub</a> edit functionality working \ud83d\ude4c <a href=\"https://gitlab.com/jamietanna/jvt.me/-/commit/fda688f955c351000095a7e5c8ee294513afad6b\">https://gitlab.com/jamietanna/jvt.me/-/commit/fda688f955c351000095a7e5c8ee294513afad6b</a> is my first update through the API. Next will be getting my syndication links auto updated once syndication is reported as successful, but not one to do tonight</p>"
},
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "note",
"_id": "10716336",
"_source": "2169",
"_is_read": true
}
{
"type": "entry",
"published": "2020-04-13T12:16:58+0000",
"url": "https://seblog.nl/2020/04/13/3/private-commenting-systems",
"category": [
"indieweb"
],
"syndication": [
"https://twitter.com/sebandeweg/status/1249674051880210435",
"https://news.indieweb.org/en/seblog.nl/2020/04/13/3/private-commenting-systems"
],
"name": "On Private Commenting Systems",
"content": {
"text": "Jan-Lukas wrote about an article by Matt from Write.as called Towards a Commenting System. The article describes a commenting system with two flavour: private and public. For private comments, an e-mail to the author is used; for public comments, one is prompted to publish the comment on their own space first and then notify the original post. It feels very IndieWeb friendly.\nThen, Jan-Lukas points out his own site already does this with webmention (as does mine), and that he also has a contact form, which people could use to reply private (at the time of writing I have no contact form).\nI like the idea of private comments taking another route than public comments. Just having a contact page is not the same though: to complete the idea you can link it with a call-to-action underneath your posts. Let\u2019s not have illusions here: most people will probably not read my posts on my site but in their reader or some other syndicated copy. But, it would give a nice UX for those on my site.\nIt also reminds me of how stories on Instagram work. There is a text box underneath it, which the user can tab to type a message. This message is then sent as a direct message to the creator of the story, and not visible to anyone but the creator and the commenter. It seems to work in that context: I do reply to friends in that way sometimes, because it feels very personal.\nAnother point is that this keeps private comments easier to implement for some and actually possible for those with static generated sites. My site has a way for visitors to log in, and I can build some form of private comments in that way. It is, however, way more work to build and maintain a site that does this, and not everyone is willing to do so. Doing private comments via a different channel makes it easier to have them.\nThe flip-side is that private comments cannot be shared among a group in this way. If you open a post to a certain circle of friends on, say, Facebook, all those friends can comment and also comment on each other\u2019s comments. This kind of interaction is very hard to do, though, if you don\u2019t have the luxury of a central service that guards access to all the posts \u2014 like Facebook does.\nThe conversation is also more likely to be ephemeral, for there are only two readers, both responsible for keeping their copies, with no help of, say, the Internet Archive.\nI remember a moment at IndieWebCamp Brighton when a session about private posts was about to start. Jeremy Keith walked out of the room while making a comment that he didn\u2019t see private pages as something the Web needed. This does not mean I can\u2019t have them, but it did make me think about why I want them and what they would mean to the Web and the world.\nBy putting the private comments on a separate channel, you are also removing them from the Web. This makes the Web a place for open and public conversations again. (Again: one could argue that thing on the \u2018Private Web\u2019 are not on the Web either.) The last few months I\u2019ve been reading more blogs and I must say I really enjoy that open Web. \nThe separation of private comments creates a clearer boundary between the open and the private, and maybe that\u2019s a good thing. It makes an easier question: it\u2019s harder to answer \u201cwhich people should be able to read this post?\u201d, than it is to answer \u201cdoes this concern only me and the author, or could there possibly be someone out there who\u2019s interested?\u201d.\nNo real plans for removal yet, but I keep being torn about private posts.",
"html": "<p>Jan-Lukas <a href=\"https://jlelse.blog/links/2020/04/remark-as/\">wrote about</a> an article by Matt from Write.as called <em><a href=\"https://write.as/matt/towards-a-commenting-system\">Towards a Commenting System</a></em>. The article describes a commenting system with two flavour: private and public. For private comments, an e-mail to the author is used; for public comments, one is prompted to publish the comment on their own space first and then notify the original post. It feels very IndieWeb friendly.</p>\n<p>Then, Jan-Lukas points out his own site already does this with webmention (as does mine), and that he also has a contact form, which people could use to reply private (at the time of writing I have no contact form).</p>\n<p>I like the idea of private comments taking another route than public comments. Just having a contact page is not the same though: to complete the idea you can link it with a call-to-action underneath your posts. Let\u2019s not have illusions here: most people will probably not read my posts on my site but in their reader or some other syndicated copy. But, it would give a nice UX for those on my site.</p>\n<p>It also reminds me of how stories on Instagram work. There is a text box underneath it, which the user can tab to type a message. This message is then sent as a direct message to the creator of the story, and not visible to anyone but the creator and the commenter. It seems to work in that context: I do reply to friends in that way sometimes, because it feels very personal.</p>\n<p>Another point is that this keeps private comments easier to implement for some and actually possible for those with <a href=\"https://indieweb.org/static_site_generator\">static generated sites</a>. My site has a way for visitors to log in, and I can build some form of private comments in that way. It is, however, way more work to build and maintain a site that does this, and not everyone is willing to do so. Doing private comments via a different channel makes it easier to have them.</p>\n<p>The flip-side is that private comments cannot be shared among a group in this way. If you open a post to a certain circle of friends on, say, Facebook, all those friends can comment and also comment on each other\u2019s comments. This kind of interaction is very hard to do, though, if you don\u2019t have the luxury of a central service that guards access to all the posts \u2014 like Facebook does.</p>\n<p>The conversation is also more likely to be ephemeral, for there are only two readers, both responsible for keeping their copies, with no help of, say, the Internet Archive.</p>\n<p>I remember a moment at <a href=\"https://indieweb.org/2019/Brighton\">IndieWebCamp Brighton</a> when a session about private posts was about to start. <a href=\"https://adactio.com/\">Jeremy Keith</a> walked out of the room while making a comment that he didn\u2019t see private pages as something the Web needed. This does not mean I can\u2019t have them, but it did make me think about why I want them and what they would mean to the Web and the world.</p>\n<p>By putting the private comments on a separate channel, you are also removing them from the Web. This makes the Web a place for open and public conversations again. (Again: one could argue that thing on the \u2018Private Web\u2019 are not on the Web either.) The last few months I\u2019ve been reading more blogs and I must say I really enjoy that open Web. </p>\n<p>The separation of private comments creates a clearer boundary between the open and the private, and maybe that\u2019s a good thing. It makes an easier question: it\u2019s harder to answer \u201cwhich people should be able to read this post?\u201d, than it is to answer \u201cdoes this concern only me and the author, or could there possibly be someone out there who\u2019s interested?\u201d.</p>\n<p>No real plans for removal yet, but I keep being torn about private posts.</p>"
},
"author": {
"type": "card",
"name": "Sebastiaan Andeweg",
"url": "https://seblog.nl/",
"photo": "https://seblog.nl/photo.jpg"
},
"post-type": "article",
"_id": "10703010",
"_source": "1366",
"_is_read": true
}
{
"type": "entry",
"published": "2020-04-12T13:18:00+01:00",
"url": "https://www.jvt.me/mf2/2020/04/hqtyq/",
"in-reply-to": [
"https://lobste.rs/s/lm7hcu/implementing_indieweb_into_my_website"
],
"content": {
"text": "For those wanting a bit more info on the IndieWeb, see the discussion and post on https://lobste.rs/s/zg6iok/indieweb_movement_owning_your_data_being where I shared a transcript of a conference talk I did on the subject",
"html": "<p>For those wanting a bit more info on the IndieWeb, see the discussion and post on <a href=\"https://lobste.rs/s/zg6iok/indieweb_movement_owning_your_data_being\">https://lobste.rs/s/zg6iok/indieweb_movement_owning_your_data_being</a> where I shared a transcript of a conference talk I did on the subject</p>"
},
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "reply",
"_id": "10676477",
"_source": "2169",
"_is_read": true
}
{
"type": "entry",
"published": "2020-04-12T13:16:00+01:00",
"url": "https://www.jvt.me/mf2/2020/04/4n3np/",
"in-reply-to": [
"https://lobste.rs/s/lm7hcu/implementing_indieweb_into_my_website#c_93bkut"
],
"content": {
"text": "I use https://github.com/PlaidWeb/webmention.js to render my webmentions client-side so they're always up to date, instead of needing to rebuild the site - I've written a bit more about it at https://www.jvt.me/posts/2019/06/30/client-side-webmentions/",
"html": "<p>I use <a href=\"https://github.com/PlaidWeb/webmention.js\">https://github.com/PlaidWeb/webmention.js</a> to render my webmentions client-side so they're always up to date, instead of needing to rebuild the site - I've written a bit more about it at <a href=\"https://www.jvt.me/posts/2019/06/30/client-side-webmentions/\">https://www.jvt.me/posts/2019/06/30/client-side-webmentions/</a></p>"
},
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "reply",
"_id": "10676478",
"_source": "2169",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Neil Mather",
"url": "https://doubleloop.net/",
"photo": null
},
"url": "https://doubleloop.net/2020/04/11/6787/",
"published": "2020-04-11T16:53:48+00:00",
"content": {
"html": "Liked <a href=\"https://kevq.uk/implementing-the-indieweb-into-my-website/\">Implementing The IndieWeb Into My Website - Kev Quirk</a> by Kev Quirk <em>(Kev Quirk)</em>\n<blockquote>I wanted to utilise the IndieWeb to take ownership of my data and to make may site more connected. This post talks about how I've managed to do that.</blockquote>",
"text": "Liked Implementing The IndieWeb Into My Website - Kev Quirk by Kev Quirk (Kev Quirk)\nI wanted to utilise the IndieWeb to take ownership of my data and to make may site more connected. This post talks about how I've managed to do that."
},
"post-type": "note",
"_id": "10661236",
"_source": "1895",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "Neil Mather",
"url": "https://doubleloop.net/",
"photo": null
},
"url": "https://doubleloop.net/2020/04/11/6782/",
"published": "2020-04-11T12:16:33+00:00",
"content": {
"html": "Read <a href=\"https://blog.cjeller.site/from-blog-to-blocks\">From Blog to Blocks</a> <em>(CJ Eller)</em>\n<blockquote>Crossposting augments my writing to not only exist as something else (blocks) but to interact with more types of media (not just other words but images and video) in a different way (connecting blocks to other blocks).</blockquote>\n\n\n\n<p>This is really interesting from CJ Eller on <a href=\"https://commonplace.doubleloop.net/20200410200959-the_potential_of_crossposting.html\">the potential of crossposting</a>. Interesting to think about how it fits in with the IndieWeb ideas of owning your own content and POSSEing (publishing on your own site, syndicating elsewhere).</p>\n<p>I\u2019ve thought of POSSE before more as a means of transitioning away from the big platforms (the <a href=\"https://commonplace.doubleloop.net/20200410190426-bit_tyrants.html\">bit tyrants</a>) while they still have the network effects. But this is more about your stuff existing in various locations as a means to enable new creative uses of it.</p>",
"text": "Read From Blog to Blocks (CJ Eller)\nCrossposting augments my writing to not only exist as something else (blocks) but to interact with more types of media (not just other words but images and video) in a different way (connecting blocks to other blocks).\n\n\n\nThis is really interesting from CJ Eller on the potential of crossposting. Interesting to think about how it fits in with the IndieWeb ideas of owning your own content and POSSEing (publishing on your own site, syndicating elsewhere).\nI\u2019ve thought of POSSE before more as a means of transitioning away from the big platforms (the bit tyrants) while they still have the network effects. But this is more about your stuff existing in various locations as a means to enable new creative uses of it."
},
"name": "Crossposting",
"post-type": "note",
"_id": "10653709",
"_source": "1895",
"_is_read": true
}
{
"type": "entry",
"published": "2020-04-10T22:59:00+01:00",
"url": "https://www.jvt.me/mf2/2020/04/roltb/",
"content": {
"text": "Made some good progress on my Micropub edit/delete functionality today - hopefully will be in a state to look at getting live tomorrow \ud83d\ude4c\ud83c\udffc",
"html": "<p>Made some good progress on my Micropub edit/delete functionality today - hopefully will be in a state to look at getting live tomorrow \ud83d\ude4c\ud83c\udffc</p>"
},
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "note",
"_id": "10638515",
"_source": "2169",
"_is_read": true
}
I have about 30 open tasks and about 4 more person-months left on Koype core and another month for its auxiliary services before I can consider it useful for self-hosting. I think I’m a little nuts but the goal is to have something that works a bit like Tumblr and can be working as a Patreon alternative - but with IndieWeb principles built in by default.
{
"type": "entry",
"published": "2020-04-09T13:54:38.70985-07:00",
"url": "https://v2.jacky.wtf/post/dd0cd0a6-616a-4f83-95d4-a8c331632061",
"content": {
"text": "I have about 30 open tasks and about 4 more person-months left on Koype core and another month for its auxiliary services before I can consider it useful for self-hosting. I think I\u2019m a little nuts but the goal is to have something that works a bit like Tumblr and can be working as a Patreon alternative - but with IndieWeb principles built in by default.",
"html": "<p>I have about 30 open tasks and about 4 more person-months left on Koype core and another month for its auxiliary services before I can consider it useful for self-hosting. I think I\u2019m a little nuts but the goal is to have something that works a bit like Tumblr and can be working as a Patreon alternative - but with IndieWeb principles built in by default.</p>"
},
"author": {
"type": "card",
"name": "",
"url": "https://v2.jacky.wtf",
"photo": null
},
"post-type": "note",
"_id": "10606043",
"_source": "1886",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "George",
"url": "https://www.allaboutgeorge.com/",
"photo": null
},
"url": "https://www.allaboutgeorge.com/2020/04/08/hello-homebrew/",
"published": "2020-04-08T21:44:55-07:00",
"content": {
"html": "<p>It\u2019s always strange to meet someone who wrote a simple HTML code snippet (aka the <a href=\"https://indieauth.com/\">IndieAuth login</a>) you just used an hour earlier to do something on your own Web site. But it\u2019s sure nice when you thank them for it and they graciously accept it. Thanks again, <a href=\"https://aaronparecki.com/\">Aaron</a>.</p>\n<p>Shout-out to <a href=\"https://www.tantek.com/\">Tantek</a> for the Homebrew Website Club West Coast <a href=\"https://events.indieweb.org/2020/04/online-homebrew-website-club-west-coast-xnjmZtjwzwZs\">invite</a>, and lovely to meet folks like <a href=\"http://alexkearney.com/\">Alex</a> <a href=\"https://www.kongaloosh.com/\">K.</a>, <a href=\"https://gregorlove.com/\">Gregor,</a> <a href=\"https://david.shanske.com/\">David,</a> <a href=\"https://www.lahacker.net/\">Angelo</a> and <a href=\"http://ikebana.website/\">Katherine</a>.</p>\n<p>P.S.: no actual beverages, alcoholic or otherwise, were consumed during our time together. Maybe next time, though \u2026</p>",
"text": "It\u2019s always strange to meet someone who wrote a simple HTML code snippet (aka the IndieAuth login) you just used an hour earlier to do something on your own Web site. But it\u2019s sure nice when you thank them for it and they graciously accept it. Thanks again, Aaron.\nShout-out to Tantek for the Homebrew Website Club West Coast invite, and lovely to meet folks like Alex K., Gregor, David, Angelo and Katherine.\nP.S.: no actual beverages, alcoholic or otherwise, were consumed during our time together. Maybe next time, though \u2026"
},
"name": "Hello, homebrew",
"post-type": "article",
"_id": "10584153",
"_source": "4592",
"_is_read": true
}
{
"type": "entry",
"published": "2020-04-07T16:05:18+00:00",
"url": "https://werd.io/2020/recording-life-on-the-ground",
"name": "Recording life on the ground",
"content": {
"text": "I'm more and more convinced that we all need to tell this story. Covid-19 landed in a world that was succumbing to nationalist leaders who enjoy bending the truth to suit their own narratives. The story of this global pandemic can't be left to them to tell. It also can't be left to the rich and powerful, or to brands. It needs to be a shared patchwork that we all contribute to.I believe the indieweb has a part to play here. If it's at all possible, everyone should be writing on their own site, and backing up to a place they control. It should all be saved in the Internet Archive, and maybe on IPFS, and anywhere else you can think of. If one site filters stories out because advertisers don't want to be associated with coronavirus, or blips out because it went out of business, it shouldn't take the stories about this unprecedented period of history with it.If you're wondering how and where to blog and share your story, I wrote this guide last year.But of course, not everyone is equipped to write their own narrative. Writing is a muscle; I don't claim to have developed it perfectly, but I think I find it easier to get to a published post than many people. I've been wondering how to help people to share their perspectives without making it hard.Over on Twitter, one person suggested around 10 questions that people could answer on a regular basis, and maybe upload a photo to go along with it. I like that idea a lot.So here's what I'm thinking: I'll do the heavy lifting of building a platform that asks those questions. If you have a website that supports micropub, it'll post them on your own site for posterity. If you have a WordPress site, it'll use the REST API to do that, too. But those things are optional. You'll also just be able to post to the website and keep your answers there - and know that they'll be shared to the Internet Archive, IPFS, and some other redundant backups. The content will be made available under a license that will allow the entire archive of stories to be downloaded.Aside from building this platform, which is my job, the only thing remaining is: what should the questions be? I have my own opinions, but I'd love to hear yours. You can always write to me at ben@benwerd.com.I'll commit to providing an update on this project by this time next week. Look for an update on Tuesday, April 14.\u00a0Photo by Clem Onojeghuo on Unsplash",
"html": "<p><img src=\"https://werd.io/file/5e8ca541b16ea147d109a172\" alt=\"\" width=\"1000\" height=\"686\" /></p><p>I'm more and more convinced that we all need to tell this story. Covid-19 landed in a world that was succumbing to nationalist leaders who enjoy bending the truth to suit their own narratives. The story of this global pandemic can't be left to them to tell. It also can't be left to the rich and powerful, or to brands. It needs to be a shared patchwork that we all contribute to.</p><p>I believe the <a href=\"https://indieweb.org\">indieweb</a> has a part to play here. If it's at all possible, everyone should be writing on their own site, and backing up to a place they control. It should all be saved in the <a href=\"https://archive.org\">Internet Archive</a>, and maybe on <a href=\"https://ipfs.io/\">IPFS</a>, and anywhere else you can think of. If one site filters stories out because <a href=\"https://www.buzzfeednews.com/article/craigsilverman/news-sites-need-ads-to-survive-the-coronavirus-more-than-35\">advertisers don't want to be associated with coronavirus</a>, or blips out because it went out of business, it shouldn't take the stories about this unprecedented period of history with it.</p><p>If you're wondering how and where to blog and share your story, <a href=\"https://werd.io/2019/the-best-way-to-blog-in-2020\">I wrote this guide last year</a>.</p><p>But of course, not everyone is equipped to write their own narrative. Writing is a muscle; I don't claim to have developed it perfectly, but I think I find it easier to get to a published post than many people. I've been wondering how to help people to share their perspectives without making it <em>hard</em>.</p><p>Over on Twitter, one person <a href=\"https://twitter.com/labour_lives/status/1247096309376581632\">suggested around 10 questions</a> that people could answer on a regular basis, and maybe upload a photo to go along with it. I like that idea a lot.</p><p>So here's what I'm thinking: I'll do the heavy lifting of building a platform that asks those questions. If you have a website that supports <a href=\"https://indieweb.org/Micropub\">micropub</a>, it'll post them on your own site for posterity. If you have a WordPress site, it'll use the <a href=\"https://developer.wordpress.org/rest-api/\">REST API</a> to do that, too. But those things are optional. You'll also just be able to post to the website and keep your answers there - and know that they'll be shared to the Internet Archive, IPFS, and some other redundant backups. The content will be made available under a license that will allow the entire archive of stories to be downloaded.</p><p>Aside from building this platform, which is my job, the only thing remaining is: what should the questions be? I have my own opinions, but I'd love to hear yours. You can always write to me at <a href=\"mailto:ben@benwerd.com\">ben@benwerd.com</a>.</p><p>I'll commit to providing an update on this project by this time next week. Look for an update on Tuesday, April 14.</p><p>\u00a0</p><p><em>Photo by <a href=\"https://unsplash.com/@clemono2?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText\">Clem Onojeghuo</a> on <a href=\"https://unsplash.com/s/photos/photographer?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText\">Unsplash</a></em></p>"
},
"author": {
"type": "card",
"name": "Ben Werdm\u00fcller",
"url": "https://werd.io/profile/benwerd",
"photo": "https://werd.io/file/5d388c5fb16ea14aac640912/thumb.jpg"
},
"post-type": "article",
"_id": "10533780",
"_source": "191",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": null,
"url": "https://monday.micro.blog/",
"photo": null
},
"url": "https://monday.micro.blog/2020/04/06/catching-up-with.html",
"published": "2020-04-06T19:57:33-07:00",
"content": {
"html": "<p>Jean and Manton do a quick review of 2020 so far, including:</p>\n\n<ul><li><a href=\"https://micro.welltempered.net/2020/01/31/february-photoblogging-challenge.html\">Photo challenge</a></li>\n<li><a href=\"https://indieweb.org/2020%2FAustin\">IndieWebCamp Austin</a></li>\n<li><a href=\"https://www.manton.org/2020/03/15/free-microcasting-through.html\">Free podcast hosting for all accounts through April</a></li>\n<li><a href=\"https://www.manton.org/2020/03/24/microblog-free-month.html\">Six months free hosting, including podcast hosting, for teachers</a></li>\n<li><a href=\"https://help.micro.blog/2020/categories/\">Categories and category feeds</a></li>\n<li><a href=\"https://help.micro.blog/2020/conversation-js/\">Hosting replies</a></li>\n<li><a href=\"https://www.manton.org/2020/03/30/microblog-for-ios.html\">Updates of iOS and macOS include post editing</a></li>\n<li><a href=\"https://www.manton.org/2020/03/31/weve-updated-sunlit.html\">Sunlit updated</a></li>\n</ul><p></p>",
"text": "Jean and Manton do a quick review of 2020 so far, including:\n\nPhoto challenge\nIndieWebCamp Austin\nFree podcast hosting for all accounts through April\nSix months free hosting, including podcast hosting, for teachers\nCategories and category feeds\nHosting replies\nUpdates of iOS and macOS include post editing\nSunlit updated"
},
"name": "84: Catching up with Manton, Spring 2020 edition",
"audio": [
"https://monday.micro.blog/uploads/2020/dcc347d9a6.mp3"
],
"post-type": "audio",
"_id": "10521168",
"_source": "250",
"_is_read": true
}
