diff options
| author | Runxi Yu <me@runxiyu.org> | 2025-03-24 07:10:07 +0800 |
|---|---|---|
| committer | Runxi Yu <me@runxiyu.org> | 2025-03-24 07:10:07 +0800 |
| commit | d395230dccaad68365fcbcbffcf6e542675b21c7 (patch) | |
| tree | 7eb5bf06e28bf1f23fab0c15df805a370345f90a | |
| parent | README.md: Add known issue about Safari address families (diff) | |
| download | powxy-d395230dccaad68365fcbcbffcf6e542675b21c7.tar.gz powxy-d395230dccaad68365fcbcbffcf6e542675b21c7.tar.zst powxy-d395230dccaad68365fcbcbffcf6e542675b21c7.zip | |
README.md: Clarify hash algorithm selection issue
| -rw-r--r-- | README.md | 6 |
1 files changed, 4 insertions, 2 deletions
@@ -23,8 +23,10 @@ It may experience occasional outages. HTTP protocol. - Currently we round times to the nearest week for persistence, but this could cause issues if a user completes the challenge at the end of a rounded week. -- SHA-256 is actually a pretty bad choice for proof-of-work. We should use - something like bcrypt or scrypt or argon2. +- SHA-256 is actually a pretty bad choice for proof-of-work. I'm not sure what + what be a good solution though, it'd be nice to have something that's more + memory-hard, but password-based key derivation functions are too heavy + on the server. - Safari on iOS and iPadOS seem to unpredictably make their requests from different address families, which causes the challenge to fail. |