{
"type": "entry",
"author": {
"name": "@tchambers",
"url": "https://indieweb.social/@tchambers",
"photo": null
},
"url": "https://indieweb.social/@tchambers/110253116793791797",
"content": {
"html": "<p><span class=\"h-card\"><a class=\"u-url\" href=\"https://mininull.com/@mookie\">@<span>mookie</span></a></span> <span class=\"h-card\"><a class=\"u-url\" href=\"https://mastodon.social/@spreadmastodon\">@<span>spreadmastodon</span></a></span> <span class=\"h-card\"><a class=\"u-url\" href=\"https://mastodon.social/@davidslifka\">@<span>davidslifka</span></a></span> </p><p>Thanks Steve: it is a start and much more in May! </p><p>Appreciate the encouragement! Hope to bring the most broad set of <a href=\"https://indieweb.social/tags/indieweb\">#<span>indieweb</span></a>, <a href=\"https://indieweb.social/tags/openweb\">#<span>openweb</span></a>, snd <a href=\"https://indieweb.social/tags/fediverse\">#<span>fediverse</span></a> advocates possible to <a href=\"https://indieweb.social/tags/TakeBackSocial\">#<span>TakeBackSocial</span></a> \u2026.and can use your help!</p>",
"text": "@mookie @spreadmastodon @davidslifka Thanks Steve: it is a start and much more in May! Appreciate the encouragement! Hope to bring the most broad set of #indieweb, #openweb, snd #fediverse advocates possible to #TakeBackSocial \u2026.and can use your help!"
},
"published": "2023-04-24T09:37:32+00:00",
"post-type": "note",
"_id": "36751336",
"_source": "7235",
"_is_read": false
}
@spreadmastodon@mastodon.social it is one of the more amazing examples of emergent distributed alignment that I have seen. There is so much overlap across efforts, principles¹, and goals that it makes sense that we are finding ways of making things seamlessly work together at the edges.
I also see a common desire for enabling more user-owned use of and creating for the web, independent of big corporate ownership (or control), and without any reliance or need for surveillance capitalism.
#Fediverse #IndieWeb #Mastodon #OpenWeb #SpreadMastodon projects do not depend on tracking & profiling users for targeted advertising.
{
"type": "entry",
"published": "2023-04-23 17:00-0700",
"url": "http://tantek.com/2023/113/t4/",
"category": [
"Fediverse",
"IndieWeb",
"Mastodon",
"OpenWeb",
"SpreadMastodon"
],
"in-reply-to": [
"https://mastodon.social/@spreadmastodon/110249767459591081"
],
"content": {
"text": "@spreadmastodon@mastodon.social it is one of the more amazing examples of emergent distributed alignment that I have seen. There is so much overlap across efforts, principles\u00b9, and goals that it makes sense that we are finding ways of making things seamlessly work together at the edges.\n\nI also see a common desire for enabling more user-owned use of and creating for the web, independent of big corporate ownership (or control), and without any reliance or need for surveillance capitalism.\n\n#Fediverse #IndieWeb #Mastodon #OpenWeb #SpreadMastodon projects do not depend on tracking & profiling users for targeted advertising.\n\nA better web is possible.\n\n\u00b9 https://indieweb.org/principles",
"html": "<a href=\"https://mastodon.social/@spreadmastodon\">@spreadmastodon@mastodon.social</a> it is one of the more amazing examples of emergent distributed alignment that I have seen. There is so much overlap across efforts, principles<a href=\"http://tantek.com/#t5QW4_note-1\">\u00b9</a>, and goals that it makes sense that we are finding ways of making things seamlessly work together at the edges.<br /><br />I also see a common desire for enabling more user-owned use of and creating for the web, independent of big corporate ownership (or control), and without any reliance or need for surveillance capitalism.<br /><br />#<span class=\"p-category\">Fediverse</span> #<span class=\"p-category\">IndieWeb</span> #<span class=\"p-category\">Mastodon</span> #<span class=\"p-category\">OpenWeb</span> #<span class=\"p-category\">SpreadMastodon</span> projects do not depend on tracking & profiling users for targeted advertising.<br /><br />A better web is possible.<br /><br /><a href=\"http://tantek.com/#t5QW4_ref-1\">\u00b9</a> <a href=\"https://indieweb.org/principles\">https://indieweb.org/principles</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "http://tantek.com/",
"photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "reply",
"refs": {
"https://mastodon.social/@spreadmastodon/110249767459591081": {
"type": "entry",
"url": "https://mastodon.social/@spreadmastodon/110249767459591081",
"name": "mastodon.social user spreadmastodon\u2019s post",
"post-type": "article"
}
},
"_id": "36746935",
"_source": "1",
"_is_read": false
}
@maegul@hachyderm.io@torb@octodon.social #BlueSky is a fascinating experiment to watch, and if there’s one thing we’ve learned from all the work on decentralized/federated social web systems over the past 13+ years (certainly since the first Federated Social Web Summit¹), there’s LOTS of room for and benefits to many folks working on solving many hard problems in parallel, even if with totally different approaches, which can learn from each other.
We learned this lesson in the #W3C Social Web Working Group².
Also a key reason the #IndieWeb community adopted a core principle of Plurality³.
I have a lot of sympathy for "so many non-techies bounce off Mastodon because it’s just too technically difficult for them", it’s one of the reasons I send most folks directly to https://micro.blog/ — it supports following / #federating with #Mastodon, and it supports core IndieWeb W3C standards like Webmention and Micropub.
Regarding what portability requires, I for one disagree that account or post portability needs "signed data repositories and DIDs". I believe that cooperative server-to-server portability can be achieved without it, and frankly, if you‘re wanting to design for uncooperative servers, what expectation can you have that they’ll support any standards or interop whatsoever?
Beyond Mastodon-to-Mastodon account migration, we already have Mastodon-to-BridgyFed (IndieWeb) and Mastodon - to - Micro.blog, and I expect we’ll see that grow to include all directions of all combinations thereof.
I am also optimistic that the “fediverse” will continue evolving various solutions that put users first in different ways, because there are users with different needs.
There’s certainly a current #fediverse hierarchy that puts a lot of power (and burden of responsibility) in the hands of ”server/instance” admins — “feudalverse” was a running joke for a while, reflecting a #federation of instance admin feudal lords and their user serfs.
Ironically, the more that account+posts migration/portability is supported, the more incentive there will be for harmonious and respectful relationships between instance admins and users, so I only see this situation improving in the future.
Long reply summarized: I think the folks innovating at BlueSky are charting interesting waters, the Mastodon development community continues show through improvements that they prioritize users and their identity & data ownership, and the IndieWeb community continues to support & play with those and many other solutions, building bridges⁴ between⁵ them⁶ to interconnect all the things.
{
"type": "entry",
"published": "2023-04-23 16:43-0700",
"url": "http://tantek.com/2023/113/t3/",
"category": [
"BlueSky",
"W3C",
"IndieWeb",
"federating",
"Mastodon",
"fediverse",
"federation"
],
"in-reply-to": [
"https://hachyderm.io/@maegul/110247571428373383"
],
"content": {
"text": "@maegul@hachyderm.io @torb@octodon.social #BlueSky is a fascinating experiment to watch, and if there\u2019s one thing we\u2019ve learned from all the work on decentralized/federated social web systems over the past 13+ years (certainly since the first Federated Social Web Summit\u00b9), there\u2019s LOTS of room for and benefits to many folks working on solving many hard problems in parallel, even if with totally different approaches, which can learn from each other.\n\nWe learned this lesson in the #W3C Social Web Working Group\u00b2.\n\nAlso a key reason the #IndieWeb community adopted a core principle of Plurality\u00b3.\n\nI have a lot of sympathy for \"so many non-techies bounce off Mastodon because it\u2019s just too technically difficult for them\", it\u2019s one of the reasons I send most folks directly to https://micro.blog/ \u2014 it supports following / #federating with #Mastodon, and it supports core IndieWeb W3C standards like Webmention and Micropub.\n\nRegarding what portability requires, I for one disagree that account or post portability needs \"signed data repositories and DIDs\". I believe that cooperative server-to-server portability can be achieved without it, and frankly, if you\u2018re wanting to design for uncooperative servers, what expectation can you have that they\u2019ll support any standards or interop whatsoever?\n\nBeyond Mastodon-to-Mastodon account migration, we already have Mastodon-to-BridgyFed (IndieWeb) and Mastodon - to - Micro.blog, and I expect we\u2019ll see that grow to include all directions of all combinations thereof.\n\nI am also optimistic that the \u201cfediverse\u201d will continue evolving various solutions that put users first in different ways, because there are users with different needs. \n\nThere\u2019s certainly a current #fediverse hierarchy that puts a lot of power (and burden of responsibility) in the hands of \u201dserver/instance\u201d admins \u2014 \u201cfeudalverse\u201d was a running joke for a while, reflecting a #federation of instance admin feudal lords and their user serfs. \n\nIronically, the more that account+posts migration/portability is supported, the more incentive there will be for harmonious and respectful relationships between instance admins and users, so I only see this situation improving in the future.\n\nLong reply summarized: I think the folks innovating at BlueSky are charting interesting waters, the Mastodon development community continues show through improvements that they prioritize users and their identity & data ownership, and the IndieWeb community continues to support & play with those and many other solutions, building bridges\u2074 between\u2075 them\u2076 to interconnect all the things.\n\nGlossary\n\nBridgyFed\n\u00a0https://fed.brid.gy/\nMicropub\n\u00a0https://indieweb.org/Micropub\nWebmention\n\u00a0https://indieweb.org/Webmention\n\nReferences\n\n\u00b9 https://indieweb.org/Federated_Social_Web_Summit#Portland_2010\n\u00b2 https://tantek.com/2023/051/t1/five-years-ago-w3c-social-web\n\u00b3 https://indieweb.org/plurality\n\u2074 https://brid.gy/\n\u2075 https://fed.brid.gy/\n\u2076 https://github.com/snarfed/bridgy-fed/issues/381",
"html": "<a href=\"https://hachyderm.io/@maegul\">@maegul@hachyderm.io</a> <a href=\"https://octodon.social/@torb\">@torb@octodon.social</a> #<span class=\"p-category\">BlueSky</span> is a fascinating experiment to watch, and if there\u2019s one thing we\u2019ve learned from all the work on decentralized/federated social web systems over the past 13+ years (certainly since the first Federated Social Web Summit<a href=\"http://tantek.com/#t5QW3_note-1\">\u00b9</a>), there\u2019s LOTS of room for and benefits to many folks working on solving many hard problems in parallel, even if with totally different approaches, which can learn from each other.<br /><br />We learned this lesson in the #<span class=\"p-category\">W3C</span> Social Web Working Group<a href=\"http://tantek.com/#t5QW3_note-2\">\u00b2</a>.<br /><br />Also a key reason the #<span class=\"p-category\">IndieWeb</span> community adopted a core principle of Plurality<a href=\"http://tantek.com/#t5QW3_note-3\">\u00b3</a>.<br /><br />I have a lot of sympathy for \"so many non-techies bounce off Mastodon because it\u2019s just too technically difficult for them\", it\u2019s one of the reasons I send most folks directly to <a href=\"https://micro.blog/\">https://micro.blog/</a> \u2014 it supports following / #<span class=\"p-category\">federating</span> with #<span class=\"p-category\">Mastodon</span>, and it supports core IndieWeb W3C standards like Webmention and Micropub.<br /><br />Regarding what portability requires, I for one disagree that account or post portability needs \"signed data repositories and DIDs\". I believe that cooperative server-to-server portability can be achieved without it, and frankly, if you\u2018re wanting to design for uncooperative servers, what expectation can you have that they\u2019ll support any standards or interop whatsoever?<br /><br />Beyond Mastodon-to-Mastodon account migration, we already have Mastodon-to-BridgyFed (IndieWeb) and Mastodon - to - <a href=\"http://Micro.blog\">Micro.blog</a>, and I expect we\u2019ll see that grow to include all directions of all combinations thereof.<br /><br />I am also optimistic that the \u201cfediverse\u201d will continue evolving various solutions that put users first in different ways, because there are users with different needs. <br /><br />There\u2019s certainly a current #<span class=\"p-category\">fediverse</span> hierarchy that puts a lot of power (and burden of responsibility) in the hands of \u201dserver/instance\u201d admins \u2014 \u201cfeudalverse\u201d was a running joke for a while, reflecting a #<span class=\"p-category\">federation</span> of instance admin feudal lords and their user serfs. <br /><br />Ironically, the more that account+posts migration/portability is supported, the more incentive there will be for harmonious and respectful relationships between instance admins and users, so I only see this situation improving in the future.<br /><br />Long reply summarized: I think the folks innovating at BlueSky are charting interesting waters, the Mastodon development community continues show through improvements that they prioritize users and their identity & data ownership, and the IndieWeb community continues to support & play with those and many other solutions, building bridges<a href=\"http://tantek.com/#t5QW3_note-4\">\u2074</a> between<a href=\"http://tantek.com/#t5QW3_note-5\">\u2075</a> them<a href=\"http://tantek.com/#t5QW3_note-6\">\u2076</a> to interconnect all the things.<br /><br />Glossary<br /><br />BridgyFed<br />\u00a0<a href=\"https://fed.brid.gy/\">https://fed.brid.gy/</a><br />Micropub<br />\u00a0<a href=\"https://indieweb.org/Micropub\">https://indieweb.org/Micropub</a><br />Webmention<br />\u00a0<a href=\"https://indieweb.org/Webmention\">https://indieweb.org/Webmention</a><br /><br />References<br /><br /><a href=\"http://tantek.com/#t5QW3_ref-1\">\u00b9</a> <a href=\"https://indieweb.org/Federated_Social_Web_Summit#Portland_2010\">https://indieweb.org/Federated_Social_Web_Summit#Portland_2010</a><br /><a href=\"http://tantek.com/#t5QW3_ref-2\">\u00b2</a> <a href=\"https://tantek.com/2023/051/t1/five-years-ago-w3c-social-web\">https://tantek.com/2023/051/t1/five-years-ago-w3c-social-web</a><br /><a href=\"http://tantek.com/#t5QW3_ref-3\">\u00b3</a> <a href=\"https://indieweb.org/plurality\">https://indieweb.org/plurality</a><br /><a href=\"http://tantek.com/#t5QW3_ref-4\">\u2074</a> <a href=\"https://brid.gy/\">https://brid.gy/</a><br /><a href=\"http://tantek.com/#t5QW3_ref-5\">\u2075</a> <a href=\"https://fed.brid.gy/\">https://fed.brid.gy/</a><br /><a href=\"http://tantek.com/#t5QW3_ref-6\">\u2076</a> <a href=\"https://github.com/snarfed/bridgy-fed/issues/381\">https://github.com/snarfed/bridgy-fed/issues/381</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "http://tantek.com/",
"photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "reply",
"refs": {
"https://hachyderm.io/@maegul/110247571428373383": {
"type": "entry",
"url": "https://hachyderm.io/@maegul/110247571428373383",
"name": "hachyderm.io user maegul\u2019s post",
"post-type": "article"
}
},
"_id": "36746936",
"_source": "1",
"_is_read": false
}
@spreadmastodon@mastodon.social it is one of the more amazing examples of emergent distributed alignment that I have seen. There is so much overlap across efforts, principles¹, and goals that it makes sense that we are finding ways of making things seamlessly work together at the edges.
I also see a common desire for enabling more user-owned use of and creating for the web, independent of big corporate ownership (or control), and without any reliance or need for surveillance capitalism.
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://fed.brid.gy/r/https://tantek.com/2023/113/t4/",
"content": {
"html": "<a href=\"https://mastodon.social/@spreadmastodon\">@spreadmastodon@mastodon.social</a> it is one of the more amazing examples of emergent distributed alignment that I have seen. There is so much overlap across efforts, principles\u00b9, and goals that it makes sense that we are finding ways of making things seamlessly work together at the edges.<br /><br />I also see a common desire for enabling more user-owned use of and creating for the web, independent of big corporate ownership (or control), and without any reliance or need for surveillance capitalism.<br /><br /><a href=\"https://indieweb.social/tags/Fediverse\">#<span class=\"p-category\">Fediverse</span></a> <a href=\"https://indieweb.social/tags/IndieWeb\">#<span class=\"p-category\">IndieWeb</span></a> <a href=\"https://indieweb.social/tags/Mastodon\">#<span class=\"p-category\">Mastodon</span></a> <a href=\"https://indieweb.social/tags/OpenWeb\">#<span class=\"p-category\">OpenWeb</span></a> <a href=\"https://indieweb.social/tags/SpreadMastodon\">#<span class=\"p-category\">SpreadMastodon</span></a> projects do not depend on tracking & profiling users for targeted advertising.<br /><br />A better web is possible.<br /><br />\u00b9 <a href=\"https://indieweb.org/principles\">https://indieweb.org/principles</a>",
"text": "@spreadmastodon@mastodon.social it is one of the more amazing examples of emergent distributed alignment that I have seen. There is so much overlap across efforts, principles\u00b9, and goals that it makes sense that we are finding ways of making things seamlessly work together at the edges.\n\nI also see a common desire for enabling more user-owned use of and creating for the web, independent of big corporate ownership (or control), and without any reliance or need for surveillance capitalism.\n\n#Fediverse #IndieWeb #Mastodon #OpenWeb #SpreadMastodon projects do not depend on tracking & profiling users for targeted advertising.\n\nA better web is possible.\n\n\u00b9 https://indieweb.org/principles"
},
"published": "2023-04-24T00:00:00+00:00",
"post-type": "note",
"_id": "36745490",
"_source": "7235",
"_is_read": false
}
@maegul@hachyderm.io@torb@octodon.social#BlueSky is a fascinating experiment to watch, and if there’s one thing we’ve learned from all the work on decentralized/federated social web systems over the past 13+ years (certainly since the first Federated Social Web Summit¹), there’s LOTS of room for and benefits to many folks working on solving many hard problems in parallel, even if with totally different approaches, which can learn from each other.
We learned this lesson in the #W3C Social Web Working Group².
Also a key reason the #IndieWeb community adopted a core principle of Plurality³.
I have a lot of sympathy for "so many non-techies bounce off Mastodon because it’s just too technically difficult for them", it’s one of the reasons I send most folks directly to https://micro.blog/ — it supports following / #federating with #Mastodon, and it supports core IndieWeb W3C standards like Webmention and Micropub.
Regarding what portability requires, I for one disagree that account or post portability needs "signed data repositories and DIDs". I believe that cooperative server-to-server portability can be achieved without it, and frankly, if you‘re wanting to design for uncooperative servers, what expectation can you have that they’ll support any standards or interop whatsoever?
Beyond Mastodon-to-Mastodon account migration, we already have Mastodon-to-BridgyFed (IndieWeb) and Mastodon - to - Micro.blog, and I expect we’ll see that grow to include all directions of all combinations thereof.
I am also optimistic that the “fediverse” will continue evolving various solutions that put users first in different ways, because there are users with different needs.
There’s certainly a current #fediverse hierarchy that puts a lot of power (and burden of responsibility) in the hands of ”server/instance” admins — “feudalverse” was a running joke for a while, reflecting a #federation of instance admin feudal lords and their user serfs.
Ironically, the more that account+posts migration/portability is supported, the more incentive there will be for harmonious and respectful relationships between instance admins and users, so I only see this situation improving in the future.
Long reply summarized: I think the folks innovating at BlueSky are charting interesting waters, the Mastodon development community continues show through improvements that they prioritize users and their identity & data ownership, and the IndieWeb community continues to support & play with those and many other solutions, building bridges⁴ between⁵ them⁶ to interconnect all the things.
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://fed.brid.gy/r/https://tantek.com/2023/113/t3/",
"content": {
"html": "<a href=\"https://hachyderm.io/@maegul\">@maegul@hachyderm.io</a> <a href=\"https://octodon.social/@torb\">@torb@octodon.social</a> <a href=\"https://indieweb.social/tags/BlueSky\">#<span class=\"p-category\">BlueSky</span></a> is a fascinating experiment to watch, and if there\u2019s one thing we\u2019ve learned from all the work on decentralized/federated social web systems over the past 13+ years (certainly since the first Federated Social Web Summit\u00b9), there\u2019s LOTS of room for and benefits to many folks working on solving many hard problems in parallel, even if with totally different approaches, which can learn from each other.<br /><br />We learned this lesson in the <a href=\"https://indieweb.social/tags/W3C\">#<span class=\"p-category\">W3C</span></a> Social Web Working Group\u00b2.<br /><br />Also a key reason the <a href=\"https://indieweb.social/tags/IndieWeb\">#<span class=\"p-category\">IndieWeb</span></a> community adopted a core principle of Plurality\u00b3.<br /><br />I have a lot of sympathy for \"so many non-techies bounce off Mastodon because it\u2019s just too technically difficult for them\", it\u2019s one of the reasons I send most folks directly to <a href=\"https://micro.blog/\">https://micro.blog/</a> \u2014 it supports following / <a href=\"https://indieweb.social/tags/federating\">#<span class=\"p-category\">federating</span></a> with <a href=\"https://indieweb.social/tags/Mastodon\">#<span class=\"p-category\">Mastodon</span></a>, and it supports core IndieWeb W3C standards like Webmention and Micropub.<br /><br />Regarding what portability requires, I for one disagree that account or post portability needs \"signed data repositories and DIDs\". I believe that cooperative server-to-server portability can be achieved without it, and frankly, if you\u2018re wanting to design for uncooperative servers, what expectation can you have that they\u2019ll support any standards or interop whatsoever?<br /><br />Beyond Mastodon-to-Mastodon account migration, we already have Mastodon-to-BridgyFed (IndieWeb) and Mastodon - to - <a href=\"http://Micro.blog\">Micro.blog</a>, and I expect we\u2019ll see that grow to include all directions of all combinations thereof.<br /><br />I am also optimistic that the \u201cfediverse\u201d will continue evolving various solutions that put users first in different ways, because there are users with different needs. <br /><br />There\u2019s certainly a current <a href=\"https://indieweb.social/tags/fediverse\">#<span class=\"p-category\">fediverse</span></a> hierarchy that puts a lot of power (and burden of responsibility) in the hands of \u201dserver/instance\u201d admins \u2014 \u201cfeudalverse\u201d was a running joke for a while, reflecting a <a href=\"https://indieweb.social/tags/federation\">#<span class=\"p-category\">federation</span></a> of instance admin feudal lords and their user serfs. <br /><br />Ironically, the more that account+posts migration/portability is supported, the more incentive there will be for harmonious and respectful relationships between instance admins and users, so I only see this situation improving in the future.<br /><br />Long reply summarized: I think the folks innovating at BlueSky are charting interesting waters, the Mastodon development community continues show through improvements that they prioritize users and their identity & data ownership, and the IndieWeb community continues to support & play with those and many other solutions, building bridges\u2074 between\u2075 them\u2076 to interconnect all the things.<br /><br />Glossary<br /><br />BridgyFed<br />\u00a0<a href=\"https://fed.brid.gy/\">https://fed.brid.gy/</a><br />Micropub<br />\u00a0<a href=\"https://indieweb.org/Micropub\">https://indieweb.org/Micropub</a><br />Webmention<br />\u00a0<a href=\"https://indieweb.org/Webmention\">https://indieweb.org/Webmention</a><br /><br />References<br /><br />\u00b9 <a href=\"https://indieweb.org/Federated_Social_Web_Summit#Portland_2010\">https://indieweb.org/Federated_Social_Web_Summit#Portland_2010</a><br />\u00b2 <a href=\"https://tantek.com/2023/051/t1/five-years-ago-w3c-social-web\">https://tantek.com/2023/051/t1/five-years-ago-w3c-social-web</a><br />\u00b3 <a href=\"https://indieweb.org/plurality\">https://indieweb.org/plurality</a><br />\u2074 <a href=\"https://brid.gy/\">https://brid.gy/</a><br />\u2075 <a href=\"https://fed.brid.gy/\">https://fed.brid.gy/</a><br />\u2076 <a href=\"https://github.com/snarfed/bridgy-fed/issues/381\">https://github.com/snarfed/bridgy-fed/issues/381</a>",
"text": "@maegul@hachyderm.io @torb@octodon.social #BlueSky is a fascinating experiment to watch, and if there\u2019s one thing we\u2019ve learned from all the work on decentralized/federated social web systems over the past 13+ years (certainly since the first Federated Social Web Summit\u00b9), there\u2019s LOTS of room for and benefits to many folks working on solving many hard problems in parallel, even if with totally different approaches, which can learn from each other.\n\nWe learned this lesson in the #W3C Social Web Working Group\u00b2.\n\nAlso a key reason the #IndieWeb community adopted a core principle of Plurality\u00b3.\n\nI have a lot of sympathy for \"so many non-techies bounce off Mastodon because it\u2019s just too technically difficult for them\", it\u2019s one of the reasons I send most folks directly to https://micro.blog/ \u2014 it supports following / #federating with #Mastodon, and it supports core IndieWeb W3C standards like Webmention and Micropub.\n\nRegarding what portability requires, I for one disagree that account or post portability needs \"signed data repositories and DIDs\". I believe that cooperative server-to-server portability can be achieved without it, and frankly, if you\u2018re wanting to design for uncooperative servers, what expectation can you have that they\u2019ll support any standards or interop whatsoever?\n\nBeyond Mastodon-to-Mastodon account migration, we already have Mastodon-to-BridgyFed (IndieWeb) and Mastodon - to - Micro.blog, and I expect we\u2019ll see that grow to include all directions of all combinations thereof.\n\nI am also optimistic that the \u201cfediverse\u201d will continue evolving various solutions that put users first in different ways, because there are users with different needs. \n\nThere\u2019s certainly a current #fediverse hierarchy that puts a lot of power (and burden of responsibility) in the hands of \u201dserver/instance\u201d admins \u2014 \u201cfeudalverse\u201d was a running joke for a while, reflecting a #federation of instance admin feudal lords and their user serfs. \n\nIronically, the more that account+posts migration/portability is supported, the more incentive there will be for harmonious and respectful relationships between instance admins and users, so I only see this situation improving in the future.\n\nLong reply summarized: I think the folks innovating at BlueSky are charting interesting waters, the Mastodon development community continues show through improvements that they prioritize users and their identity & data ownership, and the IndieWeb community continues to support & play with those and many other solutions, building bridges\u2074 between\u2075 them\u2076 to interconnect all the things.\n\nGlossary\n\nBridgyFed\n\u00a0https://fed.brid.gy/\nMicropub\n\u00a0https://indieweb.org/Micropub\nWebmention\n\u00a0https://indieweb.org/Webmention\n\nReferences\n\n\u00b9 https://indieweb.org/Federated_Social_Web_Summit#Portland_2010\n\u00b2 https://tantek.com/2023/051/t1/five-years-ago-w3c-social-web\n\u00b3 https://indieweb.org/plurality\n\u2074 https://brid.gy/\n\u2075 https://fed.brid.gy/\n\u2076 https://github.com/snarfed/bridgy-fed/issues/381"
},
"published": "2023-04-23T23:43:00+00:00",
"post-type": "note",
"_id": "36745231",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "@spreadmastodon",
"url": "https://mastodon.social/@spreadmastodon",
"photo": null
},
"url": "https://mastodon.social/@spreadmastodon/110249767459591081",
"content": {
"html": "<p><span class=\"h-card\"><a class=\"u-url\" href=\"https://fed.brid.gy/r/https://tantek.com/\">@<span>tantek.com</span></a></span> The <a href=\"https://mastodon.social/tags/Indieweb\">#<span>Indieweb</span></a>, <a href=\"https://mastodon.social/tags/Openweb\">#<span>Openweb</span></a> and <a href=\"https://mastodon.social/tags/SpreadMastodon\">#<span>SpreadMastodon</span></a> and the <a href=\"https://mastodon.social/tags/Fediverse\">#<span>Fediverse</span></a> efforts are all very clearly cousins in one big movement!</p>",
"text": "@tantek.com The #Indieweb, #Openweb and #SpreadMastodon and the #Fediverse efforts are all very clearly cousins in one big movement!"
},
"published": "2023-04-23T19:25:45+00:00",
"post-type": "note",
"_id": "36741431",
"_source": "7235",
"_is_read": false
}
So, I use Netlify’s webmention integration to send webmentions. It took ages to get just right, but it looks like it pings WordPress websites’ xmlrpc.php rather than a webmention endpoint. Makes sense, as xmlrpc.php will always exist, except there’s less chance your webmention will actually appear 🤷♂️
{
"type": "entry",
"author": {
"name": "@leonp",
"url": "https://fosstodon.org/@leonp",
"photo": null
},
"url": "https://fosstodon.org/@leonp/110247479458832594",
"content": {
"html": "<p>So, I use Netlify\u2019s webmention integration to send webmentions. It took ages to get just right, but it looks like it pings WordPress websites\u2019 xmlrpc.php rather than a webmention endpoint. Makes sense, as xmlrpc.php will always exist, except there\u2019s less chance your webmention will actually appear \ud83e\udd37\u200d\u2642\ufe0f</p><p> <br /><br /> \ud83c\udff7 <a href=\"https://fosstodon.org/tags/indieweb\">#<span>indieweb</span></a>,netlify,webmention<br /><a href=\"https://www.thisdaysportion.com/notes/more-webmention-woes\"><span>https://www.</span><span>thisdaysportion.com/notes/more</span><span>-webmention-woes</span></a></p>",
"text": "So, I use Netlify\u2019s webmention integration to send webmentions. It took ages to get just right, but it looks like it pings WordPress websites\u2019 xmlrpc.php rather than a webmention endpoint. Makes sense, as xmlrpc.php will always exist, except there\u2019s less chance your webmention will actually appear \ud83e\udd37\u200d\u2642\ufe0f \n\n \ud83c\udff7 #indieweb,netlify,webmention\nhttps://www.thisdaysportion.com/notes/more-webmention-woes"
},
"published": "2023-04-23T09:43:53+00:00",
"post-type": "note",
"_id": "36733215",
"_source": "7235",
"_is_read": false
}
One of the pretty neat innovations from #Mastodon has been actual, functional, and fairly reliable (from all accounts I’ve seen) distributed system account migration, with the notable exception of post migration, which has additional challenges worth exploring.
To be clear, as far as I know, no other blogging (or chat) software, system, or even protocol comes close to achieving the level of functionality described in Mastodon’s documentation:
In short, moving: * all your profile information * moving all your followers & followings, transparently * redirecting your old account to your new one
More at that link. From the docs, it’s clear that quite a bit of thought & consideration went into the design & implementation.
Once I had setup #BridgyFed to #federate posts from my own site¹, I myself made use of the this Mastodon feature to migrate from my try-it-out @t@xoxo.zone account to my #IndieWeb@tantek.com (move destination handled by BridgyFed).
For me the migration experience was 100%, because I had not posted anything @t@xoxo.zone.
The challenge of post migration is not unique to Mastodon, though I believe it goes beyond “simple” export & import support, which is still a good place to start.
Mastodon has two forms of posts “export” currently: * RSS feeds, which will get you some number of recent posts, by adding ".rss" to the end of any Mastodon profile URL, e.g. https://indieweb.social/@tchambers.rss * Activity Streams 2.0 JSON, per https://docs.joinmastodon.org/user/moving/#export (note: it currently says “ActivityPub JSON format”, but there is no such thing, #ActivityPub uses the #ActivityStreams 2.0 JSON format and I’ve filed a PR² to fix this in the docs)
Lots of software & services import RSS, e.g. #WordPress.
As far as I know, nothing (not even Mastodon itself) actually supports importing Activity Streams 2.0.
There is a more complete format (with specification!) for exporting & importing blog content:
Blog Archive Format has the very nice features of: * portable HTML feed (h-feed) and JSON Feed * photos and other media * locally browsable post archive
Naturally, https://micro.blog/ supports both exporting & importing Blog Archive Format.
There’s an interesting opportunity here for an open source converter * from Activity Streams 2.0 * to Blog Archive Format
Such a library would make an excellent drop-in addition to any #ActivityPub implementation, allowing both export of posts, and also a browsable archive format, so you could visually double check when importing to another service that these were the old posts you were looking for.
This would be a good first step, using an open standard, towards Mastodon itself supporting post migration³.
Ideally, similar to account migration, the old posts server should also at least: * redirect old permalinks to the new permalinks * redirect any replies being delivered by ActivityPub to the new location * provide #Webmention discovery forwarding from the old URLs to the new URLs (e.g. using HTTP LINK headers) for some amount of time.
Want to add support for Blog Archive Format or got questions or feedback?
{
"type": "entry",
"published": "2023-04-22 17:40-0700",
"url": "http://tantek.com/2023/112/t2/account-migration-post-blog-archive-format",
"category": [
"Mastodon",
"BridgyFed",
"federate",
"IndieWeb",
"ActivityPub",
"ActivityStreams",
"WordPress",
"Webmention",
"100DaysOfIndieWeb",
"100Days"
],
"content": {
"text": "One of the pretty neat innovations from #Mastodon has been actual, functional, and fairly reliable (from all accounts I\u2019ve seen) distributed system account migration, with the notable exception of post migration, which has additional challenges worth exploring.\n\nTo be clear, as far as I know, no other blogging (or chat) software, system, or even protocol comes close to achieving the level of functionality described in Mastodon\u2019s documentation:\n\nhttps://docs.joinmastodon.org/user/moving/#migration\n\nIn short, moving:\n* all your profile information\n* moving all your followers & followings, transparently \n* redirecting your old account to your new one\n\nMore at that link. From the docs, it\u2019s clear that quite a bit of thought & consideration went into the design & implementation.\n\nOnce I had setup #BridgyFed to #federate posts from my own site\u00b9, I myself made use of the this Mastodon feature to migrate from my try-it-out @t@xoxo.zone account to my #IndieWeb @tantek.com (move destination handled by BridgyFed).\n\nFor me the migration experience was 100%, because I had not posted anything @t@xoxo.zone.\n\nThe challenge of post migration is not unique to Mastodon, though I believe it goes beyond \u201csimple\u201d export & import support, which is still a good place to start.\n\nMastodon has two forms of posts \u201cexport\u201d currently:\n* RSS feeds, which will get you some number of recent posts, by adding \".rss\" to the end of any Mastodon profile URL, e.g. https://indieweb.social/@tchambers.rss\n* Activity Streams 2.0 JSON, per https://docs.joinmastodon.org/user/moving/#export (note: it currently says \u201cActivityPub JSON format\u201d, but there is no such thing, #ActivityPub uses the #ActivityStreams 2.0 JSON format and I\u2019ve filed a PR\u00b2 to fix this in the docs)\n\nLots of software & services import RSS, e.g. #WordPress.\n\nAs far as I know, nothing (not even Mastodon itself) actually supports importing Activity Streams 2.0.\n\nThere is a more complete format (with specification!) for exporting & importing blog content:\n\nBlog Archive Format (.bar), first specified here with example file:\n* https://www.manton.org/2017/11/24/blog-archive-format.html\nMore details and another example file:\n* https://www.manton.org/2021/12/27/importing-blog-archive.html\n\nBlog Archive Format has the very nice features of:\n* portable HTML feed (h-feed) and JSON Feed\n* photos and other media\n* locally browsable post archive\n\nNaturally, https://micro.blog/ supports both exporting & importing Blog Archive Format.\n\nThere\u2019s an interesting opportunity here for an open source converter \n* from Activity Streams 2.0 \n* to Blog Archive Format\n\nSuch a library would make an excellent drop-in addition to any #ActivityPub implementation, allowing both export of posts, and also a browsable archive format, so you could visually double check when importing to another service that these were the old posts you were looking for.\n\nThis would be a good first step, using an open standard, towards Mastodon itself supporting post migration\u00b3.\n\nIdeally, similar to account migration, the old posts server should also at least:\n* redirect old permalinks to the new permalinks\n* redirect any replies being delivered by ActivityPub to the new location\n* provide #Webmention discovery forwarding from the old URLs to the new URLs (e.g. using HTTP LINK headers)\nfor some amount of time.\n\nWant to add support for Blog Archive Format or got questions or feedback?\n\nJoin in the development conversations: https://chat.indieweb.org/dev\n\n\nThis is day 39 of #100DaysOfIndieWeb. #100Days\n\n\u2190 Day 38: https://tantek.com/2023/110/t2/beyond-mastodon-indieweb-own-domain\n\u2192 \ud83d\udd2e\n\n\nGlossary\n\naccount migration\n\u00a0https://indieweb.org/account_migration\nblog archive format\n\u00a0https://indieweb.org/blog_archive_format\nh-feed\n\u00a0https://microformats.org/wiki/h-feed\nJSON Feed\n\u00a0https://www.jsonfeed.org/\npost migration\n\u00a0https://indieweb.org/post_migration\nWebmention\n\u00a0https://indieweb.org/Webmention\n\nReferences\n\n\u00b9 https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb\n\u00b2 https://github.com/mastodon/documentation/pull/1202\n\u00b3 https://github.com/mastodon/mastodon/issues/12423",
"html": "One of the pretty neat innovations from #<span class=\"p-category\">Mastodon</span> has been actual, functional, and fairly reliable (from all accounts I\u2019ve seen) distributed system account migration, with the notable exception of post migration, which has additional challenges worth exploring.<br /><br />To be clear, as far as I know, no other blogging (or chat) software, system, or even protocol comes close to achieving the level of functionality described in Mastodon\u2019s documentation:<br /><br /><a href=\"https://docs.joinmastodon.org/user/moving/#migration\">https://docs.joinmastodon.org/user/moving/#migration</a><br /><br />In short, moving:<br />* all your profile information<br />* moving all your followers & followings, transparently <br />* redirecting your old account to your new one<br /><br />More at that link. From the docs, it\u2019s clear that quite a bit of thought & consideration went into the design & implementation.<br /><br />Once I had setup #<span class=\"p-category\">BridgyFed</span> to #<span class=\"p-category\">federate</span> posts from my own site<a href=\"http://tantek.com/#t5QV2_note-1\">\u00b9</a>, I myself made use of the this Mastodon feature to migrate from my try-it-out <a href=\"https://xoxo.zone/@t\">@t@xoxo.zone</a> account to my #<span class=\"p-category\">IndieWeb</span> <a href=\"https://tantek.com\">@tantek.com</a> (move destination handled by BridgyFed).<br /><br />For me the migration experience was 100%, because I had not posted anything <a href=\"https://xoxo.zone/@t\">@t@xoxo.zone</a>.<br /><br />The challenge of post migration is not unique to Mastodon, though I believe it goes beyond \u201csimple\u201d export & import support, which is still a good place to start.<br /><br />Mastodon has two forms of posts \u201cexport\u201d currently:<br />* RSS feeds, which will get you some number of recent posts, by adding \".rss\" to the end of any Mastodon profile URL, e.g. <a href=\"https://indieweb.social/@tchambers.rss\">https://indieweb.social/@tchambers.rss</a><br />* Activity Streams 2.0 JSON, per <a href=\"https://docs.joinmastodon.org/user/moving/#export\">https://docs.joinmastodon.org/user/moving/#export</a> (note: it currently says \u201cActivityPub JSON format\u201d, but there is no such thing, #<span class=\"p-category\">ActivityPub</span> uses the #<span class=\"p-category\">ActivityStreams</span> 2.0 JSON format and I\u2019ve filed a PR<a href=\"http://tantek.com/#t5QV2_note-2\">\u00b2</a> to fix this in the docs)<br /><br />Lots of software & services import RSS, e.g. #<span class=\"p-category\">WordPress</span>.<br /><br />As far as I know, nothing (not even Mastodon itself) actually supports importing Activity Streams 2.0.<br /><br />There is a more complete format (with specification!) for exporting & importing blog content:<br /><br />Blog Archive Format (.bar), first specified here with example file:<br />* <a href=\"https://www.manton.org/2017/11/24/blog-archive-format.html\">https://www.manton.org/2017/11/24/blog-archive-format.html</a><br />More details and another example file:<br />* <a href=\"https://www.manton.org/2021/12/27/importing-blog-archive.html\">https://www.manton.org/2021/12/27/importing-blog-archive.html</a><br /><br />Blog Archive Format has the very nice features of:<br />* portable HTML feed (h-feed) and JSON Feed<br />* photos and other media<br />* locally browsable post archive<br /><br />Naturally, <a href=\"https://micro.blog/\">https://micro.blog/</a> supports both exporting & importing Blog Archive Format.<br /><br />There\u2019s an interesting opportunity here for an open source converter <br />* from Activity Streams 2.0 <br />* to Blog Archive Format<br /><br />Such a library would make an excellent drop-in addition to any #<span class=\"p-category\">ActivityPub</span> implementation, allowing both export of posts, and also a browsable archive format, so you could visually double check when importing to another service that these were the old posts you were looking for.<br /><br />This would be a good first step, using an open standard, towards Mastodon itself supporting post migration<a href=\"http://tantek.com/#t5QV2_note-3\">\u00b3</a>.<br /><br />Ideally, similar to account migration, the old posts server should also at least:<br />* redirect old permalinks to the new permalinks<br />* redirect any replies being delivered by ActivityPub to the new location<br />* provide #<span class=\"p-category\">Webmention</span> discovery forwarding from the old URLs to the new URLs (e.g. using HTTP LINK headers)<br />for some amount of time.<br /><br />Want to add support for Blog Archive Format or got questions or feedback?<br /><br />Join in the development conversations: <a href=\"https://chat.indieweb.org/dev\">https://chat.indieweb.org/dev</a><br /><br /><br />This is day 39 of #<span class=\"p-category\">100DaysOfIndieWeb</span>. #<span class=\"p-category\">100Days</span><br /><br />\u2190 Day 38: <a href=\"https://tantek.com/2023/110/t2/beyond-mastodon-indieweb-own-domain\">https://tantek.com/2023/110/t2/beyond-mastodon-indieweb-own-domain</a><br />\u2192 \ud83d\udd2e<br /><br /><br />Glossary<br /><br />account migration<br />\u00a0<a href=\"https://indieweb.org/account_migration\">https://indieweb.org/account_migration</a><br />blog archive format<br />\u00a0<a href=\"https://indieweb.org/blog_archive_format\">https://indieweb.org/blog_archive_format</a><br />h-feed<br />\u00a0<a href=\"https://microformats.org/wiki/h-feed\">https://microformats.org/wiki/h-feed</a><br />JSON Feed<br />\u00a0<a href=\"https://www.jsonfeed.org/\">https://www.jsonfeed.org/</a><br />post migration<br />\u00a0<a href=\"https://indieweb.org/post_migration\">https://indieweb.org/post_migration</a><br />Webmention<br />\u00a0<a href=\"https://indieweb.org/Webmention\">https://indieweb.org/Webmention</a><br /><br />References<br /><br /><a href=\"http://tantek.com/#t5QV2_ref-1\">\u00b9</a> <a href=\"https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb\">https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb</a><br /><a href=\"http://tantek.com/#t5QV2_ref-2\">\u00b2</a> <a href=\"https://github.com/mastodon/documentation/pull/1202\">https://github.com/mastodon/documentation/pull/1202</a><br /><a href=\"http://tantek.com/#t5QV2_ref-3\">\u00b3</a> <a href=\"https://github.com/mastodon/mastodon/issues/12423\">https://github.com/mastodon/mastodon/issues/12423</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": "36729126",
"_source": "1",
"_is_read": false
}
In short: using my own #IndieWeb blog and blogging software, which has no length limit.
A bit longer:
I make my posts by writing them in @barebones.com’s excellent BBEdit (@bbedit@mastodon.social) text editor, scp them to my blog, which does all sorts of automatic linking (including #hashtags), embedding, generating of archives, streams, feeds, sequential navigation, etc.
{
"type": "entry",
"published": "2023-04-22 16:18-0700",
"url": "http://tantek.com/2023/112/t1/",
"category": [
"IndieWeb",
"hashtags",
"BridgyFed",
"federate",
"fediverse",
"Mastodon",
"ActivityPub"
],
"in-reply-to": [
"https://union.place/@Frankc1450/110228788126722907"
],
"content": {
"text": "Thanks @Frankc1450@union.place!\n\nIn short: using my own #IndieWeb blog and blogging software, which has no length limit.\n\nA bit longer:\n\nI make my posts by writing them in @barebones.com\u2019s excellent BBEdit (@bbedit@mastodon.social) text editor, scp them to my blog, which does all sorts of automatic linking (including #hashtags), embedding, generating of archives, streams, feeds, sequential navigation, etc.\n\nI use #BridgyFed to #federate my posts to #fediverse followers on #Mastodon and other #ActivityPub supporting services. More details on that here: https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb",
"html": "Thanks <a href=\"https://union.place/@Frankc1450\">@Frankc1450@union.place</a>!<br /><br />In short: using my own #<span class=\"p-category\">IndieWeb</span> blog and blogging software, which has no length limit.<br /><br />A bit longer:<br /><br />I make my posts by writing them in <a href=\"https://barebones.com\">@barebones.com</a>\u2019s excellent BBEdit (<a href=\"https://mastodon.social/@bbedit\">@bbedit@mastodon.social</a>) text editor, scp them to my blog, which does all sorts of automatic linking (including #<span class=\"p-category\">hashtags</span>), embedding, generating of archives, streams, feeds, sequential navigation, etc.<br /><br />I use #<span class=\"p-category\">BridgyFed</span> to #<span class=\"p-category\">federate</span> my posts to #<span class=\"p-category\">fediverse</span> followers on #<span class=\"p-category\">Mastodon</span> and other #<span class=\"p-category\">ActivityPub</span> supporting services. More details on that here: <a href=\"https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb\">https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "http://tantek.com/",
"photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "reply",
"refs": {
"https://union.place/@Frankc1450/110228788126722907": {
"type": "entry",
"url": "https://union.place/@Frankc1450/110228788126722907",
"name": "union.place user Frankc1450\u2019s post",
"post-type": "article"
}
},
"_id": "36729127",
"_source": "1",
"_is_read": false
}
In short: using my own #IndieWeb blog and blogging software, which has no length limit.
A bit longer:
I make my posts by writing them in @barebones.com’s excellent BBEdit (@bbedit@mastodon.social) text editor, scp them to my blog, which does all sorts of automatic linking (including #hashtags), embedding, generating of archives, streams, feeds, sequential navigation, etc.
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://fed.brid.gy/r/https://tantek.com/2023/112/t1/",
"content": {
"html": "Thanks <a href=\"https://union.place/@Frankc1450\">@Frankc1450@union.place</a>!<br /><br />In short: using my own <a href=\"https://indieweb.social/tags/IndieWeb\">#<span class=\"p-category\">IndieWeb</span></a> blog and blogging software, which has no length limit.<br /><br />A bit longer:<br /><br />I make my posts by writing them in <a href=\"https://barebones.com\">@barebones.com</a>\u2019s excellent BBEdit (<a href=\"https://mastodon.social/@bbedit\">@bbedit@mastodon.social</a>) text editor, scp them to my blog, which does all sorts of automatic linking (including <a href=\"https://indieweb.social/tags/hashtags\">#<span class=\"p-category\">hashtags</span></a>), embedding, generating of archives, streams, feeds, sequential navigation, etc.<br /><br />I use <a href=\"https://indieweb.social/tags/BridgyFed\">#<span class=\"p-category\">BridgyFed</span></a> to <a href=\"https://indieweb.social/tags/federate\">#<span class=\"p-category\">federate</span></a> my posts to <a href=\"https://indieweb.social/tags/fediverse\">#<span class=\"p-category\">fediverse</span></a> followers on <a href=\"https://indieweb.social/tags/Mastodon\">#<span class=\"p-category\">Mastodon</span></a> and other <a href=\"https://indieweb.social/tags/ActivityPub\">#<span class=\"p-category\">ActivityPub</span></a> supporting services. More details on that here: <a href=\"https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb\">https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb</a>",
"text": "Thanks @Frankc1450@union.place!\n\nIn short: using my own #IndieWeb blog and blogging software, which has no length limit.\n\nA bit longer:\n\nI make my posts by writing them in @barebones.com\u2019s excellent BBEdit (@bbedit@mastodon.social) text editor, scp them to my blog, which does all sorts of automatic linking (including #hashtags), embedding, generating of archives, streams, feeds, sequential navigation, etc.\n\nI use #BridgyFed to #federate my posts to #fediverse followers on #Mastodon and other #ActivityPub supporting services. More details on that here: https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb"
},
"published": "2023-04-22T23:18:00+00:00",
"post-type": "note",
"_id": "36728385",
"_source": "7235",
"_is_read": false
}
One of the pretty neat innovations from #Mastodon has been actual, functional, and fairly reliable (from all accounts I’ve seen) distributed system account migration, with the notable exception of post migration, which has additional challenges worth exploring.
To be clear, as far as I know, no other blogging (or chat) software, system, or even protocol comes close to achieving the level of functionality described in Mastodon’s documentation:
In short, moving: * all your profile information * moving all your followers & followings, transparently * redirecting your old account to your new one
More at that link. From the docs, it’s clear that quite a bit of thought & consideration went into the design & implementation.
Once I had setup #BridgyFed to #federate posts from my own site¹, I myself made use of the this Mastodon feature to migrate from my try-it-out @t@xoxo.zone account to my #IndieWeb@tantek.com (move destination handled by BridgyFed).
For me the migration experience was 100%, because I had not posted anything @t@xoxo.zone.
The challenge of post migration is not unique to Mastodon, though I believe it goes beyond “simple” export & import support, which is still a good place to start.
Mastodon has two forms of posts “export” currently: * RSS feeds, which will get you some number of recent posts, by adding ".rss" to the end of any Mastodon profile URL, e.g. https://indieweb.social/@tchambers.rss * Activity Streams 2.0 JSON, per https://docs.joinmastodon.org/user/moving/#export (note: it currently says “ActivityPub JSON format”, but there is no such thing, #ActivityPub uses the #ActivityStreams 2.0 JSON format and I’ve filed a PR² to fix this in the docs)
Lots of software & services import RSS, e.g. #WordPress.
As far as I know, nothing (not even Mastodon itself) actually supports importing Activity Streams 2.0.
There is a more complete format (with specification!) for exporting & importing blog content:
Blog Archive Format has the very nice features of: * portable HTML feed (h-feed) and JSON Feed * photos and other media * locally browsable post archive
Naturally, https://micro.blog/ supports both exporting & importing Blog Archive Format.
There’s an interesting opportunity here for an open source converter * from Activity Streams 2.0 * to Blog Archive Format
Such a library would make an excellent drop-in addition to any #ActivityPub implementation, allowing both export of posts, and also a browsable archive format, so you could visually double check when importing to another service that these were the old posts you were looking for.
This would be a good first step, using an open standard, towards Mastodon itself supporting post migration³.
Ideally, similar to account migration, the old posts server should also at least: * redirect old permalinks to the new permalinks * redirect any replies being delivered by ActivityPub to the new location * provide #Webmention discovery forwarding from the old URLs to the new URLs (e.g. using HTTP LINK headers) for some amount of time.
Want to add support for Blog Archive Format or got questions or feedback?
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://fed.brid.gy/r/https://tantek.com/2023/112/t2/account-migration-post-blog-archive-format",
"content": {
"html": "One of the pretty neat innovations from <a href=\"https://indieweb.social/tags/Mastodon\">#<span class=\"p-category\">Mastodon</span></a> has been actual, functional, and fairly reliable (from all accounts I\u2019ve seen) distributed system account migration, with the notable exception of post migration, which has additional challenges worth exploring.<br /><br />To be clear, as far as I know, no other blogging (or chat) software, system, or even protocol comes close to achieving the level of functionality described in Mastodon\u2019s documentation:<br /><br /><a href=\"https://docs.joinmastodon.org/user/moving/#migration\">https://docs.joinmastodon.org/user/moving/#migration</a><br /><br />In short, moving:<br />* all your profile information<br />* moving all your followers & followings, transparently <br />* redirecting your old account to your new one<br /><br />More at that link. From the docs, it\u2019s clear that quite a bit of thought & consideration went into the design & implementation.<br /><br />Once I had setup <a href=\"https://indieweb.social/tags/BridgyFed\">#<span class=\"p-category\">BridgyFed</span></a> to <a href=\"https://indieweb.social/tags/federate\">#<span class=\"p-category\">federate</span></a> posts from my own site\u00b9, I myself made use of the this Mastodon feature to migrate from my try-it-out <a href=\"https://xoxo.zone/@t\">@t@xoxo.zone</a> account to my <a href=\"https://indieweb.social/tags/IndieWeb\">#<span class=\"p-category\">IndieWeb</span></a> <a href=\"https://tantek.com\">@tantek.com</a> (move destination handled by BridgyFed).<br /><br />For me the migration experience was 100%, because I had not posted anything <a href=\"https://xoxo.zone/@t\">@t@xoxo.zone</a>.<br /><br />The challenge of post migration is not unique to Mastodon, though I believe it goes beyond \u201csimple\u201d export & import support, which is still a good place to start.<br /><br />Mastodon has two forms of posts \u201cexport\u201d currently:<br />* RSS feeds, which will get you some number of recent posts, by adding \".rss\" to the end of any Mastodon profile URL, e.g. <a href=\"https://indieweb.social/@tchambers.rss\">https://indieweb.social/@tchambers.rss</a><br />* Activity Streams 2.0 JSON, per <a href=\"https://docs.joinmastodon.org/user/moving/#export\">https://docs.joinmastodon.org/user/moving/#export</a> (note: it currently says \u201cActivityPub JSON format\u201d, but there is no such thing, <a href=\"https://indieweb.social/tags/ActivityPub\">#<span class=\"p-category\">ActivityPub</span></a> uses the <a href=\"https://indieweb.social/tags/ActivityStreams\">#<span class=\"p-category\">ActivityStreams</span></a> 2.0 JSON format and I\u2019ve filed a PR\u00b2 to fix this in the docs)<br /><br />Lots of software & services import RSS, e.g. <a href=\"https://indieweb.social/tags/WordPress\">#<span class=\"p-category\">WordPress</span></a>.<br /><br />As far as I know, nothing (not even Mastodon itself) actually supports importing Activity Streams 2.0.<br /><br />There is a more complete format (with specification!) for exporting & importing blog content:<br /><br />Blog Archive Format (.bar), first specified here with example file:<br />* <a href=\"https://www.manton.org/2017/11/24/blog-archive-format.html\">https://www.manton.org/2017/11/24/blog-archive-format.html</a><br />More details and another example file:<br />* <a href=\"https://www.manton.org/2021/12/27/importing-blog-archive.html\">https://www.manton.org/2021/12/27/importing-blog-archive.html</a><br /><br />Blog Archive Format has the very nice features of:<br />* portable HTML feed (h-feed) and JSON Feed<br />* photos and other media<br />* locally browsable post archive<br /><br />Naturally, <a href=\"https://micro.blog/\">https://micro.blog/</a> supports both exporting & importing Blog Archive Format.<br /><br />There\u2019s an interesting opportunity here for an open source converter <br />* from Activity Streams 2.0 <br />* to Blog Archive Format<br /><br />Such a library would make an excellent drop-in addition to any <a href=\"https://indieweb.social/tags/ActivityPub\">#<span class=\"p-category\">ActivityPub</span></a> implementation, allowing both export of posts, and also a browsable archive format, so you could visually double check when importing to another service that these were the old posts you were looking for.<br /><br />This would be a good first step, using an open standard, towards Mastodon itself supporting post migration\u00b3.<br /><br />Ideally, similar to account migration, the old posts server should also at least:<br />* redirect old permalinks to the new permalinks<br />* redirect any replies being delivered by ActivityPub to the new location<br />* provide <a href=\"https://indieweb.social/tags/Webmention\">#<span class=\"p-category\">Webmention</span></a> discovery forwarding from the old URLs to the new URLs (e.g. using HTTP LINK headers)<br />for some amount of time.<br /><br />Want to add support for Blog Archive Format or got questions or feedback?<br /><br />Join in the development conversations: <a href=\"https://chat.indieweb.org/dev\">https://chat.indieweb.org/dev</a><br /><br /><br />This is day 39 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 38: <a href=\"https://tantek.com/2023/110/t2/beyond-mastodon-indieweb-own-domain\">https://tantek.com/2023/110/t2/beyond-mastodon-indieweb-own-domain</a><br />\u2192 \ud83d\udd2e<br /><br /><br />Glossary<br /><br />account migration<br />\u00a0<a href=\"https://indieweb.org/account_migration\">https://indieweb.org/account_migration</a><br />blog archive format<br />\u00a0<a href=\"https://indieweb.org/blog_archive_format\">https://indieweb.org/blog_archive_format</a><br />h-feed<br />\u00a0<a href=\"https://microformats.org/wiki/h-feed\">https://microformats.org/wiki/h-feed</a><br />JSON Feed<br />\u00a0<a href=\"https://www.jsonfeed.org/\">https://www.jsonfeed.org/</a><br />post migration<br />\u00a0<a href=\"https://indieweb.org/post_migration\">https://indieweb.org/post_migration</a><br />Webmention<br />\u00a0<a href=\"https://indieweb.org/Webmention\">https://indieweb.org/Webmention</a><br /><br />References<br /><br />\u00b9 <a href=\"https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb\">https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb</a><br />\u00b2 <a href=\"https://github.com/mastodon/documentation/pull/1202\">https://github.com/mastodon/documentation/pull/1202</a><br />\u00b3 <a href=\"https://github.com/mastodon/mastodon/issues/12423\">https://github.com/mastodon/mastodon/issues/12423</a>",
"text": "One of the pretty neat innovations from #Mastodon has been actual, functional, and fairly reliable (from all accounts I\u2019ve seen) distributed system account migration, with the notable exception of post migration, which has additional challenges worth exploring.\n\nTo be clear, as far as I know, no other blogging (or chat) software, system, or even protocol comes close to achieving the level of functionality described in Mastodon\u2019s documentation:\n\nhttps://docs.joinmastodon.org/user/moving/#migration\n\nIn short, moving:\n* all your profile information\n* moving all your followers & followings, transparently \n* redirecting your old account to your new one\n\nMore at that link. From the docs, it\u2019s clear that quite a bit of thought & consideration went into the design & implementation.\n\nOnce I had setup #BridgyFed to #federate posts from my own site\u00b9, I myself made use of the this Mastodon feature to migrate from my try-it-out @t@xoxo.zone account to my #IndieWeb @tantek.com (move destination handled by BridgyFed).\n\nFor me the migration experience was 100%, because I had not posted anything @t@xoxo.zone.\n\nThe challenge of post migration is not unique to Mastodon, though I believe it goes beyond \u201csimple\u201d export & import support, which is still a good place to start.\n\nMastodon has two forms of posts \u201cexport\u201d currently:\n* RSS feeds, which will get you some number of recent posts, by adding \".rss\" to the end of any Mastodon profile URL, e.g. https://indieweb.social/@tchambers.rss\n* Activity Streams 2.0 JSON, per https://docs.joinmastodon.org/user/moving/#export (note: it currently says \u201cActivityPub JSON format\u201d, but there is no such thing, #ActivityPub uses the #ActivityStreams 2.0 JSON format and I\u2019ve filed a PR\u00b2 to fix this in the docs)\n\nLots of software & services import RSS, e.g. #WordPress.\n\nAs far as I know, nothing (not even Mastodon itself) actually supports importing Activity Streams 2.0.\n\nThere is a more complete format (with specification!) for exporting & importing blog content:\n\nBlog Archive Format (.bar), first specified here with example file:\n* https://www.manton.org/2017/11/24/blog-archive-format.html\nMore details and another example file:\n* https://www.manton.org/2021/12/27/importing-blog-archive.html\n\nBlog Archive Format has the very nice features of:\n* portable HTML feed (h-feed) and JSON Feed\n* photos and other media\n* locally browsable post archive\n\nNaturally, https://micro.blog/ supports both exporting & importing Blog Archive Format.\n\nThere\u2019s an interesting opportunity here for an open source converter \n* from Activity Streams 2.0 \n* to Blog Archive Format\n\nSuch a library would make an excellent drop-in addition to any #ActivityPub implementation, allowing both export of posts, and also a browsable archive format, so you could visually double check when importing to another service that these were the old posts you were looking for.\n\nThis would be a good first step, using an open standard, towards Mastodon itself supporting post migration\u00b3.\n\nIdeally, similar to account migration, the old posts server should also at least:\n* redirect old permalinks to the new permalinks\n* redirect any replies being delivered by ActivityPub to the new location\n* provide #Webmention discovery forwarding from the old URLs to the new URLs (e.g. using HTTP LINK headers)\nfor some amount of time.\n\nWant to add support for Blog Archive Format or got questions or feedback?\n\nJoin in the development conversations: https://chat.indieweb.org/dev\n\n\nThis is day 39 of #100DaysOfIndieWeb. #100Days\n\n\u2190 Day 38: https://tantek.com/2023/110/t2/beyond-mastodon-indieweb-own-domain\n\u2192 \ud83d\udd2e\n\n\nGlossary\n\naccount migration\n\u00a0https://indieweb.org/account_migration\nblog archive format\n\u00a0https://indieweb.org/blog_archive_format\nh-feed\n\u00a0https://microformats.org/wiki/h-feed\nJSON Feed\n\u00a0https://www.jsonfeed.org/\npost migration\n\u00a0https://indieweb.org/post_migration\nWebmention\n\u00a0https://indieweb.org/Webmention\n\nReferences\n\n\u00b9 https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb\n\u00b2 https://github.com/mastodon/documentation/pull/1202\n\u00b3 https://github.com/mastodon/mastodon/issues/12423"
},
"published": "2023-04-23T00:40:00+00:00",
"post-type": "note",
"_id": "36727939",
"_source": "7235",
"_is_read": false
}
A #feditip to those trying other #fediverse software: Treat your new account as you would signing-up in a new #SNS.
A more detailed #feditips: 1. Let each of your account grow separately.
It is fine to follow certain groups and users. These are your ‘core’ interaction. But for the rest, keep them separate and let it grow organically.
2. Define a certain theme or topic or purpose for your new account.
Since we are in an interconnected network, you will end up having a major overlap between your first account and your succeeding accounts. Which might confuse you later (as well as your followers).
For example, I still post my new articles through my @youronlyone@c.im account, for two major reasons: Follower Badge, and #Indieweb support via #Bridgy.
3. Use this opportunity to learn how discovery, growth, and reach, works in the #MycelialNetwork (or #SocialWeb)
By letting your new account grow organically, and keeping the overlap with your first account at a minimum, you will be able to observe how discovery, growth, and reach, works in the network.
The Misskey and Calckey accounts are organically growing. I also discover new people, new content, that I haven't seen in my #Mastodon account (@youronlyone@c.im). And I asked myself, why? As I find answers to that question, I slowly adjust my interactions, and this in turn helped me discover more and reach wider.
The Mycelial Network (as I now prefer to call the Fediverse), is huge. When it started in 2008, it was small, and we all know each other. Today, I've probably only discovered and reached 0.5% of the network. It grew that fast.
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://calckey.social/notes/9dw5oldjkf",
"content": {
"html": "<p><span>A </span><a href=\"https://calckey.social/tags/feditip\">#feditip</a><span> to those trying other </span><a href=\"https://calckey.social/tags/fediverse\">#fediverse</a><span> software: Treat your new account as you would signing-up in a new </span><a href=\"https://calckey.social/tags/SNS\">#SNS</a><span>.<br /><br />A more detailed </span><a href=\"https://calckey.social/tags/feditips\">#feditips</a><span>:<br /></span><span>1. Let each of your account grow separately.</span><span><br /><br />It is fine to follow certain groups and users. These are your \u2018core\u2019 interaction. But for the rest, keep them separate and let it grow organically.<br /><br /></span><span>2. Define a certain theme or topic or purpose for your new account.</span><span><br /><br />Since we are in an interconnected network, you will end up having a major overlap between your first account and your succeeding accounts. Which might confuse you later (as well as your followers).<br /><br />For example, I still post my new articles through my </span><a class=\"u-url\" href=\"https://c.im/@youronlyone\">@youronlyone@c.im</a><span> account, for two major reasons: Follower Badge, and </span><a href=\"https://calckey.social/tags/Indieweb\">#Indieweb</a><span> support via </span><a href=\"https://calckey.social/tags/Bridgy\">#Bridgy</a><span>.<br /><br /></span><span>3. Use this opportunity to learn how discovery, growth, and reach, works in the </span><a href=\"https://calckey.social/tags/MycelialNetwork\">#MycelialNetwork</a><span> (or </span><a href=\"https://calckey.social/tags/SocialWeb\">#SocialWeb</a><span>)</span><span><br /><br />By letting your new account grow organically, and keeping the overlap with your first account at a minimum, you will be able to observe how discovery, growth, and reach, works in the network.<br /><br />I have an account for </span><a href=\"https://calckey.social/tags/Calckey\">#Calckey</a><span> at </span><a class=\"u-url\" href=\"https://calckey.social/@youronlyone@calckey.social\">@youronlyone@calckey.social</a><span><br /><br />I also have an account for </span><a href=\"https://calckey.social/tags/Misskey\">#Misskey</a><span> at </span><a class=\"u-url\" href=\"https://hashi.icu/@youronlyone\">@youronlyone@hashi.icu</a><span><br /><br />The Misskey and Calckey accounts are organically growing. I also discover new people, new content, that I haven't seen in my </span><a href=\"https://calckey.social/tags/Mastodon\">#Mastodon</a><span> account (</span><a class=\"u-url\" href=\"https://c.im/@youronlyone\">@youronlyone@c.im</a><span>). And I asked myself, why? As I find answers to that question, I slowly adjust my interactions, and this in turn helped me discover more and reach wider.<br /><br />The </span><span>Mycelial Network</span><span> (as I now prefer to call the Fediverse), is huge. When it started in 2008, it was small, and we all know each other. Today, I've probably only discovered and reached 0.5% of the network. It grew that fast.<br /><br /></span><a href=\"https://calckey.social/tags/YourOnlyOne\">#YourOnlyOne</a></p>",
"text": "A #feditip to those trying other #fediverse software: Treat your new account as you would signing-up in a new #SNS.\n\nA more detailed #feditips:\n1. Let each of your account grow separately.\n\nIt is fine to follow certain groups and users. These are your \u2018core\u2019 interaction. But for the rest, keep them separate and let it grow organically.\n\n2. Define a certain theme or topic or purpose for your new account.\n\nSince we are in an interconnected network, you will end up having a major overlap between your first account and your succeeding accounts. Which might confuse you later (as well as your followers).\n\nFor example, I still post my new articles through my @youronlyone@c.im account, for two major reasons: Follower Badge, and #Indieweb support via #Bridgy.\n\n3. Use this opportunity to learn how discovery, growth, and reach, works in the #MycelialNetwork (or #SocialWeb)\n\nBy letting your new account grow organically, and keeping the overlap with your first account at a minimum, you will be able to observe how discovery, growth, and reach, works in the network.\n\nI have an account for #Calckey at @youronlyone@calckey.social\n\nI also have an account for #Misskey at @youronlyone@hashi.icu\n\nThe Misskey and Calckey accounts are organically growing. I also discover new people, new content, that I haven't seen in my #Mastodon account (@youronlyone@c.im). And I asked myself, why? As I find answers to that question, I slowly adjust my interactions, and this in turn helped me discover more and reach wider.\n\nThe Mycelial Network (as I now prefer to call the Fediverse), is huge. When it started in 2008, it was small, and we all know each other. Today, I've probably only discovered and reached 0.5% of the network. It grew that fast.\n\n#YourOnlyOne"
},
"published": "2023-04-22T23:08:30+00:00",
"post-type": "note",
"_id": "36726859",
"_source": "7235",
"_is_read": false
}
Matt Baer blogs about the future of Write.as and WriteFreely — taking features that are currently separate products and integrating them into more of a suite:
At this point, I don’t think it makes sense for our self-hosted product to be chopped up into multiple components like our hosted tools are. Instead, I want to bring all those tools into a single application in WriteFreely.
Remark.as will also get fediverse replies. Sounds like a good direction.
{
"type": "entry",
"author": {
"name": "Manton Reece",
"url": "https://www.manton.org/",
"photo": "https://micro.blog/manton/avatar.jpg"
},
"url": "https://www.manton.org/2023/04/22/matt-baer-blogs.html",
"content": {
"html": "<p><a href=\"https://write.as/matt/product-outlook-write-as-and-writefreely?pk_campaign=rss-feed\">Matt Baer blogs about</a> the future of Write.as and WriteFreely \u2014\u00a0taking features that are currently separate products and integrating them into more of a suite:</p>\n<blockquote>\n<p>At this point, I don\u2019t think it makes sense for our self-hosted product to be chopped up into multiple components like our hosted tools are. Instead, I want to bring all those tools into a single application in WriteFreely.</p>\n</blockquote>\n<p>Remark.as will also get fediverse replies. Sounds like a good direction.</p>",
"text": "Matt Baer blogs about the future of Write.as and WriteFreely \u2014\u00a0taking features that are currently separate products and integrating them into more of a suite:\n\nAt this point, I don\u2019t think it makes sense for our self-hosted product to be chopped up into multiple components like our hosted tools are. Instead, I want to bring all those tools into a single application in WriteFreely.\n\nRemark.as will also get fediverse replies. Sounds like a good direction."
},
"published": "2023-04-22T12:34:05-05:00",
"post-type": "note",
"_id": "36721522",
"_source": "12",
"_is_read": false
}
{
"type": "entry",
"published": "2023-04-22T11:25:45-0400",
"url": "https://martymcgui.re/2023/04/22/this-week-in-the-indieweb-audio-edition--april-15th---21st-2023/",
"category": [
"podcast",
"IndieWeb",
"this-week-indieweb-podcast"
],
"audio": [
"https://media.martymcgui.re/a0/f4/50/d0/367d9155348b81d423006c428139787acd84c0fe322809378c94bc71.mp3"
],
"name": "This Week in the IndieWeb Audio Edition \u2022 April 15th - 21st, 2023",
"content": {
"text": "Unblocking your blogging, Twitter login troubles, and planning IndieWebCamp Nuremburg. It\u2019s the audio edition for This Week in the IndieWeb for April 15th - 21st, 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": "<p>Unblocking your blogging, Twitter login troubles, and planning IndieWebCamp Nuremburg. It\u2019s the audio edition for <a href=\"https://indieweb.org/this-week/2023-04-21.html\">This Week in the IndieWeb for April 15th - 21st, 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": "36719141",
"_source": "175",
"_is_read": false
}
I’d like to hear from people who have De-Googled their lives. I’ve managed to cut ties with Facebook a few years ago (no Instagram, but my wife still uses it); I cut out Twitter full time back in November if I recall correctly. Google is next.
I still use search, maps, and to a much lesser extent, Gmail. I used Google Drive but I won’t be sad about losing that since I have a local (Nextcloud) alternative. #google#indieweb
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://dartboard.social/objects/8a729f42-614f-4030-b791-606b4c57e73a",
"content": {
"html": "I\u2019d like to hear from people who have De-Googled their lives. I\u2019ve managed to cut ties with Facebook a few years ago (no Instagram, but my wife still uses it); I cut out Twitter full time back in November if I recall correctly. Google is next. <br /><br />I still use search, maps, and to a much lesser extent, Gmail. I used Google Drive but I won\u2019t be sad about losing that since I have a local (Nextcloud) alternative. <a href=\"https://dartboard.social/tag/google\">#google</a> <a href=\"https://dartboard.social/tag/indieweb\">#indieweb</a>",
"text": "I\u2019d like to hear from people who have De-Googled their lives. I\u2019ve managed to cut ties with Facebook a few years ago (no Instagram, but my wife still uses it); I cut out Twitter full time back in November if I recall correctly. Google is next. \n\nI still use search, maps, and to a much lesser extent, Gmail. I used Google Drive but I won\u2019t be sad about losing that since I have a local (Nextcloud) alternative. #google #indieweb"
},
"published": "2023-04-21T23:49:38+00:00",
"post-type": "note",
"_id": "36708431",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "@john_fisherman",
"url": "https://mastodon.social/@john_fisherman",
"photo": null
},
"url": "https://mastodon.social/@john_fisherman/110238083253799526",
"content": {
"html": "<p><span class=\"h-card\"><a class=\"u-url\" href=\"https://universeodon.com/@pixeline\">@<span>pixeline</span></a></span> <span class=\"h-card\"><a class=\"u-url\" href=\"https://social.lol/@sophie\">@<span>sophie</span></a></span> <span class=\"h-card\"><a class=\"u-url\" href=\"https://mastodon.social/@nickautomatic\">@<span>nickautomatic</span></a></span> <span class=\"h-card\"><a class=\"u-url\" href=\"https://mastodon.social/@btconf\">@<span>btconf</span></a></span> <span class=\"h-card\"><a class=\"u-url\" href=\"https://fed.brid.gy/r/https://tantek.com/\">@<span>tantek.com</span></a></span> hear, hear! </p><p>I have started linking <a href=\"https://mastodon.social/tags/btconf\">#<span>btconf</span></a> folks on my website, as promised:</p><p><a href=\"https://fredrocha.net/like-minded/#btconf-sites\"><span>https://</span><span>fredrocha.net/like-minded/#btc</span><span>onf-sites</span></a></p><p>I also laid out some thoughts on what happens once you roll your own website into the wild:</p><p><a href=\"https://fredrocha.net/2023/04/21/build-your-own-website-and-they-will-not-come/\"><span>https://</span><span>fredrocha.net/2023/04/21/build</span><span>-your-own-website-and-they-will-not-come/</span></a></p><p>If we dream together, it's doable.</p><p><a href=\"https://mastodon.social/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://mastodon.social/tags/curation\">#<span>curation</span></a> <a href=\"https://mastodon.social/tags/discoverability\">#<span>discoverability</span></a></p>",
"text": "@pixeline @sophie @nickautomatic @btconf @tantek.com hear, hear! I have started linking #btconf folks on my website, as promised:https://fredrocha.net/like-minded/#btconf-sitesI also laid out some thoughts on what happens once you roll your own website into the wild:https://fredrocha.net/2023/04/21/build-your-own-website-and-they-will-not-come/If we dream together, it's doable.#indieweb #curation #discoverability"
},
"published": "2023-04-21T17:54:19+00:00",
"post-type": "note",
"_id": "36702159",
"_source": "7235",
"_is_read": false
}
Creating your own website, own your data and display the things you’re into under your domain. When online, be a creator, not a consumer.
I’m all in for this mantra, but this realization stops short of a painful, cold truth; your content is probably going to be ignored. It sucks to keep sharing your content and having no one contribute and add their own opinions / takes to yours. I know because I’ve been doing this for a decade now, ah!
I posed this problem to Sophie Koonin at the closing get-together at Beyond Tellerrand conference in Düsseldorf, and she was kind enough to share some of her ideas on this. She mentioned POSSEing your content (ie, posting it on your own website and then sharing it on all the platforms), mentioned webrings and personalsit.es, but also agreed none of this will guarantee that a continued, healthy conversation will keep happening at your own personal website. Your amazingly quirky content and your exciting ideas are prone to be forever ignored by the wider web.
I’ll link to yours if you link to mine
Lots of the attendees at #BTConf are interested, on top of interesting. Lots of them have personal websites, and are kind enough to link to each other’s websites, given the chance and the right push. So I decided to stir the exchanges a bit, and posted a request for URLs:
And with this, personal sites started pinging. And I started listing them on this page. Send me your personal URL (RSS feed included, if you have it), my touch points are here. Or by simply commenting on this post.
Proposal for a man-machine powered protocol
Tantek was kind enough to hop on the previous Mastodon post and lay out some indie web approaches and technologies that can help discoverability of your content. But this ultimately is a human problem as well, recommendations need to come with social validation lest they effectively be taken into account. Ie, I am much more likely to read / follow / comment someone’s content if I have met this person or if someone recommended them to me. People belonging to a MAFIA will float up much quicker than a new kid on the block trying to get noticed. This happens across industries, because all industries are operated and run by humans.
We need an approach that not only relies on Web Mentions, ActivityPub, POSSIE, etc, but also stems from veterans and well-known (linked) people on the web linking newcomers, or simply someone who hasn’t been able to establish an online presence yet. I am not sure how this would work in practice — this is a call for discussion — but already have a name for it: AIFAM. It’s MAFIA mirrored, meaning it should work as an anti-MAFIA, a selfless and democratizing sharing of influence online. It’s pronounced “Hey, Fam! 👋”.
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://fredrocha.net/2023/04/21/build-your-own-website-and-they-will-not-come/",
"content": {
"html": "<p>Creating your own website, own your data and display the things you\u2019re into under your domain. When online, be a creator, not a consumer.</p><p>I\u2019m all in for this mantra, but this realization stops short of a painful, cold truth; your content is probably going to be ignored. It sucks to keep sharing your content and having no one contribute and add their own opinions / takes to yours. I know because I\u2019ve been doing this for a decade now, ah!</p><p></p><p>I posed this problem to <a href=\"https://localghost.dev\">Sophie Koonin</a> at the closing get-together at <a href=\"http://beyondtellerrand.com\">Beyond Tellerrand conference in D\u00fcsseldorf</a>, and she was kind enough to share some of her ideas on this. She mentioned <a href=\"https://indieweb.org/POSSE\">POSSEing</a> your content (ie, posting it on your own website and then sharing it on all the platforms), mentioned <a href=\"https://hotlinewebring.club/\">webrings</a> and <a href=\"http://personalsit.es\">personalsit.es</a>, but also agreed none of this will guarantee that a continued, healthy conversation will keep happening at your own personal website. Your amazingly quirky content and your exciting ideas are prone to be forever ignored by the wider web.</p><p>I\u2019ll link to yours if you link to mine</p><p>Lots of the attendees at <a href=\"https://mastodon.social/tags/btconf\">#BTConf</a> are interested, on top of interesting. Lots of them have personal websites, and are kind enough to link to each other\u2019s websites, given the chance and the right push. So I decided to stir the exchanges a bit, and posted a request for URLs:</p><p>(<a href=\"https://mastodon.social/@john_fisherman/110224246899618915\">https://mastodon.social/@john_fisherman/110224246899618915</a>)</p><p>And with this, personal sites started pinging. And I started listing them on <a href=\"https://fredrocha.net/like-minded/#btconf-sites\">this page</a>. Send me your personal URL (RSS feed included, if you have it), my touch points are <a href=\"https://fredrocha.net/contact/\">here</a>. Or by simply commenting on this post.</p><p>Proposal for a man-machine powered protocol</p><p>Tantek was kind enough to hop on the previous Mastodon post and <a href=\"https://tantek.com/2023/109/t1/btconf-personal-url-fediverse-feed?skin=trn\">lay out some indie web approaches and technologies that can help discoverability of your content</a>. But this ultimately is a human problem as well, recommendations need to come with social validation lest they effectively be taken into account. Ie, I am much more likely to read / follow / comment someone\u2019s content if I have met this person or if someone recommended them to me. People belonging to a MAFIA will float up much quicker than a new kid on the block trying to get noticed. This happens across industries, because all industries are operated and run by humans. </p><p>We need an approach that not only relies on Web Mentions, ActivityPub, POSSIE, etc, but also stems from veterans and well-known (linked) people on the web linking newcomers, or simply someone who hasn\u2019t been able to establish an online presence yet. I am not sure how this would work in practice \u2014 this is a call for discussion \u2014 but already have a name for it: AIFAM. It\u2019s MAFIA mirrored, meaning it should work as an anti-MAFIA, a selfless and democratizing sharing of influence online. It\u2019s pronounced \u201cHey, Fam! \ud83d\udc4b\u201d.</p><p>Discuss!</p><p></p><p></p><p><a class=\"u-tag u-category\" href=\"https://fredrocha.net/tag/btconf/\">#btconf</a> <a class=\"u-tag u-category\" href=\"https://fredrocha.net/tag/indieweb/\">#indieweb</a></p><p><a href=\"https://fredrocha.net/2023/04/21/build-your-own-website-and-they-will-not-come/\">https://fredrocha.net/2023/04/21/build-your-own-website-and-they-will-not-come/</a></p>",
"text": "Creating your own website, own your data and display the things you\u2019re into under your domain. When online, be a creator, not a consumer.I\u2019m all in for this mantra, but this realization stops short of a painful, cold truth; your content is probably going to be ignored. It sucks to keep sharing your content and having no one contribute and add their own opinions / takes to yours. I know because I\u2019ve been doing this for a decade now, ah!I posed this problem to Sophie Koonin at the closing get-together at Beyond Tellerrand conference in D\u00fcsseldorf, and she was kind enough to share some of her ideas on this. She mentioned POSSEing your content (ie, posting it on your own website and then sharing it on all the platforms), mentioned webrings and personalsit.es, but also agreed none of this will guarantee that a continued, healthy conversation will keep happening at your own personal website. Your amazingly quirky content and your exciting ideas are prone to be forever ignored by the wider web.I\u2019ll link to yours if you link to mineLots of the attendees at #BTConf are interested, on top of interesting. Lots of them have personal websites, and are kind enough to link to each other\u2019s websites, given the chance and the right push. So I decided to stir the exchanges a bit, and posted a request for URLs:(https://mastodon.social/@john_fisherman/110224246899618915)And with this, personal sites started pinging. And I started listing them on this page. Send me your personal URL (RSS feed included, if you have it), my touch points are here. Or by simply commenting on this post.Proposal for a man-machine powered protocolTantek was kind enough to hop on the previous Mastodon post and lay out some indie web approaches and technologies that can help discoverability of your content. But this ultimately is a human problem as well, recommendations need to come with social validation lest they effectively be taken into account. Ie, I am much more likely to read / follow / comment someone\u2019s content if I have met this person or if someone recommended them to me. People belonging to a MAFIA will float up much quicker than a new kid on the block trying to get noticed. This happens across industries, because all industries are operated and run by humans. We need an approach that not only relies on Web Mentions, ActivityPub, POSSIE, etc, but also stems from veterans and well-known (linked) people on the web linking newcomers, or simply someone who hasn\u2019t been able to establish an online presence yet. I am not sure how this would work in practice \u2014 this is a call for discussion \u2014 but already have a name for it: AIFAM. It\u2019s MAFIA mirrored, meaning it should work as an anti-MAFIA, a selfless and democratizing sharing of influence online. It\u2019s pronounced \u201cHey, Fam! \ud83d\udc4b\u201d.Discuss!#btconf #indiewebhttps://fredrocha.net/2023/04/21/build-your-own-website-and-they-will-not-come/"
},
"published": "2023-04-21T17:28:02+00:00",
"post-type": "note",
"_id": "36701531",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "@voxpelli",
"url": "https://mastodon.social/@voxpelli",
"photo": null
},
"url": "https://mastodon.social/@voxpelli/110237621219568714",
"content": {
"html": "<p>For this weeks <a href=\"https://mastodon.social/tags/FollowFriday\">#<span>FollowFriday</span></a> I want to suggest:</p><p>Follow hashtags here on Mastodon!</p><p>Eg: <a href=\"https://mastodon.social/tags/webmention\">#<span>webmention</span></a> or <a href=\"https://mastodon.social/tags/IndieWeb\">#<span>IndieWeb</span></a></p><p>Perhaps <a href=\"https://mastodon.social/tags/nodejs\">#<span>nodejs</span></a> or <a href=\"https://mastodon.social/tags/rp2040\">#<span>rp2040</span></a></p><p>A great way to find new people and great posts.</p><p>Also: Remember to add hashtags and to use camel case / pascal case when doing so!</p>",
"text": "For this weeks #FollowFriday I want to suggest:Follow hashtags here on Mastodon!Eg: #webmention or #IndieWebPerhaps #nodejs or #rp2040A great way to find new people and great posts.Also: Remember to add hashtags and to use camel case / pascal case when doing so!"
},
"published": "2023-04-21T15:56:48+00:00",
"post-type": "note",
"_id": "36699751",
"_source": "7235",
"_is_read": false
}