Rob Reiss

I treat the refresh_token as a single-use token. When a new access_token is obtained, I store the new access_token and refresh_token in a central database. In a cloud server environment...

I treat the refresh_token as a single-use token, even though it has a 100-day lifespan. When a new access_token is obtained, the refresh_token should be replaced with the one returned...

My current work around for this is as follows: ```sql createdAt: datetime("createdAt", { mode: "date", fsp: 3 }) .default(sql`CURRENT_TIMESTAMP(3)`) .notNull(), updatedAt: datetime("updatedAt", { mode: "date", fsp: 3 }) .default(sql`CURRENT_TIMESTAMP(3) ON...

I fixed this in a new version if anyone is still interested. I also made the bot capable of playing multiple cards. The refreshed version uses XState 5 and is...