"spark is not permissionless"
It's incrementally better than their previous Strike wallet, which was KYC, and they held your keys.
Do you think @primal won't migrate again to a fully trustless built-in wallet when such tech is available?
Once they do, people are going to be complaining that it's not perfectly private.
Paranoid people should sweep zaps to their own setup until #Nostr has reached utopia.
Whine or build. ๐จ
cc @miljan
View quoted note โ
Login to reply
Replies (2)
I'm not sure that we ever get self managed lightning's permissionlessness and privacy while simultaneously the ease of Spark.
We will likely iterate easier a bit, though in fairness the ease is already getting pretty easy compared to where it was even a year ago to handle your own channels with thing's like Zeus or Blixt having integrated nodes right on a phone. Tools for making selecting channels to open would help, and I think Zeus would benefit from replacing its use of Cashu with Spark for the LN address functionality (I for one have had stuck zaps...). But if you want always on zappability AND full sovereignty you need an always on node.
I'm happy to zap whoever proves me wrong there of course.
It seems like there is a constant tension between full control and UX/convenience
Had a tech bro chimp out at me that lightning is not easy enough to use but few have a solution between full unilateral control vs convenience. As youve stated i think it is a progression.