Our footpaths converged around the same 5-10 platforms, each with its own particular manner of communication. I have learned, unintentionally, to code switch every time I craft a new post. It’s exhausting, trying to keep track of all those unspoken rules shaped by years of use.
But I don’t have rules like that on my blog. I turned off stats. There are no comments. No likes.
{
"type": "entry",
"published": "2021-01-19T20:23:59Z",
"url": "https://adactio.com/links/17766",
"category": [
"writing",
"blogging",
"publishing",
"sharing",
"indieweb",
"socialmedia",
"rss"
],
"bookmark-of": [
"https://lucybellwood.com/stumbling/"
],
"content": {
"text": "Stumbling \u2013 Lucy Bellwood\n\n\n\n\n Our footpaths converged around the same 5-10 platforms, each with its own particular manner of communication. I have learned, unintentionally, to code switch every time I craft a new post. It\u2019s exhausting, trying to keep track of all those unspoken rules shaped by years of use.\n \n But I don\u2019t have rules like that on my blog. I turned off stats. There are no comments. No likes.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://lucybellwood.com/stumbling/\">\nStumbling \u2013 Lucy Bellwood\n</a>\n</h3>\n\n<blockquote>\n <p>Our footpaths converged around the same 5-10 platforms, each with its own particular manner of communication. I have learned, unintentionally, to code switch every time I craft a new post. It\u2019s exhausting, trying to keep track of all those unspoken rules shaped by years of use.</p>\n \n <p>But I don\u2019t have rules like that on my blog. I turned off stats. There are no comments. No likes.</p>\n</blockquote>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "bookmark",
"_id": "17837213",
"_source": "2",
"_is_read": true
}
{
"type": "entry",
"published": "2021-01-19T18:08:06.603Z",
"url": "https://www.jvt.me/mf2/2021/01/iyvrw/",
"category": [
"homebrew-website-club"
],
"content": {
"text": "Reminder that it's #HomebrewWebsiteClub Nottingham tomorrow! I hope to see you there at 1730 for some website stuff! https://events.indieweb.org/2021/01/homebrew-website-club-nottingham-LwVx3NUZ2dKh",
"html": "<p>Reminder that it's <a href=\"https://www.jvt.me/tags/homebrew-website-club/\">#HomebrewWebsiteClub</a> Nottingham tomorrow! I hope to see you there at 1730 for some website stuff! <a href=\"https://events.indieweb.org/2021/01/homebrew-website-club-nottingham-LwVx3NUZ2dKh\">https://events.indieweb.org/2021/01/homebrew-website-club-nottingham-LwVx3NUZ2dKh</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": "17836506",
"_source": "2169",
"_is_read": true
}
“In the case of Capsule, each content creator has their own website — has their own address, like Capsule.Greenwald.com — and then people go there and their first discovery of the mesh is through people that they’re interested in hearing from.”
techcrunch.com/2021/01/18/cryptocat-author-gets-insanely-fast-backing-to-build-p2p-tech-for-social-media
I had to think about this for a bit, but I think I like this idea as an extension of the current IndieWeb ecosystem. Most people don't want to pay for a domain name or hosting, so I wonder whether Capsule can find a way to enable both groups to interact successfully.
The question for me is, will non-paying servers be able to operate as first class citizens in the federation, with a trusted identity? Will be interesting to watch development.
{
"type": "entry",
"published": "2021-01-19T17:08:26+10:00",
"url": "https://mblaney.xyz/2021-01-19-In_the_case_of_Capsule_each_content_creato",
"category": [
"indieweb"
],
"content": {
"text": "\u201cIn the case of Capsule, each content creator has their own website \u2014 has their own address, like Capsule.Greenwald.com \u2014 and then people go there and their first discovery of the mesh is through people that they\u2019re interested in hearing from.\u201d\n\ntechcrunch.com/2021/01/18/cryptocat-author-gets-insanely-fast-backing-to-build-p2p-tech-for-social-media\n\n\nI had to think about this for a bit, but I think I like this idea as an extension of the current IndieWeb ecosystem. Most people don't want to pay for a domain name or hosting, so I wonder whether Capsule can find a way to enable both groups to interact successfully.\n\n\nThe question for me is, will non-paying servers be able to operate as first class citizens in the federation, with a trusted identity? Will be interesting to watch development.",
"html": "\u201cIn the case of Capsule, each content creator has their own website \u2014 has their own address, like Capsule.Greenwald.com \u2014 and then people go there and their first discovery of the mesh is through people that they\u2019re interested in hearing from.\u201d<br /><br /><a href=\"https://techcrunch.com/2021/01/18/cryptocat-author-gets-insanely-fast-backing-to-build-p2p-tech-for-social-media/?ncid=txtlnkusaolp00000618\">techcrunch.com/2021/01/18/cryptocat-author-gets-insanely-fast-backing-to-build-p2p-tech-for-social-media</a><br /><br />\nI had to think about this for a bit, but I think I like this idea as an extension of the current IndieWeb ecosystem. Most people don't want to pay for a domain name or hosting, so I wonder whether Capsule can find a way to enable both groups to interact successfully.<br /><br />\nThe question for me is, will non-paying servers be able to operate as first class citizens in the federation, with a trusted identity? Will be interesting to watch development."
},
"author": {
"type": "card",
"name": "Malcolm Blaney",
"url": "https://mblaney.xyz",
"photo": "https://mblaney.xyz/public/profile_thumb.png"
},
"post-type": "note",
"_id": "17823101",
"_source": "3708",
"_is_read": true
}
Does anyone have any experience with the whole IndieWeb thing? It feels more complicated than it’s worth. https://indieweb.org/
mike.rockwell.mx
{
"type": "entry",
"author": {
"name": "Mike Rockwell",
"url": "https://mdrockwell.net/",
"photo": "https://www.gravatar.com/avatar/6cb444245fc3c3ace752833c2616784a?s=96&d=https%3A%2F%2Fmicro.blog%2Fimages%2Fblank_avatar.png"
},
"url": "https://mike.rockwell.mx/asides/450",
"content": {
"html": "<p>Does anyone have any experience with the whole IndieWeb thing? It feels more complicated than it\u2019s worth. <a href=\"https://indieweb.org/\">https://indieweb.org/</a></p> <a href=\"https://mike.rockwell.mx/asides/450\">mike.rockwell.mx</a>",
"text": "Does anyone have any experience with the whole IndieWeb thing? It feels more complicated than it\u2019s worth. https://indieweb.org/ mike.rockwell.mx"
},
"published": "2021-01-17T23:37:40+00:00",
"post-type": "note",
"_id": "33380031",
"_source": "7224",
"_is_read": true
}
{
"type": "entry",
"published": "2021-01-16T19:23:55+00:00",
"url": "https://werd.io/2021/adjusting-the-volume",
"name": "Adjusting the volume",
"content": {
"text": "I'm not quite an indieweb zealot - you can find me on Twitter and other social networks over the web - but I've been writing on my own site since 1998 (albeit not one consistent, continuous site - I change it up every decade or so), and it's become a core part of who I am, how I think, and how I represent myself online.You might have noticed - email subscribers certainly did - that I've turned up the volume on my posting this year. So far in January, that's meant a post a day in my personal space. The feedback has generally been good, but a few email subscribers did complain. I totally get it. Nobody wants their inboxes to clog up; the calculus might be different if this was a business newsletter with actionable insights, but that's not what this is. More than anything, I'm hoping to spark a conversation with my posts.There are a few things I'm thinking about doing. The first is dropping the frequency of the emails, and thinking about them as more of a digest. You'd get one on Thursday, and one on Sunday (or something like that). Obviously, RSS / h-feed / JSON-feed subscribers (hi!) would still receive posts in real time. Maybe there would also be an email list for people who did want to receive posts as I wrote them.The second thing I'm thinking about doing is taking this posting frequency and putting it on Medium for the rest of the month, with a regular summary post over here. This is a controversial thing for someone who's so deep into indieweb and the open web to suggest, but there are a few reasons for trying this. Mostly I want to see how the experience compares. I worked at Medium in 2016, and posted fairly regularly there during that time and while I was at Matter Ventures, but the platform has evolved significantly since then.So that's what I'm going to do to start. For the remainder of January, I'll be posting on Medium daily, with summary listings posted here semi-regularly. Then I'll return here in February and let you know what I discovered.You can follow me on Medium over here.",
"html": "<p>I'm not quite an <a href=\"https://indieweb.org\">indieweb</a> zealot - you can find me on Twitter and other social networks over the web - but I've been writing on my own site since 1998 (albeit not one consistent, continuous site - I change it up every decade or so), and it's become a core part of who I am, how I think, and how I represent myself online.</p><p>You might have noticed - email subscribers certainly did - that I've turned up the volume on my posting this year. So far in January, that's meant a post a day in my personal space. The feedback has generally been good, but a few email subscribers did complain. I totally get it. Nobody wants their inboxes to clog up; the calculus might be different if this was a business newsletter with actionable insights, but that's not what this is. More than anything, I'm hoping to spark a conversation with my posts.</p><p>There are a few things I'm thinking about doing. The first is dropping the frequency of the emails, and thinking about them as more of a digest. You'd get one on Thursday, and one on Sunday (or something like that). Obviously, RSS / h-feed / JSON-feed subscribers (hi!) would still receive posts in real time. Maybe there would also be an email list for people who <em>did</em> want to receive posts as I wrote them.</p><p>The second thing I'm thinking about doing is taking this posting frequency and <a href=\"https://benwerd.medium.com\">putting it on Medium</a> for the rest of the month, with a regular summary post over here. This is a controversial thing for someone who's so deep into indieweb and the open web to suggest, but there are a few reasons for trying this. Mostly I want to see how the experience compares. I worked at Medium in 2016, and posted fairly regularly there during that time and <a href=\"https://medium.com/matter-driven-narrative\">while I was at Matter Ventures</a>, but the platform has evolved significantly since then.</p><p>So that's what I'm going to do to start. For the remainder of January, I'll be posting on Medium daily, with summary listings posted here semi-regularly. Then I'll return here in February and let you know what I discovered.</p><p><a href=\"https://benwerd.medium.com\">You can follow me on Medium over here.</a></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": "17775347",
"_source": "191",
"_is_read": true
}
#indieweb is the best web
My new year's resolution is to read and respond to comments on my blog. Getting a bit hard to respond to every question on twitter, and I think this might be bit more manageable. conscienceandconsciousness.com
https://twitter.com/Philip_Goff/status/1350212744075743238
{
"type": "entry",
"published": "2021-01-16T12:27:09+10:00",
"url": "https://mblaney.xyz/2021-01-16-indieweb_is_the_best_web__My_new_years_res",
"syndication": [
"https://twitter.com/malcolmblaney/status/1350268343761186816"
],
"quotation-of": "https://twitter.com/Philip_Goff/status/1350212744075743238",
"content": {
"text": "#indieweb is the best web\n\nMy new year's resolution is to read and respond to comments on my blog. Getting a bit hard to respond to every question on twitter, and I think this might be bit more manageable. conscienceandconsciousness.com\nhttps://twitter.com/Philip_Goff/status/1350212744075743238",
"html": "#indieweb is the best web<br /><br />My new year's resolution is to read and respond to comments on my blog. Getting a bit hard to respond to every question on twitter, and I think this might be bit more manageable. <a href=\"https://conscienceandconsciousness.com/\">conscienceandconsciousness.com</a><br /><a class=\"u-url\" href=\"https://twitter.com/Philip_Goff/status/1350212744075743238\">https://twitter.com/Philip_Goff/status/1350212744075743238</a><a href=\"https://brid.gy/publish/twitter?bridgy_omit_link=true\"></a><a href=\"https://twitter.com/malcolmblaney/status/1350268343761186816\" class=\"u-syndication\"></a>"
},
"author": {
"type": "card",
"name": "Malcolm Blaney",
"url": "https://mblaney.xyz",
"photo": "https://mblaney.xyz/public/profile_thumb.png"
},
"post-type": "note",
"refs": {
"https://twitter.com/Philip_Goff/status/1350212744075743238": {
"type": "entry",
"url": "https://twitter.com/Philip_Goff/status/1350212744075743238",
"name": "My new year's resolution is to read and respond to comments on my blog. Getting a bit hard to respond to every question on twitter, and I think this might be bit more manageable. conscienceandconsciousness.com\nhttps://twitter.com/Philip_Goff/status/1350212744075743238",
"post-type": "article"
}
},
"_id": "17765228",
"_source": "3708",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "fluffy",
"url": "http://beesbuzz.biz/",
"photo": null
},
"url": "http://beesbuzz.biz/blog/2316-Distributed-toxicity-and-the-IndieWeb",
"published": "2021-01-12T14:44:18-08:00",
"content": {
"html": "<p>This tweet has been making the rounds in IndieWeb spaces, and reflects a thing I\u2019ve been thinking about on and off lately for obvious reasons:</p><blockquote><p>I was building a decentralized, WebMention-based social network (way before Mastodon/ActivityPub), and if anyone had cared back then, it would be a nazi darling today and that just sucks. <a href=\"https://t.co/jXaZTsUNz8\">https://t.co/jXaZTsUNz8</a></p>\u2014 Hendrik Mans (@hmans) <a href=\"https://twitter.com/hmans/status/1349105824992538624?ref_src=twsrc%5Etfw\">January 12, 2021</a></blockquote> <p>I\u2019ve seen several other related sentiments lately; with a certain prominent politician being deplatformed from all of the mainstream social media platforms, and all of the platforms that accept him being in turn shut down or otherwise made ineffective, people have been (quite reasonably!) wondering what happens if he ends up starting up his own IndieWeb site, and causes a resurgence in self-hosted or otherwise privately-run, single-author blogs.</p>\n\n\n<p>I feel like the threat model for IndieWeb is very different than the threat model of so-called \u201csilo\u201d social media. Silos are built around increasing engagement and spreading popular posts far and wide, and ensuring that people stay addicted to the site. As such, they\u2019re also biased towards fast-spreading, viral content, and quick, hot takes that give people an adrenaline and/or dopamine rush.</p><p>One way in which self-hosted platforms are different is that it\u2019s up to people to seek out and spread the information they want to. At least with current platforms it\u2019s pretty unwieldy to do a quick repost and propagation of content, and there\u2019s also no central source of post propagation. You posting something to the IndieWeb doesn\u2019t mean that it\u2019ll automatically propagate to anyone who isn\u2019t already subscribed to you, and audiences tend to remain a lot smaller and more deliberate.</p><p>Mastodon still has the concept of a federated timeline, where anything that gets posted will spread far and wide based on connections between instances. This is, in effect, very similar to the algorithmic discovery stuff that makes Twitter work the way it does too.</p><p>There\u2019s also the whole fire-and-forget quick-post hot-take nature of conversations which just plain doesn\u2019t happen in IndieWeb spaces, at least not right now. Some future stack might make Twitter-like updates more convenient. I know that I personally wouldn\u2019t subscribe to sources of those, though, and there\u2019s still a much greater onus on the reader to be able to subscribe to and process those feeds.</p><p>A future IndieWeb platform could very well make the same mistakes, though, and lead to automatic discovery and propagation of stuff. Centralized readers in particular would be a pretty obvious source of this sort of thing.</p><p>But the great thing about IndieWeb, at least, is that people are still in control of their experience. There isn\u2019t one specific publishing or reading model that people are stuck with, and this is by design. There will certainly be <em>pockets</em> of IndieWeb stuff that becomes just as objectionable as the worst parts of Twitter/Mastodon or the entirety of Parler/Gab, but people can still participate in IndieWeb without having to be a part of it.</p><p>I also feel that having personal responsibility for the content you host also makes you much more accountable for that content. If someone were to start posting illegal stuff to their website, their hosting provider would be well within their rights to shut it down. They could then move to a hosting provider that\u2019s more amenable to that or not under the same jurisdiction, but fundamentally, if nobody is subscribing to their site content, it\u2019s still not going to spread.</p><p>For that matter, nothing stops any currently-deplatformed troll from running their own website. There are <em>plenty</em> of ways that people can launch a quick-and-easy WordPress blog, for example. But just because someone is posting it to the web doesn\u2019t mean they\u2019re going to have an audience. Nothing automatically makes their toxic material spread through the universe.</p><p>I think IndieWeb developers do need to be careful about the tools they develop. If you\u2019re working on IndieWeb stuff, make sure you\u2019re solving the problems that need to be solved, and not reinventing the same problems as the silos the long way around. And if you\u2019re building a shared-hosting platform or a centralized reader, you\u2019d better damned well be putting safety and accountability as the top priority for everything you provide.</p><p>So, yeah. I can imagine some facet of IndieWeb going in a very dangerous direction that would be much more difficult to stop than on a centralized server. But IndieWeb is an ethos and a set of opt-in protocols, and participating in IndieWeb in general doesn\u2019t mean having to participate in <em>all</em> of it. I feel like that\u2019s already a huge advantage.</p>\n\n<p><a href=\"http://beesbuzz.biz/blog/2316-Distributed-toxicity-and-the-IndieWeb#comments\">comments</a></p>",
"text": "This tweet has been making the rounds in IndieWeb spaces, and reflects a thing I\u2019ve been thinking about on and off lately for obvious reasons:I was building a decentralized, WebMention-based social network (way before Mastodon/ActivityPub), and if anyone had cared back then, it would be a nazi darling today and that just sucks. https://t.co/jXaZTsUNz8\u2014 Hendrik Mans (@hmans) January 12, 2021 I\u2019ve seen several other related sentiments lately; with a certain prominent politician being deplatformed from all of the mainstream social media platforms, and all of the platforms that accept him being in turn shut down or otherwise made ineffective, people have been (quite reasonably!) wondering what happens if he ends up starting up his own IndieWeb site, and causes a resurgence in self-hosted or otherwise privately-run, single-author blogs.\n\n\nI feel like the threat model for IndieWeb is very different than the threat model of so-called \u201csilo\u201d social media. Silos are built around increasing engagement and spreading popular posts far and wide, and ensuring that people stay addicted to the site. As such, they\u2019re also biased towards fast-spreading, viral content, and quick, hot takes that give people an adrenaline and/or dopamine rush.One way in which self-hosted platforms are different is that it\u2019s up to people to seek out and spread the information they want to. At least with current platforms it\u2019s pretty unwieldy to do a quick repost and propagation of content, and there\u2019s also no central source of post propagation. You posting something to the IndieWeb doesn\u2019t mean that it\u2019ll automatically propagate to anyone who isn\u2019t already subscribed to you, and audiences tend to remain a lot smaller and more deliberate.Mastodon still has the concept of a federated timeline, where anything that gets posted will spread far and wide based on connections between instances. This is, in effect, very similar to the algorithmic discovery stuff that makes Twitter work the way it does too.There\u2019s also the whole fire-and-forget quick-post hot-take nature of conversations which just plain doesn\u2019t happen in IndieWeb spaces, at least not right now. Some future stack might make Twitter-like updates more convenient. I know that I personally wouldn\u2019t subscribe to sources of those, though, and there\u2019s still a much greater onus on the reader to be able to subscribe to and process those feeds.A future IndieWeb platform could very well make the same mistakes, though, and lead to automatic discovery and propagation of stuff. Centralized readers in particular would be a pretty obvious source of this sort of thing.But the great thing about IndieWeb, at least, is that people are still in control of their experience. There isn\u2019t one specific publishing or reading model that people are stuck with, and this is by design. There will certainly be pockets of IndieWeb stuff that becomes just as objectionable as the worst parts of Twitter/Mastodon or the entirety of Parler/Gab, but people can still participate in IndieWeb without having to be a part of it.I also feel that having personal responsibility for the content you host also makes you much more accountable for that content. If someone were to start posting illegal stuff to their website, their hosting provider would be well within their rights to shut it down. They could then move to a hosting provider that\u2019s more amenable to that or not under the same jurisdiction, but fundamentally, if nobody is subscribing to their site content, it\u2019s still not going to spread.For that matter, nothing stops any currently-deplatformed troll from running their own website. There are plenty of ways that people can launch a quick-and-easy WordPress blog, for example. But just because someone is posting it to the web doesn\u2019t mean they\u2019re going to have an audience. Nothing automatically makes their toxic material spread through the universe.I think IndieWeb developers do need to be careful about the tools they develop. If you\u2019re working on IndieWeb stuff, make sure you\u2019re solving the problems that need to be solved, and not reinventing the same problems as the silos the long way around. And if you\u2019re building a shared-hosting platform or a centralized reader, you\u2019d better damned well be putting safety and accountability as the top priority for everything you provide.So, yeah. I can imagine some facet of IndieWeb going in a very dangerous direction that would be much more difficult to stop than on a centralized server. But IndieWeb is an ethos and a set of opt-in protocols, and participating in IndieWeb in general doesn\u2019t mean having to participate in all of it. I feel like that\u2019s already a huge advantage.\n\ncomments"
},
"name": "fluffy rambles: Distributed toxicity and the IndieWeb",
"post-type": "article",
"_id": "17688237",
"_source": "3782",
"_is_read": true
}
Creating Postman collections programmatically from a Micropub server's supported configuration.
{
"type": "entry",
"published": "2021-01-11 19:37:01 +0000 UTC",
"summary": "Creating Postman collections programmatically from a Micropub server's supported configuration.",
"url": "https://www.jvt.me/posts/2021/01/11/micropub-postman/",
"category": [
"postman",
"ruby",
"micropub",
"micropub-postman"
],
"name": "Autogenerating Postman Collections for Micropub Servers",
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "article",
"_id": "17655943",
"_source": "2169",
"_is_read": true
}
Tonight I've been investigating a few things for my #Postman API Hack and I've found that Postman's OAuth2 support is pretty awesome - it works very nicely with #Indieauth which is an important part of my hack 😉 I'm also pretty happy with what I'm planning on doing - hoping to get some good progress with the hack itself this weekend, too!
{
"type": "entry",
"published": "2021-01-08T22:26:30.781Z",
"url": "https://www.jvt.me/mf2/2021/01/hjfzb/",
"category": [
"postman",
"indieauth"
],
"content": {
"text": "Tonight I've been investigating a few things for my #Postman API Hack and I've found that Postman's OAuth2 support is pretty awesome - it works very nicely with #Indieauth which is an important part of my hack \ud83d\ude09 I'm also pretty happy with what I'm planning on doing - hoping to get some good progress with the hack itself this weekend, too!",
"html": "<p>Tonight I've been investigating a few things for my <a href=\"https://www.jvt.me/tags/postman/\">#Postman</a> API Hack and I've found that Postman's OAuth2 support is pretty awesome - it works very nicely with <a href=\"https://www.jvt.me/tags/indieauth/\">#Indieauth</a> which is an important part of my hack \ud83d\ude09 I'm also pretty happy with what I'm planning on doing - hoping to get some good progress with the hack itself this weekend, too!</p>"
},
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "note",
"_id": "17596654",
"_source": "2169",
"_is_read": true
}
🔖 Bookmarked How I turned my Goodreads data into a self-hosted website with Eleventy https://hiddedevries.nl/en/blog/2021-01-04-how-i-turned-my-goodreads-data-into-a-self-hosted-website-with-eleventy
{
"type": "entry",
"published": "2021-01-07T18:17:46-0500",
"summary": "\ud83d\udd16 Bookmarked How I turned my Goodreads data into a self-hosted website with Eleventy https://hiddedevries.nl/en/blog/2021-01-04-how-i-turned-my-goodreads-data-into-a-self-hosted-website-with-eleventy",
"url": "https://martymcgui.re/2021/01/07/how-i-turned-my-goodreads-data-into-a-self-hosted-website-with-eleventy/",
"category": [
"goodreads",
"IndieWeb",
"ownyourdata"
],
"bookmark-of": [
"https://hiddedevries.nl/en/blog/2021-01-04-how-i-turned-my-goodreads-data-into-a-self-hosted-website-with-eleventy"
],
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "bookmark",
"_id": "17567148",
"_source": "175",
"_is_read": true
}
{
"type": "entry",
"published": "2021-01-06T10:13:25-08:00",
"url": "https://aaronparecki.com/2021/01/06/7/indieweb",
"category": [
"indieweb"
],
"syndication": [
"https://twitter.com/aaronpk/status/1346882587000664064"
],
"content": {
"text": "Live now! \ud83c\udf99 @allie_nimmons and @DavidWolfpaw chatting all about the #IndieWeb! https://youtu.be/i6Ixyi_I9g4",
"html": "Live now! \ud83c\udf99 <a href=\"https://twitter.com/allie_nimmons\">@allie_nimmons</a> and <a href=\"https://twitter.com/DavidWolfpaw\">@DavidWolfpaw</a> chatting all about the <a href=\"https://aaronparecki.com/tag/indieweb\">#IndieWeb</a>! <a href=\"https://youtu.be/i6Ixyi_I9g4\"><span>https://</span>youtu.be/i6Ixyi_I9g4</a>"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/41061f9de825966faa22e9c42830e1d4a614a321213b4575b9488aa93f89817a.jpg"
},
"post-type": "note",
"_id": "17527851",
"_source": "16",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": null,
"url": "https://dri.es/",
"photo": null
},
"url": "https://dri.es/can-someone-add-some-more-html-tags-please",
"published": "2021-01-06T04:39:12-05:00",
"content": {
"html": "<p>Every day, millions of new web pages are added to the internet. Most of them are unstructured, uncategorized, and nearly impossible for software to understand. It irks me.</p>\n\n<p>Look no further than <a href=\"https://en.wikipedia.org/wiki/Tim_Berners-Lee\">Sir Tim Berners-Lee's Wikipedia page</a>:</p>\n\n\n<img src=\"https://dri.es/files/images/blog/wikipedia-timbl-markup.png\" alt=\"The markup for Tim Berners-Lee's Wikipedia page; it's complex and inconsistent\" title=\"Tim Berners-Lee's Wikipedia page: HMTL code\" /><em>What Wikipedia editors write (<a href=\"https://en.wikipedia.org/w/index.php?title=Tim_Berners-Lee&action=edit\">source</a>).</em><img src=\"https://dri.es/files/images/blog/wikipedia-timbl-page.png\" alt=\"The browser output for Tim Berners-Lee's Wikipedia page\" title=\"Tim Berners-Lee's Wikipedia page: rendered page\" /><em>What visitors of Wikipedia see.</em><p>At first glance, there is <a href=\"http://blog.spencermounta.in/2019/wikipedias-in-trouble/index.html\">no rhyme or reason to Wikipedia's markup</a>. (Wikipedia also has <a href=\"https://en.wikipedia.org/wiki/Help:WikiHiero_syntax\">custom markup for hieroglyphs</a>, which admittedly <em>is</em> pretty cool.)</p>\n\n<p>The problem? Wikipedia is the world's largest source of knowledge. It's a top 10 website in the world. Yet, Wikipedia's markup language is <a href=\"http://blog.spencermounta.in/2019/wikipedias-in-trouble/index.html\">nearly impossible to parse</a>, Tim Berners-Lee's Wikipedia page has <a href=\"https://validator.w3.org/nu/?doc=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FTim_Berners-Lee\">almost 100 HTML validation errors</a>, and the page's generated HTML output is not very semantic. It's hard to use or re-use with other software.</p>\n\n<p>I bet it irks Sir Tim Berners-Lee too.</p>\n\n\n<img src=\"https://dri.es/files/images/blog/wikipedia-timbl-markup.png\" alt=\"The markup for Tim Berners-Lee's Wikipedia page; it's complex and inconsistent\" title=\"Tim Berners-Lee's Wikipedia page: HMTL code\" /><em>What Wikipedia editors write (<a href=\"https://en.wikipedia.org/w/index.php?title=Tim_Berners-Lee&action=edit\">source</a>).</em><img src=\"https://dri.es/files/images/blog/wikipedia-timbl-html.png\" alt=\"The generated HTML code for Tim Berners-Lee's Wikipedia page; it could be more semantic\" title=\"Tim Berners-Lee's Wikipedia page: generated HTML code\" /><em>What the browser sees; the HTML code Wikipedia (MediaWiki) generates.</em><p>It's not just Wikipedia. Every site is still messing around with custom <code>s for a table of contents, footnotes, logos, and more. I could think of a dozen new HTML tags that would make web pages, including Wikipedia, easier to write and reuse: , , , and many more.\n\n</code></p><p><code>A good approach would be to take the most successful <a href=\"https://en.wikipedia.org/wiki/Schema.org\">Schema.org schemas</a>, <a href=\"http://microformats.org/\">Microformats</a> and <a href=\"https://en.wikipedia.org/wiki/Web_Components\">Web Components</a>, and incorporate their functionality into the <a href=\"https://html.spec.whatwg.org/\">official HTML specification</a>.</code></p><code>\n\n</code><p><code>Adding new semantic markup options to <em>the</em> HTML specification is the surest way to improve the semantic web, improve content reuse, and advance content authoring tools.</code></p><code> \n\n</code><p><code>Unfortunately, I don't see new tags being introduced. I don't see experiments with <a href=\"https://en.wikipedia.org/wiki/Web_Components\">Web Components</a> being promoted to official standards. I hope I'm wrong! (<a href=\"https://meta.wikimedia.org/wiki/Cunningham%27s_Law\">Cunningham's Law</a> states that <q>the best way to get the right answer on the internet is not to ask a question; it's to post the wrong answer</q>. If I'm wrong, I'll update this poost.)</code></p><code>\n \n</code><p><code>If you want to help make the web better, you could literally start with <a href=\"https://en.wikipedia.org/wiki/Tim_Berners-Lee\">Sir Tim Berners-Lee's Wikipedia page</a>, and use it as the basis to spend a decade <a href=\"https://github.com/whatwg/html/commits\">pushing for HTML markup improvements</a>. It could be the <a href=\"http://1997.webhistory.org/www.lists/www-talk.1993q1/0182.html\">start of a long and successful career</a>.</code></p><code></code>",
"text": "Every day, millions of new web pages are added to the internet. Most of them are unstructured, uncategorized, and nearly impossible for software to understand. It irks me.\n\nLook no further than Sir Tim Berners-Lee's Wikipedia page:\n\n\nWhat Wikipedia editors write (source).What visitors of Wikipedia see.At first glance, there is no rhyme or reason to Wikipedia's markup. (Wikipedia also has custom markup for hieroglyphs, which admittedly is pretty cool.)\n\nThe problem? Wikipedia is the world's largest source of knowledge. It's a top 10 website in the world. Yet, Wikipedia's markup language is nearly impossible to parse, Tim Berners-Lee's Wikipedia page has almost 100 HTML validation errors, and the page's generated HTML output is not very semantic. It's hard to use or re-use with other software.\n\nI bet it irks Sir Tim Berners-Lee too.\n\n\nWhat Wikipedia editors write (source).What the browser sees; the HTML code Wikipedia (MediaWiki) generates.It's not just Wikipedia. Every site is still messing around with custom s for a table of contents, footnotes, logos, and more. I could think of a dozen new HTML tags that would make web pages, including Wikipedia, easier to write and reuse: , , , and many more.\n\nA good approach would be to take the most successful Schema.org schemas, Microformats and Web Components, and incorporate their functionality into the official HTML specification.\n\nAdding new semantic markup options to the HTML specification is the surest way to improve the semantic web, improve content reuse, and advance content authoring tools. \n\nUnfortunately, I don't see new tags being introduced. I don't see experiments with Web Components being promoted to official standards. I hope I'm wrong! (Cunningham's Law states that the best way to get the right answer on the internet is not to ask a question; it's to post the wrong answer. If I'm wrong, I'll update this poost.)\n \nIf you want to help make the web better, you could literally start with Sir Tim Berners-Lee's Wikipedia page, and use it as the basis to spend a decade pushing for HTML markup improvements. It could be the start of a long and successful career."
},
"name": "Can someone add some more HTML tags, please?",
"post-type": "article",
"_id": "17522110",
"_source": "238",
"_is_read": true
}
{
"type": "entry",
"published": "2021-01-05T12:26:11.552Z",
"url": "https://www.jvt.me/mf2/2021/01/iniue/",
"category": [
"homebrew-website-club"
],
"content": {
"text": "Reminder that it's #HomebrewWebsiteClub Nottingham tomorrow! I hope to see you there at 1730 for some website stuff! https://events.indieweb.org/2021/01/homebrew-website-club-nottingham-rVrKwhxmCz4D",
"html": "<p>Reminder that it's <a href=\"https://www.jvt.me/tags/homebrew-website-club/\">#HomebrewWebsiteClub</a> Nottingham tomorrow! I hope to see you there at 1730 for some website stuff! <a href=\"https://events.indieweb.org/2021/01/homebrew-website-club-nottingham-rVrKwhxmCz4D\">https://events.indieweb.org/2021/01/homebrew-website-club-nottingham-rVrKwhxmCz4D</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": "17496520",
"_source": "2169",
"_is_read": true
}
A rant from Robin. I share his frustration and agree with his observations.
I wonder how we can get the best of both worlds here: the ease of publishing newsletters, with all the beauty and archivability of websites.
{
"type": "entry",
"published": "2021-01-04T18:29:51Z",
"url": "https://adactio.com/links/17735",
"category": [
"newsletters",
"publishing",
"indieweb",
"rss",
"notifications",
"payments",
"subscriptions",
"writing",
"sharing",
"rant"
],
"bookmark-of": [
"https://www.robinrendle.com/essays/newsletters"
],
"content": {
"text": "Robin Rendle \u203a Newsletters\n\n\n\nA rant from Robin. I share his frustration and agree with his observations.\n\n\n I wonder how we can get the best of both worlds here: the ease of publishing newsletters, with all the beauty and archivability of websites.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://www.robinrendle.com/essays/newsletters\">\nRobin Rendle \u203a Newsletters\n</a>\n</h3>\n\n<p>A rant from Robin. I share his frustration and agree with his observations.</p>\n\n<blockquote>\n <p>I wonder how we can get the best of both worlds here: the ease of publishing newsletters, with all the beauty and archivability of websites.</p>\n</blockquote>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "bookmark",
"_id": "17481383",
"_source": "2",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "fluffy",
"url": "http://beesbuzz.biz/",
"photo": null
},
"url": "http://beesbuzz.biz/blog/11795-2021-goals",
"published": "2021-01-01T13:14:19-08:00",
"content": {
"html": "<p>Let\u2019s not call them resolutions.</p><p>One year ago I <a href=\"http://beesbuzz.biz/blog/7306-Happy-2020\">set out some goals for the next decade</a>. They\u2019re all pretty good goals. But here\u2019s some specific things I\u2019d like to accomplish over the next year:</p>\n<ul><li>Get my voice to a spot where people don\u2019t misgender me quite so much</li>\n<li>Get my fibromyalgia and ADHD meds dialed in (so far so good)</li>\n<li>Actually finish my next non-Novembeat album<a href=\"http://beesbuzz.biz/blog/11795-2021-goals#d_e11795_fn1\">1</a></li>\n<li><a href=\"https://plaidweb.site/\">PlaidWeb</a> things, such as:\n\n<ul><li>An online post editor</li>\n<li>A self-hosted notification engine (for webmention, activitypub, websub, etc.)</li>\n<li>Maybe actually write some actual <em>code</em> for Subl?</li>\n<li>Also maybe actually put a dang site together for PlaidWeb</li>\n</ul></li>\n<li>Rebuild my broken social life</li>\n<li>Get my home clean, and <em>keep</em> it clean</li>\n<li>Start drawing comics regularly again</li>\n<li>And the ever-present goal of losing, say, 15 pounds</li>\n</ul><p>Kind of ambitious, I know, but it\u2019s better to aim for the stars and hit the moon than to never even leave the ground.</p>\n\n\n\n\n<ol><li><p>I've been meaning to finish this album \"real soon\" for the last 5 years so I'm not terribly optimistic about this one <a href=\"http://beesbuzz.biz/blog/11795-2021-goals#r_e11795_fn1\">\u21a9</a></p></li></ol><p><a href=\"http://beesbuzz.biz/blog/11795-2021-goals#comments\">comments</a></p>",
"text": "Let\u2019s not call them resolutions.One year ago I set out some goals for the next decade. They\u2019re all pretty good goals. But here\u2019s some specific things I\u2019d like to accomplish over the next year:\nGet my voice to a spot where people don\u2019t misgender me quite so much\nGet my fibromyalgia and ADHD meds dialed in (so far so good)\nActually finish my next non-Novembeat album1\nPlaidWeb things, such as:\n\nAn online post editor\nA self-hosted notification engine (for webmention, activitypub, websub, etc.)\nMaybe actually write some actual code for Subl?\nAlso maybe actually put a dang site together for PlaidWeb\n\nRebuild my broken social life\nGet my home clean, and keep it clean\nStart drawing comics regularly again\nAnd the ever-present goal of losing, say, 15 pounds\nKind of ambitious, I know, but it\u2019s better to aim for the stars and hit the moon than to never even leave the ground.\n\n\n\n\nI've been meaning to finish this album \"real soon\" for the last 5 years so I'm not terribly optimistic about this one \u21a9comments"
},
"name": "fluffy rambles: 2021 goals",
"post-type": "article",
"_id": "17432127",
"_source": "3782",
"_is_read": true
}
{
"type": "entry",
"published": "2020-12-31T17:03:52Z",
"url": "https://adactio.com/journal/17727",
"category": [
"2020",
"writing",
"blogging",
"publishing",
"words",
"sharing",
"indieweb"
],
"syndication": [
"https://adactio.medium.com/c85d9760048"
],
"name": "2020 in numbers",
"content": {
"text": "I posted to adactio.com 1442 times in 2020. sparkline\n\nMarch was the busiest month with 184 posts. sparkline\n\nThis month, December, was the quietest with 68 posts. sparkline\n\nOverall I published:\n\n\n2 articles,\n\n110 blog posts, sparkline\n\n518 links, sparkline\n\n812 notes. sparkline\nIn amongst those notes are 128 photos. But the number I\u2019m happiest with is 200. From to March 18th to October 3rd, I posted a tune a day for 200 days straight.\n\nElsewhere in 2020:\n\nI huffduffed 187 pieces of audio,\nmade 1,139 contributions on Github, and\npublished 6 episodes of the Clearleft podcast.\nFor obvious reasons, in 2020 I had far fewer check ins, did far less speaking and almost no travel.",
"html": "<p>I posted to adactio.com <a href=\"https://adactio.com/archive/2020\">1442 times in 2020</a>. sparkline</p>\n\n<p>March was the busiest month with <a href=\"https://adactio.com/archive/2020/03\">184 posts</a>. sparkline</p>\n\n<p>This month, December, was the quietest with <a href=\"https://adactio.com/archive/2020/12\">68 posts</a>. sparkline</p>\n\n<p>Overall I published:</p>\n\n<ul><li>\n<a href=\"https://adactio.com/articles#in2020\">2 articles</a>,</li>\n<li>\n<a href=\"https://adactio.com/journal/archive/2020/\">110 blog posts</a>, sparkline</li>\n<li>\n<a href=\"https://adactio.com/links/archive/2020\">518 links</a>, sparkline</li>\n<li>\n<a href=\"https://adactio.com/notes/archive/2020\">812 notes</a>. sparkline</li>\n</ul><p>In amongst those notes are <a href=\"https://adactio.com/notes/photos/2020\">128 photos</a>. But the number I\u2019m happiest with is <a href=\"https://adactio.com/journal/17489\">200</a>. From to <a href=\"https://adactio.com/notes/16547\">March 18th</a> to <a href=\"https://adactio.com/notes/17487\">October 3rd</a>, I posted <a href=\"https://adactio.com/notes/tunes\">a tune a day for 200 days straight</a>.</p>\n\n<p>Elsewhere in 2020:</p>\n\n<ul><li>I huffduffed <a href=\"https://huffduffer.com/adactio\">187 pieces of audio</a>,</li>\n<li>made <a href=\"https://github.com/adactio?tab=overview&from=2020-01-01&to=2020-12-31\">1,139 contributions on Github</a>, and</li>\n<li>published <a href=\"https://podcast.clearleft.com/season01/\">6 episodes of the Clearleft podcast</a>.</li>\n</ul><p>For obvious reasons, in 2020 I had far fewer <a href=\"https://adactio.com/notes/checkins/2020\">check ins</a>, did far less <a href=\"https://adactio.com/about/speaking/#in2020\">speaking</a> and almost no <a href=\"https://adactio.com/notes/travel/2020\">travel</a>.</p>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "article",
"_id": "17407151",
"_source": "2",
"_is_read": true
}
{
"type": "entry",
"published": "2020-12-31T09:59:53Z",
"url": "https://adactio.com/journal/17723",
"category": [
"2020",
"writing",
"blogging",
"publishing",
"words",
"sharing",
"indieweb"
],
"syndication": [
"https://adactio.medium.com/543ab10f53f9"
],
"name": "Words I wrote in 2020",
"content": {
"text": "Once again I wrote over a hundred blog posts this year. While lots of other activities dropped off significantly while my main focus was to just keep on keepin\u2019 on, I still found solace and reward in writing and publishing. Like I said early on in The Situation, my website is an outlet for me:\n\n\n While you\u2019re stuck inside, your website is not just a place you can go to, it\u2019s a place you can control, a place you can maintain, a place you can tidy up, a place you can expand. Most of all, it\u2019s a place you can lose yourself in, even if it\u2019s just for a little while.\n\n\nHere are some blog posts that turned out alright:\n\n\nArchitects, gardeners, and design systems. Citing Frank Chimero, Debbie Chachra, and Lisa O\u2019Neill. \n\nHydration. Progressive enhancement. I do not think it means what you think it means.\n\nLiving Through The Future. William Gibson, Arthur C.Clarke, Daniel Dafoe, Stephen King, Emily St. John Mandel, John Wyndham, Martin Cruz-Smith, Marina Koren and H.G. Wells.\n\nPrinciples and priorities. Using design principles to embody your priorities.\n\nHard to break. Brittleness is the opposite of resilience. But they both share something in common.\n\nIntent. Black lives matter.\n\nAccessibility. Making the moral argument.\n\nT E N \u018e T. A spoiler-filled look at the new Christopher Nolan film.\n\nPortals and giant carousels. Trying to understand why people think they need to make single page apps.\n\nClean advertising. The greatest trick the devil ever pulled was convincing the world that behavioural advertising is more effective than contextual advertising.\nI find it strangely comforting that even in a year as shitty as 2020, I can look back and see that there were some decent blog posts in there. Whatever 2021 may bring, I hope to keep writing and publishing through it all. I hope you will too.",
"html": "<p><a href=\"https://adactio.com/journal/16270\">Once again</a> I wrote <a href=\"https://adactio.com/journal/archive/2020/\">over a hundred blog posts this year</a>. While lots of other activities dropped off significantly while my main focus was to just keep on keepin\u2019 on, I still found solace and reward in writing and publishing. Like I said early on in The Situation, <a href=\"https://adactio.com/journal/16585\">my website is an outlet for me</a>:</p>\n\n<blockquote>\n <p>While you\u2019re stuck inside, your website is not just a place you can go to, it\u2019s a place you can control, a place you can maintain, a place you can tidy up, a place you can expand. Most of all, it\u2019s a place you can lose yourself in, even if it\u2019s just for a little while.</p>\n</blockquote>\n\n<p>Here are some blog posts that turned out alright:</p>\n\n<ul><li>\n<a href=\"https://adactio.com/journal/16369\">Architects, gardeners, and design systems</a>. Citing Frank Chimero, Debbie Chachra, and Lisa O\u2019Neill. </li>\n<li>\n<a href=\"https://adactio.com/journal/16404\">Hydration</a>. Progressive enhancement. I do not think it means what you think it means.</li>\n<li>\n<a href=\"https://adactio.com/journal/16655\">Living Through The Future</a>. William Gibson, Arthur C.Clarke, Daniel Dafoe, Stephen King, Emily St. John Mandel, John Wyndham, Martin Cruz-Smith, Marina Koren and H.G. Wells.</li>\n<li>\n<a href=\"https://adactio.com/journal/16811\">Principles and priorities</a>. Using design principles to embody your priorities.</li>\n<li>\n<a href=\"https://adactio.com/journal/16910\">Hard to break</a>. Brittleness is the opposite of resilience. But they both share something in common.</li>\n<li>\n<a href=\"https://adactio.com/journal/16986\">Intent</a>. Black lives matter.</li>\n<li>\n<a href=\"https://adactio.com/journal/17132\">Accessibility</a>. Making the moral argument.</li>\n<li>\n<a href=\"https://adactio.com/journal/17379\">T E N \u018e T</a>. A spoiler-filled look at the new Christopher Nolan film.</li>\n<li>\n<a href=\"https://adactio.com/journal/17573\">Portals and giant carousels</a>. Trying to understand why people think they need to make single page apps.</li>\n<li>\n<a href=\"https://adactio.com/journal/17658\">Clean advertising</a>. The greatest trick the devil ever pulled was convincing the world that behavioural advertising is more effective than contextual advertising.</li>\n</ul><p>I find it strangely comforting that even in a year as shitty as 2020, I can look back and see that there were some decent blog posts in there. Whatever 2021 may bring, I hope to keep writing and publishing through it all. I hope you will too.</p>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "article",
"_id": "17400748",
"_source": "2",
"_is_read": true
}
I’ve decided. My website is in need of an overhaul. I like the concept of cultivating a digital garden whilst also combining some of the social aspects of the IndieWeb, so in the New Year I’ll don my gloves, a trowel and see how I get on!
{
"type": "entry",
"author": {
"name": "Scott Mallinson",
"url": "https://scottmallinson.com",
"photo": "https://www.gravatar.com/avatar/d4b20e750343ea81591989575e3b762b?s=96&d=https%3A%2F%2Fmicro.blog%2Fimages%2Fblank_avatar.png"
},
"url": "https://scottmallinson.com/blog/2020/12/30/im-going-to-start-gardening-in-the-new-year/",
"content": {
"html": "<p>I\u2019ve decided. <a href=\"https://scottmallinson.com\">My website</a> is in need of an overhaul. I like the concept of cultivating a <a href=\"https://maggieappleton.com/garden-history\">digital garden</a>\u00a0whilst also combining some of the social aspects of the <a href=\"https://indieweb.org/\">IndieWeb</a>, so in the New Year I\u2019ll don my gloves, a trowel and see how I get on!</p>",
"text": "I\u2019ve decided. My website is in need of an overhaul. I like the concept of cultivating a digital garden\u00a0whilst also combining some of the social aspects of the IndieWeb, so in the New Year I\u2019ll don my gloves, a trowel and see how I get on!"
},
"published": "2020-12-30T15:41:22+00:00",
"post-type": "note",
"_id": "33380032",
"_source": "7224",
"_is_read": true
}
I couldn't sleep so got up for a drink and did a little more work on the non-WordPress version of the.
It's still intrinsically linked to WordPress because it currently just retrieves the post sections from the database that are created within the main site but, ultimately, I'd like to make it a fully self-contained system.
I'll need to sort out some kind of functionality for logging in and will need to rethink posting and how sections are stored. What will be a little more problematic is working out commenting should I decide to include it.
I would also lose webmentions because my coding skills really don't extend as far as rolling my own solution for that. This, in turn, means that I would lose the current "related posts" feature.
I'm not entirely sure where I'm going with all of this, or what compromises I'm willing to make, but it would be nice to be able to say I use my own blogging engine.
{
"type": "entry",
"author": {
"name": "Colin Walker",
"url": "https://colinwalker.blog/",
"photo": null
},
"url": "https://colinwalker.blog/27-12-2020-0717/",
"published": "2020-12-27T07:17:00+00:00",
"content": {
"html": "<p>I couldn't sleep so got up for a drink and did a little more work on the <a href=\"https://colinwalker.blog/blog.php\">non-WordPress version of the</a>.</p>\n<p>It's still intrinsically linked to WordPress because it currently just retrieves the post sections from the database that are created within the main site but, ultimately, I'd like to make it a fully self-contained system.</p>\n<p>I'll need to sort out some kind of functionality for logging in and will need to rethink posting and how sections are stored. What will be a little more problematic is working out commenting should I decide to include it.</p>\n<p>I would also lose webmentions because my coding skills really don't extend as far as rolling my own solution for that. This, in turn, means that I would lose the current \"related posts\" feature.</p>\n<p>I'm not entirely sure where I'm going with all of this, or what compromises I'm willing to make, but it would be nice to be able to say I use my own blogging engine.</p>",
"text": "I couldn't sleep so got up for a drink and did a little more work on the non-WordPress version of the.\nIt's still intrinsically linked to WordPress because it currently just retrieves the post sections from the database that are created within the main site but, ultimately, I'd like to make it a fully self-contained system.\nI'll need to sort out some kind of functionality for logging in and will need to rethink posting and how sections are stored. What will be a little more problematic is working out commenting should I decide to include it.\nI would also lose webmentions because my coding skills really don't extend as far as rolling my own solution for that. This, in turn, means that I would lose the current \"related posts\" feature.\nI'm not entirely sure where I'm going with all of this, or what compromises I'm willing to make, but it would be nice to be able to say I use my own blogging engine."
},
"post-type": "note",
"_id": "17324483",
"_source": "237",
"_is_read": true
}
I’ve released version 0.0.3 of mf2 to iCalendar, a library to convert h-event microformats into iCalendar.
It no longer throws an Exception if no h-event microformats are found. Instead it will generate a minimal, “empty” iCalendar. I had run into an instance where an upcoming events page was empty and the URL for the iCalendar was returning the Exception message.
I also changed the default domain to example.com, did some minor code cleanup, and renamed the git master branch to main.
Previously
{
"type": "entry",
"published": "2020-12-23 11:40-0800",
"url": "https://gregorlove.com/2020/12/ive-released-version/",
"category": [
"indieweb",
"microformats"
],
"content": {
"text": "I\u2019ve released version 0.0.3 of mf2 to iCalendar, a library to convert h-event microformats into iCalendar.\n\nIt no longer throws an Exception if no h-event microformats are found. Instead it will generate a minimal, \u201cempty\u201d iCalendar. I had run into an instance where an upcoming events page was empty and the URL for the iCalendar was returning the Exception message.\n\nI also changed the default domain to example.com, did some minor code cleanup, and renamed the git master branch to main.\n\nPreviously",
"html": "<p>I\u2019ve released version 0.0.3 of <a href=\"https://github.com/gRegorLove/mf2-to-iCalendar\">mf2 to iCalendar</a>, a library to convert h-event microformats into iCalendar.</p>\n\n<p>It no longer throws an Exception if no h-event microformats are found. Instead it will generate a minimal, \u201cempty\u201d iCalendar. I had run into an instance where an upcoming events page was empty and the URL for the iCalendar was returning the Exception message.</p>\n\n<p>I also changed the default domain to example.com, did some minor code cleanup, and renamed the git master branch to main.</p>\n\n<p><a href=\"https://gregorlove.com/2018/03/new-release-of-mf2-to-icalendar/\">Previously</a></p>"
},
"author": {
"type": "card",
"name": "gRegor Morrill",
"url": "https://gregorlove.com/",
"photo": "https://gregorlove.com/site/assets/files/3473/profile-2016-med.jpg"
},
"post-type": "note",
"_id": "17270699",
"_source": "95",
"_is_read": true
}
