The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#41
|
|||
|
|||
Quote:
Quote:
|
#42
|
||||
|
||||
Quote:
Quote:
|
#43
|
|||
|
|||
Quote:
|
#44
|
||||
|
||||
Hmmm... Have worked on Unix/Linux based OSes for over 10 years and never had a problem with ZIP files. Always was able to uncompress without any external utilities or applications. This OSes include Solaris, HP/UX, and AIX among others.
Not making false assumptions, speaking on experience from almost 2 and a half decades of working with computers. |
#45
|
|||
|
|||
Quote:
You can't have it both ways. In one breath "it's not secrecy", and in another "bandwidth is just one consideration" and the admins clearly stated "cannot disclose the reason". And in one breath "Jelsoft has nothing to do with it" and in another "Jelsoft has to pay for the humongous bandwidth demand". Let alone the fact vb.org has gzip compression enabled. If you can't say the reason out loud, don't try to enterpret how companies allow or disallow internet access at work for employees, or how your Linux/Unix server is setup. The silliness of these excuses to avoid posting a single txt or xml files are more obvious than you think. I have ZIP on my home PC and can manage, I just resent all these new secret policies and changes coming up lately. |
#46
|
|||
|
|||
I don't see why this is a big deal, Just zip the files. As members of vB.org we should all trust both Erwin and Xenon that any new policy that is put into place is for the better of the community.
|
#47
|
|||
|
|||
Yeah, I wish those pesky dudes down at the United Nations would have done the same thing when Bush wanted to bomb Iraq to bits.
It would have been so much simpler if they would have just trusted America from the start. |
#48
|
|||
|
|||
Please don't tell me your comparing Xenon and Erwin to George Bush...please.
|
#49
|
|||
|
|||
Quote:
The thing is, many of us where using vB since 1.x and were used to a certain level of honesty and transperancy. Recent decisions by the team raised a lot of alarm bells in many of us. We used to release code on vbulletin.com before vbulletin.org was created. There was mutual respect, and clear understanding why things were done. Recently this has changed. Part of it is the loss of transperancy, and things are chasnged suddenly and you have to live it, and announcements are made after the dead is done. That's bad, but livable. Then, the worst IMHO, is that some of the changes were to addres the possibility that you and me may release code to maliciously explot other members, which I find very offensive (it's another thread), and the possibility that you or me may priate copies (possibly this thread), and I also find that offensive. As far as I'm concerned, ZIP is a trivial issue. The real issue is these excuses of "undisclose reasons", or the possibility of exploting or pirating. Granted, these thigns happen from a few members out of 10's or thousends, it's just wrong to make everyoen pay the price for such paranoia, and treat the whole community of developers in thsi way. So it's not the ZIP, it's a lot of little things here and there that signal bad things to come, which usually happens when you just accept such changes without even getting an honest answer for them. (bandwidth and employer work policies is not an honest reaosn IMHO) |
#50
|
||||
|
||||
Erwin already gave the answer, so please read his post.
|
Thread Tools | |
Display Modes | |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|