Exactly, my first thought was "Why in earth would anyone think that S3 was the right service to store millions of tiny ephemeral files?" and now it seems they have invented their own in-memory store instead of just using something like Redis. I also wonder what happens if their DIY thingy crashes, are the videos lost? Why not send to Kinesis or SQS in the first place?
From the article, individual video segments were 2-6 MB in size and SQS and Kinesis have a 1MB limit for individual records so they couldn’t have used either service directly. At least not without breaking their segments into even smaller chunks.
You're right, I didn't pay attention there. Still seems that there a many solutions better suited than S3. Probably a classic case of "We need an MVP fast, let's optimize later".
To be honest I have never used Cursor nor do I know their pricing, but isn't revenue kind of a stupid metric if you're just a frontend for a paid API? Like wouldn't almost all of this revenue just go through them towards OpenAI or Anthropic?
The only thing missing is replacing the head of the federal reserve bank with a mindless puppet so they stop standing in the way of success (inflation).
I just get downgraded to 2.5 Flash after like three prompts and can't seem to find an option to switch back. So much for "60 requests per minute are free".
It is a fungus that is harmless for humans, so I assume not that much. Of course it is always dangerous to artificially mess with an ecosystem. It has backfired more often than it has worked as intended when humans did that.
It probably varies based on item price and how obvious the issue is. I had two sub-$10 items arrive visibly broken recently and got refunds in under 5 minutes.
You have to call their bluff when they try to pull that, they don't want you to ship stuff back either. I got a full refund after a few back and forths of "are you sure you want to ship that back for a refund??".
reply