Wait, your doing backups using mysqldump? *points and laughs*

Also yes that "security" justification is total crap.

But hey, the "leader" has spoken and is content to run a site that has *less* features than the original... so who am I to say anything?

Carry on.

Pescado, it is highly unlikely that every user would have "over 9000" PMs in thier inbox.  At MTS2 I am the person with the most PMs and I have some 4000 odd.  Like I said the vast majority have less than 5.  The point here is not neccesarily technical (although people seem to believe whatever you say blindly with no asking of whether it's actually true, and you admitted yourself that it doesn't really affect things).  The point is that you are applying your own "explanations" onto things to "justify" them with faulty logic.  Just becuase you *may* have run a mail server in the past really has little comparison with running a large site.  Some things apply, but you said yourself that mySQL is "my" thing and not yours - but somehow I am in the wrong when I point out the flaws in your argument?   If you wanna talk security, fine, but leave the actual technical database knowledge transfer to somebody who knows what they are talking about, please.

You said that utting the PM limit too high would affect the *entire* site and slow it down, but then you said it would only affect the PM inbox.  Which is it?  I know full well that a large PM inbox doesn't slow anything down other than, well, the PM inbox.  It has no effect on the other tables at all, especially not with good indexes and well written SQL code.  Using it as an excuse that it would slow everything down is, quite frankly, incorrect.

Instead of putting your draconian miniscule limits on everybody, you should have actually kept it at the levels they where at before - after all, this *is* supposed to be a clone and not another instance of Pescado-land.  Isn't it?

Ali, let me tell you this - reducing the PM inbox will have little to no impact on the site "speed".  What *wouild* is optimising the mySQL configuration parameters and having good database indexes, key buffers and so on.  Your "esteemed" leader really doesn't know much about all of that - but thats fine, his server, your site. 

If, however, you want some *actual* expertise, feel free to ask.  Otherwise, carry on.

Ummmm....


Come on Pescado, you know as well as I do that that statement is complete and utter BS.  More PMs only affects the size of the PM table itself.  It has absolutely zero bearing on the rest of the database or the site.  The only thing that more PMs could possibly slow down is the actual PM inbox listing itself.  The vast majority of members on MTS2 have less than 5, and all told the entire PM table is 412,657 rows.  Does it slow the site down? Nope.  Only if you have a very badly configured mySQL could this even *possibly* have an impact (and even then it's extremely limited)... and we both know that my mySQL skills are a hell of a lot better than yours. 

I don't mean to be difficult but using this as an "excuse" to have miniscule PM inboxes really doesn't fly.  I thought that this was going to be a clone of Insim and setting excessively small PM inbox sizes really isn't anything to do with that. Cutting back the limit really has no bearing on make the site faster - it's just something the so-called "leader" decided.

For creators, having such a small PM box (which is used for both sent and recieved messages) can make it very hard to organise things, or to allow them to be asked permission, etc for items.  You know, things that PMs are actually valuable to be used for and stored.  Putting your own artificially low limits (with a damn poor excuse of why to boot) isn't the best thing to do for this site.

You mean I have to put that stuff on my head?  But it tastes so good....

I am insane.

My hair stands up on end becuase of all the lunacy I have to deal with day in day out

Either that or I'm using the wrong shampoo... hrm....

The problem with file sharing such as eMule or Bittorrent is that 1. the person needs to have the software and 2. they are impatient.

It's one thing in a community of geeks (As we have on relicnews.com, another site I admin at), but when the majority of the community are people who *haven't* touched a p2p program in the past, you run into problems.