post bug

[Silverthorn]

Now, why am I even bothering writing up a justification post? Whatever, here we go.

1) Java. The only place java runs on is on the irc-page. Debug-stuff. Local stuff that one can get when an application crashes (ON THEIR OWN COMPUTER). Now: I don't see a connection between that and a remote/server error. If you see one: Fine, then enlighten me! Ranting around might help you in putting some emotion into your posts but it doesn't help me. At all.

2) Error 500. Again. In case I wasn't clear before, take a look at this:

quickly drawn up, but illustrates the hierarchy fairly well (Click to View)

Might've messed up the order of some of these but this is the general idea.

Any Member can access the top level, mods and admins the second as well. With FTP-access, you can mess with various php-scripts etc. The database lies beneath, allowing one to deal with the life of this site; everything one posts in here. The server gives the basis to actually build a site such as LFE onto it. ANYTHING BENEATH IS NOT IN MY PERMISSION RANGE. Am I the CTO of alfahosting? No, I am not able to manage the sites of my (paying) clients from bottom-up. Do I have access to the logs stored somewhere on a separate part of the server? No. Can I look into it thus? No. Can I fix it? No. Is the server standing in my room? No. Can I actually get ahold of what the server is doing right now? You know the answer: no.
Again, Error 500 says that the server itself encountered an error. "500" is the most generic error-code in that matter, it plainly says "We have a problem.". And, once again, I HAVE NO INFLUENCE AS TO HOW TO FIX IT. This is the job of alfahosting's technical personal, to keep the server running 24/7.

3) MyBB is the harbor for anything forum-related. This is not forum-related, this is hardware-related. And if you don't have a cluster of servers that are being able to jump in whenever one throws an error (that, of course has its price), you will inevitably encounter such problems. Fine, kick some technical assistant into their elongated back, they can't prevent a statistically RANDOM EVENT happening from one second to the other. These "code-parts", as you call them, are entirely unrelated to it.

4) Regarding the issue of not being able to recover the data once submitted (after such an error, that is), it is technically possible to add a feature which will back-up your post-data every X-seconds. However, MH has once mentioned that we're running at pretty much the limit of data-transfer; and such scripts can be pretty server- and traffic-intensive. Therefore, I cannot guarantee if this feature will ever be implemented under the present circumstances.

Hope I was clearer this time. If you have anything constructive to say, say it. If you want to take a piss into somebody else's cornflakes, go to a restroom instead.