9 Commits

Author	SHA1	Message	Date
Thomas Lynch	521f9742c1	revert back to 2 thread max again because turns out firefox didnt get better, just tor limits to 1 thread anyway	2022-09-21 21:32:33 +10:00
Thomas Lynch	0af1a740ab	Make captcha submission automatic and not require clicking a "submit" form button	2022-09-18 01:41:02 +10:00
Thomas Lynch	207c3af05b	Patch some bugs in the updated challenge.js especially related to the fallback mode	2022-09-17 04:04:27 +10:00
Thomas Lynch	598790cb4f	- Fix some docker-compose issues close #14 ... - Move to new scheme with some hashing, sigs, and a random user key. close #13 - Change to sha256 rather than sha1 (temporary, but i guess its slightly more secure which is nice for now) ref #10 - Change POW output checked value - Add lib for randombytes, udpate lua sha lib - Remove outdated difficulty checks in frontend (was hardcoded 0 anyway) and since algo change is coming soon, there is no need to keep it	2022-09-17 02:45:27 +10:00
Thomas Lynch	c9e007639e	- Make the "checking your browser for robots" look more like cloudflare ... - Reduce the default concurrency of the frontend script to 2 threads because any higher seems to crash firefox (and its quick enough even with 2 threads anyway) - Remove the footerlogo from challenge and maintenance page, and update the link	2022-09-10 08:23:09 +10:00
Thomas Lynch	bc55ce5a93	reduce concurrency of client check again to max 4 thread	2021-12-01 13:54:21 +11:00
Thomas Lynch	54be416a39	add crypto.subtle check for lokinet and idiots using non-tor browser for .onion	2021-11-30 02:27:19 +11:00
Thomas Lynch	876d0835bc	change script threads to hardwareconcurrency/2 instead of -1, because it can still cause browsers to be sluggish or crash moreso on powerful machines	2021-11-27 01:02:37 +11:00
Thomas Lynch	bec6bddf40	close #4	2021-11-26 00:27:47 +11:00