: 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 successfully filled out the whole month since the 2018 IndieWeb Challenge⁴, and only the second time ever in the seven years of the IndieWeb Challenge-turned-Gift-Calendar.By going through the various gifts (more than 2 per day on average!), there are many interesting numbers and patterns we could surface. That deserves its own post however, as does a summary of the 48 posts⁵ of my 2023 100 Days of IndieWeb attempt, so I’ll end this post here.Happy New Year to all, with an especially well deserved congratulations to the IndieWeb community and everyone who contributed to the 2023 Gift Calendar. Well done! Let’s see what else we can create & share on our personal sites in 2024 and continue setting a higher bar for the independent web by showing instead of telling. #ShowDontTellThis is post 1 of #100PostsOfIndieWeb. #100Posts← ✨→ 🔮Post glossary:API https://indieweb.org/APIPOSSE https://indieweb.org/POSSEsilo https://indieweb.org/silo¹ https://tantek.com/2023/001/t1/own-your-notes² https://indieweb.org/algorithmic_feed³ https://indieweb.org/2023-12-indieweb-gift-calendar⁴ https://indieweb.org/2018-12-indieweb-challenge⁵ https://tantek.com/2023/365/t2/no-large-language-model-llm-used
's status on Monday, 01-Jan-2024 22:30:00 EST
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 successfully filled out the whole month since the 2018 IndieWeb Challenge⁴, and only the second time ever in the seven years of the IndieWeb Challenge-turned-Gift-Calendar. By going through the various gifts (more than 2 per day on average!), there are many interesting numbers and patterns we could surface. That deserves its own post however, as does a summary of the 48 posts⁵ of my 2023 100 Days of IndieWeb attempt, so I’ll end this post here. Happy New Year to all, with an especially well deserved congratulations to the IndieWeb community and everyone who contributed to the 2023 Gift Calendar. Well done! Let’s see what else we can create & share on our personal sites in 2024 and continue setting a higher bar for the independent web by showing instead of telling. #ShowDontTell This is post 1 of #100PostsOfIndieWeb. #100Posts ← ✨ → 🔮 Post glossary: API https://indieweb.org/API POSSE https://indieweb.org/POSSE silo https://indieweb.org/silo ¹ https://tantek.com/2023/001/t1/own-your-notes ² https://indieweb.org/algorithmic_feed ³ https://indieweb.org/2023-12-indieweb-gift-calendar ⁴ https://indieweb.org/2018-12-indieweb-challenge ⁵ https://tantek.com/2023/365/t2/no-large-language-model-llm-used
: 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/xfn/11#metXFN https://gmpg.org/xfn/
's status on Sunday, 31-Dec-2023 17:56:00 EST
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 http://gmpg.org/xfn/11#met XFN https://gmpg.org/xfn/
: 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/2023/277/b1/thoughtful-reading-writing-web)Post glossary:algorithmic feed https://indieweb.org/algorithmic_feedarticle https://indieweb.org/articlenote https://indieweb.org/notepost https://indieweb.org/postsense-making https://en.wikipedia.org/wiki/Sensemaking_(information_science)social media https://indieweb.org/social_media
's status on Sunday, 31-Dec-2023 17:04:00 EST
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://tantek.com/2023/277/b1/thoughtful-reading-writing-web) Post glossary: algorithmic feed https://indieweb.org/algorithmic_feed article https://indieweb.org/article note https://indieweb.org/note post https://indieweb.org/post sense-making https://en.wikipedia.org/wiki/Sensemaking_(information_science) social media https://indieweb.org/social_media
: 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 replies as well.David also noted several challenges and good questions about POSSE. Some of these have answers & established practices, others are areas of exploration. E.g. "The first is the social side of social media: what do you do with all the likes, replies, comments, and everything else that comes with your posts?" The short answer is #backfeed: https://indieweb.org/backfeedBackfeed is a concept I first wrote about as “reverse syndication”². As you syndicate your posts out to #socialMedia silos, you reverse syndicate any responses there back to your original post. Your site can do this with a service like #Bridgy, which uses the #Webmention standard to forward such silo responses back to your site, and #BridgyFed which does same for responses from Mastodon to your #federated posts.David asked many other questions, which are deserving of their own posts to help answer, so I’ll leave you with just one more: "The most immediate question, though, is simply how to build a POSSE system that works."The short answer is: just start³.Even if you have to do it manually (until it hurts), even if you have to edit your posts on a static GitHub site (behind your domain name of course), and then copy & paste to your silo(s) of choice, just start.By practicing POSSE, even manually, you will learn what aspects of POSSE & backfeed matter the most to you, what aspects actually involve reaching & responding to friends and others you care about. By doing so you will naturally focus on setting up & making what you need, and you too can join the future of web publishing, today.Questions? Join us in the chat: https://chat.indieweb.org/ (also on Discord, IRC, and Slack⁴)This is day 46 of #100DaysOfIndieWeb. #100Days← Day 45: https://tantek.com/2023/289/t1/bridgyfed-webmention-like-fediverse→ 🔮Post glossary:backfeed / reverse syndication https://indieweb.org/backfeedBridgy https://brid.gy/make what you need https://indieweb.org/make_what_you_needmanual (until it hurts) https://indieweb.org/manual_until_it_hurtsoriginal post link https://indieweb.org/original_post_linkown your data https://indieweb.org/own_your_dataown your replies https://indieweb.org/own_your_repliespermalink https://indieweb.org/permalinkpermashortlink https://indieweb.org/permashortlinkPOSSE https://indieweb.org/POSSEsilo https://indieweb.org/silosocial media https://indieweb.org/social_mediastatic site https://indieweb.org/static_sitestart https://indieweb.org/startWebmention https://indieweb.org/Webmention¹ https://tantek.com/2023/253/t2/² https://tantek.com/2010/034/t2/diso-2-personal-domains-shortener-hatom-push-relmeauth³ https://tantek.com/2023/001/t1/own-your-notes⁴ https://indieweb.org/discuss
's status on Monday, 23-Oct-2023 20:30:00 EDT
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 your replies as well. David also noted several challenges and good questions about POSSE. Some of these have answers & established practices, others are areas of exploration. E.g. "The first is the social side of social media: what do you do with all the likes, replies, comments, and everything else that comes with your posts?" The short answer is #backfeed: https://indieweb.org/backfeed Backfeed is a concept I first wrote about as “reverse syndication”². As you syndicate your posts out to #socialMedia silos, you reverse syndicate any responses there back to your original post. Your site can do this with a service like #Bridgy, which uses the #Webmention standard to forward such silo responses back to your site, and #BridgyFed which does same for responses from Mastodon to your #federated posts. David asked many other questions, which are deserving of their own posts to help answer, so I’ll leave you with just one more: "The most immediate question, though, is simply how to build a POSSE system that works." The short answer is: just start³. Even if you have to do it manually (until it hurts), even if you have to edit your posts on a static GitHub site (behind your domain name of course), and then copy & paste to your silo(s) of choice, just start. By practicing POSSE, even manually, you will learn what aspects of POSSE & backfeed matter the most to you, what aspects actually involve reaching & responding to friends and others you care about. By doing so you will naturally focus on setting up & making what you need, and you too can join the future of web publishing, today. Questions? Join us in the chat: https://chat.indieweb.org/ (also on Discord, IRC, and Slack⁴) This is day 46 of #100DaysOfIndieWeb. #100Days ← Day 45: https://tantek.com/2023/289/t1/bridgyfed-webmention-like-fediverse → 🔮 Post glossary: backfeed / reverse syndication https://indieweb.org/backfeed Bridgy https://brid.gy/ make what you need https://indieweb.org/make_what_you_need manual (until it hurts) https://indieweb.org/manual_until_it_hurts original post link https://indieweb.org/original_post_link own your data https://indieweb.org/own_your_data own your replies https://indieweb.org/own_your_replies permalink https://indieweb.org/permalink permashortlink https://indieweb.org/permashortlink POSSE https://indieweb.org/POSSE silo https://indieweb.org/silo social media https://indieweb.org/social_media static site https://indieweb.org/static_site start https://indieweb.org/start Webmention https://indieweb.org/Webmention ¹ https://tantek.com/2023/253/t2/ ² https://tantek.com/2010/034/t2/diso-2-personal-domains-shortener-hatom-push-relmeauth ³ https://tantek.com/2023/001/t1/own-your-notes ⁴ https://indieweb.org/discuss
: 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
's status on Monday, 16-Oct-2023 21:16:00 EDT
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
: 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² https://www.threads.net/@timothyjchambers/post/CupCvChAxI8³ https://www.threads.net/@0xjessel/post/Cvu7-A4viZu⁴ https://spec.indieweb.org/
's status on Tuesday, 22-Aug-2023 15:43:00 EDT
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/post/Cvu2eXurRbB ² https://www.threads.net/@timothyjchambers/post/CupCvChAxI8 ³ https://www.threads.net/@0xjessel/post/Cvu7-A4viZu ⁴ https://spec.indieweb.org/
: 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/wikipedia-supports-indieweb-rel-me⁴ https://tantek.com/2012/173/t1/posse-core-indieweb-approach⁵ https://tantek.com/2023/001/t1/own-your-notes⁶ https://indieweb.org/site-deaths⁷ https://ourincrediblejourney.tumblr.com/
's status on Tuesday, 20-Jun-2023 19:52:00 EDT
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://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me ⁴ https://tantek.com/2012/173/t1/posse-core-indieweb-approach ⁵ https://tantek.com/2023/001/t1/own-your-notes ⁶ https://indieweb.org/site-deaths ⁷ https://ourincrediblejourney.tumblr.com/
: 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
's status on Friday, 09-Jun-2023 22:14:00 EDT
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: 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
: 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
's status on Friday, 19-May-2023 16:19:00 EDT
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
: 🌱 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-friendly way.* hours open (perhaps kitchen hours if different)* location (address that links to a map UI or map embed w/o cookies/tracking)* nearest bus/tram/rail stop* payment restrictions (e.g. if only cash, or only credit) or options if you prefer* contact info (including a note about catering if that’s an option)* links to social media profiles* links to restaurant review sites/aggregator pages (e.g. venue permalink on Google Maps, TripAdvisor, Foursquare, Swarm, HappyCow)* menu with item name, description, price, optional-thumbnail, and dietary/allergy notationsNo you really don’t need the full mess of made-up things at schema-org.The community at OpenStreetMap has done A LOT (most? nearly all?) of the work figuring out the ways to express the above types of information, e.g.:https://wiki.openstreetmap.org/wiki/Key:opening_hoursYet has anyone actually seen a simple semantic HTML page that publishes this kind of information? I’ve web searched many search terms and phrases and found nothing good. Stylistically dated templates for sale. Examples with numerous unnecessary scripts (no your typical user does not care about your clever animated 3D-carousel of pretty photos, certainly not waiting for a megabyte of framework scripts for it). Something built on Bootstrap, unnecessary for today’s mobile-friendly HTML+CSS.I did find one (ONE) blog post from 2007 (those were the days) for semantic markup for a restaurant menu: https://jonchristopher.us/blog/a-semantic-breakdown-of-restaurant-menus/ Unless I find an existing solution soon, I’m going to create something from scratch with h-card (since a restaurant is an organization / venue) and add semantic HTML & class names for various fields, re-using from OpenStreetMap Keys whenever possible.That leaves the URL design, where to publish my restaurant pages on my own site, and rather than rethink it, I will likely go with what I decided in my Whistle short URL design¹ many years ago, which is /v/ at the top level of my site, followed by a slug of my short name for the venue. This way I can play with static HTML pages there, with a shared style sheet in that same directory, without impacting anything else on my site.I have some other thoughts around iconography for various diet preferences / allergen warnings for menu items that I’ve tried (or considered), though perhaps I’ll leave those for another post. Or maybe I’ll braindump them now, however incomplete, to see if they resonate or anyone has better suggestions (restaurants and menus really have no standard for these)🌱 vegan & gluten-free🌱🌾 vegan + gluten🌱🥜 vegan + nuts🌱🍫 vegan + chocolate🌱🍯 vegetarian (has honey)🌱🧈 vegetarian (has butter)🌱🥛 vegetarian (has milk, cream, or yogurt)🌱🧀 vegetarian (has cheese)🌱🥚 vegetarian (has egg)with combinations as necessary. For example, a breakfast sandwich at Devil’s Teeth Bakery²:* Regular Breakfast Sandwich (no bacon!) $10.00 🌱🌾🧈🧀🥚Or a chocolate croissant at Arsicault³:* Chocolate Croissant $5.75 🌱🌾🧈🍫Non-vegetarian items would omit the plant 🌱 icon/emoji, but could still include allergen icons.If you are posting restaurants (or any other venues) to your personal site, please add a few of their permalinks to the IndieWeb Examples here: https://indieweb.org/venue#Indieweb_ExamplesThis is day 40 of #100DaysOfIndieWeb. #100Days← Day 39: https://tantek.com/2023/112/t2/account-migration-post-blog-archive-format→ 🔮Glossaryarticle https://indieweb.org/articlecheckin https://indieweb.org/checkinh-card https://microformats.org/wiki/h-cardh-entry https://microformats.org/wiki/h-entryh-review https://microformats.org/wiki/h-reviewPOSSE https://indieweb.org/POSSEreview https://indieweb.org/reviewURL design https://indieweb.org/URL_designvenue https://indieweb.org/venueReferences¹ https://tantek.com/w/Whistle#design ² https://www.devilsteethbakingcompany.com/menu³ https://arsicault-bakery.com/menus
's status on Monday, 24-Apr-2023 16:34:00 EDT
🌱 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-friendly way. * hours open (perhaps kitchen hours if different) * location (address that links to a map UI or map embed w/o cookies/tracking) * nearest bus/tram/rail stop * payment restrictions (e.g. if only cash, or only credit) or options if you prefer * contact info (including a note about catering if that’s an option) * links to social media profiles * links to restaurant review sites/aggregator pages (e.g. venue permalink on Google Maps, TripAdvisor, Foursquare, Swarm, HappyCow) * menu with item name, description, price, optional-thumbnail, and dietary/allergy notations No you really don’t need the full mess of made-up things at schema-org. The community at OpenStreetMap has done A LOT (most? nearly all?) of the work figuring out the ways to express the above types of information, e.g.: https://wiki.openstreetmap.org/wiki/Key:opening_hours Yet has anyone actually seen a simple semantic HTML page that publishes this kind of information? I’ve web searched many search terms and phrases and found nothing good. Stylistically dated templates for sale. Examples with numerous unnecessary scripts (no your typical user does not care about your clever animated 3D-carousel of pretty photos, certainly not waiting for a megabyte of framework scripts for it). Something built on Bootstrap, unnecessary for today’s mobile-friendly HTML+CSS. I did find one (ONE) blog post from 2007 (those were the days) for semantic markup for a restaurant menu: https://jonchristopher.us/blog/a-semantic-breakdown-of-restaurant-menus/ Unless I find an existing solution soon, I’m going to create something from scratch with h-card (since a restaurant is an organization / venue) and add semantic HTML & class names for various fields, re-using from OpenStreetMap Keys whenever possible. That leaves the URL design, where to publish my restaurant pages on my own site, and rather than rethink it, I will likely go with what I decided in my Whistle short URL design¹ many years ago, which is /v/ at the top level of my site, followed by a slug of my short name for the venue. This way I can play with static HTML pages there, with a shared style sheet in that same directory, without impacting anything else on my site. I have some other thoughts around iconography for various diet preferences / allergen warnings for menu items that I’ve tried (or considered), though perhaps I’ll leave those for another post. Or maybe I’ll braindump them now, however incomplete, to see if they resonate or anyone has better suggestions (restaurants and menus really have no standard for these) 🌱 vegan & gluten-free 🌱🌾 vegan + gluten 🌱🥜 vegan + nuts 🌱🍫 vegan + chocolate 🌱🍯 vegetarian (has honey) 🌱🧈 vegetarian (has butter) 🌱🥛 vegetarian (has milk, cream, or yogurt) 🌱🧀 vegetarian (has cheese) 🌱🥚 vegetarian (has egg) with combinations as necessary. For example, a breakfast sandwich at Devil’s Teeth Bakery²: * Regular Breakfast Sandwich (no bacon!) $10.00 🌱🌾🧈🧀🥚 Or a chocolate croissant at Arsicault³: * Chocolate Croissant $5.75 🌱🌾🧈🍫 Non-vegetarian items would omit the plant 🌱 icon/emoji, but could still include allergen icons. If you are posting restaurants (or any other venues) to your personal site, please add a few of their permalinks to the IndieWeb Examples here: https://indieweb.org/venue#Indieweb_Examples This is day 40 of #100DaysOfIndieWeb. #100Days ← Day 39: https://tantek.com/2023/112/t2/account-migration-post-blog-archive-format → 🔮 Glossary article https://indieweb.org/article checkin https://indieweb.org/checkin h-card https://microformats.org/wiki/h-card h-entry https://microformats.org/wiki/h-entry h-review https://microformats.org/wiki/h-review POSSE https://indieweb.org/POSSE review https://indieweb.org/review URL design https://indieweb.org/URL_design venue https://indieweb.org/venue References ¹ https://tantek.com/w/Whistle#design ² https://www.devilsteethbakingcompany.com/menu ³ https://arsicault-bakery.com/menus
: 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 Format (.bar), first specified here with example file:* https://www.manton.org/2017/11/24/blog-archive-format.htmlMore details and another example file:* https://www.manton.org/2021/12/27/importing-blog-archive.htmlBlog Archive Format has the very nice features of:* portable HTML feed (h-feed) and JSON Feed* photos and other media* locally browsable post archiveNaturally, https://micro.blog/ supports both exporting & importing Blog Archive Format.There’s an interesting opportunity here for an open source converter * from Activity Streams 2.0 * to Blog Archive FormatSuch a library would make an excellent drop-in addition to any #ActivityPub implementation, allowing both export of posts, and also a browsable archive format, so you could visually double check when importing to another service that these were the old posts you were looking for.This would be a good first step, using an open standard, towards Mastodon itself supporting post migration³.Ideally, similar to account migration, the old posts server should also at least:* redirect old permalinks to the new permalinks* redirect any replies being delivered by ActivityPub to the new location* provide #Webmention discovery forwarding from the old URLs to the new URLs (e.g. using HTTP LINK headers)for some amount of time.Want to add support for Blog Archive Format or got questions or feedback?Join in the development conversations: https://chat.indieweb.org/devThis is day 39 of #100DaysOfIndieWeb. #100Days← Day 38: https://tantek.com/2023/110/t2/beyond-mastodon-indieweb-own-domain→ 🔮Glossaryaccount migration https://indieweb.org/account_migrationblog archive format https://indieweb.org/blog_archive_formath-feed https://microformats.org/wiki/h-feedJSON Feed https://www.jsonfeed.org/post migration https://indieweb.org/post_migrationWebmention https://indieweb.org/WebmentionReferences¹ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb² https://github.com/mastodon/documentation/pull/1202³ https://github.com/mastodon/mastodon/issues/12423
's status on Saturday, 22-Apr-2023 20:40:00 EDT
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: Blog Archive Format (.bar), first specified here with example file: * https://www.manton.org/2017/11/24/blog-archive-format.html More details and another example file: * https://www.manton.org/2021/12/27/importing-blog-archive.html Blog Archive Format has the very nice features of: * portable HTML feed (h-feed) and JSON Feed * photos and other media * locally browsable post archive Naturally, https://micro.blog/ supports both exporting & importing Blog Archive Format. There’s an interesting opportunity here for an open source converter * from Activity Streams 2.0 * to Blog Archive Format Such a library would make an excellent drop-in addition to any #ActivityPub implementation, allowing both export of posts, and also a browsable archive format, so you could visually double check when importing to another service that these were the old posts you were looking for. This would be a good first step, using an open standard, towards Mastodon itself supporting post migration³. Ideally, similar to account migration, the old posts server should also at least: * redirect old permalinks to the new permalinks * redirect any replies being delivered by ActivityPub to the new location * provide #Webmention discovery forwarding from the old URLs to the new URLs (e.g. using HTTP LINK headers) for some amount of time. Want to add support for Blog Archive Format or got questions or feedback? Join in the development conversations: https://chat.indieweb.org/dev This is day 39 of #100DaysOfIndieWeb. #100Days ← Day 38: https://tantek.com/2023/110/t2/beyond-mastodon-indieweb-own-domain → 🔮 Glossary account migration https://indieweb.org/account_migration blog archive format https://indieweb.org/blog_archive_format h-feed https://microformats.org/wiki/h-feed JSON Feed https://www.jsonfeed.org/ post migration https://indieweb.org/post_migration Webmention https://indieweb.org/Webmention References ¹ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb ² https://github.com/mastodon/documentation/pull/1202 ³ https://github.com/mastodon/mastodon/issues/12423
: 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 ready to take that next step: https://chat.indieweb.org/This is day 38 of #100DaysOfIndieWeb. #100Days← Day 37: https://tantek.com/2023/109/t2/years-ago-first-federated-indieweb-thread→ 🔮¹ https://indieweb.org/principles² https://indieweb.org/why³ https://mas.to/@pierce/110231624819547202⁴ https://tantek.com/2023/110/t1/⁵ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb⁶ https://indieweb.org/POSSE⁷ https://tantek.com/2023/001/t1/own-your-notes
's status on Thursday, 20-Apr-2023 20:57:00 EDT
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 ready to take that next step: https://chat.indieweb.org/ This is day 38 of #100DaysOfIndieWeb. #100Days ← Day 37: https://tantek.com/2023/109/t2/years-ago-first-federated-indieweb-thread → 🔮 ¹ https://indieweb.org/principles ² https://indieweb.org/why ³ https://mas.to/@pierce/110231624819547202 ⁴ https://tantek.com/2023/110/t1/ ⁵ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb ⁶ https://indieweb.org/POSSE ⁷ https://tantek.com/2023/001/t1/own-your-notes
: 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://aaronparecki.com/2013/05/21/4/xkcd
's status on Wednesday, 19-Apr-2023 20:48:00 EDT
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 ⁵ https://aaronparecki.com/2013/05/21/4/xkcd
: 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 Fed to federate hashtags in posts into Mastodon instances so they would rewrite hashtag links into instance-local hashtag pages:* https://github.com/snarfed/bridgy-fed/issues/45#issuecomment-1468962400Thus even though I’m using the indieweb.social tag space on the hashtag links in my original post, if you are reading this post on Mastodon, you should see a hashtag like #IndieWeb link to your local instance’s tag page for IndieWeb, and my post should show up on that page.From testing a few other instances tag pages, this is now working, e.g. these tag pages:* https://indieweb.social/tags/100DaysofIndieWeb (as expected)* https://xoxo.zone/tags/100DaysOfIndieWeb* https://mozilla.social/tags/100DaysofIndieWebdisplay the #MozFest post¹ I published right after implementing linked hashtags (and any subsequent 100DaysofIndieWeb posts).I did go back and send Webmentions to BridgyFed to send ActivityPub updates for all my past #100DaysofIndieWeb posts, however only a few of them showed up in those tag pages. It’s unclear why a few did and most didn’t, or why there are inconsistencies across instances. More to explore and debug.Federated hashtags definitely need their own specification, because currently they barely interoperate when published, and even then require Mastodon-implementation-specific knowledge to function.The good news is that several of us now have linked hashtags on our personal sites display and link as expected when our posts are federated across Mastodon instances, using a variety of different pieces of software to make it all work.This is day 36 of #100DaysOfIndieWeb #100Days← Day 35: https://tantek.com/2023/081/t1/mozfest-making-fediverse-socialweb→ 🔮Glossaryh-entry https://microformats.org/wiki/h-entryhashtag https://indieweb.org/hashtagstag aggregation https://indieweb.org/tag_aggregationtag page https://indieweb.org/tag_pagetags page https://indieweb.org/tags_page References¹ https://tantek.com/2023/081/t1/mozfest-making-fediverse-socialweb
's status on Tuesday, 11-Apr-2023 02:25:00 EDT
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 Bridgy Fed to federate hashtags in posts into Mastodon instances so they would rewrite hashtag links into instance-local hashtag pages: * https://github.com/snarfed/bridgy-fed/issues/45#issuecomment-1468962400 Thus even though I’m using the indieweb.social tag space on the hashtag links in my original post, if you are reading this post on Mastodon, you should see a hashtag like #IndieWeb link to your local instance’s tag page for IndieWeb, and my post should show up on that page. From testing a few other instances tag pages, this is now working, e.g. these tag pages: * https://indieweb.social/tags/100DaysofIndieWeb (as expected) * https://xoxo.zone/tags/100DaysOfIndieWeb * https://mozilla.social/tags/100DaysofIndieWeb display the #MozFest post¹ I published right after implementing linked hashtags (and any subsequent 100DaysofIndieWeb posts). I did go back and send Webmentions to BridgyFed to send ActivityPub updates for all my past #100DaysofIndieWeb posts, however only a few of them showed up in those tag pages. It’s unclear why a few did and most didn’t, or why there are inconsistencies across instances. More to explore and debug. Federated hashtags definitely need their own specification, because currently they barely interoperate when published, and even then require Mastodon-implementation-specific knowledge to function. The good news is that several of us now have linked hashtags on our personal sites display and link as expected when our posts are federated across Mastodon instances, using a variety of different pieces of software to make it all work. This is day 36 of #100DaysOfIndieWeb #100Days ← Day 35: https://tantek.com/2023/081/t1/mozfest-making-fediverse-socialweb → 🔮 Glossary h-entry https://microformats.org/wiki/h-entry hashtag https://indieweb.org/hashtags tag aggregation https://indieweb.org/tag_aggregation tag page https://indieweb.org/tag_page tags page https://indieweb.org/tags_page References ¹ https://tantek.com/2023/081/t1/mozfest-making-fediverse-socialweb
: 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
's status on Wednesday, 22-Mar-2023 11:14:00 EDT
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
: 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
's status on Monday, 13-Mar-2023 19:51:00 EDT
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
: 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 other approaches.We (as chairs) decided to do something which very few standards groups do, and for that matter, have ever done successfully.From 15+ different approaches, or projects, or efforts that were brought⁵ to the working group, we narrowed them down to about 2.5 which I can summarize as:1. #IndieWeb building blocks, many of which were already implemented, deployed, and showing rough interoperability across numerous independent websites2. ActivityStreams based approaches, which also demonstrated implementability, interoperability, and real user value as part of the OStatus suite, implemented in StatusNet, Identica, etc.2.5 "something with Linked Data (LD)" — expressed as a 0.5 because there wasn’t anything user-visible “social web” with LD working at the start of the Working Group, however there was a very passionate set of participants insisting that everything be done with RDF/LD, despite the fact that it was less of a proven social web approach than the other two.As chairs we figured out that if we were able to help facilitate the development of these 2.5 approaches in parallel, nearly everyone who was active in the Working Group would have something they would feel like they could direct their positive energy into, instead of spending time fighting or tearing down someone else’s approach.It was a very difficult social-technical balance to maintain, and we hit more than a few bumps along the way. However we also had many moments of alignment, where two (or all) of the various approaches found common problems, and either identical or at least compatible solutions.I saw many examples where the discoveries of one approach helped inform and improve another approach. Developing more than one approach in the same working group was not only possible, it actually worked.I also saw examples of different problems being solved by different approaches, and I found that aspect particularly fascinating and hopeful. Multiple approaches were able to choose & priortize different subsets of social web use-cases and problems to solve from the larger space of decentralized social web challenges. By doing so, different approaches often explored and mapped out different areas of the larger social web space.I’m still a bit amazed we were able to complete all of those Recommendations in less than four years, and everyone who participated in the working group should be proud of that accomplishment, beyond any one specification they may have worked on.With hindsight, we can see the positive practical benefits from allowing & facilitating multiple approaches to move forward. Today there is both a very healthy & growing set of folks who want simple personal sites to do with as they please (#IndieWeb), and we also have a growing network of Mastodon instances and other software & services that interoperate with them, like Bridgy Fed⁶. Millions of users are posting & interacting with each other daily, without depending on any large central corporate site or service, whether on their own personal domain & site they fully control, or with an account on a trusted community server, using different software & services.Choosing to go from 15+ down to 2.5, but not down to 1 approach turned out to be the right answer, to both allow a wide variety⁷ of decentralized social web efforts to grow, interoperate via bridges, and frankly, socially to provide something positive for everyone to contribute to, instead of wasting weeks, possibly months in heated debates about which one approach was the one true way.There’s lots more to be written about the history of the Social Web Working Group, which perhaps I will do some day.For now, if you’re curious for more, I strongly recommend diving into the group’s wiki https://www.w3.org/wiki/Socialwg and its subpages for more historical details. All the minutes of our meetings are there. All the research we conducted is there.If you’re interested in contributing to the specifications we developed, find the place where that work is being done, the people actively implementing those specs, and even better, actively using their own implementations⁸.You can find the various IndieWeb building blocks living specifications here:* https://spec.indieweb.org/And discussions thereof in the development chat channel:* https://chat.indieweb.org/devIf you’re not sure, pop by the indieweb-dev chat and ask anyway!The IndieWeb community has grown only larger and more diverse in approaches & implementations in the past five years, and we regularly have discussions about most of the specifications that were developed in the Social Web Working Group.This is day 33 of #100DaysOfIndieWeb #100Days← Day 32: https://tantek.com/2023/047/t1/nineteen-years-microformats→ 🔮Post Glossary:ActivityPub https://www.w3.org/TR/activitypub/ ActivityStreams2 https://www.w3.org/TR/activitystreams-core/ https://www.w3.org/TR/activitystreams-vocabulary/Linked Data Notifications https://www.w3.org/TR/ldn/Micropub https://micropub.spec.indieweb.org/Webmention https://webmention.net/draft/WebSub https://www.w3.org/TR/websub/References:¹ https://www.w3.org/wiki/Socialwg² https://www.w3.org/wiki/Socialwg/2015-03-18-minutes#solid³ https://mastodon.cloud/@anildash/109299991009836007⁴ https://websub.rocks/⁵ https://indieweb.org/Social_Web_Working_Group#History⁶ https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed⁷ https://indieweb.org/plurality⁸ https://indieweb.org/use_what_you_make
's status on Monday, 20-Feb-2023 22:16:00 EST
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 developing other approaches. We (as chairs) decided to do something which very few standards groups do, and for that matter, have ever done successfully. From 15+ different approaches, or projects, or efforts that were brought⁵ to the working group, we narrowed them down to about 2.5 which I can summarize as: 1. #IndieWeb building blocks, many of which were already implemented, deployed, and showing rough interoperability across numerous independent websites 2. ActivityStreams based approaches, which also demonstrated implementability, interoperability, and real user value as part of the OStatus suite, implemented in StatusNet, Identica, etc. 2.5 "something with Linked Data (LD)" — expressed as a 0.5 because there wasn’t anything user-visible “social web” with LD working at the start of the Working Group, however there was a very passionate set of participants insisting that everything be done with RDF/LD, despite the fact that it was less of a proven social web approach than the other two. As chairs we figured out that if we were able to help facilitate the development of these 2.5 approaches in parallel, nearly everyone who was active in the Working Group would have something they would feel like they could direct their positive energy into, instead of spending time fighting or tearing down someone else’s approach. It was a very difficult social-technical balance to maintain, and we hit more than a few bumps along the way. However we also had many moments of alignment, where two (or all) of the various approaches found common problems, and either identical or at least compatible solutions. I saw many examples where the discoveries of one approach helped inform and improve another approach. Developing more than one approach in the same working group was not only possible, it actually worked. I also saw examples of different problems being solved by different approaches, and I found that aspect particularly fascinating and hopeful. Multiple approaches were able to choose & priortize different subsets of social web use-cases and problems to solve from the larger space of decentralized social web challenges. By doing so, different approaches often explored and mapped out different areas of the larger social web space. I’m still a bit amazed we were able to complete all of those Recommendations in less than four years, and everyone who participated in the working group should be proud of that accomplishment, beyond any one specification they may have worked on. With hindsight, we can see the positive practical benefits from allowing & facilitating multiple approaches to move forward. Today there is both a very healthy & growing set of folks who want simple personal sites to do with as they please (#IndieWeb), and we also have a growing network of Mastodon instances and other software & services that interoperate with them, like Bridgy Fed⁶. Millions of users are posting & interacting with each other daily, without depending on any large central corporate site or service, whether on their own personal domain & site they fully control, or with an account on a trusted community server, using different software & services. Choosing to go from 15+ down to 2.5, but not down to 1 approach turned out to be the right answer, to both allow a wide variety⁷ of decentralized social web efforts to grow, interoperate via bridges, and frankly, socially to provide something positive for everyone to contribute to, instead of wasting weeks, possibly months in heated debates about which one approach was the one true way. There’s lots more to be written about the history of the Social Web Working Group, which perhaps I will do some day. For now, if you’re curious for more, I strongly recommend diving into the group’s wiki https://www.w3.org/wiki/Socialwg and its subpages for more historical details. All the minutes of our meetings are there. All the research we conducted is there. If you’re interested in contributing to the specifications we developed, find the place where that work is being done, the people actively implementing those specs, and even better, actively using their own implementations⁸. You can find the various IndieWeb building blocks living specifications here: * https://spec.indieweb.org/ And discussions thereof in the development chat channel: * https://chat.indieweb.org/dev If you’re not sure, pop by the indieweb-dev chat and ask anyway! The IndieWeb community has grown only larger and more diverse in approaches & implementations in the past five years, and we regularly have discussions about most of the specifications that were developed in the Social Web Working Group. This is day 33 of #100DaysOfIndieWeb #100Days ← Day 32: https://tantek.com/2023/047/t1/nineteen-years-microformats → 🔮 Post Glossary: ActivityPub https://www.w3.org/TR/activitypub/ ActivityStreams2 https://www.w3.org/TR/activitystreams-core/ https://www.w3.org/TR/activitystreams-vocabulary/ Linked Data Notifications https://www.w3.org/TR/ldn/ Micropub https://micropub.spec.indieweb.org/ Webmention https://webmention.net/draft/ WebSub https://www.w3.org/TR/websub/ References: ¹ https://www.w3.org/wiki/Socialwg ² https://www.w3.org/wiki/Socialwg/2015-03-18-minutes#solid ³ https://mastodon.cloud/@anildash/109299991009836007 ⁴ https://websub.rocks/ ⁵ https://indieweb.org/Social_Web_Working_Group#History ⁶ https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed ⁷ https://indieweb.org/plurality ⁸ https://indieweb.org/use_what_you_make
: 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 benefit of years of experience since we proposed “microformats”:One: Many microformats succeeded because we solved an existing problem, with existing *complex* solutions, by providing a drastically *simpler* solution.XFN instead of FOAF. rel=license instead of Creative Commons RDF in HTML comments.By doing so, we skipped the often harder problem of defining & refining a problem worth solving, a use-case, or user scenario.Two: A few microformats succeeded because they solved existing problems, re-using *existing established* open solutions in other formats, reformatted into native HTML.hCard from vCard. hCalendar from iCalendar.This methodology leveraged years of prior hard open standards work by numerous others across numerous organizations, and deliberately avoided the bikeshedding trap of renaming things (or any other kind of non-trivial “clean-up”) while reformatting, thus making it easy for developers of one technology to see the 1:1 mapping and use the other.The primary downside with this approach was formats that were larger than perhaps necessary for HTML-specific use-cases.Eventually for microformats2 vocabularies, we adopted a subset approach, looking for web publishing use-cases for each feature, making h-card smaller than hCard, and h-event smaller than hCalendar.Three: Success in a search engine was not enough, and sometimes attracted more bad actors than good. @KevinMarks.com, myself, and others at Technorati built search engine indexing and use of rel-tag and hReview, which helped evolve their specifications. A few other small search engines indexed rel=tag markup, however none remain today. hReview was adopted by Google which led to it being heavily spammed.This pattern repeated itself with other microformats, and eventually we shifted from:→ of course search is the first obvious use-case→ search is one use-case among others→ we need primary use-cases outside of search for longterm ecosystem successWhich leads to the fourth observation.Four: Publishing alone is not a use-case. There must be multiple consuming code use-cases (beyond search) for a microformat to succeed longterm.From individual features to whole microformats vocabularies, we learned that not only did there need to be sufficient content being published already, without microformats, that could benefit, but there needed to be good enough consuming code use-cases that benefited users (not just developers). The #IndieWeb community has been exceptionally helpful in both defining such use-cases and iterating on them with implementations.We still get questions of the form: What’s the best way to mark this up?I used to very much believe that if you could mark something up more semantically, you should spend the time & effort to do so. This drove a lot of early experiments with markup, and did provide some eventual benefits, most notably when semantic HTML elements provided good hooks for accessibility tools such as screen readers.Now we know the answer to the question of “How should I mark-up this content?” must be accompanied by specific use-cases for consuming code of that markup. If there is no consuming code use-case, it is not worth the time to add the mark-up (never mind the maintenance effort over time).Sometimes one single consuming code use-case is sufficient to justify the time & effort to add more semantic mark-up. If that markup helps screenreaders, then it’s worth it. More often than not however, there must be multiple (again, beyond search) consuming code use-cases for it to be worth adding semantic markup, and certainly for developing new markup, whether microformats features or new microformats.This focus on and repeated asking of questions like:* What is the (consuming code) use-case? * Or how does it benefit readers of this content?has helped focus our modern microformats efforts on actual benefits to humans first, and machines second (if at all).If you think of IndieWeb use-cases for existing or new microformats, come join us in the developers chat:* https://chat.indieweb.org/devIf you think of other use-cases or want to chat about modern microformats methodologies in general, join us in the microformats chat:* https://chat.indieweb.org/microformatsThis is day 32 of #100DaysOfIndieWeb #100Days← Day 31: https://tantek.com/2023/044/t1/unified-sent-box-universal-outbox→ 🔮Post glossary:h-card https://microformats.org/wiki/h-cardh-entry https://microformats.org/wiki/h-entryh-event https://microformats.org/wiki/h-eventh-review https://microformats.org/wiki/h-reviewhAtom https://microformats.org/wiki/hatomhCalendar https://microformats.org/wiki/hcalendarhCard https://microformats.org/wiki/hcardhReview https://microformats.org/wiki/hreviewrel-license https://microformats.org/wiki/rel-licenserel-tag https://microformats.org/wiki/rel-tagrel-values https://microformats.org/wiki/existing-rel-valuesXFN https://gmpg.org/xfn/XMDP http://gmpg.org/xmdp/descriptionXOXO https://microformats.org/wiki/xoxoPreviously, previously, previously:* https://tantek.com/2019/044/t1/15-years-ago-introduced-microformats* https://tantek.com/2014/042/t2/ten-years-ago-introduced-microformats-etech* https://tantek.com/2011/042/t2/years-ago-presented-microformats-etech* https://twitter.com/t/status/701095802References:¹ https://tantek.com/presentations/2004etech/realworldsemanticspres.html² https://tantek.com/log/2004/02.html#d04t1311³ https://gmpg.org/xfn/11#me⁴ https://docs.joinmastodon.org/user/profile/#verification⁵ https://hachyderm.io/@nova/109790530971147702⁶ https://tantek.com/2023/032/t1/years-relmeauth-replace-openid⁷ https://tantek.com/2012/353/b1/why-html-classes-css-class-selectors⁸ http://microformats.org/wiki/events/2007-12-11-open-media-web
's status on Thursday, 16-Feb-2023 20:01:00 EST
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 observations with the benefit of years of experience since we proposed “microformats”: One: Many microformats succeeded because we solved an existing problem, with existing *complex* solutions, by providing a drastically *simpler* solution. XFN instead of FOAF. rel=license instead of Creative Commons RDF in HTML comments. By doing so, we skipped the often harder problem of defining & refining a problem worth solving, a use-case, or user scenario. Two: A few microformats succeeded because they solved existing problems, re-using *existing established* open solutions in other formats, reformatted into native HTML. hCard from vCard. hCalendar from iCalendar. This methodology leveraged years of prior hard open standards work by numerous others across numerous organizations, and deliberately avoided the bikeshedding trap of renaming things (or any other kind of non-trivial “clean-up”) while reformatting, thus making it easy for developers of one technology to see the 1:1 mapping and use the other. The primary downside with this approach was formats that were larger than perhaps necessary for HTML-specific use-cases. Eventually for microformats2 vocabularies, we adopted a subset approach, looking for web publishing use-cases for each feature, making h-card smaller than hCard, and h-event smaller than hCalendar. Three: Success in a search engine was not enough, and sometimes attracted more bad actors than good. @KevinMarks.com, myself, and others at Technorati built search engine indexing and use of rel-tag and hReview, which helped evolve their specifications. A few other small search engines indexed rel=tag markup, however none remain today. hReview was adopted by Google which led to it being heavily spammed. This pattern repeated itself with other microformats, and eventually we shifted from: → of course search is the first obvious use-case → search is one use-case among others → we need primary use-cases outside of search for longterm ecosystem success Which leads to the fourth observation. Four: Publishing alone is not a use-case. There must be multiple consuming code use-cases (beyond search) for a microformat to succeed longterm. From individual features to whole microformats vocabularies, we learned that not only did there need to be sufficient content being published already, without microformats, that could benefit, but there needed to be good enough consuming code use-cases that benefited users (not just developers). The #IndieWeb community has been exceptionally helpful in both defining such use-cases and iterating on them with implementations. We still get questions of the form: What’s the best way to mark this up? I used to very much believe that if you could mark something up more semantically, you should spend the time & effort to do so. This drove a lot of early experiments with markup, and did provide some eventual benefits, most notably when semantic HTML elements provided good hooks for accessibility tools such as screen readers. Now we know the answer to the question of “How should I mark-up this content?” must be accompanied by specific use-cases for consuming code of that markup. If there is no consuming code use-case, it is not worth the time to add the mark-up (never mind the maintenance effort over time). Sometimes one single consuming code use-case is sufficient to justify the time & effort to add more semantic mark-up. If that markup helps screenreaders, then it’s worth it. More often than not however, there must be multiple (again, beyond search) consuming code use-cases for it to be worth adding semantic markup, and certainly for developing new markup, whether microformats features or new microformats. This focus on and repeated asking of questions like: * What is the (consuming code) use-case? * Or how does it benefit readers of this content? has helped focus our modern microformats efforts on actual benefits to humans first, and machines second (if at all). If you think of IndieWeb use-cases for existing or new microformats, come join us in the developers chat: * https://chat.indieweb.org/dev If you think of other use-cases or want to chat about modern microformats methodologies in general, join us in the microformats chat: * https://chat.indieweb.org/microformats This is day 32 of #100DaysOfIndieWeb #100Days ← Day 31: https://tantek.com/2023/044/t1/unified-sent-box-universal-outbox → 🔮 Post glossary: h-card https://microformats.org/wiki/h-card h-entry https://microformats.org/wiki/h-entry h-event https://microformats.org/wiki/h-event h-review https://microformats.org/wiki/h-review hAtom https://microformats.org/wiki/hatom hCalendar https://microformats.org/wiki/hcalendar hCard https://microformats.org/wiki/hcard hReview https://microformats.org/wiki/hreview rel-license https://microformats.org/wiki/rel-license rel-tag https://microformats.org/wiki/rel-tag rel-values https://microformats.org/wiki/existing-rel-values XFN https://gmpg.org/xfn/ XMDP http://gmpg.org/xmdp/description XOXO https://microformats.org/wiki/xoxo Previously, previously, previously: * https://tantek.com/2019/044/t1/15-years-ago-introduced-microformats * https://tantek.com/2014/042/t2/ten-years-ago-introduced-microformats-etech * https://tantek.com/2011/042/t2/years-ago-presented-microformats-etech * https://twitter.com/t/status/701095802 References: ¹ https://tantek.com/presentations/2004etech/realworldsemanticspres.html ² https://tantek.com/log/2004/02.html#d04t1311 ³ https://gmpg.org/xfn/11#me ⁴ https://docs.joinmastodon.org/user/profile/#verification ⁵ https://hachyderm.io/@nova/109790530971147702 ⁶ https://tantek.com/2023/032/t1/years-relmeauth-replace-openid ⁷ https://tantek.com/2012/353/b1/why-html-classes-css-class-selectors ⁸ http://microformats.org/wiki/events/2007-12-11-open-media-web
: 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 are a part of your Universal Outbox, they are only a subset. Even if you include everything you can PESOS from other sites, that still leaves services and sites without API access, or with APIs you may not have permission to use.Another approach that may work well is a browser add-on, which would at least be able to collect everything you type into websites. Such an add-on would be more useful than a keylogger, because a browser add-on would have a much better understanding of and access to the context of where you are entering information. An add-on could keep track of permalinks to each statement, e.g. each statement in Slack has a permalink (viewable only with login).A modest prototype add-on could start with my initial suggestion, a universal sent box that aggregated everything you said across all Slack instances you use in that browser. This would be particularly useful for keeping a personal log of your statements across free Slack instances where everything you say disappears in 90 days.For now, perhaps the manual-until-it-hurts answer is to periodically check the “Drafts & sent” folder in free Slacks (from the bottom upwards, since Slack’s web UI lacks the ability to sort or reverse the order of your Drafts & sent folder), one instance at a time, blogging or otherwise copy/pasting anything you want to cite, save, or remember.This is day 31 of #100DaysOfIndieWeb #100Days← Day 30: https://tantek.com/2023/043/t1/footnotes-unicode-links→ 🔮Post Glossary:composite stream https://indieweb.org/composite_streammanual-until-it-hurts https://indieweb.org/manual_until_it_hurtspermalink https://indieweb.org/permalinkPESOS https://indieweb.org/PESOSreacji https://indieweb.org/reacjiresponses https://indieweb.org/responses ¹ https://chat.indieweb.org/2023-02-02#t1675370124338700² https://en.wikipedia.org/wiki/Apple_Open_Collaboration_Environment³ https://indieweb.org/own_your_data
's status on Tuesday, 14-Feb-2023 01:33:00 EST
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 personal site are a part of your Universal Outbox, they are only a subset. Even if you include everything you can PESOS from other sites, that still leaves services and sites without API access, or with APIs you may not have permission to use. Another approach that may work well is a browser add-on, which would at least be able to collect everything you type into websites. Such an add-on would be more useful than a keylogger, because a browser add-on would have a much better understanding of and access to the context of where you are entering information. An add-on could keep track of permalinks to each statement, e.g. each statement in Slack has a permalink (viewable only with login). A modest prototype add-on could start with my initial suggestion, a universal sent box that aggregated everything you said across all Slack instances you use in that browser. This would be particularly useful for keeping a personal log of your statements across free Slack instances where everything you say disappears in 90 days. For now, perhaps the manual-until-it-hurts answer is to periodically check the “Drafts & sent” folder in free Slacks (from the bottom upwards, since Slack’s web UI lacks the ability to sort or reverse the order of your Drafts & sent folder), one instance at a time, blogging or otherwise copy/pasting anything you want to cite, save, or remember. This is day 31 of #100DaysOfIndieWeb #100Days ← Day 30: https://tantek.com/2023/043/t1/footnotes-unicode-links → 🔮 Post Glossary: composite stream https://indieweb.org/composite_stream manual-until-it-hurts https://indieweb.org/manual_until_it_hurts permalink https://indieweb.org/permalink PESOS https://indieweb.org/PESOS reacji https://indieweb.org/reacji responses https://indieweb.org/responses ¹ https://chat.indieweb.org/2023-02-02#t1675370124338700 ² https://en.wikipedia.org/wiki/Apple_Open_Collaboration_Environment ³ https://indieweb.org/own_your_data
: 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/forward-in-time-links⁴ https://tantek.com/⁵ https://indieweb.org/footnote
's status on Sunday, 12-Feb-2023 23:06:00 EST
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.com/2023/006/t1/forward-in-time-links ⁴ https://tantek.com/ ⁵ https://indieweb.org/footnote
: 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 my previous post^1 I also used a glossary syntax resembling common print conventions:term or phrase on its own line without punctuation space-indented link to a defining page, or inline definition, or bothThis pattern (when repeated with two or more adjacent instances) looks like it may be detectable for auto-markup with HTML definition (description) list , term , and details elements. Perhaps as part of existing auto-markup code.For fallback handling in syndication destinations that remove^2 HTML definition related elements, I’ll likely still have to include explicit linebreaks & spaces to preserve that presentation, perhaps marked-up to style them to remove their spacing when in the context of the HTML definition elements.I have started a glossary page on the IndieWeb wiki with some of these thoughts:* https://indieweb.org/glossaryThis is day 29 of #100DaysOfIndieWeb #100Days← Day 28: https://tantek.com/2023/036/t1/footnotes-unicode-hyperlink→ 🔮Post Glossary:auto-markup code to automatically add markup to text that implies a semantic or to preserve meaningful spaces like https://indieweb.org/auto-spaceHTML definition list https://developer.mozilla.org/en-US/docs/Web/HTML/Element/dl ^1 https://tantek.com/2023/036/t1/footnotes-unicode-hyperlink^2 https://indieweb.org/sanitize#Software_Examples
's status on Monday, 06-Feb-2023 20:04:00 EST
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 the future. In my previous post^1 I also used a glossary syntax resembling common print conventions: term or phrase on its own line without punctuation space-indented link to a defining page, or inline definition, or both This pattern (when repeated with two or more adjacent instances) looks like it may be detectable for auto-markup with HTML definition (description) list , term , and details elements. Perhaps as part of existing auto-markup code. For fallback handling in syndication destinations that remove^2 HTML definition related elements, I’ll likely still have to include explicit linebreaks & spaces to preserve that presentation, perhaps marked-up to style them to remove their spacing when in the context of the HTML definition elements. I have started a glossary page on the IndieWeb wiki with some of these thoughts: * https://indieweb.org/glossary This is day 29 of #100DaysOfIndieWeb #100Days ← Day 28: https://tantek.com/2023/036/t1/footnotes-unicode-hyperlink → 🔮 Post Glossary: auto-markup code to automatically add markup to text that implies a semantic or to preserve meaningful spaces like https://indieweb.org/auto-space HTML definition list https://developer.mozilla.org/en-US/docs/Web/HTML/Element/dl ^1 https://tantek.com/2023/036/t1/footnotes-unicode-hyperlink ^2 https://indieweb.org/sanitize#Software_Examples
: 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 usually (e.g. on Twitter) lack enough space for the expansions, and there is less chance of ASCII footnotes being misunderstood as part of something else on those destinations. POSSE destinations are in general lower fidelity than a personal site, so it’s ok have this be another instance where the original looks better than the copy.I collected many of these thoughts in a brainstorming section on the IndieWeb wiki accordingly, and will update that as I make progress:https://indieweb.org/footnote#BrainstormingIf you use footnotes in your personal site posts, please add yourself to the IndieWeb Examples section:https://indieweb.org/footnote#IndieWeb_ExamplesThis is day 28 of #100DaysOfIndieWeb #100Days← Day 27: https://tantek.com/2023/033/t1/twitter-api-log-in-web-sign-in-relmeauth→ 🔮Post Glossary: autolink https://indieweb.org/autolinkCASSIS https://indieweb.org/CASSISPOSSE https://indieweb.org/POSSEUnicode superscripts https://en.wikipedia.org/wiki/Superscripts_and_Subscripts_(Unicode_block)
's status on Monday, 06-Feb-2023 02:40:00 EST
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 usually (e.g. on Twitter) lack enough space for the expansions, and there is less chance of ASCII footnotes being misunderstood as part of something else on those destinations. POSSE destinations are in general lower fidelity than a personal site, so it’s ok have this be another instance where the original looks better than the copy. I collected many of these thoughts in a brainstorming section on the IndieWeb wiki accordingly, and will update that as I make progress: https://indieweb.org/footnote#Brainstorming If you use footnotes in your personal site posts, please add yourself to the IndieWeb Examples section: https://indieweb.org/footnote#IndieWeb_Examples This is day 28 of #100DaysOfIndieWeb #100Days ← Day 27: https://tantek.com/2023/033/t1/twitter-api-log-in-web-sign-in-relmeauth → 🔮 Post Glossary: autolink https://indieweb.org/autolink CASSIS https://indieweb.org/CASSIS POSSE https://indieweb.org/POSSE Unicode superscripts https://en.wikipedia.org/wiki/Superscripts_and_Subscripts_(Unicode_block)
: 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
's status on Friday, 03-Feb-2023 02:59:00 EST
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
: 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
's status on Wednesday, 01-Feb-2023 17:34:00 EST
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
: 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 concept of the IndieWeb goes far beyond blogging, or any jargon like decentralization or federation.^4The aforementioned principles^11 provide a good foundation for the IndieWeb, and a good contrast from the prevailing project-centric attitudes of the day. The practices described inside each principle, such as owning your data meaning owning your notes^14 as well, start to hint at what it means to do & be IndieWeb today.If you have a blog on your own domain, and yet you post notes as tweets or toots on someone else’s domain, are you “doing” IndieWeb?Such a split practice could be considered a mid-to-late 2000s approach to the “indie web”, but certainly not the 2023 IndieWeb. Since 2010, the IndieWeb evolved & extended far beyond blogs, into many kinds of posts^15 typical in social media (but lacking in blogs), and site-to-site social web interactions^16, like replies that looked like actual comments, rather than awkwardly displayed blog trackbacks/pingbacks.Either way, if you have your own site (whether a blog or not) and create with it, like the 2001 Independents Day encouragement, come join us^17, and we’ll help you get setup to do so much more.This is day 25 of #100DaysOfIndieWeb #100Days← Day 24: https://tantek.com/2023/027/t5/contrast-domain-chat-name→ 🔮^1 1997-02-01 https://web.archive.org/web/20010805195949/http://www.uzine.net/article63.html^2 https://en.wikipedia.org/wiki/Blog#History^3 https://indieweb.org/#Beyond_Blogging_and_Decentralization^4 https://indieweb.org/different^5 http://tantek.com/2010/123/t2/blogger-turned-off-ftp-what-indie-web-diso (https://twitter.com/t/status/13329370781)^6 https://indieweb.org/Independents_Day^7 https://indieweb.org/creator^8 https://web.archive.org/web/20100723133231/http://federatedsocialweb.net/wiki/2010-199-tantek-fsws-talk^9 https://indieweb.org/Federated_Social_Web_Summit#Portland_2010^10 https://indieweb.org/founders#IndieWeb_movement_and_terminology^11 https://indieweb.org/principles^12 https://indieweb.org/homepage^13 https://indieweb.org/portfolio^14 https://tantek.com/2023/001/t1/own-your-notes^15 https://indieweb.org/posts#Types_of_Posts^16 https://indieweb.org/responses^17 https://chat.indieweb.org/
's status on Sunday, 29-Jan-2023 23:42:00 EST
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 concept of the IndieWeb goes far beyond blogging, or any jargon like decentralization or federation.^4 The aforementioned principles^11 provide a good foundation for the IndieWeb, and a good contrast from the prevailing project-centric attitudes of the day. The practices described inside each principle, such as owning your data meaning owning your notes^14 as well, start to hint at what it means to do & be IndieWeb today. If you have a blog on your own domain, and yet you post notes as tweets or toots on someone else’s domain, are you “doing” IndieWeb? Such a split practice could be considered a mid-to-late 2000s approach to the “indie web”, but certainly not the 2023 IndieWeb. Since 2010, the IndieWeb evolved & extended far beyond blogs, into many kinds of posts^15 typical in social media (but lacking in blogs), and site-to-site social web interactions^16, like replies that looked like actual comments, rather than awkwardly displayed blog trackbacks/pingbacks. Either way, if you have your own site (whether a blog or not) and create with it, like the 2001 Independents Day encouragement, come join us^17, and we’ll help you get setup to do so much more. This is day 25 of #100DaysOfIndieWeb #100Days ← Day 24: https://tantek.com/2023/027/t5/contrast-domain-chat-name → 🔮 ^1 1997-02-01 https://web.archive.org/web/20010805195949/http://www.uzine.net/article63.html ^2 https://en.wikipedia.org/wiki/Blog#History ^3 https://indieweb.org/#Beyond_Blogging_and_Decentralization ^4 https://indieweb.org/different ^5 http://tantek.com/2010/123/t2/blogger-turned-off-ftp-what-indie-web-diso (https://twitter.com/t/status/13329370781) ^6 https://indieweb.org/Independents_Day ^7 https://indieweb.org/creator ^8 https://web.archive.org/web/20100723133231/http://federatedsocialweb.net/wiki/2010-199-tantek-fsws-talk ^9 https://indieweb.org/Federated_Social_Web_Summit#Portland_2010 ^10 https://indieweb.org/founders#IndieWeb_movement_and_terminology ^11 https://indieweb.org/principles ^12 https://indieweb.org/homepage ^13 https://indieweb.org/portfolio ^14 https://tantek.com/2023/001/t1/own-your-notes ^15 https://indieweb.org/posts#Types_of_Posts ^16 https://indieweb.org/responses ^17 https://chat.indieweb.org/
: 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 template allowed us to add personal time zones as well, to enable things like asking in chat, “what time is it for tantek”. This works well enough, except does not account for cross-time-zone travel, though you could update your chat-name entry if you wanted to while traveling.Having all our chat-names in a single list^11 on a page like that revealed another interesting aspect: we have folks across all the timezones in the US & Europe, some in the Middle East, Australia, and most of Asia as well.As a result, the IndieWeb chat channels have people awake and often discussing various topics 24 hours a day.Drop by^8 and say hi, and be sure to have a look at our Code of Conduct.^12This is day 24 of #100DaysOfIndieWeb #100Days← Day 23: https://tantek.com/2023/027/t4/five-years-websub→ 🔮^1 https://tantek.com/2023/026/t1/indieweb-priorities-balance^2 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb^3 https://indieweb.org/chat-names^4 https://indieweb.org/discuss^5 https://indieweb.org/IndieAuth^6 https://indieweb.org/Web_sign-in^7 https://indieweb.org/admintax^8 https://chat.indieweb.org/^9 https://indieweb.org/discuss#Join_Discussions^10 https://indieweb.org/icon^11 https://indieweb.org/chat-names#Nicknames^12 https://indieweb.org/code-of-conduct
's status on Saturday, 28-Jan-2023 02:11:00 EST
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 template allowed us to add personal time zones as well, to enable things like asking in chat, “what time is it for tantek”. This works well enough, except does not account for cross-time-zone travel, though you could update your chat-name entry if you wanted to while traveling. Having all our chat-names in a single list^11 on a page like that revealed another interesting aspect: we have folks across all the timezones in the US & Europe, some in the Middle East, Australia, and most of Asia as well. As a result, the IndieWeb chat channels have people awake and often discussing various topics 24 hours a day. Drop by^8 and say hi, and be sure to have a look at our Code of Conduct.^12 This is day 24 of #100DaysOfIndieWeb #100Days ← Day 23: https://tantek.com/2023/027/t4/five-years-websub → 🔮 ^1 https://tantek.com/2023/026/t1/indieweb-priorities-balance ^2 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb ^3 https://indieweb.org/chat-names ^4 https://indieweb.org/discuss ^5 https://indieweb.org/IndieAuth ^6 https://indieweb.org/Web_sign-in ^7 https://indieweb.org/admintax ^8 https://chat.indieweb.org/ ^9 https://indieweb.org/discuss#Join_Discussions ^10 https://indieweb.org/icon ^11 https://indieweb.org/chat-names#Nicknames ^12 https://indieweb.org/code-of-conduct
: 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
's status on Friday, 27-Jan-2023 22:51:00 EST
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
: 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
's status on Friday, 27-Jan-2023 02:22:00 EST
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
: 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
's status on Monday, 23-Jan-2023 02:49:00 EST
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
: 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^4 https://indieweb.org/test_in_production^5 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention^6 https://indieweb.org/test_in_production#IndieWeb_Examples
's status on Sunday, 22-Jan-2023 19:11:00 EST
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.org/creator ^4 https://indieweb.org/test_in_production ^5 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention ^6 https://indieweb.org/test_in_production#IndieWeb_Examples
: 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
's status on Saturday, 21-Jan-2023 02:54:00 EST
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: 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
: 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
's status on Thursday, 19-Jan-2023 21:05:00 EST
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
: 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
's status on Thursday, 19-Jan-2023 02:11:00 EST
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
: 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 well except for a couple of interesting ongoing challenges:* What is the most efficient user interface path from viewing someone else’s post to writing a reply from your own site?* How should you @-mention someone you are replying to? (and how can our tools write or pre-fill that for us?)Regarding the latter, on day 14 I wrote a bit about how should we @-mention in general https://tantek.com/2023/014/t4/domain-first-federated-atmention though that was more of a general @-mention exploration. As a follow-up to day 14, it’s worth looking into @-reply mentions in particular, specifically for each of the above 1,2,3 contexts, analyzing examples of each, and looking for patterns of @-reply mentions best practices that we can document & recommend.This is day 16 of #100DaysOfIndieWeb #100Days, except I didn’t finish writing it (mostly) til the morning after, and editing later that afternoon.← Day 15: https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute→ 🔮^1 https://en.wikipedia.org/wiki/Internet_forum^2 https://indieweb.org/silo^3 https://indieweb.org/own_your_data^4 https://tantek.com/2023/012/t1/six-years-webmention-w3c^5 https://indieweb.org/GitHub#POSSE_to_GitHub^6 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute^7 https://indieweb.org/site-deaths
's status on Tuesday, 17-Jan-2023 12:05:00 EST
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 worked well except for a couple of interesting ongoing challenges: * What is the most efficient user interface path from viewing someone else’s post to writing a reply from your own site? * How should you @-mention someone you are replying to? (and how can our tools write or pre-fill that for us?) Regarding the latter, on day 14 I wrote a bit about how should we @-mention in general https://tantek.com/2023/014/t4/domain-first-federated-atmention though that was more of a general @-mention exploration. As a follow-up to day 14, it’s worth looking into @-reply mentions in particular, specifically for each of the above 1,2,3 contexts, analyzing examples of each, and looking for patterns of @-reply mentions best practices that we can document & recommend. This is day 16 of #100DaysOfIndieWeb #100Days, except I didn’t finish writing it (mostly) til the morning after, and editing later that afternoon. ← Day 15: https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute → 🔮 ^1 https://en.wikipedia.org/wiki/Internet_forum ^2 https://indieweb.org/silo ^3 https://indieweb.org/own_your_data ^4 https://tantek.com/2023/012/t1/six-years-webmention-w3c ^5 https://indieweb.org/GitHub#POSSE_to_GitHub ^6 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute ^7 https://indieweb.org/site-deaths
: 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 its own.https://indieweb.org/Twitter#POSSE_Replies_to_TwitterSome destinations have content limitations^2, and you may want to take that into consideration when authoring your content, or not.For example, you may want to more carefully copy-edit the first 256 (for now) characters of a note if you plan to POSSE to Twitter, so that the content that makes it through makes sense as an introduction, or a summary, or a hook, and perhaps has discovery features like hashtags. https://indieweb.org/Twitter#POSSE_Notes_to_TwitterYou can use that POSSE tweet text length limitation strategically, placing content after that 256 character cut-off that you may want to edit or expand in an update, or content Twitter may mess-up, like @-domain mentions I described yesterday (day 14).When you publish a multiphoto^3 post, if you’re POSSEing to Twitter, you may want to re-order your photos to choose which four photos show up in your POSSE tweet, e.g. if you happen to be using Bridgy Publish to cross-post your photos to Twitter. You can always re-order your original multiphoto post after POSSEing it. If you’re POSSEing photos to Instagram, since you can only do that manually, there’s no need to edit your original to fit Instagram’s 10-photo limitation, or 2200 characters caption limit, or 30 hashtags limit, or 20 person-tags limit.https://indieweb.org/multi-photo#How_to_POSSEOr you can reconsider what if anything you get from syndicating to Twitter or Instagram. Are people still seeing and interacting with your posts there? Are your friends?If & when social media algorithms deprioritize your original posts in favor of showing more ads, you can deprioritize posting to social media.If & when your friends quit social media silos^4, you can quit posting copies of your posts to those social media silos.You decide what content goes where, when, why, and can change your decisions any time you want.POSSEing to social media was always a stopgap. As social media silos self-destruct, you can stop syndicating to them.Thanks to Chris Aldrich (https://boffosocko.com/) for the banner image.This is day 15 of #100DaysOfIndieWeb #100Days.← Day 14: https://tantek.com/2023/014/t4/domain-first-federated-atmention→ 🔮^1 https://indieweb.org/POSSE^2 Day 5: https://tantek.com/2023/005/t3/indieweb-simpler-approach^3 https://indieweb.org/multi-photo^4 https://indieweb.org/silo-quits
's status on Monday, 16-Jan-2023 02:58:00 EST
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 there on its own. https://indieweb.org/Twitter#POSSE_Replies_to_Twitter Some destinations have content limitations^2, and you may want to take that into consideration when authoring your content, or not. For example, you may want to more carefully copy-edit the first 256 (for now) characters of a note if you plan to POSSE to Twitter, so that the content that makes it through makes sense as an introduction, or a summary, or a hook, and perhaps has discovery features like hashtags. https://indieweb.org/Twitter#POSSE_Notes_to_Twitter You can use that POSSE tweet text length limitation strategically, placing content after that 256 character cut-off that you may want to edit or expand in an update, or content Twitter may mess-up, like @-domain mentions I described yesterday (day 14). When you publish a multiphoto^3 post, if you’re POSSEing to Twitter, you may want to re-order your photos to choose which four photos show up in your POSSE tweet, e.g. if you happen to be using Bridgy Publish to cross-post your photos to Twitter. You can always re-order your original multiphoto post after POSSEing it. If you’re POSSEing photos to Instagram, since you can only do that manually, there’s no need to edit your original to fit Instagram’s 10-photo limitation, or 2200 characters caption limit, or 30 hashtags limit, or 20 person-tags limit. https://indieweb.org/multi-photo#How_to_POSSE Or you can reconsider what if anything you get from syndicating to Twitter or Instagram. Are people still seeing and interacting with your posts there? Are your friends? If & when social media algorithms deprioritize your original posts in favor of showing more ads, you can deprioritize posting to social media. If & when your friends quit social media silos^4, you can quit posting copies of your posts to those social media silos. You decide what content goes where, when, why, and can change your decisions any time you want. POSSEing to social media was always a stopgap. As social media silos self-destruct, you can stop syndicating to them. Thanks to Chris Aldrich (https://boffosocko.com/) for the banner image. This is day 15 of #100DaysOfIndieWeb #100Days. ← Day 14: https://tantek.com/2023/014/t4/domain-first-federated-atmention → 🔮 ^1 https://indieweb.org/POSSE ^2 Day 5: https://tantek.com/2023/005/t3/indieweb-simpler-approach ^3 https://indieweb.org/multi-photo ^4 https://indieweb.org/silo-quits
: 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 @-mentions (@-name @-domain @-@) and hope to merge them into the repo soon. Aside: both that and the #testInProduction hashtag have hilarious Twitter results^4.Does anyone know of any other auto-linkers that support linking @-domain in plain text to an https URL of that domain? Extra internet points if they also support @-@ auto-linking.This is day 14 of #100DaysOfIndieWeb #100Days.← Day 13: https://tantek.com/2023/013/t1/indieweb-home-internet→ 🔮^1 Day 11: https://tantek.com/2023/011/t1/indieweb-evolving-at-mention^2 I’m curious if StatusNet, OStatus, or OpenMicroBlogging had an explicit syntax for site-to-site @-mentions, whether any of them resembled @-domain, and is there evidence of their earliest @-mention usage (if any) still visible on the web (or Internet Archive) cc: @evanp.me (@evan@prodromou.pub)^3 https://tantek.com/2023/012/t1/six-years-webmention-w3c^4 Navigating to Twitter hashtag results left as an exercise to the reader, to provide a deliberate soft barrier to a potential doomscrolling trap.
's status on Sunday, 15-Jan-2023 02:50:00 EST
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 all @-mentions (@-name @-domain @-@) and hope to merge them into the repo soon. Aside: both that and the #testInProduction hashtag have hilarious Twitter results^4. Does anyone know of any other auto-linkers that support linking @-domain in plain text to an https URL of that domain? Extra internet points if they also support @-@ auto-linking. This is day 14 of #100DaysOfIndieWeb #100Days. ← Day 13: https://tantek.com/2023/013/t1/indieweb-home-internet → 🔮 ^1 Day 11: https://tantek.com/2023/011/t1/indieweb-evolving-at-mention ^2 I’m curious if StatusNet, OStatus, or OpenMicroBlogging had an explicit syntax for site-to-site @-mentions, whether any of them resembled @-domain, and is there evidence of their earliest @-mention usage (if any) still visible on the web (or Internet Archive) cc: @evanp.me (@evan@prodromou.pub) ^3 https://tantek.com/2023/012/t1/six-years-webmention-w3c ^4 Navigating to Twitter hashtag results left as an exercise to the reader, to provide a deliberate soft barrier to a potential doomscrolling trap.
: 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
's status on Saturday, 14-Jan-2023 02:39:00 EST
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
: 🎉 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→ 🔮
's status on Friday, 13-Jan-2023 02:45:00 EST
🎉 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 → 🔮
: 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@mastodon.social), https://simonwillison.net/ (@simon@simonwillison.net) Rather than using social media silo @-names (except when explicitly replying to a silo), I’m now experimenting with all three of these (1-3) instead, both to elevate people’s IndieWeb identities, and for Mastodon viewers, provide a convenient way to follow @-@ addresses.If someone’s homepage receives Webmentions, they will get notified when I @-mention them by domain.I recently implemented syntactic auto-linking of @-@ addresses like this:* @user@example.com --> https://example.com/@userwith a special case for @-domain@-domain to just link to the domain, e.g.:* @tantek.com@tantek.com --> https://tantek.com/I also made a policy decision to auto-link all @-@ (and @-domain) mentions to https:, the reasoning being that identities on the web should be using https.Some questions: * Does/do Mastodon (or other ActivityPub servers) notify people when you @-@ mention them in a post? How? Who’s responsibility is that?* Will Bridgy Fed notify the servers (deliver to AP inboxes) of folks I merely @-@ mention (rather than explicit replies, reposts)? Should it?So many people are switching to using their personal domains to post (or at least a Mastodon account) that I no longer feel compelled to @-mention people’s Twitter handles in posts, which feels refreshing. Now the fun part is experimenting and figuring out what combination of @-domain, plain domain, or @-@ mentions looks good, makes sense to people, and sends notifications to people the way they want to receive them.This is day 11 of #100DaysOfIndieWeb #100Days.← Day 10: https://tantek.com/2023/010/t2/build-use-services→ 🔮^1 https://en.wikipedia.org/wiki/AT-AT^2 My https://github.com/tantek/cassis/blob/master/cassis.js auto_link() function supports @example.com auto-linking, yours should too.^3 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb
's status on Thursday, 12-Jan-2023 02:59:00 EST
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/ (@dangillmor@mastodon.social), https://simonwillison.net/ (@simon@simonwillison.net) Rather than using social media silo @-names (except when explicitly replying to a silo), I’m now experimenting with all three of these (1-3) instead, both to elevate people’s IndieWeb identities, and for Mastodon viewers, provide a convenient way to follow @-@ addresses. If someone’s homepage receives Webmentions, they will get notified when I @-mention them by domain. I recently implemented syntactic auto-linking of @-@ addresses like this: * @user@example.com --> https://example.com/@user with a special case for @-domain@-domain to just link to the domain, e.g.: * @tantek.com@tantek.com --> https://tantek.com/ I also made a policy decision to auto-link all @-@ (and @-domain) mentions to https:, the reasoning being that identities on the web should be using https. Some questions: * Does/do Mastodon (or other ActivityPub servers) notify people when you @-@ mention them in a post? How? Who’s responsibility is that? * Will Bridgy Fed notify the servers (deliver to AP inboxes) of folks I merely @-@ mention (rather than explicit replies, reposts)? Should it? So many people are switching to using their personal domains to post (or at least a Mastodon account) that I no longer feel compelled to @-mention people’s Twitter handles in posts, which feels refreshing. Now the fun part is experimenting and figuring out what combination of @-domain, plain domain, or @-@ mentions looks good, makes sense to people, and sends notifications to people the way they want to receive them. This is day 11 of #100DaysOfIndieWeb #100Days. ← Day 10: https://tantek.com/2023/010/t2/build-use-services → 🔮 ^1 https://en.wikipedia.org/wiki/AT-AT ^2 My https://github.com/tantek/cassis/blob/master/cassis.js auto_link() function supports @example.com auto-linking, yours should too. ^3 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb
: 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.com/ (@voxpelli@mastodon.social), https://simonwillison.net/ (@simon@simonwillison.net)Rather than using social media silo @-names (except when explicitly replying to a silo), I’m now experimenting with all three of these (1-3) instead, both to elevate people’s IndieWeb identities, and for Mastodon viewers, provide a convenient way to follow @-@ addresses.If someone’s homepage receives Webmentions, they will get notified when I @-mention them by domain.I also recently implemented syntactic auto-linking of @-@ addresses like this:* @user@example.com --> http://example.com/@userwith a special case for @-domain@-domain to just link to the domain, e.g.:* @tantek.com@tantek.com --> http://tantek.com/I am considering switching these (as well as a plain @-domain) to auto-link to https: instead, the reasoning being we should expect that identities on the web should be using https.Some questions: * Does/do Mastodon (or other ActivityPub servers) notify people when you @-@ mention them in a post? How? Who’s responsibility is that?* Will Bridgy Fed notify the servers (deliver to AP inboxes) of folks I merely @-@ mention (rather than explicit replies, reposts)? Should it?So many people are switching to using their personal domains to post (or at least a Mastodon account) that I no longer feel compelled to @-mention people’s Twitter handles in posts, which feels refreshing. Now the fun part is experimenting and figuring out what combination of @-domain, plain domain, or @-@ mentions looks good, makes sense to people, and sends notifications to people the way they want to receive them.This is day 11 of #100DaysOfIndieWeb #100Days.← Day 10: https://tantek.com/2023/010/t2/build-use-services→ 🔮^1 https://en.wikipedia.org/wiki/AT-AT^2 My https://github.com/tantek/cassis/blob/master/cassis.js auto_link() function supports @example.com auto-linking, yours should too.^3 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb
One of the fun things about #IndieWeb notes & replies is that we're still figuring things out! Like how should we @ someone? #socialMedia aliases (e.g. @Twitter) were obvious, with prior @-name usage on Flickr etc. Now, some have a domain, or an @-@ (pronounced at-at, yes, just like the abbreviation for Imperial All Terrain Armored Transport^1 walkers), or some have both. We can ask the questions of why do we @-someone? What are the use-cases? * In a reply to a public post, clearly express that you’re speaking to that person * In a reply to a reply, that you’re speaking to everyone upthread (AKA a https://indieweb.org/canoe) * When attributing something to someone (photo/post/cool thing by so-and-so), giving credit * For all the above, notifying someone accordingly * Distinguish a person (or something that can be followed) from “just” a site Some ideas: 1. Ideally, if/when everyone has their own domain (where they receive Webmention notifications, and a feed you can follow), we can @-name their domain, which your auto-linker^2 should hyperlink accordingly, e.g. * @aaronparecki.com @anomalily.net @Martymcgui.re @david.shanske.com @snarfed.org @ben.thatmustbe.me These all look close enough to social media aliases/names that they’re immediately recognizable as readable @-names, a good consideration when choosing a domain name.^3 2. As a fallback (e.g. for non-@-domain-auto-linking destinations) we can use someone’s plain domain (explicitly with https:), especially if their home page still has a stream or feed you can follow, or maybe if they don’t receive homepage Webmentions, e.g.: * https://adactio.com https://marcthiele.com https://mxb.dev/ 3. Some folks with personal sites have (for now) created separate Mastodon accounts (or an installed an instance on a subdomain), and for them, we can reference their @-@ parenthetically after their domain, like: * https://kevinmarks.com/ (@kevinmarks@xoxo.zone), https://tmichellemoore.com/ (@tmichellemoore@mastodon.social), https://voxpelli.com/ (@voxpelli@mastodon.social), https://simonwillison.net/ (@simon@simonwillison.net) Rather than using social media silo @-names (except when explicitly replying to a silo), I’m now experimenting with all three of these (1-3) instead, both to elevate people’s IndieWeb identities, and for Mastodon viewers, provide a convenient way to follow @-@ addresses. If someone’s homepage receives Webmentions, they will get notified when I @-mention them by domain. I also recently implemented syntactic auto-linking of @-@ addresses like this: * @user@example.com --> http://example.com/@user with a special case for @-domain@-domain to just link to the domain, e.g.: * @tantek.com@tantek.com --> http://tantek.com/ I am considering switching these (as well as a plain @-domain) to auto-link to https: instead, the reasoning being we should expect that identities on the web should be using https. Some questions: * Does/do Mastodon (or other ActivityPub servers) notify people when you @-@ mention them in a post? How? Who’s responsibility is that? * Will Bridgy Fed notify the servers (deliver to AP inboxes) of folks I merely @-@ mention (rather than explicit replies, reposts)? Should it? So many people are switching to using their personal domains to post (or at least a Mastodon account) that I no longer feel compelled to @-mention people’s Twitter handles in posts, which feels refreshing. Now the fun part is experimenting and figuring out what combination of @-domain, plain domain, or @-@ mentions looks good, makes sense to people, and sends notifications to people the way they want to receive them. This is day 11 of #100DaysOfIndieWeb #100Days. ← Day 10: https://tantek.com/2023/010/t2/build-use-services → 🔮 ^1 https://en.wikipedia.org/wiki/AT-AT ^2 My https://github.com/tantek/cassis/blob/master/cassis.js auto_link() function supports @example.com auto-linking, yours should too. ^3 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb
: 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 #IndieWeb support you want to implement yourself (and time to invest) vs build on the services, libraries, and other open source that the community has produced and is actively supporting.This is day 10 of #100DaysOfIndieWeb #100Days.← Day 9: https://tantek.com/2023/009/t2/edit-reply-comment-update→ 🔮^1 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb^2 https://tantek.com/2023/005/t3/indieweb-simpler-approach^3 https://tantek.com/2023/003/t1/indieweb-path-chosen-why^4 https://indieweb.org/building_blocks^5 https://tantek.com/2023/001/t1/own-your-notes^6 https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed^7 https://spec.indieweb.org/
's status on Wednesday, 11-Jan-2023 02:59:00 EST
Once you have a domain^1, and connect it to an #IndieWeb service like https://micro.blog, or a https://indieweb.org/CMS on https://indieweb.org/web_hosting, you can focus^2 on your writing. Or if you enjoy #webDevelopment and want to build (option three^3), use developer services to more rapidly add IndieWeb building blocks^4 to your site so you too can focus on creating & owning your content^5. Here are some of the most common and popular developer services: 1. Webmention sending: https://webmention.app/ by https://remysharp.com/ (@rem@front-end.social), or https://mention.tech/ by https://kevinmarks.com/ (@kevinmarks@xoxo.zone) 2. Webmention receiving: https://webmention.io/ (I use this) by https://aaronparecki.com/ or https://webmention.herokuapp.com/ by https://voxpelli.com/ (@voxpelli@mastodon.social) 3. POSSE & backfeed: https://brid.gy/ by Ryan of https://snarfed.org/ (@schnarfed) 4. ActivityPub federating: https://fed.brid.gy/ also by Ryan. More on Bridgy & Bridgy Fed^6. Using a developer service to support IndieWeb protocols saves you time. You can also contribute to the community by filing suggestions for improvements, or participating on their GitHub repositories. If you prefer that your site not depend on any external services, you can do that too. Most of the above services are also open source that you can install and fully manage yourself. For example: * Webmention installable services: https://indieweb.org/Webmention#Publisher_Services Another option is to use one of many open source libraries to more rapidly implement support for IndieWeb standards^7. The wiki pages for each standard list libraries in a variety of programming languages, e.g.: * https://indieweb.org/Webmention-developer#Libraries If you choose the path of installing or building something new with libraries or by directly implementing an IndieWeb standard, be sure to test your implementation with its test suite, e.g.: * https://webmention.rocks/ As a web developer, you can choose how much of your #IndieWeb support you want to implement yourself (and time to invest) vs build on the services, libraries, and other open source that the community has produced and is actively supporting. This is day 10 of #100DaysOfIndieWeb #100Days. ← Day 9: https://tantek.com/2023/009/t2/edit-reply-comment-update → 🔮 ^1 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb ^2 https://tantek.com/2023/005/t3/indieweb-simpler-approach ^3 https://tantek.com/2023/003/t1/indieweb-path-chosen-why ^4 https://indieweb.org/building_blocks ^5 https://tantek.com/2023/001/t1/own-your-notes ^6 https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed ^7 https://spec.indieweb.org/
: 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 with replies interlinked with protocols interlinked.This is day 9 of #100DaysOfIndieWeb #100Days.← Day 8: https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed→ 🔮^1 The ability to edit tweets has literally been the most requested feature on Twitter since perhaps its launch. Last year, paid Twitter “Blue” accounts finally got the ability to edit tweets, sort of: five times within 30 minutes of posting. Too little, too late.* https://techcrunch.com/2022/10/03/twitters-edit-button-is-rolling-out-to-blue-subscribers-in-canada-australia-and-new-zealand/* https://blog.hootsuite.com/can-you-edit-a-tweet/* https://www.pcmag.com/news/twitters-edit-button-is-coming-soon-for-paid-users* https://www.macrumors.com/2022/10/06/twitter-edit-tweet-option-united-states/* https://9to5mac.com/2022/10/06/twitter-rolling-out-edit-button/^2 Pingbacks were originally (and for many years) only implemented as one-off cross-blog interactions. One-time, uneditable. Pingbacks (and Trackbacks before them) were notoriously ugly when they showed up on blogs, listed & displayed as a separate thing (never tie presentation to the name of a protocol) with cryptically elided summaries: https://indieweb.org/pingback#Poor_display. It took over 10 years since being specified (2002) for the IndieWeb community to re-use pingbacks for actual comments across sites: https://tantek.com/2013/113/b1/first-federated-indieweb-comment-thread separating presentation & UI from the protocol. This separation of concerns approach evolved into the Webmention specification, separating the protocol from the display of comments, likes, reposts, and other social web https://indieweb.org/responses.
's status on Tuesday, 10-Jan-2023 01:44:00 EST
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. Posts interlinked with replies interlinked with protocols interlinked. This is day 9 of #100DaysOfIndieWeb #100Days. ← Day 8: https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed → 🔮 ^1 The ability to edit tweets has literally been the most requested feature on Twitter since perhaps its launch. Last year, paid Twitter “Blue” accounts finally got the ability to edit tweets, sort of: five times within 30 minutes of posting. Too little, too late. * https://techcrunch.com/2022/10/03/twitters-edit-button-is-rolling-out-to-blue-subscribers-in-canada-australia-and-new-zealand/ * https://blog.hootsuite.com/can-you-edit-a-tweet/ * https://www.pcmag.com/news/twitters-edit-button-is-coming-soon-for-paid-users * https://www.macrumors.com/2022/10/06/twitter-edit-tweet-option-united-states/ * https://9to5mac.com/2022/10/06/twitter-rolling-out-edit-button/ ^2 Pingbacks were originally (and for many years) only implemented as one-off cross-blog interactions. One-time, uneditable. Pingbacks (and Trackbacks before them) were notoriously ugly when they showed up on blogs, listed & displayed as a separate thing (never tie presentation to the name of a protocol) with cryptically elided summaries: https://indieweb.org/pingback#Poor_display. It took over 10 years since being specified (2002) for the IndieWeb community to re-use pingbacks for actual comments across sites: https://tantek.com/2013/113/b1/first-federated-indieweb-comment-thread separating presentation & UI from the protocol. This separation of concerns approach evolved into the Webmention specification, separating the protocol from the display of comments, likes, reposts, and other social web https://indieweb.org/responses.
: 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 encouraging personally relevant work and community contributions that makes the #IndieWeb community special. Yes there is a focus on greater independence with your personal website. However we can all do more by working together. We achieve more independence, more quickly, by collaborating in community.This is day 8 of #100DaysOfIndieWeb #100Days.← Day 7: https://tantek.com/2023/007/t2/more-100daysofindieweb-projects→ 🔮
's status on Sunday, 08-Jan-2023 23:43:00 EST
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 hybrid of encouraging personally relevant work and community contributions that makes the #IndieWeb community special. Yes there is a focus on greater independence with your personal website. However we can all do more by working together. We achieve more independence, more quickly, by collaborating in community. This is day 8 of #100DaysOfIndieWeb #100Days. ← Day 7: https://tantek.com/2023/007/t2/more-100daysofindieweb-projects → 🔮
: 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→ 🔮
's status on Sunday, 08-Jan-2023 02:59:00 EST
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 → 🔮
: 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
's status on Saturday, 07-Jan-2023 02:59:00 EST
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
: 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
's status on Tuesday, 03-Jan-2023 02:59:00 EST
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
: 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
's status on Monday, 02-Jan-2023 02:11:00 EST
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
: 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
's status on Wednesday, 03-Jan-2018 02:42:00 EST
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