-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Activate watchtower client by default #5344
Comments
Personally, I dont think we should activate it by default. It would mean that users who dont want to use watchtowers or users who dont even know about them will have backups continue to build up because the user would not know that they need to add the details of a tower to send the updates too. I think it should remain an opt-in feature. |
Agreed. Unless there's a possibility that, the backups start building only after the user adds the tower to send the updates to, it wouldn't make sense to activate WT client by default. |
Background
I think it would be useful if the watchtower client is enabled by default. More people should use watchtowers I feel; but them having to activate wtclient first makes it harder. Why not enable by default?
Your environment
lnd
commit=v0.12.1-betaSteps to reproduce
People try to connect to watchtower
People get error
watchtower not active
Expected behaviour
People try to connect to watchtower
Watchtower connects
Actual behaviour
Well I just said that ;).
The text was updated successfully, but these errors were encountered: