4 ms·

Was he the CTO as well? That’s who should really be fired (unless Matze hired the CTO in which case sack them both).

by koolba 6y ago

rahimnathwani 6y ago
It doesn't matter whether you hired someone or not. If they report to you it's your job to make them successful. Maybe you deserve some slack for the first 100 days, but after that it's irrelevant whether you hired them or inherited them from your predecessor.
0xy 6y ago
The incompetence is really astounding, politics aside. If they were behind Cloudflare or another DDoS protection website, you wouldn't even be able to tell they were an AWS customer at all. That coupled with their multi-million dollar monthly infrastructure bill and I'm scratching my head. The site seems like it was built by outsourced lowest bidder contractors and they scaled by throwing blank checks at the problem.
- hn_throwaway_99 6y ago
  > If they were behind Cloudflare or another DDoS protection website, you wouldn't even be able to tell they were an AWS customer at all. This is non-sensical. AWS certainly knew they were a customer, and they were the ones that kicked them off. Plus, Cloudflare has deplatformed other customers before, don't think they would have wanted to touch Parler either.
  - dilyevsky 6y ago
    Cloudflare fronts gab without issues afaik. I agree with parent comment that if they didn’t parade it so much they could get away with it
    - redisman 6y ago
      And the .win sites. But those seem to have taken their warning to moderate seriously
grensley 6y ago
Could you imagine being the CTO of this company, kind of cruising along in the modern integration focused environment? You need an email provider (looks like they used SendGrid) a 2FA provider (Twilio), hosting (AWS), apps (Apple, Google), internal chat (Slack), etc. Now imagine all of those services say "nah, you're done". All of the sudden you need to roll your own everything. You have millions of users and no access to fractional development of load balancing, crafting emails to avoid spam filter, best practices in 2FA, well organized chat permission systems. It's the true nightmare scenario for a modern company. If you say "they should have anticipated being de-platformed", well they probably never would have made it as far if they had focused on that.
- karmicthreat 6y ago
  The smarter move for the CTO might have been to get things going. Keep networking with other companies for a same level position and then peace out when it looks like things are going to blow up. At least you would have some reputation intact. Now he is just the guy that failed, couldn't recover and will have a hard time going anywhere.
- jorblumesea 6y ago
  I could imagine a stronger and more politically astute leader would have realized this and stalled for time. He could have done literally anything and it would have been better than what he did. Which was basically nothing. When the criticism came in he just pushed back like he was the one holding all the cards. Then everyone cut him off because he had no leverage. Completely predictable and poorly handled.
- gkoberger 6y ago
  Eh every similar platform, such as Gab, was "deplatformed" so it feels like they should have seen it coming.
  - judge2020 6y ago
    Exactly, the story of Parler sounds like it was just a trojan horse to ignite the 'deplatforming' debate on the world stage, or at least in the U.S. which is largely unique in the belief that you can say whatever you want without consequence (at least for a double-digit percentage of the population).
tyingq 6y ago
Their CTO's linkedin page says this: "A Linux system administrator with five years of system deployment and management work experience" Previous job included hyperscale things like: "Designed, managed, and maintained a commodity-based hardware platform with twelve supermicro servers" That's, uh, interesting.

Was he the CTO as well? That’s who should really be fired (unless Matze hired the CTO in which case sack them both).

by koolba 6y ago

Was he the CTO as well? That’s who should really be fired (unless Matze hired the CTO in which case sack them both).

It doesn't matter whether you hired someone or not. If they report to you it's your job to make them successful. Maybe you deserve some slack for the first 100 days, but after that it's irrelevant whether you hired them or inherited them from your predecessor.

0xy 6y ago

The incompetence is really astounding, politics aside. If they were behind Cloudflare or another DDoS protection website, you wouldn't even be able to tell they were an AWS customer at all. That coupled with their multi-million dollar monthly infrastructure bill and I'm scratching my head. The site seems like it was built by outsourced lowest bidder contractors and they scaled by throwing blank checks at the problem.

hn_throwaway_99 6y ago
> If they were behind Cloudflare or another DDoS protection website, you wouldn't even be able to tell they were an AWS customer at all. This is non-sensical. AWS certainly knew they were a customer, and they were the ones that kicked them off. Plus, Cloudflare has deplatformed other customers before, don't think they would have wanted to touch Parler either.
- dilyevsky 6y ago
  Cloudflare fronts gab without issues afaik. I agree with parent comment that if they didn’t parade it so much they could get away with it
  - redisman 6y ago
    And the .win sites. But those seem to have taken their warning to moderate seriously

grensley 6y ago

Could you imagine being the CTO of this company, kind of cruising along in the modern integration focused environment? You need an email provider (looks like they used SendGrid) a 2FA provider (Twilio), hosting (AWS), apps (Apple, Google), internal chat (Slack), etc. Now imagine all of those services say "nah, you're done". All of the sudden you need to roll your own everything. You have millions of users and no access to fractional development of load balancing, crafting emails to avoid spam filter, best practices in 2FA, well organized chat permission systems. It's the true nightmare scenario for a modern company. If you say "they should have anticipated being de-platformed", well they probably never would have made it as far if they had focused on that.

karmicthreat 6y ago
The smarter move for the CTO might have been to get things going. Keep networking with other companies for a same level position and then peace out when it looks like things are going to blow up. At least you would have some reputation intact. Now he is just the guy that failed, couldn't recover and will have a hard time going anywhere.
jorblumesea 6y ago
I could imagine a stronger and more politically astute leader would have realized this and stalled for time. He could have done literally anything and it would have been better than what he did. Which was basically nothing. When the criticism came in he just pushed back like he was the one holding all the cards. Then everyone cut him off because he had no leverage. Completely predictable and poorly handled.
gkoberger 6y ago
Eh every similar platform, such as Gab, was "deplatformed" so it feels like they should have seen it coming.
- judge2020 6y ago
  Exactly, the story of Parler sounds like it was just a trojan horse to ignite the 'deplatforming' debate on the world stage, or at least in the U.S. which is largely unique in the belief that you can say whatever you want without consequence (at least for a double-digit percentage of the population).

tyingq 6y ago

Their CTO's linkedin page says this: "A Linux system administrator with five years of system deployment and management work experience" Previous job included hyperscale things like: "Designed, managed, and maintained a commodity-based hardware platform with twelve supermicro servers" That's, uh, interesting.