this post was submitted on 14 Jan 2026
346 points (95.3% liked)
Technology
78661 readers
3830 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Thatβs because you went to Lemmy.world/digg.com π
OP has done something weird with the comment because for me the link comes to lemmy.dbzer0.com/digg.com - both of you have LW home instances so the URL is incorrectly being parsed as an instance link?
I think it loads a community named digg(dot)com on your local instance
Edit: could be a Voyager (mis)feature?
Edit 2: Jerboa doesn't even react when clicking that link
The raw comment is this:
[Digg.com](digg.com) didn't load for me, good start πIt's missing the
https://protocol, so the link is assumed to be relative to the current page you're on. It should have been formatted as[Digg.com](https://digg.com/)and then it'll look like: Digg.comLooks like this is a feature for most markdown parsers. In piefed, the same thing happens. I wrote most of the customizations for parsing markdown, but nothing to create relative links like this except for footnotes. So, it must be the default behavior of the markdown library we are using.
You guys were right. Iβm on Voyager!