š Six years ago today, the #IndieWeb Webmention protocol was published as a W3C REC 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 ...
tantek.com/t5Np1
{
"type": "entry",
"published": "2023-01-13T11:37:35+00:00",
"url": "https://twitter.com/t/status/1613862819799404546",
"content": {
"text": "\ud83c\udf89 Six years ago today, the #IndieWeb Webmention protocol was published as a W3C REC 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 ...\ntantek.com/t5Np1",
"html": "\ud83c\udf89 Six years ago today, the <a href=\"https://twitter.com/search?q=%23IndieWeb\">#IndieWeb</a> Webmention protocol was published as a W3C REC <a href=\"https://www.w3.org/TR/webmention/\">w3.org/TR/webmention/</a>\n\nA key social web building block, Webmention enabled peer-to-peer comments, likes, and other responses to be created, updated, and deleted ...\n<a href=\"https://tantek.com/t5Np1\">tantek.com/t5Np1</a>"
},
"author": {
"type": "card",
"name": "Tantek",
"url": "https://twitter.com/t",
"photo": "https://pbs.twimg.com/profile_images/423350922408767488/nlA_m2WH.jpeg"
},
"post-type": "note",
"_id": "34381452",
"_source": "2773"
}
š 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": "https://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": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "34381331",
"_source": "2460"
}
Are you practicing good oral hygiene during eternal Caturday?
{
"type": "entry",
"published": "2023-01-13T00:02:59-0500",
"url": "https://martymcgui.re/2023/01/13/000259/",
"category": [
"Caturday"
],
"video": [
"https://res.cloudinary.com/schmarty/video/upload/vc_h264/mmmgre/0d/41/68/14/a3670fdec0808bcbab0b74543973de0e15383a4577a681f47b208f07.mov"
],
"content": {
"text": "Are you practicing good oral hygiene during eternal Caturday?",
"html": "<p>Are you practicing good oral hygiene during eternal Caturday?</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "video",
"_id": "34377031",
"_source": "175"
}
{
"type": "entry",
"published": "2023-01-12T10:52:38-08:00",
"url": "https://beesbuzz.biz/blog/12693-In-defense-of-WebP",
"name": "In defense of WebP",
"author": {
"type": "card",
"name": "fluffy",
"url": "https://beesbuzz.biz/",
"photo": "https://beesbuzz.biz/static/headshot.jpg"
},
"post-type": "article",
"_id": "34365537",
"_source": "2778"
}
#NAFO is giving #Russia #Putin a hard time as they do the MOD Shuffle
We should be happy the Government has an Open Window Policy
{
"type": "entry",
"published": "2023-01-12T17:52:04+00:00",
"url": "https://twitter.com/jgmac1106/status/1613594676849672198",
"photo": [
"https://pbs.twimg.com/media/FmSjxb-XwAASXGu.jpg"
],
"content": {
"text": "#NAFO is giving #Russia #Putin a hard time as they do the MOD Shuffle\n\nWe should be happy the Government has an Open Window Policy",
"html": "<a href=\"https://twitter.com/search?q=%23NAFO\">#NAFO</a> is giving <a href=\"https://twitter.com/search?q=%23Russia\">#Russia</a> <a href=\"https://twitter.com/search?q=%23Putin\">#Putin</a> a hard time as they do the MOD Shuffle\n\nWe should be happy the Government has an Open Window Policy"
},
"author": {
"type": "card",
"name": "jgregorymcverry.com",
"url": "https://twitter.com/jgmac1106",
"photo": "https://pbs.twimg.com/profile_images/1586874242913734658/3GMcjnTC.jpg"
},
"post-type": "photo",
"_id": "34364073",
"_source": "2773"
}
Excited to give this talk today on #CMMC at @dcodethegov Nexus Accelerate event
We will discuss NIST-SP-800-171 requirements and CMMC
Impact of DoD's announcement they will file a draft rule change for CFR 32 and 48 and not an interim rule
Finally opportunities for #govcon
{
"type": "entry",
"published": "2023-01-12T16:18:30+00:00",
"url": "https://twitter.com/jgmac1106/status/1613571126935830528",
"photo": [
"https://pbs.twimg.com/media/FmSNe9VX0Ak-4xB.jpg"
],
"content": {
"text": "Excited to give this talk today on #CMMC at @dcodethegov Nexus Accelerate event \n\nWe will discuss NIST-SP-800-171 requirements and CMMC\n\nImpact of DoD's announcement they will file a draft rule change for CFR 32 and 48 and not an interim rule \n\nFinally opportunities for #govcon",
"html": "Excited to give this talk today on <a href=\"https://twitter.com/search?q=%23CMMC\">#CMMC</a> at <a href=\"https://twitter.com/dcodethegov\">@dcodethegov</a> Nexus Accelerate event \n\nWe will discuss NIST-SP-800-171 requirements and CMMC\n\nImpact of DoD's announcement they will file a draft rule change for CFR 32 and 48 and not an interim rule \n\nFinally opportunities for <a href=\"https://twitter.com/search?q=%23govcon\">#govcon</a>"
},
"author": {
"type": "card",
"name": "jgregorymcverry.com",
"url": "https://twitter.com/jgmac1106",
"photo": "https://pbs.twimg.com/profile_images/1586874242913734658/3GMcjnTC.jpg"
},
"post-type": "photo",
"_id": "34362352",
"_source": "2773"
}
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": "https://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": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "34356301",
"_source": "2460"
}
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 @-@ ...
tantek.com/t5No1
{
"type": "entry",
"published": "2023-01-12T11:22:24+00:00",
"url": "https://twitter.com/t/status/1613496611149352960",
"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 @-@ ...\ntantek.com/t5No1",
"html": "One of the fun things about <a href=\"https://twitter.com/search?q=%23IndieWeb\">#IndieWeb</a> notes & replies is that how we post is actively evolving! Like how should we @ someone?\n\n<a href=\"https://twitter.com/search?q=%23socialMedia\">#socialMedia</a> aliases (e.g. <a href=\"https://twitter.com/Twitter\">@Twitter</a>) were obvious, with prior @-name usage on Flickr etc.\n\nNow, some have a domain, or an @-@ ...\n<a href=\"https://tantek.com/t5No1\">tantek.com/t5No1</a>"
},
"author": {
"type": "card",
"name": "Tantek",
"url": "https://twitter.com/t",
"photo": "https://pbs.twimg.com/profile_images/423350922408767488/nlA_m2WH.jpeg"
},
"post-type": "note",
"_id": "34355415",
"_source": "2773"
}
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 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 also made a policy decision to auto-link all @-@ (and @-domain) mentions to https:, the reasoning being 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": "https://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 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 also made a policy decision to auto-link all @-@ (and @-domain) mentions to https:, the reasoning being 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=\"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://snarfed.org\">@snarfed.org</a> <a href=\"https://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 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 also made a policy decision to auto-link all @-@ (and @-domain) mentions to https:, the reasoning being 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=\"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": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "34354274",
"_source": "2460"
}
{
"type": "entry",
"published": "2023-01-11T23:55:28-08:00",
"url": "https://beesbuzz.biz/blog/2389-Electric-vehicles-in-2023",
"name": "Electric vehicles in 2023",
"author": {
"type": "card",
"name": "fluffy",
"url": "https://beesbuzz.biz/",
"photo": "https://beesbuzz.biz/static/headshot.jpg"
},
"post-type": "article",
"_id": "34353219",
"_source": "2778"
}
Are you positioned for success during eternal Caturday?
{
"type": "entry",
"published": "2023-01-12T00:03:08-0500",
"url": "https://martymcgui.re/2023/01/12/000308/",
"category": [
"Caturday"
],
"video": [
"https://res.cloudinary.com/schmarty/video/upload/vc_h264/mmmgre/ef/a8/12/2d/84153f126bb5cec53f9e9b4f72d84a9dc381e864bfbe45c3e0c56bce.mov"
],
"content": {
"text": "Are you positioned for success during eternal Caturday?",
"html": "<p>Are you positioned for success during eternal Caturday?</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "video",
"_id": "34351387",
"_source": "175"
}
Hey, San Diego! We All We Got is doing another grocery distribution this Saturday, January 14th 12:30pm until supplies run out. Location: Azalea Park (corner of Poplar & Violet). weallwegotsd.com/distro
No proof of income or ID is necessary to receive food. Solidarity, not charity.
Sign up to volunteer: signup.com/go/VFTCiVs
{
"type": "entry",
"published": "2023-01-11 18:23-0800",
"url": "https://gregorlove.com/2023/01/wawg-distribution/",
"content": {
"text": "Hey, San Diego! We All We Got is doing another grocery distribution this Saturday, January 14th 12:30pm until supplies run out. Location: Azalea Park (corner of Poplar & Violet). weallwegotsd.com/distro\n\nNo proof of income or ID is necessary to receive food. Solidarity, not charity.\n\nSign up to volunteer: signup.com/go/VFTCiVs",
"html": "<p>Hey, San Diego! We All We Got is doing another grocery distribution this Saturday, January 14th 12:30pm until supplies run out. Location: Azalea Park (corner of Poplar & Violet). <a href=\"https://www.weallwegotsd.com/distro\">weallwegotsd.com/distro</a></p>\n\n<p>No proof of income or ID is necessary to receive food. Solidarity, not charity.</p>\n\n<p>Sign up to volunteer: <a href=\"https://signup.com/go/VFTCiVs\">signup.com/go/VFTCiVs</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": "34350357",
"_source": "95"
}
A #NAFO fella for an OG Guitar hero.
If you have never listened to Jeff Beck's Wired do so tonight.
Meant to pluck the strings in the nursery of stars.
{
"type": "entry",
"published": "2023-01-12T00:54:50+00:00",
"url": "https://twitter.com/jgmac1106/status/1613338682131357698",
"photo": [
"https://pbs.twimg.com/media/FmO68XkWQAA6Vl6.jpg"
],
"content": {
"text": "A #NAFO fella for an OG Guitar hero.\n\nIf you have never listened to Jeff Beck's Wired do so tonight.\n\nMeant to pluck the strings in the nursery of stars.",
"html": "A <a href=\"https://twitter.com/search?q=%23NAFO\">#NAFO</a> fella for an OG Guitar hero.\n\nIf you have never listened to Jeff Beck's Wired do so tonight.\n\nMeant to pluck the strings in the nursery of stars."
},
"author": {
"type": "card",
"name": "jgregorymcverry.com",
"url": "https://twitter.com/jgmac1106",
"photo": "https://pbs.twimg.com/profile_images/1586874242913734658/3GMcjnTC.jpg"
},
"post-type": "photo",
"_id": "34347270",
"_source": "2773"
}
{
"type": "entry",
"published": "2023-01-11T23:11:39+00:00",
"url": "https://twitter.com/anomalily/status/1613312714537054208",
"video": [
"https://video.twimg.com/ext_tw_video/1613312678591877126/pu/vid/746x720/SM-7AigxbGYvo_We.mp4?tag=12"
],
"content": {
"text": "\u26f8\u26f8\u26f8"
},
"author": {
"type": "card",
"name": "Lillian Karabaic",
"url": "https://twitter.com/anomalily",
"photo": "https://pbs.twimg.com/profile_images/1455236306162761732/jPv9ROKG.jpg"
},
"post-type": "video",
"_id": "34345537",
"_source": "2773"
}
NEW: Musk emailed Twitter saying most of his Tesla work was completed this wknd & heās available to discuss āurgentā product needs. All changes have to be signed off by him personally. āWe are going to agonize until we achieve as close to the perfect product as possibleā
{
"type": "entry",
"published": "2023-01-11T21:48:59+00:00",
"url": "https://twitter.com/ZoeSchiffer/status/1613291907886747649",
"content": {
"text": "NEW: Musk emailed Twitter saying most of his Tesla work was completed this wknd & he\u2019s available to discuss \u201curgent\u201d product needs. All changes have to be signed off by him personally. \u201cWe are going to agonize until we achieve as close to the perfect product as possible\u201d",
"html": "NEW: Musk emailed Twitter saying most of his Tesla work was completed this wknd & he\u2019s available to discuss \u201curgent\u201d product needs. All changes have to be signed off by him personally. \u201cWe are going to agonize until we achieve as close to the perfect product as possible\u201d"
},
"author": {
"type": "card",
"name": "Zo\u00eb Schiffer",
"url": "https://twitter.com/ZoeSchiffer",
"photo": "https://pbs.twimg.com/profile_images/1564799885794086914/ZU6qMT_n.jpg"
},
"post-type": "note",
"_id": "34343797",
"_source": "2773"
}
Hi #PortfolioDay I am a fake artist just trying to teach kids to make cool webby stuff and cut and paste my way to insignificance helping #NAFO raise money for #Ukraineļø
Watching how important art is to those facing the horrors of war helps restore my faith in humanity
{
"type": "entry",
"published": "2023-01-11T17:32:28+00:00",
"url": "https://twitter.com/jgmac1106/status/1613227357258780672",
"photo": [
"https://pbs.twimg.com/media/FmNU6iqXECMgG8e.jpg",
"https://pbs.twimg.com/media/FmNU8J9XEAk0Tam.jpg",
"https://pbs.twimg.com/media/FmNVDqCXEBcI03C.jpg",
"https://pbs.twimg.com/media/FmNVZ9kXEBw2DAX.jpg"
],
"content": {
"text": "Hi #PortfolioDay I am a fake artist just trying to teach kids to make cool webby stuff and cut and paste my way to insignificance helping #NAFO raise money for #Ukraine\ufe0f \n\nWatching how important art is to those facing the horrors of war helps restore my faith in humanity",
"html": "Hi <a href=\"https://twitter.com/search?q=%23PortfolioDay\">#PortfolioDay</a> I am a fake artist just trying to teach kids to make cool webby stuff and cut and paste my way to insignificance helping <a href=\"https://twitter.com/search?q=%23NAFO\">#NAFO</a> raise money for <a href=\"https://twitter.com/search?q=%23Ukraine%EF%B8%8F\">#Ukraine\ufe0f</a> \n\nWatching how important art is to those facing the horrors of war helps restore my faith in humanity"
},
"author": {
"type": "card",
"name": "jgregorymcverry.com",
"url": "https://twitter.com/jgmac1106",
"photo": "https://pbs.twimg.com/profile_images/1586874242913734658/3GMcjnTC.jpg"
},
"post-type": "photo",
"_id": "34338002",
"_source": "2773"
}
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": "https://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": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "34336231",
"_source": "2460"
}
If you want to understand how those in power used #disinfo to attack America subscribe.
Good perspective as you look at overalp between #MAGA #Q and #Russia goals in #Ukraine
Our democracy was fundamentally attacked and must be defended.
Here are some details about how, after Trump lost the 2020 election, Mike Flynn ended āQā and turned it into the Big Lie that led to the insurrection.
The only diffe...
{
"type": "entry",
"published": "2023-01-11T14:58:30+00:00",
"url": "https://twitter.com/jgmac1106/status/1613188608059400192",
"quotation-of": "https://twitter.com/jimstewartson/status/1612992296689229824",
"content": {
"text": "If you want to understand how those in power used #disinfo to attack America subscribe.\n\nGood perspective as you look at overalp between #MAGA #Q and #Russia goals in #Ukraine \n\nOur democracy was fundamentally attacked and must be defended.",
"html": "If you want to understand how those in power used <a href=\"https://twitter.com/search?q=%23disinfo\">#disinfo</a> to attack America subscribe.\n\nGood perspective as you look at overalp between <a href=\"https://twitter.com/search?q=%23MAGA\">#MAGA</a> <a href=\"https://twitter.com/search?q=%23Q\">#Q</a> and <a href=\"https://twitter.com/search?q=%23Russia\">#Russia</a> goals in <a href=\"https://twitter.com/search?q=%23Ukraine\">#Ukraine</a> \n\nOur democracy was fundamentally attacked and must be defended."
},
"author": {
"type": "card",
"name": "jgregorymcverry.com",
"url": "https://twitter.com/jgmac1106",
"photo": "https://pbs.twimg.com/profile_images/1586874242913734658/3GMcjnTC.jpg"
},
"post-type": "note",
"refs": {
"https://twitter.com/jimstewartson/status/1612992296689229824": {
"type": "entry",
"published": "2023-01-11T01:58:26+00:00",
"url": "https://twitter.com/jimstewartson/status/1612992296689229824",
"in-reply-to": [
"https://twitter.com/jimstewartson/status/1612985443934687232"
],
"content": {
"text": "Here are some details about how, after Trump lost the 2020 election, Mike Flynn ended \u201cQ\u201d and turned it into the Big Lie that led to the insurrection.\n\nThe only difference between the Big Lie cult and QAnon was focus of purpose and branding. Same people.\njimstewartson.substack.com/p/how-mike-fly\u2026",
"html": "Here are some details about how, after Trump lost the 2020 election, Mike Flynn ended \u201cQ\u201d and turned it into the Big Lie that led to the insurrection.\n\nThe only difference between the Big Lie cult and QAnon was focus of purpose and branding. Same people.\n<a href=\"https://jimstewartson.substack.com/p/how-mike-flynn-transformed-qanon\">jimstewartson.substack.com/p/how-mike-fly\u2026</a>"
},
"author": {
"type": "card",
"name": "Jim Stewartson, Antifascist, #RIPQ \ud83c\uddfa\ud83c\uddf8\ud83c\udff4\u200d\u2620\ufe0f",
"url": "https://twitter.com/jimstewartson",
"photo": "https://pbs.twimg.com/profile_images/1384158490667589633/pu-Uyypx.jpg"
},
"post-type": "reply"
}
},
"_id": "34334015",
"_source": "2773"
}
Once you have a domain^1, and connect it to an #IndieWeb service like micro.blog, or a indieweb.org/CMS on indieweb.org/web_hosting, you can focus^2 on your writing.
Or if you enjoy #webDevelopment and want to build (option three^3),...
tantek.com/t5Nn2
{
"type": "entry",
"published": "2023-01-11T14:43:57+00:00",
"url": "https://twitter.com/t/status/1613184946931392512",
"content": {
"text": "Once you have a domain^1, and connect it to an #IndieWeb service like micro.blog, or a indieweb.org/CMS on indieweb.org/web_hosting, you can focus^2 on your writing.\n\nOr if you enjoy #webDevelopment and want to build (option three^3),...\ntantek.com/t5Nn2",
"html": "Once you have a domain^1, and connect it to an <a href=\"https://twitter.com/search?q=%23IndieWeb\">#IndieWeb</a> service like <a href=\"https://micro.blog\">micro.blog</a>, or a <a href=\"https://indieweb.org/CMS\">indieweb.org/CMS</a> on <a href=\"https://indieweb.org/web_hosting\">indieweb.org/web_hosting</a>, you can focus^2 on your writing.\n\nOr if you enjoy <a href=\"https://twitter.com/search?q=%23webDevelopment\">#webDevelopment</a> and want to build (option three^3),...\n<a href=\"https://tantek.com/t5Nn2\">tantek.com/t5Nn2</a>"
},
"author": {
"type": "card",
"name": "Tantek",
"url": "https://twitter.com/t",
"photo": "https://pbs.twimg.com/profile_images/423350922408767488/nlA_m2WH.jpeg"
},
"post-type": "note",
"_id": "34334016",
"_source": "2773"
}
Four hundred years of Russian diplomacy captured in one image,
thx @JudyTheGoodGal
Another way to look at liberation
{
"type": "entry",
"published": "2023-01-11T14:09:34+00:00",
"url": "https://twitter.com/jgmac1106/status/1613176295151525890",
"quotation-of": "https://twitter.com/JudyTheGoodGal/status/1613174872473014274",
"content": {
"text": "Four hundred years of Russian diplomacy captured in one image,\n\nthx @JudyTheGoodGal",
"html": "Four hundred years of Russian diplomacy captured in one image,\n\nthx <a href=\"https://twitter.com/JudyTheGoodGal\">@JudyTheGoodGal</a>"
},
"author": {
"type": "card",
"name": "jgregorymcverry.com",
"url": "https://twitter.com/jgmac1106",
"photo": "https://pbs.twimg.com/profile_images/1586874242913734658/3GMcjnTC.jpg"
},
"post-type": "note",
"refs": {
"https://twitter.com/JudyTheGoodGal/status/1613174872473014274": {
"type": "entry",
"published": "2023-01-11T14:03:55+00:00",
"url": "https://twitter.com/JudyTheGoodGal/status/1613174872473014274",
"photo": [
"https://pbs.twimg.com/media/FmMl_13X0AEp6p_.jpg"
],
"in-reply-to": [
"https://twitter.com/jgmac1106/status/1613174414341816323"
],
"content": {
"text": "Another way to look at liberation",
"html": "Another way to look at liberation\n<a class=\"u-mention\" href=\"https://twitter.com/jgmac1106\"></a>"
},
"author": {
"type": "card",
"name": "JustAmericanUkrainianMe",
"url": "https://twitter.com/JudyTheGoodGal",
"photo": "https://pbs.twimg.com/profile_images/1607922916443693057/6uuGMKQh.jpg"
},
"post-type": "reply"
}
},
"_id": "34334018",
"_source": "2773"
}