status.blaise.ca
type: Site
name: stadeus
space of: 100days

100days
type: Container
type: channel
description: Updates tagged with 100days on stadeus!
licence: http://creativecommons.org/licenses/by/3.0/
items: restarting-100days-indieweb-gift-calendar
items: no-large-language-model-llm-used
items: capture-first-edit-publish-later
items: posse-syndicate-link-reply
items: bridgyfed-webmention-like-fediverse
items: threads-supports-indieweb-rel-me
items: anniversaries-microformats-posse
items: mastodon-activitypub-follow-form-bridgy-fed
items: wikipedia-supports-indieweb-rel-me
items: venues-reviews-personal-pages
items: account-migration-post-blog-archive-format
items: beyond-mastodon-indieweb-own-domain
items: years-ago-first-federated-indieweb-thread
items: auto-linked-hashtags-federated
items: mozfest-making-fediverse-socialweb
items: blog-as-if-ai-trained-posts
items: five-years-ago-w3c-social-web
items: nineteen-years-microformats
items: unified-sent-box-universal-outbox
items: footnotes-unicode-links
items: post-glossary
items: footnotes-unicode-hyperlink
items: twitter-api-log-in-web-sign-in-relmeauth
items: years-relmeauth-replace-openid
items: indieweb-beyond-blogging
items: contrast-domain-chat-name
items: five-years-websub
items: indieweb-priorities-balance
items: own-your-notes-domain-migration
items: indieweb-eat-what-you-cook
items: bridgy-fed-follow-form
items: reply-domain-above-address-and-silo
items: elevate-indieweb-above-silo
items: socialweb-blogs-reply-comment-post
items: publish-indieweb-decide-distribute
items: domain-first-federated-atmention
items: indieweb-home-internet
items: six-years-webmention-w3c
items: indieweb-evolving-at-mention
items: indieweb-domain-at-mention
items: build-use-services
items: edit-reply-comment-update
items: bridgy-indieweb-posse-backfeed
items: more-100daysofindieweb-projects
items: forward-in-time-links
items: key-owning-notes-domain-name
items: own-your-notes
items: hello

restarting-100days-indieweb-gift-calendar
type: item
type: MicroblogPost
title: : Time to begin again: restarting my #100Days of #IndieWeb project for 2024, as a #100Posts of IndieWeb project, and congrats to the IndieWeb community on a fully completed 2023 IndieWeb Gift Calendar!Last year I completed 48 out of a planned 100 posts in my #100DaysOfIndieWeb project, for nearly 48 days (some days had multiple posts). Instead of resetting my goals accordingly, say down to 50, I’m going for 100 again, however, this time for 100 posts rather than 100 days, having learned that some days I find the time for multiple posts, and other days none at all.Looking back to the start of last year’s 100 Days project, it’s been one year since I encouraged everyone to own their own notes¹. Since then many have started, restarted, or expanded their personal sites to do so. Some have switched from a #Twitter account to a #Mastodon (or other #fediverse) account as a stopgap for short-form status posts. A step in the right direction, yet also an opportunity to take the leap this year to fully own their identity and posts on the web.In 2023 Twitter also broke all existing API clients (including my website). I did not feel it was worth my time to re-apply for an API key and rebuild/retest any necessary code for my semi-automatic #POSSE publishing, not knowing when they might break things again (since there was no rational reason for them to have broken things in the first place).I manually POSSEd a few posts after that, yet from the lack of interactions, either Twitter’s feed algorithm² isn’t showing my posts, or people have largely left or stopped using Twitter. Either way, when your friends stop seeing your posts on a silo, there’s no need to spend any time POSSEing to it.On the positive side, the IndieWeb community really came together in 2023, shining brightly even through the darker days of December.We, the IndieWeb community (and some beyond!) provided a gift (or often multiple) to the rest of community for every single day of December 2023³, the first time we suc…
link: https://status.blaise.ca/notice/116150
description: 's status on Monday, 01-Jan-2024 22:30:00 EST
encoded: Time to begin again: restarting my #100Days of #IndieWeb project for 2024, as a #100Posts of IndieWeb project, and congrats to the IndieWeb community on a fully completed 2023 IndieWeb Gift Calendar! Last year I completed 48 out of a planned 100 posts in my #100DaysOfIndieWeb project, for nearly 48 days (some days had multiple posts). Instead of resetting my goals accordingly, say down to 50, I’m going for 100 again, however, this time for 100 posts rather than 100 days, having learned that some days I find the time for multiple posts, and other days none at all. Looking back to the start of last year’s 100 Days project, it’s been one year since I encouraged everyone to own their own notes¹. Since then many have started, restarted, or expanded their personal sites to do so. Some have switched from a #Twitter account to a #Mastodon (or other #fediverse) account as a stopgap for short-form status posts. A step in the right direction, yet also an opportunity to take the leap this year to fully own their identity and posts on the web. In 2023 Twitter also broke all existing API clients (including my website). I did not feel it was worth my time to re-apply for an API key and rebuild/retest any necessary code for my semi-automatic #POSSE publishing, not knowing when they might break things again (since there was no rational reason for them to have broken things in the first place). I manually POSSEd a few posts after that, yet from the lack of interactions, either Twitter’s feed algorithm² isn’t showing my posts, or people have largely left or stopped using Twitter. Either way, when your friends stop seeing your posts on a silo, there’s no need to spend any time POSSEing to it. On the positive side, the IndieWeb community really came together in 2023, shining brightly even through the darker days of December. We, the IndieWeb community (and some beyond!) provided a gift (or often multiple) to the rest of community for every single day of December 2023³, the first time we…
date: 2024-01-01T22:30:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110227
tagged: concept

concept
type: Tag
label: 100days

concept
type: Tag
label: 100daysofindieweb

concept
type: Tag
label: 100posts

concept
type: Tag
label: 100postsofindieweb

concept
type: Tag
label: fediverse

concept
type: Tag
label: indieweb

concept
type: Tag
label: mastodon

concept
type: Tag
label: posse

concept
type: Tag
label: showdonttellthis

concept
type: Tag
label: twitter

