because rewriting the whole page can be annoying and you couldnt access the text without styling
also can change .html name, maybe that will get removed but it works atm.
still needs more tweaks and proper testing
i *think* the migration from previous version will work.
made the version to 0.1.0 because im sick of 0.0.10000 and this is kinda a big change.
close#334
option for lock reset and captcha reset, to pick what you want the lock mode and captcha mod to go back to at the end of the hour
also fix avuln in boardsettings where pph trigger/mode settings were not range checked
They were getting reset to their latest reply date, when a bumplocked thread should never have its
bump date reset to earlier than whatever the latest reply was when it was bumplocked, or the OP date
if all replies are deleted.
Still not accounting for bump limited thread (a uncommon edge case), and i think the simplest way to deal with that would
be set bumplocked:1 when its exceeded the board settings bump limit. More efficient, less work for me, and actually
serves a useful purpose because long threads could tell when they are bumplocked from going past bump limit.
The only decision then would be whether to set it permanently from that point forward, or only set it once,
so they could be unlocked by moderators if they want which would be an added side effect/feature of being able
to selectively unlock them.
wtf is this commit message, and the code for this section is a cluster fuck lmao
Previously early404 would match the threads with less than "early404Replies" BEFORE skipping and then deleting.
Which would be incorrect because then early404 would only be deleting a fraction of the posts with less than
early404Replies, rather than any thread with less than early404Replies past a certain fraction of the threadLimit
Bit of a stupid mistake, but this should fix it, if my interpretation of how early404 is supposed to work is correct.
***DO NOT USE***
This still has some issues and needs testing.
- needs updated nginx configs added, expects "TOR" in the x-country-code header under a separate vhost
- need to make sure bans work properly still
- need to implement system to prevent captcha ddos, since i cant just to IP ratelimit now
- im 99% sure post history of tor users is broken if viewed by non-global staff
- manual input ban form will also be broken for non-global staff
- could still use some improvement on the middleware having a little more complicated flor for tor users
But for the most part it works. Basically it will use the bypass id of a tor user as their "ip".
some random guy