Kwinten on Nostr: My first idea was that the client should be responsible for checking periodically if ...
My first idea was that the client should be responsible for checking periodically if payments are due and doing them. But now I think that it’s better if a server (zapplepay/zapplanner/recipient server is doing it). The zap events can be authored by a 3rd party while the subscription event is authored by the end-user once, at the start.
Published at
2023-10-26 06:18:39Event JSON
{
"id": "f6c5bbafa5d427dcf57708e759e13a57b5dc4918cecbc5b6e19681039938b1f9",
"pubkey": "8c3b267e9db6b0115498cc3efcd187d1474864940ae8ff977826b9d83d205877",
"created_at": 1698293919,
"kind": 1,
"tags": [
[
"e",
"b85b484613233ca480130e56aca4f832268eac79761bd838d958862473800a14"
],
[
"e",
"d938b6e2f3db9b4e163b4bd412fabe74f1f05e7e23f9fb368fe54eddceb7ba1c"
],
[
"p",
"e1ff3bfdd4e40315959b08b4fcc8245eaa514637e1d4ec2ae166b743341be1af"
],
[
"p",
"fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52"
]
],
"content": "My first idea was that the client should be responsible for checking periodically if payments are due and doing them. But now I think that it’s better if a server (zapplepay/zapplanner/recipient server is doing it). The zap events can be authored by a 3rd party while the subscription event is authored by the end-user once, at the start.",
"sig": "bb5235f3a04cbd1cf9c67f7279a736481da2c01ab8b0143e262e33dabf2b782ca5cf00b3e0891114cb4f6c228d4ab7cbb5c6e8f7ef4592a8e33d3b301b067cb4"
}