no-large-language-model-llm-used
type: item
type: MicroblogPost
title: : No large language models (LLM) were used in the production of this post.Inspired by a subtle but clear sign-of-the-times one-line disclaimer at the end of RFC9518’s Acknowledgments (https://www.rfc-editor.org/rfc/rfc9518.html#appendix-A-4) “No large language models were used in the production of this document.” I have added a similar disclaimer to the footer of my homepage: “No large language models were used in the production of this site.” 2023 was certainly a year that LLMs took off and stole the hypecycle from #metaverse and #blockchain before that.Yet unlike those previous two, #LLMs are already having real impacts on the way people create (from emails to art), communicate (LLM chat apps), and work (2023 Writer’s Strike), fueling growing concerns about the authenticity of content, especially content from human authors.I expect we will see more such disclaimers in the future.For now, if you blog on your own site with words written by you not #ChatGPT or a similar tool, I encourage you to add a similar disclaimer, and then add your site as an example to the #IndieWeb wiki: * https://indieweb.org/LLM#IndieWeb_Examples#largeLanguageModel #LLM #generativeAI #AIThere is the related problem of, when you discover what seems to be an independent site written by a human, how do you know that human actually exists?For now I’ll mention that XFN rel=met links, published (e.g. metrolls / met-rolls), aggregated, indexed, and queried, can solve that problem. This will be similar to how XFN rel=me links solved #distributed verification on the web (see https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me and posts it links to).This is day 48 of #100DaysOfIndieWeb. #100Days← Day 47: https://tantek.com/2023/365/t1/capture-first-edit-publish-later→ 🔮Post glossary:blockchain https://indieweb.org/blockchainlarge language model / LLM https://indieweb.org/large_language_modelmetaverse https://indieweb.org/metaverserel=me https://indieweb.org/rel-merel=met http://gmpg.org/x…
link: https://status.blaise.ca/notice/116147
description: 's status on Sunday, 31-Dec-2023 17:56:00 EST
encoded: No large language models (LLM) were used in the production of this post. Inspired by a subtle but clear sign-of-the-times one-line disclaimer at the end of RFC9518’s Acknowledgments (https://www.rfc-editor.org/rfc/rfc9518.html#appendix-A-4) “No large language models were used in the production of this document.” I have added a similar disclaimer to the footer of my homepage: “No large language models were used in the production of this site.” 2023 was certainly a year that LLMs took off and stole the hypecycle from #metaverse and #blockchain before that. Yet unlike those previous two, #LLMs are already having real impacts on the way people create (from emails to art), communicate (LLM chat apps), and work (2023 Writer’s Strike), fueling growing concerns about the authenticity of content, especially content from human authors. I expect we will see more such disclaimers in the future. For now, if you blog on your own site with words written by you not #ChatGPT or a similar tool, I encourage you to add a similar disclaimer, and then add your site as an example to the #IndieWeb wiki: * https://indieweb.org/LLM#IndieWeb_Examples #largeLanguageModel #LLM #generativeAI #AI There is the related problem of, when you discover what seems to be an independent site written by a human, how do you know that human actually exists? For now I’ll mention that XFN rel=met links, published (e.g. metrolls / met-rolls), aggregated, indexed, and queried, can solve that problem. This will be similar to how XFN rel=me links solved #distributed verification on the web (see https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me and posts it links to). This is day 48 of #100DaysOfIndieWeb. #100Days ← Day 47: https://tantek.com/2023/365/t1/capture-first-edit-publish-later → 🔮 Post glossary: blockchain https://indieweb.org/blockchain large language model / LLM https://indieweb.org/large_language_model metaverse https://indieweb.org/metaverse rel=me https://indieweb.org/rel-me rel=met htt…
date: 2023-12-31T17:56:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110224
enclosure: threads-supports-indieweb-rel-me
links to: threads-supports-indieweb-rel-me
enclosure: appendix-A-4
links to: appendix-A-4
enclosure: largeLanguageModel
links to: largeLanguageModel
enclosure: capture-first-edit-publish-later
links to: capture-first-edit-publish-later
enclosure: blockchainlarge
links to: blockchainlarge
enclosure: large language modelmetaverse
links to: large language modelmetaverse
enclosure: https://indieweb.org/metaverserel=me
links to: https://indieweb.org/metaverserel=me
enclosure: https://indieweb.org/rel-merel=met
links to: https://indieweb.org/rel-merel=met
enclosure: metXFN
links to: metXFN
enclosure: xfn
links to: xfn
tagged: concept
date: 2023-12-31T19:22:23-05:00
type: text/html; charset=UTF-8

threads-supports-indieweb-rel-me
date: 2023-10-17T00:09:45-04:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : Threads.net now supports the #indieWeb #microformats #openStandard rel-me for distributed ✅ verification!¹ (supported since 2023-08-09)My Threads profile already had my domain since it was created from my Instagram profile.View source on https://www.threads.net/@tantek and you can see the #relMe on a link tag: Instructions to add yours:* Add your domain to your Threads profile "Link" field. That’s it.Longer explicit steps: https://indieweb.org/rel-me#ThreadsThanks especially to @timothychambers.net (@tchambers@indieweb.social, @timothyjchambers@threads.net) for requesting rel-me support² which one Threads engineer “decided to hack it together” one night!³You can view Tim’s profile @tchambers@indieweb.social for a real world example of a Mastodon profile showing a green text ✅ verified link to a Threads profile.Tim made several good points in his request:“… a small, but disproportionately helpful addition would be to support this "rel=me" feature in your profiles. That could launch well before full ActivityPub, & show the first real integration to open social web standards”Microformats (and IndieWeb) standards in general are deliberately designed as small, incremental building blocks which are disproportionately helpful as Tim says.These small building blocks which directly enable user features are usually something a web developer can code at least some (often complete!) support for in one day/night which makes them particularly appealing as a way to rapidly support open #socialWeb standards used by the #fediverse and beyond.Incrementally implementing microformats & IndieWeb standards⁴ also demonstrates good will and good intentions for supporting the #openWeb.This is day 44 of #100DaysOfIndieWeb. #100Days← Day 43: https://tantek.com/2023/171/t1/anniversaries-microformats-posse→ 🔮Previously:* 2023-02-01 Wikipedia.org supports multiple rel=me links: https://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me¹ https://www.threads.net/@mosseri/post/Cvu2eXurRbB²…
link: https://status.blaise.ca/notice/116129
description: 's status on Tuesday, 22-Aug-2023 15:43:00 EDT
encoded: Threads.net now supports the #indieWeb #microformats #openStandard rel-me for distributed ✅ verification!¹ (supported since 2023-08-09) My Threads profile already had my domain since it was created from my Instagram profile. View source on https://www.threads.net/@tantek and you can see the #relMe on a link tag: Instructions to add yours: * Add your domain to your Threads profile "Link" field. That’s it. Longer explicit steps: https://indieweb.org/rel-me#Threads Thanks especially to @timothychambers.net (@tchambers@indieweb.social, @timothyjchambers@threads.net) for requesting rel-me support² which one Threads engineer “decided to hack it together” one night!³ You can view Tim’s profile @tchambers@indieweb.social for a real world example of a Mastodon profile showing a green text ✅ verified link to a Threads profile. Tim made several good points in his request: “… a small, but disproportionately helpful addition would be to support this "rel=me" feature in your profiles. That could launch well before full ActivityPub, & show the first real integration to open social web standards” Microformats (and IndieWeb) standards in general are deliberately designed as small, incremental building blocks which are disproportionately helpful as Tim says. These small building blocks which directly enable user features are usually something a web developer can code at least some (often complete!) support for in one day/night which makes them particularly appealing as a way to rapidly support open #socialWeb standards used by the #fediverse and beyond. Incrementally implementing microformats & IndieWeb standards⁴ also demonstrates good will and good intentions for supporting the #openWeb. This is day 44 of #100DaysOfIndieWeb. #100Days ← Day 43: https://tantek.com/2023/171/t1/anniversaries-microformats-posse → 🔮 Previously: * 2023-02-01 Wikipedia.org supports multiple rel=me links: https://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me ¹ https://www.threads.net/@mosseri/po…
date: 2023-08-22T15:43:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110207
enclosure: tantek.com
links to: tantek.com
enclosure: spec.indieweb.org
links to: spec.indieweb.org
enclosure: wikipedia-supports-indieweb-rel-me
links to: wikipedia-supports-indieweb-rel-me
enclosure: @tantek
links to: @tantek
enclosure: ThreadsThanks
links to: ThreadsThanks
enclosure: anniversaries-microformats-posse
links to: anniversaries-microformats-posse
links to: Cvu2eXurRbB²
links to: CupCvChAxI8³
links to: Cvu7-A4viZu⁴
tagged: concept

appendix-A-4
date: 2023-12-31T19:22:15-05:00
type: text/html; charset=UTF-8

largeLanguageModel
date: 2023-12-31T19:22:16-05:00
type: text/html; charset=UTF-8

capture-first-edit-publish-later
date: 2023-12-31T19:22:17-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : Writing about writing: capture first, edit & publish later.Braindump timely thoughts & experiences into as many draft notes as it takes, while ideas & memories are fresh.Collecting higher fidelity memories seems more important than editing past writings or finishing/polishing a post for publishing, which can be done at a later time.Sometimes the passage of time helps provide insights and broader understandings that can help with writing more effective posts, from better summaries to narratives that help sense-making.Bits of even this minor post sat for weeks, and only today did I add a summary and related thoughts.Similarly, it makes sense to edit and publish small notes on a subject, without feeling compelled to turn them into a larger blog post, or a longer list of points.This is a key advantage to publishing on your own #indieweb site, you decide on the granularity of your posts, small, medium or large, instead of being constrained, burdened, or pressured by any particular #socialMedia user interface, character count limitation, or audience expectation. Like Twitter before it, even the default #Mastodon user interface has limitations, and the #fediverse itself as a whole has audience/cultural expectations (certainly quite a few articles have been written about that).On your own site you decide if you want to publish a post to make one point, or mention a related point or two, or collect things into a list or longer article, or eventually all of the above.On your own site you feel more free to prioritize and share what is on your mind, instead of feeling compelled to first respond to whatever topics are trending, or to whatever you happen to read in your algorithmic feed.#writingAboutWritingThis is day 47 of #100DaysOfIndieWeb. #100Days← Day 46: https://tantek.com/2023/289/t1/bridgyfed-webmention-like-fediverse→ Day 48: https://tantek.com/2023/365/t2/no-large-language-model-llm-usedRelated: * “More Thoughtful Reading & Writing on the Web” (https://tantek.com/202…
link: https://status.blaise.ca/notice/116148
description: 's status on Sunday, 31-Dec-2023 17:04:00 EST
encoded: Writing about writing: capture first, edit & publish later. Braindump timely thoughts & experiences into as many draft notes as it takes, while ideas & memories are fresh. Collecting higher fidelity memories seems more important than editing past writings or finishing/polishing a post for publishing, which can be done at a later time. Sometimes the passage of time helps provide insights and broader understandings that can help with writing more effective posts, from better summaries to narratives that help sense-making. Bits of even this minor post sat for weeks, and only today did I add a summary and related thoughts. Similarly, it makes sense to edit and publish small notes on a subject, without feeling compelled to turn them into a larger blog post, or a longer list of points. This is a key advantage to publishing on your own #indieweb site, you decide on the granularity of your posts, small, medium or large, instead of being constrained, burdened, or pressured by any particular #socialMedia user interface, character count limitation, or audience expectation. Like Twitter before it, even the default #Mastodon user interface has limitations, and the #fediverse itself as a whole has audience/cultural expectations (certainly quite a few articles have been written about that). On your own site you decide if you want to publish a post to make one point, or mention a related point or two, or collect things into a list or longer article, or eventually all of the above. On your own site you feel more free to prioritize and share what is on your mind, instead of feeling compelled to first respond to whatever topics are trending, or to whatever you happen to read in your algorithmic feed. #writingAboutWriting This is day 47 of #100DaysOfIndieWeb. #100Days ← Day 46: https://tantek.com/2023/289/t1/bridgyfed-webmention-like-fediverse → Day 48: https://tantek.com/2023/365/t2/no-large-language-model-llm-used Related: * “More Thoughtful Reading & Writing on the Web” (https://tan…
date: 2023-12-31T17:04:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110225
enclosure: articlenote
links to: articlenote
enclosure: bridgyfed-webmention-like-fediverse
links to: bridgyfed-webmention-like-fediverse
enclosure: no-large-language-model-llm-used
links to: no-large-language-model-llm-used
enclosure: thoughtful-reading-writing-web
links to: thoughtful-reading-writing-web
enclosure: algorithmic feedarticle
links to: algorithmic feedarticle
enclosure: notepost
links to: notepost
enclosure: postsense-making
links to: postsense-making
enclosure: Sensemaking (information science)social
links to: Sensemaking (information science)social
enclosure: social media
links to: social media
tagged: concept

blockchainlarge
date: 2023-12-31T19:22:18-05:00
type: text/html; charset=UTF-8

large language modelmetaverse
date: 2023-12-31T19:22:18-05:00
type: text/html; charset=UTF-8

https://indieweb.org/metaverserel=me
date: 2023-12-31T19:22:19-05:00
type: text/html; charset=UTF-8

https://indieweb.org/rel-merel=met
date: 2023-12-31T19:22:20-05:00
type: text/html; charset=UTF-8

metXFN
date: 2023-12-31T19:22:21-05:00
type: text/html; charset=UTF-8

xfn
date: 2023-12-31T19:22:21-05:00
type: text/html; charset=UTF-8

concept
type: Tag
label: aithere

concept
type: Tag
label: blockchain

concept
type: Tag
label: chatgpt

concept
type: Tag
label: distributed

concept
type: Tag
label: generativeai

concept
type: Tag
label: llm

concept
type: Tag
label: llms

concept
type: Tag
label: metaverse

articlenote
date: 2023-09-24T23:16:24-04:00
type: text/html; charset=UTF-8

bridgyfed-webmention-like-fediverse
date: 2023-10-23T22:05:42-04:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : Implemented liking/favoriting of #Mastodon posts via Bridgy Fed on my site! (Actually of any post on any site that #BridgyFed can discover an #ActivityPub endpoint to send likes to.)Tested it by liking @evanp.me (@evan@cosocial.ca @evanpro)’s reply¹ confirming that he received a notification from my prior post². I sent a #Webmention from my like post³ to Bridgy Fed, and it #federated the like to Evan’s server, which subsequently showed up in the "favourites" list of Evan’s post:https://cosocial.ca/@evan/111237962392745000/favouritesEvery step that connects heterogenous #socialWeb systems & protocols feels like progress.This is day 45 of #100DaysOfIndieWeb. #100Days #IndieWeb #like #likes #fediverse #favorite #favourite #favourites← Day 44: https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me→ 🔮¹ https://cosocial.ca/@evan/111237962392745000² https://tantek.com/2023/287/t1/federating-mentions³ https://tantek.com/2023/289/f1
link: https://status.blaise.ca/notice/116139
description: 's status on Monday, 16-Oct-2023 21:16:00 EDT
encoded: Implemented liking/favoriting of #Mastodon posts via Bridgy Fed on my site! (Actually of any post on any site that #BridgyFed can discover an #ActivityPub endpoint to send likes to.) Tested it by liking @evanp.me (@evan@cosocial.ca @evanpro)’s reply¹ confirming that he received a notification from my prior post². I sent a #Webmention from my like post³ to Bridgy Fed, and it #federated the like to Evan’s server, which subsequently showed up in the "favourites" list of Evan’s post: https://cosocial.ca/@evan/111237962392745000/favourites Every step that connects heterogenous #socialWeb systems & protocols feels like progress. This is day 45 of #100DaysOfIndieWeb. #100Days #IndieWeb #like #likes #fediverse #favorite #favourite #favourites ← Day 44: https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me → 🔮 ¹ https://cosocial.ca/@evan/111237962392745000 ² https://tantek.com/2023/287/t1/federating-mentions ³ https://tantek.com/2023/289/f1
date: 2023-10-16T21:16:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110216
enclosure: threads-supports-indieweb-rel-me
links to: threads-supports-indieweb-rel-me
enclosure: 111237962392745000²
links to: 111237962392745000²
enclosure: federating-mentions
links to: federating-mentions
enclosure: f1
links to: f1
tagged: concept

thoughtful-reading-writing-web
date: 2023-12-31T19:22:24-05:00
type: text/html; charset=UTF-8

algorithmic feedarticle
date: 2023-12-31T19:22:25-05:00
type: text/html; charset=UTF-8

notepost
date: 2023-12-31T19:22:26-05:00
type: text/html; charset=UTF-8

postsense-making
date: 2023-12-31T19:22:27-05:00
type: text/html; charset=UTF-8

Sensemaking (information science)social
date: 2023-12-31T19:22:28-05:00
type: text/html; charset=UTF-8

social media
date: 2023-12-31T19:22:28-05:00
type: text/html; charset=UTF-8

concept
type: Tag
label: socialmedia

posse-syndicate-link-reply
type: item
type: MicroblogPost
title: : Great article on #POSSE by David Pierce (@davidpierce@mastodon.social @pierce) @Verge:https://www.theverge.com/2023/10/23/23928550/posse-posting-activitypub-standard-twitter-tumblr-mastodonSeveral key points of POSSE explained in the article:First, post on your own site: “In a POSSE world, everybody owns a domain name, and everybody has a blog. (… a place on the internet where you post your stuff and others consume it.)” Second, syndicate elsewhere, appropriately for each destination: “Then, your long blog post might be broken into chunks and posted as a thread on X and Mastodon and Threads. The whole thing might go to your Medium page and your Tumblr and your LinkedIn profile, too. If you post a photo, it might go straight to Instagram, and a vertical video would whoosh straight to TikTok, Reels, and Shorts. Your post appears natively on all of those platforms,”You can use Bridgy Publish (https://brid.gy/) to POSSE to many destinations, and Bridgy Fed (https://fed.brid.gy/) to #federate to #Mastodon and other #fediverse destinations, directly from your site instead of posting a copy on yet another account on yet another server.Third, and this is a key piece that distinguishes proper POSSE setups, with original post perma(short)links back to your posts on your domain: “typically with some kind of link back to your blog.” All copies link to (your) home. "And your blog becomes the hub for everything, your main home on the internet." You have power over your domain (name), not outside silos.David embedded a screenshot of one of my posts, a reply post:in which I posted a reply *on my own site*¹ to @Zeldman.com’s tweet (itself a reply to a POSSE copy of one of my posts), and POSSEd my reply to Twitter so it would thread with his reply.This illustrates another important detail of a proper POSSE setup:Fourth, post *replies* and other responses from your own site, whether to other #IndieWeb sites, or to others’s silo posts (tweets etc.).Own your data means owning your rep…
link: https://status.blaise.ca/notice/116140
description: 's status on Monday, 23-Oct-2023 20:30:00 EDT
encoded: Great article on #POSSE by David Pierce (@davidpierce@mastodon.social @pierce) @Verge: https://www.theverge.com/2023/10/23/23928550/posse-posting-activitypub-standard-twitter-tumblr-mastodon Several key points of POSSE explained in the article: First, post on your own site: “In a POSSE world, everybody owns a domain name, and everybody has a blog. (… a place on the internet where you post your stuff and others consume it.)” Second, syndicate elsewhere, appropriately for each destination: “Then, your long blog post might be broken into chunks and posted as a thread on X and Mastodon and Threads. The whole thing might go to your Medium page and your Tumblr and your LinkedIn profile, too. If you post a photo, it might go straight to Instagram, and a vertical video would whoosh straight to TikTok, Reels, and Shorts. Your post appears natively on all of those platforms,” You can use Bridgy Publish (https://brid.gy/) to POSSE to many destinations, and Bridgy Fed (https://fed.brid.gy/) to #federate to #Mastodon and other #fediverse destinations, directly from your site instead of posting a copy on yet another account on yet another server. Third, and this is a key piece that distinguishes proper POSSE setups, with original post perma(short)links back to your posts on your domain: “typically with some kind of link back to your blog.” All copies link to (your) home. "And your blog becomes the hub for everything, your main home on the internet." You have power over your domain (name), not outside silos. David embedded a screenshot of one of my posts, a reply post: in which I posted a reply *on my own site*¹ to @Zeldman.com’s tweet (itself a reply to a POSSE copy of one of my posts), and POSSEd my reply to Twitter so it would thread with his reply. This illustrates another important detail of a proper POSSE setup: Fourth, post *replies* and other responses from your own site, whether to other #IndieWeb sites, or to others’s silo posts (tweets etc.). Own your data means owning …
date: 2023-10-23T20:30:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110217
tagged: concept

concept
type: Tag
label: backfeed

concept
type: Tag
label: bridgy

concept
type: Tag
label: bridgyfed

concept
type: Tag
label: federate

concept
type: Tag
label: federated

concept
type: Tag
label: webmention

111237962392745000²
date: 2023-10-17T00:09:46-04:00
length: 22930
type: text/html; charset=utf-8

federating-mentions
date: 2023-10-17T00:09:47-04:00
type: text/html; charset=UTF-8

f1
date: 2023-10-17T00:09:47-04:00
type: text/html; charset=UTF-8

concept
type: Tag
label: activitypub

concept
type: Tag
label: favorite

concept
type: Tag
label: favourite

concept
type: Tag
label: favourites

concept
type: Tag
label: like

concept
type: Tag
label: likes

concept
type: Tag
label: socialweb

tantek.com
date: 2022-10-29T03:01:39-04:00
type: text/html; charset=UTF-8

spec.indieweb.org
date: 2023-01-11T09:44:12-05:00
length: 35487
type: text/html

wikipedia-supports-indieweb-rel-me
date: 2023-06-10T00:12:54-04:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : Wikipedia.org (@wikipedia@wikis.world @wikipedia) now supports #IndieWeb rel-me!¹Thanks to @taavi.wtf (@taavi@wikis.world) for the #MediaWiki RealMe extension²Added it to my #Wikipedia User: page https://en.wikipedia.org/wiki/User:TantekView source and you can see the #relMe on a link tag: Instructions to add yours here:* https://indieweb.org/rel-me#WikipediaThis is day 41 of #100DaysOfIndieWeb. #100Days← Day 40: https://tantek.com/2023/114/t1/venues-reviews-personal-pages→ 🔮Previously:* 2023-02-01 GitHub supports multiple rel=me links: https://tantek.com/2023/032/t1/years-relmeauth-replace-openid¹ https://wikis.world/@wikipedia/110396865170645710² https://www.mediawiki.org/wiki/Extension:RealMe
link: https://status.blaise.ca/notice/116095
description: 's status on Friday, 19-May-2023 16:19:00 EDT
encoded: Wikipedia.org (@wikipedia@wikis.world @wikipedia) now supports #IndieWeb rel-me!¹ Thanks to @taavi.wtf (@taavi@wikis.world) for the #MediaWiki RealMe extension² Added it to my #Wikipedia User: page https://en.wikipedia.org/wiki/User:Tantek View source and you can see the #relMe on a link tag: Instructions to add yours here: * https://indieweb.org/rel-me#Wikipedia This is day 41 of #100DaysOfIndieWeb. #100Days ← Day 40: https://tantek.com/2023/114/t1/venues-reviews-personal-pages → 🔮 Previously: * 2023-02-01 GitHub supports multiple rel=me links: https://tantek.com/2023/032/t1/years-relmeauth-replace-openid ¹ https://wikis.world/@wikipedia/110396865170645710 ² https://www.mediawiki.org/wiki/Extension:RealMe
date: 2023-05-19T16:19:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110191
tagged: concept

@tantek
date: 2023-08-22T19:29:05-04:00
type: text/html; charset="utf-8"

ThreadsThanks
date: 2023-08-22T19:29:06-04:00
type: text/html; charset=UTF-8

anniversaries-microformats-posse
date: 2023-08-22T19:29:07-04:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : Two anniversaries today: microformats (18y) and POSSE (11y).Happy 18 years of https://microformats.org/ #microformats!Most prominent this past year (again) has been the littlest #microformat that could:rel=me — AKA #relme, now effectively the standard for #distributed #verification on the web:* https://microformats.org/wiki/rel-me (originally introduced in 2004¹)with support added in the past year for:* #GitHub multiple rel-me links²* #Wikipedia User page rel-me link³, which is surprising since when it was conceived, the #IndieWeb community was in a period of very rapid innovation & iteration. POSSE itself replaced a previous term, "POSE", short for “Publish Once Syndicate Everywhere”, which had only been around a year or two at most (I’m still looking for the first use of the "POSE" abbreviation for that meaning). Since “publish once” was vague enough to include practices of publishing once on a social media silo, or in someone else’s garage⁵, we needed to clearly express the requirement to use your own site instead, first, as the source of your truth. Cross-posting to other sites & channels, is a second, optional step, ideally with a permalink linking back to your original post so viewers can easily discover and use your site.That distinction was enough for POSSE to express a strong creator-owned-first publishing model that resonated and grew. Every time a silo shutdown⁶ at the end of its incredible journey⁷, removing posts & permalinks from the web, POSSE was there for people who were tired of losing their data, permalinks, & profiles, and wanted an alternative.This is day 43 of #100DaysOfIndieWeb. #100Days← Day 42: https://tantek.com/2023/160/t1/mastodon-activitypub-follow-form-bridgy-fed→ 🔮Glossarypermalink https://indieweb.org/permalinkPOSE https://indieweb.org/POSEPOSSE https://indieweb.org/POSSEsilo https://indieweb.org/siloReferences¹ https://gmpg.org/xfn/11#me² https://tantek.com/2023/032/t1/years-relmeauth-replace-openid³ https://tantek.com/2023/139/t1/…
link: https://status.blaise.ca/notice/116117
description: 's status on Tuesday, 20-Jun-2023 19:52:00 EDT
encoded: Two anniversaries today: microformats (18y) and POSSE (11y). Happy 18 years of https://microformats.org/ #microformats! Most prominent this past year (again) has been the littlest #microformat that could: rel=me — AKA #relme, now effectively the standard for #distributed #verification on the web: * https://microformats.org/wiki/rel-me (originally introduced in 2004¹) with support added in the past year for: * #GitHub multiple rel-me links² * #Wikipedia User page rel-me link³ , which is surprising since when it was conceived, the #IndieWeb community was in a period of very rapid innovation & iteration. POSSE itself replaced a previous term, "POSE", short for “Publish Once Syndicate Everywhere”, which had only been around a year or two at most (I’m still looking for the first use of the "POSE" abbreviation for that meaning). Since “publish once” was vague enough to include practices of publishing once on a social media silo, or in someone else’s garage⁵, we needed to clearly express the requirement to use your own site instead, first, as the source of your truth. Cross-posting to other sites & channels, is a second, optional step, ideally with a permalink linking back to your original post so viewers can easily discover and use your site. That distinction was enough for POSSE to express a strong creator-owned-first publishing model that resonated and grew. Every time a silo shutdown⁶ at the end of its incredible journey⁷, removing posts & permalinks from the web, POSSE was there for people who were tired of losing their data, permalinks, & profiles, and wanted an alternative. This is day 43 of #100DaysOfIndieWeb. #100Days ← Day 42: https://tantek.com/2023/160/t1/mastodon-activitypub-follow-form-bridgy-fed → 🔮 Glossary permalink https://indieweb.org/permalink POSE https://indieweb.org/POSE POSSE https://indieweb.org/POSSE silo https://indieweb.org/silo References ¹ https://gmpg.org/xfn/11#me ² https://tantek.com/2023/032/t1/years-relmeauth-replace-openid ³ https://tant…
date: 2023-06-20T19:52:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110202
enclosure: own-your-notes
links to: own-your-notes
enclosure: years-relmeauth-replace-openid
links to: years-relmeauth-replace-openid
enclosure: wikipedia-supports-indieweb-rel-me
links to: wikipedia-supports-indieweb-rel-me
enclosure: microformats.org
links to: microformats.org
enclosure: rel-me
links to: rel-me
enclosure: mastodon-activitypub-follow-form-bridgy-fed
links to: mastodon-activitypub-follow-form-bridgy-fed
enclosure: permalinkPOSE
links to: permalinkPOSE
enclosure: POSEPOSSE
links to: POSEPOSSE
enclosure: POSSEsilo
links to: POSSEsilo
enclosure: siloReferences¹
links to: siloReferences¹
enclosure: me²
links to: me²
enclosure: posse-core-indieweb-approach
links to: posse-core-indieweb-approach
enclosure: site-deaths⁷
links to: site-deaths⁷
enclosure: ourincrediblejourney.tumblr.com
links to: ourincrediblejourney.tumblr.com
tagged: concept

concept
type: Tag
label: microformats

concept
type: Tag
label: openstandard

concept
type: Tag
label: openwebthis

concept
type: Tag
label: relme

own-your-notes
date: 2023-01-03T03:32:20-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : I am once again asking you to own your notes, rather than tweeting them into Big Chad's garage.Maybe you left the big garage and now toot in your neighborhood Chad's garage. It's still someone else's garage. https://xkcd.com/1150 #IndieWebMaybe it was an easier first step to take. Time to take the next step, with your own domain, and a turnkey service like https://micro.blog/, or an https://indieweb.org/CMS if you prefer, or go full stack and make it yourself, using building blocks like https://indieweb.org/Indiekit. Just https://indieweb.org/start.This is day 1 of my 2023 #100Days project, #100DaysOfIndieWeb, posting an #IndieWeb encouragement, tool, or tip at least once a day for 100 days, to setup and use your own personal site instead of someone else's garage.In the theme of: https://indieweb.org/100_days#100_Days_of_IndieWebPreviously: https://tantek.com/2022/001/t1/12-years-notes-my-site
link: https://status.blaise.ca/notice/115970
description: 's status on Monday, 02-Jan-2023 02:11:00 EST
encoded: I am once again asking you to own your notes, rather than tweeting them into Big Chad's garage. Maybe you left the big garage and now toot in your neighborhood Chad's garage. It's still someone else's garage. https://xkcd.com/1150 #IndieWeb Maybe it was an easier first step to take. Time to take the next step, with your own domain, and a turnkey service like https://micro.blog/, or an https://indieweb.org/CMS if you prefer, or go full stack and make it yourself, using building blocks like https://indieweb.org/Indiekit. Just https://indieweb.org/start. This is day 1 of my 2023 #100Days project, #100DaysOfIndieWeb, posting an #IndieWeb encouragement, tool, or tip at least once a day for 100 days, to setup and use your own personal site instead of someone else's garage. In the theme of: https://indieweb.org/100_days#100_Days_of_IndieWeb Previously: https://tantek.com/2022/001/t1/12-years-notes-my-site
date: 2023-01-02T02:11:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110101
tagged: concept

years-relmeauth-replace-openid
date: 2023-02-03T14:13:08-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : 13 years ago today: created #RelMeAuth with @progrium.com, to replace OpenID 1&2 for *reasons** modest proposal: authentication using domain as identity, rel=me link to OAuth profile with rel=me link back^1* @progrium.com suggested RelMeAuth name^2 * I agreed, and wrote up a draft algorithm^3All on the same day. A few months later I wrote it up as a draft spec:* https://microformats.org/wiki/RelMeAuth (could use some updates)More updates and discussion:* https://indieweb.org/RelMeAuthSee those links for RelMeAuth implementations in:* PHP, Python, Node, Ruby, GoRelMeAuth is simpler for both publishers & parsers (consuming code) than OpenID.There are now more sites that support RelMeAuth (and the complementary IndieAuth) than OpenID (which is largely abandoned^4).And today, @Github.com rolled out support for multiple rel=me profile links!^5This means you can now use @Github.com’s OAuth (and their multifactor login etc.) to authenticate as your own domain via RelMeAuth on even more services.E.g. see my profile https://tantek.com/github (not a typo^6). The left sidebar links to my personal site, Twitter, and https://micro.blog/t all with rel=me markup.This is day 26 of #100DaysOfIndieWeb #100Days← Day 25: https://tantek.com/2023/029/t1/indieweb-beyond-blogging→ 🔮^1 https://tantek.com/2010/032/t5/modest-proposal-authentication-oauth-twitter-rel-me^2 https://twitter.com/progrium/status/8521001762 ^3 https://tantek.com/2010/032/t6/relmeauth-oauth-rel-me-auto-fallback-authentication^4 OpenID 1&2 were abandoned for OIDC (OpenID Connect), a supposed update/replacement, despite dropping the goal of domain as identity, the use-case for OpenID in the first place, so the IndieWeb picked up that use-case with RelMeAuth & IndieAuth.^5 https://hachyderm.io/@nova/109790530971147702^6 https://tantek.com/2022/144/t1/redirected-github-ownyourlinks
link: https://status.blaise.ca/notice/116012
description: 's status on Wednesday, 01-Feb-2023 17:34:00 EST
encoded: 13 years ago today: created #RelMeAuth with @progrium.com, to replace OpenID 1&2 for *reasons* * modest proposal: authentication using domain as identity, rel=me link to OAuth profile with rel=me link back^1 * @progrium.com suggested RelMeAuth name^2 * I agreed, and wrote up a draft algorithm^3 All on the same day. A few months later I wrote it up as a draft spec: * https://microformats.org/wiki/RelMeAuth (could use some updates) More updates and discussion: * https://indieweb.org/RelMeAuth See those links for RelMeAuth implementations in: * PHP, Python, Node, Ruby, Go RelMeAuth is simpler for both publishers & parsers (consuming code) than OpenID. There are now more sites that support RelMeAuth (and the complementary IndieAuth) than OpenID (which is largely abandoned^4). And today, @Github.com rolled out support for multiple rel=me profile links!^5 This means you can now use @Github.com’s OAuth (and their multifactor login etc.) to authenticate as your own domain via RelMeAuth on even more services. E.g. see my profile https://tantek.com/github (not a typo^6). The left sidebar links to my personal site, Twitter, and https://micro.blog/t all with rel=me markup. This is day 26 of #100DaysOfIndieWeb #100Days ← Day 25: https://tantek.com/2023/029/t1/indieweb-beyond-blogging → 🔮 ^1 https://tantek.com/2010/032/t5/modest-proposal-authentication-oauth-twitter-rel-me ^2 https://twitter.com/progrium/status/8521001762 ^3 https://tantek.com/2010/032/t6/relmeauth-oauth-rel-me-auto-fallback-authentication ^4 OpenID 1&2 were abandoned for OIDC (OpenID Connect), a supposed update/replacement, despite dropping the goal of domain as identity, the use-case for OpenID in the first place, so the IndieWeb picked up that use-case with RelMeAuth & IndieAuth. ^5 https://hachyderm.io/@nova/109790530971147702 ^6 https://tantek.com/2022/144/t1/redirected-github-ownyourlinks
date: 2023-02-01T17:34:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110135
enclosure: RelMeAuth
links to: RelMeAuth
enclosure: RelMeAuthSee
links to: RelMeAuthSee
enclosure: tantek
links to: tantek
enclosure: https://micro.blog/t
links to: https://micro.blog/t
enclosure: indieweb-beyond-blogging
links to: indieweb-beyond-blogging
enclosure: modest-proposal-authentication-oauth-twitter-rel-me
links to: modest-proposal-authentication-oauth-twitter-rel-me
enclosure: https://twitter.com/progrium/status/8521001762
links to: https://twitter.com/progrium/status/8521001762
enclosure: relmeauth-oauth-rel-me-auto-fallback-authentication
links to: relmeauth-oauth-rel-me-auto-fallback-authentication
enclosure: https://hachyderm.io/@nova/109790530971147702
links to: https://hachyderm.io/@nova/109790530971147702
enclosure: redirected-github-ownyourlinks
links to: redirected-github-ownyourlinks
tagged: concept

microformats.org
date: 2023-06-21T04:00:16-04:00
type: text/html; charset=UTF-8

rel-me
date: 2023-06-21T04:00:17-04:00
type: text/html; charset=UTF-8

mastodon-activitypub-follow-form-bridgy-fed
date: 2023-06-21T04:00:18-04:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : If you added a #Mastodon / #ActivityPub follow form to your #IndieWeb site based on Bridgy Fed (e.g. using code/instructions I previously posted¹), you need to update it to add another invisible input element for the "protocol", e.g.: Otherwise people trying to use your form to follow you may see an error from #BridgyFed like:> Bad Request > Missing required parameter protocolHere is the complete example that I posted previously with the new invisible input: 🐘 Follow @tantek.com@tantek.com: enter your @-@ fediverse address: Follow I also updated that previous post¹ with the new input in case people find that instead.This is day 42 of #100DaysOfIndieWeb. #100Days← Day 41: https://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me→ 🔮¹ https://tantek.com/2023/020/t2/bridgy-fed-follow-form
link: https://status.blaise.ca/notice/116116
description: 's status on Friday, 09-Jun-2023 22:14:00 EDT
encoded: If you added a #Mastodon / #ActivityPub follow form to your #IndieWeb site based on Bridgy Fed (e.g. using code/instructions I previously posted¹), you need to update it to add another invisible input element for the "protocol", e.g.: Otherwise people trying to use your form to follow you may see an error from #BridgyFed like: > Bad Request > Missing required parameter protocol Here is the complete example that I posted previously with the new invisible input: 🐘 Follow @tantek.com@tantek.com: enter your @-@ fediverse address: <input id="follow-address" name="address" type="text" required="required" placeholder="@you@instance.social" alt="fediverse address" value="" /> Follow I also updated that previous post¹ with the new input in case people find that instead. This is day 42 of #100DaysOfIndieWeb. #100Days ← Day 41: https://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me → 🔮 ¹ https://tantek.com/2023/020/t2/bridgy-fed-follow-form
date: 2023-06-09T22:14:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110201
tagged: concept

permalinkPOSE
date: 2023-06-21T04:00:19-04:00
type: text/html; charset=UTF-8

POSEPOSSE
date: 2023-06-21T04:00:21-04:00
type: text/html; charset=UTF-8

POSSEsilo
date: 2023-06-21T04:00:22-04:00
type: text/html; charset=UTF-8

siloReferences¹
date: 2023-06-21T04:00:24-04:00
type: text/html; charset=UTF-8

me²
date: 2023-06-21T04:00:25-04:00
type: text/html; charset=UTF-8

posse-core-indieweb-approach
date: 2023-06-21T04:00:27-04:00
type: text/html; charset=UTF-8

site-deaths⁷
date: 2023-06-21T04:00:29-04:00
type: text/html; charset=UTF-8

ourincrediblejourney.tumblr.com
date: 2023-06-21T04:00:30-04:00
type: text/html; charset=UTF-8

concept
type: Tag
label: github

concept
type: Tag
label: microformat

concept
type: Tag
label: verification

concept
type: Tag
label: wikipedia

concept
type: Tag
label: mediawiki

venues-reviews-personal-pages
type: item
type: MicroblogPost
title: : 🌱 I have long been a fan of @Foursquare.com and @Swarmapp.com, having created many venues, posted many tips, and (checks profile) over 45,000 checkins. I recently joined @happycow.net and before I start posting new vegan (friendly) venues or reviews there, I really need to figure out my own personal site venue pages (including URL design) and review posts design and authoring workflow.I’m pretty sure I can and should post h-review posts as a variant of articles (with usual h-entry markup) with an explicit article name, since most review destinations request a title (name) for the review (e.g. HappyCow, TripAdvisor), and for others with only review text (e.g. Google Maps), I can include the name at the start.Different review destinations have different text requirements (minimum and/or maximum lengths), and I’ll take time to document those first.The first destination I’ll likely try automatically syndicating to is a site created by #IndieWeb community member @jamesg.blog (@capjamesg@indieweb.social): @breakfastand.coffeeIt’s still quite new, but the thing that makes Breakfast & Coffee innovative and unique is that it encourages you to post your venue (e.g. cafe) description or review on your own site with a meaningful slug, link to https://breakfastand.coffee/ and then send a Webmention to indicate that you’d like to syndicate your venue or review into Breakfast & Coffee, like into an aggregator.Before I get to that point however, I feel there’s quite a few challenges in publishing a “decent” restaurant / cafe venue page, because there really is a dearth of good examples of doing so with simple semantic HTML + CSS. You really don’t need JS to post info about a restaurant.Setting aside the economic / intermediation challenges of "delivery apps" for now, people really want a few simple things from a restaurant site / page that could all be marked up with simple semantic HTML (thus resulting in good web search rankings) and styled in a quickly readable and mobile-frie…
link: https://status.blaise.ca/notice/116065
description: 's status on Monday, 24-Apr-2023 16:34:00 EDT
encoded: 🌱 I have long been a fan of @Foursquare.com and @Swarmapp.com, having created many venues, posted many tips, and (checks profile) over 45,000 checkins. I recently joined @happycow.net and before I start posting new vegan (friendly) venues or reviews there, I really need to figure out my own personal site venue pages (including URL design) and review posts design and authoring workflow. I’m pretty sure I can and should post h-review posts as a variant of articles (with usual h-entry markup) with an explicit article name, since most review destinations request a title (name) for the review (e.g. HappyCow, TripAdvisor), and for others with only review text (e.g. Google Maps), I can include the name at the start. Different review destinations have different text requirements (minimum and/or maximum lengths), and I’ll take time to document those first. The first destination I’ll likely try automatically syndicating to is a site created by #IndieWeb community member @jamesg.blog (@capjamesg@indieweb.social): @breakfastand.coffee It’s still quite new, but the thing that makes Breakfast & Coffee innovative and unique is that it encourages you to post your venue (e.g. cafe) description or review on your own site with a meaningful slug, link to https://breakfastand.coffee/ and then send a Webmention to indicate that you’d like to syndicate your venue or review into Breakfast & Coffee, like into an aggregator. Before I get to that point however, I feel there’s quite a few challenges in publishing a “decent” restaurant / cafe venue page, because there really is a dearth of good examples of doing so with simple semantic HTML + CSS. You really don’t need JS to post info about a restaurant. Setting aside the economic / intermediation challenges of "delivery apps" for now, people really want a few simple things from a restaurant site / page that could all be marked up with simple semantic HTML (thus resulting in good web search rankings) and styled in a quickly readable and mobile-…
date: 2023-04-24T16:34:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110171
enclosure: h-cardh-entry
links to: h-cardh-entry
enclosure: Main Page
links to: Main Page
enclosure: a-semantic-breakdown-of-restaurant-menus
links to: a-semantic-breakdown-of-restaurant-menus
enclosure: Indieweb ExamplesThis
links to: Indieweb ExamplesThis
enclosure: account-migration-post-blog-archive-format
links to: account-migration-post-blog-archive-format
enclosure: articlecheckin
links to: articlecheckin
enclosure: checkinh-card
links to: checkinh-card
enclosure: h-entryh-review
links to: h-entryh-review
enclosure: h-reviewPOSSE
links to: h-reviewPOSSE
enclosure: POSSEreview
links to: POSSEreview
enclosure: reviewURL
links to: reviewURL
enclosure: URL designvenue
links to: URL designvenue
enclosure: venueReferences¹
links to: venueReferences¹
enclosure: Whistle
links to: Whistle
enclosure: menu³
links to: menu³
enclosure: menus
links to: menus
tagged: concept

h-cardh-entry
date: 2023-02-16T20:15:30-05:00
type: text/html; charset=UTF-8

Main Page
date: 2023-04-24T19:02:26-04:00
type: text/html; charset=UTF-8

a-semantic-breakdown-of-restaurant-menus
date: 2023-04-24T19:02:27-04:00
type: text/html; charset=UTF-8

Indieweb ExamplesThis
date: 2023-04-24T19:02:28-04:00
type: text/html; charset=UTF-8

account-migration-post-blog-archive-format
date: 2023-04-24T19:02:29-04:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : One of the pretty neat innovations from #Mastodon has been actual, functional, and fairly reliable (from all accounts I’ve seen) distributed system account migration, with the notable exception of post migration, which has additional challenges worth exploring.To be clear, as far as I know, no other blogging (or chat) software, system, or even protocol comes close to achieving the level of functionality described in Mastodon’s documentation:https://docs.joinmastodon.org/user/moving/#migrationIn short, moving:* all your profile information* moving all your followers & followings, transparently * redirecting your old account to your new oneMore at that link. From the docs, it’s clear that quite a bit of thought & consideration went into the design & implementation.Once I had setup #BridgyFed to #federate posts from my own site¹, I myself made use of the this Mastodon feature to migrate from my try-it-out @t@xoxo.zone account to my #IndieWeb @tantek.com (move destination handled by BridgyFed).For me the migration experience was 100%, because I had not posted anything @t@xoxo.zone.The challenge of post migration is not unique to Mastodon, though I believe it goes beyond “simple” export & import support, which is still a good place to start.Mastodon has two forms of posts “export” currently:* RSS feeds, which will get you some number of recent posts, by adding ".rss" to the end of any Mastodon profile URL, e.g. https://indieweb.social/@tchambers.rss* Activity Streams 2.0 JSON, per https://docs.joinmastodon.org/user/moving/#export (note: it currently says “ActivityPub JSON format”, but there is no such thing, #ActivityPub uses the #ActivityStreams 2.0 JSON format and I’ve filed a PR² to fix this in the docs)Lots of software & services import RSS, e.g. #WordPress.As far as I know, nothing (not even Mastodon itself) actually supports importing Activity Streams 2.0.There is a more complete format (with specification!) for exporting & importing blog content:Blog Archive For…
link: https://status.blaise.ca/notice/116064
description: 's status on Saturday, 22-Apr-2023 20:40:00 EDT
encoded: One of the pretty neat innovations from #Mastodon has been actual, functional, and fairly reliable (from all accounts I’ve seen) distributed system account migration, with the notable exception of post migration, which has additional challenges worth exploring. To be clear, as far as I know, no other blogging (or chat) software, system, or even protocol comes close to achieving the level of functionality described in Mastodon’s documentation: https://docs.joinmastodon.org/user/moving/#migration In short, moving: * all your profile information * moving all your followers & followings, transparently * redirecting your old account to your new one More at that link. From the docs, it’s clear that quite a bit of thought & consideration went into the design & implementation. Once I had setup #BridgyFed to #federate posts from my own site¹, I myself made use of the this Mastodon feature to migrate from my try-it-out @t@xoxo.zone account to my #IndieWeb @tantek.com (move destination handled by BridgyFed). For me the migration experience was 100%, because I had not posted anything @t@xoxo.zone. The challenge of post migration is not unique to Mastodon, though I believe it goes beyond “simple” export & import support, which is still a good place to start. Mastodon has two forms of posts “export” currently: * RSS feeds, which will get you some number of recent posts, by adding ".rss" to the end of any Mastodon profile URL, e.g. https://indieweb.social/@tchambers.rss * Activity Streams 2.0 JSON, per https://docs.joinmastodon.org/user/moving/#export (note: it currently says “ActivityPub JSON format”, but there is no such thing, #ActivityPub uses the #ActivityStreams 2.0 JSON format and I’ve filed a PR² to fix this in the docs) Lots of software & services import RSS, e.g. #WordPress. As far as I know, nothing (not even Mastodon itself) actually supports importing Activity Streams 2.0. There is a more complete format (with specification!) for exporting & importing blog content: Bl…
date: 2023-04-22T20:40:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110170
tagged: concept

articlecheckin
date: 2023-04-24T19:02:30-04:00
type: text/html; charset=UTF-8

checkinh-card
date: 2023-04-24T19:02:31-04:00
type: text/html; charset=UTF-8

h-entryh-review
date: 2023-04-24T19:02:32-04:00
type: text/html; charset=UTF-8

h-reviewPOSSE
date: 2023-04-24T19:02:33-04:00
type: text/html; charset=UTF-8

POSSEreview
date: 2023-04-24T19:02:34-04:00
type: text/html; charset=UTF-8

reviewURL
date: 2023-04-24T19:02:34-04:00
type: text/html; charset=UTF-8

URL designvenue
date: 2023-04-24T19:02:35-04:00
type: text/html; charset=UTF-8

venueReferences¹
date: 2023-04-24T19:02:36-04:00
type: text/html; charset=UTF-8

Whistle
date: 2023-04-24T19:02:37-04:00
type: text/html; charset=utf-8

menu³
date: 2023-04-24T19:02:38-04:00
type: text/html;charset=utf-8

menus
date: 2023-04-24T19:02:38-04:00
length: 2541
type: text/html; charset=utf-8

concept
type: Tag
label: activitystreams

concept
type: Tag
label: wordpressas

beyond-mastodon-indieweb-own-domain
type: item
type: MicroblogPost
title: : In https://www.theverge.com/2023/4/20/23689570/activitypub-protocol-standard-social-network, author @pierce@mas.to does an excellent job covering a broad range of #ActivityPub related updates, and goes beyond the usual #Mastodon focus to describe numerous implementations.I was very happy to see that he also clearly communicated several #IndieWeb principles¹, practices, goals, and reasons why². Like this quote: “But the advice you’ll hear from most people in this space is this: own your own domain. Don’t be john@/mastodon.social or anna@/facebook.com. Have a space that is yours, that belongs to you, a username and identity that can’t disappear just because a company goes out of business or sells to a megalomaniac.”and this: “It’s [your own domain is] your YouTube channel name and your TikTok username and your Instagram handle and your phone number and your Twitter @, all in one name.”Great interviews with @stevetex@mozilla.social, @mike@flipboard.social, @dustycloud.org (@cwebber@octodon.social), @evanp.me (@evan@cosocial.ca), @anildash.com (@anildash@me.dm), @coachtony@me.dm, and @manton.org.As Manton said in the article: “If you solve identity with domain names, it makes things easier because it fits the way the web has been for 20 years,”Pierce also noted: “you might soon be able to turn your personal website into your entire social identity online” Already can.I replied to Pierce’s post³ about his article noting this⁴, from #federating directly from my website for the past ~6 months⁵, to over a decade of using it as my social identity with the POSSE method⁶ with various #socialMedia silos.It’s important enough that I’ll repeat part of Pierce’s quote at the top: “own your own domain. Don’t be john@/mastodon.social or anna@/facebook.com. Have a space that is yours” He gets it. Don’t be someone at someone else’s server. Big Chad or Little Chad’s garages⁷ are social media stepping stones towards owning your own domain and IndieWeb presence.We’re here when you’re re…
link: https://status.blaise.ca/notice/116063
description: 's status on Thursday, 20-Apr-2023 20:57:00 EDT
encoded: In https://www.theverge.com/2023/4/20/23689570/activitypub-protocol-standard-social-network, author @pierce@mas.to does an excellent job covering a broad range of #ActivityPub related updates, and goes beyond the usual #Mastodon focus to describe numerous implementations. I was very happy to see that he also clearly communicated several #IndieWeb principles¹, practices, goals, and reasons why². Like this quote: “But the advice you’ll hear from most people in this space is this: own your own domain. Don’t be john@/mastodon.social or anna@/facebook.com. Have a space that is yours, that belongs to you, a username and identity that can’t disappear just because a company goes out of business or sells to a megalomaniac.” and this: “It’s [your own domain is] your YouTube channel name and your TikTok username and your Instagram handle and your phone number and your Twitter @, all in one name.” Great interviews with @stevetex@mozilla.social, @mike@flipboard.social, @dustycloud.org (@cwebber@octodon.social), @evanp.me (@evan@cosocial.ca), @anildash.com (@anildash@me.dm), @coachtony@me.dm, and @manton.org. As Manton said in the article: “If you solve identity with domain names, it makes things easier because it fits the way the web has been for 20 years,” Pierce also noted: “you might soon be able to turn your personal website into your entire social identity online” Already can. I replied to Pierce’s post³ about his article noting this⁴, from #federating directly from my website for the past ~6 months⁵, to over a decade of using it as my social identity with the POSSE method⁶ with various #socialMedia silos. It’s important enough that I’ll repeat part of Pierce’s quote at the top: “own your own domain. Don’t be john@/mastodon.social or anna@/facebook.com. Have a space that is yours” He gets it. Don’t be someone at someone else’s server. Big Chad or Little Chad’s garages⁷ are social media stepping stones towards owning your own domain and IndieWeb presence. We’re here when you…
date: 2023-04-20T20:57:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110169
enclosure: twittermigration-bridgyfed-mastodon-indieweb
links to: twittermigration-bridgyfed-mastodon-indieweb
enclosure: own-your-notes
links to: own-your-notes
enclosure: activitypub-protocol-standard-social-network
links to: activitypub-protocol-standard-social-network
enclosure: This
links to: This
enclosure: years-ago-first-federated-indieweb-thread
links to: years-ago-first-federated-indieweb-thread
enclosure: principles²
links to: principles²
enclosure: why³
links to: why³
enclosure: 110231624819547202⁴
links to: 110231624819547202⁴
enclosure: t1
links to: t1
enclosure: POSSE⁷
links to: POSSE⁷
tagged: concept

twittermigration-bridgyfed-mastodon-indieweb
date: 2022-12-02T15:58:37-05:00
type: text/html; charset=UTF-8

activitypub-protocol-standard-social-network
date: 2023-04-20T23:31:24-04:00
length: 274524
type: text/html; charset=utf-8

This
date: 2023-04-20T23:31:24-04:00
length: 169
type: text/html

years-ago-first-federated-indieweb-thread
date: 2023-04-20T23:31:25-04:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : 10 years ago today the first #federated #IndieWeb comment thread was published and collected peer-to-peer IndieWeb replies across websites without any intermediary, silo or otherwise¹.2013-04-19 @eschnou.com posted a brief note on his personal site with #atMentions of a few domains (putting an '@' sign immediately before a domain name to indicate an explicit cross-web @-mention), which itself was also a first² "Testing #indieweb federation with @waterpigs.co.uk, @aaronparecki.com and @indiewebcamp.com !"When @aaronpk.com was notified and replied from his site within minutes³, it became the first peer-to-peer federated IndieWeb comment thread, at the time using h-entry and Pingback. I blogged about it a few days later⁴.Earlier this year I blogged more observations of all the user interactions that happened on that day and shortly thereafter to make this all work: https://tantek.com/2023/014/t4/domain-first-federated-atmentionUnfortunately Laurent Eschnou’s original post is no longer up, and we only have the Internet Archive copy. However most of the IndieWeb reply posts are still up including Barnaby’s: https://waterpigs.co.uk/notes/1334/The oldest still working federated post and comment thread was second overall, unsurprisingly from @aaronparecki.com⁵, a whole 40 days after Laurent’s first.This is day 37 of #100DaysOfIndieWeb. #100Days #OpenWeb #federation #fediverse← Day 36: https://tantek.com/2023/100/t1/auto-linked-hashtags-federated→ 🔮Glossaryfederation https://indieweb.org/federationh-entry https://microformats.org/wiki/h-entryPingback https://indieweb.org/Pingbackreply post https://indieweb.org/replyReferences¹ https://web.archive.org/web/20130427010301/http://eschnou.com/entry/testing-indieweb-federation-with-waterpigscouk-aaronpareckicom-and--62-24908.html² https://tantek.com/2023/014/t4/domain-first-federated-atmention³ https://aaronparecki.com/2013/04/19/3/indieweb⁴ https://tantek.com/2013/113/b1/first-federated-indieweb-comment-thread⁵ https://aaronpar…
link: https://status.blaise.ca/notice/116061
description: 's status on Wednesday, 19-Apr-2023 20:48:00 EDT
encoded: 10 years ago today the first #federated #IndieWeb comment thread was published and collected peer-to-peer IndieWeb replies across websites without any intermediary, silo or otherwise¹. 2013-04-19 @eschnou.com posted a brief note on his personal site with #atMentions of a few domains (putting an '@' sign immediately before a domain name to indicate an explicit cross-web @-mention), which itself was also a first² "Testing #indieweb federation with @waterpigs.co.uk, @aaronparecki.com and @indiewebcamp.com !" When @aaronpk.com was notified and replied from his site within minutes³, it became the first peer-to-peer federated IndieWeb comment thread, at the time using h-entry and Pingback. I blogged about it a few days later⁴. Earlier this year I blogged more observations of all the user interactions that happened on that day and shortly thereafter to make this all work: https://tantek.com/2023/014/t4/domain-first-federated-atmention Unfortunately Laurent Eschnou’s original post is no longer up, and we only have the Internet Archive copy. However most of the IndieWeb reply posts are still up including Barnaby’s: https://waterpigs.co.uk/notes/1334/ The oldest still working federated post and comment thread was second overall, unsurprisingly from @aaronparecki.com⁵, a whole 40 days after Laurent’s first. This is day 37 of #100DaysOfIndieWeb. #100Days #OpenWeb #federation #fediverse ← Day 36: https://tantek.com/2023/100/t1/auto-linked-hashtags-federated → 🔮 Glossary federation https://indieweb.org/federation h-entry https://microformats.org/wiki/h-entry Pingback https://indieweb.org/Pingback reply post https://indieweb.org/reply References ¹ https://web.archive.org/web/20130427010301/http://eschnou.com/entry/testing-indieweb-federation-with-waterpigscouk-aaronpareckicom-and--62-24908.html ² https://tantek.com/2023/014/t4/domain-first-federated-atmention ³ https://aaronparecki.com/2013/04/19/3/indieweb ⁴ https://tantek.com/2013/113/b1/first-federated-indieweb-comment-thread ⁵…
date: 2023-04-19T20:48:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110167
enclosure: first-federated-indieweb-comment-thread
links to: first-federated-indieweb-comment-thread
enclosure: domain-first-federated-atmention
links to: domain-first-federated-atmention
enclosure: The
links to: The
enclosure: auto-linked-hashtags-federated
links to: auto-linked-hashtags-federated
enclosure: federationh-entry
links to: federationh-entry
enclosure: h-entryPingback
links to: h-entryPingback
enclosure: Pingbackreply
links to: Pingbackreply
enclosure: replyReferences¹
links to: replyReferences¹
links to: testing-indieweb-federation-with-waterpigscouk-aaronpareckicom-and--62-24908.html²
enclosure: indieweb
links to: indieweb
enclosure: xkcd
links to: xkcd
tagged: concept

principles²
date: 2023-04-20T23:31:26-04:00
type: text/html; charset=UTF-8

why³
date: 2023-04-20T23:31:27-04:00
type: text/html; charset=UTF-8

110231624819547202⁴
date: 2023-04-20T23:31:27-04:00
type: text/html; charset=utf-8

t1
date: 2023-04-20T23:31:29-04:00
type: text/html; charset=UTF-8

POSSE⁷
date: 2023-04-20T23:31:30-04:00
type: text/html; charset=UTF-8

concept
type: Tag
label: federating

first-federated-indieweb-comment-thread
date: 2023-01-10T07:07:39-05:00
type: text/html; charset=UTF-8

domain-first-federated-atmention
date: 2023-01-16T07:31:35-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : Previously^1 I asked "How should we @ someone [on the #IndieWeb]?" & suggested we use @-domain. With some web spelunking, the earliest such use I found was 2013-03-26 (~10y ago!) by @eschnou.com, maybe^2 the first #siteToSite #federated #atMention! "And my first ever #indieweb pingback goes to @tantek.com, @aaronparecki.com and @waterpigs.co.uk ! Yes, I can now federate... well.. if I can manage to get it to interop :-)"Though the original post disappeared in a site update (and was unarchived), you can see it on the Internet Archive of @eschnou.com’s #IndieWeb tag page: https://web.archive.org/web/20130609045145/http://eschnou.com/tag/indieweb#2013Mar26At the time, Barnaby (@waterpigs.co.uk) did confirm receiving that @-mention on his site via Pingback (this was before Webmention was a thing^3): https://waterpigs.co.uk/notes/1199/ (https://twitter.com/BarnabyWalters/status/316664943820812289)@eschnou.com also asked in the IndieWeb chat if @aaronparecki.com had gotten his @-domain mention: https://chat.indieweb.org/2013-03-26#t1364333721000000 You can see at the bottom of that chat log that he did.I myself started using @-domain in my posts ~4 years later in a 2017 reply: https://tantek.com/2017/345/t1/aaronpk-paid-thanks (https://twitter.com/t/status/940382393097228288) though only when the same person controlled the domain and the Twitter @-name of the first part of the domain name before the "." (which was/is not many people. Workaround: use other @-domain mentions in posts after the POSSE tweet cut-off).I think that was my earliest use because two days after that post I added @-domain auto-linking to the https://tantek.com/github/cassis (@cassisjs) "auto_link" function https://github.com/tantek/cassis/commit/0e8e6270c0a3b600423c283f59b5d22c3648d59a (https://twitter.com/cassisjs/status/941107922318381057), likely having already tested it in production on my own site with that post.I’m still #testingInProduction the updates noted in ^3, notably "https:" for all @…
link: https://status.blaise.ca/notice/115999
description: 's status on Sunday, 15-Jan-2023 02:50:00 EST
encoded: Previously^1 I asked "How should we @ someone [on the #IndieWeb]?" & suggested we use @-domain. With some web spelunking, the earliest such use I found was 2013-03-26 (~10y ago!) by @eschnou.com, maybe^2 the first #siteToSite #federated #atMention! "And my first ever #indieweb pingback goes to @tantek.com, @aaronparecki.com and @waterpigs.co.uk ! Yes, I can now federate... well.. if I can manage to get it to interop :-)" Though the original post disappeared in a site update (and was unarchived), you can see it on the Internet Archive of @eschnou.com’s #IndieWeb tag page: https://web.archive.org/web/20130609045145/http://eschnou.com/tag/indieweb#2013Mar26 At the time, Barnaby (@waterpigs.co.uk) did confirm receiving that @-mention on his site via Pingback (this was before Webmention was a thing^3): https://waterpigs.co.uk/notes/1199/ (https://twitter.com/BarnabyWalters/status/316664943820812289) @eschnou.com also asked in the IndieWeb chat if @aaronparecki.com had gotten his @-domain mention: https://chat.indieweb.org/2013-03-26#t1364333721000000 You can see at the bottom of that chat log that he did. I myself started using @-domain in my posts ~4 years later in a 2017 reply: https://tantek.com/2017/345/t1/aaronpk-paid-thanks (https://twitter.com/t/status/940382393097228288) though only when the same person controlled the domain and the Twitter @-name of the first part of the domain name before the "." (which was/is not many people. Workaround: use other @-domain mentions in posts after the POSSE tweet cut-off). I think that was my earliest use because two days after that post I added @-domain auto-linking to the https://tantek.com/github/cassis (@cassisjs) "auto_link" function https://github.com/tantek/cassis/commit/0e8e6270c0a3b600423c283f59b5d22c3648d59a (https://twitter.com/cassisjs/status/941107922318381057), likely having already tested it in production on my own site with that post. I’m still #testingInProduction the updates noted in ^3, notably "https:" for a…
date: 2023-01-15T02:50:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110122
tagged: concept

The
date: 2023-04-19T22:24:37-04:00
type: text/html; charset=UTF-8

auto-linked-hashtags-federated
date: 2023-04-19T22:24:38-04:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : About three weeks ago I got auto-linked hashtags working on my posts.The biggest challenge was picking a tag space to link my hashtags. The second biggest challenge was figuring out how to get my linked hashtags to work when my posts were federated into Mastodon instances, and have them rewrite those links into instance-local tag page links. We need a term for such locally rewritten linked hashtags, perhaps “federated hashtags”.While typical personal sites link a hashtag to a tag page that only displays personal posts, I wanted to link to something more like a tag aggregation page that also displayed similar posts from others.The tag pages on Mastodon instances do a good job of this, showing tagged posts from any user on that instance, and tagged posts from any user followed by any user on that instance.I reviewed my hashtags since the start of 2023, checked their pages on indieweb.social and found that the posts displayed were all on topic, and surprisingly free of tag spam (perhaps for now).I chose https://indieweb.social/tags/ for my tag space (which is a 404 if you click it, where it really should display a tags page listing popular or recent tags or a tag cloud). Combining a hashtag like #100DaysOfIndieWeb with a tag space produces a link to a tag page like: https://indieweb.social/tags/100DaysOfIndieWeb.The other interesting thing about hashtag links is how they’re rewritten when a post is displayed on another Mastodon instance, to link to the tag page local to that instance. This linked-hashtag-portability is underspecified unfortunately (it could probably use its own portable markup specification, or at least a best practice for h-entry publishing).How it works in Mastodon is non-obvious enough that there’s a 4+ year old Bridgy Fed issue on the subject!* https://github.com/snarfed/bridgy-fed/issues/45With a bunch of research and experiment contributions from several folks in the issue, @snarfed.org (@schnarfed) did eventually figure out how to get Bridgy F…
link: https://status.blaise.ca/notice/116052
description: 's status on Tuesday, 11-Apr-2023 02:25:00 EDT
encoded: About three weeks ago I got auto-linked hashtags working on my posts. The biggest challenge was picking a tag space to link my hashtags. The second biggest challenge was figuring out how to get my linked hashtags to work when my posts were federated into Mastodon instances, and have them rewrite those links into instance-local tag page links. We need a term for such locally rewritten linked hashtags, perhaps “federated hashtags”. While typical personal sites link a hashtag to a tag page that only displays personal posts, I wanted to link to something more like a tag aggregation page that also displayed similar posts from others. The tag pages on Mastodon instances do a good job of this, showing tagged posts from any user on that instance, and tagged posts from any user followed by any user on that instance. I reviewed my hashtags since the start of 2023, checked their pages on indieweb.social and found that the posts displayed were all on topic, and surprisingly free of tag spam (perhaps for now). I chose https://indieweb.social/tags/ for my tag space (which is a 404 if you click it, where it really should display a tags page listing popular or recent tags or a tag cloud). Combining a hashtag like #100DaysOfIndieWeb with a tag space produces a link to a tag page like: https://indieweb.social/tags/100DaysOfIndieWeb. The other interesting thing about hashtag links is how they’re rewritten when a post is displayed on another Mastodon instance, to link to the tag page local to that instance. This linked-hashtag-portability is underspecified unfortunately (it could probably use its own portable markup specification, or at least a best practice for h-entry publishing). How it works in Mastodon is non-obvious enough that there’s a 4+ year old Bridgy Fed issue on the subject! * https://github.com/snarfed/bridgy-fed/issues/45 With a bunch of research and experiment contributions from several folks in the issue, @snarfed.org (@schnarfed) did eventually figure out how to get B…
date: 2023-04-11T02:25:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110160
tagged: concept

federationh-entry
date: 2023-04-19T22:24:39-04:00
type: text/html; charset=UTF-8

h-entryPingback
date: 2023-04-19T22:24:40-04:00
type: text/html; charset=UTF-8

Pingbackreply
date: 2023-04-19T22:24:40-04:00
type: text/html; charset=UTF-8

replyReferences¹
date: 2023-04-19T22:24:41-04:00
type: text/html; charset=UTF-8

indieweb
date: 2023-04-19T22:24:45-04:00
type: text/html; charset=UTF-8

xkcd
date: 2023-04-19T22:24:48-04:00
type: text/html; charset=UTF-8

concept
type: Tag
label: atmentions

concept
type: Tag
label: federation

concept
type: Tag
label: openweb

concept
type: Tag
label: mozfest

mozfest-making-fediverse-socialweb
type: item
type: MicroblogPost
title: : Watching #MozFest session Dialogues & Debates: Making the Fediverse¹ and panelist @stevetex@mozilla.social (@stevetex) just announced that we (#Mozilla) are standing up a #Mastodon instance², starting with limited sign-ups.I’m excited that Mozilla is experimenting with #socialWeb alternatives to centralized #socialMedia silos.There are many #Mozillians with #fediverse addresses you can follow:* https://wiki.mozilla.org/MastodonSeveral of these folks also have their own #IndieWeb sites. It’s interesting seeing how people are individually choosing to use a fediverse address on someone else’s server, vs their own server like with a subdomain, vs just using their existing site.One trend I have seen is people using someone else’s Mastodon server as a stepping stone, a learning experience, before migrating to either self-hosting Mastodon (or an easier to run alternative like microblog.pub³, not to be confused with micro.blog⁴), or ideally directly using their own site, blog etc. to connect to the fediverse⁵.Do you have an @-@ address and want to use your own site instead?If you’re a #webdev, you can totally do this by connecting your existing personal site with https://fed.brid.gy/ and own your presence on the web, social web, fediverse all at one place.Got questions? Drop by the IndieWeb chat! https://chat.indieweb.org/devThis is day 35 of #100DaysOfIndieWeb #100Days← Day 34: https://tantek.com/2023/072/t1/blog-as-if-ai-trained-posts→ 🔮¹ https://schedule.mozillafestival.org/session/UEEGYL-1² https://mozilla.social/³ https://indieweb.org/microblog.pub⁴ https://indieweb.org/micro.blog⁵ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb
link: https://status.blaise.ca/notice/116045
description: 's status on Wednesday, 22-Mar-2023 11:14:00 EDT
encoded: Watching #MozFest session Dialogues & Debates: Making the Fediverse¹ and panelist @stevetex@mozilla.social (@stevetex) just announced that we (#Mozilla) are standing up a #Mastodon instance², starting with limited sign-ups. I’m excited that Mozilla is experimenting with #socialWeb alternatives to centralized #socialMedia silos. There are many #Mozillians with #fediverse addresses you can follow: * https://wiki.mozilla.org/Mastodon Several of these folks also have their own #IndieWeb sites. It’s interesting seeing how people are individually choosing to use a fediverse address on someone else’s server, vs their own server like with a subdomain, vs just using their existing site. One trend I have seen is people using someone else’s Mastodon server as a stepping stone, a learning experience, before migrating to either self-hosting Mastodon (or an easier to run alternative like microblog.pub³, not to be confused with micro.blog⁴), or ideally directly using their own site, blog etc. to connect to the fediverse⁵. Do you have an @-@ address and want to use your own site instead? If you’re a #webdev, you can totally do this by connecting your existing personal site with https://fed.brid.gy/ and own your presence on the web, social web, fediverse all at one place. Got questions? Drop by the IndieWeb chat! https://chat.indieweb.org/dev This is day 35 of #100DaysOfIndieWeb #100Days ← Day 34: https://tantek.com/2023/072/t1/blog-as-if-ai-trained-posts → 🔮 ¹ https://schedule.mozillafestival.org/session/UEEGYL-1 ² https://mozilla.social/ ³ https://indieweb.org/microblog.pub ⁴ https://indieweb.org/micro.blog ⁵ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb
date: 2023-03-22T11:14:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110156
enclosure: twittermigration-bridgyfed-mastodon-indieweb
links to: twittermigration-bridgyfed-mastodon-indieweb
enclosure: fed.brid.gy
links to: fed.brid.gy
enclosure: devThis
links to: devThis
enclosure: MastodonSeveral
links to: MastodonSeveral
enclosure: UEEGYL-1²
links to: UEEGYL-1²
enclosure: https://mozilla.social/³
links to: https://mozilla.social/³
enclosure: microblog.pub⁴
links to: microblog.pub⁴
enclosure: micro.blog⁵
links to: micro.blog⁵
enclosure: blog-as-if-ai-trained-posts
links to: blog-as-if-ai-trained-posts
tagged: concept

fed.brid.gy
date: 2023-01-09T00:56:28-05:00
length: 4243
type: text/html; charset=utf-8

devThis
date: 2023-01-27T23:33:59-05:00
length: 169
type: text/html

MastodonSeveral
date: 2023-03-22T11:42:06-04:00
length: 118
type: text/html

UEEGYL-1²
date: 2023-03-22T11:42:07-04:00
length: 1268
type: text/html

https://mozilla.social/³
date: 2023-03-22T11:42:09-04:00
type: text/html; charset=utf-8

microblog.pub⁴
date: 2023-03-22T11:42:09-04:00
type: text/html; charset=UTF-8

micro.blog⁵
date: 2023-03-22T11:42:10-04:00
type: text/html; charset=UTF-8

blog-as-if-ai-trained-posts
date: 2023-03-22T11:47:48-04:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : Blog as if there’s an #AI being trained¹ to be you based on your blog posts.And what if it was trained on your Universal Outbox²?#IndieWeb #OpenAI #ChatGPTThis is day 34 of #100DaysOfIndieWeb #100Days← Day 33: https://tantek.com/2023/051/t1/five-years-ago-w3c-social-web→ 🔮¹ https://indieweb.org/OpenAI#IndieWeb_Examples² https://tantek.com/2023/044/t1/unified-sent-box-universal-outbox
link: https://status.blaise.ca/notice/116031
description: 's status on Monday, 13-Mar-2023 19:51:00 EDT
encoded: Blog as if there’s an #AI being trained¹ to be you based on your blog posts. And what if it was trained on your Universal Outbox²? #IndieWeb #OpenAI #ChatGPT This is day 34 of #100DaysOfIndieWeb #100Days ← Day 33: https://tantek.com/2023/051/t1/five-years-ago-w3c-social-web → 🔮 ¹ https://indieweb.org/OpenAI#IndieWeb_Examples ² https://tantek.com/2023/044/t1/unified-sent-box-universal-outbox
date: 2023-03-13T19:51:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110149
enclosure: unified-sent-box-universal-outbox
links to: unified-sent-box-universal-outbox
enclosure: five-years-ago-w3c-social-web
links to: five-years-ago-w3c-social-web
enclosure: IndieWeb Examples²
links to: IndieWeb Examples²
tagged: concept

concept
type: Tag
label: mozillians

concept
type: Tag
label: webdev

unified-sent-box-universal-outbox
date: 2023-02-16T20:15:29-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : 11 days ago I suggested¹ a unified Sent box of everything sent/reacji’d to all Slacks logged-in with the same email. Beyond Slack though, everything you write & send anywhere: txt, chat, email, web. A Universal Outbox of all content you create, including responses. A flat time ordered list of output across mediums. And a source of material to blog.The phrase “Universal Outbox” seemed obvious to describe such a feature, parallel to the idea of a universal inbox that I remember first learning of as a concept from Apple’s AOCE project² in the early 1990s, but called a “single universal mailbox”.Figuring someone must have come up with the idea, I did a web search, and found a minimal wiki page from 2011:http://webseitz.fluxent.com/wiki/UniversalOutboxwhich did vaguely describe the idea: “a single hub where someone can find all your outbound LifeStreams?”Except I don’t want “where someone can”, but rather “where I can”, which is an important distinction, because it would explicitly include things you send to a single person or other limited audience.And yes, “can find”, with full personal search.Aside: the “where someone can” use-case of the presumably more public “all your outbound LifeStreams” is essentially what an #IndieWeb site is for. One place to publish all you want, any way you want, in a composite stream.How many times have you texted, IM’d, Slacked, or emailed nearly the same thing, maybe to different people, retyped from memory, that you could have searched, and copy & pasted instead?Or how many times have you written similar public posts, replies, or emails, on the same topic, where you said the same thing just slightly differently?What if you could publish such common ideas, concepts, points once, with a permalink, and then cite that permalink rather than retyping the same thing repeatedly?The idea of a Universal Outbox feels like a logical extension of many IndieWeb practices such as owning your data³.While all the things you post on your personal site a…
link: https://status.blaise.ca/notice/116017
description: 's status on Tuesday, 14-Feb-2023 01:33:00 EST
encoded: 11 days ago I suggested¹ a unified Sent box of everything sent/reacji’d to all Slacks logged-in with the same email. Beyond Slack though, everything you write & send anywhere: txt, chat, email, web. A Universal Outbox of all content you create, including responses. A flat time ordered list of output across mediums. And a source of material to blog. The phrase “Universal Outbox” seemed obvious to describe such a feature, parallel to the idea of a universal inbox that I remember first learning of as a concept from Apple’s AOCE project² in the early 1990s, but called a “single universal mailbox”. Figuring someone must have come up with the idea, I did a web search, and found a minimal wiki page from 2011: http://webseitz.fluxent.com/wiki/UniversalOutbox which did vaguely describe the idea: “a single hub where someone can find all your outbound LifeStreams?” Except I don’t want “where someone can”, but rather “where I can”, which is an important distinction, because it would explicitly include things you send to a single person or other limited audience. And yes, “can find”, with full personal search. Aside: the “where someone can” use-case of the presumably more public “all your outbound LifeStreams” is essentially what an #IndieWeb site is for. One place to publish all you want, any way you want, in a composite stream. How many times have you texted, IM’d, Slacked, or emailed nearly the same thing, maybe to different people, retyped from memory, that you could have searched, and copy & pasted instead? Or how many times have you written similar public posts, replies, or emails, on the same topic, where you said the same thing just slightly differently? What if you could publish such common ideas, concepts, points once, with a permalink, and then cite that permalink rather than retyping the same thing repeatedly? The idea of a Universal Outbox feels like a logical extension of many IndieWeb practices such as owning your data³. While all the things you post on your perso…
date: 2023-02-14T01:33:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110140
enclosure: responses
links to: responses
enclosure: own your data
links to: own your data
enclosure: footnotes-unicode-links
links to: footnotes-unicode-links
enclosure: composite streammanual-until-it-hurts
links to: composite streammanual-until-it-hurts
enclosure: manual until it hurtspermalink
links to: manual until it hurtspermalink
enclosure: permalinkPESOS
links to: permalinkPESOS
enclosure: PESOSreacji
links to: PESOSreacji
enclosure: reacjiresponses
links to: reacjiresponses
enclosure: t1675370124338700²
links to: t1675370124338700²
enclosure: Apple Open Collaboration Environment³
links to: Apple Open Collaboration Environment³
tagged: concept

five-years-ago-w3c-social-web
date: 2023-03-13T20:34:57-04:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : Five years ago last Monday, the @W3C Social Web Working Group officially closed¹.Operating for less than four years, it standardized several foundations of the #fediverse & #IndieWeb:#Webmention#Micropub#ActivityStreams2#ActivityPubEach of these has numerous interoperable implementations which are in active use by anywhere from thousands to millions of users.Two additional specifications also had several implementations as of the time of their publication as a W3C Recommendations (which you can find from the Implementation Report linked near the top of each spec). However today they’re both fairly invisible "plumbing" (as most specs should be) or they haven’t picked up widespread use like the others:#LinkedDataNotifications (LDN)#WebSubTo be fair, LDN was only one building block in what eventually became SoLiD², the basis of Tim Berners–Lee’s startup Inrupt.However, in the post Elon-acquisition of Twitter and subsequent Twexodus, as Anil Dash noted³, “nobody ran to the ’web3’ platforms”, and nobody ran to SoLiD either.The other spec, WebSub, was roughly interoperably implemented as PubSubHubbub before it was brought to the Social Web Working Group. Yet despite that implementation experience, a more rigorous specification that fixed a lot of bugs, and a test suite⁴, WebSub’s adoption hasn’t really noticeably grown since. Existing implementations & services are still functioning though. My own blog supports WebSub notifications for example, for anyone that wants to receive/read my posts in real time.One of the biggest challenges the Social Web Working Group faced was with so many approaches being brought to the group, which approach should we choose?As one of the co-chairs of the group, with the other co-chairs, and our staff contacts over time, we realized that if we as chairs & facilitators tried to pick any one approach, we would almost certainly alienate and lose more than half of the working group who had already built or were actively interested in developing …
link: https://status.blaise.ca/notice/116020
description: 's status on Monday, 20-Feb-2023 22:16:00 EST
encoded: Five years ago last Monday, the @W3C Social Web Working Group officially closed¹. Operating for less than four years, it standardized several foundations of the #fediverse & #IndieWeb: #Webmention #Micropub #ActivityStreams2 #ActivityPub Each of these has numerous interoperable implementations which are in active use by anywhere from thousands to millions of users. Two additional specifications also had several implementations as of the time of their publication as a W3C Recommendations (which you can find from the Implementation Report linked near the top of each spec). However today they’re both fairly invisible "plumbing" (as most specs should be) or they haven’t picked up widespread use like the others: #LinkedDataNotifications (LDN) #WebSub To be fair, LDN was only one building block in what eventually became SoLiD², the basis of Tim Berners–Lee’s startup Inrupt. However, in the post Elon-acquisition of Twitter and subsequent Twexodus, as Anil Dash noted³, “nobody ran to the ’web3’ platforms”, and nobody ran to SoLiD either. The other spec, WebSub, was roughly interoperably implemented as PubSubHubbub before it was brought to the Social Web Working Group. Yet despite that implementation experience, a more rigorous specification that fixed a lot of bugs, and a test suite⁴, WebSub’s adoption hasn’t really noticeably grown since. Existing implementations & services are still functioning though. My own blog supports WebSub notifications for example, for anyone that wants to receive/read my posts in real time. One of the biggest challenges the Social Web Working Group faced was with so many approaches being brought to the group, which approach should we choose? As one of the co-chairs of the group, with the other co-chairs, and our staff contacts over time, we realized that if we as chairs & facilitators tried to pick any one approach, we would almost certainly alienate and lose more than half of the working group who had already built or were actively interested in…
date: 2023-02-20T22:16:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110143
enclosure: activitypub
links to: activitypub
enclosure: bridgy-indieweb-posse-backfeed
links to: bridgy-indieweb-posse-backfeed
enclosure: use what you make
links to: use what you make
enclosure: devIf
links to: devIf
enclosure: Socialwg
links to: Socialwg
enclosure: And
links to: And
enclosure: nineteen-years-microformats
links to: nineteen-years-microformats
enclosure: activitystreams-core
links to: activitystreams-core
enclosure: Linked
links to: Linked
enclosure: Micropub
links to: Micropub
enclosure: Webmention
links to: Webmention
enclosure: WebSub
links to: WebSub
enclosure: References:¹
links to: References:¹
enclosure: Socialwg²
links to: Socialwg²
enclosure: solid³
links to: solid³
enclosure: 109299991009836007⁴
links to: 109299991009836007⁴
enclosure: https://websub.rocks/⁵
links to: https://websub.rocks/⁵
enclosure: History⁶
links to: History⁶
enclosure: plurality⁸
links to: plurality⁸
tagged: concept

IndieWeb Examples²
date: 2023-03-13T20:34:58-04:00
type: text/html; charset=UTF-8

concept
type: Tag
label: ai

concept
type: Tag
label: chatgptthis

concept
type: Tag
label: openai

activitypub
date: 2017-04-14T08:55:31-04:00
length: 171119
type: text/html; charset=utf-8

bridgy-indieweb-posse-backfeed
date: 2023-01-10T07:07:32-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : 11 years ago today, Ryan Barrett (https://snarfed.org/ @schnarfed) launched Bridgy (https://brid.gy/) to copy #socialmedia replies as comments on original blog posts.This meant those of us building #IndieWeb sites could use a service for that functionality, instead of having to write code ourselves, for each proprietary API.When a few of us originally started syndicating to silos (https://indieweb.org/POSSE), and sometimes reverse-syndicating replies (https://indieweb.org/backfeed), we had to write custom code to do so, calling each social media API (like Twitter) both ways.Bridgy alleviated some of that burden, and over time added support for more silos, sometimes dropping support when they were shutdown (Google+, Buzz) or scuttled their APIs (Facebook).While Bridgy started only with backfeed as a service, it eventually added publishing support, POSSE as a service.Even though I already had code working to POSSE text notes to Twitter, when I added photo posting support to my site, rather than write more code to call Twitter’s API, I started conditionally using Bridgy Publish to POSSE my photo (and video) posts.In 2017, Ryan launched Bridgy Fed (https://fed.brid.gy) which he has substantially improved in the past few months.I and many others now use Bridgy Fed to broadcast to & interact with Mastodon (and other ActivityPub) servers, without having to write any ActivityPub, Webfinger etc. code ourselves.https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indiewebEvery user of Bridgy Fed gets a nice dashboard for notifications and activity. Here’s mine: https://fed.brid.gy/user/tantek.comBridgy is a great example of a project that was started to fulfill a personal need (https://indieweb.org/make_what_you_need), growing to support broader community needs.Read more about Bridgy & Bridgy Fed:* https://indieweb.org/Bridgy (including Publish)* https://indieweb.org/Bridgy_Fed* Launch post: https://snarfed.org/2012-01-08_bridgy_launchedIt’s this hybrid of enc…
link: https://status.blaise.ca/notice/115987
description: 's status on Sunday, 08-Jan-2023 23:43:00 EST
encoded: 11 years ago today, Ryan Barrett (https://snarfed.org/ @schnarfed) launched Bridgy (https://brid.gy/) to copy #socialmedia replies as comments on original blog posts. This meant those of us building #IndieWeb sites could use a service for that functionality, instead of having to write code ourselves, for each proprietary API. When a few of us originally started syndicating to silos (https://indieweb.org/POSSE), and sometimes reverse-syndicating replies (https://indieweb.org/backfeed), we had to write custom code to do so, calling each social media API (like Twitter) both ways. Bridgy alleviated some of that burden, and over time added support for more silos, sometimes dropping support when they were shutdown (Google+, Buzz) or scuttled their APIs (Facebook). While Bridgy started only with backfeed as a service, it eventually added publishing support, POSSE as a service. Even though I already had code working to POSSE text notes to Twitter, when I added photo posting support to my site, rather than write more code to call Twitter’s API, I started conditionally using Bridgy Publish to POSSE my photo (and video) posts. In 2017, Ryan launched Bridgy Fed (https://fed.brid.gy) which he has substantially improved in the past few months. I and many others now use Bridgy Fed to broadcast to & interact with Mastodon (and other ActivityPub) servers, without having to write any ActivityPub, Webfinger etc. code ourselves. https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb Every user of Bridgy Fed gets a nice dashboard for notifications and activity. Here’s mine: https://fed.brid.gy/user/tantek.com Bridgy is a great example of a project that was started to fulfill a personal need (https://indieweb.org/make_what_you_need), growing to support broader community needs. Read more about Bridgy & Bridgy Fed: * https://indieweb.org/Bridgy (including Publish) * https://indieweb.org/Bridgy_Fed * Launch post: https://snarfed.org/2012-01-08_bridgy_launched It’s this …
date: 2023-01-08T23:43:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110113
enclosure: POSSE
links to: POSSE
enclosure: brid.gy
links to: brid.gy
enclosure: snarfed.org
links to: snarfed.org
enclosure: backfeed
links to: backfeed
enclosure: fed.brid.gy
links to: fed.brid.gy
enclosure: tantek.comBridgy
links to: tantek.comBridgy
enclosure: make what you need
links to: make what you need
enclosure: Bridgy
links to: Bridgy
enclosure: Bridgy Fed*
links to: Bridgy Fed*
enclosure: 2012-01-08 bridgy launchedIt
links to: 2012-01-08 bridgy launchedIt
enclosure: more-100daysofindieweb-projects
links to: more-100daysofindieweb-projects
tagged: concept

use what you make
date: 2023-01-22T19:43:21-05:00
type: text/html; charset=UTF-8

devIf
date: 2023-02-16T20:15:28-05:00
length: 169
type: text/html

Socialwg
date: 2023-02-21T04:41:05-05:00
type: text/html; charset=UTF-8

And
date: 2023-02-21T04:41:05-05:00
length: 169
type: text/html

nineteen-years-microformats
date: 2023-02-21T04:41:06-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : Nineteen years ago last Saturday, @KevinMarks.com & I introduced¹ #microformats @OReillyMedia ETech 2004, building on "semantic (x)html".We’ve come a long way since, from methodologies to #microformats2, from publishing to peer-to-peer #IndieWeb use-cases.We named #microformats only after we had established a pattern of real world examples; even our talk proposal was named RealWorldSemantics², and provided examples in that broader theme.This exemplified important implicit values in ordering our efforts:1. get real world things working first, not just theory2. name them after a pattern emerges, not just solo efforts3. grow the pattern with proposals, prototypes, iteration, evolutionThe examples at that point in time:* XFN — using rel-values for blogroll semantics, and the technology that defined rel=me in v1.1³, now the standard for decentralized social media verification on Mastodon⁴, GitHub⁵, elsewhere, and the basis of RelMeAuth⁶* XMDP — XHTML MetaData Profiles, notably using an HTML class⁷ with a particular value 'profile' to indicate presence of a specific semantic structure* XOXO — XHTML Outlines, formalizing existing usage of (X)HTML elements for outlines, also using an HTML class with a particular value 'xoxo' to express a semanticGrowing the pattern:* rel=license — solved page licensing better than before, since widespread adopted* VoteLinks — new rel values, prototyped, only one consuming implementation (since defunct)And further brainstorming:* recommendations — initial rel="recommendation" idea eventually evolved to hReview, and today’s h-review* syndication — helped motivate HTML5 element, eventually led to hAtom, and today’s h-entry* playlists — led to various ideas, proposals, & demos⁸, still not really solved todayThe mid-2000s were a time of eager experimentation, when we were learning that very small bits of markup (yes, hence the name) could be used to build some very useful capabilities on top of the open web platform.A few observations with the…
link: https://status.blaise.ca/notice/116019
description: 's status on Thursday, 16-Feb-2023 20:01:00 EST
encoded: Nineteen years ago last Saturday, @KevinMarks.com & I introduced¹ #microformats @OReillyMedia ETech 2004, building on "semantic (x)html". We’ve come a long way since, from methodologies to #microformats2, from publishing to peer-to-peer #IndieWeb use-cases. We named #microformats only after we had established a pattern of real world examples; even our talk proposal was named RealWorldSemantics², and provided examples in that broader theme. This exemplified important implicit values in ordering our efforts: 1. get real world things working first, not just theory 2. name them after a pattern emerges, not just solo efforts 3. grow the pattern with proposals, prototypes, iteration, evolution The examples at that point in time: * XFN — using rel-values for blogroll semantics, and the technology that defined rel=me in v1.1³, now the standard for decentralized social media verification on Mastodon⁴, GitHub⁵, elsewhere, and the basis of RelMeAuth⁶ * XMDP — XHTML MetaData Profiles, notably using an HTML class⁷ with a particular value 'profile' to indicate presence of a specific semantic structure * XOXO — XHTML Outlines, formalizing existing usage of (X)HTML elements for outlines, also using an HTML class with a particular value 'xoxo' to express a semantic Growing the pattern: * rel=license — solved page licensing better than before, since widespread adopted * VoteLinks — new rel values, prototyped, only one consuming implementation (since defunct) And further brainstorming: * recommendations — initial rel="recommendation" idea eventually evolved to hReview, and today’s h-review * syndication — helped motivate HTML5 element, eventually led to hAtom, and today’s h-entry * playlists — led to various ideas, proposals, & demos⁸, still not really solved today The mid-2000s were a time of eager experimentation, when we were learning that very small bits of markup (yes, hence the name) could be used to build some very useful capabilities on top of the open web platform. A few obse…
date: 2023-02-16T20:01:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110142
enclosure: years-relmeauth-replace-openid
links to: years-relmeauth-replace-openid
enclosure: devIf
links to: devIf
enclosure: microformatsThis
links to: microformatsThis
enclosure: unified-sent-box-universal-outbox
links to: unified-sent-box-universal-outbox
enclosure: h-cardh-entry
links to: h-cardh-entry
enclosure: h-entryh-event
links to: h-entryh-event
enclosure: h-eventh-review
links to: h-eventh-review
enclosure: h-reviewhAtom
links to: h-reviewhAtom
enclosure: hatomhCalendar
links to: hatomhCalendar
enclosure: hcalendarhCard
links to: hcalendarhCard
enclosure: hcardhReview
links to: hcardhReview
enclosure: hreviewrel-license
links to: hreviewrel-license
enclosure: rel-licenserel-tag
links to: rel-licenserel-tag
enclosure: rel-tagrel-values
links to: rel-tagrel-values
enclosure: existing-rel-valuesXFN
links to: existing-rel-valuesXFN
enclosure: XMDP
links to: XMDP
enclosure: descriptionXOXO
links to: descriptionXOXO
enclosure: xoxoPreviously
links to: xoxoPreviously
enclosure: 15-years-ago-introduced-microformats
links to: 15-years-ago-introduced-microformats
enclosure: ten-years-ago-introduced-microformats-etech
links to: ten-years-ago-introduced-microformats-etech
enclosure: years-ago-presented-microformats-etech
links to: years-ago-presented-microformats-etech
links to: 701095802References:¹
enclosure: realworldsemanticspres.html²
links to: realworldsemanticspres.html²
enclosure: d04t1311³
links to: d04t1311³
enclosure: me⁴
links to: me⁴
enclosure: verification⁵
links to: verification⁵
enclosure: 109790530971147702⁶
links to: 109790530971147702⁶
enclosure: why-html-classes-css-class-selectors
links to: why-html-classes-css-class-selectors
enclosure: 2007-12-11-open-media-web
links to: 2007-12-11-open-media-web
tagged: concept

activitystreams-core
date: 2023-02-21T04:41:07-05:00
type: text/html; charset=utf-8

Linked
date: 2023-02-21T04:41:07-05:00
length: 6831
type: text/html;charset=utf-8

Micropub
date: 2023-02-21T04:41:08-05:00
length: 6831
type: text/html;charset=utf-8

Webmention
date: 2023-02-21T04:41:08-05:00
length: 169
type: text/html

WebSub
date: 2023-02-21T04:41:09-05:00
type: text/html; charset=UTF-8

References:¹
date: 2023-02-21T04:41:09-05:00
length: 6831
type: text/html;charset=utf-8

Socialwg²
date: 2023-02-21T04:41:09-05:00
type: text/html; charset=UTF-8

solid³
date: 2023-02-21T04:41:10-05:00
type: text/html; charset=UTF-8

109299991009836007⁴
date: 2023-02-21T04:41:11-05:00
type: text/html; charset=utf-8

https://websub.rocks/⁵
date: 2023-02-21T04:41:16-05:00
type: text/html; charset=UTF-8

History⁶
date: 2023-02-21T04:41:17-05:00
type: text/html; charset=UTF-8

plurality⁸
date: 2023-02-21T04:41:19-05:00
type: text/html; charset=UTF-8

microformatsThis
date: 2023-02-16T20:15:28-05:00
length: 169
type: text/html

h-entryh-event
date: 2023-02-16T20:15:30-05:00
type: text/html; charset=UTF-8

h-eventh-review
date: 2023-02-16T20:15:31-05:00
type: text/html; charset=UTF-8

h-reviewhAtom
date: 2023-02-16T20:15:32-05:00
type: text/html; charset=UTF-8

hatomhCalendar
date: 2023-02-16T20:15:33-05:00
type: text/html; charset=UTF-8

hcalendarhCard
date: 2023-02-16T20:15:34-05:00
type: text/html; charset=UTF-8

hcardhReview
date: 2023-02-16T20:15:35-05:00
type: text/html; charset=UTF-8

hreviewrel-license
date: 2023-02-16T20:15:36-05:00
type: text/html; charset=UTF-8

rel-licenserel-tag
date: 2023-02-16T20:15:37-05:00
type: text/html; charset=UTF-8

rel-tagrel-values
date: 2023-02-16T20:15:38-05:00
type: text/html; charset=UTF-8

existing-rel-valuesXFN
date: 2023-02-16T20:15:38-05:00
type: text/html; charset=UTF-8

XMDP
date: 2023-02-16T20:15:39-05:00
type: text/html; charset=iso-8859-1

descriptionXOXO
date: 2023-02-16T20:15:39-05:00
type: text/html; charset=iso-8859-1

xoxoPreviously
date: 2023-02-16T20:15:40-05:00
type: text/html; charset=UTF-8

15-years-ago-introduced-microformats
date: 2023-02-16T20:15:41-05:00
type: text/html; charset=UTF-8

ten-years-ago-introduced-microformats-etech
date: 2023-02-16T20:15:42-05:00
type: text/html; charset=UTF-8

years-ago-presented-microformats-etech
date: 2023-02-16T20:15:44-05:00
type: text/html; charset=UTF-8

realworldsemanticspres.html²
date: 2023-02-16T20:15:45-05:00
type: text/html; charset=iso-8859-1

d04t1311³
date: 2023-02-16T20:15:45-05:00
length: 62971
type: text/html; charset=utf-8

me⁴
date: 2023-02-16T20:15:46-05:00
type: text/html; charset=UTF-8

verification⁵
date: 2023-02-16T20:15:46-05:00
length: 35792
type: text/html; charset=utf-8

109790530971147702⁶
date: 2023-02-16T20:15:47-05:00
type: text/html; charset=utf-8

why-html-classes-css-class-selectors
date: 2023-02-16T20:15:49-05:00
type: text/html; charset=UTF-8

2007-12-11-open-media-web
date: 2023-02-16T20:15:49-05:00
type: text/html; charset=UTF-8

concept
type: Tag
label: microformats2

responses
date: 2023-01-10T07:07:40-05:00
type: text/html; charset=UTF-8

own your data
date: 2023-01-17T19:26:39-05:00
type: text/html; charset=UTF-8

footnotes-unicode-links
date: 2023-02-14T17:50:22-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : I got auto-Unicode & linking footnotes¹ working!In notes like this post, I can type "^1" (like after the word "footnotes" above) and the code on my server automatically:* turns it into a Unicode superscript '¹'* links it to the expansion at the end of my postSimilarly, I can type "^1" at the start of an expansion line (e.g. at the end of a post) and that code automatically:* turns it into a Unicode superscript '¹'* links it back to the inline referenceSince that code is part of my site’s CASSIS auto_link function², all previous posts with such "^n" style footnotes have also been updated, like my day 6 post³ and since.Clicking an inline footnote reference scrolls to the line with the footnote expansion. Clicking the Unicode superscript number at the start of that expansion scrolls back to the inline footnote reference. I decided to postpone adding the small return arrows '⮐' at the end of a footnote expansions. Linking the superscript numbers to each other works well, and seemed sufficiently discoverable without being distracting.By using post-specific unique prefixes for the footnote reference & expansion links, those links also work even in the presence of more than one post with footnotes, e.g. on my home page⁴. They’re also in my Atom feed entries. I’m curious how the footnotes links in a post work in other contexts, like when viewing in a reader.I also discovered that Unicode superscripts were inconsistent on some platforms, and added a bit of CSS to set an explicit font-family for footnotes numbers:/* CSS style rule to use a specific font for footnote refs and expansions */a[id*='_ref-'],a[id*='_note-'] { font-family:"Arial Unicode MS",system-ui; }/* end of style rule */I added this and some other tips to the #IndieWeb footnote page⁵.This is day 30 of #100DaysOfIndieWeb #100Days← Day 29: https://tantek.com/2023/037/t1/post-glossary→ 🔮¹ https://tantek.com/2023/036/t1/footnotes-unicode-hyperlink² https://tantek.com/cassis.js³ https://tantek.com/2023/006/t1/forw…
link: https://status.blaise.ca/notice/116016
description: 's status on Sunday, 12-Feb-2023 23:06:00 EST
encoded: I got auto-Unicode & linking footnotes¹ working! In notes like this post, I can type "^1" (like after the word "footnotes" above) and the code on my server automatically: * turns it into a Unicode superscript '¹' * links it to the expansion at the end of my post Similarly, I can type "^1" at the start of an expansion line (e.g. at the end of a post) and that code automatically: * turns it into a Unicode superscript '¹' * links it back to the inline reference Since that code is part of my site’s CASSIS auto_link function², all previous posts with such "^n" style footnotes have also been updated, like my day 6 post³ and since. Clicking an inline footnote reference scrolls to the line with the footnote expansion. Clicking the Unicode superscript number at the start of that expansion scrolls back to the inline footnote reference. I decided to postpone adding the small return arrows '⮐' at the end of a footnote expansions. Linking the superscript numbers to each other works well, and seemed sufficiently discoverable without being distracting. By using post-specific unique prefixes for the footnote reference & expansion links, those links also work even in the presence of more than one post with footnotes, e.g. on my home page⁴. They’re also in my Atom feed entries. I’m curious how the footnotes links in a post work in other contexts, like when viewing in a reader. I also discovered that Unicode superscripts were inconsistent on some platforms, and added a bit of CSS to set an explicit font-family for footnotes numbers: /* CSS style rule to use a specific font for footnote refs and expansions */ a[id*='_ref-'],a[id*='_note-'] { font-family:"Arial Unicode MS",system-ui; } /* end of style rule */ I added this and some other tips to the #IndieWeb footnote page⁵. This is day 30 of #100DaysOfIndieWeb #100Days ← Day 29: https://tantek.com/2023/037/t1/post-glossary → 🔮 ¹ https://tantek.com/2023/036/t1/footnotes-unicode-hyperlink ² https://tantek.com/cassis.js ³ https://tantek.co…
date: 2023-02-12T23:06:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110139
enclosure: forward-in-time-links
links to: forward-in-time-links
enclosure: footnotes-unicode-hyperlink
links to: footnotes-unicode-hyperlink
enclosure: post-glossary
links to: post-glossary
enclosure: cassis.js³
links to: cassis.js³
enclosure: https://tantek.com/⁵
links to: https://tantek.com/⁵
enclosure: footnote
links to: footnote
tagged: concept

composite streammanual-until-it-hurts
date: 2023-02-14T17:50:23-05:00
type: text/html; charset=UTF-8

manual until it hurtspermalink
date: 2023-02-14T17:50:24-05:00
type: text/html; charset=UTF-8

permalinkPESOS
date: 2023-02-14T17:50:25-05:00
type: text/html; charset=UTF-8

PESOSreacji
date: 2023-02-14T17:50:26-05:00
type: text/html; charset=UTF-8

reacjiresponses
date: 2023-02-14T17:50:27-05:00
type: text/html; charset=UTF-8

t1675370124338700²
date: 2023-02-14T17:50:28-05:00
type: text/html; charset=utf-8

Apple Open Collaboration Environment³
date: 2023-02-14T17:50:28-05:00
type: text/html; charset=UTF-8

forward-in-time-links
date: 2023-01-08T05:17:05-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : https://dangillmor.com/ wishes for "forward-in-time links so we could read … his 2023 #100Days project, #100DaysOfIndieWeb … more easily from the beginning" https://mastodon.social/@dangillmor/109646621709452885Great suggestion Dan. Wish granted. On my #IndieWeb site, I control the user experience.Since 2010^1, I’ve had previous/next ( ← → ) temporal^2 navigation links on the top right of my post permalinks, across all posts (something I always wanted on my notes, and Twitter lacked)In 2018^3, I added similar ( ← → ) links on day archive pages, for previous/next days.Ideally I’d build similar automatic ( ← → ) links for each hashtag in a post, for the previous/next post with that same hashtag.OR for now I could manually add forward-in-time links to the bottom of my five previous #100DaysOfIndieWeb posts, and with each subsequent post, remember to update the previous one. So that’s what I did, am doing, per https://indieweb.org/manual_until_it_hurts.Previous #100DaysOfIndieWeb posts updated.This is day 6 of #100DaysOfIndieWeb #100Days, which is now a https://en.wikipedia.org/wiki/Doubly_linked_list← Day 5: https://tantek.com/2023/005/t3/indieweb-simpler-approach→ 🔮Previously, previously, previously:^1 https://tantek.com/2010/032/t7/inventions-to-tweet-from-site^2 https://tantek.com/2011/102/t2/navigation-arrows-back-past-forward-future-ui-pattern^3 https://tantek.com/2018/308/t2/indiewebcamp-archive-navigation-day-archives
link: https://status.blaise.ca/notice/115985
description: 's status on Saturday, 07-Jan-2023 02:59:00 EST
encoded: https://dangillmor.com/ wishes for "forward-in-time links so we could read … his 2023 #100Days project, #100DaysOfIndieWeb … more easily from the beginning" https://mastodon.social/@dangillmor/109646621709452885 Great suggestion Dan. Wish granted. On my #IndieWeb site, I control the user experience. Since 2010^1, I’ve had previous/next ( ← → ) temporal^2 navigation links on the top right of my post permalinks, across all posts (something I always wanted on my notes, and Twitter lacked) In 2018^3, I added similar ( ← → ) links on day archive pages, for previous/next days. Ideally I’d build similar automatic ( ← → ) links for each hashtag in a post, for the previous/next post with that same hashtag. OR for now I could manually add forward-in-time links to the bottom of my five previous #100DaysOfIndieWeb posts, and with each subsequent post, remember to update the previous one. So that’s what I did, am doing, per https://indieweb.org/manual_until_it_hurts. Previous #100DaysOfIndieWeb posts updated. This is day 6 of #100DaysOfIndieWeb #100Days, which is now a https://en.wikipedia.org/wiki/Doubly_linked_list ← Day 5: https://tantek.com/2023/005/t3/indieweb-simpler-approach → 🔮 Previously, previously, previously: ^1 https://tantek.com/2010/032/t7/inventions-to-tweet-from-site ^2 https://tantek.com/2011/102/t2/navigation-arrows-back-past-forward-future-ui-pattern ^3 https://tantek.com/2018/308/t2/indiewebcamp-archive-navigation-day-archives
date: 2023-01-07T02:59:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110111
tagged: concept

footnotes-unicode-hyperlink
date: 2023-02-06T21:15:09-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : In recent posts I’ve used ASCII footnotes like "^1" to indicate more information about a subject in a footnote line starting with "^1" at the bottom of the post.Both inline refs & footer notes should use Unicode superscripts like '¹' and hyperlink both ways, in contexts that support it.I have heard feedback from the #IndieWeb community that inline ASCII footnotes like "^1" are distracting and interrupt the flow of reading, and I can sympathize with that.From an authoring perspective, it’s easier to type "^2" than "²" so I’d rather keep doing so, and write code to do the conversion.I’m also considering what to change as an author, like instead of footnoting special terms/jargon, I can include them in an mini-glossary at the end of a post, thus only using footnotes for specific points or citations. I won’t include terms that mean exactly the same thing as defined by a literal page of the same name on Wikipedia (e.g. ASCII in this post means https://enwp.org/ASCII).During a run I figured out how my existing CASSIS autolink function could detect both inline footnote references and their expansions, convert them to Unicode, and add local hyperlinks in both directions, given an optional parameter to prefix their fragment IDs. I looked at Wikipedia’s references and fragments for examples, and they use "_ref-{number}" and "_note-{number}" respectively which seem sensible. The one Wikipedia design aspect I disagree with is their use of a hat character '^' at the *start* of a reference note to link back to the inline reference, which look distracting, and in my opinion are too subtle/unobvious. I prefer what I’ve seen on blogs: a small return arrow '⮐' at the *end* of a note to link back to the inline reference, which does a much better job of conveying the meaning of “return to where this was referenced / you were reading.”Lastly, I think it’s ok if POSSE copies of my posts to text-only (non-hyperlinking) destinations keep the ASCII footnote style, because such copies usua…
link: https://status.blaise.ca/notice/116014
description: 's status on Monday, 06-Feb-2023 02:40:00 EST
encoded: In recent posts I’ve used ASCII footnotes like "^1" to indicate more information about a subject in a footnote line starting with "^1" at the bottom of the post. Both inline refs & footer notes should use Unicode superscripts like '¹' and hyperlink both ways, in contexts that support it. I have heard feedback from the #IndieWeb community that inline ASCII footnotes like "^1" are distracting and interrupt the flow of reading, and I can sympathize with that. From an authoring perspective, it’s easier to type "^2" than "²" so I’d rather keep doing so, and write code to do the conversion. I’m also considering what to change as an author, like instead of footnoting special terms/jargon, I can include them in an mini-glossary at the end of a post, thus only using footnotes for specific points or citations. I won’t include terms that mean exactly the same thing as defined by a literal page of the same name on Wikipedia (e.g. ASCII in this post means https://enwp.org/ASCII). During a run I figured out how my existing CASSIS autolink function could detect both inline footnote references and their expansions, convert them to Unicode, and add local hyperlinks in both directions, given an optional parameter to prefix their fragment IDs. I looked at Wikipedia’s references and fragments for examples, and they use "_ref-{number}" and "_note-{number}" respectively which seem sensible. The one Wikipedia design aspect I disagree with is their use of a hat character '^' at the *start* of a reference note to link back to the inline reference, which look distracting, and in my opinion are too subtle/unobvious. I prefer what I’ve seen on blogs: a small return arrow '⮐' at the *end* of a note to link back to the inline reference, which does a much better job of conveying the meaning of “return to where this was referenced / you were reading.” Lastly, I think it’s ok if POSSE copies of my posts to text-only (non-hyperlinking) destinations keep the ASCII footnote style, because such copies …
date: 2023-02-06T02:40:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110137
enclosure: ASCII).During
links to: ASCII).During
enclosure: twitter-api-log-in-web-sign-in-relmeauth
links to: twitter-api-log-in-web-sign-in-relmeauth
enclosure: autolinkCASSIS
links to: autolinkCASSIS
enclosure: CASSISPOSSE
links to: CASSISPOSSE
enclosure: POSSEUnicode
links to: POSSEUnicode
enclosure: Superscripts and Subscripts (Unicode block)
links to: Superscripts and Subscripts (Unicode block)
tagged: concept

post-glossary
date: 2023-02-13T07:12:48-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : Taking a closer look at both my syntax and use-cases of footnotes in posts^1 revealed that a post glossary would suffice in many instances.In reviewing my #100DaysOfIndieWeb footnotes, I found:1. citations in reference to “since” a date (or year)2. citations providing deeper points beyond the definition of a term3. citations substantiating a point or assertion4. citations to an earlier post providing context for a term, phrase, summary5. links to the #IndieWeb community site for a definition of a term or phrase6. links to a Wikipedia article that defines a term in a section7. links to open source software defining a functionThe latter three (5,6,7) make more sense as part of a post glossary rather than references footnotes. Using a post glossary in previous #100DaysOfIndieWeb posts would have reduced the need for footnotes, in some case up to half of them per post.There’s one more silent use-case which helped inform when I would use those (5,6,7):8. implicit absence of linking/defining jargon where a Wikipedia look-up would sufficeThis analysis led me to a five-step if/else for when/how to add a term to a post glossary:When I use an unobvious (like jargon) term or phrase in prose:1. If looking it up literally in Wikipedia (prepending it with https://enwp.org/) provides the meaning I intend (e.g. https://enwp.org/jargon), then do nothing with it and trust readers will look it up if they need to.2. Else if an unobvious Wikipedia link would convey the intended meaning (e.g. to another page or a specific section), then add that to a glossary3. Else if the IndieWeb wiki definition conveys the intended meaning (and is expected to in the future), then add an IndieWeb wiki link to a glossary4. Else if there is an open source software or other reliable reference that conveys the intended meaning (and is expected to in the future), then add a link to that to a glossary5. Else define the term in a glossary entry, and contribute that somewhere I can link to in the future.In m…
link: https://status.blaise.ca/notice/116015
description: 's status on Monday, 06-Feb-2023 20:04:00 EST
encoded: Taking a closer look at both my syntax and use-cases of footnotes in posts^1 revealed that a post glossary would suffice in many instances. In reviewing my #100DaysOfIndieWeb footnotes, I found: 1. citations in reference to “since” a date (or year) 2. citations providing deeper points beyond the definition of a term 3. citations substantiating a point or assertion 4. citations to an earlier post providing context for a term, phrase, summary 5. links to the #IndieWeb community site for a definition of a term or phrase 6. links to a Wikipedia article that defines a term in a section 7. links to open source software defining a function The latter three (5,6,7) make more sense as part of a post glossary rather than references footnotes. Using a post glossary in previous #100DaysOfIndieWeb posts would have reduced the need for footnotes, in some case up to half of them per post. There’s one more silent use-case which helped inform when I would use those (5,6,7): 8. implicit absence of linking/defining jargon where a Wikipedia look-up would suffice This analysis led me to a five-step if/else for when/how to add a term to a post glossary: When I use an unobvious (like jargon) term or phrase in prose: 1. If looking it up literally in Wikipedia (prepending it with https://enwp.org/) provides the meaning I intend (e.g. https://enwp.org/jargon), then do nothing with it and trust readers will look it up if they need to. 2. Else if an unobvious Wikipedia link would convey the intended meaning (e.g. to another page or a specific section), then add that to a glossary 3. Else if the IndieWeb wiki definition conveys the intended meaning (and is expected to in the future), then add an IndieWeb wiki link to a glossary 4. Else if there is an open source software or other reliable reference that conveys the intended meaning (and is expected to in the future), then add a link to that to a glossary 5. Else define the term in a glossary entry, and contribute that somewhere I can link to in…
date: 2023-02-06T20:04:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110138
tagged: concept

cassis.js³
date: 2023-02-13T07:12:51-05:00
type: text/html; charset=iso-8859-1

https://tantek.com/⁵
date: 2023-02-13T07:12:53-05:00
type: text/html; charset=iso-8859-1

footnote
date: 2023-02-13T07:12:54-05:00
type: text/html; charset=UTF-8

ASCII).During
date: 2023-02-06T15:00:40-05:00
type: text/html; charset=UTF-8

twitter-api-log-in-web-sign-in-relmeauth
date: 2023-02-06T15:00:42-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : Imminent end of free use^1 of the Twitter API likely also means the end of free Log in with Twitter^2 delegated signin service^3.If you use [Sign in with Twitter]^4, consider replacing it with Web sign-in^5, implementing #RelMeAuth^6 & #IndieAuth^7 (OAuth for the #openWeb^8) ASAP!If you already have your own domain (got get one^9), add a link from your home page to your GitHub profile with rel=me^10, and then test it by using your domain to sign-in to:* https://indielogin.com/* https://indieweb.org/Any challenges or questions? Ask in #IndieWeb chat: https://chat.indieweb.org/devThis is day 27 of #100DaysOfIndieWeb #100Days← Day 26: https://tantek.com/2023/032/t1/years-relmeauth-replace-openid→ 🔮^1 https://www.theverge.com/2023/2/2/23582615/twitter-removing-free-api-developer-apps-price-announcement^2 https://indieweb.org/Log_in_with_Twitter^3 https://indieweb.org/silo_sign-in^4 https://indieweb.org/Log_in_with_Twitter#Button^5 https://indieweb.org/Web_sign-in^6 https://tantek.com/2023/032/t1/years-relmeauth-replace-openid^7 https://indieauth.spec.indieweb.org/^8 https://indieauth.net/^9 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb^10 https://indieweb.org/How_to_set_up_web_sign-in_on_your_own_domain#How_to_setup_RelMeAuth
link: https://status.blaise.ca/notice/116013
description: 's status on Friday, 03-Feb-2023 02:59:00 EST
encoded: Imminent end of free use^1 of the Twitter API likely also means the end of free Log in with Twitter^2 delegated signin service^3. If you use [Sign in with Twitter]^4, consider replacing it with Web sign-in^5, implementing #RelMeAuth^6 & #IndieAuth^7 (OAuth for the #openWeb^8) ASAP! If you already have your own domain (got get one^9), add a link from your home page to your GitHub profile with rel=me^10, and then test it by using your domain to sign-in to: * https://indielogin.com/ * https://indieweb.org/ Any challenges or questions? Ask in #IndieWeb chat: https://chat.indieweb.org/dev This is day 27 of #100DaysOfIndieWeb #100Days ← Day 26: https://tantek.com/2023/032/t1/years-relmeauth-replace-openid → 🔮 ^1 https://www.theverge.com/2023/2/2/23582615/twitter-removing-free-api-developer-apps-price-announcement ^2 https://indieweb.org/Log_in_with_Twitter ^3 https://indieweb.org/silo_sign-in ^4 https://indieweb.org/Log_in_with_Twitter#Button ^5 https://indieweb.org/Web_sign-in ^6 https://tantek.com/2023/032/t1/years-relmeauth-replace-openid ^7 https://indieauth.spec.indieweb.org/ ^8 https://indieauth.net/ ^9 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb ^10 https://indieweb.org/How_to_set_up_web_sign-in_on_your_own_domain#How_to_setup_RelMeAuth
date: 2023-02-03T02:59:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110136
tagged: concept

autolinkCASSIS
date: 2023-02-06T15:00:43-05:00
type: text/html; charset=UTF-8

CASSISPOSSE
date: 2023-02-06T15:00:44-05:00
type: text/html; charset=UTF-8

POSSEUnicode
date: 2023-02-06T15:00:44-05:00
type: text/html; charset=UTF-8

Superscripts and Subscripts (Unicode block)
date: 2023-02-06T15:00:45-05:00
length: 70329
type: text/html; charset=UTF-8

concept
type: Tag
label: indieauth

concept
type: Tag
label: relmeauth

RelMeAuth
date: 2023-02-01T19:49:00-05:00
type: text/html; charset=UTF-8

RelMeAuthSee
date: 2023-02-01T19:49:01-05:00
type: text/html; charset=UTF-8

tantek
date: 2023-02-01T19:49:02-05:00
type: text/html; charset=utf-8

https://micro.blog/t
date: 2023-02-01T19:49:03-05:00
length: 6598
type: text/html;charset=utf-8

indieweb-beyond-blogging
date: 2023-02-01T19:49:04-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : Is the #IndieWeb just blogs/blogging?What if I told you the "indie web"^1 is older than "blog" or "weblog"^2?The IndieWeb, as it says on the homepage^3, also goes beyond blogging^4.And those are just the terms.It should come as no surprise that conceptually:personal sites in general, predated personal sites with reverse-chronologically-ordered dated entries.Good concepts, even if forgotten, tend to be rediscovered & reinvented over time.When I first used the phrase "indie web" (two words) in 2010^5, I used it descriptively, an informal shorthand for the "independent web". I didn’t find out about the 1997^1 use of the phrase until many years later.I saw & was a fan of the 2001 launch of the "Independents Day" site & its manifesto^6 (at independentsday(.)org, since offline) that asked “if you create^7 your own site”, to join them. That encouragement stuck with me, and was a source of inspiration nine years later.In my presentation^8 at the 2010 Federated Social Web Summit^9, I referenced the "indie web" again, and afterwards I proposed to @aaronparecki.com that we start something focused on explicit principles & practices.^10 After subsequent chats & discussions, we settled on the term “IndieWeb” (one word). We started with three essential principles/practices, in today’s terms: “create”, “use what you make”, and “own your data”, which the community eventually expanded into 11 principles^11.This brings us back to the original question, is the #IndieWeb just blogs/blogging?In short no. Seemingly paradoxically, blogging is neither required nor sufficient to “be” IndieWeb as we use the term today.Are IndieWeb sites blogs?Some (perhaps even most) of them are. However, there are plenty of personal sites that are just a homepage^12, or a handful of static pages like a portfolio^13.Are blogs IndieWeb sites?Some of them are, if they are personal blogs, or other forms of independent sites, like small organizations with their own blogs, on their own domains. However the conce…
link: https://status.blaise.ca/notice/116010
description: 's status on Sunday, 29-Jan-2023 23:42:00 EST
encoded: Is the #IndieWeb just blogs/blogging? What if I told you the "indie web"^1 is older than "blog" or "weblog"^2? The IndieWeb, as it says on the homepage^3, also goes beyond blogging^4. And those are just the terms. It should come as no surprise that conceptually: personal sites in general, predated personal sites with reverse-chronologically-ordered dated entries. Good concepts, even if forgotten, tend to be rediscovered & reinvented over time. When I first used the phrase "indie web" (two words) in 2010^5, I used it descriptively, an informal shorthand for the "independent web". I didn’t find out about the 1997^1 use of the phrase until many years later. I saw & was a fan of the 2001 launch of the "Independents Day" site & its manifesto^6 (at independentsday(.)org, since offline) that asked “if you create^7 your own site”, to join them. That encouragement stuck with me, and was a source of inspiration nine years later. In my presentation^8 at the 2010 Federated Social Web Summit^9, I referenced the "indie web" again, and afterwards I proposed to @aaronparecki.com that we start something focused on explicit principles & practices.^10 After subsequent chats & discussions, we settled on the term “IndieWeb” (one word). We started with three essential principles/practices, in today’s terms: “create”, “use what you make”, and “own your data”, which the community eventually expanded into 11 principles^11. This brings us back to the original question, is the #IndieWeb just blogs/blogging? In short no. Seemingly paradoxically, blogging is neither required nor sufficient to “be” IndieWeb as we use the term today. Are IndieWeb sites blogs? Some (perhaps even most) of them are. However, there are plenty of personal sites that are just a homepage^12, or a handful of static pages like a portfolio^13. Are blogs IndieWeb sites? Some of them are, if they are personal blogs, or other forms of independent sites, like small organizations with their own blogs, on their own domains. Howe…
date: 2023-01-29T23:42:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110133
enclosure: https://twitter.com/t/status/13329370781
links to: https://twitter.com/t/status/13329370781
enclosure: own-your-notes
links to: own-your-notes
enclosure: homepage
links to: homepage
enclosure: creator
links to: creator
enclosure: principles
links to: principles
enclosure: contrast-domain-chat-name
links to: contrast-domain-chat-name
enclosure: article63.html
links to: article63.html
enclosure: History
links to: History
enclosure: Beyond Blogging and Decentralization
links to: Beyond Blogging and Decentralization
enclosure: different
links to: different
enclosure: blogger-turned-off-ftp-what-indie-web-diso
links to: blogger-turned-off-ftp-what-indie-web-diso
enclosure: Independents Day
links to: Independents Day
links to: 2010-199-tantek-fsws-talk
enclosure: Portland 2010
links to: Portland 2010
enclosure: IndieWeb movement and terminology
links to: IndieWeb movement and terminology
enclosure: portfolio
links to: portfolio
tagged: concept

modest-proposal-authentication-oauth-twitter-rel-me
date: 2023-02-01T19:49:05-05:00
type: text/html; charset=UTF-8

https://twitter.com/progrium/status/8521001762
date: 2023-02-01T19:49:05-05:00
type: text/html; charset=utf-8

relmeauth-oauth-rel-me-auto-fallback-authentication
date: 2023-02-01T19:49:07-05:00
type: text/html; charset=UTF-8

https://hachyderm.io/@nova/109790530971147702
date: 2023-02-01T19:49:08-05:00
type: text/html; charset=utf-8

redirected-github-ownyourlinks
date: 2023-02-01T19:49:09-05:00
type: text/html; charset=UTF-8

https://twitter.com/t/status/13329370781
date: 2020-05-04T01:01:52-04:00
length: 347942
type: text/html;charset=utf-8

homepage
date: 2023-01-14T04:42:23-05:00
type: text/html; charset=UTF-8

creator
date: 2023-01-14T04:42:28-05:00
type: text/html; charset=UTF-8

principles
date: 2023-01-27T05:10:04-05:00
type: text/html; charset=UTF-8

contrast-domain-chat-name
date: 2023-01-30T06:06:50-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : Another interesting contrast^1 in the #IndieWeb community is that most of us have both:* a domain name^2 — for posting our content, replies, likes etc.* a chat-name^3 — for chatting in our discussion channels^4Ideally, we would have a discussion system that “just” used our domain names as identities (IndieAuth^5 for Web sign-in^6) to chat with each other, but no such system exists (yet).No we’re not going to all setup XMPP servers on our domains and attempt to hook them all up. Nearly no one wants to pay that admintax^7. Nor would XMPP let us “just” use our domain names. Like email, XMPP requires a separate “username”. Sure we could fake it like Bridgy Fed does for us with 'domain @ domain', but why would we work harder for a worse UX?So instead of making things more complex than domains, we took the opposite approach, and based our chat on IRC, and our chat-names on plain nicknames.Using a chat system like IRC lowered the barrier to participation in the IndieWeb community, so you could for example, ask about how to pick a domain name^2 instead of being stuck in an actual catch-22^1 of needing a domain name just to ask about a domain name.By putting our chat archives on the web^8, we were able to reduce our chat system requirements, provide a simple minimal web app for brief chats, and bridge our IRC channels with multiple other chat systems, like Slack, Matrix, and even Discord^9. This has the significant advantage of much greater chat client choice for community members.However, we did realize that our statements in the chat archives^8 could be more closely tied to our domain identities, including our personal icons^10. Rather than a complex system or new protocol, we just put our flat list of nicknames in templates with images & domains on the wiki^11.Thus our chat archives, despite being based on IRC, show icons for people, and link their chat nicknames to their personal domain names, again striking a pragmatic balance.^1The flexibility of using a wiki templat…
link: https://status.blaise.ca/notice/116009
description: 's status on Saturday, 28-Jan-2023 02:11:00 EST
encoded: Another interesting contrast^1 in the #IndieWeb community is that most of us have both: * a domain name^2 — for posting our content, replies, likes etc. * a chat-name^3 — for chatting in our discussion channels^4 Ideally, we would have a discussion system that “just” used our domain names as identities (IndieAuth^5 for Web sign-in^6) to chat with each other, but no such system exists (yet). No we’re not going to all setup XMPP servers on our domains and attempt to hook them all up. Nearly no one wants to pay that admintax^7. Nor would XMPP let us “just” use our domain names. Like email, XMPP requires a separate “username”. Sure we could fake it like Bridgy Fed does for us with 'domain @ domain', but why would we work harder for a worse UX? So instead of making things more complex than domains, we took the opposite approach, and based our chat on IRC, and our chat-names on plain nicknames. Using a chat system like IRC lowered the barrier to participation in the IndieWeb community, so you could for example, ask about how to pick a domain name^2 instead of being stuck in an actual catch-22^1 of needing a domain name just to ask about a domain name. By putting our chat archives on the web^8, we were able to reduce our chat system requirements, provide a simple minimal web app for brief chats, and bridge our IRC channels with multiple other chat systems, like Slack, Matrix, and even Discord^9. This has the significant advantage of much greater chat client choice for community members. However, we did realize that our statements in the chat archives^8 could be more closely tied to our domain identities, including our personal icons^10. Rather than a complex system or new protocol, we just put our flat list of nicknames in templates with images & domains on the wiki^11. Thus our chat archives, despite being based on IRC, show icons for people, and link their chat nicknames to their personal domain names, again striking a pragmatic balance.^1 The flexibility of using a wiki…
date: 2023-01-28T02:11:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110132
enclosure: bottom
links to: bottom
enclosure: choosing-domain-name-indieweb
links to: choosing-domain-name-indieweb
enclosure: indieweb-priorities-balance
links to: indieweb-priorities-balance
enclosure: five-years-websub
links to: five-years-websub
enclosure: chat-names
links to: chat-names
enclosure: discuss
links to: discuss
enclosure: IndieAuth
links to: IndieAuth
enclosure: Web sign-in
links to: Web sign-in
enclosure: admintax
links to: admintax
enclosure: Join Discussions
links to: Join Discussions
enclosure: icon
links to: icon
enclosure: Nicknames
links to: Nicknames
enclosure: code-of-conduct
links to: code-of-conduct
tagged: concept

article63.html
date: 2023-01-30T06:06:58-05:00
length: 24857
type: text/html

History
date: 2023-01-30T06:07:06-05:00
length: 306471
type: text/html; charset=UTF-8

Beyond Blogging and Decentralization
date: 2023-01-30T06:07:06-05:00
type: text/html; charset=UTF-8

different
date: 2023-01-30T06:07:07-05:00
type: text/html; charset=UTF-8

blogger-turned-off-ftp-what-indie-web-diso
date: 2023-01-30T06:07:08-05:00
type: text/html; charset=UTF-8

Independents Day
date: 2023-01-30T06:07:09-05:00
type: text/html; charset=UTF-8

Portland 2010
date: 2023-01-30T06:07:20-05:00
type: text/html; charset=UTF-8

IndieWeb movement and terminology
date: 2023-01-30T06:07:21-05:00
type: text/html; charset=UTF-8

portfolio
date: 2023-01-30T06:07:25-05:00
type: text/html; charset=UTF-8

bottom
date: 2020-01-02T00:13:25-05:00
type: text/html; charset=utf-8

choosing-domain-name-indieweb
date: 2023-01-06T07:17:04-05:00
type: text/html; charset=UTF-8

indieweb-priorities-balance
date: 2023-01-27T23:34:00-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : There are many opposing forces in the #IndieWeb that can seem like catch-22s, yet help clarify priorities, and balance present pragmatism & future optimism.* Indie, yet often on corporate infrastructure* Independent, yet dependent on community * Own your content^1, yet share publicly, perhaps CC0^2* Control of your design^3, yet lack of control elsewhere^4* UX freedom & creativity, yet guidance toward common patterns for usability* Decentralized, yet DNS* Make what you need^5, yet open source^6 for others* Plurality^7 of projects, yet conforming to standards^8* Build it yourself, yet use services, software, & libraries built by othersThese are a few off the top of my head and implied by the IndieWeb wiki home page^9 and principles^10.Rather than contradictions, these tensions are a source of inquiry, questions, and conversations.Each could be expanded into their own discussion or exploration.Each of them is an axis of sorts, with different “right” answers for different people, depending on what they want, and how much time or other resources they have.Each makes the most sense when explored in the context of a focus on solving real user needs to participate directly on today’s web.Each is also a trap for abstract logic, theoretical purity, or dogmatic absolutism, especially when detached from real world goals, constraints, and efforts.This is day 22 of #100DaysOfIndieWeb #100Days, written after a break. Many double days ahead.← Day 21: https://tantek.com/2023/022/t2/own-your-notes-domain-migration→ 🔮^1 https://tantek.com/2023/001/t1/own-your-notes^2 https://indieweb.org/IndieWeb:Copyrights^3 https://indieweb.org/design^4 https://indieweb.org/display-guidelines^5 https://indieweb.org/make_what_you_need^6 https://indieweb.org/open_source^7 https://indieweb.org/plurality^8 https://spec.indieweb.org/^9 https://indieweb.org/^10 https://indieweb.org/principles
link: https://status.blaise.ca/notice/116007
description: 's status on Friday, 27-Jan-2023 02:22:00 EST
encoded: There are many opposing forces in the #IndieWeb that can seem like catch-22s, yet help clarify priorities, and balance present pragmatism & future optimism. * Indie, yet often on corporate infrastructure * Independent, yet dependent on community * Own your content^1, yet share publicly, perhaps CC0^2 * Control of your design^3, yet lack of control elsewhere^4 * UX freedom & creativity, yet guidance toward common patterns for usability * Decentralized, yet DNS * Make what you need^5, yet open source^6 for others * Plurality^7 of projects, yet conforming to standards^8 * Build it yourself, yet use services, software, & libraries built by others These are a few off the top of my head and implied by the IndieWeb wiki home page^9 and principles^10. Rather than contradictions, these tensions are a source of inquiry, questions, and conversations. Each could be expanded into their own discussion or exploration. Each of them is an axis of sorts, with different “right” answers for different people, depending on what they want, and how much time or other resources they have. Each makes the most sense when explored in the context of a focus on solving real user needs to participate directly on today’s web. Each is also a trap for abstract logic, theoretical purity, or dogmatic absolutism, especially when detached from real world goals, constraints, and efforts. This is day 22 of #100DaysOfIndieWeb #100Days, written after a break. Many double days ahead. ← Day 21: https://tantek.com/2023/022/t2/own-your-notes-domain-migration → 🔮 ^1 https://tantek.com/2023/001/t1/own-your-notes ^2 https://indieweb.org/IndieWeb:Copyrights ^3 https://indieweb.org/design ^4 https://indieweb.org/display-guidelines ^5 https://indieweb.org/make_what_you_need ^6 https://indieweb.org/open_source ^7 https://indieweb.org/plurality ^8 https://spec.indieweb.org/ ^9 https://indieweb.org/ ^10 https://indieweb.org/principles
date: 2023-01-27T02:22:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110130
enclosure: indieweb.org
links to: indieweb.org
enclosure: own-your-notes
links to: own-your-notes
enclosure: make what you need
links to: make what you need
enclosure: spec.indieweb.org
links to: spec.indieweb.org
enclosure: own-your-notes-domain-migration
links to: own-your-notes-domain-migration
enclosure: IndieWeb:Copyrights
links to: IndieWeb:Copyrights
enclosure: design
links to: design
enclosure: display-guidelines
links to: display-guidelines
enclosure: open source
links to: open source
enclosure: plurality
links to: plurality
enclosure: principles
links to: principles
tagged: concept

five-years-websub
date: 2023-01-28T08:19:03-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : Five years ago (Monday the 23rd) the @W3C Social Web Working Group published the WebSub Recommendation^1The test suites https://websub.rocks/ for Publishers, Subscribers, and Hubs are still up & running, as are the vast majority of implementations documented in the implementation report.My site supports the publishing side of WebSub via the Superfeedr Hub^2 and there are many more supporting sites^3.Beyond publishing blog posts and realtime updates in social readers^4, there are additional WebSub use-cases such as real time #IndieWeb search^5 results, like Technorati except opt-in via WebSub subscriptions, and without any polling.Such diverse use-cases are one of the benefits of building-block^6 standards^7 like WebSub.If you create a new WebSub implementation, be sure to test it with the test suite^8 and add your results to the WebSub Implementation Reports repo^9.Got questions about WebSub? Ask in https://chat.indieweb.org/devThis is day 23 of #100DaysOfIndieWeb #100Days← Day 22: https://tantek.com/2023/026/t1/indieweb-priorities-balance→ 🔮^1 https://www.w3.org/TR/2018/REC-websub-20180123/^2 https://pubsubhubbub.superfeedr.com/^3 https://indieweb.org/WebSub#IndieWeb_Examples^4 https://indieweb.org/social_reader^5 https://indieweb.org/IndieWeb_Search^6 https://indieweb.org/building-blocks^7 https://spec.indieweb.org/^8 https://websub.rocks/^9 https://websub.net/implementation-reports
link: https://status.blaise.ca/notice/116008
description: 's status on Friday, 27-Jan-2023 22:51:00 EST
encoded: Five years ago (Monday the 23rd) the @W3C Social Web Working Group published the WebSub Recommendation^1 The test suites https://websub.rocks/ for Publishers, Subscribers, and Hubs are still up & running, as are the vast majority of implementations documented in the implementation report. My site supports the publishing side of WebSub via the Superfeedr Hub^2 and there are many more supporting sites^3. Beyond publishing blog posts and realtime updates in social readers^4, there are additional WebSub use-cases such as real time #IndieWeb search^5 results, like Technorati except opt-in via WebSub subscriptions, and without any polling. Such diverse use-cases are one of the benefits of building-block^6 standards^7 like WebSub. If you create a new WebSub implementation, be sure to test it with the test suite^8 and add your results to the WebSub Implementation Reports repo^9. Got questions about WebSub? Ask in https://chat.indieweb.org/dev This is day 23 of #100DaysOfIndieWeb #100Days ← Day 22: https://tantek.com/2023/026/t1/indieweb-priorities-balance → 🔮 ^1 https://www.w3.org/TR/2018/REC-websub-20180123/ ^2 https://pubsubhubbub.superfeedr.com/ ^3 https://indieweb.org/WebSub#IndieWeb_Examples ^4 https://indieweb.org/social_reader ^5 https://indieweb.org/IndieWeb_Search ^6 https://indieweb.org/building-blocks ^7 https://spec.indieweb.org/ ^8 https://websub.rocks/ ^9 https://websub.net/implementation-reports
date: 2023-01-27T22:51:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110131
enclosure: websub.rocks
links to: websub.rocks
enclosure: IndieWeb Examples
links to: IndieWeb Examples
enclosure: social reader
links to: social reader
enclosure: spec.indieweb.org
links to: spec.indieweb.org
enclosure: devThis
links to: devThis
enclosure: indieweb-priorities-balance
links to: indieweb-priorities-balance
enclosure: REC-websub-20180123
links to: REC-websub-20180123
enclosure: pubsubhubbub.superfeedr.com
links to: pubsubhubbub.superfeedr.com
enclosure: IndieWeb Search
links to: IndieWeb Search
enclosure: building-blocks
links to: building-blocks
enclosure: implementation-reports
links to: implementation-reports
tagged: concept

chat-names
date: 2023-01-28T08:19:04-05:00
type: text/html; charset=UTF-8

discuss
date: 2023-01-28T08:19:05-05:00
type: text/html; charset=UTF-8

IndieAuth
date: 2023-01-28T08:19:06-05:00
type: text/html; charset=UTF-8

Web sign-in
date: 2023-01-28T08:19:07-05:00
type: text/html; charset=UTF-8

admintax
date: 2023-01-28T08:19:08-05:00
type: text/html; charset=UTF-8

Join Discussions
date: 2023-01-28T08:19:09-05:00
type: text/html; charset=UTF-8

icon
date: 2023-01-28T08:19:10-05:00
type: text/html; charset=UTF-8

Nicknames
date: 2023-01-28T08:19:11-05:00
type: text/html; charset=UTF-8

code-of-conduct
date: 2023-01-28T08:19:12-05:00
type: text/html; charset=UTF-8

websub.rocks
date: 2017-06-08T16:07:25-04:00
length: 4151
type: text/html; charset=UTF-8

IndieWeb Examples
date: 2022-02-02T02:23:24-05:00
type: text/html; charset=UTF-8

social reader
date: 2022-02-02T02:23:26-05:00
type: text/html; charset=UTF-8

REC-websub-20180123
date: 2023-01-27T23:34:01-05:00
type: text/html; charset=utf-8

pubsubhubbub.superfeedr.com
date: 2023-01-27T23:34:01-05:00
length: 4
type: text/plain; charset=utf-8

IndieWeb Search
date: 2023-01-27T23:34:01-05:00
type: text/html; charset=UTF-8

building-blocks
date: 2023-01-27T23:34:03-05:00
type: text/html; charset=UTF-8

implementation-reports
date: 2023-01-27T23:34:04-05:00
type: text/html; charset=utf-8

indieweb.org
date: 2018-06-11T17:12:37-04:00
type: text/html; charset=UTF-8

make what you need
date: 2023-01-09T00:56:29-05:00
type: text/html; charset=UTF-8

own-your-notes-domain-migration
date: 2023-01-27T05:09:58-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : 3 weeks since the 1st, since asking you to own your notes^1Still tweeting in Big Chad’s garage or tooting in little Chad’s garage next door?^2 What's the delay?Choosing a domain name?^3Or a service or other path?^4Or #TwitterMigration to #Mastodon?Two #IndieWeb alternatives to owning your notes (https://micro.blog/ or https://fed.brid.gy/, either with your own domain) both support migrating your followers from Mastodon.For example, I migrated my experimental @t@xoxo.zone Mastodon account to my own site^5, @tantek.com, thanks to the migration support in Bridgy Fed.If you’re not sure where you’d like to migrate, you can try https://micro.blog/ for 30 days to see if it works for you.If you’re a #webDev or otherwise like to tinker, it’s well worth the time to setup your own website with an SSG or CMS^6 or your own code, and grow it incrementally as you post and have time to do so.Either way, drop by https://chat.indieweb.org/ and ask any questions you have. There’s a whole community that wants you to succeed, that wants to help you own your notes.This is day 21 of #100DaysOfIndieWeb #100Days, written the night after. ← Day 20: https://tantek.com/2023/022/t1/indieweb-eat-what-you-cook→ 🔮^1 https://tantek.com/2023/001/t1/own-your-notes^2 https://xkcd.com/1150/^3 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb^4 https://tantek.com/2023/003/t1/indieweb-path-chosen-why^5 https://tantek.com/2022/358/t3/^6 https://indieweb.org/CMS
link: https://status.blaise.ca/notice/116006
description: 's status on Monday, 23-Jan-2023 02:49:00 EST
encoded: 3 weeks since the 1st, since asking you to own your notes^1 Still tweeting in Big Chad’s garage or tooting in little Chad’s garage next door?^2 What's the delay? Choosing a domain name?^3 Or a service or other path?^4 Or #TwitterMigration to #Mastodon? Two #IndieWeb alternatives to owning your notes (https://micro.blog/ or https://fed.brid.gy/, either with your own domain) both support migrating your followers from Mastodon. For example, I migrated my experimental @t@xoxo.zone Mastodon account to my own site^5, @tantek.com, thanks to the migration support in Bridgy Fed. If you’re not sure where you’d like to migrate, you can try https://micro.blog/ for 30 days to see if it works for you. If you’re a #webDev or otherwise like to tinker, it’s well worth the time to setup your own website with an SSG or CMS^6 or your own code, and grow it incrementally as you post and have time to do so. Either way, drop by https://chat.indieweb.org/ and ask any questions you have. There’s a whole community that wants you to succeed, that wants to help you own your notes. This is day 21 of #100DaysOfIndieWeb #100Days, written the night after. ← Day 20: https://tantek.com/2023/022/t1/indieweb-eat-what-you-cook → 🔮 ^1 https://tantek.com/2023/001/t1/own-your-notes ^2 https://xkcd.com/1150/ ^3 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb ^4 https://tantek.com/2023/003/t1/indieweb-path-chosen-why ^5 https://tantek.com/2022/358/t3/ ^6 https://indieweb.org/CMS
date: 2023-01-23T02:49:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110129
enclosure: bottom
links to: bottom
enclosure: https://xkcd.com/1150/
links to: https://xkcd.com/1150/
enclosure: micro.blog
links to: micro.blog
enclosure: CMS
links to: CMS
enclosure: own-your-notes
links to: own-your-notes
enclosure: indieweb-path-chosen-why
links to: indieweb-path-chosen-why
enclosure: choosing-domain-name-indieweb
links to: choosing-domain-name-indieweb
enclosure: fed.brid.gy
links to: fed.brid.gy
enclosure: indieweb-eat-what-you-cook
links to: indieweb-eat-what-you-cook
enclosure: t3
links to: t3
tagged: concept

IndieWeb:Copyrights
date: 2023-01-27T05:09:59-05:00
type: text/html; charset=UTF-8

design
date: 2023-01-27T05:10:00-05:00
type: text/html; charset=UTF-8

display-guidelines
date: 2023-01-27T05:10:00-05:00
type: text/html; charset=UTF-8

open source
date: 2023-01-27T05:10:02-05:00
type: text/html; charset=UTF-8

plurality
date: 2023-01-27T05:10:03-05:00
type: text/html; charset=UTF-8

https://xkcd.com/1150/
date: 2023-01-02T02:36:49-05:00
length: 8725
type: text/html; charset=UTF-8

micro.blog
date: 2023-01-02T02:36:49-05:00
length: 7960
type: text/html;charset=utf-8

CMS
date: 2023-01-02T02:36:50-05:00
type: text/html; charset=UTF-8

indieweb-path-chosen-why
date: 2023-01-05T04:06:24-05:00
type: text/html; charset=UTF-8

indieweb-eat-what-you-cook
date: 2023-01-23T05:45:22-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : One of our #IndieWeb principles is Use What You Make^1. We use the metaphor Eat What You Cook^2 to more broadly relate to creators^3 of all kinds, the chefs & cooks of the IndieWeb.Cooks often taste their dishes while cooking, and modify them accordingly. Some even prepare entire dishes or meals to try themselves first, before preparing them for others.On the IndieWeb, some of us do the same by first testing our own code changes in production^4 on our personal sites, before publishing them more widely. Sometimes we let our changes simmer on our own sites for a while, before serving our code for others to consume.I myself have been most recently testing in production my at-mention auto-linking updates^5 on my site for over a week now. They seem to be working well, and I haven’t noticed any errors or regressions, so I’ll likely roll at least some of those changes into the CASSIS GitHub repo soon.While testing in production may be a reasonable & good practice for personal sites, it’s often a bad idea for corporate or critical web sites or services, and there’s no shortage of such examples.I have been wanting to write about our IndieWeb “test in production” practices for a while, and finally created a separate page on the IndieWeb wiki accordingly^4, organizing content from other pages, and adding examples beyond the IndieWeb as well.Do you write code for your website that you test there in production before sharing it more broadly on GitHub etc.? Add yourself to the examples section^6Thanks to Chris Aldrich (https://boffosocko.com/) for the eating what you cook banner image.This is day 20 of #100DaysOfIndieWeb #100Days, written two days after. I have some double days ahead of me.← Day 19: https://tantek.com/2023/020/t2/bridgy-fed-follow-form→ 🔮^1 https://indieweb.org/use_what_you_make^2 https://indieweb.org/eat_what_you_cook, much more palatable than prior "selfdogfood" or "dogfood" metaphors from other open source related communities.^3 https://indieweb.org/creator^…
link: https://status.blaise.ca/notice/116005
description: 's status on Sunday, 22-Jan-2023 19:11:00 EST
encoded: One of our #IndieWeb principles is Use What You Make^1. We use the metaphor Eat What You Cook^2 to more broadly relate to creators^3 of all kinds, the chefs & cooks of the IndieWeb. Cooks often taste their dishes while cooking, and modify them accordingly. Some even prepare entire dishes or meals to try themselves first, before preparing them for others. On the IndieWeb, some of us do the same by first testing our own code changes in production^4 on our personal sites, before publishing them more widely. Sometimes we let our changes simmer on our own sites for a while, before serving our code for others to consume. I myself have been most recently testing in production my at-mention auto-linking updates^5 on my site for over a week now. They seem to be working well, and I haven’t noticed any errors or regressions, so I’ll likely roll at least some of those changes into the CASSIS GitHub repo soon. While testing in production may be a reasonable & good practice for personal sites, it’s often a bad idea for corporate or critical web sites or services, and there’s no shortage of such examples. I have been wanting to write about our IndieWeb “test in production” practices for a while, and finally created a separate page on the IndieWeb wiki accordingly^4, organizing content from other pages, and adding examples beyond the IndieWeb as well. Do you write code for your website that you test there in production before sharing it more broadly on GitHub etc.? Add yourself to the examples section^6 Thanks to Chris Aldrich (https://boffosocko.com/) for the eating what you cook banner image. This is day 20 of #100DaysOfIndieWeb #100Days, written two days after. I have some double days ahead of me. ← Day 19: https://tantek.com/2023/020/t2/bridgy-fed-follow-form → 🔮 ^1 https://indieweb.org/use_what_you_make ^2 https://indieweb.org/eat_what_you_cook, much more palatable than prior "selfdogfood" or "dogfood" metaphors from other open source related communities. ^3 https://indieweb.o…
date: 2023-01-22T19:11:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110128
tagged: concept

t3
date: 2023-01-23T05:45:22-05:00
type: text/html; charset=UTF-8

concept
type: Tag
label: twittermigration

bridgy-fed-follow-form
type: item
type: MicroblogPost
title: : When you setup your site with Bridgy Fed^1, it creates a dashboard with a form for others to follow you site. E.g. mine: https://fed.brid.gy/user/tantek.comCopying that Follow form to your site sets up cross-instance following directly from your #IndieWeb site! Starting with the Follow form markup on the dashboard, copy it and make any necessary changes for its HTML & CSS to fit in with your own, e.g. 🐘 Follow @tantek.com@tantek.com: enter your @-@ fediverse address: Follow After adding the Follow form to my site, I added more instructions and screenshots to the IndieWeb wiki to hopefuly enable more developers to setup Follow buttons:* https://indieweb.org/Bridgy_Fed#How_to_add_a_follow_formSee that section for a sample rendering of the form, and what happens when someone else clicks the Follow button on your site while they’re logged into a Mastodon instance.They get prompted to FOLLOW you, and when they click that button, they get a follow confirmation.A functioning cross-instance “Follow” button is one step closer to a universal cross-site “Follow button”.This is day 19 of #100DaysOfIndieWeb #100Days, written the night after.← Day 18: https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo→ 🔮^1 https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed
link: https://status.blaise.ca/notice/116004
description: 's status on Saturday, 21-Jan-2023 02:54:00 EST
encoded: When you setup your site with Bridgy Fed^1, it creates a dashboard with a form for others to follow you site. E.g. mine: https://fed.brid.gy/user/tantek.com Copying that Follow form to your site sets up cross-instance following directly from your #IndieWeb site! Starting with the Follow form markup on the dashboard, copy it and make any necessary changes for its HTML & CSS to fit in with your own, e.g. 🐘 Follow @tantek.com@tantek.com: enter your @-@ fediverse address: <input id="follow-address" name="address" type="text" required="required" placeholder="@you@instance.social" alt="fediverse address" value="" /> Follow After adding the Follow form to my site, I added more instructions and screenshots to the IndieWeb wiki to hopefuly enable more developers to setup Follow buttons: * https://indieweb.org/Bridgy_Fed#How_to_add_a_follow_form See that section for a sample rendering of the form, and what happens when someone else clicks the Follow button on your site while they’re logged into a Mastodon instance. They get prompted to FOLLOW you, and when they click that button, they get a follow confirmation. A functioning cross-instance “Follow” button is one step closer to a universal cross-site “Follow button”. This is day 19 of #100DaysOfIndieWeb #100Days, written the night after. ← Day 18: https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo → 🔮 ^1 https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed
date: 2023-01-21T02:54:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110127
tagged: concept

reply-domain-above-address-and-silo
type: item
type: MicroblogPost
title: : Instead of posting on a personal #IndieWeb site (& POSSE copies), some post primarily to a #fediverse instance and syndicate to Twitter, or vice-versa. How to reply^1 to such posts, e.g.:Reply to a toot (& POSSE tweet): https://tantek.com/2023/019/t4* @-@ (Twitter @-name)This is a variant of case (2) in https://tantek.com/2023/018/t1/elevate-indieweb-above-silo.We can update the directive and two questions & answers in that prior post accordingly:* Elevate #IndieWeb domains above @-@ addresses, and those above any silo identities1. Do they have an #IndieWeb domain? Then @-domain mention them^2, like you are speaking to them at their domain identity. This will notify them there, or at least reinforce their domain’s importance.2. Was their post only published on a #fediverse instance (and/or silo), or was it POSSEd to a fediverse instance (and/or silo) and do you plan to federate (and/or POSSE) your reply^3?Then use their @-@ address or silo @-name, or @-@ (silo @-name) for both, or (@-@, silo @-name) parenthetically following their @-domain if (1). This will notify them on that instance (or silo), and may help thread your POSSE reply.When posting a reply, you (or your CMS automatically) should explicitly link with u-in-reply-to markup^4 to the post your are replying to, and any of its syndicated copy permalinks on destinations you plan to POSSE your reply (see also multi-reply^5). This is day 18 of #100DaysOfIndieWeb #100Days, written the day after.← Day 17: https://tantek.com/2023/018/t1/elevate-indieweb-above-silo→ 🔮^1 https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post^2 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention^3 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute^4 https://indieweb.org/in-reply-to^5 https://indieweb.org/multiple-reply
link: https://status.blaise.ca/notice/116003
description: 's status on Thursday, 19-Jan-2023 21:05:00 EST
encoded: Instead of posting on a personal #IndieWeb site (& POSSE copies), some post primarily to a #fediverse instance and syndicate to Twitter, or vice-versa. How to reply^1 to such posts, e.g.: Reply to a toot (& POSSE tweet): https://tantek.com/2023/019/t4 * @-@ (Twitter @-name) This is a variant of case (2) in https://tantek.com/2023/018/t1/elevate-indieweb-above-silo. We can update the directive and two questions & answers in that prior post accordingly: * Elevate #IndieWeb domains above @-@ addresses, and those above any silo identities 1. Do they have an #IndieWeb domain? Then @-domain mention them^2, like you are speaking to them at their domain identity. This will notify them there, or at least reinforce their domain’s importance. 2. Was their post only published on a #fediverse instance (and/or silo), or was it POSSEd to a fediverse instance (and/or silo) and do you plan to federate (and/or POSSE) your reply^3? Then use their @-@ address or silo @-name, or @-@ (silo @-name) for both, or (@-@, silo @-name) parenthetically following their @-domain if (1). This will notify them on that instance (or silo), and may help thread your POSSE reply. When posting a reply, you (or your CMS automatically) should explicitly link with u-in-reply-to markup^4 to the post your are replying to, and any of its syndicated copy permalinks on destinations you plan to POSSE your reply (see also multi-reply^5). This is day 18 of #100DaysOfIndieWeb #100Days, written the day after. ← Day 17: https://tantek.com/2023/018/t1/elevate-indieweb-above-silo → 🔮 ^1 https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post ^2 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention ^3 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute ^4 https://indieweb.org/in-reply-to ^5 https://indieweb.org/multiple-reply
date: 2023-01-19T21:05:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110126
enclosure: indieweb-evolving-at-mention
links to: indieweb-evolving-at-mention
enclosure: publish-indieweb-decide-distribute
links to: publish-indieweb-decide-distribute
enclosure: socialweb-blogs-reply-comment-post
links to: socialweb-blogs-reply-comment-post
enclosure: t4*
links to: t4*
enclosure: elevate-indieweb-above-silo
links to: elevate-indieweb-above-silo
enclosure: in-reply-to
links to: in-reply-to
enclosure: multiple-reply
links to: multiple-reply
tagged: concept

indieweb-evolving-at-mention
date: 2023-01-13T06:37:52-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : 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 accordinglySome 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 @jacky.wtf @Martymcgui.re @david.shanske.com @voxpelli.com @adactio.com @marcthiele.com @mxb.dev @ben.thatmustbe.meThese 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.^32. 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://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@mastodo…
link: https://status.blaise.ca/notice/115991
description: 's status on Thursday, 12-Jan-2023 02:59:00 EST
encoded: 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 @jacky.wtf @Martymcgui.re @david.shanske.com @voxpelli.com @adactio.com @marcthiele.com @mxb.dev @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 (yet), e.g.: * 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/ (@dang…
date: 2023-01-12T02:59:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110117
tagged: concept

publish-indieweb-decide-distribute
date: 2023-01-17T19:26:37-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : When you publish on your #IndieWeb site, you can decide afterwards where to distribute your content, and when. Figure out how you want to fit into the network of sites & instances.We call this POSSE — for Publish on your Own Site, then Syndicate Elsewhere.^1By prioritizing your own site, you decide whether (and when) you want to syndicate your posts (or a particular post) to a feed, to a fediverse, to a social media silo or silos, and/or to email like a newsletter.You can make it as simple or as detailed as you want. It’s up to you.Choose deliberately. Change your mind when things change. You can opt out of any destination, either by not opting-in, i.e. explicitly not sending your posts to them, or blocking them if necessary.Here are a few of the destination decisions I’ve made, and reasons why.You can delay sending a post to an RSS or Atom feed, say 10 minutes after the time of publication, to give yourself a chance to edit your post, fix typos or links, before a classic feed reader retrieves and perhaps caches your post.You can further delay sending to known uneditable destinations, like Twitter or email, to give yourself even longer to make further edits, corrections, updates, or improvements based on feedback to your original post.Some destination decisions may depend on the type of post.When you post a reply to someone else’s post, in addition to sending a webmention to that other post, it makes sense to also distribute it to where that other post was originally distributed, or a subset thereof, threading your POSSE reply with their original post POSSE copy.https://indieweb.org/reply#POSSE_a_replyFor example, if you reply to someone’s IndieWeb note, and they’ve POSSEd that note to Twitter, you should POSSE your reply to Twitter as well, threading it with their POSSE copy, if you’re still using Twitter that is. If they did not POSSE their original note to Twitter, there may be reasons to POSSE your reply to Twitter anyway, if your reply makes sense there on it…
link: https://status.blaise.ca/notice/116000
description: 's status on Monday, 16-Jan-2023 02:58:00 EST
encoded: When you publish on your #IndieWeb site, you can decide afterwards where to distribute your content, and when. Figure out how you want to fit into the network of sites & instances. We call this POSSE — for Publish on your Own Site, then Syndicate Elsewhere.^1 By prioritizing your own site, you decide whether (and when) you want to syndicate your posts (or a particular post) to a feed, to a fediverse, to a social media silo or silos, and/or to email like a newsletter. You can make it as simple or as detailed as you want. It’s up to you. Choose deliberately. Change your mind when things change. You can opt out of any destination, either by not opting-in, i.e. explicitly not sending your posts to them, or blocking them if necessary. Here are a few of the destination decisions I’ve made, and reasons why. You can delay sending a post to an RSS or Atom feed, say 10 minutes after the time of publication, to give yourself a chance to edit your post, fix typos or links, before a classic feed reader retrieves and perhaps caches your post. You can further delay sending to known uneditable destinations, like Twitter or email, to give yourself even longer to make further edits, corrections, updates, or improvements based on feedback to your original post. Some destination decisions may depend on the type of post. When you post a reply to someone else’s post, in addition to sending a webmention to that other post, it makes sense to also distribute it to where that other post was originally distributed, or a subset thereof, threading your POSSE reply with their original post POSSE copy. https://indieweb.org/reply#POSSE_a_reply For example, if you reply to someone’s IndieWeb note, and they’ve POSSEd that note to Twitter, you should POSSE your reply to Twitter as well, threading it with their POSSE copy, if you’re still using Twitter that is. If they did not POSSE their original note to Twitter, there may be reasons to POSSE your reply to Twitter anyway, if your reply makes sense th…
date: 2023-01-16T02:58:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110123
tagged: concept

socialweb-blogs-reply-comment-post
date: 2023-01-19T04:34:11-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : Replying to people on the social web used to be “simple” before #socialMedia, when we used blogs. You would either write:1. a short reply — directly on someone’s blog post comment form, OR2. a longer reply — on your own blog, in-reply-to & linking to the other post and send a Pingback, expecting at least the other post’s author to see your reply, or you would also write a short comment in their blog post comment form with a brief summary & link to your longer reply postAside: web forums^1 at the time were proto-silos^2, and replies/threads were generally self-contained therein.Then social media exploded and eventually everybody was replying everywhere all at once.This was so burdensome that some even hired social media managers to perform the labor of how (and if) to reply on each silo, and attempt to keep up with every new silo that popped up.After a few years of this mid-to-late-2000s social web chaos, in the early 2010s many of us went back to option 2. above from the pre-social-media era, and as part of owning our data^3, started posting our replies in general on our own #IndieWeb sites:1. Regardless of brevity or length, we resumed posting peer-to-peer replies on our personal sites (now sent site-to-site with Webmentions^4), watched destinations retrieve & display our comments, and were pleased that our peer-to-peer comments looked like any other comments (except with permalinks back to our originals).2. We also started posting replies to tweets, GitHub issues^5, etc. on our own sites, and automatically POSSE-threading them into their sites of origin.3. When we wrote site-to-site replies where the original post had itself been syndicated to social media^6, we did both 1 & 2. This let readers follow the conversation in either place, providing an #IndieWeb record for if/when the social media thread was taken down, or disappeared along with another silo shutdown^7.Following this 1,2,3 approach helped conceptually simplify replying on the social web, and worked w…
link: https://status.blaise.ca/notice/116001
description: 's status on Tuesday, 17-Jan-2023 12:05:00 EST
encoded: Replying to people on the social web used to be “simple” before #socialMedia, when we used blogs. You would either write: 1. a short reply — directly on someone’s blog post comment form, OR 2. a longer reply — on your own blog, in-reply-to & linking to the other post and send a Pingback, expecting at least the other post’s author to see your reply, or you would also write a short comment in their blog post comment form with a brief summary & link to your longer reply post Aside: web forums^1 at the time were proto-silos^2, and replies/threads were generally self-contained therein. Then social media exploded and eventually everybody was replying everywhere all at once. This was so burdensome that some even hired social media managers to perform the labor of how (and if) to reply on each silo, and attempt to keep up with every new silo that popped up. After a few years of this mid-to-late-2000s social web chaos, in the early 2010s many of us went back to option 2. above from the pre-social-media era, and as part of owning our data^3, started posting our replies in general on our own #IndieWeb sites: 1. Regardless of brevity or length, we resumed posting peer-to-peer replies on our personal sites (now sent site-to-site with Webmentions^4), watched destinations retrieve & display our comments, and were pleased that our peer-to-peer comments looked like any other comments (except with permalinks back to our originals). 2. We also started posting replies to tweets, GitHub issues^5, etc. on our own sites, and automatically POSSE-threading them into their sites of origin. 3. When we wrote site-to-site replies where the original post had itself been syndicated to social media^6, we did both 1 & 2. This let readers follow the conversation in either place, providing an #IndieWeb record for if/when the social media thread was taken down, or disappeared along with another silo shutdown^7. Following this 1,2,3 approach helped conceptually simplify replying on the social web, and …
date: 2023-01-17T12:05:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110124
tagged: concept

t4*
date: 2023-01-19T21:39:51-05:00
type: text/html; charset=UTF-8

elevate-indieweb-above-silo
date: 2023-01-19T21:40:10-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : The answer to “How should you @-mention someone you are replying to?”^1 can depend on many factors or a few. Context matters somewhat, sometimes.We can simplify it to 2 questions, based on 1 directive:* Elevate #IndieWeb domains, above any silo or @-@ identitiesTwo questions and answers: 1. Do they have an #IndieWeb domain? Then @-domain mention them^2, like you are speaking to them at their domain identity. This will notify them there, or at least reinforce their domain’s importance.2. Was their post only published on a silo (or #fediverse instance), or was it POSSEd to a silo (or fediverse instance) and you plan to POSSE (or federate) your reply^3? Then @-mention their silo @-name (or @-@ address), in parentheses if (1). This will notify them on that silo (or instance), and may help thread your POSSE reply.Examples:If the author has their own domain:Reply to an IndieWeb post (& POSSE toot): https://tantek.com/2023/008/t1/* @-domain (@-@)Reply to an IndieWeb post (& POSSE tweet): https://tantek.com/2023/016/t1/* @-domain [that matches their Twitter @-name]Reply to a toot: https://tantek.com/2023/008/t4/* @-domain (@-@)Reply to a tweet: https://tantek.com/2023/002/t2/* @-domain (Twitter @-name)If the author does not have their own domain:Reply to a toot: https://tantek.com/2023/002/t4/* @-@Reply to a tweet: none since this series, though it would be of the form:* Twitter @-nameThis is day 17 of #100DaysOfIndieWeb #100Days, again finished the next day.← Day 16: https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute→ 🔮^1 https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post^2 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention^3 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute
link: https://status.blaise.ca/notice/116002
description: 's status on Thursday, 19-Jan-2023 02:11:00 EST
encoded: The answer to “How should you @-mention someone you are replying to?”^1 can depend on many factors or a few. Context matters somewhat, sometimes. We can simplify it to 2 questions, based on 1 directive: * Elevate #IndieWeb domains, above any silo or @-@ identities Two questions and answers: 1. Do they have an #IndieWeb domain? Then @-domain mention them^2, like you are speaking to them at their domain identity. This will notify them there, or at least reinforce their domain’s importance. 2. Was their post only published on a silo (or #fediverse instance), or was it POSSEd to a silo (or fediverse instance) and you plan to POSSE (or federate) your reply^3? Then @-mention their silo @-name (or @-@ address), in parentheses if (1). This will notify them on that silo (or instance), and may help thread your POSSE reply. Examples: If the author has their own domain: Reply to an IndieWeb post (& POSSE toot): https://tantek.com/2023/008/t1/ * @-domain (@-@) Reply to an IndieWeb post (& POSSE tweet): https://tantek.com/2023/016/t1/ * @-domain [that matches their Twitter @-name] Reply to a toot: https://tantek.com/2023/008/t4/ * @-domain (@-@) Reply to a tweet: https://tantek.com/2023/002/t2/ * @-domain (Twitter @-name) If the author does not have their own domain: Reply to a toot: https://tantek.com/2023/002/t4/ * @-@ Reply to a tweet: none since this series, though it would be of the form: * Twitter @-name This is day 17 of #100DaysOfIndieWeb #100Days, again finished the next day. ← Day 16: https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute → 🔮 ^1 https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post ^2 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention ^3 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute
date: 2023-01-19T02:11:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110125
enclosure: indieweb-evolving-at-mention
links to: indieweb-evolving-at-mention
enclosure: publish-indieweb-decide-distribute
links to: publish-indieweb-decide-distribute
enclosure: t1
links to: t1
enclosure: t4
links to: t4
enclosure: t2
links to: t2
enclosure: socialweb-blogs-reply-comment-post
links to: socialweb-blogs-reply-comment-post
tagged: concept

in-reply-to
date: 2023-01-19T21:40:12-05:00
type: text/html; charset=UTF-8

multiple-reply
date: 2023-01-19T21:40:13-05:00
type: text/html; charset=UTF-8

t1
date: 2023-01-19T04:34:06-05:00
type: text/html; charset=UTF-8

t1
date: 2023-01-19T04:34:07-05:00
type: text/html; charset=UTF-8

t4
date: 2023-01-19T04:34:08-05:00
type: text/html; charset=UTF-8

t2
date: 2023-01-19T04:34:09-05:00
type: text/html; charset=UTF-8

t4
date: 2023-01-19T04:34:10-05:00
type: text/html; charset=UTF-8

concept
type: Tag
label: atmention

concept
type: Tag
label: sitetosite

concept
type: Tag
label: testinginproduction

concept
type: Tag
label: testinproduction

indieweb-home-internet
type: item
type: MicroblogPost
title: : Your #IndieWeb site can be the home you’ve always wanted on the internet.While posting on a personal site has many^1 advantages^2 over only posting to #socialMedia, maybe you already quit social media silos^3.There are lots of reasons to get a domain name^4 and setup your own homepage on the web.If you’re a web professional, a personal site with your name on it (perhaps also in its domain) can make it easier for potential employers to find you and read your description in your own words.If you’re a web developer, a personal home page is also an opportunity to demonstrate your craft.^5If you’re a writer, you can organize your words, essays, and longer form articles in a form that’s easier for readers to browse, and style them to both be easier to read, and express your style better than any silo.Similarly if you’re an artist, photographer, or any other kind of content creator.See https://indieweb.org/homepage for more reasons why, and what other kinds of things you can put on your home page.Thanks to Chris Aldrich (https://boffosocko.com/) for the header image.This is day 13 of #100DaysOfIndieWeb #100Days.← Day 12: https://tantek.com/2023/012/t1/six-years-webmention-w3c→ 🔮^1 https://tantek.com/2023/001/t1/own-your-notes^2 https://tantek.com/2023/005/t3/indieweb-simpler-approach^3 https://indieweb.org/silo-quits^4 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb^5 https://indieweb.org/creator
link: https://status.blaise.ca/notice/115993
description: 's status on Saturday, 14-Jan-2023 02:39:00 EST
encoded: Your #IndieWeb site can be the home you’ve always wanted on the internet. While posting on a personal site has many^1 advantages^2 over only posting to #socialMedia, maybe you already quit social media silos^3. There are lots of reasons to get a domain name^4 and setup your own homepage on the web. If you’re a web professional, a personal site with your name on it (perhaps also in its domain) can make it easier for potential employers to find you and read your description in your own words. If you’re a web developer, a personal home page is also an opportunity to demonstrate your craft.^5 If you’re a writer, you can organize your words, essays, and longer form articles in a form that’s easier for readers to browse, and style them to both be easier to read, and express your style better than any silo. Similarly if you’re an artist, photographer, or any other kind of content creator. See https://indieweb.org/homepage for more reasons why, and what other kinds of things you can put on your home page. Thanks to Chris Aldrich (https://boffosocko.com/) for the header image. This is day 13 of #100DaysOfIndieWeb #100Days. ← Day 12: https://tantek.com/2023/012/t1/six-years-webmention-w3c → 🔮 ^1 https://tantek.com/2023/001/t1/own-your-notes ^2 https://tantek.com/2023/005/t3/indieweb-simpler-approach ^3 https://indieweb.org/silo-quits ^4 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb ^5 https://indieweb.org/creator
date: 2023-01-14T02:39:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110119
enclosure: own-your-notes
links to: own-your-notes
enclosure: choosing-domain-name-indieweb
links to: choosing-domain-name-indieweb
enclosure: indieweb-simpler-approach
links to: indieweb-simpler-approach
enclosure: homepage
links to: homepage
enclosure: boffosocko.com
links to: boffosocko.com
enclosure: six-years-webmention-w3c
links to: six-years-webmention-w3c
enclosure: silo-quits
links to: silo-quits
enclosure: creator
links to: creator
tagged: concept

indieweb-simpler-approach
date: 2023-01-07T08:30:40-05:00
type: text/html; charset=UTF-8

boffosocko.com
date: 2023-01-14T04:42:24-05:00
type: text/html; charset=UTF-8

six-years-webmention-w3c
date: 2023-01-14T04:42:26-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : 🎉 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/WebmentionIf 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/devPreviously, 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-barThis is day 12 of #100DaysOfIndieWeb #100Days.← Day 11: https://tantek.com/2023/011/t1/indieweb-evolving-at-mention→ 🔮
link: https://status.blaise.ca/notice/115992
description: 's status on Friday, 13-Jan-2023 02:45:00 EST
encoded: 🎉 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 → 🔮
date: 2023-01-13T02:45:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110118
enclosure: summary
links to: summary
enclosure: https://www.w3.org/TR/webmention/A
links to: https://www.w3.org/TR/webmention/A
enclosure: webmention.rocks
links to: webmention.rocks
enclosure: It
links to: It
enclosure: WebmentionIf
links to: WebmentionIf
enclosure: Webmention-developer
links to: Webmention-developer
enclosure: devPreviously
links to: devPreviously
enclosure: happy-birthday-webmention
links to: happy-birthday-webmention
enclosure: anniversary-million-webmentions
links to: anniversary-million-webmentions
enclosure: webmntion-first-w3c-recommendation-high-bar
links to: webmntion-first-w3c-recommendation-high-bar
enclosure: indieweb-evolving-at-mention
links to: indieweb-evolving-at-mention
tagged: concept

silo-quits
date: 2023-01-14T04:42:27-05:00
type: text/html; charset=UTF-8

summary
date: 2017-01-12T13:47:20-05:00
length: 74273
type: text/html

https://www.w3.org/TR/webmention/A
date: 2023-01-13T06:37:44-05:00
length: 6831
type: text/html;charset=utf-8

webmention.rocks
date: 2023-01-13T06:37:44-05:00
type: text/html; charset=UTF-8

It
date: 2023-01-13T06:37:44-05:00
length: 6831
type: text/html;charset=utf-8

WebmentionIf
date: 2023-01-13T06:37:45-05:00
type: text/html; charset=UTF-8

Webmention-developer
date: 2023-01-13T06:37:46-05:00
type: text/html; charset=UTF-8

devPreviously
date: 2023-01-13T06:37:47-05:00
length: 169
type: text/html

happy-birthday-webmention
date: 2023-01-13T06:37:48-05:00
type: text/html; charset=UTF-8

anniversary-million-webmentions
date: 2023-01-13T06:37:50-05:00
type: text/html; charset=UTF-8

webmntion-first-w3c-recommendation-high-bar
date: 2023-01-13T06:37:52-05:00
type: text/html; charset=UTF-8

indieweb-domain-at-mention
type: item
type: MicroblogPost
title: : 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 siteSome 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.meThese 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.^32. 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.c…
link: https://status.blaise.ca/notice/115990
description: 's status on Thursday, 12-Jan-2023 02:59:00 EST
encoded: 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), http…
date: 2023-01-12T02:59:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110116
enclosure: choosing-domain-name-indieweb
links to: choosing-domain-name-indieweb
links to: kevinmarks.com
enclosure: voxpelli.com
links to: voxpelli.com
enclosure: canoe)*
links to: canoe)*
enclosure: adactio.com
links to: adactio.com
enclosure: marcthiele.com
links to: marcthiele.com
enclosure: https://mxb.dev/3
links to: https://mxb.dev/3
enclosure: tmichellemoore.com
links to: tmichellemoore.com
enclosure: simonwillison.net
links to: simonwillison.net
enclosure: @userwith
links to: @userwith
enclosure: http://tantek.com/I
links to: http://tantek.com/I
enclosure: build-use-services
links to: build-use-services
enclosure: AT-AT
links to: AT-AT
enclosure: cassis.js
links to: cassis.js
tagged: concept

