Here is Lilu's file re-uploaded in a password protected shell...
sec.env.d508.rar - Solidfiles (
http://www.solidfiles.com/d/ae83bc9d65/)
Password: Orion999
---------- Post added at 08:23 AM ---------- Previous post was at 08:12 AM ----------
It's not the programmers fault (speaking as one myself), its all down to cost. You get what you pay for; and lets face it few of us on this forum pay a penny.
The hosters pay for the absolute minimum of work to implement only what is necessary. So if free users get a less than perfect experience, why should they care ?.
Thanks much for the reup!
Likewise, speaking as a programmer myself -- while I understand the logic of pay/premium services and their equivalents -- in this case, it is the programmers' fault (or you could say, by extension, it's management's fault). There's a forum thread that details the months of Peeje's admissions of glitches and problems (specifically with this error, and with slot-filled/locked/lost uploads, seconds after uploading), and hollow promises to have such fixed... which apparently never end up getting fixed.
Again, I understand the logic of premium vs. free business models, but in reality, the "free" still isn't really free. It's a business model of advertising predicated upon the principle of market saturation. In other words -- the "free" actually isn't free, and is paid by a user through either an eventual premium upgrade (which likely wouldn't come about had they not partaken of the initial "free" offering), or paid through subsequent degrees of advertising when he/she uploads to the site and shares it with others, (who then repeat and disseminate the process).
As such, if a company turns their noses up to the "lowly" free-bers, say goodbye to that company as a company -- their preliminary form of advertising and marketing disappears as the bulk of the user base is "forced" to turn to alternative services. And with that, their main supply channel of premium upgraders dries up, as well.
Anyway, just noting that, yes, I agree it's not the programmers' fault (per se), but rather management's fault. Regardless of such, however, if their desire is to grow and expand, it's poor business practice to have such frequent, continuous, and long-lasting bugs in a service (and it has been confirmed that the "All upload slots filled" is indeed a bug, and due in no part to actual server saturation). Whatever resource they're not able to keep up with (programmers, servers, etc.), they'd be better served to back down some of their services/features/storage space/etc. to at least provide a smooth running service, rather than over-promising and under-fulfilling.
But again, thanks much for the re-up!