[jgarber][tantek] Did some archaeology on that post and found the original was a reply to a post from Zach Leatherman. Formerly `zachleat` on Twitter, nowadays on Mastodon, etc. linked from his website: https://www.zachleat.com.
[jgarber]It's been four years, so hard to say with any precision, but what he asked about there also vaguely looks like a feature that landed in Eleventy where the tool may be configured to infer output URLs based on input file paths.
[jgarber]• a `rel="source"` without any containing microformat _could_ maybe be generically interpreted as the source for the page or the website as a whole
[jgarber]I don't have an example of the first one. For the second one, there's https://micromicro.cc which has an `h-x-app` on the body and a `rel="source"` link to the project's source code.
[jgarber]For the last bullet, most of the sites I've put together that use `rel="source"` are marked up that way (including the Refresh DC website which is cited on the wiki and was mentioned earlier).
[tantek]Our experience with h-entry and rel-tag showed that mixing of h-* microformats and rel microformats was very error prone (confusing to devs) so if there's really strong demand for such scoped use cases we need a u-* property for h-* scoping
[tantek]Also on that brainstorming page, "source" is too ambiguous/ overloaded (like info/news source like a citation) so for source *code* we need a more specific term. Or just code
[tantek]Yeah the Slack channel bookmarks feature showed up in the past year or so. I've experimented with it at work. Still not sure how useful it is bc the feature is a bit buried
[jgarber]Agreed, this wasn't quite what I thought it was going to be. I recall a version of this that let you add linked items directly to the bar that has "Messages," "Files," etc. Not sure if that's a paid feature or something that got changed. 🤔
[jgarber]"Forge" is another term I'm seeing in used to generically describe version control / code hosting services. That may be quite a bit more niche and isn't _quite_ the same as a "repository."
[jgarber]Suppose you could say the same thing about the Markdown file from which any of my blog posts is generated. I wouldn't generally refer to those files "code."
[tantek]Eg rel=code could link to a "view source" view of the current page content like the "View source" link you see on microformats or indieweb wiki pages when you're not logged in
[tantek]But my examples are exactly why "source" fails to convey a precise semantic that can be matched to a meaningful UI for the user in a link auto discovery implementation
[tantek]Because the goal here isn't to provide a random new rel value for punishers to quietly put in their code and feel good about. The point is to provide a hook for a useful UI for users
capjamesgI don't think rel=alternate applies when linking to source code because the view isn't just an alternate: it can and often does have additional information, too (i.e. a repo home often shows a README, license information, contributors).
[jgarber] [tantek] Did some archaeology on that post and found the original was a reply to a post from Zach Leatherman. Formerly `zachleat` on Twitter, nowadays on Mastodon, etc. linked from his website: https://www.zachleat.com.
[tantek] [jgarber] see my current brainstorm here: https://chat.indieweb.org/dev/2025-05-25#t1748200026257300 (and some back scroll there has some breadcrumbs)
tantek edited /source-code-brainstorming (+664) "add summary of brainstorm alternatives from before this year" (view diff)