HN user

animeshjain

47 karma

indie dev making Chips of Fury - a private poker app

hi.kanily at g mail

Posts4
Comments28
View on HN

i am building https://alphacheck.ai on the side. it uses stock market data to track performance of recommendations made by youtubers.

What i have working as of now: - submit a video and get a snapshot of which stocks were mentioned, sentiment (buy/sell), price delta and reasoning. - analyze a channel and get a performance 'report card' of that channel

Zed is our office 8 months ago

I tried the collaborative features to pair program with a colleague a few months ago, but it was bad. It was very flaky in establishing a connection. In the cases we were able to establish a connection, the voice chat would not work. We tried to make it work for a couple of days, and then we gave up. Has there been lots of work in the past few months on the collaborative features?

I develop Chips of Fury, a poker app for playing privately with friends. Currently I am building support for lots of home game variations like pineapple (regular, crazy, lazy), different Holdem variations like Super, reverse, super reverse, blind man's bluff etc and many more. I am thinking about how to implement AI bots for a wide range of variations.

This is awesome. Want to just mention my experience trying to replicate sqlite here.

I host a multiplayer game on fly. The way I've designed it is, each game server has it's own sqlite database. And each fly server can host multiple game servers, to keep a high utilization. I currently use Litestream to replicate each database to s3 for disaster recovery. I am planning to move from S3 to sftp to save on the high post/put costs that s3 incurs (the actual storage costs are negligible).

I thought what I am doing would be more common place. But it seems that running single machine instances that can recover after a crash is not common after all (or atleast the tooling does not focus on that). Most use cases seem to be serving high availability or scalability.

In the unnecessary (IMO) desire to make everything highly available, I think simpler solutions have been over looked. I can't help but feel that if you need LiteFS, it is possible that you should be looking at a server oriented database like Postgres or Mysql. In that respect, I feel Litestream is underrated and deserves more attention. It serves a use case which is perhaps more in-line with an in-process DB :)

PS. this thread has some really interesting tools though (Marmot, mycelite). Great to see so many options.

From what I know, full text search in Postgres (and MySQL) does not have faceted search. So it only supports returning full text results from the entire index.

Actually, it is possible, but doing a search on a particular segment of rows is a very slow operation - say text search for all employees with name matching 'x', in organization id 'y'.

It is not able to utilise the index on organization id in this case, and it results in a full scan.

I was wondering if Materialize is meant to be used in analytical workloads only, or would it be equally up to the task for consumer app kind of workloads as well?

I agree, and would like to pay Google (would have already done so earlier), BUT, there is this gaping trust gap. I find it hard to trust that my account won't one day be randomly banned with no option to communicate with a human customer support agent.

Based on a cursory search, these bans are not so uncommon, and it is just scary

[1] https://news.ycombinator.com/item?id=24965432

[2] https://news.ycombinator.com/item?id=24791357

[3] https://news.ycombinator.com/item?id=23057365

[4] https://support.google.com/accounts/thread/5016170?hl=en

(edit for formatting)

There was a very cool resource (video, ebook) on how git works on a website called peepcode. I just realised they're no longer operational. It was by Scott Chacon I think. Can't find it anywhere else now. Would have made a good addition to the resources listed here.

Was pretty surprised that it cost you almost 250$ for a month to run this. Perhaps you could have tried hosting elsewhere. For eg. this would be easily acoomodated in AWS free tier I think. Could have given you a longer runway to iterate. Anyway, cool idea. Few hundred visitors a day is not bad!

this immediately made me think, don't the amazon API limits prevent one from making more than a few thousand calls an hour. Would be very interested to learn how you are countering that. I simply avoid doing anything with Amazon's product api just because of that reason.