"Personal stories on personal #blogs are historical documents," said this Verge article.
This is so true for Christopher, who left behind a treasure trove of thoughts, a record of his brilliance on earth. I feel privileged to have found his #blog.
And that's why we need personal #blogging to return, #algorithms be damned. We can't let these stories disappear into the ether.
#IndieWeb #Writing
https://www.theverge.com/23513418/bring-back-personal-blogging
{
"type": "entry",
"author": {
"name": "@liztai",
"url": "https://hachyderm.io/@liztai",
"photo": null
},
"url": "https://hachyderm.io/@liztai/109715970125576953",
"content": {
"html": "<p>\"Personal stories on personal <a href=\"https://hachyderm.io/tags/blogs\">#<span>blogs</span></a> are historical documents,\" said this Verge article. </p><p>This is so true for Christopher, who left behind a treasure trove of thoughts, a record of his brilliance on earth. I feel privileged to have found his <a href=\"https://hachyderm.io/tags/blog\">#<span>blog</span></a>.</p><p>And that's why we need personal <a href=\"https://hachyderm.io/tags/blogging\">#<span>blogging</span></a> to return, <a href=\"https://hachyderm.io/tags/algorithms\">#<span>algorithms</span></a> be damned. We can't let these stories disappear into the ether.</p><p><a href=\"https://hachyderm.io/tags/IndieWeb\">#<span>IndieWeb</span></a> <a href=\"https://hachyderm.io/tags/Writing\">#<span>Writing</span></a> <br /><br /><a href=\"https://www.theverge.com/23513418/bring-back-personal-blogging\"><span>https://www.</span><span>theverge.com/23513418/bring-ba</span><span>ck-personal-blogging</span></a></p>",
"text": "\"Personal stories on personal #blogs are historical documents,\" said this Verge article. This is so true for Christopher, who left behind a treasure trove of thoughts, a record of his brilliance on earth. I feel privileged to have found his #blog.And that's why we need personal #blogging to return, #algorithms be damned. We can't let these stories disappear into the ether.#IndieWeb #Writing \n\nhttps://www.theverge.com/23513418/bring-back-personal-blogging"
},
"published": "2023-01-19T12:54:04+00:00",
"post-type": "note",
"_id": "34516789",
"_source": "7235",
"_is_read": false
}
The answer to “How should you @-mention someone you are replying to?”^1 can depend on many factors or a few. Context matters somewhat, sometimes.
We can simplify it to 2 questions, based on 1 directive:
* Elevate #IndieWeb domains, above any silo or @-@ identities
Two questions and answers:
1. Do they have an #IndieWeb domain? Then @-domain mention them^2, like you are speaking to them at their domain identity. This will notify them there, or at least reinforce their domain’s importance.
2. Was their post only published on a silo (or #fediverse instance), or was it POSSEd to a silo (or fediverse instance) and you plan to POSSE (or federate) your reply^3? Then @-mention their silo @-name (or @-@ address), in parentheses if (1). This will notify them on that silo (or instance), and may help thread your POSSE reply.
Examples:
If the author has their own domain:
Reply to an IndieWeb post (& POSSE toot): https://tantek.com/2023/008/t1/
* @-domain (@-@)
Reply to an IndieWeb post (& POSSE tweet): https://tantek.com/2023/016/t1/
* @-domain [that matches their Twitter @-name]
Reply to a toot: https://tantek.com/2023/008/t4/
* @-domain (@-@)
Reply to a tweet: https://tantek.com/2023/002/t2/
* @-domain (Twitter @-name)
If the author does not have their own domain:
Reply to a toot: https://tantek.com/2023/002/t4/
* @-@
Reply to a tweet: none since this series, though it would be of the form:
* Twitter @-name
This is day 17 of #100DaysOfIndieWeb #100Days, again finished the next day.
← Day 16: https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute
→ 🔮
^1 https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post
^2 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention
^3 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute
{
"type": "entry",
"published": "2023-01-18 23:11-0800",
"url": "http://tantek.com/2023/018/t1/elevate-indieweb-above-silo",
"category": [
"IndieWeb",
"fediverse",
"100DaysOfIndieWeb",
"100Days"
],
"content": {
"text": "The answer to \u201cHow should you @-mention someone you are replying to?\u201d^1 can depend on many factors or a few. Context matters somewhat, sometimes.\n\nWe can simplify it to 2 questions, based on 1 directive:\n\n* Elevate #IndieWeb domains, above any silo or @-@ identities\n\nTwo questions and answers: \n\n1. Do they have an #IndieWeb domain? Then @-domain mention them^2, like you are speaking to them at their domain identity. This will notify them there, or at least reinforce their domain\u2019s importance.\n\n2. Was their post only published on a silo (or #fediverse instance), or was it POSSEd to a silo (or fediverse instance) and you plan to POSSE (or federate) your reply^3? Then @-mention their silo @-name (or @-@ address), in parentheses if (1). This will notify them on that silo (or instance), and may help thread your POSSE reply.\n\n\nExamples:\n\n\nIf the author has their own domain:\n\nReply to an IndieWeb post (& POSSE toot): https://tantek.com/2023/008/t1/\n* @-domain (@-@)\n\nReply to an IndieWeb post (& POSSE tweet): https://tantek.com/2023/016/t1/\n* @-domain [that matches their Twitter @-name]\n\nReply to a toot: https://tantek.com/2023/008/t4/\n* @-domain (@-@)\n\nReply to a tweet: https://tantek.com/2023/002/t2/\n* @-domain (Twitter @-name)\n\n\nIf the author does not have their own domain:\n\nReply to a toot: https://tantek.com/2023/002/t4/\n* @-@\n\nReply to a tweet: none since this series, though it would be of the form:\n* Twitter @-name\n\n\nThis is day 17 of #100DaysOfIndieWeb #100Days, again finished the next day.\n\n\u2190 Day 16: https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute\n\u2192 \ud83d\udd2e\n\n\n^1 https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post\n^2 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention\n^3 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute",
"html": "The answer to \u201cHow should you @-mention someone you are replying to?\u201d^1 can depend on many factors or a few. Context matters somewhat, sometimes.<br /><br />We can simplify it to 2 questions, based on 1 directive:<br /><br />* Elevate #<span class=\"p-category\">IndieWeb</span> domains, above any silo or @-@ identities<br /><br />Two questions and answers: <br /><br />1. Do they have an #<span class=\"p-category\">IndieWeb</span> domain? Then @-domain mention them^2, like you are speaking to them at their domain identity. This will notify them there, or at least reinforce their domain\u2019s importance.<br /><br />2. Was their post only published on a silo (or #<span class=\"p-category\">fediverse</span> instance), or was it POSSEd to a silo (or fediverse instance) and you plan to POSSE (or federate) your reply^3? Then @-mention their silo @-name (or @-@ address), in parentheses if (1). This will notify them on that silo (or instance), and may help thread your POSSE reply.<br /><br /><br />Examples:<br /><br /><br />If the author has their own domain:<br /><br />Reply to an IndieWeb post (& POSSE toot): <a href=\"https://tantek.com/2023/008/t1/\">https://tantek.com/2023/008/t1/</a><br />* @-domain (@-@)<br /><br />Reply to an IndieWeb post (& POSSE tweet): <a href=\"https://tantek.com/2023/016/t1/\">https://tantek.com/2023/016/t1/</a><br />* @-domain [that matches their Twitter @-name]<br /><br />Reply to a toot: <a href=\"https://tantek.com/2023/008/t4/\">https://tantek.com/2023/008/t4/</a><br />* @-domain (@-@)<br /><br />Reply to a tweet: <a href=\"https://tantek.com/2023/002/t2/\">https://tantek.com/2023/002/t2/</a><br />* @-domain (Twitter @-name)<br /><br /><br />If the author does not have their own domain:<br /><br />Reply to a toot: <a href=\"https://tantek.com/2023/002/t4/\">https://tantek.com/2023/002/t4/</a><br />* @-@<br /><br />Reply to a tweet: none since this series, though it would be of the form:<br />* Twitter @-name<br /><br /><br />This is day 17 of #<span class=\"p-category\">100DaysOfIndieWeb</span> #<span class=\"p-category\">100Days</span>, again finished the next day.<br /><br />\u2190 Day 16: <a href=\"https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute\">https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute</a><br />\u2192 \ud83d\udd2e<br /><br /><br />^1 <a href=\"https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post\">https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post</a><br />^2 <a href=\"https://tantek.com/2023/011/t1/indieweb-evolving-at-mention\">https://tantek.com/2023/011/t1/indieweb-evolving-at-mention</a><br />^3 <a href=\"https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute\">https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute</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": "34515882",
"_source": "1",
"_is_read": false
}
Tonight, I had some success in my #IndieWeb journey - adding #WebMentions to my blog. I took some shortcuts, but it did help me understand the concepts. Now I can go back and #POSSE it up. 💪
https://www.box464.com/indieweb/2023/01/18/indieweb-webmentions/
{
"type": "entry",
"author": {
"name": "@box464",
"url": "https://mastodon.social/@box464",
"photo": null
},
"url": "https://mastodon.social/@box464/109714183426309418",
"content": {
"html": "<p>Tonight, I had some success in my <a href=\"https://mastodon.social/tags/IndieWeb\">#<span>IndieWeb</span></a> journey - adding <a href=\"https://mastodon.social/tags/WebMentions\">#<span>WebMentions</span></a> to my blog. I took some shortcuts, but it did help me understand the concepts. Now I can go back and <a href=\"https://mastodon.social/tags/POSSE\">#<span>POSSE</span></a> it up. \ud83d\udcaa </p><p><a href=\"https://www.box464.com/indieweb/2023/01/18/indieweb-webmentions/\"><span>https://www.</span><span>box464.com/indieweb/2023/01/18</span><span>/indieweb-webmentions/</span></a></p>",
"text": "Tonight, I had some success in my #IndieWeb journey - adding #WebMentions to my blog. I took some shortcuts, but it did help me understand the concepts. Now I can go back and #POSSE it up. \ud83d\udcaa https://www.box464.com/indieweb/2023/01/18/indieweb-webmentions/"
},
"published": "2023-01-19T05:19:42+00:00",
"post-type": "note",
"_id": "34510894",
"_source": "7235",
"_is_read": false
}
I’m not entirely certain when I was turned onto this phrase, but it has stuck with me for quite some time. It’s been sitting as a mobile bookmark for me for at least as long as I’ve owned an iPhone, so maybe going back to 2015-ish. Hapax legomenon – it seems so exotic, and definitely hard to pronounce in casual speech.
Hapax legomenon: a word or an expression that occurs only once within a context: either in the written record of an entire language, in the works of an author, or in a single text. (Definition courtesy of Wikipedia)
I think I may have been alerted to this phrase when doing a nostalgic look at Googlewhacking – trying to find a search result on google that only returns one result. Oddly enough, I do remember the first time hearing (and trying) the sport – it was the night before starting high school, and some friends and I learned about it and ended up finding a few.
I always thought the term would be a good name for a musical side-project, or an album title, but it looks like someone beat me to it.
#100daysofindieweb #atleast100 #indieweb
https://novakeith.net/2023/01/18/hapax-legomenon/
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://novakeith.net/2023/01/18/hapax-legomenon/",
"content": {
"html": "<p>I\u2019m not entirely certain when I was turned onto this phrase, but it has stuck with me for quite some time. It\u2019s been sitting as a mobile bookmark for me for at least as long as I\u2019ve owned an iPhone, so maybe going back to 2015-ish. <a href=\"https://en.wikipedia.org/wiki/Hapax_legomenon\">Hapax legomenon</a> \u2013 it seems so exotic, and definitely hard to pronounce in casual speech.</p><br /><p>Hapax legomenon:\u00a0a word or an expression that occurs only once within a context: either in the written record of an entire language, in the works of an author, or in a single text. (Definition courtesy of Wikipedia)</p><br /><p>I think I may have been alerted to this phrase when doing a nostalgic look at <a href=\"https://en.wikipedia.org/wiki/Googlewhack\">Googlewhacking </a>\u2013 trying to find a search result on google that only returns one result. Oddly enough, I do remember the first time hearing (and trying) the sport \u2013 it was the night before starting high school, and some friends and I learned about it and ended up finding a few.</p><br /><p>I always thought the term would be a good name for a musical side-project, or an album title, but it looks like <a href=\"https://open.spotify.com/artist/13tG87RcFNf8Q6tdbbRvY8\">someone</a> beat me to it.</p><p><a class=\"u-tag u-category\" href=\"https://novakeith.net/tag/100daysofindieweb/\">#100daysofindieweb</a> <a class=\"u-tag u-category\" href=\"https://novakeith.net/tag/atleast100/\">#atleast100</a> <a class=\"u-tag u-category\" href=\"https://novakeith.net/tag/indieweb/\">#indieweb</a></p><p><a href=\"https://novakeith.net/2023/01/18/hapax-legomenon/\">https://novakeith.net/2023/01/18/hapax-legomenon/</a></p>",
"text": "I\u2019m not entirely certain when I was turned onto this phrase, but it has stuck with me for quite some time. It\u2019s been sitting as a mobile bookmark for me for at least as long as I\u2019ve owned an iPhone, so maybe going back to 2015-ish. Hapax legomenon \u2013 it seems so exotic, and definitely hard to pronounce in casual speech.\nHapax legomenon:\u00a0a word or an expression that occurs only once within a context: either in the written record of an entire language, in the works of an author, or in a single text. (Definition courtesy of Wikipedia)\nI think I may have been alerted to this phrase when doing a nostalgic look at Googlewhacking \u2013 trying to find a search result on google that only returns one result. Oddly enough, I do remember the first time hearing (and trying) the sport \u2013 it was the night before starting high school, and some friends and I learned about it and ended up finding a few.\nI always thought the term would be a good name for a musical side-project, or an album title, but it looks like someone beat me to it.#100daysofindieweb #atleast100 #indiewebhttps://novakeith.net/2023/01/18/hapax-legomenon/"
},
"published": "2023-01-19T03:21:34+00:00",
"post-type": "note",
"_id": "34509925",
"_source": "7235",
"_is_read": false
}
Managed to mess up links on my blog while changing something else. Some RSS and ActivityPub posts might be wrong while I sort it out.
{
"type": "entry",
"author": {
"name": "Manton Reece",
"url": "https://www.manton.org/",
"photo": "https://micro.blog/manton/avatar.jpg"
},
"url": "https://www.manton.org/2023/01/18/managed-to-mess.html",
"content": {
"html": "<p>Managed to mess up links on my blog while changing something else. Some RSS and ActivityPub posts might be wrong while I sort it out.</p>",
"text": "Managed to mess up links on my blog while changing something else. Some RSS and ActivityPub posts might be wrong while I sort it out."
},
"published": "2023-01-18T21:41:31-06:00",
"post-type": "note",
"_id": "34509695",
"_source": "12",
"_is_read": false
}
Today, I am reading the Webmention and Webmention-Developer pages on the IndieWeb.org website. This is going to take a couple of days to review the examples. This is under the task to:
* Learn About Webmentions a Little More Deeply.
Day 11 of 100 #100DaysofIndieWeb, #IndieWeb, #ProjectJournal, #WordPress (https://tmichellemoore.com/?p=152149)
{
"type": "entry",
"author": {
"name": "@tmichellemoore",
"url": "https://mastodon.social/@tmichellemoore",
"photo": null
},
"url": "https://mastodon.social/@tmichellemoore/109713631606535064",
"content": {
"html": "<p>Today, I am reading the Webmention and Webmention-Developer pages on the IndieWeb.org website. This is going to take a couple of days to review the examples. This is under the task to:</p><p> * Learn About Webmentions a Little More Deeply.</p><p>Day 11 of 100 <a href=\"https://mastodon.social/tags/100DaysofIndieWeb\">#<span>100DaysofIndieWeb</span></a>, <a href=\"https://mastodon.social/tags/IndieWeb\">#<span>IndieWeb</span></a>, <a href=\"https://mastodon.social/tags/ProjectJournal\">#<span>ProjectJournal</span></a>, <a href=\"https://mastodon.social/tags/WordPress\">#<span>WordPress</span></a> (<a href=\"https://tmichellemoore.com/?p=152149\"><span>https://</span><span>tmichellemoore.com/?p=152149</span><span></span></a>)</p>",
"text": "Today, I am reading the Webmention and Webmention-Developer pages on the IndieWeb.org website. This is going to take a couple of days to review the examples. This is under the task to: * Learn About Webmentions a Little More Deeply.Day 11 of 100 #100DaysofIndieWeb, #IndieWeb, #ProjectJournal, #WordPress (https://tmichellemoore.com/?p=152149)"
},
"published": "2023-01-19T02:59:21+00:00",
"post-type": "note",
"_id": "34509222",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"published": "2023-01-18 15:09-0800",
"url": "https://gregorlove.com/2023/01/support-profile-updates/",
"syndication": [
"https://github.com/snarfed/bridgy-fed/issues/376"
],
"in-reply-to": [
"https://github.com/snarfed/bridgy-fed/issues"
],
"name": "Support profile updates",
"content": {
"text": "It would be nice if BF could send profile update activities when h-card bio, photo, and link(s) change. I recently changed the h-card on my homepage and instances aware of me prior to that still have my old photo. You mentioned in chat that BF would need to poll for updates. I also wonder if an on-demand option could work via a webmention trigger? I have not thought through this in-depth, but maybe microformats like:\n\n<a href=\"https://gregorlove.com\" class=\"u-edit-of\">updated profile</a>",
"html": "<p>It would be nice if BF could send profile update activities when h-card bio, photo, and link(s) change. I recently changed the h-card on my homepage and instances aware of me prior to that still have my old photo. You <a href=\"https://chat.indieweb.org/dev/2023-01-03#t1672777500729600\">mentioned in chat</a> that BF would need to poll for updates. I also wonder if an on-demand option could work via a webmention trigger? I have not thought through this in-depth, but maybe microformats like:</p>\n\n<p><code><a href=\"https://gregorlove.com\" class=\"u-edit-of\">updated profile</a></code></p>"
},
"author": {
"type": "card",
"name": "gRegor Morrill",
"url": "https://gregorlove.com/",
"photo": "https://gregorlove.com/site/assets/files/6268/profile-2021-square.300x0.jpg"
},
"post-type": "reply",
"_id": "34506794",
"_source": "95",
"_is_read": false
}
Yes, I want to relaunch my website! Yes, I want start to blog (at least occasionally)!! And yes, I want to launch it all THIS YEAR!!! Let's see how it goes …
Thanks @matthiasott and the #IndieWeb folks for the motivation and the constant reminder to own our content.
{
"type": "entry",
"author": {
"name": "@flokosiol",
"url": "https://mastodon.social/@flokosiol",
"photo": null
},
"url": "https://mastodon.social/@flokosiol/109712015057024377",
"content": {
"html": "<p>Yes, I want to relaunch my website! Yes, I want start to blog (at least occasionally)!! And yes, I want to launch it all THIS YEAR!!! Let's see how it goes \u2026 </p><p>Thanks <span class=\"h-card\"><a class=\"u-url\" href=\"https://mastodon.social/@matthiasott\">@<span>matthiasott</span></a></span> and the <a href=\"https://mastodon.social/tags/IndieWeb\">#<span>IndieWeb</span></a> folks for the motivation and the constant reminder to own our content.</p>",
"text": "Yes, I want to relaunch my website! Yes, I want start to blog (at least occasionally)!! And yes, I want to launch it all THIS YEAR!!! Let's see how it goes \u2026 Thanks @matthiasott and the #IndieWeb folks for the motivation and the constant reminder to own our content."
},
"published": "2023-01-18T20:08:15+00:00",
"post-type": "note",
"_id": "34503534",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "@voxpelli",
"url": "https://mastodon.social/@voxpelli",
"photo": null
},
"url": "https://mastodon.social/@voxpelli/109709830323778398",
"content": {
"html": "<p>Someone should really build a Nuzzel for the Fediverse / <a href=\"https://mastodon.social/tags/IndieWeb\">#<span>IndieWeb</span></a> <a href=\"https://daringfireball.net/linked/2021/05/05/nuzzel\"><span>https://</span><span>daringfireball.net/linked/2021</span><span>/05/05/nuzzel</span></a></p>",
"text": "Someone should really build a Nuzzel for the Fediverse / #IndieWeb https://daringfireball.net/linked/2021/05/05/nuzzel"
},
"published": "2023-01-18T10:52:38+00:00",
"post-type": "note",
"_id": "34490743",
"_source": "7235",
"_is_read": false
}
Seeing as I've thought of some other things I didn't manage to squeeze in last time, here's another #introduction - Lately I've been #writing tiny generic #fantasy #horror adventures in #pocketmod format for #ttrpgs. I plan to put these up on Itch. And maybe I'll put together a #neocities page since I come from a #retroweb era and find the resurrected #indieweb movement very interesting. That dovetails with my ongoing interests in #politics #psychology and #philosophy. Proudest sport moment: I once took a brilliant hat-trick in indoor #cricket, Warne-style, with my legspin bowling - completely bamboozling the batsman. From #australia.
{
"type": "entry",
"author": {
"name": "@lime_juice_cube",
"url": "https://mastodon.au/@lime_juice_cube",
"photo": null
},
"url": "https://mastodon.au/@lime_juice_cube/109709314228921946",
"content": {
"html": "<p>Seeing as I've thought of some other things I didn't manage to squeeze in last time, here's another <a href=\"https://mastodon.au/tags/introduction\">#<span>introduction</span></a> - Lately I've been <a href=\"https://mastodon.au/tags/writing\">#<span>writing</span></a> tiny generic <a href=\"https://mastodon.au/tags/fantasy\">#<span>fantasy</span></a> <a href=\"https://mastodon.au/tags/horror\">#<span>horror</span></a> adventures in <a href=\"https://mastodon.au/tags/pocketmod\">#<span>pocketmod</span></a> format for <a href=\"https://mastodon.au/tags/ttrpgs\">#<span>ttrpgs</span></a>. I plan to put these up on Itch. And maybe I'll put together a <a href=\"https://mastodon.au/tags/neocities\">#<span>neocities</span></a> page since I come from a <a href=\"https://mastodon.au/tags/retroweb\">#<span>retroweb</span></a> era and find the resurrected <a href=\"https://mastodon.au/tags/indieweb\">#<span>indieweb</span></a> movement very interesting. That dovetails with my ongoing interests in <a href=\"https://mastodon.au/tags/politics\">#<span>politics</span></a> <a href=\"https://mastodon.au/tags/psychology\">#<span>psychology</span></a> and <a href=\"https://mastodon.au/tags/philosophy\">#<span>philosophy</span></a>. Proudest sport moment: I once took a brilliant hat-trick in indoor <a href=\"https://mastodon.au/tags/cricket\">#<span>cricket</span></a>, Warne-style, with my legspin bowling - completely bamboozling the batsman. From <a href=\"https://mastodon.au/tags/australia\">#<span>australia</span></a>.</p>",
"text": "Seeing as I've thought of some other things I didn't manage to squeeze in last time, here's another #introduction - Lately I've been #writing tiny generic #fantasy #horror adventures in #pocketmod format for #ttrpgs. I plan to put these up on Itch. And maybe I'll put together a #neocities page since I come from a #retroweb era and find the resurrected #indieweb movement very interesting. That dovetails with my ongoing interests in #politics #psychology and #philosophy. Proudest sport moment: I once took a brilliant hat-trick in indoor #cricket, Warne-style, with my legspin bowling - completely bamboozling the batsman. From #australia."
},
"published": "2023-01-18T08:41:24+00:00",
"post-type": "note",
"_id": "34488945",
"_source": "7235",
"_is_read": false
}
Planiverse: a minimalist, no-JS front-end for Mastodon (or
Peroma, or anything supporting the Mastodon API).
The Web was once a document delivery platform. It's now an
application platform, which is great if you want everything to be
an application. But what if you don't? What if you use an older
computer, or like using a text-only browser, or simply prefer to
turn JavaScript off? This is the Mastodon front-end for you.
#fediverse #mastodon #indieweb #smolnet
https://git.stjo.hn/planiverse/file/README.html
{
"type": "entry",
"author": {
"name": "@sehnsucht",
"url": "https://social.sdf.org/@sehnsucht",
"photo": null
},
"url": "https://social.sdf.org/@sehnsucht/109708775813489288",
"content": {
"html": "<p>Planiverse: a minimalist, no-JS front-end for Mastodon (or<br />Peroma, or anything supporting the Mastodon API).</p><p>The Web was once a document delivery platform. It's now an<br />application platform, which is great if you want everything to be<br />an application. But what if you don't? What if you use an older<br />computer, or like using a text-only browser, or simply prefer to<br />turn JavaScript off? This is the Mastodon front-end for you.</p><p><a href=\"https://social.sdf.org/tags/fediverse\">#<span>fediverse</span></a> <a href=\"https://social.sdf.org/tags/mastodon\">#<span>mastodon</span></a> <a href=\"https://social.sdf.org/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://social.sdf.org/tags/smolnet\">#<span>smolnet</span></a><br /><a href=\"https://git.stjo.hn/planiverse/file/README.html\"><span>https://</span><span>git.stjo.hn/planiverse/file/RE</span><span>ADME.html</span></a></p>",
"text": "Planiverse: a minimalist, no-JS front-end for Mastodon (or\nPeroma, or anything supporting the Mastodon API).The Web was once a document delivery platform. It's now an\napplication platform, which is great if you want everything to be\nan application. But what if you don't? What if you use an older\ncomputer, or like using a text-only browser, or simply prefer to\nturn JavaScript off? This is the Mastodon front-end for you.#fediverse #mastodon #indieweb #smolnet\nhttps://git.stjo.hn/planiverse/file/README.html"
},
"published": "2023-01-18T06:24:28+00:00",
"post-type": "note",
"_id": "34487151",
"_source": "7235",
"_is_read": false
}
Replying to people on the social web used to be “simple” before #socialMedia, when we used blogs. You would either write:
1. a short reply — directly on someone’s blog post comment form, OR
2. a longer reply — on your own blog, in-reply-to & linking to the other post and send a Pingback, expecting at least the other post’s author to see your reply, or you would also write a short comment in their blog post comment form with a brief summary & link to your longer reply post
Aside: web forums^1 at the time were proto-silos^2, and replies/threads were generally self-contained therein.
Then social media exploded and eventually everybody was replying everywhere all at once.
This was so burdensome that some even hired social media managers to perform the labor of how (and if) to reply on each silo, and attempt to keep up with every new silo that popped up.
After a few years of this mid-to-late-2000s social web chaos, in the early 2010s many of us went back to option 2. above from the pre-social-media era, and as part of owning our data^3, started posting our replies in general on our own #IndieWeb sites:
1. Regardless of brevity or length, we resumed posting peer-to-peer replies on our personal sites (now sent site-to-site with Webmentions^4), watched destinations retrieve & display our comments, and were pleased that our peer-to-peer comments looked like any other comments (except with permalinks back to our originals).
2. We also started posting replies to tweets, GitHub issues^5, etc. on our own sites, and automatically POSSE-threading them into their sites of origin.
3. When we wrote site-to-site replies where the original post had itself been syndicated to social media^6, we did both 1 & 2. This let readers follow the conversation in either place, providing an #IndieWeb record for if/when the social media thread was taken down, or disappeared along with another silo shutdown^7.
Following this 1,2,3 approach helped conceptually simplify replying on the social web, and worked well except for a couple of interesting ongoing challenges:
* What is the most efficient user interface path from viewing someone else’s post to writing a reply from your own site?
* How should you @-mention someone you are replying to? (and how can our tools write or pre-fill that for us?)
Regarding the latter, on day 14 I wrote a bit about how should we @-mention in general https://tantek.com/2023/014/t4/domain-first-federated-atmention though that was more of a general @-mention exploration.
As a follow-up to day 14, it’s worth looking into @-reply mentions in particular, specifically for each of the above 1,2,3 contexts, analyzing examples of each, and looking for patterns of @-reply mentions best practices that we can document & recommend.
This is day 16 of #100DaysOfIndieWeb #100Days, except I didn’t finish writing it (mostly) til the morning after, and editing later that afternoon.
← Day 15: https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute
→ 🔮
^1 https://en.wikipedia.org/wiki/Internet_forum
^2 https://indieweb.org/silo
^3 https://indieweb.org/own_your_data
^4 https://tantek.com/2023/012/t1/six-years-webmention-w3c
^5 https://indieweb.org/GitHub#POSSE_to_GitHub
^6 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute
^7 https://indieweb.org/site-deaths
{
"type": "entry",
"published": "2023-01-17 09:05-0800",
"url": "http://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post",
"category": [
"socialMedia",
"IndieWeb",
"100DaysOfIndieWeb",
"100Days"
],
"content": {
"text": "Replying to people on the social web used to be \u201csimple\u201d before #socialMedia, when we used blogs. You would either write:\n\n1. a short reply \u2014 directly on someone\u2019s blog post comment form, OR\n\n2. a longer reply \u2014 on your own blog, in-reply-to & linking to the other post and send a Pingback, expecting at least the other post\u2019s author to see your reply, or you would also write a short comment in their blog post comment form with a brief summary & link to your longer reply post\n\nAside: web forums^1 at the time were proto-silos^2, and replies/threads were generally self-contained therein.\n\n\nThen social media exploded and eventually everybody was replying everywhere all at once.\n\nThis was so burdensome that some even hired social media managers to perform the labor of how (and if) to reply on each silo, and attempt to keep up with every new silo that popped up.\n\n\nAfter a few years of this mid-to-late-2000s social web chaos, in the early 2010s many of us went back to option 2. above from the pre-social-media era, and as part of owning our data^3, started posting our replies in general on our own #IndieWeb sites:\n\n1. Regardless of brevity or length, we resumed posting peer-to-peer replies on our personal sites (now sent site-to-site with Webmentions^4), watched destinations retrieve & display our comments, and were pleased that our peer-to-peer comments looked like any other comments (except with permalinks back to our originals).\n\n2. We also started posting replies to tweets, GitHub issues^5, etc. on our own sites, and automatically POSSE-threading them into their sites of origin.\n\n3. When we wrote site-to-site replies where the original post had itself been syndicated to social media^6, we did both 1 & 2. This let readers follow the conversation in either place, providing an #IndieWeb record for if/when the social media thread was taken down, or disappeared along with another silo shutdown^7.\n\n\nFollowing this 1,2,3 approach helped conceptually simplify replying on the social web, and worked well except for a couple of interesting ongoing challenges:\n\n* What is the most efficient user interface path from viewing someone else\u2019s post to writing a reply from your own site?\n\n* How should you @-mention someone you are replying to? (and how can our tools write or pre-fill that for us?)\n\nRegarding the latter, on day 14 I wrote a bit about how should we @-mention in general https://tantek.com/2023/014/t4/domain-first-federated-atmention though that was more of a general @-mention exploration. \n\nAs a follow-up to day 14, it\u2019s worth looking into @-reply mentions in particular, specifically for each of the above 1,2,3 contexts, analyzing examples of each, and looking for patterns of @-reply mentions best practices that we can document & recommend.\n\nThis is day 16 of #100DaysOfIndieWeb #100Days, except I didn\u2019t finish writing it (mostly) til the morning after, and editing later that afternoon.\n\n\u2190 Day 15: https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute\n\u2192 \ud83d\udd2e\n\n\n^1 https://en.wikipedia.org/wiki/Internet_forum\n^2 https://indieweb.org/silo\n^3 https://indieweb.org/own_your_data\n^4 https://tantek.com/2023/012/t1/six-years-webmention-w3c\n^5 https://indieweb.org/GitHub#POSSE_to_GitHub\n^6 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute\n^7 https://indieweb.org/site-deaths",
"html": "Replying to people on the social web used to be \u201csimple\u201d before #<span class=\"p-category\">socialMedia</span>, when we used blogs. You would either write:<br /><br />1. a short reply \u2014 directly on someone\u2019s blog post comment form, OR<br /><br />2. a longer reply \u2014 on your own blog, in-reply-to & linking to the other post and send a Pingback, expecting at least the other post\u2019s author to see your reply, or you would also write a short comment in their blog post comment form with a brief summary & link to your longer reply post<br /><br />Aside: web forums^1 at the time were proto-silos^2, and replies/threads were generally self-contained therein.<br /><br /><br />Then social media exploded and eventually everybody was replying everywhere all at once.<br /><br />This was so burdensome that some even hired social media managers to perform the labor of how (and if) to reply on each silo, and attempt to keep up with every new silo that popped up.<br /><br /><br />After a few years of this mid-to-late-2000s social web chaos, in the early 2010s many of us went back to option 2. above from the pre-social-media era, and as part of owning our data^3, started posting our replies in general on our own #<span class=\"p-category\">IndieWeb</span> sites:<br /><br />1. Regardless of brevity or length, we resumed posting peer-to-peer replies on our personal sites (now sent site-to-site with Webmentions^4), watched destinations retrieve & display our comments, and were pleased that our peer-to-peer comments looked like any other comments (except with permalinks back to our originals).<br /><br />2. We also started posting replies to tweets, GitHub issues^5, etc. on our own sites, and automatically POSSE-threading them into their sites of origin.<br /><br />3. When we wrote site-to-site replies where the original post had itself been syndicated to social media^6, we did both 1 & 2. This let readers follow the conversation in either place, providing an #<span class=\"p-category\">IndieWeb</span> record for if/when the social media thread was taken down, or disappeared along with another silo shutdown^7.<br /><br /><br />Following this 1,2,3 approach helped conceptually simplify replying on the social web, and worked well except for a couple of interesting ongoing challenges:<br /><br />* What is the most efficient user interface path from viewing someone else\u2019s post to writing a reply from your own site?<br /><br />* How should you @-mention someone you are replying to? (and how can our tools write or pre-fill that for us?)<br /><br />Regarding the latter, on day 14 I wrote a bit about how should we @-mention in general <a href=\"https://tantek.com/2023/014/t4/domain-first-federated-atmention\">https://tantek.com/2023/014/t4/domain-first-federated-atmention</a> though that was more of a general @-mention exploration. <br /><br />As a follow-up to day 14, it\u2019s worth looking into @-reply mentions in particular, specifically for each of the above 1,2,3 contexts, analyzing examples of each, and looking for patterns of @-reply mentions best practices that we can document & recommend.<br /><br />This is day 16 of #<span class=\"p-category\">100DaysOfIndieWeb</span> #<span class=\"p-category\">100Days</span>, except I didn\u2019t finish writing it (mostly) til the morning after, and editing later that afternoon.<br /><br />\u2190 Day 15: <a href=\"https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute\">https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute</a><br />\u2192 \ud83d\udd2e<br /><br /><br />^1 <a href=\"https://en.wikipedia.org/wiki/Internet_forum\">https://en.wikipedia.org/wiki/Internet_forum</a><br />^2 <a href=\"https://indieweb.org/silo\">https://indieweb.org/silo</a><br />^3 <a href=\"https://indieweb.org/own_your_data\">https://indieweb.org/own_your_data</a><br />^4 <a href=\"https://tantek.com/2023/012/t1/six-years-webmention-w3c\">https://tantek.com/2023/012/t1/six-years-webmention-w3c</a><br />^5 <a href=\"https://indieweb.org/GitHub#POSSE_to_GitHub\">https://indieweb.org/GitHub#POSSE_to_GitHub</a><br />^6 <a href=\"https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute\">https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute</a><br />^7 <a href=\"https://indieweb.org/site-deaths\">https://indieweb.org/site-deaths</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": "34485634",
"_source": "1",
"_is_read": false
}
In the process of transforming my elizabethtai.com #website into an #indieweb #digitalgarden and I'm so hyperfocused on it it's hard to work lol.
{
"type": "entry",
"author": {
"name": "@liztai",
"url": "https://hachyderm.io/@liztai",
"photo": null
},
"url": "https://hachyderm.io/@liztai/109708141805304505",
"content": {
"html": "<p>In the process of transforming my elizabethtai.com <a href=\"https://hachyderm.io/tags/website\">#<span>website</span></a> into an <a href=\"https://hachyderm.io/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://hachyderm.io/tags/digitalgarden\">#<span>digitalgarden</span></a> and I'm so hyperfocused on it it's hard to work lol.</p>",
"text": "In the process of transforming my elizabethtai.com #website into an #indieweb #digitalgarden and I'm so hyperfocused on it it's hard to work lol."
},
"published": "2023-01-18T03:43:14+00:00",
"post-type": "note",
"_id": "34485546",
"_source": "7235",
"_is_read": false
}
Seeing as I've thought of some other things I didn't manage to squeeze in last time, here's another #introduction - Lately I've been #writing tiny generic #fantasy #horror adventures in #pocketmod format for #ttrpgs. I plan to put these up on Itch. And maybe I'll put together a #neocities page since I come from a #retroweb era and find the resurrected #indieweb movement very interesting. That dovetails with my ongoing interests in #politics #psychology and #philosophy. Proudest sport moment: I once took a brilliant hat-trick in indoor #cricket, Warne-style, with my legspin bowling - completely bamboozling the batsman.
{
"type": "entry",
"author": {
"name": "@lime_juice_cube",
"url": "https://mastodon.au/@lime_juice_cube",
"photo": null
},
"url": "https://mastodon.au/@lime_juice_cube/109707444862394038",
"content": {
"html": "<p>Seeing as I've thought of some other things I didn't manage to squeeze in last time, here's another <a href=\"https://mastodon.au/tags/introduction\">#<span>introduction</span></a> - Lately I've been <a href=\"https://mastodon.au/tags/writing\">#<span>writing</span></a> tiny generic <a href=\"https://mastodon.au/tags/fantasy\">#<span>fantasy</span></a> <a href=\"https://mastodon.au/tags/horror\">#<span>horror</span></a> adventures in <a href=\"https://mastodon.au/tags/pocketmod\">#<span>pocketmod</span></a> format for <a href=\"https://mastodon.au/tags/ttrpgs\">#<span>ttrpgs</span></a>. I plan to put these up on Itch. And maybe I'll put together a <a href=\"https://mastodon.au/tags/neocities\">#<span>neocities</span></a> page since I come from a <a href=\"https://mastodon.au/tags/retroweb\">#<span>retroweb</span></a> era and find the resurrected <a href=\"https://mastodon.au/tags/indieweb\">#<span>indieweb</span></a> movement very interesting. That dovetails with my ongoing interests in <a href=\"https://mastodon.au/tags/politics\">#<span>politics</span></a> <a href=\"https://mastodon.au/tags/psychology\">#<span>psychology</span></a> and <a href=\"https://mastodon.au/tags/philosophy\">#<span>philosophy</span></a>. Proudest sport moment: I once took a brilliant hat-trick in indoor <a href=\"https://mastodon.au/tags/cricket\">#<span>cricket</span></a>, Warne-style, with my legspin bowling - completely bamboozling the batsman.</p>",
"text": "Seeing as I've thought of some other things I didn't manage to squeeze in last time, here's another #introduction - Lately I've been #writing tiny generic #fantasy #horror adventures in #pocketmod format for #ttrpgs. I plan to put these up on Itch. And maybe I'll put together a #neocities page since I come from a #retroweb era and find the resurrected #indieweb movement very interesting. That dovetails with my ongoing interests in #politics #psychology and #philosophy. Proudest sport moment: I once took a brilliant hat-trick in indoor #cricket, Warne-style, with my legspin bowling - completely bamboozling the batsman."
},
"published": "2023-01-18T00:45:59+00:00",
"post-type": "note",
"_id": "34484017",
"_source": "7235",
"_is_read": false
}
Day 10 of 100 #100DaysofIndieWeb, #IndieWeb, #ProjectJournal, #ProjectManagement #WordPress
Today, I had hoped to have a plan documented to for my WordPress RSVP Block Pattern. Since yesterday I have been working on:
* Learn About Webmentions a Little More Deeply.
I read the Webmention specification from the W3C. Reading the spec was very informative. Even though I am going to have to read it again. And there will be some things that I will not understand, maybe… https://tmichellemoore.com/?p=152147
{
"type": "entry",
"author": {
"name": "@tmichellemoore",
"url": "https://mastodon.social/@tmichellemoore",
"photo": null
},
"url": "https://mastodon.social/@tmichellemoore/109707188179945313",
"content": {
"html": "<p>Day 10 of 100 <a href=\"https://mastodon.social/tags/100DaysofIndieWeb\">#<span>100DaysofIndieWeb</span></a>, <a href=\"https://mastodon.social/tags/IndieWeb\">#<span>IndieWeb</span></a>, <a href=\"https://mastodon.social/tags/ProjectJournal\">#<span>ProjectJournal</span></a>, <a href=\"https://mastodon.social/tags/ProjectManagement\">#<span>ProjectManagement</span></a> <a href=\"https://mastodon.social/tags/WordPress\">#<span>WordPress</span></a></p><p>Today, I had hoped to have a plan documented to for my WordPress RSVP Block Pattern. Since yesterday I have been working on:</p><p> * Learn About Webmentions a Little More Deeply.</p><p>I read the Webmention specification from the W3C. Reading the spec was very informative. Even though I am going to have to read it again. And there will be some things that I will not understand, maybe\u2026 <a href=\"https://tmichellemoore.com/?p=152147\"><span>https://</span><span>tmichellemoore.com/?p=152147</span><span></span></a></p>",
"text": "Day 10 of 100 #100DaysofIndieWeb, #IndieWeb, #ProjectJournal, #ProjectManagement #WordPressToday, I had hoped to have a plan documented to for my WordPress RSVP Block Pattern. Since yesterday I have been working on: * Learn About Webmentions a Little More Deeply.I read the Webmention specification from the W3C. Reading the spec was very informative. Even though I am going to have to read it again. And there will be some things that I will not understand, maybe\u2026 https://tmichellemoore.com/?p=152147"
},
"published": "2023-01-17T23:40:43+00:00",
"post-type": "note",
"_id": "34483181",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "Manton Reece",
"url": "https://www.manton.org/",
"photo": "https://micro.blog/manton/avatar.jpg"
},
"url": "https://www.manton.org/2023/01/17/more-brief-thoughts.html",
"name": "More brief thoughts on the end of Twitter apps",
"content": {
"html": "<p>I was re-reading <a href=\"https://furbo.org/2023/01/15/the-shit-show/\">Craig Hockenberry\u2019s post</a> on the third-party Twitter apps shutdown. It\u2019s a great post, channeling the frustration of so many developers and users. And I love that it\u2019s on his blog, not as a tweet or toot. Ideas and writing sometimes need space to breath on the web.</p>\n<p>Everyone had a different last straw with Twitter. It helped to have a villain in Elon Musk who could be blamed for every bad decision in the <a href=\"https://www.theverge.com/23551060/elon-musk-twitter-takeover-layoffs-workplace-salute-emoji\">growing narrative of Twitter acquisition chaos</a>.</p>\n<p>But one problem with pinning everything on Elon is that it leaves open the possibility that maybe Twitter would be fine if the company was led by a different CEO who continued the Twitter API status quo. I don\u2019t think so. Twitter wasn\u2019t going to last forever because massive ad-based silos will always be at odds with the open web. Twitter\u2019s recent implosion greatly accelerated what would need to happen regardless.</p>\n<p><a href=\"https://twitter.com/TwitterDev/status/1615405842735714304\">Today we got Twitter\u2019s first public statement</a> that the apps shutdown was about API rules. Remember back in 2012 they announced that apps could not have more than 100k users, even if popular apps at the time were exempted. There were other restrictions too, largely ignored. Third-party Twitter apps were living on borrowed time, strung along with false hope every few years as Twitter\u2019s leadership drifted back and forth on whether to encourage developers or cut them off.</p>\n<p>Craig also highlights open standards like ActivityPub in his blog post, and how the future shouldn\u2019t be Mastodon-only:</p>\n<blockquote>\n<p>Federation exposes a lot of different data sources that you\u2019d want to follow. Not all of these sources will be <a href=\"https://joinmastodon.org/\">Mastodon</a> instances: you may want to stay up-to-date with someone\u2019s <a href=\"https://micro.blog/\">Micro.blog</a>, or maybe another person\u2019s <a href=\"https://techcrunch.com/2022/11/21/tumblr-to-add-support-for-activitypub-the-social-protocol-powering-mastodon-and-other-apps/\">Tumblr</a>, or someone else\u2019s <a href=\"https://pixelfed.org/\">photo feed</a>.</p>\n</blockquote>\n<p>The sudden migration to Mastodon is going to make Mastodon look a lot like Twitter in the coming months. Don\u2019t get me wrong: the migration is a great thing. Smaller social networks is one of the four parts <a href=\"https://www.manton.org/2018/09/07/the-way-out.html\">I blogged about in 2018</a> for how to get out of the social network mess. But we need new apps and ideas too, to not recreate some of the same problems again.</p>",
"text": "I was re-reading Craig Hockenberry\u2019s post on the third-party Twitter apps shutdown. It\u2019s a great post, channeling the frustration of so many developers and users. And I love that it\u2019s on his blog, not as a tweet or toot. Ideas and writing sometimes need space to breath on the web.\nEveryone had a different last straw with Twitter. It helped to have a villain in Elon Musk who could be blamed for every bad decision in the growing narrative of Twitter acquisition chaos.\nBut one problem with pinning everything on Elon is that it leaves open the possibility that maybe Twitter would be fine if the company was led by a different CEO who continued the Twitter API status quo. I don\u2019t think so. Twitter wasn\u2019t going to last forever because massive ad-based silos will always be at odds with the open web. Twitter\u2019s recent implosion greatly accelerated what would need to happen regardless.\nToday we got Twitter\u2019s first public statement that the apps shutdown was about API rules. Remember back in 2012 they announced that apps could not have more than 100k users, even if popular apps at the time were exempted. There were other restrictions too, largely ignored. Third-party Twitter apps were living on borrowed time, strung along with false hope every few years as Twitter\u2019s leadership drifted back and forth on whether to encourage developers or cut them off.\nCraig also highlights open standards like ActivityPub in his blog post, and how the future shouldn\u2019t be Mastodon-only:\n\nFederation exposes a lot of different data sources that you\u2019d want to follow. Not all of these sources will be Mastodon instances: you may want to stay up-to-date with someone\u2019s Micro.blog, or maybe another person\u2019s Tumblr, or someone else\u2019s photo feed.\n\nThe sudden migration to Mastodon is going to make Mastodon look a lot like Twitter in the coming months. Don\u2019t get me wrong: the migration is a great thing. Smaller social networks is one of the four parts I blogged about in 2018 for how to get out of the social network mess. But we need new apps and ideas too, to not recreate some of the same problems again."
},
"published": "2023-01-17T13:42:15-06:00",
"category": [
"Essays"
],
"post-type": "article",
"_id": "34481579",
"_source": "12",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "@mor10",
"url": "https://front-end.social/@mor10",
"photo": null
},
"url": "https://front-end.social/@mor10/109706366166296025",
"content": {
"html": "<p>Personal <a href=\"https://front-end.social/tags/blog\">#<span>blog</span></a> link for those who prefer the <a href=\"https://front-end.social/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://mor10.com/pair-programming-with-ai/\"><span>https://</span><span>mor10.com/pair-programming-wit</span><span>h-ai/</span></a></p>",
"text": "Personal #blog link for those who prefer the #indieweb https://mor10.com/pair-programming-with-ai/"
},
"published": "2023-01-17T20:11:40+00:00",
"post-type": "note",
"_id": "34478487",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "@krosylight",
"url": "https://fosstodon.org/@krosylight",
"photo": null
},
"url": "https://fosstodon.org/@krosylight/109706321646424453",
"content": {
"html": "<p>TIL there's <a href=\"https://fosstodon.org/tags/indieweb\">#<span>indieweb</span></a> living standard <a href=\"https://indieauth.spec.indieweb.org/20201126/\"><span>https://</span><span>indieauth.spec.indieweb.org/20</span><span>201126/</span></a></p>",
"text": "TIL there's #indieweb living standard https://indieauth.spec.indieweb.org/20201126/"
},
"published": "2023-01-17T20:00:20+00:00",
"post-type": "note",
"_id": "34478488",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "@box464",
"url": "https://mastodon.social/@box464",
"photo": null
},
"url": "https://mastodon.social/@box464/109702985034705429",
"content": {
"html": "<p>Slowly getting <a href=\"https://mastodon.social/tags/IndieWeb\">#<span>IndieWeb</span></a> configurations setup on my site. Added h-card values to my post templates. </p><p><a href=\"https://indiewebify.me/validate-h-entry/?url=https%3A%2F%2Fbox464.com%2Fdevops%2F2023%2F01%2F10%2Fwhats-up-doc%2F\"><span>https://</span><span>indiewebify.me/validate-h-entr</span><span>y/?url=https%3A%2F%2Fbox464.com%2Fdevops%2F2023%2F01%2F10%2Fwhats-up-doc%2F</span></a></p>",
"text": "Slowly getting #IndieWeb configurations setup on my site. Added h-card values to my post templates. https://indiewebify.me/validate-h-entry/?url=https%3A%2F%2Fbox464.com%2Fdevops%2F2023%2F01%2F10%2Fwhats-up-doc%2F"
},
"published": "2023-01-17T05:51:48+00:00",
"post-type": "note",
"_id": "34462434",
"_source": "7235",
"_is_read": false
}
I am having trouble figuring out how to set the way that posts display on Mastodon. There used to be a page in the IndieWeb or ActivityPub settings where you could choose the order like Title, Excerpt, Link, etc. Now I can't find it. So it just posts either an image or just the link with no context. I don't know how it got that way or how to change it. #IndieWeb #ActivityPub
{
"type": "entry",
"author": {
"name": "@IronWynch",
"url": "https://mastodon.social/@IronWynch",
"photo": null
},
"url": "https://mastodon.social/@IronWynch/109702297176192043",
"content": {
"html": "<p>I am having trouble figuring out how to set the way that posts display on Mastodon. There used to be a page in the IndieWeb or ActivityPub settings where you could choose the order like Title, Excerpt, Link, etc. Now I can't find it. So it just posts either an image or just the link with no context. I don't know how it got that way or how to change it. <a href=\"https://mastodon.social/tags/IndieWeb\">#<span>IndieWeb</span></a> <a href=\"https://mastodon.social/tags/ActivityPub\">#<span>ActivityPub</span></a></p>",
"text": "I am having trouble figuring out how to set the way that posts display on Mastodon. There used to be a page in the IndieWeb or ActivityPub settings where you could choose the order like Title, Excerpt, Link, etc. Now I can't find it. So it just posts either an image or just the link with no context. I don't know how it got that way or how to change it. #IndieWeb #ActivityPub"
},
"published": "2023-01-17T02:56:52+00:00",
"post-type": "note",
"_id": "34460824",
"_source": "7235",
"_is_read": false
}