Steven Bell :pci: on Nostr: So, the thing with your solution using boostCallback is it requires wallet holders ...
So, the thing with your solution using boostCallback is it requires wallet holders (you know, the ones that can create lightning invoices, which need a preimage to work) to support the boostCallback. You're willing to be a wallet holder is seems, so you can support it and generate invoices for the wallets you hold. But you're creating a solution in which all the other potential wallet holders have to now support boostCallback. They don't support keysend, why do you think they'll support this?
Published at
2024-12-07 22:52:46Event JSON
{
"id": "6f56525bb1682976ec7c2a7664dbf09775260d8a33c76235a67c4c3834794eb1",
"pubkey": "5020099b0d106f8433f87f9274bae9f98b66326206d852dcf16e15f94cd9711b",
"created_at": 1733611966,
"kind": 1,
"tags": [
[
"e",
"b37188cba2ce034052aaea35375f06a1fbb20110fcd29b8280050a394da4b4f9",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://podcastindex.social/users/StevenB/statuses/113613993843384961",
"activitypub"
]
],
"content": "So, the thing with your solution using boostCallback is it requires wallet holders (you know, the ones that can create lightning invoices, which need a preimage to work) to support the boostCallback. You're willing to be a wallet holder is seems, so you can support it and generate invoices for the wallets you hold. But you're creating a solution in which all the other potential wallet holders have to now support boostCallback. They don't support keysend, why do you think they'll support this?",
"sig": "533f1b23f0062d3f2615bc012a03da8c8c992d49882167fada17973beedee78e7b3793652fad9fb60f71dddf0b8e751a1081e9a380b9246709d6f9bbd48d58dd"
}