I’ve tried, but it’s not really effective in an application that is predominantly used on mobile.
Discussion
Why?
Guessing that significant “work” for phones is still too easy for bot servers?
Battery life too. But the filter would still be desireable for some clients. Iiuc, some relays already have a way to query prefix for event ids
Yes. Easy on servers, rough on phones. Amethyst used to show the PoW on posts (might still, I’m not on Android) but didn’t have a way to create them. Not sure if it’s been added. I’ve been iPhone for a while now.
Maybe we need a PoW provider market
User drafts message -> pressed add PoW -> user client sends message to PoWaaS -> PoWaaS sends back an LN invoice -> user’s client pays invoice -> PoWaaS sends back nonce
Be interesting to see how that could work without revealing your nsec, since that’s needed to perform the PoW.
I’m sure this can be done fairly safely self hosted though.
Why is nsec needed? Cant one just add PoW to the signed message?
The PoW is the number of leading zeros in the ID, so maybe not. Pow could be done, then signing could be done on device. Yeah, I guess that tracks.
Yeah, PoW can be built into the binary version of the npub (no nonce), or into a hash of any values. To prove we aren’t just reusing an old PoW i guess it should be a hash of the contents of the signed message. The PoW verification would work nicely into the signature verification flow.