Opened 13 months ago

Last modified 13 months ago

#31038 new enhancement

Multiple project trying to creating services & including Tor - make this easier?

Reported by: Diagon Owned by:
Priority: Medium Milestone:
Component: Core Tor Version: Tor: unspecified
Severity: Normal Keywords: hidden_services
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


I see multiple services, like [ricochet](, [onionshare](, [onionize](, and probably others, all creating services for Tor and including Tor with them, which: (1) causes them to become rapidly obsolete, (2) limits our ability to run Tor on one machine and the service on another and (3) results in multiple Tor services running.

In the interests of the development of the Tor ecosystem, and with the caveat that I am not much of a developer, wouldn't it make sense to have a simple Tor API, authenticated with a token generated by Tor, via which a new service may be offered/plugged in?

Child Tickets

Change History (1)

comment:1 Changed 13 months ago by Diagon

Never mind - I just discovered "ephemeral onion services". /Thx.

Note: See TracTickets for help on using tickets.