# Not resolving .jl links if https://juliaregistries.github.io doesn't have it **URL:** \ **Category:** Meta Discussion\ **Created:** [January 11, 2026, 7:49am UTC](https://discourse.julialang.org/t/not-resolving-jl-links-if-https-juliaregistries-github-io-doesnt-have-it/134989 "2026-01-11T07:49:45Z")\ **Posts on this page:** 1\ **Showing post:** 2

**Author:** ![abraemer](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/abraemer/32/51403_2.png) [@abraemer](https://discourse.julialang.org/u/abraemer)\ **Post date:** [January 11, 2026, 10:40am UTC](https://discourse.julialang.org/t/not-resolving-jl-links-if-https-juliaregistries-github-io-doesnt-have-it/134989/2 "2026-01-11T10:40:56Z")

See previous thread for some more context about the current mechanism: > [@Automatic package links](https://discourse.julialang.org/t/automatic-package-links/106275/17): > > We’re now using these linkifiers on Zulip and it’s really nice. Thank you again for putting in the work to make these redirect pages @jules. @mbauman what do you think? Can we switch the Discourse linkifiers to use these redirect pages from the General Registry? I think this solution is a much better fit than the JuliaHub pages because it’s significantly faster to load Authors intend for people to visit their repos, and they have control over those repos, unlike the JuliaHub pages (i.e. if a … The problem is that discourse provides only quite basic tools. The linkification is done via regexes and these cannot perform additional logic to e.g. check whether the package actually exists in General. If anything, we could try to make the script that generates the redirects smarter somehow. Although I don’t see how it could divine the existence of some package that’s not registered in General. --- _[View the full topic](https://discourse.julialang.org/t/not-resolving-jl-links-if-https-juliaregistries-github-io-doesnt-have-it/134989)._