voxpelli.com
date: 2023-01-11T09:44:08-05:00
length: 7876
type: text/html; charset=UTF-8

canoe)*
date: 2023-01-12T05:30:38-05:00
type: text/html; charset=UTF-8

adactio.com
date: 2023-01-12T05:30:39-05:00
type: text/html; charset=utf-8

marcthiele.com
date: 2023-01-12T05:30:40-05:00
type: text/html; charset=UTF-8

https://mxb.dev/3
date: 2023-01-12T05:30:41-05:00
length: 19233
type: text/html; charset=UTF-8

tmichellemoore.com
date: 2023-01-12T05:30:41-05:00
type: text/html; charset=UTF-8

simonwillison.net
date: 2023-01-12T05:30:43-05:00
type: text/html; charset=utf-8

@userwith
date: 2023-01-12T05:30:43-05:00
length: 1256
type: text/html; charset=UTF-8

http://tantek.com/I
date: 2023-01-12T05:30:44-05:00
type: text/html; charset=iso-8859-1

build-use-services
date: 2023-01-12T05:30:44-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : 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_ServicesAnother 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#LibrariesIf 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…
link: https://status.blaise.ca/notice/115989
description: 's status on Wednesday, 11-Jan-2023 02:59:00 EST
encoded: 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 …
date: 2023-01-11T02:59:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110115
tagged: concept

