28
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 05 Aug 2026
28 points (96.7% liked)
Asklemmy
55903 readers
418 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 7 years ago
MODERATORS
I don't know how things are right now, but a couple of years ago I researched the topic and read that an instance.onion would have difficulties to properly federate with instances no .onion, which seems logical. It would be necessary to create a parallel lemmy only with .onion
Couldn't you have an instance that's accessible on .onion and not on .onion? The same way duckduckgo is accessible through both?
I believe there was some issue with this, at least I get to recall Nutomic discussing it in one of the GitHub issues
Yeah the code only accepts one domain AFAIK that it uses for federation and everything in the UI/API. So even if you could host it at .onion, links, images, in-browser API calls, etc would all serve from the public domain if you wanted federation. The code would need to be written to support alternative domain access with an authoritative domain for federation. In theory you could put some sort of proxy in front that just rewrote everything the server output to replace with .onion and then intercept every request to change the header so the server thought it was coming from the standard TLD, but that's incredibly fragile and a ton of work.