Removing choice is fine, but people will want to know what number they'll get if they order right now. Even if you can't or won't show the next rock, show the next number.
windowshopping•1h ago
That's actually kinda hard, no?
Say the server has a counter. When you load the page, it's at 57, so it displays that you would be ordering #57. While you're looking at this, someone else loads the page - what number do you show them? If you show 57, then whoever orders first gets it and the other person gets a message "Sorry, not available. Want 58 instead?" but the same thing could then happen to them with #58, too – "Sorry, not available. Want 59 instead?"
So maybe instead you show the 2nd person counter+1, i.e. 58. And you show the 3rd person counter+2, i.e. 59. But what if #59 purchases but 57 and 58 don't? What do you show the NEXT person, 57 or 60?
I'm not saying it's intractable but it merits thought.
crobertsbmw•1h ago
Maybe just show the last purchased number? Then it’s a race to get your order in if you want the next sequential number.
inerte•1h ago
The solution is to hide deep into the Terms of Service "Duplicate numbers may occur. You reserve the right to be sued if you complain."
cloudmanager•1h ago
Exactly why we kept it simple. You find out your number when it ships.
defrost•44m ago
What guarantee is there against transit hash collisions?
When two rocks are ordered, several rocks arrive, some with no ID numbers, others with IDs that match previously issued rocks?
JKCalhoun•36m ago
Heads up: I purchased the first seven already.
guide42•1h ago
Like physical EtherRocks[0]. Do will also come with a digital certificate that can be transfered online?
What stack are you running? How do you guarantee sequential consistency of order numbers across your app server regions, cache layers and data lakehouse?
superconduct123•1h ago
Thanks for asking, we're using AWS Bedrock to handle all that
It's funny you ask, I had this exact idea back during the NFT craze. I have an unlimited supply of rocks thanks to the creek in my back yard. Well not unlimited, but there are more rocks back there than people willing to buy them as a joke.
firecall•1h ago
Congrats on the launch!
Small suggestion - work on the semantic structure and SEO.
It's all H1 Tags as far as the eye can see!
caust1c•1h ago
~That's a good way to launder money.~
Err, tumble money. Err, that's a good internet gag.
satisfice•59m ago
I need unnumbered rocks. Can you remove the numbering?
analog31•56m ago
What are you, some kind of quarry robber?
pipularpop•55m ago
What are your contingency plans if a hecto-billionaire suddenly orders 100 million rocks? Can you scale?
sexeriy237•34m ago
One order == one rock
JKCalhoun•38m ago
Curious, was rocks.ai not available?
danielodievich•24m ago
you guys are entirely too cool. I love it. Perfect commentary after a work day full of ai adjacent nonsense.
untrimmed•13m ago
What makes a $50 rock different from the one in my backyard?
Kerrick•1h ago
windowshopping•1h ago
Say the server has a counter. When you load the page, it's at 57, so it displays that you would be ordering #57. While you're looking at this, someone else loads the page - what number do you show them? If you show 57, then whoever orders first gets it and the other person gets a message "Sorry, not available. Want 58 instead?" but the same thing could then happen to them with #58, too – "Sorry, not available. Want 59 instead?"
So maybe instead you show the 2nd person counter+1, i.e. 58. And you show the 3rd person counter+2, i.e. 59. But what if #59 purchases but 57 and 58 don't? What do you show the NEXT person, 57 or 60?
I'm not saying it's intractable but it merits thought.
crobertsbmw•1h ago
inerte•1h ago
cloudmanager•1h ago
defrost•44m ago
When two rocks are ordered, several rocks arrive, some with no ID numbers, others with IDs that match previously issued rocks?
JKCalhoun•36m ago