AT-AT
date: 2023-01-12T05:30:45-05:00
type: text/html; charset=UTF-8

cassis.js
date: 2023-01-12T05:30:46-05:00
type: text/html; charset=utf-8

concept
type: Tag
label: webdevelopment

edit-reply-comment-update
type: item
type: MicroblogPost
title: : Sometimes it’s the little things, like editing a post. Edit a reply, see a comment update on another post.From day 5 (https://tantek.com/2023/005/t3/indieweb-simpler-approach)* Can I edit my post after publishing?Whether a tweet or Instagram photo, the answer is no.^1Blogs and websites have had editing capabilities since the start.However, no site is an island, it's a *web* site. Interlinked.We expect edits on one site to show up when embedded or syndicated on other sites.#Webmention provides the ability for cross-site comments, and unlike the "one-off" prior protocols of Trackbacks & Pingbacks^2, when you update a cross-site comment, by resending a Webmention, the other post updates its copy of your reply: https://www.w3.org/TR/webmention/#sending-webmentions-for-updated-postsIf you delete a reply, by resending a Webmention, the other post can delete its copy (or mark it as deleted) https://www.w3.org/TR/webmention/#sending-webmentions-for-deleted-postsSimilarly, the #ActivityPub protocol specifies update & delete capabilities, as implemented by #Mastodon and others.#BridgyFed (https://fed.brid.gy) bridges (as the name says) these two protocols, which enables the following interactions.#IndieWeb post -(Webmention)-> BridgyFed -(ActivtyPub)-> Mastodon displays postand then this:IndieWeb updated post -(Webmention)-> BridgyFed -(ActivtyPub)-> Mastodon displays updated postThis works for replies to toots as well:IndieWeb reply to toot -(Webmention)-> BridgyFed -(ActivtyPub)-> toot displays replyand subsequently:IndieWeb updated reply -(Webmention)-> BridgyFed -(ActivtyPub)-> toot updates display of replyThanks to these update protocols in Webmention & ActivityPub, and BridgyFed connecting them, after adding “forward-in-time” links (https://tantek.com/2023/006/t1/forward-in-time-links) I was able to resend webmentions for my previous #100DaysOfIndieWeb posts, and have those forward links show up wherever my posts were already displayed on Mastodon.Posts interlinked wi…
link: https://status.blaise.ca/notice/115988
description: 's status on Tuesday, 10-Jan-2023 01:44:00 EST
encoded: Sometimes it’s the little things, like editing a post. Edit a reply, see a comment update on another post. From day 5 (https://tantek.com/2023/005/t3/indieweb-simpler-approach) * Can I edit my post after publishing? Whether a tweet or Instagram photo, the answer is no.^1 Blogs and websites have had editing capabilities since the start. However, no site is an island, it's a *web* site. Interlinked. We expect edits on one site to show up when embedded or syndicated on other sites. #Webmention provides the ability for cross-site comments, and unlike the "one-off" prior protocols of Trackbacks & Pingbacks^2, when you update a cross-site comment, by resending a Webmention, the other post updates its copy of your reply: https://www.w3.org/TR/webmention/#sending-webmentions-for-updated-posts If you delete a reply, by resending a Webmention, the other post can delete its copy (or mark it as deleted) https://www.w3.org/TR/webmention/#sending-webmentions-for-deleted-posts Similarly, the #ActivityPub protocol specifies update & delete capabilities, as implemented by #Mastodon and others. #BridgyFed (https://fed.brid.gy) bridges (as the name says) these two protocols, which enables the following interactions. #IndieWeb post -(Webmention)-> BridgyFed -(ActivtyPub)-> Mastodon displays post and then this: IndieWeb updated post -(Webmention)-> BridgyFed -(ActivtyPub)-> Mastodon displays updated post This works for replies to toots as well: IndieWeb reply to toot -(Webmention)-> BridgyFed -(ActivtyPub)-> toot displays reply and subsequently: IndieWeb updated reply -(Webmention)-> BridgyFed -(ActivtyPub)-> toot updates display of reply Thanks to these update protocols in Webmention & ActivityPub, and BridgyFed connecting them, after adding “forward-in-time” links (https://tantek.com/2023/006/t1/forward-in-time-links) I was able to resend webmentions for my previous #100DaysOfIndieWeb posts, and have those forward links show up wherever my posts were already displayed on Mastodon. Pos…
date: 2023-01-10T01:44:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110114
tagged: concept

POSSE
date: 2020-01-02T00:13:24-05:00
type: text/html; charset=UTF-8

brid.gy
date: 2022-01-06T03:52:41-05:00
type: text/html; charset=utf-8

snarfed.org
date: 2023-01-09T00:56:26-05:00
length: 98039
type: text/html; charset=UTF-8

backfeed
date: 2023-01-09T00:56:27-05:00
type: text/html; charset=UTF-8

tantek.comBridgy
date: 2023-01-09T00:56:28-05:00
length: 2193
type: text/html; charset=utf-8

Bridgy
date: 2023-01-09T00:56:30-05:00
type: text/html; charset=UTF-8

Bridgy Fed*
date: 2023-01-09T00:56:31-05:00
type: text/html; charset=UTF-8

2012-01-08 bridgy launchedIt
date: 2023-01-09T00:56:32-05:00
type: text/html; charset=UTF-8

more-100daysofindieweb-projects
date: 2023-01-09T00:56:34-05:00
type: text/html; charset=UTF-8
type: item
type: MicroblogPost
title: : There are more 2023 #100DaysOfIndieWeb projects, you should check them out:* https://tmichellemoore.com/blog/tag/100daysofindieweb/ (@tmichellemoore@mastodon.social)* https://crowdersoup.com/tags/100days (@CrowderSoup@hachyderm.io)Got one? Reply and I'll add it.You can (re)start a #100Days project any day. While continuity is nice, you can take breaks. As https://kevinmarks.com/ (@kevinmarks) said in #IndieWeb chat:* https://indieweb.org/life_happens and should take priority over artificial deadlines.It all started back in 2017 when https://aaronparecki.com/ did the first #100DaysOfIndieWeb project:* https://aaronparecki.com/tag/100daysofindieweb* @100daysindiewebWant to start one of your own? See past & present IndieWeb related 100 days projects for ideas & inspiration:* https://indieweb.org/100_daysThis is day 7 of #100DaysOfIndieWeb.← Day 6: https://tantek.com/2023/006/t1/forward-in-time-links→ 🔮
link: https://status.blaise.ca/notice/115986
description: 's status on Sunday, 08-Jan-2023 02:59:00 EST
encoded: There are more 2023 #100DaysOfIndieWeb projects, you should check them out: * https://tmichellemoore.com/blog/tag/100daysofindieweb/ (@tmichellemoore@mastodon.social) * https://crowdersoup.com/tags/100days (@CrowderSoup@hachyderm.io) Got one? Reply and I'll add it. You can (re)start a #100Days project any day. While continuity is nice, you can take breaks. As https://kevinmarks.com/ (@kevinmarks) said in #IndieWeb chat: * https://indieweb.org/life_happens and should take priority over artificial deadlines. It all started back in 2017 when https://aaronparecki.com/ did the first #100DaysOfIndieWeb project: * https://aaronparecki.com/tag/100daysofindieweb * @100daysindieweb Want to start one of your own? See past & present IndieWeb related 100 days projects for ideas & inspiration: * https://indieweb.org/100_days This is day 7 of #100DaysOfIndieWeb. ← Day 6: https://tantek.com/2023/006/t1/forward-in-time-links → 🔮
date: 2023-01-08T02:59:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110112
enclosure: 100daysofindieweb
links to: 100daysofindieweb
enclosure: 100days
links to: 100days
links to: kevinmarks.com
enclosure: life happens
links to: life happens
enclosure: aaronparecki.com
links to: aaronparecki.com
enclosure: 100daysofindieweb*
links to: 100daysofindieweb*
enclosure: 100 daysThis
links to: 100 daysThis
enclosure: forward-in-time-links
links to: forward-in-time-links
tagged: concept

100daysofindieweb
date: 2023-01-08T05:16:50-05:00
type: text/html; charset=UTF-8

100days
date: 2023-01-08T05:16:51-05:00
length: 7239
type: text/html; charset=utf-8

life happens
date: 2023-01-08T05:17:02-05:00
type: text/html; charset=UTF-8

aaronparecki.com
date: 2023-01-08T05:17:03-05:00
type: text/html; charset=UTF-8

100daysofindieweb*
date: 2023-01-08T05:17:04-05:00
type: text/html; charset=UTF-8

100 daysThis
date: 2023-01-08T05:17:05-05:00
type: text/html; charset=UTF-8

key-owning-notes-domain-name
type: item
type: MicroblogPost
title: : The key to owning your notes is posting them with permalinks using a domain name you control. That’s it. https://indieweb.org/permalinkThere are many providers, like https://micro.blog/, that happily enable using your own domain name for everything you post.This gives you the ability to change your provider, while preserving your post permalinks. From the web’s perspective, your posts work just as they did before.You are in control.This is day 2 of #100DaysOfIndieWeb #100Days #IndieWeb. Day 1: https://tantek.com/2023/001/t1/own-your-notes
link: https://status.blaise.ca/notice/115971
description: 's status on Tuesday, 03-Jan-2023 02:59:00 EST
encoded: The key to owning your notes is posting them with permalinks using a domain name you control. That’s it. https://indieweb.org/permalink There are many providers, like https://micro.blog/, that happily enable using your own domain name for everything you post. This gives you the ability to change your provider, while preserving your post permalinks. From the web’s perspective, your posts work just as they did before. You are in control. This is day 2 of #100DaysOfIndieWeb #100Days #IndieWeb. Day 1: https://tantek.com/2023/001/t1/own-your-notes
date: 2023-01-03T02:59:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110102
enclosure: micro.blog
links to: micro.blog
enclosure: permalinkThere
links to: permalinkThere
enclosure: own-your-notes
links to: own-your-notes
tagged: concept

permalinkThere
date: 2023-01-03T03:32:19-05:00
type: text/html; charset=UTF-8

concept
type: Tag
label: indiewebmaybe

hello
type: item
type: MicroblogPost
title: : Hello 2018.This changing of the year feels very different than last. Yesterday (+today) felt more like just another day to make the most of. Regardless I am doing an #IndieWeb #100Days of Positive Posts again, but refocusing on doing:#100PDTP 100 Days Positive Doing then Posting.As an optimist I believe every day we have opportunities to choose to make things better (or not), even if in seemingly small ways, every day.The 2018 plan for #100DoPP:* Every day: *do* something positive in-person (not just online). E.g. * Something for the first time * Or the first time this year * Or build on something * Or complete something* Post about it on your own site, - or make a note of it and post it later.* *Before* posting anything negative or critical that same dayFrom my experience last year, there were several times when for one reason or another I went days without posting, then had to "catch up". Instead of catch-up, I’m making the posting part strictly secondary, and ok even if published days after the action.I expect to spend more time offline and perhaps even offgrid this year. I’ll be taking paper notes which I can then post about later.Last year’s #100DoPP: http://tantek.com/2017/020/t3/indieweb-100days-positive-posts-100dopp
link: https://status.blaise.ca/notice/106240
description: 's status on Wednesday, 03-Jan-2018 02:42:00 EST
encoded: Hello 2018. This changing of the year feels very different than last. Yesterday (+today) felt more like just another day to make the most of. Regardless I am doing an #IndieWeb #100Days of Positive Posts again, but refocusing on doing: #100PDTP 100 Days Positive Doing then Posting. As an optimist I believe every day we have opportunities to choose to make things better (or not), even if in seemingly small ways, every day. The 2018 plan for #100DoPP: * Every day: *do* something positive in-person (not just online). E.g. * Something for the first time * Or the first time this year * Or build on something * Or complete something * Post about it on your own site, - or make a note of it and post it later. * *Before* posting anything negative or critical that same day From my experience last year, there were several times when for one reason or another I went days without posting, then had to "catch up". Instead of catch-up, I’m making the posting part strictly secondary, and ok even if published days after the action. I expect to spend more time offline and perhaps even offgrid this year. I’ll be taking paper notes which I can then post about later. Last year’s #100DoPP: http://tantek.com/2017/020/t3/indieweb-100days-positive-posts-100dopp
date: 2018-01-03T02:42:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/102415
tagged: concept

concept
type: Tag
label: 100dopp

Tantek
type: Agent
holds account: acct