Sounds helpful.

For me the biggest concern is whether ppq can correlate my different chats as I can be conscious about privacy in one chat but if all my chats were correlated, it would instantly give away who I am, as in some chats I ask to help author nostr posts that then can clearly be matched to me. And the credit ID is where see a necessity in the current version for the client to send a linkable ID to the ppq servers. So how about instead of a creditID, use a built-in cashu wallet? Then you would still be able to match my chats from the IP address but the Android app could use TOR circuits per chat ...

Reply to this note

Please Login to reply.

Discussion

Yes. We've thought quite a bit about this option. I even had a call with nostr:nprofile1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcpzemhxue69uhks6tnwshxummnw3ezumrpdejz7qpq2rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sugh36r on it. Don't want to leave you hanging here, but we'll probably respond in a more long form brainstorming post here coming up soon.

I think it could be done without changes to the UI. So instead of a creditId and a hosted wallet, the wallet would be in the client. Now the over-payment issue you always have when you don't know how much the service will cost can be solved by returning eTokens with the server answer. Always charge the theoretical maximum of the model and with the reply, return change.

Only problem is the backup of that extra data but that could be encrypted using the "creditId" to stick with the same UI.