Ya' boi midsxeph here, comin' at 'cha with another 'dea. Y'all niggas best be ready for dis 1. It's comin' at ya' hard.

The script we're using, Kareha, is a perl server resource eating ancient piece of shit. I realize that when the BBS was made in 2010, there was still support and a very small community revolved around it. The times have changed. The script hasn't been updated by its maintainers since 16-Apr-2009, and the technology which it uses is very old. Today, in 2015, there are so many better image board script it baffles my mind. Wakaba, Kareha's brother, is just as old and the only main difference is how pages are indexed, updated, and inserted with SQL. Other than that, it's still a perl eating shit.

Let's take a look at some other scripts we could use which meet web standards. Firstly, there'sTinyboard. I'd say this should really just be a framework. It doesn't appear to be maintained, or contributed to. Another is vichan. Vichan is a fork of the famous Tinyboard with many additions. It is constantly updated by its maintainer and other contributors. Finally, we'll take a look at infinity. The infinity script is recommended by me. A reason is that users are able to create their own boards. In reality, it's just a much more complex version of vichan with that one huge addition. I feel like infinity would be great to use because people could make their own boards and be listed in a different place outside of the main board area we see on our left.


A main concern is how we go about transferring the current threads. It should be pretty easy to take the current threads and insert their information to the new image board script's database using whatever script.

Give some feedback. I'd love to know how everyone feels about this.

Or something in node.js, but I feel like it's way too far out there for Reltair. https://github.com/lalcmellkmal/doushio

>>1
We could have him use his server space and rework a new BBS using other methods and keep this around until it's fixed, then all important, active topics is recreated, but not copied over. This would clean it up, making it fresh without the added hassle of adding every topic over that we already have.

>>3 I would certainly be willing to help with the recreation. I think we should do that kind of stuff if we can.

>>4
If we can keep this current version until then, or have this current version as it's own sub-board under random after the fact, copying EVERY line of code for it, we probably won't mind having a new site. Either way a fix is in order.

>>5 https://github.com/techjanitor/kareha_convert
I found this. It's just for HTML. I haven't taken a really good look at any of the sources posted above.
I could try to convert that current script into HTML>SQL instead. Then, it could be imported with something like phpmyadmin or some shit.

Great ideas as usual.gonna bump this thread

^

=_=, seeing the update page, the guy who handle the site, Reltiar maybe, havent really update the site all that much, unless the update page itself is out of date, i dont think we get an grand update to this site for a while (unless the guy is doing it in secret)

^

I'm thinking about e-mailing Reltair. What does everyone think?

You might as well, and see what he thinks to do.

Nah, who cares. If the admin was losing money or the server was inefficient to the point of damaging the user experience because of Kareha then things'd change and we wouldn't need to suggest anything.