You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 13, 2017. It is now read-only.
I propose that you package a "client" version of Nightweb (Android or desktop) where you drop router.jar from the app and don't run your own I2P router. Instead, allow the user to specify an I2CP host:port of a remote router to connect to via SSL, and use that for communication.
This would allow users to run the I2P Android app separately (currently just an alpha) and use it for Nightweb as well as other potential client apps. Or they could use Nightweb on their phone connecting through an I2P router on their computer or a remote server.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I propose that you package a "client" version of Nightweb (Android or desktop) where you drop router.jar from the app and don't run your own I2P router. Instead, allow the user to specify an I2CP host:port of a remote router to connect to via SSL, and use that for communication.
This would allow users to run the I2P Android app separately (currently just an alpha) and use it for Nightweb as well as other potential client apps. Or they could use Nightweb on their phone connecting through an I2P router on their computer or a remote server.
The text was updated successfully, but these errors were encountered: