Darknet support #22

New issue

Open

opened 2026-06-13 22:49:30 -04:00 by chipmunkmc · 0 comments

chipmunkmc commented

2026-06-13 22:49:30 -04:00

Owner

Currently, some chipmunk.land can be accessed via .onion services, however the way it's set up is not ideal, and I want to support other networks like I2P.

Tor is currently set up to use Unix sockets for http sites such that nginx fails to start before it (and tries to despite that).
I want to have I2P support via i2pd, which if I remember correctly cannot work with Unix sockets.
Should each service
- use a separate port/socket for each network?
- have a separate nginx server block for each network? (would change how the whole config is written, but relates to the next question)
- be able to distinguish between the networks, with either hardcoded IPs for each or some form of identifier (Tor circuit id? dunno)?

I'm inexperienced with this stuff, sorry.

Currently, some chipmunk.land can be accessed via .onion services, however the way it's set up is not ideal, and I want to support other networks like I2P. * Tor is currently set up to use Unix sockets for http sites such that nginx fails to start before it (and tries to despite that). * I want to have I2P support via `i2pd`, which if I remember correctly cannot work with Unix sockets. * Should each service * use a separate port/socket for each network? * have a separate nginx `server` block for each network? (would change how the whole config is written, but relates to the next question) * be able to distinguish between the networks, with either hardcoded IPs for each or some form of identifier (Tor circuit id? dunno)? I'm inexperienced with this stuff, sorry.

chipmunkmc added the

enhancement

label

2026-06-13 22:49:30 -04:00