I updated my homepage to show the latest photo post: gregorlove.com/#photos
{
"type": "entry",
"published": "2023-01-13 17:33-0800",
"url": "https://gregorlove.com/2023/01/i-updated-my-homepage/",
"category": [
"indieweb"
],
"content": {
"text": "I updated my homepage to show the latest photo post: gregorlove.com/#photos",
"html": "<p>I updated my homepage to show the latest photo post: <a href=\"https://gregorlove.com/#photos\">gregorlove.com/#photos</a></p>"
},
"author": {
"type": "card",
"name": "gRegor Morrill",
"url": "https://gregorlove.com/",
"photo": "https://gregorlove.com/site/assets/files/6268/profile-2021-square.300x0.jpg"
},
"post-type": "note",
"_id": "34400305",
"_source": "95",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "@tmichellemoore",
"url": "https://mastodon.social/@tmichellemoore",
"photo": null
},
"url": "https://mastodon.social/@tmichellemoore/109684791107020064",
"content": {
"html": "<p>Project Journal: Onboarding a Project Team: <a href=\"https://tmichellemoore.com/?p=151821\"><span>https://</span><span>tmichellemoore.com/?p=151821</span><span></span></a></p><p>Day 6 of 100 <a href=\"https://mastodon.social/tags/100DaysofIndieWeb\">#<span>100DaysofIndieWeb</span></a>, <a href=\"https://mastodon.social/tags/IndieWeb\">#<span>IndieWeb</span></a>, <a href=\"https://mastodon.social/tags/ProjectJournal\">#<span>ProjectJournal</span></a>, <a href=\"https://mastodon.social/tags/ProjectManagement\">#<span>ProjectManagement</span></a></p>",
"text": "Project Journal: Onboarding a Project Team: https://tmichellemoore.com/?p=151821Day 6 of 100 #100DaysofIndieWeb, #IndieWeb, #ProjectJournal, #ProjectManagement"
},
"published": "2023-01-14T00:44:50+00:00",
"post-type": "note",
"_id": "34397306",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "@tmichellemoore",
"url": "https://mastodon.social/@tmichellemoore",
"photo": null
},
"url": "https://mastodon.social/@tmichellemoore/109678946371796879",
"content": {
"html": "<p>Project Journal: IndieWeb Project Progress: <a href=\"https://tmichellemoore.com/?p=151791\"><span>https://</span><span>tmichellemoore.com/?p=151791</span><span></span></a><br />Day 5 of 100 <a href=\"https://mastodon.social/tags/100DaysofIndieWeb\">#<span>100DaysofIndieWeb</span></a>, <a href=\"https://mastodon.social/tags/IndieWeb\">#<span>IndieWeb</span></a>, <a href=\"https://mastodon.social/tags/ProjectJournal\">#<span>ProjectJournal</span></a>, <a href=\"https://mastodon.social/tags/ProjectManagement\">#<span>ProjectManagement</span></a></p>",
"text": "Project Journal: IndieWeb Project Progress: https://tmichellemoore.com/?p=151791\nDay 5 of 100 #100DaysofIndieWeb, #IndieWeb, #ProjectJournal, #ProjectManagement"
},
"published": "2023-01-12T23:58:27+00:00",
"post-type": "note",
"_id": "34397307",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "@hollie",
"url": "https://social.coop/@hollie",
"photo": null
},
"url": "https://social.coop/@hollie/109684337200050018",
"content": {
"html": "<p>IndieWeb online event on Sunday! Learning about Webmention: </p><p><a href=\"https://events.indieweb.org/2023/01/decentralized-website-communication-with-webmention-49Mvf9ZDUHzk\"><span>https://</span><span>events.indieweb.org/2023/01/de</span><span>centralized-website-communication-with-webmention-49Mvf9ZDUHzk</span></a></p><p><a href=\"https://social.coop/tags/IndieWeb\">#<span>IndieWeb</span></a> <a href=\"https://social.coop/tags/WebMention\">#<span>WebMention</span></a></p>",
"text": "IndieWeb online event on Sunday! Learning about Webmention: https://events.indieweb.org/2023/01/decentralized-website-communication-with-webmention-49Mvf9ZDUHzk#IndieWeb #WebMention"
},
"published": "2023-01-13T22:49:24+00:00",
"post-type": "note",
"_id": "34395167",
"_source": "7235",
"_is_read": false
}
I added a "Guestbook" to my personal site!
Feel free to drop by and sign it however you please:
https://foreverliketh.is/docs/assortments/guestbook/
Also open to any thoughts / suggestions on its implementation.
#webdev #web #indieweb #website #hugo
{
"type": "entry",
"author": {
"name": "@accordionpolar",
"url": "https://indieweb.social/@accordionpolar",
"photo": null
},
"url": "https://indieweb.social/@accordionpolar/109683797126633510",
"content": {
"html": "<p>I added a \"Guestbook\" to my personal site!</p><p>Feel free to drop by and sign it however you please:</p><p><a href=\"https://foreverliketh.is/docs/assortments/guestbook/\"><span>https://</span><span>foreverliketh.is/docs/assortme</span><span>nts/guestbook/</span></a></p><p>Also open to any thoughts / suggestions on its implementation.</p><p><a href=\"https://indieweb.social/tags/webdev\">#<span>webdev</span></a> <a href=\"https://indieweb.social/tags/web\">#<span>web</span></a> <a href=\"https://indieweb.social/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://indieweb.social/tags/website\">#<span>website</span></a> <a href=\"https://indieweb.social/tags/hugo\">#<span>hugo</span></a></p>",
"text": "I added a \"Guestbook\" to my personal site!Feel free to drop by and sign it however you please:https://foreverliketh.is/docs/assortments/guestbook/Also open to any thoughts / suggestions on its implementation.#webdev #web #indieweb #website #hugo"
},
"published": "2023-01-13T20:32:03+00:00",
"post-type": "note",
"_id": "34392422",
"_source": "7235",
"_is_read": false
}
New Core Intuition! We talk about marketing and upcoming app plans. I also fixed a feed issue in Micro.blog with it, so posts will start flowing into @coreint@micro.blog again for fediverse folks who want to follow along.
{
"type": "entry",
"author": {
"name": "Manton Reece",
"url": "https://www.manton.org/",
"photo": "https://micro.blog/manton/avatar.jpg"
},
"url": "https://www.manton.org/2023/01/13/new-core-intuition.html",
"content": {
"html": "<p><a href=\"https://coreint.org/2023/01/episode-544-a-bit-of-a-conflict-there/\">New Core Intuition</a>! We talk about marketing and upcoming app plans. I also fixed a feed issue in Micro.blog with it, so posts will start flowing into <a href=\"https://micro.blog/coreint@micro.blog\">@coreint@micro.blog</a> again for fediverse folks who want to follow along.</p>",
"text": "New Core Intuition! We talk about marketing and upcoming app plans. I also fixed a feed issue in Micro.blog with it, so posts will start flowing into @coreint@micro.blog again for fediverse folks who want to follow along."
},
"published": "2023-01-13T14:05:21-06:00",
"category": [
"Podcasts"
],
"post-type": "note",
"_id": "34392359",
"_source": "12",
"_is_read": false
}
Are there any other indie web makers on Mastodon making cool things?
#indieweb #indie #maker
{
"type": "entry",
"author": {
"name": "@taylorishere",
"url": "https://mas.to/@taylorishere",
"photo": null
},
"url": "https://mas.to/@taylorishere/109683145752159155",
"content": {
"html": "<p>Are there any other indie web makers on Mastodon making cool things?</p><p><a href=\"https://mas.to/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://mas.to/tags/indie\">#<span>indie</span></a> <a href=\"https://mas.to/tags/maker\">#<span>maker</span></a></p>",
"text": "Are there any other indie web makers on Mastodon making cool things?#indieweb #indie #maker"
},
"published": "2023-01-13T17:46:24+00:00",
"post-type": "note",
"_id": "34388848",
"_source": "7235",
"_is_read": false
}
I'm dying! The Normal Gossip Podcast described 90s internet as
"a magical, lawless land where fewer parts of the internet were centralized so that 4 men could make a lot of money"
#internet #indieweb
{
"type": "entry",
"author": {
"name": "@SueNeu",
"url": "https://fosstodon.org/@SueNeu",
"photo": null
},
"url": "https://fosstodon.org/@SueNeu/109682993574312492",
"content": {
"html": "<p>I'm dying! The Normal Gossip Podcast described 90s internet as </p><p>\"a magical, lawless land where fewer parts of the internet were centralized so that 4 men could make a lot of money\"</p><p><a href=\"https://fosstodon.org/tags/internet\">#<span>internet</span></a> <a href=\"https://fosstodon.org/tags/indieweb\">#<span>indieweb</span></a></p>",
"text": "I'm dying! The Normal Gossip Podcast described 90s internet as \"a magical, lawless land where fewer parts of the internet were centralized so that 4 men could make a lot of money\"#internet #indieweb"
},
"published": "2023-01-13T17:07:42+00:00",
"post-type": "note",
"_id": "34387789",
"_source": "7235",
"_is_read": false
}
One way of getting to know me is my writing and my talks.
Here is a selection of posts within the areas of Digital Ethics, Human Rights, Usability, Accessibility and more – all with a leaning towards design and communication theory.
The Elements of Digital Ethics
AI and Human Rights - video and transcript
The Trouble Diamond
Design for Universal Wellbeing
The world map that reboots your brain
The slavery supported by that device in your pocket
Tech addiction: Why it matters
Digital Compassion: A Human Act
Fairy tale experiences talk at UXLx - my first talk on design ethics in front of an international audience
25 years of online resilience - a newsletter about #indieweb
Digital abuse is hard to leave – by design
I teach, consult and write about these issues. If you want to know more, don’t hesitate to contact me.
#Introduction #DigitalEthics
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://indieweb.social/tags/indieweb",
"photo": null
},
"url": "https://axbom.me/objects/20db85fa-2c49-4205-9bb9-f91264f4cabf",
"content": {
"html": "<p>One way of getting to know me is my writing and my talks.</p><p>Here is a selection of posts within the areas of Digital Ethics, Human Rights, Usability, Accessibility and more \u2013 all with a leaning towards design and communication theory.</p><p><a href=\"https://axbom.com/elements/\">The Elements of Digital Ethics</a><br /><a href=\"https://axbom.com/aihr/\">AI and Human Rights</a> - video and transcript<br /><a href=\"https://axbom.com/trouble-diamond/\">The Trouble Diamond</a><br /><a href=\"https://axbom.com/design-for-universal-wellbeing/\">Design for Universal Wellbeing</a><br /><a href=\"https://axbom.com/world-map/\">The world map that reboots your brain</a><br /><a href=\"https://axbom.com/the-slavery-behind-the-device-in-your-pocket/\"> The slavery supported by that device in your pocket</a><br /><a href=\"https://axbom.com/tech-addiction/\">Tech addiction: Why it matters</a><br /><a href=\"https://axbom.com/digital-compassion-human-act/\">Digital Compassion: A Human Act</a><br /><a href=\"https://axbom.com/fairytale/\">Fairy tale experiences talk at UXLx</a> - my first talk on design ethics in front of an international audience<br /><a href=\"https://axbom.com/25y/\">25 years of online resilience</a> - a newsletter about <a href=\"https://axbom.me/tag/indieweb\">#indieweb</a><br /><a href=\"https://axbom.com/digital-abuse-is-hard-to-leave/\">Digital abuse is hard to leave \u2013 by design</a></p><p>I teach, consult and write about these issues. If you want to know more, don\u2019t hesitate to <a href=\"https://axbom.com/contact/\">contact me</a>.</p><p><a href=\"https://axbom.me/tag/introduction\">#Introduction</a> <a href=\"https://axbom.me/tag/digitalethics\">#DigitalEthics</a></p>",
"text": "One way of getting to know me is my writing and my talks.Here is a selection of posts within the areas of Digital Ethics, Human Rights, Usability, Accessibility and more \u2013 all with a leaning towards design and communication theory.The Elements of Digital Ethics\nAI and Human Rights - video and transcript\nThe Trouble Diamond\nDesign for Universal Wellbeing\nThe world map that reboots your brain\n The slavery supported by that device in your pocket\nTech addiction: Why it matters\nDigital Compassion: A Human Act\nFairy tale experiences talk at UXLx - my first talk on design ethics in front of an international audience\n25 years of online resilience - a newsletter about #indieweb\nDigital abuse is hard to leave \u2013 by designI teach, consult and write about these issues. If you want to know more, don\u2019t hesitate to contact me.#Introduction #DigitalEthics"
},
"published": "2023-01-13T14:51:07+00:00",
"post-type": "note",
"_id": "34384702",
"_source": "7235",
"_is_read": false
}
🎉 Six years ago today, the #IndieWeb Webmention protocol was published as a W3C REC https://www.w3.org/TR/webmention/
A key social web building block, Webmention enabled peer-to-peer comments, likes, and other responses to be created, updated, and deleted across the web, by both dynamic & static websites.
It was accompanied by a report of over a dozen implementations that demonstrated interoperability: https://webmention.net/implementation-reports/summary/ using an open test suite: https://webmention.rocks/ that is still up and running and used by developers today.
Many many more implementations have been developed, open sourced, shipped, launched since. The specification itself has a webmention endpoint and accepts webmentions.
Exactly a year before that, Webmention was published as a First Public Working Draft by the W3C Social Web Working Group: https://www.w3.org/TR/2016/WD-webmention-20160112/
It took the best parts of the prior Pingback protocol, simplified it (ditched XML-RPC), made it more secure, separated presentation from plumbing, and added update & delete semantics.
It was in many ways a model for how open web standards should be developed.
See the wiki page for an overview and numerous screenshots of implementations: https://indieweb.org/Webmention
If you want to implement Webmention yourself, there are now numerous developer resources to do so.
Start here: https://indieweb.org/Webmention-developer and come say hi at the IndieWeb development chat channel: https://chat.indieweb.org/dev
Previously, previously, previously:
* https://tantek.com/2020/012/t1/happy-birthday-webmention
* https://tantek.com/2018/012/t1/anniversary-million-webmentions
* https://tantek.com/2017/012/t1/webmntion-first-w3c-recommendation-high-bar
This is day 12 of #100DaysOfIndieWeb #100Days.
← Day 11: https://tantek.com/2023/011/t1/indieweb-evolving-at-mention
→ 🔮
{
"type": "entry",
"published": "2023-01-12 23:45-0800",
"url": "http://tantek.com/2023/012/t1/six-years-webmention-w3c",
"category": [
"IndieWeb",
"100DaysOfIndieWeb",
"100Days"
],
"content": {
"text": "\ud83c\udf89 Six years ago today, the #IndieWeb Webmention protocol was published as a W3C REC https://www.w3.org/TR/webmention/\n\nA key social web building block, Webmention enabled peer-to-peer comments, likes, and other responses to be created, updated, and deleted across the web, by both dynamic & static websites.\n\nIt was accompanied by a report of over a dozen implementations that demonstrated interoperability: https://webmention.net/implementation-reports/summary/ using an open test suite: https://webmention.rocks/ that is still up and running and used by developers today.\n\nMany many more implementations have been developed, open sourced, shipped, launched since. The specification itself has a webmention endpoint and accepts webmentions.\n\nExactly a year before that, Webmention was published as a First Public Working Draft by the W3C Social Web Working Group: https://www.w3.org/TR/2016/WD-webmention-20160112/\n\nIt took the best parts of the prior Pingback protocol, simplified it (ditched XML-RPC), made it more secure, separated presentation from plumbing, and added update & delete semantics. \n\nIt was in many ways a model for how open web standards should be developed.\n\nSee the wiki page for an overview and numerous screenshots of implementations: https://indieweb.org/Webmention\n\nIf you want to implement Webmention yourself, there are now numerous developer resources to do so.\n\nStart here: https://indieweb.org/Webmention-developer and come say hi at the IndieWeb development chat channel: https://chat.indieweb.org/dev\n\nPreviously, previously, previously: \n* https://tantek.com/2020/012/t1/happy-birthday-webmention\n* https://tantek.com/2018/012/t1/anniversary-million-webmentions\n* https://tantek.com/2017/012/t1/webmntion-first-w3c-recommendation-high-bar\n\nThis is day 12 of #100DaysOfIndieWeb #100Days.\n\n\u2190 Day 11: https://tantek.com/2023/011/t1/indieweb-evolving-at-mention\n\u2192 \ud83d\udd2e",
"html": "\ud83c\udf89 Six years ago today, the #<span class=\"p-category\">IndieWeb</span> Webmention protocol was published as a W3C REC <a href=\"https://www.w3.org/TR/webmention/\">https://www.w3.org/TR/webmention/</a><br /><br />A key social web building block, Webmention enabled peer-to-peer comments, likes, and other responses to be created, updated, and deleted across the web, by both dynamic & static websites.<br /><br />It was accompanied by a report of over a dozen implementations that demonstrated interoperability: <a href=\"https://webmention.net/implementation-reports/summary/\">https://webmention.net/implementation-reports/summary/</a> using an open test suite: <a href=\"https://webmention.rocks/\">https://webmention.rocks/</a> that is still up and running and used by developers today.<br /><br />Many many more implementations have been developed, open sourced, shipped, launched since. The specification itself has a webmention endpoint and accepts webmentions.<br /><br />Exactly a year before that, Webmention was published as a First Public Working Draft by the W3C Social Web Working Group: <a href=\"https://www.w3.org/TR/2016/WD-webmention-20160112/\">https://www.w3.org/TR/2016/WD-webmention-20160112/</a><br /><br />It took the best parts of the prior Pingback protocol, simplified it (ditched XML-RPC), made it more secure, separated presentation from plumbing, and added update & delete semantics. <br /><br />It was in many ways a model for how open web standards should be developed.<br /><br />See the wiki page for an overview and numerous screenshots of implementations: <a href=\"https://indieweb.org/Webmention\">https://indieweb.org/Webmention</a><br /><br />If you want to implement Webmention yourself, there are now numerous developer resources to do so.<br /><br />Start here: <a href=\"https://indieweb.org/Webmention-developer\">https://indieweb.org/Webmention-developer</a> and come say hi at the IndieWeb development chat channel: <a href=\"https://chat.indieweb.org/dev\">https://chat.indieweb.org/dev</a><br /><br />Previously, previously, previously: <br />* <a href=\"https://tantek.com/2020/012/t1/happy-birthday-webmention\">https://tantek.com/2020/012/t1/happy-birthday-webmention</a><br />* <a href=\"https://tantek.com/2018/012/t1/anniversary-million-webmentions\">https://tantek.com/2018/012/t1/anniversary-million-webmentions</a><br />* <a href=\"https://tantek.com/2017/012/t1/webmntion-first-w3c-recommendation-high-bar\">https://tantek.com/2017/012/t1/webmntion-first-w3c-recommendation-high-bar</a><br /><br />This is day 12 of #<span class=\"p-category\">100DaysOfIndieWeb</span> #<span class=\"p-category\">100Days</span>.<br /><br />\u2190 Day 11: <a href=\"https://tantek.com/2023/011/t1/indieweb-evolving-at-mention\">https://tantek.com/2023/011/t1/indieweb-evolving-at-mention</a><br />\u2192 \ud83d\udd2e"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "http://tantek.com/",
"photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "note",
"_id": "34381253",
"_source": "1",
"_is_read": false
}
I was able to get my #100DaysofIndieweb post today in just under the wire. I was actually able to write it from my phone!
Have a look here: https://crowdersoup.com/posts/projects/indieweb/100-days/day-7-posting-from-my-phone/
#indieweb
{
"type": "entry",
"author": {
"name": "@CrowderSoup",
"url": "https://hachyderm.io/@CrowderSoup",
"photo": null
},
"url": "https://hachyderm.io/@CrowderSoup/109680623482980974",
"content": {
"html": "<p>I was able to get my <a href=\"https://hachyderm.io/tags/100DaysofIndieweb\">#<span>100DaysofIndieweb</span></a> post today in just under the wire. I was actually able to write it from my phone!</p><p>Have a look here: <a href=\"https://crowdersoup.com/posts/projects/indieweb/100-days/day-7-posting-from-my-phone/\"><span>https://</span><span>crowdersoup.com/posts/projects</span><span>/indieweb/100-days/day-7-posting-from-my-phone/</span></a></p><p><a href=\"https://hachyderm.io/tags/indieweb\">#<span>indieweb</span></a></p>",
"text": "I was able to get my #100DaysofIndieweb post today in just under the wire. I was actually able to write it from my phone!Have a look here: https://crowdersoup.com/posts/projects/indieweb/100-days/day-7-posting-from-my-phone/#indieweb"
},
"published": "2023-01-13T07:04:57+00:00",
"post-type": "note",
"_id": "34377029",
"_source": "7235",
"_is_read": false
}
Someone should create a service that enables people to establish and retain an identity in the Fediverse. Its great that you can move from instance-to-instance on Mastodon, with redirection, but it would be better if the instance that a user was on was largely irrelevant.
You should be “@ user @ your domain” and seamlessly be able to change backend instances.
{
"type": "entry",
"published": "2023-01-12T18:27:16+00:00",
"url": "https://cleverdevil.io/2023/someone-should-create-a-service-that-enables",
"syndication": [
"https://cleverdevil.club/@jonathan/109677645463280971"
],
"content": {
"text": "Someone should create a service that enables people to establish and retain an identity in the Fediverse. Its great that you can move from instance-to-instance on Mastodon, with redirection, but it would be better if the instance that a user was on was largely irrelevant.\n\n\nYou should be \u201c@ user @ your domain\u201d and seamlessly be able to change backend instances.",
"html": "Someone should create a service that enables people to establish and retain an identity in the Fediverse. Its great that you can move from instance-to-instance on Mastodon, with redirection, but it would be better if the instance that a user was on was largely irrelevant.<br /><br />\nYou should be \u201c@ user @ your domain\u201d and seamlessly be able to change backend instances."
},
"author": {
"type": "card",
"name": "Jonathan LaCour",
"url": "https://cleverdevil.io/profile/cleverdevil",
"photo": "https://cleverdevil.io/file/e37c3982acf4f0a8421d085b9971cd71/thumb.jpg"
},
"post-type": "note",
"_id": "34366064",
"_source": "71",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "@evenstar",
"url": "https://fandom.ink/@evenstar",
"photo": null
},
"url": "https://fandom.ink/@evenstar/109677312452882182",
"content": {
"html": "<p>opened: Memento Mori, the Yami no Matsuei fanlisting<br /><a href=\"http://hoshi.nu/yamimatsu/\"><span>http://</span><span>hoshi.nu/yamimatsu/</span><span></span></a></p><p>...okay, it's 3AM, I'm exhausted, bedtime nao.</p><p><a href=\"https://fandom.ink/tags/YaminoMatsuei\">#<span>YaminoMatsuei</span></a> <a href=\"https://fandom.ink/tags/YamiMatsu\">#<span>YamiMatsu</span></a> <a href=\"https://fandom.ink/tags/fanlisting\">#<span>fanlisting</span></a> <a href=\"https://fandom.ink/tags/fansite\">#<span>fansite</span></a> <a href=\"https://fandom.ink/tags/staticwebsite\">#<span>staticwebsite</span></a> <a href=\"https://fandom.ink/tags/oldweb\">#<span>oldweb</span></a> <a href=\"https://fandom.ink/tags/handmadehtml\">#<span>handmadehtml</span></a> <a href=\"https://fandom.ink/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://fandom.ink/tags/retroweb\">#<span>retroweb</span></a></p>",
"text": "opened: Memento Mori, the Yami no Matsuei fanlisting\nhttp://hoshi.nu/yamimatsu/...okay, it's 3AM, I'm exhausted, bedtime nao.#YaminoMatsuei #YamiMatsu #fanlisting #fansite #staticwebsite #oldweb #handmadehtml #indieweb #retroweb"
},
"published": "2023-01-12T17:02:55+00:00",
"post-type": "note",
"_id": "34364284",
"_source": "7235",
"_is_read": false
}
I think an often-overlooked tool for us alternative-platform users is bridging/syndication. Not everyone agrees on what platforms to use, and that's okay.
How do we resolve disagreements in platform choice? By bridging between them! We must accept disagreements in choice.
Also known as: https://indieweb.org/bridge_all_the_things
i.e. Philosophies must be progressive -- not in the political sense, but in the "don't expect everyone to use the same platform" sense.
#SocialCoding #IndieWeb #Fediverse
{
"type": "entry",
"author": {
"name": "@ignis",
"url": "https://poketopia.city/@ignis",
"photo": null
},
"url": "https://poketopia.city/@ignis/109677283593874698",
"content": {
"html": "<p>I think an often-overlooked tool for us alternative-platform users is bridging/syndication. Not everyone agrees on what platforms to use, and that's okay.</p><p>How do we resolve disagreements in platform choice? By bridging between them! We must accept disagreements in choice.</p><p>Also known as: <a href=\"https://indieweb.org/bridge_all_the_things\"><span>https://</span><span>indieweb.org/bridge_all_the_th</span><span>ings</span></a></p><p>i.e. Philosophies must be progressive -- not in the political sense, but in the \"don't expect everyone to use the same platform\" sense.</p><p><a href=\"https://poketopia.city/tags/SocialCoding\">#<span>SocialCoding</span></a> <a href=\"https://poketopia.city/tags/IndieWeb\">#<span>IndieWeb</span></a> <a href=\"https://poketopia.city/tags/Fediverse\">#<span>Fediverse</span></a></p>",
"text": "I think an often-overlooked tool for us alternative-platform users is bridging/syndication. Not everyone agrees on what platforms to use, and that's okay.How do we resolve disagreements in platform choice? By bridging between them! We must accept disagreements in choice.Also known as: https://indieweb.org/bridge_all_the_thingsi.e. Philosophies must be progressive -- not in the political sense, but in the \"don't expect everyone to use the same platform\" sense.#SocialCoding #IndieWeb #Fediverse"
},
"published": "2023-01-12T16:55:35+00:00",
"post-type": "note",
"_id": "34362637",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"published": "2023-01-12T15:39:35+00:00",
"url": "https://werd.io/2023/medium-embraces-mastodon",
"category": [
"Technology"
],
"bookmark-of": [
"https://blog.medium.com/medium-embraces-mastodon-19dcb873eb11"
],
"name": "Medium embraces Mastodon",
"content": {
"text": "\u201cToday, Medium is launching a Mastodon instance at me.dm to help our authors, publications and readers find a home in the fediverse. Mastodon is an emerging force for good in social media and we are excited to join this community.\u201d Hell yeah. #Technology",
"html": "<p>\u201cToday, Medium is launching a Mastodon instance at me.dm to help our authors, publications and readers find a home in the fediverse. Mastodon is an emerging force for good in social media and we are excited to join this community.\u201d Hell yeah. <a href=\"https://werd.io/tag/Technology\" class=\"p-category\">#Technology</a></p>"
},
"author": {
"type": "card",
"name": "Ben Werdmuller",
"url": "https://werd.io/profile/benwerd",
"photo": "https://werd.io/file/5d388c5fb16ea14aac640912/thumb.jpg"
},
"post-type": "bookmark",
"_id": "34362486",
"_source": "191",
"_is_read": false
}
I’ll be watching as Medium runs their own Mastodon instance. I like my approach better: integrating ActivityPub directly into the blog platform, not alongside it as a separate platform. But there’s no single right way to do this.
{
"type": "entry",
"author": {
"name": "Manton Reece",
"url": "https://www.manton.org/",
"photo": "https://micro.blog/manton/avatar.jpg"
},
"url": "https://www.manton.org/2023/01/12/ill-be-watching.html",
"content": {
"html": "<p>I\u2019ll be watching as <a href=\"https://blog.medium.com/medium-embraces-mastodon-19dcb873eb11\">Medium runs their own Mastodon instance</a>. I like my approach better: integrating ActivityPub directly into the blog platform, not alongside it as a separate platform. But there\u2019s no single right way to do this.</p>",
"text": "I\u2019ll be watching as Medium runs their own Mastodon instance. I like my approach better: integrating ActivityPub directly into the blog platform, not alongside it as a separate platform. But there\u2019s no single right way to do this."
},
"published": "2023-01-12T09:47:35-06:00",
"post-type": "note",
"_id": "34361067",
"_source": "12",
"_is_read": false
}
The #indieweb social scene is jumping this morning. On Twitter at https://twitter.com/faebornofficial, is mostly the one retweeting all of them. I run that account, by the way.
{
"type": "entry",
"author": {
"name": "@cambridgeport90",
"url": "https://indieweb.social/@cambridgeport90",
"photo": null
},
"url": "https://indieweb.social/@cambridgeport90/109676816017606991",
"content": {
"html": "<p>The <a href=\"https://indieweb.social/tags/indieweb\">#<span>indieweb</span></a> social scene is jumping this morning. On Twitter at <a href=\"https://twitter.com/faebornofficial\"><span>https://</span><span>twitter.com/faebornofficial</span><span></span></a>, is mostly the one retweeting all of them. I run that account, by the way.</p>",
"text": "The #indieweb social scene is jumping this morning. On Twitter at https://twitter.com/faebornofficial, is mostly the one retweeting all of them. I run that account, by the way."
},
"published": "2023-01-12T14:56:40+00:00",
"post-type": "note",
"_id": "34359376",
"_source": "7235",
"_is_read": false
}
One of the fun things about #IndieWeb notes & replies is that how we post is actively evolving! Like how should we @ someone?
#socialMedia aliases (e.g. @Twitter) were obvious, with prior @-name usage on Flickr etc.
Now, some have a domain, or an @-@ (pronounced at-at, yes, just like the abbreviation for Imperial All Terrain Armored Transport^1), or some have both.
We can ask questions like why do we @-someone? What are the use-cases?
* In a reply to a public post, clearly express that you’re speaking to that person
* In a reply to a reply, that you’re speaking to everyone upthread (AKA a https://indieweb.org/canoe)
* When attributing something to someone (photo/post/cool thing by so-and-so), giving credit
* Distinguish a person (or something that can be followed) from “just” a site
* For all the above, notifying someone accordingly
Some ideas:
1. Ideally, if/when everyone has their own domain (where they receive Webmention notifications, and a feed you can follow), we can @-name their domain, which your auto-linker^2 should hyperlink accordingly, e.g.
* @aaronparecki.com @anomalily.net @Martymcgui.re @david.shanske.com @voxpelli.com @adactio.com @marcthiele.com @mxb.dev
These all look close enough to social media aliases/names that they’re immediately recognizable as readable @-names, a good consideration when choosing a domain name.^3
2. As a fallback (e.g. for non-@-domain-auto-linking destinations) we can use someone’s plain domain (explicitly with https:), especially if their home page still has a stream or feed you can follow, or maybe if they don’t receive homepage Webmentions (yet), e.g.:
* https://jacky.wtf/ https://tmichellemoore.com/ https://crowdersoup.com/
3. Some folks with personal sites have (for now) created separate Mastodon accounts (or installed an instance on a subdomain), and for them, we can reference their @-@ parenthetically after their domain, like:
* https://kevinmarks.com/ (@kevinmarks@xoxo.zone), https://dangillmor.com/ (@dangillmor@mastodon.social), https://simonwillison.net/ (@simon@simonwillison.net)
Rather than using social media silo @-names (except when explicitly replying to a silo), I’m now experimenting with all three of these (1-3) instead, both to elevate people’s IndieWeb identities, and for Mastodon viewers, provide a convenient way to follow @-@ addresses.
If someone’s homepage receives Webmentions, they will get notified when I @-mention them by domain.
I recently implemented syntactic auto-linking of @-@ addresses like this:
* @user@example.com --> https://example.com/@user
with a special case for @-domain@-domain to just link to the domain, e.g.:
* @tantek.com@tantek.com --> https://tantek.com/
I also made a recent policy decision to auto-link all @-@ (and @-domain) mentions to https:, the reasoning being that identities on the web should be using https.
* Testing in production here: https://tantek.com/cassis.js, search for "auto_link("
Some questions:
* Does/do Mastodon (or other ActivityPub servers) notify people when you @-@ mention them in a post? How? Who’s responsible for that?
* Will Bridgy Fed notify the servers (deliver to AP inboxes) of folks I merely @-@ mention (rather than explicit replies, reposts)? Should it?
So many people are switching to using their personal domains to post (or at least a Mastodon account) that I no longer feel compelled to @-mention people’s Twitter handles in posts, which feels refreshing.
Now the fun part is experimenting and figuring out what combination of @-domain, plain domain, or @-@ mentions looks good, makes sense to people, and sends notifications to people the way they want to receive them.
This is day 11 of #100DaysOfIndieWeb #100Days.
← Day 10: https://tantek.com/2023/010/t2/build-use-services
→ 🔮
^1 https://en.wikipedia.org/wiki/AT-AT
^2 My https://tantek.com/github/cassis/blob/master/cassis.js auto_link() function supports @example.com auto-linking, yours should too.
^3 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb
{
"type": "entry",
"published": "2023-01-11 23:59-0800",
"url": "http://tantek.com/2023/011/t1/indieweb-evolving-at-mention",
"category": [
"IndieWeb",
"socialMedia",
"100DaysOfIndieWeb",
"100Days"
],
"content": {
"text": "One of the fun things about #IndieWeb notes & replies is that how we post is actively evolving! Like how should we @ someone?\n\n#socialMedia aliases (e.g. @Twitter) were obvious, with prior @-name usage on Flickr etc.\n\nNow, some have a domain, or an @-@ (pronounced at-at, yes, just like the abbreviation for Imperial All Terrain Armored Transport^1), or some have both.\n\nWe can ask questions like why do we @-someone? What are the use-cases?\n* In a reply to a public post, clearly express that you\u2019re speaking to that person\n* In a reply to a reply, that you\u2019re speaking to everyone upthread (AKA a https://indieweb.org/canoe)\n* When attributing something to someone (photo/post/cool thing by so-and-so), giving credit\n* Distinguish a person (or something that can be followed) from \u201cjust\u201d a site\n* For all the above, notifying someone accordingly\n\nSome ideas:\n\n1. Ideally, if/when everyone has their own domain (where they receive Webmention notifications, and a feed you can follow), we can @-name their domain, which your auto-linker^2 should hyperlink accordingly, e.g.\n* @aaronparecki.com @anomalily.net @Martymcgui.re\u200e @david.shanske.com @voxpelli.com @adactio.com @marcthiele.com @mxb.dev\n\nThese all look close enough to social media aliases/names that they\u2019re immediately recognizable as readable @-names, a good consideration when choosing a domain name.^3\n\n2. As a fallback (e.g. for non-@-domain-auto-linking destinations) we can use someone\u2019s plain domain (explicitly with https:), especially if their home page still has a stream or feed you can follow, or maybe if they don\u2019t receive homepage Webmentions (yet), e.g.:\n* https://jacky.wtf/ https://tmichellemoore.com/ https://crowdersoup.com/\n\n3. Some folks with personal sites have (for now) created separate Mastodon accounts (or installed an instance on a subdomain), and for them, we can reference their @-@ parenthetically after their domain, like:\n* https://kevinmarks.com/ (@kevinmarks@xoxo.zone), https://dangillmor.com/ (@dangillmor@mastodon.social), https://simonwillison.net/ (@simon@simonwillison.net) \n\nRather than using social media silo @-names (except when explicitly replying to a silo), I\u2019m now experimenting with all three of these (1-3) instead, both to elevate people\u2019s IndieWeb identities, and for Mastodon viewers, provide a convenient way to follow @-@ addresses.\n\nIf someone\u2019s homepage receives Webmentions, they will get notified when I @-mention them by domain.\n\nI recently implemented syntactic auto-linking of @-@ addresses like this:\n* @user@example.com --> https://example.com/@user\nwith a special case for @-domain@-domain to just link to the domain, e.g.:\n* @tantek.com@tantek.com --> https://tantek.com/\n\nI also made a recent policy decision to auto-link all @-@ (and @-domain) mentions to https:, the reasoning being that identities on the web should be using https.\n* Testing in production here: https://tantek.com/cassis.js, search for \"auto_link(\"\n\nSome questions: \n* Does/do Mastodon (or other ActivityPub servers) notify people when you @-@ mention them in a post? How? Who\u2019s responsible for that?\n* Will Bridgy Fed notify the servers (deliver to AP inboxes) of folks I merely @-@ mention (rather than explicit replies, reposts)? Should it?\n\nSo many people are switching to using their personal domains to post (or at least a Mastodon account) that I no longer feel compelled to @-mention people\u2019s Twitter handles in posts, which feels refreshing. \n\nNow the fun part is experimenting and figuring out what combination of @-domain, plain domain, or @-@ mentions looks good, makes sense to people, and sends notifications to people the way they want to receive them.\n\nThis is day 11 of #100DaysOfIndieWeb #100Days.\n\n\u2190 Day 10: https://tantek.com/2023/010/t2/build-use-services\n\u2192 \ud83d\udd2e\n\n^1 https://en.wikipedia.org/wiki/AT-AT\n^2 My https://tantek.com/github/cassis/blob/master/cassis.js auto_link() function supports @example.com auto-linking, yours should too.\n^3 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb",
"html": "One of the fun things about #<span class=\"p-category\">IndieWeb</span> notes & replies is that how we post is actively evolving! Like how should we @ someone?<br /><br />#<span class=\"p-category\">socialMedia</span> aliases (e.g. <a class=\"h-cassis-username\" href=\"https://twitter.com/Twitter\">@Twitter</a>) were obvious, with prior @-name usage on Flickr etc.<br /><br />Now, some have a domain, or an @-@ (pronounced at-at, yes, just like the abbreviation for Imperial All Terrain Armored Transport^1), or some have both.<br /><br />We can ask questions like why do we @-someone? What are the use-cases?<br />* In a reply to a public post, clearly express that you\u2019re speaking to that person<br />* In a reply to a reply, that you\u2019re speaking to everyone upthread (AKA a <a href=\"https://indieweb.org/canoe\">https://indieweb.org/canoe</a>)<br />* When attributing something to someone (photo/post/cool thing by so-and-so), giving credit<br />* Distinguish a person (or something that can be followed) from \u201cjust\u201d a site<br />* For all the above, notifying someone accordingly<br /><br />Some ideas:<br /><br />1. Ideally, if/when everyone has their own domain (where they receive Webmention notifications, and a feed you can follow), we can @-name their domain, which your auto-linker^2 should hyperlink accordingly, e.g.<br />* <a href=\"https://aaronparecki.com\">@aaronparecki.com</a> <a href=\"https://anomalily.net\">@anomalily.net</a> <a href=\"https://Martymcgui.re\">@Martymcgui.re</a>\u200e <a href=\"https://david.shanske.com\">@david.shanske.com</a> <a href=\"https://voxpelli.com\">@voxpelli.com</a> <a href=\"https://adactio.com\">@adactio.com</a> <a href=\"https://marcthiele.com\">@marcthiele.com</a> <a href=\"https://mxb.dev\">@mxb.dev</a><br /><br />These all look close enough to social media aliases/names that they\u2019re immediately recognizable as readable @-names, a good consideration when choosing a domain name.^3<br /><br />2. As a fallback (e.g. for non-@-domain-auto-linking destinations) we can use someone\u2019s plain domain (explicitly with https:), especially if their home page still has a stream or feed you can follow, or maybe if they don\u2019t receive homepage Webmentions (yet), e.g.:<br />* <a href=\"https://jacky.wtf/\">https://jacky.wtf/</a> <a href=\"https://tmichellemoore.com/\">https://tmichellemoore.com/</a> <a href=\"https://crowdersoup.com/\">https://crowdersoup.com/</a><br /><br />3. Some folks with personal sites have (for now) created separate Mastodon accounts (or installed an instance on a subdomain), and for them, we can reference their @-@ parenthetically after their domain, like:<br />* <a href=\"https://kevinmarks.com/\">https://kevinmarks.com/</a> (<a href=\"https://xoxo.zone/@kevinmarks\">@kevinmarks@xoxo.zone</a>), <a href=\"https://dangillmor.com/\">https://dangillmor.com/</a> (<a href=\"https://mastodon.social/@dangillmor\">@dangillmor@mastodon.social</a>), <a href=\"https://simonwillison.net/\">https://simonwillison.net/</a> (<a href=\"https://simonwillison.net/@simon\">@simon@simonwillison.net</a>) <br /><br />Rather than using social media silo @-names (except when explicitly replying to a silo), I\u2019m now experimenting with all three of these (1-3) instead, both to elevate people\u2019s IndieWeb identities, and for Mastodon viewers, provide a convenient way to follow @-@ addresses.<br /><br />If someone\u2019s homepage receives Webmentions, they will get notified when I @-mention them by domain.<br /><br />I recently implemented syntactic auto-linking of @-@ addresses like this:<br />* <a href=\"https://example.com/@user\">@user@example.com</a> --> <a href=\"https://example.com/@user\">https://example.com/@user</a><br />with a special case for @-domain@-domain to just link to the domain, e.g.:<br />* <a href=\"https://tantek.com\">@tantek.com@tantek.com</a> --> <a href=\"https://tantek.com/\">https://tantek.com/</a><br /><br />I also made a recent policy decision to auto-link all @-@ (and @-domain) mentions to https:, the reasoning being that identities on the web should be using https.<br />* Testing in production here: <a href=\"https://tantek.com/cassis.js\">https://tantek.com/cassis.js</a>, search for \"auto_link(\"<br /><br />Some questions: <br />* Does/do Mastodon (or other ActivityPub servers) notify people when you @-@ mention them in a post? How? Who\u2019s responsible for that?<br />* Will Bridgy Fed notify the servers (deliver to AP inboxes) of folks I merely @-@ mention (rather than explicit replies, reposts)? Should it?<br /><br />So many people are switching to using their personal domains to post (or at least a Mastodon account) that I no longer feel compelled to @-mention people\u2019s Twitter handles in posts, which feels refreshing. <br /><br />Now the fun part is experimenting and figuring out what combination of @-domain, plain domain, or @-@ mentions looks good, makes sense to people, and sends notifications to people the way they want to receive them.<br /><br />This is day 11 of #<span class=\"p-category\">100DaysOfIndieWeb</span> #<span class=\"p-category\">100Days</span>.<br /><br />\u2190 Day 10: <a href=\"https://tantek.com/2023/010/t2/build-use-services\">https://tantek.com/2023/010/t2/build-use-services</a><br />\u2192 \ud83d\udd2e<br /><br />^1 <a href=\"https://en.wikipedia.org/wiki/AT-AT\">https://en.wikipedia.org/wiki/AT-AT</a><br />^2 My <a href=\"https://tantek.com/github/cassis/blob/master/cassis.js\">https://tantek.com/github/cassis/blob/master/cassis.js</a> auto_link() function supports <a href=\"https://example.com\">@example.com</a> auto-linking, yours should too.<br />^3 <a href=\"https://tantek.com/2023/004/t1/choosing-domain-name-indieweb\">https://tantek.com/2023/004/t1/choosing-domain-name-indieweb</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": "34356128",
"_source": "1",
"_is_read": false
}
Morning everybody. This function is giving me fits, but I will continue tackling it this morning to get a working importer for scrobbles from Last FM as listen posts to my site. #indieweb
{
"type": "entry",
"author": {
"name": "@arush",
"url": "https://indieweb.social/@arush",
"photo": null
},
"url": "https://indieweb.social/@arush/109675897250658473",
"content": {
"html": "<p>Morning everybody. This function is giving me fits, but I will continue tackling it this morning to get a working importer for scrobbles from Last FM as listen posts to my site. <a href=\"https://indieweb.social/tags/indieweb\">#<span>indieweb</span></a></p>",
"text": "Morning everybody. This function is giving me fits, but I will continue tackling it this morning to get a working importer for scrobbles from Last FM as listen posts to my site. #indieweb"
},
"published": "2023-01-12T11:03:01+00:00",
"post-type": "note",
"_id": "34355010",
"_source": "7235",
"_is_read": false
}
One of the fun things about #IndieWeb notes & replies is that we're still figuring things out! Like how should we @ someone?
#socialMedia aliases (e.g. @Twitter) were obvious, with prior @-name usage on Flickr etc.
Now, some have a domain, or an @-@ (pronounced at-at, yes, just like the abbreviation for Imperial All Terrain Armored Transport^1 walkers), or some have both.
We can ask the questions of why do we @-someone? What are the use-cases?
* In a reply to a public post, clearly express that you’re speaking to that person
* In a reply to a reply, that you’re speaking to everyone upthread (AKA a https://indieweb.org/canoe)
* When attributing something to someone (photo/post/cool thing by so-and-so), giving credit
* For all the above, notifying someone accordingly
* Distinguish a person (or something that can be followed) from “just” a site
Some ideas:
1. Ideally, if/when everyone has their own domain (where they receive Webmention notifications, and a feed you can follow), we can @-name their domain, which your auto-linker^2 should hyperlink accordingly, e.g.
* @aaronparecki.com @anomalily.net @Martymcgui.re @david.shanske.com @snarfed.org @ben.thatmustbe.me
These all look close enough to social media aliases/names that they’re immediately recognizable as readable @-names, a good consideration when choosing a domain name.^3
2. As a fallback (e.g. for non-@-domain-auto-linking destinations) we can use someone’s plain domain (explicitly with https:), especially if their home page still has a stream or feed you can follow, or maybe if they don’t receive homepage Webmentions, e.g.:
* https://adactio.com https://marcthiele.com https://mxb.dev/
3. Some folks with personal sites have (for now) created separate Mastodon accounts (or an installed an instance on a subdomain), and for them, we can reference their @-@ parenthetically after their domain, like:
* https://kevinmarks.com/ (@kevinmarks@xoxo.zone), https://tmichellemoore.com/ (@tmichellemoore@mastodon.social), https://voxpelli.com/ (@voxpelli@mastodon.social), https://simonwillison.net/ (@simon@simonwillison.net)
Rather than using social media silo @-names (except when explicitly replying to a silo), I’m now experimenting with all three of these (1-3) instead, both to elevate people’s IndieWeb identities, and for Mastodon viewers, provide a convenient way to follow @-@ addresses.
If someone’s homepage receives Webmentions, they will get notified when I @-mention them by domain.
I also recently implemented syntactic auto-linking of @-@ addresses like this:
* @user@example.com --> http://example.com/@user
with a special case for @-domain@-domain to just link to the domain, e.g.:
* @tantek.com@tantek.com --> http://tantek.com/
I am considering switching these (as well as a plain @-domain) to auto-link to https: instead, the reasoning being we should expect that identities on the web should be using https.
Some questions:
* Does/do Mastodon (or other ActivityPub servers) notify people when you @-@ mention them in a post? How? Who’s responsibility is that?
* Will Bridgy Fed notify the servers (deliver to AP inboxes) of folks I merely @-@ mention (rather than explicit replies, reposts)? Should it?
So many people are switching to using their personal domains to post (or at least a Mastodon account) that I no longer feel compelled to @-mention people’s Twitter handles in posts, which feels refreshing.
Now the fun part is experimenting and figuring out what combination of @-domain, plain domain, or @-@ mentions looks good, makes sense to people, and sends notifications to people the way they want to receive them.
This is day 11 of #100DaysOfIndieWeb #100Days.
← Day 10: https://tantek.com/2023/010/t2/build-use-services
→ 🔮
^1 https://en.wikipedia.org/wiki/AT-AT
^2 My https://github.com/tantek/cassis/blob/master/cassis.js auto_link() function supports @example.com auto-linking, yours should too.
^3 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb
{
"type": "entry",
"published": "2023-01-11 23:59-0800",
"url": "http://tantek.com/2023/011/t1/indieweb-domain-at-mention",
"category": [
"IndieWeb",
"socialMedia",
"100DaysOfIndieWeb",
"100Days"
],
"content": {
"text": "One of the fun things about #IndieWeb notes & replies is that we're still figuring things out! Like how should we @ someone?\n\n#socialMedia aliases (e.g. @Twitter) were obvious, with prior @-name usage on Flickr etc.\n\nNow, some have a domain, or an @-@ (pronounced at-at, yes, just like the abbreviation for Imperial All Terrain Armored Transport^1 walkers), or some have both.\n\nWe can ask the questions of why do we @-someone? What are the use-cases?\n* In a reply to a public post, clearly express that you\u2019re speaking to that person\n* In a reply to a reply, that you\u2019re speaking to everyone upthread (AKA a https://indieweb.org/canoe)\n* When attributing something to someone (photo/post/cool thing by so-and-so), giving credit\n* For all the above, notifying someone accordingly\n* Distinguish a person (or something that can be followed) from \u201cjust\u201d a site\n\nSome ideas:\n\n1. Ideally, if/when everyone has their own domain (where they receive Webmention notifications, and a feed you can follow), we can @-name their domain, which your auto-linker^2 should hyperlink accordingly, e.g.\n* @aaronparecki.com @anomalily.net @Martymcgui.re\u200e @david.shanske.com @snarfed.org @ben.thatmustbe.me\n\nThese all look close enough to social media aliases/names that they\u2019re immediately recognizable as readable @-names, a good consideration when choosing a domain name.^3\n\n2. As a fallback (e.g. for non-@-domain-auto-linking destinations) we can use someone\u2019s plain domain (explicitly with https:), especially if their home page still has a stream or feed you can follow, or maybe if they don\u2019t receive homepage Webmentions, e.g.:\n* https://adactio.com https://marcthiele.com https://mxb.dev/\n\n3. Some folks with personal sites have (for now) created separate Mastodon accounts (or an installed an instance on a subdomain), and for them, we can reference their @-@ parenthetically after their domain, like:\n* https://kevinmarks.com/ (@kevinmarks@xoxo.zone), https://tmichellemoore.com/ (@tmichellemoore@mastodon.social), https://voxpelli.com/ (@voxpelli@mastodon.social), https://simonwillison.net/ (@simon@simonwillison.net)\n\nRather than using social media silo @-names (except when explicitly replying to a silo), I\u2019m now experimenting with all three of these (1-3) instead, both to elevate people\u2019s IndieWeb identities, and for Mastodon viewers, provide a convenient way to follow @-@ addresses.\n\nIf someone\u2019s homepage receives Webmentions, they will get notified when I @-mention them by domain.\n\nI also recently implemented syntactic auto-linking of @-@ addresses like this:\n* @user@example.com --> http://example.com/@user\nwith a special case for @-domain@-domain to just link to the domain, e.g.:\n* @tantek.com@tantek.com --> http://tantek.com/\n\nI am considering switching these (as well as a plain @-domain) to auto-link to https: instead, the reasoning being we should expect that identities on the web should be using https.\n\nSome questions: \n* Does/do Mastodon (or other ActivityPub servers) notify people when you @-@ mention them in a post? How? Who\u2019s responsibility is that?\n* Will Bridgy Fed notify the servers (deliver to AP inboxes) of folks I merely @-@ mention (rather than explicit replies, reposts)? Should it?\n\nSo many people are switching to using their personal domains to post (or at least a Mastodon account) that I no longer feel compelled to @-mention people\u2019s Twitter handles in posts, which feels refreshing. \n\nNow the fun part is experimenting and figuring out what combination of @-domain, plain domain, or @-@ mentions looks good, makes sense to people, and sends notifications to people the way they want to receive them.\n\nThis is day 11 of #100DaysOfIndieWeb #100Days.\n\n\u2190 Day 10: https://tantek.com/2023/010/t2/build-use-services\n\u2192 \ud83d\udd2e\n\n^1 https://en.wikipedia.org/wiki/AT-AT\n^2 My https://github.com/tantek/cassis/blob/master/cassis.js auto_link() function supports @example.com auto-linking, yours should too.\n^3 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb",
"html": "One of the fun things about #<span class=\"p-category\">IndieWeb</span> notes & replies is that we're still figuring things out! Like how should we @ someone?<br /><br />#<span class=\"p-category\">socialMedia</span> aliases (e.g. <a class=\"h-cassis-username\" href=\"https://twitter.com/Twitter\">@Twitter</a>) were obvious, with prior @-name usage on Flickr etc.<br /><br />Now, some have a domain, or an @-@ (pronounced at-at, yes, just like the abbreviation for Imperial All Terrain Armored Transport^1 walkers), or some have both.<br /><br />We can ask the questions of why do we @-someone? What are the use-cases?<br />* In a reply to a public post, clearly express that you\u2019re speaking to that person<br />* In a reply to a reply, that you\u2019re speaking to everyone upthread (AKA a <a href=\"https://indieweb.org/canoe\">https://indieweb.org/canoe</a>)<br />* When attributing something to someone (photo/post/cool thing by so-and-so), giving credit<br />* For all the above, notifying someone accordingly<br />* Distinguish a person (or something that can be followed) from \u201cjust\u201d a site<br /><br />Some ideas:<br /><br />1. Ideally, if/when everyone has their own domain (where they receive Webmention notifications, and a feed you can follow), we can @-name their domain, which your auto-linker^2 should hyperlink accordingly, e.g.<br />* <a href=\"http://aaronparecki.com\">@aaronparecki.com</a> <a href=\"http://anomalily.net\">@anomalily.net</a> <a href=\"http://Martymcgui.re\">@Martymcgui.re</a>\u200e <a href=\"http://david.shanske.com\">@david.shanske.com</a> <a href=\"http://snarfed.org\">@snarfed.org</a> <a href=\"http://ben.thatmustbe.me\">@ben.thatmustbe.me</a><br /><br />These all look close enough to social media aliases/names that they\u2019re immediately recognizable as readable @-names, a good consideration when choosing a domain name.^3<br /><br />2. As a fallback (e.g. for non-@-domain-auto-linking destinations) we can use someone\u2019s plain domain (explicitly with https:), especially if their home page still has a stream or feed you can follow, or maybe if they don\u2019t receive homepage Webmentions, e.g.:<br />* <a href=\"https://adactio.com\">https://adactio.com</a> <a href=\"https://marcthiele.com\">https://marcthiele.com</a> <a href=\"https://mxb.dev/\">https://mxb.dev/</a><br /><br />3. Some folks with personal sites have (for now) created separate Mastodon accounts (or an installed an instance on a subdomain), and for them, we can reference their @-@ parenthetically after their domain, like:<br />* <a href=\"https://kevinmarks.com/\">https://kevinmarks.com/</a> (<a href=\"https://xoxo.zone/@kevinmarks\">@kevinmarks@xoxo.zone</a>), <a href=\"https://tmichellemoore.com/\">https://tmichellemoore.com/</a> (<a href=\"https://mastodon.social/@tmichellemoore\">@tmichellemoore@mastodon.social</a>), <a href=\"https://voxpelli.com/\">https://voxpelli.com/</a> (<a href=\"https://mastodon.social/@voxpelli\">@voxpelli@mastodon.social</a>), <a href=\"https://simonwillison.net/\">https://simonwillison.net/</a> (<a href=\"https://simonwillison.net/@simon\">@simon@simonwillison.net</a>)<br /><br />Rather than using social media silo @-names (except when explicitly replying to a silo), I\u2019m now experimenting with all three of these (1-3) instead, both to elevate people\u2019s IndieWeb identities, and for Mastodon viewers, provide a convenient way to follow @-@ addresses.<br /><br />If someone\u2019s homepage receives Webmentions, they will get notified when I @-mention them by domain.<br /><br />I also recently implemented syntactic auto-linking of @-@ addresses like this:<br />* <a href=\"https://example.com/@user\">@user@example.com</a> --> <a href=\"http://example.com/@user\">http://example.com/@user</a><br />with a special case for @-domain@-domain to just link to the domain, e.g.:<br />* <a href=\"https://tantek.com\">@tantek.com@tantek.com</a> --> <a href=\"http://tantek.com/\">http://tantek.com/</a><br /><br />I am considering switching these (as well as a plain @-domain) to auto-link to https: instead, the reasoning being we should expect that identities on the web should be using https.<br /><br />Some questions: <br />* Does/do Mastodon (or other ActivityPub servers) notify people when you @-@ mention them in a post? How? Who\u2019s responsibility is that?<br />* Will Bridgy Fed notify the servers (deliver to AP inboxes) of folks I merely @-@ mention (rather than explicit replies, reposts)? Should it?<br /><br />So many people are switching to using their personal domains to post (or at least a Mastodon account) that I no longer feel compelled to @-mention people\u2019s Twitter handles in posts, which feels refreshing. <br /><br />Now the fun part is experimenting and figuring out what combination of @-domain, plain domain, or @-@ mentions looks good, makes sense to people, and sends notifications to people the way they want to receive them.<br /><br />This is day 11 of #<span class=\"p-category\">100DaysOfIndieWeb</span> #<span class=\"p-category\">100Days</span>.<br /><br />\u2190 Day 10: <a href=\"https://tantek.com/2023/010/t2/build-use-services\">https://tantek.com/2023/010/t2/build-use-services</a><br />\u2192 \ud83d\udd2e<br /><br />^1 <a href=\"https://en.wikipedia.org/wiki/AT-AT\">https://en.wikipedia.org/wiki/AT-AT</a><br />^2 My <a href=\"https://github.com/tantek/cassis/blob/master/cassis.js\">https://github.com/tantek/cassis/blob/master/cassis.js</a> auto_link() function supports <a href=\"http://example.com\">@example.com</a> auto-linking, yours should too.<br />^3 <a href=\"https://tantek.com/2023/004/t1/choosing-domain-name-indieweb\">https://tantek.com/2023/004/t1/choosing-domain-name-indieweb</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": "34354183",
"_source": "1",
"_is_read": false
}