aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRunxi Yu <me@runxiyu.org>2025-03-25 08:06:57 +0800
committerRunxi Yu <me@runxiyu.org>2025-03-25 08:06:57 +0800
commit895f750a56f37990e538de9ab98db13e45fd5166 (patch)
tree90a3289c5e121292a7ffce7bb23e4ea0cc05b86a
parentAdd Python challenge-solver script (diff)
downloadpowxy-895f750a56f37990e538de9ab98db13e45fd5166.tar.gz
powxy-895f750a56f37990e538de9ab98db13e45fd5166.tar.zst
powxy-895f750a56f37990e538de9ab98db13e45fd5166.zip
Update README to reflect the provision of a Python program
-rw-r--r--README.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/README.md b/README.md
index a9abcf4..de471cb 100644
--- a/README.md
+++ b/README.md
@@ -12,8 +12,8 @@ forges where scrapers do silly things like fetching each file in each commit
every hour.
Users that run JS and WASM will have their browsers solve the challenge
-automatically. Other users will need to solve the challenge externally; a C
-program is provided for this purpose.
+automatically. Other users will need to solve the challenge externally; C
+and Python programs are provided for this purpose.
It aims to be very easy to deploy, use, and maintain. The implementation is
rather minimal: there are no Go dependencies, no JavaScript dependencies, no
@@ -41,8 +41,8 @@ cookie to pass the validation.
JavaScript is provided to automatically solve the challenge without user
interaction; the current solver requires WebAssembly. Clients that do not run
-JavaScript need to solve the challenge externally, e.g. via the C program
-provided near the HTML form, and submit their nonce manually.
+JavaScript need to solve the challenge externally, e.g. via the C/Python
+program provided near the HTML form, and submit their nonce manually.
## To-do