#31038: Multiple project trying to creating services & including Tor - make this easier? ------------------------------+-------------------------- Reporter: Diagon | Owner: (none) Type: enhancement | Status: new Priority: Medium | Component: Core Tor Version: Tor: unspecified | Severity: Normal Keywords: hidden_services | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: ------------------------------+-------------------------- I see multiple services, like [ricochet](https://github.com/ricochet- im/ricochet/), [onionshare](https://github.com/micahflee/onionshare), [onionize](https://github.com/nogoegst/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? -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/31038> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs