Thread

🚨 only for reckless testers, this is not a release! help me find a reasonable proof of work limit by testing out this build of bitchat with proof of work for spam prevention (the same way bitcoin prevents spam btw). - download and install - go into a geohash chat - write something, see semicolon guy - turn on proof of work, notice the difficulty slider - write a few messages - increase difficulty, write a few messages πŸ“ report: device, max difficulty at what difficulty does it take your phone more than a few seconds to send a message? which device are you using? which operating system? comment below so I can gather some data. appreciate you 🫑 View quoted note β†’

Replies (37)

Yeah I think the big question is. What delay when sending a message is acceptable for UX. I don’t have an Android so I can’t test it on bitchat, but will work on implementing this in coolr. My guess is that a second or so would be fine. Especially if there some animated visual that indicates something is happening. It’s also worth people to understand yoyll probably only see others messages that are using the same threshold or lower since I assume the client is blocking any messages that are not meeting your set threshold.