>>22960
Don't get me wrong, I'm glad that there's a non-JS option for it. I think if a site has a botspam problem, having a PoW checker is a much better solution than banning VPNs/Tor or (god forbid) using Cloudflare. However, I don't think this site has nearly enough traffic outside of /gacha/, /v/, and /vyt/ for a PoW checker to really be necessary, and it may be actively detrimental to participation as I described in
>>22907.
Anyway, if the PoW solver has to stay then the admin should make it easier to access and compile. It's really simple:
1) Link directly to a .zip of the PoWSolver git repo, allowing users to bypass the JS-required repo site.
2) Include simple instructions for compiling the PoWSolver from source, which the repo lacks.
It's nice that the solver's codebase is so simple that even a codelet like me can audit it. I think implementing these steps would increase transparency and avoid scaring off potential posters who care about FOSS, although I'm probably way overestimating the number of users who actually give a shit about this.
>>22960
What's L+JS?