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
}
k so in the interests of creating my own space online for content and participating in the #indieweb movement, i’ve built my little barebones shack of a website to hock my #horrorart both in print form and on #apparel
https://fady.wtf
i’m beyond excited about #blogging like it’s 2009. since i stopped streaming on #twitch i haven’t had a replacement outlet for my work and i’m so happy to have one again, and on my own ridiculous domain!
so thankful for the friends who have cheered me on 🖤
{
"type": "entry",
"author": {
"name": "@fady",
"url": "https://is.nota.live/@fady",
"photo": null
},
"url": "https://is.nota.live/@fady/109675111002635976",
"content": {
"html": "<p>k so in the interests of creating my own space online for content and participating in the <a href=\"https://is.nota.live/tags/indieweb\">#<span>indieweb</span></a> movement, i\u2019ve built my little barebones shack of a website to hock my <a href=\"https://is.nota.live/tags/horrorart\">#<span>horrorart</span></a> both in print form and on <a href=\"https://is.nota.live/tags/apparel\">#<span>apparel</span></a> </p><p><a href=\"https://fady.wtf\"><span>https://</span><span>fady.wtf</span><span></span></a> </p><p>i\u2019m beyond excited about <a href=\"https://is.nota.live/tags/blogging\">#<span>blogging</span></a> like it\u2019s 2009. since i stopped streaming on <a href=\"https://is.nota.live/tags/twitch\">#<span>twitch</span></a> i haven\u2019t had a replacement outlet for my work and i\u2019m so happy to have one again, and on my own ridiculous domain! </p><p>so thankful for the friends who have cheered me on \ud83d\udda4</p>",
"text": "k so in the interests of creating my own space online for content and participating in the #indieweb movement, i\u2019ve built my little barebones shack of a website to hock my #horrorart both in print form and on #apparel https://fady.wtf i\u2019m beyond excited about #blogging like it\u2019s 2009. since i stopped streaming on #twitch i haven\u2019t had a replacement outlet for my work and i\u2019m so happy to have one again, and on my own ridiculous domain! so thankful for the friends who have cheered me on \ud83d\udda4"
},
"published": "2023-01-12T07:43:04+00:00",
"post-type": "note",
"_id": "34351968",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "@CrowderSoup",
"url": "https://hachyderm.io/@CrowderSoup",
"photo": null
},
"url": "https://hachyderm.io/@CrowderSoup/109674450187794710",
"content": {
"html": "<p>Okay okay, I did it! I blogged about the `npm prune` command. <a href=\"https://hachyderm.io/tags/100daysofindieweb\">#<span>100daysofindieweb</span></a> is still going strong at day 6. <a href=\"https://hachyderm.io/tags/Indieweb\">#<span>Indieweb</span></a> </p><p><a href=\"https://crowdersoup.com/posts/projects/indieweb/100-days/day-6-npm-prune/\"><span>https://</span><span>crowdersoup.com/posts/projects</span><span>/indieweb/100-days/day-6-npm-prune/</span></a></p>",
"text": "Okay okay, I did it! I blogged about the `npm prune` command. #100daysofindieweb is still going strong at day 6. #Indieweb https://crowdersoup.com/posts/projects/indieweb/100-days/day-6-npm-prune/"
},
"published": "2023-01-12T04:55:00+00:00",
"post-type": "note",
"_id": "34350212",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "@jdzero",
"url": "https://indieweb.social/@jdzero",
"photo": null
},
"url": "https://indieweb.social/@jdzero/109673549312752839",
"content": {
"html": "<p>The Digital Native Myth</p><p><a href=\"https://www.jdzero.net/2023/01/09/the-digital-native-myth/\"><span>https://www.</span><span>jdzero.net/2023/01/09/the-digi</span><span>tal-native-myth/</span></a></p><p><a href=\"https://indieweb.social/tags/Education\">#<span>Education</span></a> <a href=\"https://indieweb.social/tags/Technology\">#<span>Technology</span></a> <a href=\"https://indieweb.social/tags/EdTech\">#<span>EdTech</span></a> <a href=\"https://indieweb.social/tags/IndieWeb\">#<span>IndieWeb</span></a> <a href=\"https://indieweb.social/tags/Blog\">#<span>Blog</span></a></p>",
"text": "The Digital Native Mythhttps://www.jdzero.net/2023/01/09/the-digital-native-myth/#Education #Technology #EdTech #IndieWeb #Blog"
},
"published": "2023-01-12T01:05:54+00:00",
"post-type": "note",
"_id": "34347396",
"_source": "7235",
"_is_read": false
}
Project Journal: If You See Something That Needs Fixing, Try to Fix It
Introduction
Today’s project journal is a memory of finding something that was wrong and reaching out to find a solution.
#100DaysofIndieWeb, #IndieWeb, #ProjectJournal, #ProjectManagement
Day 4 of 100
When I was an Instructional Techno
https://tmichellemoore.com/blog/project-journal-if-you-see-something-that-needs-fixing-try-to-fix-it/
#100DaysOfIndieWeb #IndieWeb #ProjectJournal #ProjectManagement
{
"type": "entry",
"author": {
"name": "@tmichellemoore",
"url": "https://mastodon.social/@tmichellemoore",
"photo": null
},
"url": "https://mastodon.social/@tmichellemoore/109673431507254226",
"content": {
"html": "<p>Project Journal: If You See Something That Needs Fixing, Try to Fix It</p><p>Introduction</p><p>Today\u2019s project journal is a memory of finding something that was wrong and reaching out to find a solution.</p><p><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><p>Day 4 of 100</p><p>When I was an Instructional Techno</p><p><a href=\"https://tmichellemoore.com/blog/project-journal-if-you-see-something-that-needs-fixing-try-to-fix-it/\"><span>https://</span><span>tmichellemoore.com/blog/projec</span><span>t-journal-if-you-see-something-that-needs-fixing-try-to-fix-it/</span></a></p><p><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: If You See Something That Needs Fixing, Try to Fix ItIntroductionToday\u2019s project journal is a memory of finding something that was wrong and reaching out to find a solution.#100DaysofIndieWeb, #IndieWeb, #ProjectJournal, #ProjectManagementDay 4 of 100When I was an Instructional Technohttps://tmichellemoore.com/blog/project-journal-if-you-see-something-that-needs-fixing-try-to-fix-it/#100DaysOfIndieWeb #IndieWeb #ProjectJournal #ProjectManagement"
},
"published": "2023-01-12T00:35:57+00:00",
"post-type": "note",
"_id": "34346926",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"published": "2023-01-11T14:11:00-08:00",
"url": "https://snarfed.org/2023-01-11_logs-as-end-user-ui",
"syndication": [
"https://twitter.com/schnarfed/status/1613299141496700928",
"https://fed.brid.gy/user/snarfed.org"
],
"name": "Logs as end user UI",
"content": {
"text": "A long time ago, I decided to show Bridgy\u2018s raw logs to its end users. Like, raw logs. HTTP requests, database reads and writes, JSON objects, stack traces, etc. It\u2019s an unusual UI feature, but it\u2019s been an unqualified success, enough that when I built Bridgy Fed, I immediately included it and never looked back.\nWhenever Bridgy does something nontrivial \u2013 poll a social network account, send a webmention, publish a post \u2013 I generally include a link to the server logs for that operation. Here\u2019s an example, a series of timestamped plain text log messages from a poll of my Twitter account. They include initial config and parameters, account status, each individual Twitter API request, the results of those requests, how Bridgy interpreted them, HTTP requests to my web site, the subsequent actions Bridgy took and why, how the account\u2019s status changed, and when the next poll is scheduled for.\n Continue reading \u2192",
"html": "<p>\n <img src=\"https://snarfed.org/matrix.webp\" alt=\"matrix.webp\" /></p><img src=\"https://snarfed.org/matrix.webp\" alt=\"matrix.webp\" />\n<p>A long time ago, I decided to show <a href=\"https://brid.gy/\">Bridgy</a>\u2018s raw logs to its end users. Like, <em>raw</em> logs. HTTP requests, database reads and writes, JSON objects, stack traces, etc. It\u2019s an unusual UI feature, but it\u2019s been an unqualified success, enough that when I built <a href=\"https://fed.brid.gy/\">Bridgy Fed</a>, I immediately included it and never looked back.</p>\n<p>Whenever Bridgy does something nontrivial \u2013 <a href=\"https://brid.gy/about#checks+your+accounts\">poll a social network account</a>, <a href=\"https://brid.gy/about#which\">send a webmention</a>, <a href=\"https://brid.gy/about#publishing\">publish a post</a> \u2013 I generally include a link to the server logs for that operation. <a href=\"https://snarfed.org/bridgy-poll-log.png\">Here\u2019s an example</a>, a series of timestamped plain text log messages from a poll of my Twitter account. They include initial config and parameters, account status, each individual Twitter API request, the results of those requests, how Bridgy interpreted them, HTTP requests to my web site, the subsequent actions Bridgy took and why, how the account\u2019s status changed, and when the next poll is scheduled for.\n <a href=\"https://snarfed.org/2023-01-11_logs-as-end-user-ui#more-48949\">Continue reading <span>\u2192</span></a></p>"
},
"author": {
"type": "card",
"name": "Ryan Barrett",
"url": "https://snarfed.org/",
"photo": "https://secure.gravatar.com/avatar/947b5f3f323da0ef785b6f02d9c265d6?s=96&d=blank&r=g"
},
"post-type": "article",
"_id": "34344360",
"_source": "3",
"_is_read": false
}
Disabling notifications from all my corporate social accounts, while leaving them on for Fediverse social accounts: an accidental stroke of genius 
It helps me prioritize where I truly want to spend my time 
#IndieWeb
{
"type": "entry",
"author": {
"name": "@josh",
"url": "https://josh.tel/@josh",
"photo": null
},
"url": "https://josh.tel/@josh/109672351436464142",
"content": {
"html": "<p>Disabling notifications from all my corporate social accounts, while leaving them on for Fediverse social accounts: an accidental stroke of genius <img alt=\":blobcatmaths:\" height=\"16\" src=\"https://files.mastodon.social/cache/custom_emojis/images/000/441/678/original/0c2192664d0c125d.png\" title=\":blobcatmaths:\" width=\"16\" /></p><p>It helps me prioritize where I truly want to spend my time <img alt=\":fedi:\" height=\"16\" src=\"https://files.mastodon.social/cache/custom_emojis/images/000/484/889/original/deb4552c6181a8b5.png\" title=\":fedi:\" width=\"16\" /><a href=\"https://josh.tel/tags/IndieWeb\">#<span>IndieWeb</span></a></p>",
"text": "Disabling notifications from all my corporate social accounts, while leaving them on for Fediverse social accounts: an accidental stroke of genius It helps me prioritize where I truly want to spend my time #IndieWeb"
},
"published": "2023-01-11T20:01:16+00:00",
"post-type": "note",
"_id": "34341324",
"_source": "7235",
"_is_read": false
}
@hrbf thank you and I appreciate it!
Still haven’t heard back from #tumblr customer support, after 8 days. I won’t be going back, but I’m hoping to at least get back my content.
I’ve decided to move forward with a flat file CMS for my personal website and I’m currently leaning towards @getkirby (old favorite of mine) or @eleventy
I see there are good enough options for both to get some #IndieWeb goodness going (e.g. webmentions).
What do you think?
{
"type": "entry",
"author": {
"name": "@rtud",
"url": "https://mastodon.social/@rtud",
"photo": null
},
"url": "https://mastodon.social/@rtud/109672150260826815",
"content": {
"html": "<p><span class=\"h-card\"><a class=\"u-url\" href=\"https://mastodon.social/@hrbf\">@<span>hrbf</span></a></span> thank you and I appreciate it!</p><p>Still haven\u2019t heard back from <a href=\"https://mastodon.social/tags/tumblr\">#<span>tumblr</span></a> customer support, after 8 days. I won\u2019t be going back, but I\u2019m hoping to at least get back my content.</p><p>I\u2019ve decided to move forward with a flat file CMS for my personal website and I\u2019m currently leaning towards <span class=\"h-card\"><a class=\"u-url\" href=\"https://mastodon.social/@getkirby\">@<span>getkirby</span></a></span> (old favorite of mine) or <span class=\"h-card\"><a class=\"u-url\" href=\"https://fosstodon.org/@eleventy\">@<span>eleventy</span></a></span></p><p>I see there are good enough options for both to get some <a href=\"https://mastodon.social/tags/IndieWeb\">#<span>IndieWeb</span></a> goodness going (e.g. webmentions).</p><p>What do you think?</p>",
"text": "@hrbf thank you and I appreciate it!Still haven\u2019t heard back from #tumblr customer support, after 8 days. I won\u2019t be going back, but I\u2019m hoping to at least get back my content.I\u2019ve decided to move forward with a flat file CMS for my personal website and I\u2019m currently leaning towards @getkirby (old favorite of mine) or @eleventyI see there are good enough options for both to get some #IndieWeb goodness going (e.g. webmentions).What do you think?"
},
"published": "2023-01-11T19:10:06+00:00",
"post-type": "note",
"_id": "34340620",
"_source": "7235",
"_is_read": false
}
The past, present and future of blogs.
{
"type": "entry",
"published": "2023-01-11T17:54:25Z",
"url": "https://adactio.com/links/19823",
"category": [
"blogs",
"blogging",
"indieweb",
"personal",
"publishing",
"silos",
"writing",
"sharing"
],
"bookmark-of": [
"https://cdevroe.com/2023/01/11/blogging-is-alive"
],
"content": {
"text": "Colin Devroe - Blogging is alive and well\n\n\n\nThe past, present and future of blogs.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://cdevroe.com/2023/01/11/blogging-is-alive\">\nColin Devroe - Blogging is alive and well\n</a>\n</h3>\n\n<p>The past, present and future of blogs.</p>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "bookmark",
"_id": "34339529",
"_source": "2",
"_is_read": false
}
Thinking about this post on "permanence" with #SocialMedia / #IndieWeb / #SelfHosting (for things that you *want* to keep permanent, anyway), balancing questions like are you going to outlive Facebook or the other way around, etc.
https://hyperborea.org/journal/2019/11/online-permanence/
I still think an "export to static site" option should be standard on any CMS as an exit strategy (on top of actual data portability) for cases where you no longer have the resources, time, inclination, etc. to maintain it.
{
"type": "entry",
"author": {
"name": "@KelsonV",
"url": "https://wandering.shop/@KelsonV",
"photo": null
},
"url": "https://wandering.shop/@KelsonV/109671921890123042",
"content": {
"html": "<p>Thinking about this post on \"permanence\" with <a href=\"https://wandering.shop/tags/SocialMedia\">#<span>SocialMedia</span></a> / <a href=\"https://wandering.shop/tags/IndieWeb\">#<span>IndieWeb</span></a> / <a href=\"https://wandering.shop/tags/SelfHosting\">#<span>SelfHosting</span></a> (for things that you *want* to keep permanent, anyway), balancing questions like are you going to outlive Facebook or the other way around, etc.</p><p><a href=\"https://hyperborea.org/journal/2019/11/online-permanence/\"><span>https://</span><span>hyperborea.org/journal/2019/11</span><span>/online-permanence/</span></a></p><p>I still think an \"export to static site\" option should be standard on any CMS as an exit strategy (on top of actual data portability) for cases where you no longer have the resources, time, inclination, etc. to maintain it.</p>",
"text": "Thinking about this post on \"permanence\" with #SocialMedia / #IndieWeb / #SelfHosting (for things that you *want* to keep permanent, anyway), balancing questions like are you going to outlive Facebook or the other way around, etc.https://hyperborea.org/journal/2019/11/online-permanence/I still think an \"export to static site\" option should be standard on any CMS as an exit strategy (on top of actual data portability) for cases where you no longer have the resources, time, inclination, etc. to maintain it."
},
"published": "2023-01-11T18:12:02+00:00",
"post-type": "note",
"_id": "34339191",
"_source": "7235",
"_is_read": false
}
@rozie @miklo Rozdzielmy tutaj zwiększanie zasięgu rozumiane jak w publikacjach naukowych: cytujesz, dajesz przypis, treść może dotrzeć w miejsca, w które inaczej by nie dotarła, od zwiększania zasięgu w sensie algorytmu / systemu informatycznego napędzającego sieci społecznościowe.
Nieporozumienia mogą się brać imo z tego, że różne rzeczy mamy na myśli, pisząc "zwiększanie zasięgu".
Poinformowanie autora załatwia już #indieweb, #wordpress (ping back) czy wzmiankowanie w #ActivityPub/#Mastodon
{
"type": "entry",
"author": {
"name": "@m0bi13",
"url": "https://mastodon.social/@m0bi13",
"photo": null
},
"url": "https://mastodon.social/@m0bi13/109671642573468496",
"content": {
"html": "<p><span class=\"h-card\"><a class=\"u-url\" href=\"https://mastodon.online/@rozie\">@<span>rozie</span></a></span> <span class=\"h-card\"><a class=\"u-url\" href=\"https://soc.citizen4.eu/profile/miklo\">@<span>miklo</span></a></span> Rozdzielmy tutaj zwi\u0119kszanie zasi\u0119gu rozumiane jak w publikacjach naukowych: cytujesz, dajesz przypis, tre\u015b\u0107 mo\u017ce dotrze\u0107 w miejsca, w kt\u00f3re inaczej by nie dotar\u0142a, od zwi\u0119kszania zasi\u0119gu w sensie algorytmu / systemu informatycznego nap\u0119dzaj\u0105cego sieci spo\u0142eczno\u015bciowe.</p><p>Nieporozumienia mog\u0105 si\u0119 bra\u0107 imo z tego, \u017ce r\u00f3\u017cne rzeczy mamy na my\u015bli, pisz\u0105c \"zwi\u0119kszanie zasi\u0119gu\".</p><p>Poinformowanie autora za\u0142atwia ju\u017c <a href=\"https://mastodon.social/tags/indieweb\">#<span>indieweb</span></a>, <a href=\"https://mastodon.social/tags/wordpress\">#<span>wordpress</span></a> (ping back) czy wzmiankowanie w <a href=\"https://mastodon.social/tags/ActivityPub\">#<span>ActivityPub</span></a>/#Mastodon</p>",
"text": "@rozie @miklo Rozdzielmy tutaj zwi\u0119kszanie zasi\u0119gu rozumiane jak w publikacjach naukowych: cytujesz, dajesz przypis, tre\u015b\u0107 mo\u017ce dotrze\u0107 w miejsca, w kt\u00f3re inaczej by nie dotar\u0142a, od zwi\u0119kszania zasi\u0119gu w sensie algorytmu / systemu informatycznego nap\u0119dzaj\u0105cego sieci spo\u0142eczno\u015bciowe.Nieporozumienia mog\u0105 si\u0119 bra\u0107 imo z tego, \u017ce r\u00f3\u017cne rzeczy mamy na my\u015bli, pisz\u0105c \"zwi\u0119kszanie zasi\u0119gu\".Poinformowanie autora za\u0142atwia ju\u017c #indieweb, #wordpress (ping back) czy wzmiankowanie w #ActivityPub/#Mastodon"
},
"published": "2023-01-11T17:01:00+00:00",
"post-type": "note",
"_id": "34337713",
"_source": "7235",
"_is_read": false
}
Can’t shake a comment that someone liked Micro.blog but it didn’t have many features. Blogs, themes, plug-ins, social network, podcast hosting, read-later bookmarks, cross-posts, archiving, highlights, email newsletters, bookshelves, IndieWeb, fediverse… Missing: marketing.
{
"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/11/cant-shake-a.html",
"content": {
"html": "<p>Can\u2019t shake a comment that someone liked Micro.blog but it didn\u2019t have many features. Blogs, themes, plug-ins, social network, podcast hosting, read-later bookmarks, cross-posts, archiving, highlights, email newsletters, bookshelves, IndieWeb, fediverse\u2026 Missing: marketing.</p>",
"text": "Can\u2019t shake a comment that someone liked Micro.blog but it didn\u2019t have many features. Blogs, themes, plug-ins, social network, podcast hosting, read-later bookmarks, cross-posts, archiving, highlights, email newsletters, bookshelves, IndieWeb, fediverse\u2026 Missing: marketing."
},
"published": "2023-01-11T09:14:57-06:00",
"post-type": "note",
"_id": "34336722",
"_source": "12",
"_is_read": false
}
Added two new characters to my kinning red flags, Dr. Horrible, and Rick Sanchez
#IndieWeb
https://www.vzqk50.com/blog/mens-kinning-red-flags/#dr-horrible
{
"type": "entry",
"author": {
"name": "@ApisNecros",
"url": "https://ioc.exchange/@ApisNecros",
"photo": null
},
"url": "https://ioc.exchange/@ApisNecros/109671430320940204",
"content": {
"html": "<p>Added two new characters to my kinning red flags, Dr. Horrible, and Rick Sanchez</p><p><a href=\"https://ioc.exchange/tags/IndieWeb\">#<span>IndieWeb</span></a> <br /><a href=\"https://www.vzqk50.com/blog/mens-kinning-red-flags/#dr-horrible\"><span>https://www.</span><span>vzqk50.com/blog/mens-kinning-r</span><span>ed-flags/#dr-horrible</span></a></p>",
"text": "Added two new characters to my kinning red flags, Dr. Horrible, and Rick Sanchez#IndieWeb \nhttps://www.vzqk50.com/blog/mens-kinning-red-flags/#dr-horrible"
},
"published": "2023-01-11T16:07:01+00:00",
"post-type": "note",
"_id": "34336167",
"_source": "7235",
"_is_read": false
}
Once you have a domain^1, and connect it to an #IndieWeb service like https://micro.blog, or a https://indieweb.org/CMS on https://indieweb.org/web_hosting, you can focus^2 on your writing.
Or if you enjoy #webDevelopment and want to build (option three^3), use developer services to more rapidly add IndieWeb building blocks^4 to your site so you too can focus on creating & owning your content^5.
Here are some of the most common and popular developer services:
1. Webmention sending: https://webmention.app/ by https://remysharp.com/ (@rem@front-end.social), or https://mention.tech/ by https://kevinmarks.com/ (@kevinmarks@xoxo.zone)
2. Webmention receiving: https://webmention.io/ (I use this) by https://aaronparecki.com/ or https://webmention.herokuapp.com/ by https://voxpelli.com/ (@voxpelli@mastodon.social)
3. POSSE & backfeed: https://brid.gy/ by Ryan of https://snarfed.org/ (@schnarfed)
4. ActivityPub federating: https://fed.brid.gy/ also by Ryan. More on Bridgy & Bridgy Fed^6.
Using a developer service to support IndieWeb protocols saves you time. You can also contribute to the community by filing suggestions for improvements, or participating on their GitHub repositories.
If you prefer that your site not depend on any external services, you can do that too.
Most of the above services are also open source that you can install and fully manage yourself. For example:
* Webmention installable services: https://indieweb.org/Webmention#Publisher_Services
Another option is to use one of many open source libraries to more rapidly implement support for IndieWeb standards^7. The wiki pages for each standard list libraries in a variety of programming languages, e.g.:
* https://indieweb.org/Webmention-developer#Libraries
If you choose the path of installing or building something new with libraries or by directly implementing an IndieWeb standard, be sure to test your implementation with its test suite, e.g.:
* https://webmention.rocks/
As a web developer, you can choose how much of your #IndieWeb support you want to implement yourself (and time to invest) vs build on the services, libraries, and other open source that the community has produced and is actively supporting.
This is day 10 of #100DaysOfIndieWeb #100Days.
← Day 9: https://tantek.com/2023/009/t2/edit-reply-comment-update
→ 🔮
^1 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb
^2 https://tantek.com/2023/005/t3/indieweb-simpler-approach
^3 https://tantek.com/2023/003/t1/indieweb-path-chosen-why
^4 https://indieweb.org/building_blocks
^5 https://tantek.com/2023/001/t1/own-your-notes
^6 https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed
^7 https://spec.indieweb.org/
{
"type": "entry",
"published": "2023-01-10 23:59-0800",
"url": "http://tantek.com/2023/010/t2/build-use-services",
"category": [
"IndieWeb",
"webDevelopment",
"100DaysOfIndieWeb",
"100Days"
],
"content": {
"text": "Once you have a domain^1, and connect it to an #IndieWeb service like https://micro.blog, or a https://indieweb.org/CMS on https://indieweb.org/web_hosting, you can focus^2 on your writing.\n\nOr if you enjoy #webDevelopment and want to build (option three^3), use developer services to more rapidly add IndieWeb building blocks^4 to your site so you too can focus on creating & owning your content^5.\n\nHere are some of the most common and popular developer services:\n1. Webmention sending: https://webmention.app/ by https://remysharp.com/ (@rem@front-end.social), or https://mention.tech/ by https://kevinmarks.com/ (@kevinmarks@xoxo.zone)\n2. Webmention receiving: https://webmention.io/ (I use this) by https://aaronparecki.com/ or https://webmention.herokuapp.com/ by https://voxpelli.com/ (@voxpelli@mastodon.social) \n3. POSSE & backfeed: https://brid.gy/ by Ryan of https://snarfed.org/ (@schnarfed)\n4. ActivityPub federating: https://fed.brid.gy/ also by Ryan. More on Bridgy & Bridgy Fed^6.\n\nUsing a developer service to support IndieWeb protocols saves you time. You can also contribute to the community by filing suggestions for improvements, or participating on their GitHub repositories.\n\nIf you prefer that your site not depend on any external services, you can do that too.\n\nMost of the above services are also open source that you can install and fully manage yourself. For example:\n* Webmention installable services: https://indieweb.org/Webmention#Publisher_Services\n\nAnother option is to use one of many open source libraries to more rapidly implement support for IndieWeb standards^7. The wiki pages for each standard list libraries in a variety of programming languages, e.g.:\n* https://indieweb.org/Webmention-developer#Libraries\n\nIf you choose the path of installing or building something new with libraries or by directly implementing an IndieWeb standard, be sure to test your implementation with its test suite, e.g.:\n* https://webmention.rocks/\n\nAs a web developer, you can choose how much of your #IndieWeb support you want to implement yourself (and time to invest) vs build on the services, libraries, and other open source that the community has produced and is actively supporting.\n\nThis is day 10 of #100DaysOfIndieWeb #100Days.\n\n\u2190 Day 9: https://tantek.com/2023/009/t2/edit-reply-comment-update\n\u2192 \ud83d\udd2e\n\n^1 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb\n^2 https://tantek.com/2023/005/t3/indieweb-simpler-approach\n^3 https://tantek.com/2023/003/t1/indieweb-path-chosen-why\n^4 https://indieweb.org/building_blocks\n^5 https://tantek.com/2023/001/t1/own-your-notes\n^6 https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed\n^7 https://spec.indieweb.org/",
"html": "Once you have a domain^1, and connect it to an #<span class=\"p-category\">IndieWeb</span> service like <a href=\"https://micro.blog\">https://micro.blog</a>, or a <a href=\"https://indieweb.org/CMS\">https://indieweb.org/CMS</a> on <a href=\"https://indieweb.org/web_hosting\">https://indieweb.org/web_hosting</a>, you can focus^2 on your writing.<br /><br />Or if you enjoy #<span class=\"p-category\">webDevelopment</span> and want to build (option three^3), use developer services to more rapidly add IndieWeb building blocks^4 to your site so you too can focus on creating & owning your content^5.<br /><br />Here are some of the most common and popular developer services:<br />1. Webmention sending: <a href=\"https://webmention.app/\">https://webmention.app/</a> by <a href=\"https://remysharp.com/\">https://remysharp.com/</a> (<a class=\"h-cassis-username\" href=\"https://twitter.com/rem@front\">@rem@front</a>-<a href=\"http://end.social\">end.social</a>), or <a href=\"https://mention.tech/\">https://mention.tech/</a> by <a href=\"https://kevinmarks.com/\">https://kevinmarks.com/</a> (<a href=\"http://xoxo.zone/@kevinmarks\">@kevinmarks@xoxo.zone</a>)<br />2. Webmention receiving: <a href=\"https://webmention.io/\">https://webmention.io/</a> (I use this) by <a href=\"https://aaronparecki.com/\">https://aaronparecki.com/</a> or <a href=\"https://webmention.herokuapp.com/\">https://webmention.herokuapp.com/</a> by <a href=\"https://voxpelli.com/\">https://voxpelli.com/</a> (<a href=\"http://mastodon.social/@voxpelli\">@voxpelli@mastodon.social</a>) <br />3. POSSE & backfeed: <a href=\"https://brid.gy/\">https://brid.gy/</a> by Ryan of <a href=\"https://snarfed.org/\">https://snarfed.org/</a> (<a class=\"h-cassis-username\" href=\"https://twitter.com/schnarfed\">@schnarfed</a>)<br />4. ActivityPub federating: <a href=\"https://fed.brid.gy/\">https://fed.brid.gy/</a> also by Ryan. More on Bridgy & Bridgy Fed^6.<br /><br />Using a developer service to support IndieWeb protocols saves you time. You can also contribute to the community by filing suggestions for improvements, or participating on their GitHub repositories.<br /><br />If you prefer that your site not depend on any external services, you can do that too.<br /><br />Most of the above services are also open source that you can install and fully manage yourself. For example:<br />* Webmention installable services: <a href=\"https://indieweb.org/Webmention#Publisher_Services\">https://indieweb.org/Webmention#Publisher_Services</a><br /><br />Another option is to use one of many open source libraries to more rapidly implement support for IndieWeb standards^7. The wiki pages for each standard list libraries in a variety of programming languages, e.g.:<br />* <a href=\"https://indieweb.org/Webmention-developer#Libraries\">https://indieweb.org/Webmention-developer#Libraries</a><br /><br />If you choose the path of installing or building something new with libraries or by directly implementing an IndieWeb standard, be sure to test your implementation with its test suite, e.g.:<br />* <a href=\"https://webmention.rocks/\">https://webmention.rocks/</a><br /><br />As a web developer, you can choose how much of your #<span class=\"p-category\">IndieWeb</span> support you want to implement yourself (and time to invest) vs build on the services, libraries, and other open source that the community has produced and is actively supporting.<br /><br />This is day 10 of #<span class=\"p-category\">100DaysOfIndieWeb</span> #<span class=\"p-category\">100Days</span>.<br /><br />\u2190 Day 9: <a href=\"https://tantek.com/2023/009/t2/edit-reply-comment-update\">https://tantek.com/2023/009/t2/edit-reply-comment-update</a><br />\u2192 \ud83d\udd2e<br /><br />^1 <a href=\"https://tantek.com/2023/004/t1/choosing-domain-name-indieweb\">https://tantek.com/2023/004/t1/choosing-domain-name-indieweb</a><br />^2 <a href=\"https://tantek.com/2023/005/t3/indieweb-simpler-approach\">https://tantek.com/2023/005/t3/indieweb-simpler-approach</a><br />^3 <a href=\"https://tantek.com/2023/003/t1/indieweb-path-chosen-why\">https://tantek.com/2023/003/t1/indieweb-path-chosen-why</a><br />^4 <a href=\"https://indieweb.org/building_blocks\">https://indieweb.org/building_blocks</a><br />^5 <a href=\"https://tantek.com/2023/001/t1/own-your-notes\">https://tantek.com/2023/001/t1/own-your-notes</a><br />^6 <a href=\"https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed\">https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed</a><br />^7 <a href=\"https://spec.indieweb.org/\">https://spec.indieweb.org/</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": "34336157",
"_source": "1",
"_is_read": false
}
dear lord, if you MUST put white text on an only very slightly darker background, would it be too much to ask to beg you NOT to use a super-aliased pixel-based font, for the love of all that is holy? actually, look, #indieweb folks, can we please, PLEASE stop using pixel fonts for paragraphs of text altogether? readability is nobody's enemy AND it can look good, too. no, really.
{
"type": "entry",
"author": {
"name": "@evenstar",
"url": "https://mas.to/@evenstar",
"photo": null
},
"url": "https://mas.to/@evenstar/109670912167005349",
"content": {
"html": "<p>dear lord, if you MUST put white text on an only very slightly darker background, would it be too much to ask to beg you NOT to use a super-aliased pixel-based font, for the love of all that is holy? actually, look, <a href=\"https://mas.to/tags/indieweb\">#<span>indieweb</span></a> folks, can we please, PLEASE stop using pixel fonts for paragraphs of text altogether? readability is nobody's enemy AND it can look good, too. no, really.</p>",
"text": "dear lord, if you MUST put white text on an only very slightly darker background, would it be too much to ask to beg you NOT to use a super-aliased pixel-based font, for the love of all that is holy? actually, look, #indieweb folks, can we please, PLEASE stop using pixel fonts for paragraphs of text altogether? readability is nobody's enemy AND it can look good, too. no, really."
},
"published": "2023-01-11T13:55:15+00:00",
"post-type": "note",
"_id": "34333135",
"_source": "7235",
"_is_read": false
}
@OohDirectory Other reason I ask is because, back in the day (early 00s) when Netscape and Microsoft were embattled in a bitter browser war of increasing incompatibility (you might remember this), the community rallied around Web Standards. It became *the thing* to blog about Web Standards and a whole community flourished. It was multiplicative and wonderful.
I just wish there were more ways people could rally around #IndieWeb, which is spiritually the same community as before rising up again.
{
"type": "entry",
"author": {
"name": "@charlesroper",
"url": "https://indieweb.social/@charlesroper",
"photo": null
},
"url": "https://indieweb.social/@charlesroper/109670499905125154",
"content": {
"html": "<p><span class=\"h-card\"><a class=\"u-url\" href=\"https://mastodon.social/@OohDirectory\">@<span>OohDirectory</span></a></span> Other reason I ask is because, back in the day (early 00s) when Netscape and Microsoft were embattled in a bitter browser war of increasing incompatibility (you might remember this), the community rallied around Web Standards. It became *the thing* to blog about Web Standards and a whole community flourished. It was multiplicative and wonderful.</p><p>I just wish there were more ways people could rally around <a href=\"https://indieweb.social/tags/IndieWeb\">#<span>IndieWeb</span></a>, which is spiritually the same community as before rising up again.</p>",
"text": "@OohDirectory Other reason I ask is because, back in the day (early 00s) when Netscape and Microsoft were embattled in a bitter browser war of increasing incompatibility (you might remember this), the community rallied around Web Standards. It became *the thing* to blog about Web Standards and a whole community flourished. It was multiplicative and wonderful.I just wish there were more ways people could rally around #IndieWeb, which is spiritually the same community as before rising up again."
},
"published": "2023-01-11T12:10:24+00:00",
"post-type": "note",
"_id": "34330766",
"_source": "7235",
"_is_read": false
}
