I'm Michael. Over the past few months, my wife and I have been working on a project that we're excited to share with you all. It's a chess game that we've built from the ground up.
A couple of years ago, I developed a keen interest in chess. However, I found that I didn't particularly enjoy playing against other humans. The anxiety was just too much for me. Instead, I found myself gravitating towards playing against chess bots.
This led us to the idea for our game. We wanted to create a chess game where you could play against a bot, but with an added twist. We wanted to incorporate an element of conversation into the game.
The way we've achieved this is by using the OpenAI API to act as various characters and provide commentary as the game progresses and 'injecting' the game state into the conversation prompt. This allows the bot to have a deeper understanding of the current state of the chess game, and it can then comment on it.
All the character avatars were created in Midjourney.
We're really excited about this project and we hope you'll enjoy it as much as we've enjoyed creating it. We're looking forward to hearing your feedback and thoughts.
Just released https://www.chesswith.ai today. It's a basic chess app, but it lets you play against hundreds of famous historic/fictional characters.
The in game dialogue is powered by OpenAI's ChatGPT API. This dialogue is always unique and tailored to the events happening on the board, making every game a one-of-a-kind experience.
Not only is a problem that deleting a bucket costs money, but if you have a big bucket with many deeply nested files, it can take a really long time to clean it up using the AWS command line.
I ran into this with a bucket full of EMR log files a few years ago and had to figure out some pretty crazy command line hackiness, plus running on a EC2 machine with lots of cores to figure it out. This a write-up I did if anyone else ever runs into this issue.
These days the "easy" way to delete a bucket of a billion tiny files is to configure a very short-term expiration rule on the bucket, and let AWS itself delete all your files as they expire.
When we did this (a few years ago) it still took several days for it to remove all the files.
I believe the nesting shouldn’t affect it. When you’re iterating over objects to delete them, you can just iterate over the keys and ignore nesting—I believe that’s how the s3 tools do “recursive” deleting. The underlying S3 API provides a recursive interface (the “delimiter” parameter) but keys are really just string keys, and directories are illusory.
But yes, it can take a while to iterate through the objects.
It won't effect it, because there is no concept of nesting in an object storage engine like S3. Everything is a flat key that references an object, but we just abstract and conceptualize a directory structure because it makes it easier for us to manage our data.
But in reality you just have a really, really long list of keys and a big, flat file system of objects.
Yup, similar experience.
Our devs kept using S3 as a caching backend for some small pictures. Only based on billing, we learned that we had over 17TB in tiny files, unable to groom it in any way that was feasible. Kept hitting all sorts of api limits.
How you carry and present yourself does matter in life, regardless of whether or not think it should. It says something about you, and people infer things about you based upon it. If you don't come to terms with that early on then you're holding yourself back for no reason.
Small thing, you have a typo in the page header. Potencial should be spelled Potential.