Hello!
ok likes and retweets are cool, but how about this: lightning tip on nostr via bolt12 or lnurl. payer_note is the (signed?) nostr note_id and payer pubkey. lightning node publishes a confirmation-of-payment note for that pubkey. you can see total tips by accumulating these notes.
nostr-post, a [nostril](https://github.com/jb55/nostril) script to make a post with your EDITOR
```bash
#!/usr/bin/env bash
set -e
TMP=$(mktemp)
$EDITOR "$TMP"
if [ ! -f "$TMP" ]; then
printf "could not create temporary file\n" >&2
exit 1
fi
content="$(cat $TMP)"
re="^[[:space:]]*$"
if [[ "$content" =~ $re ]]; then
printf "note empty. aborting.\n" >&2
exit 2
fi
note=$(nostril "$@" --content "$content")
printf "relaying:\n" >&2
printf "$note\n"
<<<"$note" nostr-relay-note
printf "done.\n" >&2
rm -f "$TMP"
```
How I post to nostr from cli:
$ nostr-post --pow 20 --sec mykey -e reply_to -p notify_user
This opens up vim to compose a post, creates the post with nostril and and then relays it with websocat.
nostr-post is here: #[0]
PR reply emails to bitcoin didn't go through but work for other repos? There goes the main way I contributed to bitcoin reviews =/
The service could send you a lightning invoice in an encrypted DM if you're not registered. "Pay this invoice for 10 PoW notes". Pay invoice -> service starts working on sent notes. Maybe there could be a lightning invoice NIP where clients can integrate with lightning natively.
You could use this for threads that have PoW restricted replies
idea: pay for PoW over nostr:
Send note to a paid pow relay where you register your pubkey. The contents of this is a json-encoded unsigned note that you want PoW on.
Service decodes this note, does PoW, sends it back to relays encrypted. Client sees this, decrypts, checks it against the original note sent (that is encoded in the response for convenience), signs it, and broadcasts.
Cool, what are you thinking?
Hmm I guess the downside is that quote reboosts wouldn't have this data to render previews so I guess I'm back to square one and having just references and doing more work on the client side... bleh
If I do this I just make a distinct kind for reboost and quote reboots. Kind all the things why not? The less parsing the better imo
I think I might json serialize the note into a boost's content to avoid a an n-lookup after you fetch a timeline
Smart!
Hello!
Welcome!