like

Updated the auto-linking code^1 on my website last Sunday to handle a few more @-mention use-cases. In particular: * @-domains with dashes/hyphens like @sonja-weckenmann.de * @-@ with (some) Unicode alphabetic characters like @briansuda@loðfíll.is * @-domain-and-path for indicating @-mentions of silo profiles that don’t support @-@ syntax, like @flickr.com/people/tantek or @instagram.com/tantek I also dropped auto-linking of URLs with user:password “userinfo”, since they’ve been long abandoned and effectively deprecated because there’s fairly wide agreement that such basic HTTP authentication^2 was poorly designed and should not be used (and thus should not be linked). If you’re curious you can take a look at https://tantek.com/cassis.js, which has updated functions: * auto_link_re() — regular expression to recognize URLs, @-mentions, @-@, and footnotes to link * auto_link() — specifically the code to recognize different kinds of @-@ and @-mentions and link them properly to profiles, domains, and paths. This code is only live on my website (testing in production^3 as it were) for now, and you’re welcome to copy/paste to experiment with it. I plan to test it more over the coming weeks (or so) and when I feel it is sufficiently well tested, will update it on GitHub^4 as well. With this additional auto-linking functionality, I feel I have a fairly complete implementation of how to auto-link various URLs and @-mentions, and plan to write that up at least as a minimal “list of use-cases and how they should work” auto-linking specification. This (blog post) is my contribution to today’s #IndieWebCamp Brighton^5 #hackday! This was originally a project I wanted to complete during IndieWebCamp Nuremberg last October, however I was pre-occupied at the time with fixing other things.^6 #autolink #atmention #atmentions #atat #atatmention This is post 12 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/047/t1/indieweb-major-update-design → https://tantek.com/2024/072/t1/created-at-indiewebcamp-brighton ^1 https://tantek.com/cassis.js ^2 https://en.wikipedia.org/wiki/Basic_access_authentication ^3 https://indieweb.org/test_in_production ^4 https://tantek.com/github/cassis ^5 https://indieweb.org/2024/Brighton ^6 https://tantek.com/2023/302/t1/indiewebcamp-completed-projects – Tantek

Likes https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases.

Updated the auto-linking code^1 on my website last Sunday to handle a few more @-mention use-cases. In particular: * @-domains with dashes/hyphens like @sonja-weckenmann.de * @-@ with (some) Unicode alphabetic characters like @briansuda@loðfíll.is * @-domain-and-path for indicating @-mentions of silo profiles that don’t support @-@ syntax, like @flickr.com/people/tantek or @instagram.com/tantek I also dropped auto-linking of URLs with user:password "userinfo", since they’ve been long abandoned and effectively deprecated because there’s fairly wide agreement that such basic HTTP authentication^2 was poorly designed and should not be used (and thus should not be linked). If you’re curious you can take a look at https://tantek.com/cassis.js, which has updated functions: * auto_link_re() — regular expression to recognize URLs, @-mentions, @-@, and footnotes to link * auto_link() — specifically the code to recognize different kinds of @-@ and @-mentions and link them properly to profiles, domains, and paths. This code is only live on my website (testing in production^3 as it were) for now, and you’re welcome to copy/paste to experiment with it. I plan to test it more over the coming weeks (or so) and when I feel it is sufficiently well tested, will update it on GitHub^4 as well. With this additional auto-linking functionality, I feel I have a fairly complete implementation of how to auto-link various URLs and @-mentions, and plan to write that up at least as a minimal “list of use-cases and how they should work” auto-linking specification. This (blog post) is my contribution to today’s #IndieWebCamp Brighton^5 #hackday! This was originally a project I wanted to complete during IndieWebCamp Nuremberg last October, however I was pre-occupied at the time with fixing other things.^6 #autolink #atmention #atmentions #atat #atatmention This is post 12 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/047/t1/indieweb-major-update-design → https://tantek.com/2024/072/t1/created-at-indiewebcamp-brighton ^1 https://tantek.com/cassis.js ^2 https://en.wikipedia.org/wiki/Basic_access_authentication ^3 https://indieweb.org/test_in_production ^4 https://tantek.com/github/cassis ^5 https://indieweb.org/2024/Brighton ^6 https://tantek.com/2023/302/t1/indiewebcamp-completed-projects – Tantek
Standard
like

