Posts by mordauk

Hmm, I’m looking at mine fine.

Since I posted on that thread before it was closed, I’m getting notices of new replies added by moderators (that’s how I know what they’re doing).

They calling in one of the main devs right now to look at everything.

P.S. Hatred and yelling gets no one anywhere in life. Just my two cents.

KingDog temporary hid it until he can talk to support. It was “censored” because it posted potential security threats to Envato, which are much better handled by sending them directly to support, instead of publicly exposing them.

That’s awesome! Congrats!

Thecodingdude said

mordauk said

Thecodingdude said

mordauk said
I’d like to point out that it was as much a fault of aMember (the software used to run Tuts+) as it was Envato, yet NO ONE is yelling at them. Seriously? Amember is one of the largest and most widely used membership softwares on the net. It was definitely very, very negligent of Envato to not fix the issue sooner, but if you’re going to yell at someone, yell at both of them.

Envato must make over $500,000 every month. I’m pretty damn sure a company like Envato can afford to have every single line in their code examined for security, performance etc. Envato knew about this bug since last year.

I never said they shouldn’t have or could not have. I was simply pointing out that making the move is very difficult.

Envato patched the issue within 48 hours, don’t give me bullshit about it being difficult. Yeah, it is when you’ve got an entire team of useless “developers”.

Envato have had over 6 months to patch the issue, instead they wait for the breach to happen and then update it – do you see the logic because I certainly don’t?

Dude, not trying to start a war. Just because it can be done in 48 hours does not mean it isn’t extremely difficult. They have a large development team with a ton of skill. It’s obvious they can (they did) do it.

Anyhow, I NEVER said it shouldn’t have happened a long time ago.

And please, come on, don’t call Envato developers useless. Not fixing the security breach was a mistake higher up. If it wasn’t for the fantastic Envato devs, we wouldn’t have these great marketplaces.

GravityDept said
Uptime reporting isn’t a deal breaker, but I’m effectively paying Envato four figures every month to keep the marketplaces up. I’d like to know they’re doing that so we can both earn more.

How is it you’re paying Envato four figures?

Congrats

I’m inclined to agree with Jonathan.

Thecodingdude said

mordauk said
I’d like to point out that it was as much a fault of aMember (the software used to run Tuts+) as it was Envato, yet NO ONE is yelling at them. Seriously? Amember is one of the largest and most widely used membership softwares on the net. It was definitely very, very negligent of Envato to not fix the issue sooner, but if you’re going to yell at someone, yell at both of them.

Envato must make over $500,000 every month. I’m pretty damn sure a company like Envato can afford to have every single line in their code examined for security, performance etc. Envato knew about this bug since last year.

I never said they shouldn’t have or could not have. I was simply pointing out that making the move is very difficult.

mordauk said
Yes, I agree that they should have, but I can also tell you that moving away from amember is a serious pain. I’ve had to do it before and it is excruciatingly difficult.

Oh, and that’s not to say that it being a serious pain is a good enough reason to not do it, because that’s definitely not the case.