{"generator":"GNU social 1.2.0-beta4","title":"Notices tagged with indieweb","totalItems":21,"items":[{"actor":{"id":"http:\/\/tantek.com\/","displayName":"Tantek","status_net":{"avatarLinks":[{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-profile.png","rel":"avatar","type":"image\/png","width":96,"height":96},{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-stream.png","rel":"avatar","type":"image\/png","width":48,"height":48},{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-mini.png","rel":"avatar","type":"image\/png","width":24,"height":24}],"profile_info":{"local_id":"207"}},"image":{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-profile.png","rel":"avatar","type":"image\/png","width":96,"height":96},"objectType":"person","url":"http:\/\/tantek.com\/","portablecontacts_net":{"displayName":"Tantek","addresses":{"formatted":"\nSan Francisco, CA\n"}}},"content":"@indieweb.org\/POSSE<\/a> in effect!
Well done @joanwestenberg@threads.net<\/a> \ud83d\ude4c\ud83c\udffb
#POSSE<\/span> threads
\u00a0
https:\/\/www.threads.net\/@joanwestenberg\/post\/C43gPbVSzPI:<\/a>
\u201cMe: You should publish on your own website first, then other platforms.
\u00a0Me: Publishes on my own website first, then other platforms.
\u00a0Galaxy brains: HOW IRONIC YOU PUBLISH ON OTHER PLATFORMS\u201d
\u00a0
#IndieWeb<\/span>","generator":{"id":"tag:status.net,2009:notice-source:ostatus","objectType":"application","status_net":{"source_code":"ostatus"}},"id":"https:\/\/tantek.com\/2024\/084\/t2\/posse-in-effect","object":{"id":"https:\/\/tantek.com\/2024\/084\/t2\/posse-in-effect","objectType":"note","content":"@indieweb.org\/POSSE<\/a> in effect!
Well done @joanwestenberg@threads.net<\/a> \ud83d\ude4c\ud83c\udffb
#POSSE<\/span> threads
\u00a0
https:\/\/www.threads.net\/@joanwestenberg\/post\/C43gPbVSzPI:<\/a>
\u201cMe: You should publish on your own website first, then other platforms.
\u00a0Me: Publishes on my own website first, then other platforms.
\u00a0Galaxy brains: HOW IRONIC YOU PUBLISH ON OTHER PLATFORMS\u201d
\u00a0
#IndieWeb<\/span>","url":"https:\/\/tantek.com\/2024\/084\/t2\/posse-in-effect","status_net":{"notice_id":116194},"tags":[{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"indieweb"}]},"to":[{"objectType":"http:\/\/activitystrea.ms\/schema\/1.0\/collection","id":"http:\/\/activityschema.org\/collection\/public"}],"status_net":{"conversation":"tag:status.blaise.ca,2024-03-27:objectType=thread:nonce=2f65d1b39503fe96","notice_info":{"local_id":"116194","source":"ostatus"}},"published":"2024-03-24T21:50:00+00:00","provider":{"objectType":"service","displayName":"stadeus","url":"http:\/\/status.blaise.ca\/"},"verb":"post","url":"https:\/\/tantek.com\/2024\/084\/t2\/posse-in-effect"},{"actor":{"id":"http:\/\/tantek.com\/","displayName":"Tantek","status_net":{"avatarLinks":[{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-profile.png","rel":"avatar","type":"image\/png","width":96,"height":96},{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-stream.png","rel":"avatar","type":"image\/png","width":48,"height":48},{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-mini.png","rel":"avatar","type":"image\/png","width":24,"height":24}],"profile_info":{"local_id":"207"}},"image":{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-profile.png","rel":"avatar","type":"image\/png","width":96,"height":96},"objectType":"person","url":"http:\/\/tantek.com\/","portablecontacts_net":{"displayName":"Tantek","addresses":{"formatted":"\nSan Francisco, CA\n"}}},"content":"While an HTML style element for inline CSS needs nothing but simple start and end tags (as of HTML5 and later)
<style>
p { margin:0 }
<\/style>
a more robust style element requires a precise series of overlapping code comments.
Here is the answer if you want a code snippet to copy & paste
<style><!--\/*--><![CDATA[*\/
p { margin:0 } \/* you may delete this sample style rule *\/
\/*]]><!--*\/--><\/style>
Here is why:
1. Not all HTML processors are CSS processors. While all modern browsers know how to parse CSS in style elements inside HTML, it is still quite reasonable for people to build HTML processors that do not, and many exist. There are plenty of ways that errant or deliberately misplaced markup inside a style element, like in a CSS comment, that such processors will not see, that can break them and cause unexpected and different results in different processors.
Thus it makes your HTML more parseable, by more processors, if you can hide the entirety of the style sheet inside the style elmenet from such processing. A CDATA section does exactly that:
<style><![CDATA[
p { margin:0 } \/* CDATA allows a <\/style> here to not close the element *\/
body > p { margin:1em } \/* CDATA allows an unescaped > child combinator *\/
]]><\/style>
2. However CSS syntax does not recognize a CDATA directive (even as of the latest published CSS Syntax Module Level 3\u00b9<\/a> or editor's draft\u00b2<\/a> as of this writing). CSS parsers may very well treat a CDATA directive as a syntax error that invalidates the subsequent style rule.
Thus we must hide the CDATA directive, its opening and closing markup, from CSS parsers. \u00a0CSS code comments \/* ... *\/ can do exactly that:
<style>\/* <![CDATA[*\/
p { margin:0 } \/* CDATA allows a <\/style> here to not close the element *\/
body > p { margin:1em } \/* CDATA allows an unescaped > child combinator *\/
\/*]]>*\/<\/style>
3. This is close but still exposes HTML processors that do not process CSS to a minimal bit of content, the CSS comment opener and closer that are outside the CDATA section:
\/* *\/
This recently showed up in a draft of the This Week in The #IndieWeb<\/span> newsletter\u00b3<\/a>, because portions of it are automatically constructed by parsing the HTML of MediaWiki pages for content, and one of those used a MediaWiki template that included a minimal style element to style the marked up content inserted by the template. A draft of the newsletter was showing raw CSS, extracted as text from the style element by the CSS-unaware parser extracting content. I was able to hide nearly all of it using CSS comments around the CDATA section opener and closer. Except for that little bit of CSS comment noise outside the CDATA section: \/* *\/
Fortunately there is one more tool in our toolbox that we can use. Simple HTML\/SGML comments <!-- --> are ignored at the start and end of style sheets\u2074<\/a> (noted there as CDO-token\u2075<\/a> and CDC-token\u2076<\/a>), and thus we can use those to hide the last two remaining CSS comment pieces that were leaking out, like this: <!-- \/* --> and <!-- *\/ -->. Note that the portion of the HTML comment directives that are inside CSS comments are ignored by CSS processors, which is why this works for both processors that parse CSS and those that do not.
This last addition produces our answer, with no fewer than three different comment mechanisms (CDATA, CSS, HTML\/SGML), overlapping to hide each other from different processors:
<style><!--\/*--><![CDATA[*\/
p { margin:0 } \/* CDATA allows a <\/style> here to not close the element *\/
body > p { margin:1em } \/* CDATA allows an unescaped > child combinator *\/
\/*]]><!--*\/--><\/style>
By replacing those informative style rules with a style rule to be deleted, we have recreated the code snippet to copy & paste from the top of the post:
<style><!--\/*--><![CDATA[*\/
p { margin:0 } \/* you may delete this sample style rule *\/
\/*]]><!--*\/--><\/style>
Q.E.D.
Afterword:
If you View Source on this original permalink or my home page you can see the more robust style element in a real world example, following the IndieWeb Use What You Make\u2077<\/a> principle.
#CSS<\/span> #style<\/span> #styleElement<\/span> #styleSheet<\/span> #HTML<\/span> #HTML5<\/span> #CSSsyntax<\/span> #codecomments<\/span>
Glossary:
CDATA
\u00a0 https:\/\/en.wikipedia.org\/wiki\/CDATA<\/a>
CSS \u2014 Cascading Style Sheets
\u00a0 https:\/\/en.wikipedia.org\/wiki\/CSS<\/a>
HTML \u2014 HyperText Markup Language
\u00a0 https:\/\/en.wikipedia.org\/wiki\/HTML<\/a>
HTML5
\u00a0 https:\/\/en.wikipedia.org\/wiki\/HTML5<\/a>
IndieWeb Principles
\u00a0 https:\/\/indieweb.org\/principles<\/a>
MediaWiki
\u00a0 https:\/\/en.wikipedia.org\/wiki\/MediaWiki<\/a>
original permalink
\u00a0 https:\/\/indieweb.org\/original_permalink<\/a>
Q.E.D.
\u00a0 https:\/\/en.wikipedia.org\/wiki\/Q.E.D<\/a>.
References:
\u00b9<\/a> https:\/\/www.w3.org\/TR\/css-syntax-3\/<\/a>
\u00b2<\/a> https:\/\/drafts.csswg.org\/css-syntax\/<\/a>
\u00b3<\/a> https:\/\/indieweb.org\/this-week-in-the-indieweb<\/a>
\u2074<\/a> https:\/\/www.w3.org\/TR\/css-syntax-3\/#stylesheet-diagram<\/a>
\u2075<\/a> https:\/\/www.w3.org\/TR\/css-syntax-3\/#CDO-token-diagram<\/a>
\u2076<\/a> https:\/\/www.w3.org\/TR\/css-syntax-3\/#CDC-token-diagram<\/a>
\u2077<\/a> https:\/\/indieweb.org\/use_what_you_make<\/a>","generator":{"id":"tag:status.net,2009:notice-source:ostatus","objectType":"application","status_net":{"source_code":"ostatus"}},"id":"https:\/\/tantek.com\/2024\/075\/t1\/css-more-robust-style-element","object":{"id":"https:\/\/tantek.com\/2024\/075\/t1\/css-more-robust-style-element","objectType":"note","content":"While an HTML style element for inline CSS needs nothing but simple start and end tags (as of HTML5 and later)
<style>
p { margin:0 }
<\/style>
a more robust style element requires a precise series of overlapping code comments.
Here is the answer if you want a code snippet to copy & paste
<style><!--\/*--><![CDATA[*\/
p { margin:0 } \/* you may delete this sample style rule *\/
\/*]]><!--*\/--><\/style>
Here is why:
1. Not all HTML processors are CSS processors. While all modern browsers know how to parse CSS in style elements inside HTML, it is still quite reasonable for people to build HTML processors that do not, and many exist. There are plenty of ways that errant or deliberately misplaced markup inside a style element, like in a CSS comment, that such processors will not see, that can break them and cause unexpected and different results in different processors.
Thus it makes your HTML more parseable, by more processors, if you can hide the entirety of the style sheet inside the style elmenet from such processing. A CDATA section does exactly that:
<style><![CDATA[
p { margin:0 } \/* CDATA allows a <\/style> here to not close the element *\/
body > p { margin:1em } \/* CDATA allows an unescaped > child combinator *\/
]]><\/style>
2. However CSS syntax does not recognize a CDATA directive (even as of the latest published CSS Syntax Module Level 3\u00b9<\/a> or editor's draft\u00b2<\/a> as of this writing). CSS parsers may very well treat a CDATA directive as a syntax error that invalidates the subsequent style rule.
Thus we must hide the CDATA directive, its opening and closing markup, from CSS parsers. \u00a0CSS code comments \/* ... *\/ can do exactly that:
<style>\/* <![CDATA[*\/
p { margin:0 } \/* CDATA allows a <\/style> here to not close the element *\/
body > p { margin:1em } \/* CDATA allows an unescaped > child combinator *\/
\/*]]>*\/<\/style>
3. This is close but still exposes HTML processors that do not process CSS to a minimal bit of content, the CSS comment opener and closer that are outside the CDATA section:
\/* *\/
This recently showed up in a draft of the This Week in The #IndieWeb<\/span> newsletter\u00b3<\/a>, because portions of it are automatically constructed by parsing the HTML of MediaWiki pages for content, and one of those used a MediaWiki template that included a minimal style element to style the marked up content inserted by the template. A draft of the newsletter was showing raw CSS, extracted as text from the style element by the CSS-unaware parser extracting content. I was able to hide nearly all of it using CSS comments around the CDATA section opener and closer. Except for that little bit of CSS comment noise outside the CDATA section: \/* *\/
Fortunately there is one more tool in our toolbox that we can use. Simple HTML\/SGML comments <!-- --> are ignored at the start and end of style sheets\u2074<\/a> (noted there as CDO-token\u2075<\/a> and CDC-token\u2076<\/a>), and thus we can use those to hide the last two remaining CSS comment pieces that were leaking out, like this: <!-- \/* --> and <!-- *\/ -->. Note that the portion of the HTML comment directives that are inside CSS comments are ignored by CSS processors, which is why this works for both processors that parse CSS and those that do not.
This last addition produces our answer, with no fewer than three different comment mechanisms (CDATA, CSS, HTML\/SGML), overlapping to hide each other from different processors:
<style><!--\/*--><![CDATA[*\/
p { margin:0 } \/* CDATA allows a <\/style> here to not close the element *\/
body > p { margin:1em } \/* CDATA allows an unescaped > child combinator *\/
\/*]]><!--*\/--><\/style>
By replacing those informative style rules with a style rule to be deleted, we have recreated the code snippet to copy & paste from the top of the post:
<style><!--\/*--><![CDATA[*\/
p { margin:0 } \/* you may delete this sample style rule *\/
\/*]]><!--*\/--><\/style>
Q.E.D.
Afterword:
If you View Source on this original permalink or my home page you can see the more robust style element in a real world example, following the IndieWeb Use What You Make\u2077<\/a> principle.
#CSS<\/span> #style<\/span> #styleElement<\/span> #styleSheet<\/span> #HTML<\/span> #HTML5<\/span> #CSSsyntax<\/span> #codecomments<\/span>
Glossary:
CDATA
\u00a0 https:\/\/en.wikipedia.org\/wiki\/CDATA<\/a>
CSS \u2014 Cascading Style Sheets
\u00a0 https:\/\/en.wikipedia.org\/wiki\/CSS<\/a>
HTML \u2014 HyperText Markup Language
\u00a0 https:\/\/en.wikipedia.org\/wiki\/HTML<\/a>
HTML5
\u00a0 https:\/\/en.wikipedia.org\/wiki\/HTML5<\/a>
IndieWeb Principles
\u00a0 https:\/\/indieweb.org\/principles<\/a>
MediaWiki
\u00a0 https:\/\/en.wikipedia.org\/wiki\/MediaWiki<\/a>
original permalink
\u00a0 https:\/\/indieweb.org\/original_permalink<\/a>
Q.E.D.
\u00a0 https:\/\/en.wikipedia.org\/wiki\/Q.E.D<\/a>.
References:
\u00b9<\/a> https:\/\/www.w3.org\/TR\/css-syntax-3\/<\/a>
\u00b2<\/a> https:\/\/drafts.csswg.org\/css-syntax\/<\/a>
\u00b3<\/a> https:\/\/indieweb.org\/this-week-in-the-indieweb<\/a>
\u2074<\/a> https:\/\/www.w3.org\/TR\/css-syntax-3\/#stylesheet-diagram<\/a>
\u2075<\/a> https:\/\/www.w3.org\/TR\/css-syntax-3\/#CDO-token-diagram<\/a>
\u2076<\/a> https:\/\/www.w3.org\/TR\/css-syntax-3\/#CDC-token-diagram<\/a>
\u2077<\/a> https:\/\/indieweb.org\/use_what_you_make<\/a>","url":"https:\/\/tantek.com\/2024\/075\/t1\/css-more-robust-style-element","status_net":{"notice_id":116191},"tags":[{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"codecommentsglossary"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"csssyntax"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"html"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"html5"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"indieweb"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"style"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"styleelement"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"stylesheet"}]},"to":[{"objectType":"http:\/\/activitystrea.ms\/schema\/1.0\/collection","id":"http:\/\/activityschema.org\/collection\/public"}],"status_net":{"conversation":"tag:status.blaise.ca,2024-03-16:objectType=thread:nonce=18c27b737961196b","notice_info":{"local_id":"116191","source":"ostatus"}},"published":"2024-03-16T04:35:00+00:00","provider":{"objectType":"service","displayName":"stadeus","url":"http:\/\/status.blaise.ca\/"},"verb":"post","url":"https:\/\/tantek.com\/2024\/075\/t1\/css-more-robust-style-element"},{"actor":{"id":"http:\/\/tantek.com\/","displayName":"Tantek","status_net":{"avatarLinks":[{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-profile.png","rel":"avatar","type":"image\/png","width":96,"height":96},{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-stream.png","rel":"avatar","type":"image\/png","width":48,"height":48},{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-mini.png","rel":"avatar","type":"image\/png","width":24,"height":24}],"profile_info":{"local_id":"207"}},"image":{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-profile.png","rel":"avatar","type":"image\/png","width":96,"height":96},"objectType":"person","url":"http:\/\/tantek.com\/","portablecontacts_net":{"displayName":"Tantek","addresses":{"formatted":"\nSan Francisco, CA\n"}}},"content":"What I created while remotely participating at #IndieWebCamp<\/span> Brighton 2024: wiki-gardened day 1\u2019s BarCamp sessions notes pages, and documented my @-mention @-@-mention autolinking coding improvements I built the Sunday before.
Day 2 of IndieWebCamps is Create Day, where everyone is encouraged to create, make, or build something for their personal website, or the IndieWeb community, or both.
At the start of day 2, everyone is encourage to pick things to make\u00b9<\/a>. What to make at an IndieWebCamp\u00b2<\/a> can be anything from setting up your personal website, to writing a blog post, redesigning your styling, building new features, helping other participants, or contributing to shared IndieWeb community resources, whether code or content.
Everyone is encouraged to at least pick something they consider easy, that they can do in less than an hour, then a more bold goal, and then perhaps a stretch goal, something challenging that may require collaboration, asking for help, or breaking into smaller steps.
For my \"easy\" task, I built on what another remote participant, @gregorlove.com<\/a> completed the night before. gRegor had archived all the IndieWebCamp Brighton Sessions Etherpads onto the wiki, linked from the Schedule page\u00b3<\/a>. gRegor had noted that he didn\u2019t have time to clean-up the pages, e.g. convert and fix Markdown links.
I went through the 13 Session Notes archives and did the following:
* converted Markdown links to MediaWiki links
* converted indieweb.org<\/a> (and some services) links to local wiki page links
* fixed (some) typos
With some help from @alexsirac.com<\/a> (@alexture@todo.eu<\/a>), I figured out how to create a MediaWiki Contributions summary link of my edits:
* https:\/\/indieweb.org\/wiki\/index.php?title=Special:Contributions&target=Tantek.com&namespace=all&start=2024-03-10&end=2024-03-10&offset=20240310143900&limit=25<\/a>
I point this out to provide an example of an IndieWeb Create Day project that is:
* incremental on top of someone else\u2019s work
* community contribution rather a personal-focused project
* editing and wiki-gardening as valid contributions, not just creating new content
I point this out to illustrate some of the IndieWeb community's recognitions & values in contrast to typical corporate cultures and incentive systems which often only reward:
* new innovations (not incremental improvements)
* solo (or maybe jointly in a small team) inventions, designs, specs, or implementations
* something large, a new service or a big feature, not numerous small edits & fixes
In this regard, the IndieWeb community shares more in common with Wikipedia and similar collaborative communities (despite the #Indie<\/span> in #IndieWeb<\/span>), than any corporation.
For my \"more bold\" goal, I wrote a medium-sized post about the auto-linking improvements I made the Sunday before the IndieWebCamp to my personal website with examples and brief descriptions of the coding changes & improvements.
* https:\/\/tantek.com\/2024\/070\/t1\/updated-auto-linking-mention-use-cases<\/a>
My stretch goal was to write up a more complete auto-linking specification, based on the research I have done into @-mention @-@-mention user practices (on #Mastodon<\/span>, other #ActivityPub<\/span> or #fediverse<\/span> implementations, and even across #socialMedia<\/span> silos), as well as how implementations link URLs, domains, and paths.
That stretch goal remains a goal, however I did collect a handful of prior posts on @-mentions which I plan to source for specifying auto-linking and @-mentioning:
* https:\/\/tantek.com\/2023\/011\/t1\/indieweb-evolving-at-mention<\/a>
* https:\/\/tantek.com\/2023\/014\/t4\/domain-first-federated-atmention<\/a>
* https:\/\/tantek.com\/2023\/018\/t1\/elevate-indieweb-above-silo<\/a>
* https:\/\/tantek.com\/2023\/019\/t5\/reply-domain-above-address-and-silo<\/a>
* https:\/\/tantek.com\/2023\/109\/t2\/years-ago-first-federated-indieweb-thread<\/a>
#autoLink<\/span> #atDomain<\/span> #atPath<\/span> #atMention<\/span> #atMentions<\/span> #atat<\/span> #atAtMention<\/span>
I was one of a few remote participants in addition to ~18 in-person participants, the overwhelming majority of overall attendees, who demonstrated something at the end of IndieWebCamp Brighton 2024 day 2. See what everyone else made & demonstrated on Create Day:
* https:\/\/indieweb.org\/2024\/Brighton\/Demos<\/a>
This is post 13 of #100PostsOfIndieWeb<\/span>. #100Posts<\/span>
\u2190 https:\/\/tantek.com\/2024\/070\/t1\/updated-auto-linking-mention-use-cases<\/a>
\u2192 \ud83d\udd2e
Glossary:
Create Day
\u00a0 https:\/\/indieweb.org\/Create_Day<\/a>
IndieWebCamp Brighton 2024
\u00a0 https:\/\/indieweb.org\/2024\/Brighton<\/a>
References:
\u00b9<\/a> https:\/\/indieweb.org\/IndieWebCamps\/Attending#Day_Two<\/a>
\u00b2<\/a> https:\/\/indieweb.org\/what_to_make_at_IndieWebCamp<\/a>
\u00b3<\/a> https:\/\/indieweb.org\/2024\/Brighton\/Schedule#Saturday<\/a>","generator":{"id":"tag:status.net,2009:notice-source:ostatus","objectType":"application","status_net":{"source_code":"ostatus"}},"id":"https:\/\/tantek.com\/2024\/072\/t1\/created-at-indiewebcamp-brighton","object":{"id":"https:\/\/tantek.com\/2024\/072\/t1\/created-at-indiewebcamp-brighton","objectType":"note","content":"What I created while remotely participating at #IndieWebCamp<\/span> Brighton 2024: wiki-gardened day 1\u2019s BarCamp sessions notes pages, and documented my @-mention @-@-mention autolinking coding improvements I built the Sunday before.
Day 2 of IndieWebCamps is Create Day, where everyone is encouraged to create, make, or build something for their personal website, or the IndieWeb community, or both.
At the start of day 2, everyone is encourage to pick things to make\u00b9<\/a>. What to make at an IndieWebCamp\u00b2<\/a> can be anything from setting up your personal website, to writing a blog post, redesigning your styling, building new features, helping other participants, or contributing to shared IndieWeb community resources, whether code or content.
Everyone is encouraged to at least pick something they consider easy, that they can do in less than an hour, then a more bold goal, and then perhaps a stretch goal, something challenging that may require collaboration, asking for help, or breaking into smaller steps.
For my \"easy\" task, I built on what another remote participant, @gregorlove.com<\/a> completed the night before. gRegor had archived all the IndieWebCamp Brighton Sessions Etherpads onto the wiki, linked from the Schedule page\u00b3<\/a>. gRegor had noted that he didn\u2019t have time to clean-up the pages, e.g. convert and fix Markdown links.
I went through the 13 Session Notes archives and did the following:
* converted Markdown links to MediaWiki links
* converted indieweb.org<\/a> (and some services) links to local wiki page links
* fixed (some) typos
With some help from @alexsirac.com<\/a> (@alexture@todo.eu<\/a>), I figured out how to create a MediaWiki Contributions summary link of my edits:
* https:\/\/indieweb.org\/wiki\/index.php?title=Special:Contributions&target=Tantek.com&namespace=all&start=2024-03-10&end=2024-03-10&offset=20240310143900&limit=25<\/a>
I point this out to provide an example of an IndieWeb Create Day project that is:
* incremental on top of someone else\u2019s work
* community contribution rather a personal-focused project
* editing and wiki-gardening as valid contributions, not just creating new content
I point this out to illustrate some of the IndieWeb community's recognitions & values in contrast to typical corporate cultures and incentive systems which often only reward:
* new innovations (not incremental improvements)
* solo (or maybe jointly in a small team) inventions, designs, specs, or implementations
* something large, a new service or a big feature, not numerous small edits & fixes
In this regard, the IndieWeb community shares more in common with Wikipedia and similar collaborative communities (despite the #Indie<\/span> in #IndieWeb<\/span>), than any corporation.
For my \"more bold\" goal, I wrote a medium-sized post about the auto-linking improvements I made the Sunday before the IndieWebCamp to my personal website with examples and brief descriptions of the coding changes & improvements.
* https:\/\/tantek.com\/2024\/070\/t1\/updated-auto-linking-mention-use-cases<\/a>
My stretch goal was to write up a more complete auto-linking specification, based on the research I have done into @-mention @-@-mention user practices (on #Mastodon<\/span>, other #ActivityPub<\/span> or #fediverse<\/span> implementations, and even across #socialMedia<\/span> silos), as well as how implementations link URLs, domains, and paths.
That stretch goal remains a goal, however I did collect a handful of prior posts on @-mentions which I plan to source for specifying auto-linking and @-mentioning:
* https:\/\/tantek.com\/2023\/011\/t1\/indieweb-evolving-at-mention<\/a>
* https:\/\/tantek.com\/2023\/014\/t4\/domain-first-federated-atmention<\/a>
* https:\/\/tantek.com\/2023\/018\/t1\/elevate-indieweb-above-silo<\/a>
* https:\/\/tantek.com\/2023\/019\/t5\/reply-domain-above-address-and-silo<\/a>
* https:\/\/tantek.com\/2023\/109\/t2\/years-ago-first-federated-indieweb-thread<\/a>
#autoLink<\/span> #atDomain<\/span> #atPath<\/span> #atMention<\/span> #atMentions<\/span> #atat<\/span> #atAtMention<\/span>
I was one of a few remote participants in addition to ~18 in-person participants, the overwhelming majority of overall attendees, who demonstrated something at the end of IndieWebCamp Brighton 2024 day 2. See what everyone else made & demonstrated on Create Day:
* https:\/\/indieweb.org\/2024\/Brighton\/Demos<\/a>
This is post 13 of #100PostsOfIndieWeb<\/span>. #100Posts<\/span>
\u2190 https:\/\/tantek.com\/2024\/070\/t1\/updated-auto-linking-mention-use-cases<\/a>
\u2192 \ud83d\udd2e
Glossary:
Create Day
\u00a0 https:\/\/indieweb.org\/Create_Day<\/a>
IndieWebCamp Brighton 2024
\u00a0 https:\/\/indieweb.org\/2024\/Brighton<\/a>
References:
\u00b9<\/a> https:\/\/indieweb.org\/IndieWebCamps\/Attending#Day_Two<\/a>
\u00b2<\/a> https:\/\/indieweb.org\/what_to_make_at_IndieWebCamp<\/a>
\u00b3<\/a> https:\/\/indieweb.org\/2024\/Brighton\/Schedule#Saturday<\/a>","url":"https:\/\/tantek.com\/2024\/072\/t1\/created-at-indiewebcamp-brighton","status_net":{"notice_id":116190},"tags":[{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"100posts"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"100postsofindieweb"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"activitypub"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"atat"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"atatmentioni"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"atdomain"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"atmention"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"atmentions"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"atpath"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"fediverse"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"indie"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"indieweb"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"indiewebcamp"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"mastodon"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"socialmedia"}]},"to":[{"objectType":"http:\/\/activitystrea.ms\/schema\/1.0\/collection","id":"http:\/\/activityschema.org\/collection\/public"}],"status_net":{"conversation":"tag:status.blaise.ca,2024-03-13:objectType=thread:nonce=5ccd8f9b3b4cd92f","notice_info":{"local_id":"116190","source":"ostatus"}},"published":"2024-03-13T02:19:00+00:00","provider":{"objectType":"service","displayName":"stadeus","url":"http:\/\/status.blaise.ca\/"},"verb":"post","url":"https:\/\/tantek.com\/2024\/072\/t1\/created-at-indiewebcamp-brighton"},{"actor":{"id":"http:\/\/tantek.com\/","displayName":"Tantek","status_net":{"avatarLinks":[{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-profile.png","rel":"avatar","type":"image\/png","width":96,"height":96},{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-stream.png","rel":"avatar","type":"image\/png","width":48,"height":48},{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-mini.png","rel":"avatar","type":"image\/png","width":24,"height":24}],"profile_info":{"local_id":"207"}},"image":{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-profile.png","rel":"avatar","type":"image\/png","width":96,"height":96},"objectType":"person","url":"http:\/\/tantek.com\/","portablecontacts_net":{"displayName":"Tantek","addresses":{"formatted":"\nSan Francisco, CA\n"}}},"content":"New this week: the #IndieWeb<\/span> community deployed a major modern update to the design, usability, and cross-device support of the https:\/\/indieweb.org\/<\/a> home page and wiki in general! In brief:
* Updated MediaWiki install, updated themes, better mobile device support
* New default theme: Vector (2022), the same as English Wikipedia
* Lots of CSS fixes for content, sidebars, etc.
* Home page content simplification and more pleasing design update
Lots more details on the 2024 homepage and design update project page:
* https:\/\/indieweb.org\/2024\/homepage<\/a>
This was a community effort, with many people pitching in with major & minor contributions, spending weeks, days, hours, or a few minutes here and there helping out. \u00a0From server work, to PHP coding, to HTML+CSS (re)coding, to testing variants of MediaWiki themes, browsers, and devices.
Huge thanks in particular to @PaulRobertLloyd.com<\/a> for both driving this design update (e.g. said project page) and doing the heavy lifting of debugging, patching, and testing the latest MediaWiki Vector theme, documenting before & after screenshots, and @AaronParecki.com<\/a> for all the server-side software updates, PHP\/IndieAuth wrangling, and critical devops too.
Go try the new https:\/\/indieweb.org\/<\/a> on any browser, on any device, and share your experience!
#IndieNews<\/span>
This is post 11 of #100PostsOfIndieWeb<\/span>. #100Posts<\/span>
\u2190 https:\/\/tantek.com\/2024\/046\/t1\/the-ephemeral-web<\/a>
\u2192 \ud83d\udd2e","generator":{"id":"tag:status.net,2009:notice-source:ostatus","objectType":"application","status_net":{"source_code":"ostatus"}},"id":"https:\/\/tantek.com\/2024\/047\/t1\/indieweb-major-update-design","object":{"id":"https:\/\/tantek.com\/2024\/047\/t1\/indieweb-major-update-design","objectType":"note","content":"New this week: the #IndieWeb<\/span> community deployed a major modern update to the design, usability, and cross-device support of the https:\/\/indieweb.org\/<\/a> home page and wiki in general! In brief:
* Updated MediaWiki install, updated themes, better mobile device support
* New default theme: Vector (2022), the same as English Wikipedia
* Lots of CSS fixes for content, sidebars, etc.
* Home page content simplification and more pleasing design update
Lots more details on the 2024 homepage and design update project page:
* https:\/\/indieweb.org\/2024\/homepage<\/a>
This was a community effort, with many people pitching in with major & minor contributions, spending weeks, days, hours, or a few minutes here and there helping out. \u00a0From server work, to PHP coding, to HTML+CSS (re)coding, to testing variants of MediaWiki themes, browsers, and devices.
Huge thanks in particular to @PaulRobertLloyd.com<\/a> for both driving this design update (e.g. said project page) and doing the heavy lifting of debugging, patching, and testing the latest MediaWiki Vector theme, documenting before & after screenshots, and @AaronParecki.com<\/a> for all the server-side software updates, PHP\/IndieAuth wrangling, and critical devops too.
Go try the new https:\/\/indieweb.org\/<\/a> on any browser, on any device, and share your experience!
#IndieNews<\/span>
This is post 11 of #100PostsOfIndieWeb<\/span>. #100Posts<\/span>
\u2190 https:\/\/tantek.com\/2024\/046\/t1\/the-ephemeral-web<\/a>
\u2192 \ud83d\udd2e","url":"https:\/\/tantek.com\/2024\/047\/t1\/indieweb-major-update-design","status_net":{"notice_id":116172},"tags":[{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"100posts"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"100postsofindieweb"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"indieweb"}]},"to":[{"objectType":"http:\/\/activitystrea.ms\/schema\/1.0\/collection","id":"http:\/\/activityschema.org\/collection\/public"}],"status_net":{"conversation":"tag:status.blaise.ca,2024-02-16:objectType=thread:nonce=6a2702a9411c81ec","notice_info":{"local_id":"116172","source":"ostatus"}},"published":"2024-02-16T22:25:00+00:00","provider":{"objectType":"service","displayName":"stadeus","url":"http:\/\/status.blaise.ca\/"},"verb":"post","url":"https:\/\/tantek.com\/2024\/047\/t1\/indieweb-major-update-design"},{"actor":{"id":"http:\/\/tantek.com\/","displayName":"Tantek","status_net":{"avatarLinks":[{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-profile.png","rel":"avatar","type":"image\/png","width":96,"height":96},{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-stream.png","rel":"avatar","type":"image\/png","width":48,"height":48},{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-mini.png","rel":"avatar","type":"image\/png","width":24,"height":24}],"profile_info":{"local_id":"207"}},"image":{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-profile.png","rel":"avatar","type":"image\/png","width":96,"height":96},"objectType":"person","url":"http:\/\/tantek.com\/","portablecontacts_net":{"displayName":"Tantek","addresses":{"formatted":"\nSan Francisco, CA\n"}}},"content":"A couple of days ago in an informal discussion in the #indieweb<\/span> chat channel about how different people view #Mastodon<\/span>, the #fediverse<\/span>, or #Bluesky<\/span>, and services like #Bridgy<\/span> & #BridgyFed<\/span> quite differently, I noted\u00b9<\/a> that one big unspoken difference was how things on the web last over time, from the traditional persistent web, vs the newer and growing ephemeral web.
There is the publicly viewable #OpenWeb<\/span> that many of us take for granted, meaning the web that is persistent, that lasts over time, and thanks to being #curlable<\/span>, that the Internet Archive archives, and that a plurality of search engines see and index (robots.txt allowing). The HTML + CSS + media files declarative web.
Then there are the https APIs that return JSON \"web\", the thing that I\u2019ve started calling the ephemeral web, the set of things that are here today, briefly, gone tomorrow. I\u2019ve previously used the more provocative phrase js;dr (JavaScript required, Didn\u2019t Read) for this #ephemeralWeb<\/span>, yet like many things, it turns out there is a spectrum from ephemeral to persistent.
One popular example on that spectrum that\u2019s closer to the ephemeral edge is anything on a Mastodon server running v4 (or later as of this writing) of the software. (I\u2019m not bothering to discuss the examples of walled garden social media silos because I expect we will continue to see their demise\u00b2<\/a> over time.)
For example, the Internet Archive version of the shutdown notice for the queer(.)af Mastodon server, is visibly blank:
https:\/\/web.archive.org\/web\/20240112165635\/https:\/\/queer.af\/@postmaster\/111733741786950083<\/a>
Note: only a single Internet Archive snapshot was made of that post.
However if you View Source, you can find the entirety of that #queerAF<\/span> post duplicated across a couple of invisible-to-the-user meta tags inside the raw HTML:
\u00a0\"**TL;DR: Queer[.]AF will close on 2024-04-12** \u2026\" \u00a0
[.] added to avoid linking to a dead domain.
Note: such meta tags in js;dr pages were part of the motivation to specify metaformats.
To be clear, the shutdown of queer(.)af was a tragedy and not the fault of the creators, administrators etc., but rather one of the unfortunate outcomes of using some ccTLDs, country-code top level domains, that risk sudden draconian rules, domain renewal price hikes, or other unpredictable risks due to the politics, turmoil, regime changes etc. of the countries that administrate such domains.
Nearly the entirety of every Mastodon server, every post, every reply, is ephemeral.
When a Mastodon server shuts down, all its posts disappear from the surface of the web, forever.
Perhaps internet archeologists of the future will discover such dead permalinks, check the Internet Archive, find apparent desolation, and a few of them will be curious enough to use View Source tools to unearth parts of those posts, unintentionally preserved inside ceremonial meta tags next to dead scripts disconnected from databases and an empty shell of a body. \u00a0
All reply-contexts of and replies to such posts and conversations lost, like threads unraveled from an ancient tapestry, scattered to the winds.
If you\u2019re reading this post in your Mastodon reader, on either the website of your Mastodon account, or in a proprietary native client application, you should be able to click through, perhaps on the date-time stamp displayed to you, to view the original post on my website, where it is served in relatively simple declarative HTML + CSS with a bit of progressive enhancement script.
Because I serve declarative content, my posts are both findable across a variety of services & search engines, and archived by the Internet Archive. Even if my site goes down, snapshots or archives will be viewable elsewhere, with nearly the same fidelity of viewing them directly on my site.
This design for longevity is both deliberate, and the default for which the web was designed. It\u2019s also one of the explicit principles in the IndieWeb community.
If that resonates with you, if creating, writing, & building things that last matter to you, choose web tools, services, and software that support the persistence & longevity of your work.
#persistentWeb<\/span> #longWeb<\/span> #LongNow<\/span>
This is post 10 of #100PostsOfIndieWeb<\/span>. #100Posts<\/span>
\u2190 https:\/\/tantek.com\/2024\/035\/t2\/indiewebcamp-brighton-tickets-available<\/a>
\u2192 \ud83d\udd2e
Post glossary:
API (Application Programming Interface)
\u00a0 https:\/\/indieweb.org\/API<\/a>
Bluesky
\u00a0 https:\/\/indieweb.org\/Bluesky<\/a>
Bridgy
\u00a0 https:\/\/brid.gy\/<\/a>
Bridgy Fed
\u00a0 https:\/\/fed.brid.gy\/<\/a>
ccTLD (country-code top level domain)
\u00a0 https:\/\/indieweb.org\/ccTLD<\/a>
curlable
\u00a0 https:\/\/indieweb.org\/curlable<\/a>
declarative web
\u00a0 https:\/\/www.mozilla.org\/en-US\/about\/webvision\/full\/#thedeclarativeweb<\/a>
Internet Archive
\u00a0 https:\/\/archive.org\/<\/a>
js;dr (JavaScript required; Didn\u2019t Read)
\u00a0 https:\/\/tantek.com\/2015\/069\/t1\/js-dr-javascript-required-dead<\/a>
JSON
\u00a0 https:\/\/indieweb.org\/JSON<\/a>
longevity
\u00a0 https:\/\/indieweb.org\/longevity<\/a>
Mastodon
\u00a0 https:\/\/indieweb.org\/Mastodon<\/a>
metaformats
\u00a0 https:\/\/microformats.org\/wiki\/metaformats<\/a>
permalink
\u00a0 https:\/\/indieweb.org\/permalink<\/a>
principles in the IndieWeb community
\u00a0 https:\/\/indieweb.org\/principles<\/a>
progressive enhancement
\u00a0 https:\/\/indieweb.org\/progressive_enhancement<\/a>
reply
\u00a0 https:\/\/indieweb.org\/reply<\/a>
reply-context
\u00a0 https:\/\/indieweb.org\/reply-context<\/a>
robots.txt
\u00a0 https:\/\/indieweb.org\/robots_txt<\/a>
social media
\u00a0 https:\/\/indieweb.org\/social_media<\/a>
silo
\u00a0 https:\/\/indieweb.org\/silo<\/a>
View Source
\u00a0 https:\/\/firefox-source-docs.mozilla.org\/devtools-user\/view_source\/index.html<\/a>
\u00b9<\/a> https:\/\/chat.indieweb.org\/2024-02-13#t1707845454695700<\/a>
\u00b2<\/a> https:\/\/indieweb.org\/site-deaths<\/a>","generator":{"id":"tag:status.net,2009:notice-source:ostatus","objectType":"application","status_net":{"source_code":"ostatus"}},"id":"https:\/\/tantek.com\/2024\/046\/t1\/the-ephemeral-web","object":{"id":"https:\/\/tantek.com\/2024\/046\/t1\/the-ephemeral-web","objectType":"note","content":"A couple of days ago in an informal discussion in the #indieweb<\/span> chat channel about how different people view #Mastodon<\/span>, the #fediverse<\/span>, or #Bluesky<\/span>, and services like #Bridgy<\/span> & #BridgyFed<\/span> quite differently, I noted\u00b9<\/a> that one big unspoken difference was how things on the web last over time, from the traditional persistent web, vs the newer and growing ephemeral web.
There is the publicly viewable #OpenWeb<\/span> that many of us take for granted, meaning the web that is persistent, that lasts over time, and thanks to being #curlable<\/span>, that the Internet Archive archives, and that a plurality of search engines see and index (robots.txt allowing). The HTML + CSS + media files declarative web.
Then there are the https APIs that return JSON \"web\", the thing that I\u2019ve started calling the ephemeral web, the set of things that are here today, briefly, gone tomorrow. I\u2019ve previously used the more provocative phrase js;dr (JavaScript required, Didn\u2019t Read) for this #ephemeralWeb<\/span>, yet like many things, it turns out there is a spectrum from ephemeral to persistent.
One popular example on that spectrum that\u2019s closer to the ephemeral edge is anything on a Mastodon server running v4 (or later as of this writing) of the software. (I\u2019m not bothering to discuss the examples of walled garden social media silos because I expect we will continue to see their demise\u00b2<\/a> over time.)
For example, the Internet Archive version of the shutdown notice for the queer(.)af Mastodon server, is visibly blank:
https:\/\/web.archive.org\/web\/20240112165635\/https:\/\/queer.af\/@postmaster\/111733741786950083<\/a>
Note: only a single Internet Archive snapshot was made of that post.
However if you View Source, you can find the entirety of that #queerAF<\/span> post duplicated across a couple of invisible-to-the-user meta tags inside the raw HTML:
\u00a0\"**TL;DR: Queer[.]AF will close on 2024-04-12** \u2026\" \u00a0
[.] added to avoid linking to a dead domain.
Note: such meta tags in js;dr pages were part of the motivation to specify metaformats.
To be clear, the shutdown of queer(.)af was a tragedy and not the fault of the creators, administrators etc., but rather one of the unfortunate outcomes of using some ccTLDs, country-code top level domains, that risk sudden draconian rules, domain renewal price hikes, or other unpredictable risks due to the politics, turmoil, regime changes etc. of the countries that administrate such domains.
Nearly the entirety of every Mastodon server, every post, every reply, is ephemeral.
When a Mastodon server shuts down, all its posts disappear from the surface of the web, forever.
Perhaps internet archeologists of the future will discover such dead permalinks, check the Internet Archive, find apparent desolation, and a few of them will be curious enough to use View Source tools to unearth parts of those posts, unintentionally preserved inside ceremonial meta tags next to dead scripts disconnected from databases and an empty shell of a body. \u00a0
All reply-contexts of and replies to such posts and conversations lost, like threads unraveled from an ancient tapestry, scattered to the winds.
If you\u2019re reading this post in your Mastodon reader, on either the website of your Mastodon account, or in a proprietary native client application, you should be able to click through, perhaps on the date-time stamp displayed to you, to view the original post on my website, where it is served in relatively simple declarative HTML + CSS with a bit of progressive enhancement script.
Because I serve declarative content, my posts are both findable across a variety of services & search engines, and archived by the Internet Archive. Even if my site goes down, snapshots or archives will be viewable elsewhere, with nearly the same fidelity of viewing them directly on my site.
This design for longevity is both deliberate, and the default for which the web was designed. It\u2019s also one of the explicit principles in the IndieWeb community.
If that resonates with you, if creating, writing, & building things that last matter to you, choose web tools, services, and software that support the persistence & longevity of your work.
#persistentWeb<\/span> #longWeb<\/span> #LongNow<\/span>
This is post 10 of #100PostsOfIndieWeb<\/span>. #100Posts<\/span>
\u2190 https:\/\/tantek.com\/2024\/035\/t2\/indiewebcamp-brighton-tickets-available<\/a>
\u2192 \ud83d\udd2e
Post glossary:
API (Application Programming Interface)
\u00a0 https:\/\/indieweb.org\/API<\/a>
Bluesky
\u00a0 https:\/\/indieweb.org\/Bluesky<\/a>
Bridgy
\u00a0 https:\/\/brid.gy\/<\/a>
Bridgy Fed
\u00a0 https:\/\/fed.brid.gy\/<\/a>
ccTLD (country-code top level domain)
\u00a0 https:\/\/indieweb.org\/ccTLD<\/a>
curlable
\u00a0 https:\/\/indieweb.org\/curlable<\/a>
declarative web
\u00a0 https:\/\/www.mozilla.org\/en-US\/about\/webvision\/full\/#thedeclarativeweb<\/a>
Internet Archive
\u00a0 https:\/\/archive.org\/<\/a>
js;dr (JavaScript required; Didn\u2019t Read)
\u00a0 https:\/\/tantek.com\/2015\/069\/t1\/js-dr-javascript-required-dead<\/a>
JSON
\u00a0 https:\/\/indieweb.org\/JSON<\/a>
longevity
\u00a0 https:\/\/indieweb.org\/longevity<\/a>
Mastodon
\u00a0 https:\/\/indieweb.org\/Mastodon<\/a>
metaformats
\u00a0 https:\/\/microformats.org\/wiki\/metaformats<\/a>
permalink
\u00a0 https:\/\/indieweb.org\/permalink<\/a>
principles in the IndieWeb community
\u00a0 https:\/\/indieweb.org\/principles<\/a>
progressive enhancement
\u00a0 https:\/\/indieweb.org\/progressive_enhancement<\/a>
reply
\u00a0 https:\/\/indieweb.org\/reply<\/a>
reply-context
\u00a0 https:\/\/indieweb.org\/reply-context<\/a>
robots.txt
\u00a0 https:\/\/indieweb.org\/robots_txt<\/a>
social media
\u00a0 https:\/\/indieweb.org\/social_media<\/a>
silo
\u00a0 https:\/\/indieweb.org\/silo<\/a>
View Source
\u00a0 https:\/\/firefox-source-docs.mozilla.org\/devtools-user\/view_source\/index.html<\/a>
\u00b9<\/a> https:\/\/chat.indieweb.org\/2024-02-13#t1707845454695700<\/a>
\u00b2<\/a> https:\/\/indieweb.org\/site-deaths<\/a>","url":"https:\/\/tantek.com\/2024\/046\/t1\/the-ephemeral-web","status_net":{"notice_id":116170},"tags":[{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"100posts"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"100postsofindieweb"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"bluesky"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"bridgy"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"bridgyfed"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"curlable"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"ephemeralweb"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"fediverse"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"indieweb"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"longnowthis"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"longweb"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"mastodon"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"openweb"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"queeraf"}]},"to":[{"objectType":"http:\/\/activitystrea.ms\/schema\/1.0\/collection","id":"http:\/\/activityschema.org\/collection\/public"}],"status_net":{"conversation":"tag:status.blaise.ca,2024-02-16:objectType=thread:nonce=fd6b1bb12f00f7f5","notice_info":{"local_id":"116170","source":"ostatus"}},"published":"2024-02-15T21:18:00+00:00","provider":{"objectType":"service","displayName":"stadeus","url":"http:\/\/status.blaise.ca\/"},"verb":"post","url":"https:\/\/tantek.com\/2024\/046\/t1\/the-ephemeral-web"},{"actor":{"id":"http:\/\/tantek.com\/","displayName":"Tantek","status_net":{"avatarLinks":[{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-profile.png","rel":"avatar","type":"image\/png","width":96,"height":96},{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-stream.png","rel":"avatar","type":"image\/png","width":48,"height":48},{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-mini.png","rel":"avatar","type":"image\/png","width":24,"height":24}],"profile_info":{"local_id":"207"}},"image":{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-profile.png","rel":"avatar","type":"image\/png","width":96,"height":96},"objectType":"person","url":"http:\/\/tantek.com\/","portablecontacts_net":{"displayName":"Tantek","addresses":{"formatted":"\nSan Francisco, CA\n"}}},"content":"Twenty years and two days ago, @KevinMarks.com<\/a> (@KevinMarks@xoxo.zone<\/a> @KevinMarks<\/a>) and I introduced #microformats<\/span> in a conference presentation.
I wrote a long retrospective last year: https:\/\/tantek.com\/2023\/047\/t1\/nineteen-years-microformats<\/a>
Since that post nearly a year ago, here are the top three updates & interesting developments in microformats:
1. Growing rel=me adoption for distributed verification (\u2705 in Mastodon etc.)
\u00a0* Wikipedia: https:\/\/tantek.com\/2023\/139\/t1\/wikipedia-supports-indieweb-rel-me<\/a>
\u00a0* Threads: https:\/\/tantek.com\/2023\/234\/t1\/threads-supports-indieweb-rel-me<\/a>
\u00a0* omg.lol<\/a> profile links by default: https:\/\/home.omg.lol\/info\/profile-items<\/a>
2. A proposal to merge h-review into h-entry, since reviews are in practice always entries with a bit more information:
\u00a0* https:\/\/github.com\/microformats\/h-entry\/issues\/32<\/a>
\u00a0
3. #metaformats<\/span> adoptions, implementations, and iteration
\u00a0* There was growing practical interest in metaformats, so I updated the spec accordingly
\u00a0* A half dozen implementations shipped: https:\/\/indieweb.org\/metaformats#IndieWeb_Examples<\/a>
\u00a0* Active discussion for evolving metaformats to support more real world use-cases: https:\/\/github.com\/microformats\/metaformats\/issues<\/a>
Hard to believe it\u2019s been 20 years of iterating and evolving microformats, to #microformats2<\/span>, growing adoption as #IndieWeb<\/span> building blocks, distributed verification (those green checkmarks) in #Mastodon<\/span> and across the #fediverse<\/span>, and implementing metaformats parsing to standardize parsing various meta tags for link previews into equivalent microformats2.
From last year\u2019s activity, it\u2019s clear there\u2019s more use-cases, implementer interest, and community activity than ever. \u00a0Looking forward to seeing what we can build in 2024.
Post Glossary
h-entry
\u00a0 https:\/\/microformats.org\/wiki\/h-entry<\/a>
h-review
\u00a0 https:\/\/microformats.org\/wiki\/h-review<\/a>
link-preview
\u00a0 https:\/\/indieweb.org\/link-preview<\/a>
metaformats
\u00a0 https:\/\/microformats.org\/wiki\/metaformats<\/a>
microformats
\u00a0 https:\/\/microformats.org\/wiki\/<\/a>
microformats2
\u00a0 https:\/\/microformats.org\/wiki\/microformats2<\/a>
rel-me
\u00a0 https:\/\/microformats.org\/wiki\/rel-me<\/a>","generator":{"id":"tag:status.net,2009:notice-source:ostatus","objectType":"application","status_net":{"source_code":"ostatus"}},"id":"https:\/\/tantek.com\/2024\/044\/t1\/twenty-years-microformats-updates","object":{"id":"https:\/\/tantek.com\/2024\/044\/t1\/twenty-years-microformats-updates","objectType":"note","content":"Twenty years and two days ago, @KevinMarks.com<\/a> (@KevinMarks@xoxo.zone<\/a> @KevinMarks<\/a>) and I introduced #microformats<\/span> in a conference presentation.
I wrote a long retrospective last year: https:\/\/tantek.com\/2023\/047\/t1\/nineteen-years-microformats<\/a>
Since that post nearly a year ago, here are the top three updates & interesting developments in microformats:
1. Growing rel=me adoption for distributed verification (\u2705 in Mastodon etc.)
\u00a0* Wikipedia: https:\/\/tantek.com\/2023\/139\/t1\/wikipedia-supports-indieweb-rel-me<\/a>
\u00a0* Threads: https:\/\/tantek.com\/2023\/234\/t1\/threads-supports-indieweb-rel-me<\/a>
\u00a0* omg.lol<\/a> profile links by default: https:\/\/home.omg.lol\/info\/profile-items<\/a>
2. A proposal to merge h-review into h-entry, since reviews are in practice always entries with a bit more information:
\u00a0* https:\/\/github.com\/microformats\/h-entry\/issues\/32<\/a>
\u00a0
3. #metaformats<\/span> adoptions, implementations, and iteration
\u00a0* There was growing practical interest in metaformats, so I updated the spec accordingly
\u00a0* A half dozen implementations shipped: https:\/\/indieweb.org\/metaformats#IndieWeb_Examples<\/a>
\u00a0* Active discussion for evolving metaformats to support more real world use-cases: https:\/\/github.com\/microformats\/metaformats\/issues<\/a>
Hard to believe it\u2019s been 20 years of iterating and evolving microformats, to #microformats2<\/span>, growing adoption as #IndieWeb<\/span> building blocks, distributed verification (those green checkmarks) in #Mastodon<\/span> and across the #fediverse<\/span>, and implementing metaformats parsing to standardize parsing various meta tags for link previews into equivalent microformats2.
From last year\u2019s activity, it\u2019s clear there\u2019s more use-cases, implementer interest, and community activity than ever. \u00a0Looking forward to seeing what we can build in 2024.
Post Glossary
h-entry
\u00a0 https:\/\/microformats.org\/wiki\/h-entry<\/a>
h-review
\u00a0 https:\/\/microformats.org\/wiki\/h-review<\/a>
link-preview
\u00a0 https:\/\/indieweb.org\/link-preview<\/a>
metaformats
\u00a0 https:\/\/microformats.org\/wiki\/metaformats<\/a>
microformats
\u00a0 https:\/\/microformats.org\/wiki\/<\/a>
microformats2
\u00a0 https:\/\/microformats.org\/wiki\/microformats2<\/a>
rel-me
\u00a0 https:\/\/microformats.org\/wiki\/rel-me<\/a>","url":"https:\/\/tantek.com\/2024\/044\/t1\/twenty-years-microformats-updates","status_net":{"notice_id":116169},"tags":[{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"fediverse"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"indieweb"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"mastodon"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"metaformats"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"microformats"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"microformats2"}]},"to":[{"objectType":"http:\/\/activitystrea.ms\/schema\/1.0\/collection","id":"http:\/\/activityschema.org\/collection\/public"}],"status_net":{"conversation":"tag:status.blaise.ca,2024-02-15:objectType=thread:nonce=f41cb86551d10a2d","notice_info":{"local_id":"116169","source":"ostatus"}},"published":"2024-02-14T06:03:00+00:00","provider":{"objectType":"service","displayName":"stadeus","url":"http:\/\/status.blaise.ca\/"},"verb":"post","url":"https:\/\/tantek.com\/2024\/044\/t1\/twenty-years-microformats-updates"},{"actor":{"id":"http:\/\/tantek.com\/","displayName":"Tantek","status_net":{"avatarLinks":[{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-profile.png","rel":"avatar","type":"image\/png","width":96,"height":96},{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-stream.png","rel":"avatar","type":"image\/png","width":48,"height":48},{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-mini.png","rel":"avatar","type":"image\/png","width":24,"height":24}],"profile_info":{"local_id":"207"}},"image":{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-profile.png","rel":"avatar","type":"image\/png","width":96,"height":96},"objectType":"person","url":"http:\/\/tantek.com\/","portablecontacts_net":{"displayName":"Tantek","addresses":{"formatted":"\nSan Francisco, CA\n"}}},"content":"Twenty years and two days ago, @KevinMarks.com<\/a> (@KevinMarks@xoxo.zone<\/a> @KevinMarks<\/a>) and I introduced #microformats<\/span> in a conference presentation.
I wrote a long retrospective last year: https:\/\/tantek.com\/2023\/047\/t1\/nineteen-years-microformats<\/a>
Since that update nearly a year ago, here are the top three interesting developments in microformats:
1. Growing rel=me adoption for distributed verification:
\u00a0* Wikipedia: https:\/\/tantek.com\/2023\/139\/t1\/wikipedia-supports-indieweb-rel-me<\/a>
\u00a0* Threads: https:\/\/tantek.com\/2023\/234\/t1\/threads-supports-indieweb-rel-me<\/a>
\u00a0* omg.lol<\/a> profile links by default: https:\/\/home.omg.lol\/info\/profile-items<\/a>
2. A proposal to merge h-review into h-entry, since reviews are in practice always entries with a bit more information:
\u00a0* https:\/\/github.com\/microformats\/h-entry\/issues\/32<\/a>
\u00a0
3. #metaformats<\/span> adoptions, implementations, and iteration
\u00a0* There was growing practical interest in metaformats, so I updated the spec accordingly
\u00a0* A half dozen implementations shipped: https:\/\/indieweb.org\/metaformats#IndieWeb_Examples<\/a>
\u00a0* Active discussion for evolving metaformats to support more real world use-cases: https:\/\/github.com\/microformats\/metaformats\/issues<\/a>
Hard to believe it\u2019s been 20 years of iterating and evolving microformats, to #microformats2<\/span>, growing adoption as #IndieWeb<\/span> building blocks, distributed verification (those green checkmarks) in #Mastodon<\/span> and across the #fediverse<\/span>, and implementing metaformats parsing to standardize parsing various meta tags for link previews into equivalent microformats2.
From last year\u2019s activity, it\u2019s clear there\u2019s more use-cases, implementer interest, and community activity than ever. \u00a0Looking forward to seeing what we can build in 2024.
Post Glossary
h-entry
\u00a0 https:\/\/microformats.org\/wiki\/h-entry<\/a>
h-review
\u00a0 https:\/\/microformats.org\/wiki\/h-review<\/a>
link-preview
\u00a0 https:\/\/indieweb.org\/link-preview<\/a>
metaformats
\u00a0 https:\/\/microformats.org\/wiki\/metaformats<\/a>
microformats
\u00a0 https:\/\/microformats.org\/wiki\/<\/a>
microformats2
\u00a0 https:\/\/microformats.org\/wiki\/microformats2<\/a>
rel-me
\u00a0 https:\/\/microformats.org\/wiki\/rel-me<\/a>","generator":{"id":"tag:status.net,2009:notice-source:ostatus","objectType":"application","status_net":{"source_code":"ostatus"}},"id":"https:\/\/tantek.com\/2024\/044\/t1\/twenty-years-microformats","object":{"id":"https:\/\/tantek.com\/2024\/044\/t1\/twenty-years-microformats","objectType":"note","content":"Twenty years and two days ago, @KevinMarks.com<\/a> (@KevinMarks@xoxo.zone<\/a> @KevinMarks<\/a>) and I introduced #microformats<\/span> in a conference presentation.
I wrote a long retrospective last year: https:\/\/tantek.com\/2023\/047\/t1\/nineteen-years-microformats<\/a>
Since that update nearly a year ago, here are the top three interesting developments in microformats:
1. Growing rel=me adoption for distributed verification:
\u00a0* Wikipedia: https:\/\/tantek.com\/2023\/139\/t1\/wikipedia-supports-indieweb-rel-me<\/a>
\u00a0* Threads: https:\/\/tantek.com\/2023\/234\/t1\/threads-supports-indieweb-rel-me<\/a>
\u00a0* omg.lol<\/a> profile links by default: https:\/\/home.omg.lol\/info\/profile-items<\/a>
2. A proposal to merge h-review into h-entry, since reviews are in practice always entries with a bit more information:
\u00a0* https:\/\/github.com\/microformats\/h-entry\/issues\/32<\/a>
\u00a0
3. #metaformats<\/span> adoptions, implementations, and iteration
\u00a0* There was growing practical interest in metaformats, so I updated the spec accordingly
\u00a0* A half dozen implementations shipped: https:\/\/indieweb.org\/metaformats#IndieWeb_Examples<\/a>
\u00a0* Active discussion for evolving metaformats to support more real world use-cases: https:\/\/github.com\/microformats\/metaformats\/issues<\/a>
Hard to believe it\u2019s been 20 years of iterating and evolving microformats, to #microformats2<\/span>, growing adoption as #IndieWeb<\/span> building blocks, distributed verification (those green checkmarks) in #Mastodon<\/span> and across the #fediverse<\/span>, and implementing metaformats parsing to standardize parsing various meta tags for link previews into equivalent microformats2.
From last year\u2019s activity, it\u2019s clear there\u2019s more use-cases, implementer interest, and community activity than ever. \u00a0Looking forward to seeing what we can build in 2024.
Post Glossary
h-entry
\u00a0 https:\/\/microformats.org\/wiki\/h-entry<\/a>
h-review
\u00a0 https:\/\/microformats.org\/wiki\/h-review<\/a>
link-preview
\u00a0 https:\/\/indieweb.org\/link-preview<\/a>
metaformats
\u00a0 https:\/\/microformats.org\/wiki\/metaformats<\/a>
microformats
\u00a0 https:\/\/microformats.org\/wiki\/<\/a>
microformats2
\u00a0 https:\/\/microformats.org\/wiki\/microformats2<\/a>
rel-me
\u00a0 https:\/\/microformats.org\/wiki\/rel-me<\/a>","url":"https:\/\/tantek.com\/2024\/044\/t1\/twenty-years-microformats","status_net":{"notice_id":116168},"tags":[{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"fediverse"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"indieweb"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"mastodon"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"metaformats"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"microformats"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"microformats2"}]},"to":[{"objectType":"http:\/\/activitystrea.ms\/schema\/1.0\/collection","id":"http:\/\/activityschema.org\/collection\/public"}],"status_net":{"conversation":"tag:status.blaise.ca,2024-02-14:objectType=thread:nonce=3a070e4e6f296876","notice_info":{"local_id":"116168","source":"ostatus"}},"published":"2024-02-14T06:03:00+00:00","provider":{"objectType":"service","displayName":"stadeus","url":"http:\/\/status.blaise.ca\/"},"verb":"post","url":"https:\/\/tantek.com\/2024\/044\/t1\/twenty-years-microformats"},{"actor":{"id":"http:\/\/tantek.com\/","displayName":"Tantek","status_net":{"avatarLinks":[{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-profile.png","rel":"avatar","type":"image\/png","width":96,"height":96},{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-stream.png","rel":"avatar","type":"image\/png","width":48,"height":48},{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-mini.png","rel":"avatar","type":"image\/png","width":24,"height":24}],"profile_info":{"local_id":"207"}},"image":{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-profile.png","rel":"avatar","type":"image\/png","width":96,"height":96},"objectType":"person","url":"http:\/\/tantek.com\/","portablecontacts_net":{"displayName":"Tantek","addresses":{"formatted":"\nSan Francisco, CA\n"}}},"content":"#Brighton<\/span> #London<\/span> and other #England<\/span> & #Europe<\/span> friends:
\ud83c\udfaa #IndieWebCamp<\/span> Brighton tickets are available!
\ud83c\udf9f https:\/\/ti.to\/indiewebcamp\/brighton-2024<\/a>
\ud83d\uddd3 2024-03-09\u202610
\ud83c\udfe2 The Skiff, Brighton, England
\ud83c\udf10 https:\/\/indieweb.org\/2024\/Brighton<\/a>
Grab an in-person ticket (limited capacity) then optionally add yourself to the list of participants: https:\/\/indieweb.org\/2024\/Brighton#In_person<\/a>
For more information, see organizer @paulrobertlloyd.com<\/a> (@paulrobertlloyd@mastodon.social<\/a>)\u2019s post: https:\/\/paulrobertlloyd.com\/2024\/032\/a1\/indiewebcamp_brighton\/<\/a>
Also check out @ClearLeft.com<\/a> (@clearleft@mastodon.social<\/a> @clearleft<\/a>)\u2019s \u201cPatterns Day\u201d (https:\/\/patternsday.com\/<\/a>) in Brighton the Thursday (2024-03-07) beforehand!
Previously: https:\/\/tantek.com\/2024\/022\/t1\/indiewebcamp-brighton-planned<\/a>
This is post 9 of #100PostsOfIndieWeb<\/span>. #100Posts<\/span> #IndieWeb<\/span>
\u2190 https:\/\/tantek.com\/2024\/035\/t1\/greshams-law-developers-users-jargon<\/a>
\u2192 \ud83d\udd2e","generator":{"id":"tag:status.net,2009:notice-source:ostatus","objectType":"application","status_net":{"source_code":"ostatus"}},"id":"https:\/\/tantek.com\/2024\/035\/t2\/indiewebcamp-brighton-tickets-available","object":{"id":"https:\/\/tantek.com\/2024\/035\/t2\/indiewebcamp-brighton-tickets-available","objectType":"note","content":"#Brighton<\/span> #London<\/span> and other #England<\/span> & #Europe<\/span> friends:
\ud83c\udfaa #IndieWebCamp<\/span> Brighton tickets are available!
\ud83c\udf9f https:\/\/ti.to\/indiewebcamp\/brighton-2024<\/a>
\ud83d\uddd3 2024-03-09\u202610
\ud83c\udfe2 The Skiff, Brighton, England
\ud83c\udf10 https:\/\/indieweb.org\/2024\/Brighton<\/a>
Grab an in-person ticket (limited capacity) then optionally add yourself to the list of participants: https:\/\/indieweb.org\/2024\/Brighton#In_person<\/a>
For more information, see organizer @paulrobertlloyd.com<\/a> (@paulrobertlloyd@mastodon.social<\/a>)\u2019s post: https:\/\/paulrobertlloyd.com\/2024\/032\/a1\/indiewebcamp_brighton\/<\/a>
Also check out @ClearLeft.com<\/a> (@clearleft@mastodon.social<\/a> @clearleft<\/a>)\u2019s \u201cPatterns Day\u201d (https:\/\/patternsday.com\/<\/a>) in Brighton the Thursday (2024-03-07) beforehand!
Previously: https:\/\/tantek.com\/2024\/022\/t1\/indiewebcamp-brighton-planned<\/a>
This is post 9 of #100PostsOfIndieWeb<\/span>. #100Posts<\/span> #IndieWeb<\/span>
\u2190 https:\/\/tantek.com\/2024\/035\/t1\/greshams-law-developers-users-jargon<\/a>
\u2192 \ud83d\udd2e","url":"https:\/\/tantek.com\/2024\/035\/t2\/indiewebcamp-brighton-tickets-available","status_net":{"notice_id":116167},"tags":[{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"100posts"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"100postsofindieweb"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"brighton"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"england"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"europe"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"indieweb"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"indiewebcamp"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"london"}]},"to":[{"objectType":"http:\/\/activitystrea.ms\/schema\/1.0\/collection","id":"http:\/\/activityschema.org\/collection\/public"}],"status_net":{"conversation":"tag:status.blaise.ca,2024-02-05:objectType=thread:nonce=426e321047ee407e","notice_info":{"local_id":"116167","source":"ostatus"}},"published":"2024-02-05T04:08:00+00:00","provider":{"objectType":"service","displayName":"stadeus","url":"http:\/\/status.blaise.ca\/"},"verb":"post","url":"https:\/\/tantek.com\/2024\/035\/t2\/indiewebcamp-brighton-tickets-available"},{"actor":{"id":"http:\/\/tantek.com\/","displayName":"Tantek","status_net":{"avatarLinks":[{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-profile.png","rel":"avatar","type":"image\/png","width":96,"height":96},{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-stream.png","rel":"avatar","type":"image\/png","width":48,"height":48},{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-mini.png","rel":"avatar","type":"image\/png","width":24,"height":24}],"profile_info":{"local_id":"207"}},"image":{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-profile.png","rel":"avatar","type":"image\/png","width":96,"height":96},"objectType":"person","url":"http:\/\/tantek.com\/","portablecontacts_net":{"displayName":"Tantek","addresses":{"formatted":"\nSan Francisco, CA\n"}}},"content":"Similar to @paulgraham.com<\/a> (@paulg@mas.to<\/a> @paulg<\/a>)\u2019s 2008 observation about trolls\u00b9<\/a>, there\u2019s a sort of Gresham's Law of developers (vs users): developers are willing to use a forum with a lot of users in it, but users aren\u2019t willing to use a forum with a lot of developer-speak.
Whether such forums are email lists, chat (IRC, #Matrix<\/span>, #Slack<\/span>, #Discord<\/span>), or, well, online forums (#Reddit, #HackerNews<\/span>), when discussions either start or shift into technical details, jargon, or acronyms, users (in a very broad sense) tend to stop participating, and sometimes leave, never to return.
Users in this context are anyone with a desire (or a preference) not to chat or even be bothered spending time reading about technical plumbing & #jargon<\/span>, and see such discussions as a distraction at best, and more like noise to be avoided.
Paraphrasing Paul Graham again: once technical details, jargon, acronyms \u201ctake hold, it tends to become the dominant culture\u201d and discourages users from showing up, discussing user-centric topics, or even staying in said forum.
The #IndieWeb<\/span> community started in 2011 as a single #indiewebcamp<\/span> IRC channel (no email list\u00b2<\/a>) because it was tightly coupled to IndieWebCamp events, which were both highly technical and yet focused on actually making things work on your personal site that you need\u00b3<\/a>, that you will use\u2074<\/a> yourself. Conversations bridged real world use-cases and technical details.
It only took us five years after the first IndieWebCamp in Portland to recognize that the community had grown beyond the events, and had a clear need for a separate place for deep discussions of developer topics.
As part of renaming the community from IndieWebCamp to IndieWeb\u2075<\/a>, we created the #indieweb-dev<\/span> (dev) channel for such technical topics like protocols, formats, tools, coding libraries, APIs, and any other acronyms or jargon.
The community did a good job of keeping technical topics in the dev channel, and encouraging new folks in the main #indieweb<\/span> channel who started technical conversations to continue them in the dev channel.
Still, it was too easy for user-centric topics to veer into technical territory. It often felt more natural to continue a thread in the channel it started rather than break to another channel. There was also a need for regular community labor to nudge developer conversations to the developer chat channel.
We had already started documenting IndieWeb related jargon\u2076<\/a> on the wiki and turned it into a MediaWiki Category so we could tag individual pages as jargon and have them automatically show-up in a list. Soon after, @aaronparecki.com<\/a> (@aaronpk@aaronparecki.com<\/a>) added a heuristic to the friendly channel bot Loqi to recognize when people started using jargon in the main IndieWeb chat channel and nudge\u2077<\/a> them to the development channel.
Having Loqi do some of the gentle nudging has helped, though it\u2018s still quite easy for even the experienced folks in the community to get drawn into a developer conversation on main as it were.
We\u2019ve documented both a summary and lengthier descriptions of channel purposes\u2078<\/a> which help us remind each other, as well as provide a guide to newcomers.
Both experienced community members and newcomers share much of the user-centric focus of the IndieWeb, the IndieWeb being for everyone\u2079<\/a>, whether developer, hobbyist, or someone who wants an independent presence on the web without bothering with technical details. Whether some of us want to code or not, we all want to use our IndieWeb sites to express ourselves on the web, to use our sites instead of depending on social media silos. That shared purpose keeps us focused.
It takes a village: eternal community vigilance is the price of staying user-centric and welcoming to newcomers.
The ideas behind this post were originally shared in the IndieWeb meta chat channel.\u00b9\u2070<\/a>
This is post 8 of #100PostsOfIndieWeb<\/span>. #100Posts<\/span>
\u2190 https:\/\/tantek.com\/2024\/033\/t1\/earthquake-sanfrancisco-shifted<\/a>
\u2192 \ud83d\udd2e
Post glossary:
development channel (indieweb-dev)
\u00a0 https:\/\/indieweb.org\/discuss#dev<\/a>
Discord
\u00a0 https:\/\/indieweb.org\/Discord<\/a>
format
\u00a0 https:\/\/indieweb.org\/format<\/a>
Hacker News (HN)
\u00a0 https:\/\/indieweb.org\/Hacker_News<\/a>
IndieWeb
\u00a0 https:\/\/indieweb.org\/IndieWeb<\/a>
IndieWebCamp
\u00a0 https:\/\/indieweb.org\/IndieWebCamp<\/a>
IRC
\u00a0 https:\/\/indieweb.org\/IRC<\/a>
jargon
\u00a0 https:\/\/indieweb.org\/jargon<\/a>
Loqi
\u00a0 https:\/\/indieweb.org\/Loqi<\/a>
main IndieWeb chat channel (on main)
\u00a0 https:\/\/indieweb.org\/discuss#indieweb<\/a>
Matrix
\u00a0 https:\/\/indieweb.org\/Matrix<\/a>
meta chat channel
\u00a0 https:\/\/indieweb.org\/discuss#meta<\/a>
MediaWiki Category
\u00a0 https:\/\/www.mediawiki.org\/wiki\/Project:Categories<\/a>
plumbing
\u00a0 https:\/\/indieweb.org\/plumbing<\/a>
protocol
\u00a0 https:\/\/indieweb.org\/protocol<\/a>
Reddit
\u00a0 https:\/\/indieweb.org\/Reddit<\/a>
tools
\u00a0 https:\/\/indieweb.org\/tools<\/a>
Slack
\u00a0 https:\/\/indieweb.org\/Slack<\/a>
social media silos
\u00a0 https:\/\/indieweb.org\/silos<\/a>
\u00b9<\/a> https:\/\/www.paulgraham.com\/trolls.html<\/a> (2008 essay, HN still succumbed to trolling)
\u00b2<\/a> https:\/\/indieweb.org\/discuss#Email<\/a>
\u00b3<\/a> https:\/\/indieweb.org\/make_what_you_need<\/a>
\u2074<\/a> https:\/\/indieweb.org\/use_what_you_make<\/a>
\u2075<\/a> https:\/\/indieweb.org\/rename_to_IndieWeb<\/a>
\u2076<\/a> https:\/\/indieweb.org\/jargon<\/a>
\u2077<\/a> https:\/\/indieweb.org\/Category:jargon#Loqi_Nudge<\/a>
\u2078<\/a> https:\/\/indieweb.org\/discuss#Chat_Channels_Purposes<\/a>
\u2079<\/a> https:\/\/tantek.com\/2024\/026\/t3\/indieweb-for-everyone-internet-of-people<\/a>
\u00b9\u2070<\/a> https:\/\/chat.indieweb.org\/meta\/2024-01-22#t1705883690759800<\/a>","generator":{"id":"tag:status.net,2009:notice-source:ostatus","objectType":"application","status_net":{"source_code":"ostatus"}},"id":"https:\/\/tantek.com\/2024\/035\/t1\/greshams-law-developers-users-jargon","object":{"id":"https:\/\/tantek.com\/2024\/035\/t1\/greshams-law-developers-users-jargon","objectType":"note","content":"Similar to @paulgraham.com<\/a> (@paulg@mas.to<\/a> @paulg<\/a>)\u2019s 2008 observation about trolls\u00b9<\/a>, there\u2019s a sort of Gresham's Law of developers (vs users): developers are willing to use a forum with a lot of users in it, but users aren\u2019t willing to use a forum with a lot of developer-speak.
Whether such forums are email lists, chat (IRC, #Matrix<\/span>, #Slack<\/span>, #Discord<\/span>), or, well, online forums (#Reddit, #HackerNews<\/span>), when discussions either start or shift into technical details, jargon, or acronyms, users (in a very broad sense) tend to stop participating, and sometimes leave, never to return.
Users in this context are anyone with a desire (or a preference) not to chat or even be bothered spending time reading about technical plumbing & #jargon<\/span>, and see such discussions as a distraction at best, and more like noise to be avoided.
Paraphrasing Paul Graham again: once technical details, jargon, acronyms \u201ctake hold, it tends to become the dominant culture\u201d and discourages users from showing up, discussing user-centric topics, or even staying in said forum.
The #IndieWeb<\/span> community started in 2011 as a single #indiewebcamp<\/span> IRC channel (no email list\u00b2<\/a>) because it was tightly coupled to IndieWebCamp events, which were both highly technical and yet focused on actually making things work on your personal site that you need\u00b3<\/a>, that you will use\u2074<\/a> yourself. Conversations bridged real world use-cases and technical details.
It only took us five years after the first IndieWebCamp in Portland to recognize that the community had grown beyond the events, and had a clear need for a separate place for deep discussions of developer topics.
As part of renaming the community from IndieWebCamp to IndieWeb\u2075<\/a>, we created the #indieweb-dev<\/span> (dev) channel for such technical topics like protocols, formats, tools, coding libraries, APIs, and any other acronyms or jargon.
The community did a good job of keeping technical topics in the dev channel, and encouraging new folks in the main #indieweb<\/span> channel who started technical conversations to continue them in the dev channel.
Still, it was too easy for user-centric topics to veer into technical territory. It often felt more natural to continue a thread in the channel it started rather than break to another channel. There was also a need for regular community labor to nudge developer conversations to the developer chat channel.
We had already started documenting IndieWeb related jargon\u2076<\/a> on the wiki and turned it into a MediaWiki Category so we could tag individual pages as jargon and have them automatically show-up in a list. Soon after, @aaronparecki.com<\/a> (@aaronpk@aaronparecki.com<\/a>) added a heuristic to the friendly channel bot Loqi to recognize when people started using jargon in the main IndieWeb chat channel and nudge\u2077<\/a> them to the development channel.
Having Loqi do some of the gentle nudging has helped, though it\u2018s still quite easy for even the experienced folks in the community to get drawn into a developer conversation on main as it were.
We\u2019ve documented both a summary and lengthier descriptions of channel purposes\u2078<\/a> which help us remind each other, as well as provide a guide to newcomers.
Both experienced community members and newcomers share much of the user-centric focus of the IndieWeb, the IndieWeb being for everyone\u2079<\/a>, whether developer, hobbyist, or someone who wants an independent presence on the web without bothering with technical details. Whether some of us want to code or not, we all want to use our IndieWeb sites to express ourselves on the web, to use our sites instead of depending on social media silos. That shared purpose keeps us focused.
It takes a village: eternal community vigilance is the price of staying user-centric and welcoming to newcomers.
The ideas behind this post were originally shared in the IndieWeb meta chat channel.\u00b9\u2070<\/a>
This is post 8 of #100PostsOfIndieWeb<\/span>. #100Posts<\/span>
\u2190 https:\/\/tantek.com\/2024\/033\/t1\/earthquake-sanfrancisco-shifted<\/a>
\u2192 \ud83d\udd2e
Post glossary:
development channel (indieweb-dev)
\u00a0 https:\/\/indieweb.org\/discuss#dev<\/a>
Discord
\u00a0 https:\/\/indieweb.org\/Discord<\/a>
format
\u00a0 https:\/\/indieweb.org\/format<\/a>
Hacker News (HN)
\u00a0 https:\/\/indieweb.org\/Hacker_News<\/a>
IndieWeb
\u00a0 https:\/\/indieweb.org\/IndieWeb<\/a>
IndieWebCamp
\u00a0 https:\/\/indieweb.org\/IndieWebCamp<\/a>
IRC
\u00a0 https:\/\/indieweb.org\/IRC<\/a>
jargon
\u00a0 https:\/\/indieweb.org\/jargon<\/a>
Loqi
\u00a0 https:\/\/indieweb.org\/Loqi<\/a>
main IndieWeb chat channel (on main)
\u00a0 https:\/\/indieweb.org\/discuss#indieweb<\/a>
Matrix
\u00a0 https:\/\/indieweb.org\/Matrix<\/a>
meta chat channel
\u00a0 https:\/\/indieweb.org\/discuss#meta<\/a>
MediaWiki Category
\u00a0 https:\/\/www.mediawiki.org\/wiki\/Project:Categories<\/a>
plumbing
\u00a0 https:\/\/indieweb.org\/plumbing<\/a>
protocol
\u00a0 https:\/\/indieweb.org\/protocol<\/a>
Reddit
\u00a0 https:\/\/indieweb.org\/Reddit<\/a>
tools
\u00a0 https:\/\/indieweb.org\/tools<\/a>
Slack
\u00a0 https:\/\/indieweb.org\/Slack<\/a>
social media silos
\u00a0 https:\/\/indieweb.org\/silos<\/a>
\u00b9<\/a> https:\/\/www.paulgraham.com\/trolls.html<\/a> (2008 essay, HN still succumbed to trolling)
\u00b2<\/a> https:\/\/indieweb.org\/discuss#Email<\/a>
\u00b3<\/a> https:\/\/indieweb.org\/make_what_you_need<\/a>
\u2074<\/a> https:\/\/indieweb.org\/use_what_you_make<\/a>
\u2075<\/a> https:\/\/indieweb.org\/rename_to_IndieWeb<\/a>
\u2076<\/a> https:\/\/indieweb.org\/jargon<\/a>
\u2077<\/a> https:\/\/indieweb.org\/Category:jargon#Loqi_Nudge<\/a>
\u2078<\/a> https:\/\/indieweb.org\/discuss#Chat_Channels_Purposes<\/a>
\u2079<\/a> https:\/\/tantek.com\/2024\/026\/t3\/indieweb-for-everyone-internet-of-people<\/a>
\u00b9\u2070<\/a> https:\/\/chat.indieweb.org\/meta\/2024-01-22#t1705883690759800<\/a>","url":"https:\/\/tantek.com\/2024\/035\/t1\/greshams-law-developers-users-jargon","status_net":{"notice_id":116166},"tags":[{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"100posts"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"100postsofindieweb"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"discord"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"hackernews"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"indieweb"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"indiewebcamp"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"indiewebdev"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"jargon"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"matrix"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"slack"}]},"to":[{"objectType":"http:\/\/activitystrea.ms\/schema\/1.0\/collection","id":"http:\/\/activityschema.org\/collection\/public"}],"status_net":{"conversation":"tag:status.blaise.ca,2024-02-05:objectType=thread:nonce=735a2250f00304a3","notice_info":{"local_id":"116166","source":"ostatus"}},"published":"2024-02-04T23:05:00+00:00","provider":{"objectType":"service","displayName":"stadeus","url":"http:\/\/status.blaise.ca\/"},"verb":"post","url":"https:\/\/tantek.com\/2024\/035\/t1\/greshams-law-developers-users-jargon"},{"actor":{"id":"http:\/\/tantek.com\/","displayName":"Tantek","status_net":{"avatarLinks":[{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-profile.png","rel":"avatar","type":"image\/png","width":96,"height":96},{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-stream.png","rel":"avatar","type":"image\/png","width":48,"height":48},{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-mini.png","rel":"avatar","type":"image\/png","width":24,"height":24}],"profile_info":{"local_id":"207"}},"image":{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-profile.png","rel":"avatar","type":"image\/png","width":96,"height":96},"objectType":"person","url":"http:\/\/tantek.com\/","portablecontacts_net":{"displayName":"Tantek","addresses":{"formatted":"\nSan Francisco, CA\n"}}},"content":"Similar to @paulgraham.com<\/a> (@paulg@mas.to<\/a> @paulg<\/a>)\u2019s observation about trolls\u00b9<\/a>, there\u2019s a sort of Gresham's Law of developers (vs users): developers are willing to use a forum with a lot of users in it, but users aren\u2019t willing to use a forum with a lot of developer-speak.
Whether such forums are email lists, chat (IRC, #Matrix<\/span>, #Slack<\/span>, #Discord<\/span>), or, well, online forums (#Reddit, #HackerNews<\/span>), when discussions either start or shift into technical details, jargon, or acronyms, users (in a very broad sense) tend to stop participating, and sometimes leave, never to return.
Users in this context are anyone with a desire (or a preference) not to chat or even be bothered spending time reading about technical plumbing & #jargon<\/span>, and see such discussions as a distraction at best, and more like noise to be avoided.
Paraphrasing Paul Graham again: once technical details, jargon, acronyms \u201ctake hold, it tends to become the dominant culture\u201d and discourages users from showing up, discussing user-centric topics, or even staying in said forum.
The #IndieWeb<\/span> community started in 2011 as a single IRC channel #indiewebcamp<\/span> (no email list\u00b2<\/a>) because it was tightly coupled to IndieWebCamp events, which were both highly technical and yet focused on actually making things work on your personal site that you need\u00b3<\/a>, that you will use\u2074<\/a> yourself. Conversations bridged real world use-cases and technical details.
It only took us five years after the first IndieWebCamp in Portland to recognize that the community had grown beyond the events, and had a clear need for a separate place for deep discussions of developer topics.
As part of renaming the community from IndieWebCamp to IndieWeb\u2075<\/a>, we created the #indieweb-dev<\/span> (dev) channel for such technical topics like protocols, formats, tools, coding libraries, APIs, and any other acronyms or jargon.
The community did a good job of keeping technical topics in the dev channel, and encouraging new folks in the main #indieweb<\/span> channel who started technical conversations to continue them in the dev channel.
Still, it was too easy for user-centric topics to veer into technical territory. It often felt more natural to continue such threads in the channel it started rather than break to another channel. It was also a constant bit of community labor to nudge developer conversations to the developer chat channel.
We had already started documenting IndieWeb related jargon\u2076<\/a> on the wiki and turned it into a MediaWiki Category so we could tag individual pages as jargon and have them automatically show-up in a list. Soon after, @aaronparecki.com<\/a> (@aaronpk@aaronparecki.com<\/a>) added a heuristic to the friendly channel bot Loqi to recognize when people started using jargon in the main IndieWeb chat channel and nudge\u2077<\/a> them to the development channel.
Having Loqi do some of the gentle nudging has helped, though it\u2018s still quite easy for even the experienced folks in the community to get drawn into a developer conversation on main as it were.
We\u2019ve documented both a summary and lengthier descriptions of channel purposes\u2078<\/a> which help us remind each other, as well as provide a guide to newcomers.
Both experienced community members and newcomers share much of the user-centric focus of the IndieWeb, the IndieWeb being for everyone\u2079<\/a>, whether developer, hobbyist, or someone who wants an independent presence on the web without bothering with technical details. Whether some of us want to code or not, we all want to use our IndieWeb sites to express ourselves on the web, to use our sites instead of depending on social media silos. That shared purpose keeps us focused.
It takes a community to keep a community healthy and welcoming to newcomers. Eternal community vigilance is the price of being user-centric and welcoming to newcomers.
The ideas behind this post were originally shared in the IndieWeb meta chat channel.\u00b9\u2070<\/a>
This is post 8 of #100PostsOfIndieWeb<\/span>. #100Posts<\/span>
\u2190 https:\/\/tantek.com\/2024\/033\/t1\/earthquake-sanfrancisco-shifted<\/a>
\u2192 \ud83d\udd2e
Post glossary:
development channel (indieweb-dev)
\u00a0 https:\/\/indieweb.org\/discuss#dev<\/a>
format
\u00a0 https:\/\/indieweb.org\/format<\/a>
IndieWeb
\u00a0 https:\/\/indieweb.org\/IndieWeb<\/a>
IndieWebCamp
\u00a0 https:\/\/indieweb.org\/IndieWebCamp<\/a>
jargon
\u00a0 https:\/\/indieweb.org\/jargon<\/a>
Loqi
\u00a0 https:\/\/indieweb.org\/Loqi<\/a>
main IndieWeb chat channel (on main)
\u00a0 https:\/\/indieweb.org\/discuss#indieweb<\/a>
meta chat channel
\u00a0 https:\/\/indieweb.org\/discuss#meta<\/a>
MediaWiki Category
\u00a0 https:\/\/www.mediawiki.org\/wiki\/Project:Categories<\/a>
plumbing
\u00a0 https:\/\/indieweb.org\/plumbing<\/a>
protocol
\u00a0 https:\/\/indieweb.org\/protocol<\/a>
tools
\u00a0 https:\/\/indieweb.org\/tools<\/a>
social media silos
\u00a0 https:\/\/indieweb.org\/silos<\/a>
\u00b9<\/a> https:\/\/www.paulgraham.com\/trolls.html<\/a>
\u00b2<\/a> https:\/\/indieweb.org\/discuss#Email<\/a>
\u00b3<\/a> https:\/\/indieweb.org\/make_what_you_need<\/a>
\u2074<\/a> https:\/\/indieweb.org\/use_what_you_make<\/a>
\u2075<\/a> https:\/\/indieweb.org\/rename_to_IndieWeb<\/a>
\u2076<\/a> https:\/\/indieweb.org\/jargon<\/a>
\u2077<\/a> https:\/\/indieweb.org\/Category:jargon#Loqi_Nudge<\/a>
\u2078<\/a> https:\/\/indieweb.org\/discuss#Chat_Channels_Purposes<\/a>
\u2079<\/a> https:\/\/tantek.com\/2024\/026\/t3\/indieweb-for-everyone-internet-of-people<\/a>
\u00b9\u2070<\/a> https:\/\/chat.indieweb.org\/meta\/2024-01-22#t1705883690759800<\/a>","generator":{"id":"tag:status.net,2009:notice-source:ostatus","objectType":"application","status_net":{"source_code":"ostatus"}},"id":"https:\/\/tantek.com\/2024\/035\/t1\/gresham-law-developers-users-jargon","object":{"id":"https:\/\/tantek.com\/2024\/035\/t1\/gresham-law-developers-users-jargon","objectType":"note","content":"Similar to @paulgraham.com<\/a> (@paulg@mas.to<\/a> @paulg<\/a>)\u2019s observation about trolls\u00b9<\/a>, there\u2019s a sort of Gresham's Law of developers (vs users): developers are willing to use a forum with a lot of users in it, but users aren\u2019t willing to use a forum with a lot of developer-speak.
Whether such forums are email lists, chat (IRC, #Matrix<\/span>, #Slack<\/span>, #Discord<\/span>), or, well, online forums (#Reddit, #HackerNews<\/span>), when discussions either start or shift into technical details, jargon, or acronyms, users (in a very broad sense) tend to stop participating, and sometimes leave, never to return.
Users in this context are anyone with a desire (or a preference) not to chat or even be bothered spending time reading about technical plumbing & #jargon<\/span>, and see such discussions as a distraction at best, and more like noise to be avoided.
Paraphrasing Paul Graham again: once technical details, jargon, acronyms \u201ctake hold, it tends to become the dominant culture\u201d and discourages users from showing up, discussing user-centric topics, or even staying in said forum.
The #IndieWeb<\/span> community started in 2011 as a single IRC channel #indiewebcamp<\/span> (no email list\u00b2<\/a>) because it was tightly coupled to IndieWebCamp events, which were both highly technical and yet focused on actually making things work on your personal site that you need\u00b3<\/a>, that you will use\u2074<\/a> yourself. Conversations bridged real world use-cases and technical details.
It only took us five years after the first IndieWebCamp in Portland to recognize that the community had grown beyond the events, and had a clear need for a separate place for deep discussions of developer topics.
As part of renaming the community from IndieWebCamp to IndieWeb\u2075<\/a>, we created the #indieweb-dev<\/span> (dev) channel for such technical topics like protocols, formats, tools, coding libraries, APIs, and any other acronyms or jargon.
The community did a good job of keeping technical topics in the dev channel, and encouraging new folks in the main #indieweb<\/span> channel who started technical conversations to continue them in the dev channel.
Still, it was too easy for user-centric topics to veer into technical territory. It often felt more natural to continue such threads in the channel it started rather than break to another channel. It was also a constant bit of community labor to nudge developer conversations to the developer chat channel.
We had already started documenting IndieWeb related jargon\u2076<\/a> on the wiki and turned it into a MediaWiki Category so we could tag individual pages as jargon and have them automatically show-up in a list. Soon after, @aaronparecki.com<\/a> (@aaronpk@aaronparecki.com<\/a>) added a heuristic to the friendly channel bot Loqi to recognize when people started using jargon in the main IndieWeb chat channel and nudge\u2077<\/a> them to the development channel.
Having Loqi do some of the gentle nudging has helped, though it\u2018s still quite easy for even the experienced folks in the community to get drawn into a developer conversation on main as it were.
We\u2019ve documented both a summary and lengthier descriptions of channel purposes\u2078<\/a> which help us remind each other, as well as provide a guide to newcomers.
Both experienced community members and newcomers share much of the user-centric focus of the IndieWeb, the IndieWeb being for everyone\u2079<\/a>, whether developer, hobbyist, or someone who wants an independent presence on the web without bothering with technical details. Whether some of us want to code or not, we all want to use our IndieWeb sites to express ourselves on the web, to use our sites instead of depending on social media silos. That shared purpose keeps us focused.
It takes a community to keep a community healthy and welcoming to newcomers. Eternal community vigilance is the price of being user-centric and welcoming to newcomers.
The ideas behind this post were originally shared in the IndieWeb meta chat channel.\u00b9\u2070<\/a>
This is post 8 of #100PostsOfIndieWeb<\/span>. #100Posts<\/span>
\u2190 https:\/\/tantek.com\/2024\/033\/t1\/earthquake-sanfrancisco-shifted<\/a>
\u2192 \ud83d\udd2e
Post glossary:
development channel (indieweb-dev)
\u00a0 https:\/\/indieweb.org\/discuss#dev<\/a>
format
\u00a0 https:\/\/indieweb.org\/format<\/a>
IndieWeb
\u00a0 https:\/\/indieweb.org\/IndieWeb<\/a>
IndieWebCamp
\u00a0 https:\/\/indieweb.org\/IndieWebCamp<\/a>
jargon
\u00a0 https:\/\/indieweb.org\/jargon<\/a>
Loqi
\u00a0 https:\/\/indieweb.org\/Loqi<\/a>
main IndieWeb chat channel (on main)
\u00a0 https:\/\/indieweb.org\/discuss#indieweb<\/a>
meta chat channel
\u00a0 https:\/\/indieweb.org\/discuss#meta<\/a>
MediaWiki Category
\u00a0 https:\/\/www.mediawiki.org\/wiki\/Project:Categories<\/a>
plumbing
\u00a0 https:\/\/indieweb.org\/plumbing<\/a>
protocol
\u00a0 https:\/\/indieweb.org\/protocol<\/a>
tools
\u00a0 https:\/\/indieweb.org\/tools<\/a>
social media silos
\u00a0 https:\/\/indieweb.org\/silos<\/a>
\u00b9<\/a> https:\/\/www.paulgraham.com\/trolls.html<\/a>
\u00b2<\/a> https:\/\/indieweb.org\/discuss#Email<\/a>
\u00b3<\/a> https:\/\/indieweb.org\/make_what_you_need<\/a>
\u2074<\/a> https:\/\/indieweb.org\/use_what_you_make<\/a>
\u2075<\/a> https:\/\/indieweb.org\/rename_to_IndieWeb<\/a>
\u2076<\/a> https:\/\/indieweb.org\/jargon<\/a>
\u2077<\/a> https:\/\/indieweb.org\/Category:jargon#Loqi_Nudge<\/a>
\u2078<\/a> https:\/\/indieweb.org\/discuss#Chat_Channels_Purposes<\/a>
\u2079<\/a> https:\/\/tantek.com\/2024\/026\/t3\/indieweb-for-everyone-internet-of-people<\/a>
\u00b9\u2070<\/a> https:\/\/chat.indieweb.org\/meta\/2024-01-22#t1705883690759800<\/a>","url":"https:\/\/tantek.com\/2024\/035\/t1\/gresham-law-developers-users-jargon","status_net":{"notice_id":116165},"tags":[{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"100posts"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"100postsofindieweb"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"discord"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"hackernews"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"indieweb"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"indiewebcamp"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"indiewebdev"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"jargon"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"matrix"},{"objectType":"http:\/\/activityschema.org\/object\/hashtag","displayName":"slack"}]},"to":[{"objectType":"http:\/\/activitystrea.ms\/schema\/1.0\/collection","id":"http:\/\/activityschema.org\/collection\/public"}],"status_net":{"conversation":"tag:status.blaise.ca,2024-02-05:objectType=thread:nonce=be23603d82853ed2","notice_info":{"local_id":"116165","source":"ostatus"}},"published":"2024-02-04T23:05:00+00:00","provider":{"objectType":"service","displayName":"stadeus","url":"http:\/\/status.blaise.ca\/"},"verb":"post","url":"https:\/\/tantek.com\/2024\/035\/t1\/gresham-law-developers-users-jargon"},{"actor":{"id":"http:\/\/tantek.com\/","displayName":"Tantek","status_net":{"avatarLinks":[{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-profile.png","rel":"avatar","type":"image\/png","width":96,"height":96},{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-stream.png","rel":"avatar","type":"image\/png","width":48,"height":48},{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-mini.png","rel":"avatar","type":"image\/png","width":24,"height":24}],"profile_info":{"local_id":"207"}},"image":{"url":"https:\/\/status.blaise.ca\/theme\/neo-gnu\/default-avatar-profile.png","rel":"avatar","type":"image\/png","width":96,"height":96},"objectType":"person","url":"http:\/\/tantek.com\/","portablecontacts_net":{"displayName":"Tantek","addresses":{"formatted":"\nSan Francisco, CA\n"}}},"content":"I felt the #earthquake<\/span> here in #SanFrancisco<\/span>. A single quick sharp jolt with rapid decay, duration less than 2s, meaning it was relatively nearby and small in magnitude
I was about to say, perhaps #earthquakes<\/span> are the last use-case for #Twitter<\/span> because yes I reflexively checked it and did see posts about it from folks, including a few friends.
Then I checked https:\/\/indieweb.social\/tags\/earthquake<\/a> and it has plenty of recent #fediverse<\/span> posts about the earthquake, several @sfba.social<\/a>.
Feels like something big has shifted.
The #federated<\/span> #IndieWeb<\/span> has replaced another #socialMedia<\/span> silo use-case.
This is post 7 of #100PostsOfIndieWeb<\/span>. #100Posts<\/span>
\u2190 https:\/\/tantek.com\/2024\/027\/t1\/indieweb-ideals-systems-swappable<\/a>
\u2192 \ud83d\udd2e
Post glossary:
silo
\u00a0 https:\/\/indieweb.org\/silo<\/a>
social media
\u00a0 https:\/\/indieweb.org\/social_media<\/a>
use-case
\u00a0 https:\/\/indieweb.org\/use_case<\/a>","generator":{"id":"tag:status.net,2009:notice-source:ostatus","objectType":"application","status_net":{"source_code":"ostatus"}},"id":"https:\/\/tantek.com\/2024\/033\/t1\/earthquake-sanfrancisco-shifted","object":{"id":"https:\/\/tantek.com\/2024\/033\/t1\/earthquake-sanfrancisco-shifted","objectType":"note","content":"I felt the #earthquake<\/span> here in #SanFrancisco<\/span>. A single quick sharp jolt with rapid decay, duration less than 2s, meaning it was relatively nearby and small in magnitude
I was about to say, perhaps #earthquakes<\/span> are the last use-case for #Twitter<\/span> because yes I reflexively checked it and did see posts about it from folks, including a few friends.
Then I checked https:\/\/indieweb.social\/tags\/earthquake<\/a> and it has plenty of recent #fediverse<\/span> posts about the earthquake, several @sfba.social<\/a>.
Feels like something big has shifted.
The #federated<\/span> #