>>09165311
>is there a bump limit?
Not right now.
>what's the maximum number of pages a board can have?
Unlimited right now.
>how do you block a client ID?
There's no mechanism for this currently. By default every new post is created with a randomly generated clientID (for anonymity sake, but you can post using a static clientID by modifying config/config.json if you want). Deletion actions are done with the static client ID you can see on the homepage, which allows for the moderator-subscription mechanism.
>is there a way to save client and reuse it, aka static client ID?
Yep, in config/config.json change:
postPostRandomKey
and
postFileRandomKey
to false.
>client side locking sticking.
This is probably something that should happen. Going to what you said about page and bump limits, the next feature I want to implement is pruning and thread limits and stuff, which I've been considering how to go about in the best way for a little while. I think you're right that stickying or "keeping" a thread would be a good measure to prevent board-wiping spam type things if a threads-per-board limit was introduced.
>will you ever implement a captcha?
Personally I'm not interested in captchas and kind of hate captchas. They are going to become (if they aren't already) more of a burden to humans than robots at some point very soon anyway, as OCR is already a well established technoligy. That being said I want gladden to be flexible enough to support various validation systems in a plug-in type manner.
Based on what I've considered working on the precursors to this project and various discussions, I've come to think the main way to handle the "spam problem" in a p2p system is not by gating access to posting to verified individuals etc, but instead "filtering" the content to only show what you want and discarding/pruning/filtering what you consider to be the dross. Like an immune system protects an organism from germs, type of thing.
