900 karma · joined June 6, 2011
I was working on a similar idea a couple of years ago but got hung up on the scraping step after realising google api restrictions were too onerous.
I was trying to come up with a way that would have the videos scraped by the user and then randomised, entirely client side.
Excited to hear that some AI stuff is going to be brought over, currently do a lot of switching back and forth with ChatGPT, and having your database schema automatically be part of the prompt would be great.
I'm guessing visualisation stuff is going to stay part of the paid offering?
M1 macbook pro, Arc browser
Being able to try a service "risk free" seems really important. To start replying to emails in a new service and then lose them if it doesn't work out doesn't sound like a reasonable option.
There's also a really neat solution that involves a matrix of wires, one for each row and column, and then running a current through the wires. The pieces then each interact with the current in a unique way producing a signal. You then do some clever stuff to figure out all the pieces that are on a given wire. Cheaper than RFID, and you don't need a sensor for each square and can do some multiplexing. I think it possibly uses magnets in the pieces? You can tell electronics is my strong point!
My only comment is that it feels like there are too many items for the amount of inventory space.
There will be rooms completely littered with boots that you just walk past. Every time you see something interesting like a potion you have to first chuck away a pair of boots before you can pick it up and drink it.
The solution I ended up with was to build my own pseudo-idempotency around Postmark. It helps that Postmark at least has proper persistence so you can query their API to check if you've already sent a certain email. I had to move away from Mailchimp because, if an email gets queued for some reason, it isn't reflected as sent in the API so there's no way of knowing whether an email is hiding in "queued limbo". Postmark doesn't have this problem.
The only caveat is that there is a delay between sending an email and it being reflected in the API (seems pretty standard across the different services). This means I had to implement a simple database backed lock to make sure I never try to send the same email more than once in quick succession.
It's kind of ridiculous, but.. I couldn't find any alternative.
Edit:
Wonder if it would be worth wrapping something like this up into some kind of a self-hostable proxy service. You'd provide the idempotency key in a header and it would do the rest