What I created while remotely participating at #IndieWebCamp Brighton 2024: wiki-gardened day 1’s 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^1. What to make at an IndieWebCamp^2 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 completed the night before. gRegor had archived all the IndieWebCamp Brighton Sessions Etherpads onto the wiki, linked from the Schedule page^3. gRegor had noted that he didn’t 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 (and some services) links to local wiki page links * fixed (some) typos With some help from @alexsirac.com (@alexture@todo.eu), 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 I point this out to provide an example of an IndieWeb Create Day project that is: * incremental on top of someone else’s 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 in #IndieWeb), 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 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, other #ActivityPub or #fediverse implementations, and even across #socialMedia silos), as well as how many implementations autolink plain text 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 * https://tantek.com/2023/014/t4/domain-first-federated-atmention * https://tantek.com/2023/018/t1/elevate-indieweb-above-silo * https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo * https://tantek.com/2023/109/t2/years-ago-first-federated-indieweb-thread #autoLink #atDomain #atPath #atMention #atMentions #atat #atAtMention 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 And read what other participants have blogged about their IndieWebCamp Brighton experience: * https://roobottom.com/articles/plugging-into-the-indieweb/ * https://adactio.com/journal/20968 * https://theadhocracy.co.uk/wrote/indiewebcamp-brighton-2024/ This is post 13 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases → 🔮 Glossary: Create Day https://indieweb.org/Create_Day IndieWebCamp Brighton 2024 https://indieweb.org/2024/Brighton References: ^1 https://indieweb.org/IndieWebCamps/Attending#Day_Two ^2 https://indieweb.org/what_to_make_at_IndieWebCamp ^3 https://indieweb.org/2024/Brighton/Schedule#Saturday – Tantek

Likes https://tantek.com/2024/072/t1/created-at-indiewebcamp-brighton.

What I created while remotely participating at #IndieWebCamp Brighton 2024: wiki-gardened day 1’s 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^1. What to make at an IndieWebCamp^2 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 completed the night before. gRegor had archived all the IndieWebCamp Brighton Sessions Etherpads onto the wiki, linked from the Schedule page^3. gRegor had noted that he didn’t 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 (and some services) links to local wiki page links * fixed (some) typos With some help from @alexsirac.com (@alexture@todo.eu), 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 I point this out to provide an example of an IndieWeb Create Day project that is: * incremental on top of someone else’s 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 in #IndieWeb), 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 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, other #ActivityPub or #fediverse implementations, and even across #socialMedia silos), as well as how many implementations autolink plain text 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 * https://tantek.com/2023/014/t4/domain-first-federated-atmention * https://tantek.com/2023/018/t1/elevate-indieweb-above-silo * https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo * https://tantek.com/2023/109/t2/years-ago-first-federated-indieweb-thread #autoLink #atDomain #atPath #atMention #atMentions #atat #atAtMention 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 And read what other participants have blogged about their IndieWebCamp Brighton experience: * https://roobottom.com/articles/plugging-into-the-indieweb/ * https://adactio.com/journal/20968 * https://theadhocracy.co.uk/wrote/indiewebcamp-brighton-2024/ This is post 13 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases → 🔮 Glossary: Create Day https://indieweb.org/Create_Day IndieWebCamp Brighton 2024 https://indieweb.org/2024/Brighton References: ^1 https://indieweb.org/IndieWebCamps/Attending#Day_Two ^2 https://indieweb.org/what_to_make_at_IndieWebCamp ^3 https://indieweb.org/2024/Brighton/Schedule#Saturday – Tantek
Standard