github : https://github.com/Heyuri/kokonotsuba
as of making this thread, me and one other anon are working on a fork to try and clean up most of this shit.
we are planing on making proper objects for board,thread,post data. this of course would simplify things for module creation and future proof the code base.
i believe the module system will be powerful hooked base system that will be able to change data mid pipe line with out messing with the underlying system.

for creating a post postRequest. it should look something like this.

	$postData = new postData();
	$postData->loadFromPostRequest();
	executeHook("preValidation", $postData); //can trigger a whole post fail based on IP ban or failed capcha moduel.
	if(!$postData->isValidPost()){  //inside module hooks. there would be a postValidation() in contrast to preValidation() to stop files with pizza

	}
        .....

i also want to remove a lot of crud that is scatted all over the place and make a proper pipeline.
the pipeline should look like.
start -> post received -> post validated -> post saved to db -> load threads from db based on board configs -> load post in threads -> redraw html files -> end

of course there might be slightly different pipelines for admin menus or live views, witch might consist of a module having special things drawn in the render, or remove validation.
output should be redirectable so its either stright from*.php or gets written to *.html with proper redirect code


lots of things are still a mystery and what i said may not even work or might need some slight changes.
the more experimental fork that aims on chaining a lot of the underlying system that me and anon are working on is right here https://github.com/nashikouen/kokonotsuba

please ask in this thread about things you don't understand!! we are happy to help you learn more about kokonotsuba.