pv make something bitcoiners want
It’s nontrivial afaik. Might’ve changed recently. Going to give it a shot I think and see where it lands.
It’s really nice for some of the toys I’ve made.
Just concerned about having a hard time finding the right deps.
Anyone building on https://deno.land/?
Thinking of porting https://github.com/huumn/booger over (at least) and building a client on https://alephjs.org/ or https://fresh.deno.dev/.
But I'm a little concerned things aren't "ready" yet ... and I'm just geeking out.
Not equally distributed, but 100% distributed.
We distribute what we've earned for the day to the top 21% of posters/commenters in proportion to how much they were favored and people that "zapped" those top posts/comments in proportion to how much and how early they zapped.
pv make something bitcoiners want
You could. The k1 ends up being known to the wallet and anyone who can view the QR on your screen. Everywhere else is subject to tls.
I generate a random 32 byte k1 and set it to expire. That seemed good enough to me. More or less the security of a magic link.
That’s what I do. Client polls with the challenge seeing if it was signed. If so links to that client.
Yeah! I'll be around the lab working at least.
Yeah I'm signing it and everything ... just returning the wrong pubkey on the lnurl endpoint.
Is it still free if I zap you?
WoS/Alby have it right I think.
Yeah, npubs are bech32 encodings of the pubkey and are meant for user facing pubkeys.
In the protocol pubkeys are usually encoded as hex.
pv make something bitcoiners want
pv make something bitcoiners want
Should just be postgresql-12 based on the postgres website: https://www.postgresql.org/download/linux/debian/
I'm only really interested in the former. Hadn't considered charging *per* read or impression. Seems hard to measure given what you've said.
> Mostly curious the frequency, types, and shape of all the 'REQ' queries relays get.
>
> Nostr band dev was telling me the read ratios were like 10k read requests for every write.
Thanks! I wonder what the best way to approach query stats are. Naive thing would just be to record all queries then analyze periodically.
You mean receiving a bunch of pointless/extra/wasteful reads? Seems like something worthy of tracking