Shapes Inc founders committed the cardinal sin of mass emailing by CCing

Shapes Inc founders committed the cardinal sin of mass emailing by CCing(twitter.com)

3 points by matthewsh 180 days ago | 3 comments

matthewsh 180 days ago |

First submission to HN so could be the wrong kind of post, but I find it interesting that a platform that has had presumably millions in investments, boosts 30 million users (based on one of the founder's personal websites), and has dedicated engineers and staff can't be bothered to do the basics of ensuring marketing emails are sent out safely.

There's other posts about it on X, but they don't blur out emails so I won't share.

BoorishBears 180 days ago | |

Well this is the platform that got kicked off Discord for refusing to delete user accounts in a timely manner, then training an AI model on user inputs...

Then tried to weaponize their userbase to mass email Discord over being kicked off.

matthewsh 180 days ago | | |

And then struggled to manage Reddit...then scaled to as many platforms as possible (text, whatsapp, etc) then shut it all down then built out an entire API just to shut it down (apparently, can't confirm). They can't even get dark mode to work by default on their own website. Suspended from Twitter/X. Founder, Anush, making comments about "replacing engineers with AI" (source: https://x.com/anushkmittal/status/1979372588850884724), although that could be a joke, using their absolute dogshit "talk" platform.

And speaking of their chat platform...it's literally horrible. Slow to load, terrible UX, disjointed UI, no accessibility options, AI chatbots everywhere and you can't even tell their AI without clicking their profiles. It's like if Slack was made by a 12 year old.

Seriously, to put it in perspective I'm on a MacBook Pro M3 (so not that old) and a fiber, gigabit network. I click one chat and it can take up to 5 seconds to load the channel. JUST TO LOAD THE CHANNEL. It legit fires off like 30 fetch requests each time you load a channel. It's insane. I can't even blame NextJS for that, it's straight up them probably "vibe coding" everything.