#Substack’s financials are… suspect. Plus, the platform doesn’t seem interested in an open #IndieWeb future. So, I’m building a life raft. Read about how in today’s newsletter.
{
"type": "entry",
"author": {
"name": "@justin",
"url": "https://beige.party/@justin",
"photo": null
},
"url": "https://beige.party/@justin/110179926915017830",
"content": {
"html": "<p><a href=\"https://beige.party/tags/Substack\">#<span>Substack</span></a>\u2019s financials are\u2026 suspect. Plus, the platform doesn\u2019t seem interested in an open <a href=\"https://beige.party/tags/IndieWeb\">#<span>IndieWeb</span></a> future. So, I\u2019m building a life raft. Read about how in today\u2019s newsletter. </p><p><a href=\"https://justincox.com/blog/2023/04/we-have-to-talk-about-substack/\"><span>https://</span><span>justincox.com/blog/2023/04/we-</span><span>have-to-talk-about-substack/</span></a></p>",
"text": "#Substack\u2019s financials are\u2026 suspect. Plus, the platform doesn\u2019t seem interested in an open #IndieWeb future. So, I\u2019m building a life raft. Read about how in today\u2019s newsletter. https://justincox.com/blog/2023/04/we-have-to-talk-about-substack/"
},
"published": "2023-04-11T11:24:23+00:00",
"post-type": "note",
"_id": "36470904",
"_source": "7235",
"_is_read": true
}
New blog post up, where I talk about how I discovered the indie web and how it makes me feel. Inspired by a podcast and an article. For the link to the latter, thank you to @lostletters@social.yesterweb.org!
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://calckey.social/notes/9dfnp6dyom",
"content": {
"html": "<p><span>New blog post up, where I talk about how I discovered the indie web and how it makes me feel.<br />Inspired by a podcast and an article. For the link to the latter, thank you to </span><a class=\"u-url\" href=\"https://social.yesterweb.org/@lostletters\">@lostletters@social.yesterweb.org</a><span>!<br /><br /></span><a href=\"https://calckey.social/tags/IndieWeb\">#IndieWeb</a><span> </span><a href=\"https://calckey.social/tags/PersonalWebsite\">#PersonalWebsite</a><span> </span><a href=\"https://calckey.social/tags/neocities\">#neocities</a><span> </span><a href=\"https://calckey.social/tags/DigitalGardens\">#DigitalGardens</a><span> </span><a href=\"https://calckey.social/tags/PersonalBlog\">#PersonalBlog</a><span><br /><br /></span><a href=\"https://theresmiling.neocities.org/blog/2023/04/jungles-and-gardens\">https://theresmiling.neocities.org/blog/2023/04/jungles-and-gardens</a></p>",
"text": "New blog post up, where I talk about how I discovered the indie web and how it makes me feel.\nInspired by a podcast and an article. For the link to the latter, thank you to @lostletters@social.yesterweb.org!\n\n#IndieWeb #PersonalWebsite #neocities #DigitalGardens #PersonalBlog\n\nhttps://theresmiling.neocities.org/blog/2023/04/jungles-and-gardens"
},
"published": "2023-04-11T10:00:45+00:00",
"post-type": "note",
"_id": "36469461",
"_source": "7235",
"_is_read": true
}
About three weeks ago I got auto-linked hashtags working on my posts.
The biggest challenge was picking a tag space to link my hashtags.
The second biggest challenge was figuring out how to get my linked hashtags to work when my posts were federated into Mastodon instances, and have them rewrite those links into instance-local tag page links. We need a term for such locally rewritten linked hashtags, perhaps “federated hashtags”.
While typical personal sites link a hashtag to a tag page that only displays personal posts, I wanted to link to something more like a tag aggregation page that also displayed similar posts from others.
The tag pages on Mastodon instances do a good job of this, showing tagged posts from any user on that instance, and tagged posts from any user followed by any user on that instance.
I reviewed my hashtags since the start of 2023, checked their pages on indieweb.social and found that the posts displayed were all on topic, and surprisingly free of tag spam (perhaps for now).
I chose https://indieweb.social/tags/ for my tag space (which is a 404 if you click it, where it really should display a tags page listing popular or recent tags or a tag cloud).
The other interesting thing about hashtag links is how they’re rewritten when a post is displayed on another Mastodon instance, to link to the tag page local to that instance.
This linked-hashtag-portability is underspecified unfortunately (it could probably use its own portable markup specification, or at least a best practice for h-entry publishing).
Thus even though I’m using the indieweb.social tag space on the hashtag links in my original post, if you are reading this post on Mastodon, you should see a hashtag like #IndieWeb link to your local instance’s tag page for IndieWeb, and my post should show up on that page.
I did go back and send Webmentions to BridgyFed to send ActivityPub updates for all my past #100DaysofIndieWeb posts, however only a few of them showed up in those tag pages. It’s unclear why a few did and most didn’t, or why there are inconsistencies across instances. More to explore and debug.
Federated hashtags definitely need their own specification, because currently they barely interoperate when published, and even then require Mastodon-implementation-specific knowledge to function.
The good news is that several of us now have linked hashtags on our personal sites display and link as expected when our posts are federated across Mastodon instances, using a variety of different pieces of software to make it all work.
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://fed.brid.gy/r/https://tantek.com/2023/100/t1/auto-linked-hashtags-federated",
"content": {
"html": "About three weeks ago I got auto-linked hashtags working on my posts.<br /><br />The biggest challenge was picking a tag space to link my hashtags. <br /><br />The second biggest challenge was figuring out how to get my linked hashtags to work when my posts were federated into Mastodon instances, and have them rewrite those links into instance-local tag page links. We need a term for such locally rewritten linked hashtags, perhaps \u201cfederated hashtags\u201d.<br /><br />While typical personal sites link a hashtag to a tag page that only displays personal posts, I wanted to link to something more like a tag aggregation page that also displayed similar posts from others.<br /><br />The tag pages on Mastodon instances do a good job of this, showing tagged posts from any user on that instance, and tagged posts from any user followed by any user on that instance.<br /><br />I reviewed my hashtags since the start of 2023, checked their pages on <a href=\"http://indieweb.social\">indieweb.social</a> and found that the posts displayed were all on topic, and surprisingly free of tag spam (perhaps for now).<br /><br />I chose <a href=\"https://indieweb.social/tags/\">https://indieweb.social/tags/</a> for my tag space (which is a 404 if you click it, where it really should display a tags page listing popular or recent tags or a tag cloud). <br /><br />Combining a hashtag like <a href=\"https://indieweb.social/tags/100DaysOfIndieWeb\">#<span class=\"p-category\">100DaysOfIndieWeb</span></a> with a tag space produces a link to a tag page like: <a href=\"https://indieweb.social/tags/100DaysOfIndieWeb\">https://indieweb.social/tags/100DaysOfIndieWeb</a>.<br /><br />The other interesting thing about hashtag links is how they\u2019re rewritten when a post is displayed on another Mastodon instance, to link to the tag page local to that instance. <br /><br />This linked-hashtag-portability is underspecified unfortunately (it could probably use its own portable markup specification, or at least a best practice for h-entry publishing).<br /><br />How it works in Mastodon is non-obvious enough that there\u2019s a 4+ year old Bridgy Fed issue on the subject!<br />* <a href=\"https://github.com/snarfed/bridgy-fed/issues/45\">https://github.com/snarfed/bridgy-fed/issues/45</a><br /><br />With a bunch of research and experiment contributions from several folks in the issue, <a href=\"https://snarfed.org\">@snarfed.org</a> (<a class=\"h-cassis-username\" href=\"https://twitter.com/schnarfed\">@schnarfed</a>) did eventually figure out how to get Bridgy Fed to federate hashtags in posts into Mastodon instances so they would rewrite hashtag links into instance-local hashtag pages:<br />* <a href=\"https://github.com/snarfed/bridgy-fed/issues/45#issuecomment-1468962400\">https://github.com/snarfed/bridgy-fed/issues/45#issuecomment-1468962400</a><br /><br />Thus even though I\u2019m using the <a href=\"http://indieweb.social\">indieweb.social</a> tag space on the hashtag links in my original post, if you are reading this post on Mastodon, you should see a hashtag like <a href=\"https://indieweb.social/tags/IndieWeb\">#<span class=\"p-category\">IndieWeb</span></a> link to your local instance\u2019s tag page for IndieWeb, and my post should show up on that page.<br /><br />From testing a few other instances tag pages, this is now working, e.g. these tag pages:<br />* <a href=\"https://indieweb.social/tags/100DaysofIndieWeb\">https://indieweb.social/tags/100DaysofIndieWeb</a> (as expected)<br />* <a href=\"https://xoxo.zone/tags/100DaysOfIndieWeb\">https://xoxo.zone/tags/100DaysOfIndieWeb</a><br />* <a href=\"https://mozilla.social/tags/100DaysofIndieWeb\">https://mozilla.social/tags/100DaysofIndieWeb</a><br />display the <a href=\"https://indieweb.social/tags/MozFest\">#<span class=\"p-category\">MozFest</span></a> post\u00b9 I published right after implementing linked hashtags (and any subsequent 100DaysofIndieWeb posts).<br /><br />I did go back and send Webmentions to BridgyFed to send ActivityPub updates for all my past <a href=\"https://indieweb.social/tags/100DaysofIndieWeb\">#<span class=\"p-category\">100DaysofIndieWeb</span></a> posts, however only a few of them showed up in those tag pages. It\u2019s unclear why a few did and most didn\u2019t, or why there are inconsistencies across instances. More to explore and debug.<br /><br />Federated hashtags definitely need their own specification, because currently they barely interoperate when published, and even then require Mastodon-implementation-specific knowledge to function.<br /><br />The good news is that several of us now have linked hashtags on our personal sites display and link as expected when our posts are federated across Mastodon instances, using a variety of different pieces of software to make it all work.<br /><br /><br />This is day 36 of <a href=\"https://indieweb.social/tags/100DaysOfIndieWeb\">#<span class=\"p-category\">100DaysOfIndieWeb</span></a> <a href=\"https://indieweb.social/tags/100Days\">#<span class=\"p-category\">100Days</span></a><br /><br />\u2190 Day 35: <a href=\"https://tantek.com/2023/081/t1/mozfest-making-fediverse-socialweb\">https://tantek.com/2023/081/t1/mozfest-making-fediverse-socialweb</a><br />\u2192 \ud83d\udd2e<br /><br /><br />Glossary<br /><br />h-entry<br />\u00a0<a href=\"https://microformats.org/wiki/h-entry\">https://microformats.org/wiki/h-entry</a><br />hashtag<br />\u00a0<a href=\"https://indieweb.org/hashtags\">https://indieweb.org/hashtags</a><br />tag aggregation<br />\u00a0<a href=\"https://indieweb.org/tag_aggregation\">https://indieweb.org/tag_aggregation</a><br />tag page<br />\u00a0<a href=\"https://indieweb.org/tag_page\">https://indieweb.org/tag_page</a><br />tags page<br />\u00a0<a href=\"https://indieweb.org/tags_page\">https://indieweb.org/tags_page</a><br />\u00a0<br />References<br /><br />\u00b9 <a href=\"https://tantek.com/2023/081/t1/mozfest-making-fediverse-socialweb\">https://tantek.com/2023/081/t1/mozfest-making-fediverse-socialweb</a>",
"text": "About three weeks ago I got auto-linked hashtags working on my posts.\n\nThe biggest challenge was picking a tag space to link my hashtags. \n\nThe second biggest challenge was figuring out how to get my linked hashtags to work when my posts were federated into Mastodon instances, and have them rewrite those links into instance-local tag page links. We need a term for such locally rewritten linked hashtags, perhaps \u201cfederated hashtags\u201d.\n\nWhile typical personal sites link a hashtag to a tag page that only displays personal posts, I wanted to link to something more like a tag aggregation page that also displayed similar posts from others.\n\nThe tag pages on Mastodon instances do a good job of this, showing tagged posts from any user on that instance, and tagged posts from any user followed by any user on that instance.\n\nI reviewed my hashtags since the start of 2023, checked their pages on indieweb.social and found that the posts displayed were all on topic, and surprisingly free of tag spam (perhaps for now).\n\nI chose https://indieweb.social/tags/ for my tag space (which is a 404 if you click it, where it really should display a tags page listing popular or recent tags or a tag cloud). \n\nCombining a hashtag like #100DaysOfIndieWeb with a tag space produces a link to a tag page like: https://indieweb.social/tags/100DaysOfIndieWeb.\n\nThe other interesting thing about hashtag links is how they\u2019re rewritten when a post is displayed on another Mastodon instance, to link to the tag page local to that instance. \n\nThis linked-hashtag-portability is underspecified unfortunately (it could probably use its own portable markup specification, or at least a best practice for h-entry publishing).\n\nHow it works in Mastodon is non-obvious enough that there\u2019s a 4+ year old Bridgy Fed issue on the subject!\n* https://github.com/snarfed/bridgy-fed/issues/45\n\nWith a bunch of research and experiment contributions from several folks in the issue, @snarfed.org (@schnarfed) did eventually figure out how to get Bridgy Fed to federate hashtags in posts into Mastodon instances so they would rewrite hashtag links into instance-local hashtag pages:\n* https://github.com/snarfed/bridgy-fed/issues/45#issuecomment-1468962400\n\nThus even though I\u2019m using the indieweb.social tag space on the hashtag links in my original post, if you are reading this post on Mastodon, you should see a hashtag like #IndieWeb link to your local instance\u2019s tag page for IndieWeb, and my post should show up on that page.\n\nFrom testing a few other instances tag pages, this is now working, e.g. these tag pages:\n* https://indieweb.social/tags/100DaysofIndieWeb (as expected)\n* https://xoxo.zone/tags/100DaysOfIndieWeb\n* https://mozilla.social/tags/100DaysofIndieWeb\ndisplay the #MozFest post\u00b9 I published right after implementing linked hashtags (and any subsequent 100DaysofIndieWeb posts).\n\nI did go back and send Webmentions to BridgyFed to send ActivityPub updates for all my past #100DaysofIndieWeb posts, however only a few of them showed up in those tag pages. It\u2019s unclear why a few did and most didn\u2019t, or why there are inconsistencies across instances. More to explore and debug.\n\nFederated hashtags definitely need their own specification, because currently they barely interoperate when published, and even then require Mastodon-implementation-specific knowledge to function.\n\nThe good news is that several of us now have linked hashtags on our personal sites display and link as expected when our posts are federated across Mastodon instances, using a variety of different pieces of software to make it all work.\n\n\nThis is day 36 of #100DaysOfIndieWeb #100Days\n\n\u2190 Day 35: https://tantek.com/2023/081/t1/mozfest-making-fediverse-socialweb\n\u2192 \ud83d\udd2e\n\n\nGlossary\n\nh-entry\n\u00a0https://microformats.org/wiki/h-entry\nhashtag\n\u00a0https://indieweb.org/hashtags\ntag aggregation\n\u00a0https://indieweb.org/tag_aggregation\ntag page\n\u00a0https://indieweb.org/tag_page\ntags page\n\u00a0https://indieweb.org/tags_page\n\u00a0\nReferences\n\n\u00b9 https://tantek.com/2023/081/t1/mozfest-making-fediverse-socialweb"
},
"published": "2023-04-11T06:25:00+00:00",
"post-type": "note",
"_id": "36467782",
"_source": "7235",
"_is_read": true
}
About three weeks ago I got auto-linked hashtags working on my posts.
The biggest challenge was picking a tag space to link my hashtags.
The second biggest challenge was figuring out how to get my linked hashtags to work when my posts were federated into Mastodon instances, and have them rewrite those links into instance-local tag page links. We need a term for such locally rewritten linked hashtags, perhaps “federated hashtags”.
While typical personal sites link a hashtag to a tag page that only displays personal posts, I wanted to link to something more like a tag aggregation page that also displayed similar posts from others.
The tag pages on Mastodon instances do a good job of this, showing tagged posts from any user on that instance, and tagged posts from any user followed by any user on that instance.
I reviewed my hashtags since the start of 2023, checked their pages indieweb.social and found that the posts displayed were all on topic, and surprisingly free of tag spam (perhaps for now).
The other interesting thing about hashtag links is how they’re rewritten when a post is displayed on another Mastodon instance, to link to the tag page local to that instance.
This linked-hashtag-portability is underspecified unfortunately (it could probably use its own portable markup specification, or at least a best practice for h-entry publishing).
Thus even though I’m using the indieweb.social tag space on the hashtag links in my original post, if you are reading this post on Mastodon, you should see a hashtag like #IndieWeb link to your local instance’s tag page for IndieWeb, and my post should show up on that page.
I did go back and send Webmentions to BridgyFed send ActivityPub updates for all my past #100DaysofIndieWeb posts, however only a few of them showed up in those tag pages. It’s not why a few did and most didn’t, nor why there were inconsistencies across instances. More to explore and debug.
Federated hashtags definitely need their own specification, because currently they barely interoperate when published, and even then require Mastodon-implementation-specific knowledge to function.
{
"type": "entry",
"published": "2023-04-10 23:25-0700",
"url": "http://tantek.com/2023/100/t1/auto-linked-hashtags-federated",
"category": [
"100DaysOfIndieWeb",
"IndieWeb",
"MozFest",
"100DaysofIndieWeb",
"100Days"
],
"content": {
"text": "About three weeks ago I got auto-linked hashtags working on my posts.\n\nThe biggest challenge was picking a tag space to link my hashtags. \n\nThe second biggest challenge was figuring out how to get my linked hashtags to work when my posts were federated into Mastodon instances, and have them rewrite those links into instance-local tag page links. We need a term for such locally rewritten linked hashtags, perhaps \u201cfederated hashtags\u201d.\n\nWhile typical personal sites link a hashtag to a tag page that only displays personal posts, I wanted to link to something more like a tag aggregation page that also displayed similar posts from others.\n\nThe tag pages on Mastodon instances do a good job of this, showing tagged posts from any user on that instance, and tagged posts from any user followed by any user on that instance.\n\nI reviewed my hashtags since the start of 2023, checked their pages indieweb.social and found that the posts displayed were all on topic, and surprisingly free of tag spam (perhaps for now).\n\nI chose https://indieweb.social/tags/ for my tag space (which is a 404 if you click it, where it really should display a list of tags page). When combined with a hashtag like #100DaysOfIndieWeb, it links to https://indieweb.social/tags/100DaysOfIndieWeb.\n\nThe other interesting thing about hashtag links is how they\u2019re rewritten when a post is displayed on another Mastodon instance, to link to the tag page local to that instance. \n\nThis linked-hashtag-portability is underspecified unfortunately (it could probably use its own portable markup specification, or at least a best practice for h-entry publishing).\n\nHow it works in Mastodon is non-obvious enough that there\u2019s a 4+ year old Bridgy Fed issue on the subject!\n* https://github.com/snarfed/bridgy-fed/issues/45\n\nWith a bunch of research and experiment contributions from several folks in the issue, @snarfed.org (@schnarfed) did eventually figure out how to make hashtags in posts federate into Mastodon so it would rewrite their links into instance-local hashtag pages:\n* https://github.com/snarfed/bridgy-fed/issues/45#issuecomment-1468962400\n\nThus even though I\u2019m using the indieweb.social tag space on the hashtag links in my original post, if you are reading this post on Mastodon, you should see a hashtag like #IndieWeb link to your local instance\u2019s tag page for IndieWeb, and my post should show up on that page.\n\nFrom testing a few other instances tag pages, this is now working, e.g. these tag pages:\n* https://indieweb.social/tags/100DaysofIndieWeb (as expected)\n* https://xoxo.zone/tags/100DaysOfIndieWeb\n* https://mozilla.social/tags/100DaysofIndieWeb\ndisplays the #MozFest post I published right after implementing linked hashtags (as well as this post by the time you see this).\n\nI did go back and send Webmentions to BridgyFed send ActivityPub updates for all my past #100DaysofIndieWeb posts, however only a few of them showed up in those tag pages. It\u2019s not why a few did and most didn\u2019t, nor why there were inconsistencies across instances. More to explore and debug.\n\nFederated hashtags definitely need their own specification, because currently they barely interoperate when published, and even then require Mastodon-implementation-specific knowledge to function.\n\n\nThis is day 36 of #100DaysOfIndieWeb #100Days\n\n\u2190 Day 35: https://tantek.com/2023/081/t1/mozfest-making-fediverse-socialweb\n\u2192 \ud83d\udd2e\n\n\nGlossary\n\nh-entry\n\u00a0https://microformats.org/wiki/h-entry\nhashtag\n\u00a0https://indieweb.org/hashtags\ntag aggregation\n\u00a0https://indieweb.org/tag_aggregation\ntag page\n\u00a0https://indieweb.org/tag_page\ntags page\n\u00a0https://indieweb.org/tags_page",
"html": "About three weeks ago I got auto-linked hashtags working on my posts.<br /><br />The biggest challenge was picking a tag space to link my hashtags. <br /><br />The second biggest challenge was figuring out how to get my linked hashtags to work when my posts were federated into Mastodon instances, and have them rewrite those links into instance-local tag page links. We need a term for such locally rewritten linked hashtags, perhaps \u201cfederated hashtags\u201d.<br /><br />While typical personal sites link a hashtag to a tag page that only displays personal posts, I wanted to link to something more like a tag aggregation page that also displayed similar posts from others.<br /><br />The tag pages on Mastodon instances do a good job of this, showing tagged posts from any user on that instance, and tagged posts from any user followed by any user on that instance.<br /><br />I reviewed my hashtags since the start of 2023, checked their pages <a href=\"http://indieweb.social\">indieweb.social</a> and found that the posts displayed were all on topic, and surprisingly free of tag spam (perhaps for now).<br /><br />I chose <a href=\"https://indieweb.social/tags/\">https://indieweb.social/tags/</a> for my tag space (which is a 404 if you click it, where it really should display a list of tags page). When combined with a hashtag like #<span class=\"p-category\">100DaysOfIndieWeb</span>, it links to <a href=\"https://indieweb.social/tags/100DaysOfIndieWeb\">https://indieweb.social/tags/100DaysOfIndieWeb</a>.<br /><br />The other interesting thing about hashtag links is how they\u2019re rewritten when a post is displayed on another Mastodon instance, to link to the tag page local to that instance. <br /><br />This linked-hashtag-portability is underspecified unfortunately (it could probably use its own portable markup specification, or at least a best practice for h-entry publishing).<br /><br />How it works in Mastodon is non-obvious enough that there\u2019s a 4+ year old Bridgy Fed issue on the subject!<br />* <a href=\"https://github.com/snarfed/bridgy-fed/issues/45\">https://github.com/snarfed/bridgy-fed/issues/45</a><br /><br />With a bunch of research and experiment contributions from several folks in the issue, <a href=\"https://snarfed.org\">@snarfed.org</a> (<a class=\"h-cassis-username\" href=\"https://twitter.com/schnarfed\">@schnarfed</a>) did eventually figure out how to make hashtags in posts federate into Mastodon so it would rewrite their links into instance-local hashtag pages:<br />* <a href=\"https://github.com/snarfed/bridgy-fed/issues/45#issuecomment-1468962400\">https://github.com/snarfed/bridgy-fed/issues/45#issuecomment-1468962400</a><br /><br />Thus even though I\u2019m using the <a href=\"http://indieweb.social\">indieweb.social</a> tag space on the hashtag links in my original post, if you are reading this post on Mastodon, you should see a hashtag like #<span class=\"p-category\">IndieWeb</span> link to your local instance\u2019s tag page for IndieWeb, and my post should show up on that page.<br /><br />From testing a few other instances tag pages, this is now working, e.g. these tag pages:<br />* <a href=\"https://indieweb.social/tags/100DaysofIndieWeb\">https://indieweb.social/tags/100DaysofIndieWeb</a> (as expected)<br />* <a href=\"https://xoxo.zone/tags/100DaysOfIndieWeb\">https://xoxo.zone/tags/100DaysOfIndieWeb</a><br />* <a href=\"https://mozilla.social/tags/100DaysofIndieWeb\">https://mozilla.social/tags/100DaysofIndieWeb</a><br />displays the #<span class=\"p-category\">MozFest</span> post I published right after implementing linked hashtags (as well as this post by the time you see this).<br /><br />I did go back and send Webmentions to BridgyFed send ActivityPub updates for all my past #<span class=\"p-category\">100DaysofIndieWeb</span> posts, however only a few of them showed up in those tag pages. It\u2019s not why a few did and most didn\u2019t, nor why there were inconsistencies across instances. More to explore and debug.<br /><br />Federated hashtags definitely need their own specification, because currently they barely interoperate when published, and even then require Mastodon-implementation-specific knowledge to function.<br /><br /><br />This is day 36 of #<span class=\"p-category\">100DaysOfIndieWeb</span> #<span class=\"p-category\">100Days</span><br /><br />\u2190 Day 35: <a href=\"https://tantek.com/2023/081/t1/mozfest-making-fediverse-socialweb\">https://tantek.com/2023/081/t1/mozfest-making-fediverse-socialweb</a><br />\u2192 \ud83d\udd2e<br /><br /><br />Glossary<br /><br />h-entry<br />\u00a0<a href=\"https://microformats.org/wiki/h-entry\">https://microformats.org/wiki/h-entry</a><br />hashtag<br />\u00a0<a href=\"https://indieweb.org/hashtags\">https://indieweb.org/hashtags</a><br />tag aggregation<br />\u00a0<a href=\"https://indieweb.org/tag_aggregation\">https://indieweb.org/tag_aggregation</a><br />tag page<br />\u00a0<a href=\"https://indieweb.org/tag_page\">https://indieweb.org/tag_page</a><br />tags page<br />\u00a0<a href=\"https://indieweb.org/tags_page\">https://indieweb.org/tags_page</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "http://tantek.com/",
"photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "note",
"_id": "36467172",
"_source": "1",
"_is_read": true
}
{
"type": "entry",
"published": "2023-04-10 23:07-0700",
"url": "http://tantek.com/2023/100/b1/",
"in-reply-to": [
"https://github.com/capjamesg/indieweb-etherpad-archiver/issues"
],
"name": "Warn if event or Etherpad link already archived",
"content": {
"text": "If someone in chat issues a !archive command on an event or Etherpad URL (per \nissue 4), \nand it has already been archived (the destination wiki URL already exists), the bot should return with a warning that the event has already been archived, and provide the full wiki URL for the chat user to inspect, and manually make any improvements if necessary.\n\nRequested originally in IndieWeb meta chat, earlier today.",
"html": "<p>\nIf someone in chat issues a !archive command on an event or Etherpad URL (per \n<a href=\"https://github.com/capjamesg/indieweb-etherpad-archiver/issues/4\">issue 4</a>), \nand it has already been archived (the destination wiki URL already exists), the bot should return with a warning that the event has already been archived, and provide the full wiki URL for the chat user to inspect, and manually make any improvements if necessary.\n\nRequested originally in IndieWeb meta chat, <a href=\"https://chat.indieweb.org/meta/2023-04-10#t1681162290848100\">earlier today</a>.\n</p>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "http://tantek.com/",
"photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "reply",
"refs": {
"https://github.com/capjamesg/indieweb-etherpad-archiver/issues": {
"type": "entry",
"url": "https://github.com/capjamesg/indieweb-etherpad-archiver/issues",
"name": "GitHub project \u201cindieweb-etherpad-archiver\u201d",
"post-type": "article"
}
},
"_id": "36467173",
"_source": "1",
"_is_read": true
}
Inspired by Cory Doctorow (@pluralistic) , I've been thinking about the IndieWeb idea of POSSE (Publish on your Own Site, Syndicate Elsewhere, see https://indieweb.org/POSSE) and how to extend the reach of my blog posts. So I'm trying something new and syndicating blog posts to dev.to.
dev.to makes this quite nice with native support a "canonical URL" for posts originally published elsewhere. It's also pretty easy to repost existing content to since it supports Markdown (my posts are written in reStructuredText for my website but can be easily converted to Markdown using pandoc) and future posts can be automatically shared to dev.to via an RSS feed.
So, assuming I don't find any reason to cancel this experiment, you'll be able to read my writing at https://dev.to/pbarker as well as here on Mastodon and on my website.
{
"type": "entry",
"author": {
"name": "@pbarker",
"url": "https://social.afront.org/@pbarker",
"photo": null
},
"url": "https://social.afront.org/@pbarker/110175621239003874",
"content": {
"html": "<p>Inspired by Cory Doctorow (<span class=\"h-card\"><a class=\"u-url\" href=\"https://mamot.fr/@pluralistic\">@<span>pluralistic</span></a></span>) , I've been thinking about the IndieWeb idea of POSSE (Publish on your Own Site, Syndicate Elsewhere, see <a href=\"https://indieweb.org/POSSE\"><span>https://</span><span>indieweb.org/POSSE</span><span></span></a>) and how to extend the reach of my blog posts. So I'm trying something new and syndicating blog posts to dev.to.</p><p>dev.to makes this quite nice with native support a \"canonical URL\" for posts originally published elsewhere. It's also pretty easy to repost existing content to since it supports Markdown (my posts are written in reStructuredText for my website but can be easily converted to Markdown using pandoc) and future posts can be automatically shared to dev.to via an RSS feed.</p><p>So, assuming I don't find any reason to cancel this experiment, you'll be able to read my writing at <a href=\"https://dev.to/pbarker\"><span>https://</span><span>dev.to/pbarker</span><span></span></a> as well as here on Mastodon and on my website.</p><p>(originally posted at <a href=\"https://pbarker.dev/posts/2023-04-10/syndication/\"><span>https://</span><span>pbarker.dev/posts/2023-04-10/s</span><span>yndication/</span></a>)</p><p><a href=\"https://social.afront.org/tags/writing\">#<span>writing</span></a> <a href=\"https://social.afront.org/tags/blog\">#<span>blog</span></a> <a href=\"https://social.afront.org/tags/blogging\">#<span>blogging</span></a> <a href=\"https://social.afront.org/tags/indieweb\">#<span>indieweb</span></a></p>",
"text": "Inspired by Cory Doctorow (@pluralistic) , I've been thinking about the IndieWeb idea of POSSE (Publish on your Own Site, Syndicate Elsewhere, see https://indieweb.org/POSSE) and how to extend the reach of my blog posts. So I'm trying something new and syndicating blog posts to dev.to.dev.to makes this quite nice with native support a \"canonical URL\" for posts originally published elsewhere. It's also pretty easy to repost existing content to since it supports Markdown (my posts are written in reStructuredText for my website but can be easily converted to Markdown using pandoc) and future posts can be automatically shared to dev.to via an RSS feed.So, assuming I don't find any reason to cancel this experiment, you'll be able to read my writing at https://dev.to/pbarker as well as here on Mastodon and on my website.(originally posted at https://pbarker.dev/posts/2023-04-10/syndication/)#writing #blog #blogging #indieweb"
},
"published": "2023-04-10T17:09:24+00:00",
"post-type": "note",
"_id": "36456559",
"_source": "7235",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "@htmldecoder",
"url": "https://indieweb.social/@htmldecoder",
"photo": null
},
"url": "https://indieweb.social/@htmldecoder/110175765410077429",
"content": {
"html": "<p>My blog (<a href=\"https://decodedHTML.com\"><span>https://</span><span>decodedHTML.com</span><span></span></a>) is built using Rust's \ud83e\udd80 mdbook. Which is a tool to build books using markdown. </p><p>Moving into the indie web, I was too much concerned about the design and other features, that I forgot what I should use the indie web space for.</p><p>It's now a kind of devlog. Is indie web a fancy word for devlog? \ud83e\udd14</p><p><a href=\"https://indieweb.social/tags/rustlang\">#<span>rustlang</span></a> <a href=\"https://indieweb.social/tags/indieweb\">#<span>indieweb</span></a></p>",
"text": "My blog (https://decodedHTML.com) is built using Rust's \ud83e\udd80 mdbook. Which is a tool to build books using markdown. Moving into the indie web, I was too much concerned about the design and other features, that I forgot what I should use the indie web space for.It's now a kind of devlog. Is indie web a fancy word for devlog? \ud83e\udd14#rustlang #indieweb"
},
"published": "2023-04-10T17:46:04+00:00",
"post-type": "note",
"_id": "36456560",
"_source": "7235",
"_is_read": true
}
After a bit of break, I'm back at it with #webmentions. I am now wondering, if it is possible for someone to reply to a comment on a post?
This sounds a bit stupid because obviously that has to work. But I've never seen a webmention-powered comment section that actually has threads. Are there any examples out there on the #indieweb?
{
"type": "entry",
"author": {
"name": "@nachtfunke",
"url": "https://indieweb.social/@nachtfunke",
"photo": null
},
"url": "https://indieweb.social/@nachtfunke/110169924494781102",
"content": {
"html": "<p>After a bit of break, I'm back at it with <a href=\"https://indieweb.social/tags/webmentions\">#<span>webmentions</span></a>. I am now wondering, if it is possible for someone to reply to a comment on a post?</p><p>This sounds a bit stupid because obviously that has to work. But I've never seen a webmention-powered comment section that actually has threads. Are there any examples out there on the <a href=\"https://indieweb.social/tags/indieweb\">#<span>indieweb</span></a>?</p>",
"text": "After a bit of break, I'm back at it with #webmentions. I am now wondering, if it is possible for someone to reply to a comment on a post?This sounds a bit stupid because obviously that has to work. But I've never seen a webmention-powered comment section that actually has threads. Are there any examples out there on the #indieweb?"
},
"published": "2023-04-09T17:00:38+00:00",
"post-type": "note",
"_id": "36438406",
"_source": "7235",
"_is_read": true
}
So on the day that my 16 year old bird site has been consigned to oblivion, I have taken my first baby step into #indieweb by publishing my own notes site as a canonical home for all of my content that isn't proper blogging or main website stuff. You can find it here: https://rustyniall.com .
It'll be a proper home for drafts, ephemera, anomalies and abominations going forward.
It still needs plenty of work but the BBC Micro text adventure aesthetic is completely intentional and will remain that way until another retro-fad-infatuation turns my head.
{
"type": "entry",
"author": {
"name": "@rustyniall",
"url": "https://sunny.garden/@rustyniall",
"photo": null
},
"url": "https://sunny.garden/@rustyniall/110169074701974945",
"content": {
"html": "<p>So on the day that my 16 year old bird site has been consigned to oblivion, I have taken my first baby step into <a href=\"https://sunny.garden/tags/indieweb\">#<span>indieweb</span></a> by publishing my own notes site as a canonical home for all of my content that isn't proper blogging or main website stuff. You can find it here: <a href=\"https://rustyniall.com\"><span>https://</span><span>rustyniall.com</span><span></span></a> . </p><p>It'll be a proper home for drafts, ephemera, anomalies and abominations going forward. </p><p>It still needs plenty of work but the BBC Micro text adventure aesthetic is completely intentional and will remain that way until another retro-fad-infatuation turns my head.</p>",
"text": "So on the day that my 16 year old bird site has been consigned to oblivion, I have taken my first baby step into #indieweb by publishing my own notes site as a canonical home for all of my content that isn't proper blogging or main website stuff. You can find it here: https://rustyniall.com . It'll be a proper home for drafts, ephemera, anomalies and abominations going forward. It still needs plenty of work but the BBC Micro text adventure aesthetic is completely intentional and will remain that way until another retro-fad-infatuation turns my head."
},
"published": "2023-04-09T13:24:32+00:00",
"post-type": "note",
"_id": "36434748",
"_source": "7235",
"_is_read": false
}
I’m honestly very excited about the possibility of a revival of blogging and so forth, but I’d love to see the word “content” thrown into the dustbin. I don’t create “content”. I write (occasionally). And my writing isn’t just the grist for some corporate mill; my blog isn’t just a source of inventory for some ad network to monetize.
{
"type": "entry",
"author": {
"name": "@brettk",
"url": "https://indieweb.social/@brettk",
"photo": null
},
"url": "https://indieweb.social/@brettk/110166176641387083",
"content": {
"html": "<p>I\u2019m honestly very excited about the possibility of a revival of blogging and so forth, but I\u2019d love to see the word \u201ccontent\u201d thrown into the dustbin. I don\u2019t create \u201ccontent\u201d. I write (occasionally). And my writing isn\u2019t just the grist for some corporate mill; my blog isn\u2019t just a source of inventory for some ad network to monetize.</p><p><a href=\"https://indieweb.social/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://indieweb.social/tags/writing\">#<span>writing</span></a></p><p>(<a href=\"https://b-ark.ca/248ecC\"><span>https://</span><span>b-ark.ca/248ecC</span><span></span></a>)</p>",
"text": "I\u2019m honestly very excited about the possibility of a revival of blogging and so forth, but I\u2019d love to see the word \u201ccontent\u201d thrown into the dustbin. I don\u2019t create \u201ccontent\u201d. I write (occasionally). And my writing isn\u2019t just the grist for some corporate mill; my blog isn\u2019t just a source of inventory for some ad network to monetize.#indieweb #writing(https://b-ark.ca/248ecC)"
},
"published": "2023-04-09T01:07:31+00:00",
"post-type": "note",
"_id": "36427946",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "@philipp",
"url": "https://social.anoxinon.de/@philipp",
"photo": null
},
"url": "https://social.anoxinon.de/@philipp/110165873660520746",
"content": {
"html": "<p>Thinking about starting a personal blog soon. This article really spoke to me \ud83d\ude0d <a href=\"https://social.anoxinon.de/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://manuelmoreale.com/unsolicited-blogging-advice\"><span>https://</span><span>manuelmoreale.com/unsolicited-</span><span>blogging-advice</span></a></p>",
"text": "Thinking about starting a personal blog soon. This article really spoke to me \ud83d\ude0d #indieweb https://manuelmoreale.com/unsolicited-blogging-advice"
},
"published": "2023-04-08T23:50:28+00:00",
"post-type": "note",
"_id": "36426956",
"_source": "7235",
"_is_read": false
}
After a 4-day session, I deployed a complete refactor of my website. All remnants of bloated frameworks, such as Bootstrap, are gone. Most classes in my markup are for Indieweb purposes.
I have reduced the homepage size to 63 KB uncompressed, with 0.01g of CO2 produced.
{
"type": "entry",
"author": {
"name": "@m2m",
"url": "https://indieweb.social/@m2m",
"photo": null
},
"url": "https://indieweb.social/@m2m/110165231395797392",
"content": {
"html": "<p>After a 4-day session, I deployed a complete refactor of my website. All remnants of bloated frameworks, such as Bootstrap, are gone. Most classes in my markup are for Indieweb purposes.</p><p>I have reduced the homepage size to 63 KB uncompressed, with 0.01g of CO2 produced.</p><p>I've also added a credits page with links to the people who inspired me with ideas and tools, such as: <span class=\"h-card\"><a class=\"u-url\" href=\"https://indieweb.social/@silviamaggi\">@<span>silviamaggi</span></a></span> <span class=\"h-card\"><a class=\"u-url\" href=\"https://fosstodon.org/@lkhrs\">@<span>lkhrs</span></a></span> <span class=\"h-card\"><a class=\"u-url\" href=\"https://tech.lgbt/@zinzy\">@<span>zinzy</span></a></span> <span class=\"h-card\"><a class=\"u-url\" href=\"https://mastodon.chriswiegman.com/@chris\">@<span>chris</span></a></span> <span class=\"h-card\"><a class=\"u-url\" href=\"https://dosgame.club/@jefklak\">@<span>jefklak</span></a></span> <span class=\"h-card\"><a class=\"u-url\" href=\"https://fosstodon.org/@tdarb\">@<span>tdarb</span></a></span> <span class=\"h-card\"><a class=\"u-url\" href=\"https://fosstodon.org/@ru\">@<span>ru</span></a></span> <span class=\"h-card\"><a class=\"u-url\" href=\"https://qrk.social/activitypub/kev\">@<span>kev</span></a></span> <span class=\"h-card\"><a class=\"u-url\" href=\"https://bsd.network/@rubenerd\">@<span>rubenerd</span></a></span> </p><p><a href=\"https://minutestomidnight.co.uk\"><span>https://</span><span>minutestomidnight.co.uk</span><span></span></a></p><p><a href=\"https://indieweb.social/tags/IndieWeb\">#<span>IndieWeb</span></a> <a href=\"https://indieweb.social/tags/sustainability\">#<span>sustainability</span></a></p>",
"text": "After a 4-day session, I deployed a complete refactor of my website. All remnants of bloated frameworks, such as Bootstrap, are gone. Most classes in my markup are for Indieweb purposes.I have reduced the homepage size to 63 KB uncompressed, with 0.01g of CO2 produced.I've also added a credits page with links to the people who inspired me with ideas and tools, such as: @silviamaggi @lkhrs @zinzy @chris @jefklak @tdarb @ru @kev @rubenerd https://minutestomidnight.co.uk#IndieWeb #sustainability"
},
"published": "2023-04-08T21:07:07+00:00",
"post-type": "note",
"_id": "36425622",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "@sp1ff",
"url": "https://indieweb.social/@sp1ff",
"photo": null
},
"url": "https://indieweb.social/@sp1ff/110165036153346969",
"content": {
"html": "<p>I've published indie-org.sh, a demonstration site for my Emacs package indie-org, which helps you put Org Mode static sites on the Indieweb. <a href=\"https://indieweb.social/tags/emacs\">#<span>emacs</span></a> <a href=\"https://indieweb.social/tags/orgmode\">#<span>orgmode</span></a> <a href=\"https://indieweb.social/tags/indieweb\">#<span>indieweb</span></a> (<a href=\"https://www.unwoundstack.com/blog/indie-org.sh.html\"><span>https://www.</span><span>unwoundstack.com/blog/indie-or</span><span>g.sh.html</span></a>)</p>",
"text": "I've published indie-org.sh, a demonstration site for my Emacs package indie-org, which helps you put Org Mode static sites on the Indieweb. #emacs #orgmode #indieweb (https://www.unwoundstack.com/blog/indie-org.sh.html)"
},
"published": "2023-04-08T20:17:28+00:00",
"post-type": "note",
"_id": "36425623",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"published": "2023-04-07T23:39:59-0400",
"url": "https://martymcgui.re/2023/04/07/this-week-in-the-indieweb-audio-edition--april-1st---7th-2023/",
"category": [
"podcast",
"IndieWeb",
"this-week-indieweb-podcast"
],
"audio": [
"https://media.martymcgui.re/1c/8c/b4/ae/4df4700afe8248b3e0d46f8eba32af2b26fa768d055df73e6a4628c1.mp3"
],
"name": "This Week in the IndieWeb Audio Edition \u2022 April 1st - 7th, 2023",
"content": {
"text": "Show/Hide Transcript\n \n Fun facts about Feedly, going indie with 11ty, and bye bye, Twitter API. It\u2019s the audio edition for This Week in the IndieWeb for April 1st - 7th, 2023.\nYou can find all of my audio editions and subscribe with your favorite podcast app here: martymcgui.re/podcasts/indieweb/.\nMusic from Aaron Parecki\u2019s 100DaysOfMusic project: Day 85 - Suit, Day 48 - Glitch, Day 49 - Floating, Day 9, and Day 11\nThanks to everyone in the IndieWeb chat for their feedback and suggestions. Please drop me a note if there are any changes you\u2019d like to see for this audio edition!",
"html": "Show/Hide Transcript\n \n <p>Fun facts about Feedly, going indie with 11ty, and bye bye, Twitter API. It\u2019s the audio edition for <a href=\"https://indieweb.org/this-week/2023-04-07.html\">This Week in the IndieWeb for April 1st - 7th, 2023</a>.</p>\n<p>You can find all of my audio editions and subscribe with your favorite podcast app here: <a href=\"https://martymcgui.re/podcasts/indieweb/\">martymcgui.re/podcasts/indieweb/</a>.</p>\n<p>Music from <a href=\"https://aaronparecki.com/\">Aaron Parecki</a>\u2019s <a href=\"https://100.aaronparecki.com/\">100DaysOfMusic project</a>: <a href=\"https://aaronparecki.com/2017/03/15/14/day85\">Day 85 - Suit</a>, <a href=\"https://aaronparecki.com/2017/02/06/7/day48\">Day 48 - Glitch</a>, <a href=\"https://aaronparecki.com/2017/02/07/4/day49\">Day 49 - Floating</a>, <a href=\"https://aaronparecki.com/2016/12/29/21/day-9\">Day 9</a>, and <a href=\"https://aaronparecki.com/2016/12/31/15/\">Day 11</a></p>\n<p>Thanks to everyone in the <a href=\"https://chat.indieweb.org/\">IndieWeb chat</a> for their feedback and suggestions. Please drop me a note if there are any changes you\u2019d like to see for this audio edition!</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "audio",
"_id": "36412289",
"_source": "175",
"_is_read": false
}
