I don't agree. This way it is a) easier to onboard _receivers_, and b) stays open in the sense that _senders_ can send bitcoins by any app they want (including non-custodial of course).
>>This way it is a) easier to onboard _receivers_, and b) stays open in the sense that _senders_ can send bitcoins by any app they want (including non-custodial of course).
If I were to restate what I think you're saying: Twitter is implementing a tipping system that allows you pay using Strike _as_well_as additional non-custodial [and potentially non-kyc] lightning payment apps once a lightning channel is open.
I think that you're either dead wrong, or the non-Strike lightning payment option will be so convoluted that almost no one actually will actually use it. I will be happy to be proven wrong though.
Ok, I understand (a). Regarding (b) I guess I don't fully understand their implementation, but are you suggesting that any 3rd party app could implement the payments? I guess if any app or user can pull the twitter user's lightning address one can tip then yeah I guess so. So I guess they are just using "Strike" as an officially-supported app?
If I were to restate what I think you're saying: Twitter is implementing a tipping system that allows you pay using Strike _as_well_as additional non-custodial [and potentially non-kyc] lightning payment apps once a lightning channel is open.
I think that you're either dead wrong, or the non-Strike lightning payment option will be so convoluted that almost no one actually will actually use it. I will be happy to be proven wrong though.