rameerez

Look at the commit history.

Out of 557 total commits in the repo, 510 have been done before the past 2 weeks. All those (minus 5 in 2023-2024) have been done on or before July 2022, months before ChatGPT had even launched.

Out of the 47 commits in the last 2 weeks, 26 were README updates / CI / docs. The remaining 21 commits are clearly cleanups, speedups, bugfixes, and tangential features like Blender import/export. Which leaves us with 505/557 commits (90%) if we're not generous --or 531/557 commits (95%) in the best case-- of non-AI commits to the repo.

OP clearly wrote most of the project by hand and has just been cleaning things up for public release the last couple weeks. Exactly as he disclosed in his comment.

Loads just fine?

It works just fine?

OP here. As others have said, it loads immediately for me (tested on desktop + on mobile data + incognito)

The entire site is cached + Cloudflare sits on top of everything. I just ran a couple performance tests under the current HN traffic (~120 concurrent visitors) and everything looks good, all loads under 1 second. The server is quite happy at an average load of 0.06 right now, not even close to start breaking a sweat.

Turns out you can get off the cloud and hit the frontpage of HN and your site will be alright.

I'm the thread OP – can confirm we're using Stripe Checkout and all CC processing happens in a fully-managed Stripe Checkout page.

We're not using any other API from Stripe other than that required to launch the hosted Checkout page.

I'm the OP of the Twitter thread – I've had the exact same experience: unrealistically low risk scores for most fraudulent transactions. There were plenty of red flags for each of them (400+ cards and 40+ names under one single IP, most payments got already flagged for credit card testing fraud early on before succeeding after many tries...) Even dumb heuristics would have blocked 90% of the fraudulent payments. I appreciate Stripe is fixing this quickly after making it public and refunding fees, but something is definitely wrong with their risk calculation algorithm.

Fixed! Thanks for the heads up. The cache was interfering with pagination in category pages.

Where?

Update – just fixed this!

Thanks for the heads up! It may be that the filtered query yields no results and I'm showing a blank page instead of a message. I need to add a nice info message like "No results – please remove some filters" or something along these lines to make it clearer.

Try with a common query word like "cat" – filters work fine for me with all models!

Search anything – the model selection filter is at the top right

Thanks! It's Ruby on Rails with some vanilla JS here and there when I need it.