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
Ideally we wouldn't even need a startup delay, and could receive a signal from the router when it is ready to be used (which is what we do in the Bote Android app: the delay is short-circuited once the router is ready). In the meantime, we could probably make this configurable, but I don't really see many cases where that would be beneficial. The only one I can think of is in standalone mode, where you probably don't want any delay at all - in which case, we could just have the standalone WAR contain no delay, and the plugin WAR contain a delay. What is your use case?
On a busy router at the startup phase sometimes bote fails to startdue to the lack of tunnels.
In that case a plugin restart is needed cause otherwise bote hangs.
So the use case would be busy router on startup.
It would be great to have the startup delay to be configurable via i2pbote.config file
The text was updated successfully, but these errors were encountered: