pull down to refresh
0 sats \ 9 replies \ @k00b 26 May 2022 \ parent \ on: Daily discussion thread
If you use the same keys for your new node, lnurl-auth will still work.
No man, I am talking to shut down the node for good.
A routing node nowadays is getting crazy to maintain with all these force closures happening right now.
So my plan is to close it for good and use only Blixt, SBW, Breeze, Electrum as mobile/desktop LN nodes, with private channels. No more public node.
Yes I can use same keys from defunct node in Blixt, but I do not want all the shit history to bring into a fresh wallet app.
reply
Okay, I'll look more into "linking accounts" or changing auth methods. It might take me a couple weeks.
reply
I am not the only one in this situation. I am just a "noise" voice here for them.
reply
Why not keep the node a little longer. Its possible the channels that remain are in for the long run and gives you a solid foundation to build the node up again
reply
Agreed, many people have asked.
reply
I would love to link my two accounts on here, but I can see a complication would be in adding complexity in your WoT system.
reply
We should maybe distinguish between linking and merging. By linking I mean having multiple auth methods for an account.
It sounds like what you're describing is merging? Which to me means taking multiple accounts and making them one. This wouldn't be an issue for WoT but it would be a relative pain to implement.
reply
I guess I hadn't considered they are different. A merge might be a one-time manual process, where linking auth methods could be done to the resultant merged account so you can access the merged account with either auth. Ideally there would be a facility to add multiple lnauth methods, email and oauth methods to a single account. There wouldnt have been a need to merge multiple accounts if one account supported multiple auth methods.
reply
Agreed