• review e2ee device sync for wallets
  • allow anons to edit comments using invoice hash+hmac
  • improve error handling for wallets
  • improve internal and user-facing logging
How are you going to determine which anon user can edit? I'm intrigued.
reply
161 sats \ 4 replies \ @ek 11 Sep
When anons pay the invoice for a post or comment, we can give them a special string they can use to proof to us that they are the ones who created the item. It's not the preimage because any node on the route knows it, not only the author. So instead, we create a hmac based on the invoice hash. If an anon can give us this hmac on edit, it's a proof of authorship.
reply
100 sats \ 1 reply \ @ek 11 Sep
I have proofread this comment so many times to make sure I don't make my common mistake of writing "to proof" instead of "to prove" but I still did it.
reply
Yes but did you proveread it
reply
111 sats \ 1 reply \ @anon 11 Sep
deleted by author
reply
77 sats \ 0 replies \ @ek 11 Sep
anon fan service
reply