Thanks! And it does actually. I basically set all messages prior to the 50 cent value being hit as free just to promote early engagement and prevent transaction failures (Stripe suggest $0.50 as a minimum). But generally speaking, their (online transaction) fees are 2.9% + $0.30 so there's solid headroom.
I've got lots of features on both the frontend and backend to prevent automated behavior that could be problematic. But ultimately nothing is stopping someone from throwing a random number into the payment modal to see if it works (though they'd still have to enter an email, zip, expiration, and CVV too).
All these exploits and we still can't get proper jailbreaks on new iOS versions :( I moved away from Android years ago in the interest of digital privacy so it's just wonderful to hear security isn't as tight as I'd hoped haha.. Then again I guess those like myself staying on the bleeding edge version-wise aren't affected.
I've seen a few videos with the audible whine heard from people's houses even super far away from these datacenters. Guess we'll see in a few years whether they were worth building in the first place or whether they end up abandoned once the bubble bursts.
These AI datacenters generally have invested quite a lot in Nvidia Chips and completely high end hardware by having DDR5 Chips etc.
And even more than that, the largest things for these things is how to supply enough water properly and water-cooling systems which aren't required in traditional systems.
They also are very conditional and spike the grid up and down with their use cases slowing the grid.
If the bubble bursts, which it will, It's hard to justify the billions of dollars spent on AI specific datacenters for essentially the bricks and mortars. I don't think that its very sound decision that they were worth building, it might make some compensation but not enough, in my opinion.
I saw more than one video about datacenter noise that were clearly crypto mining. There are some questionable designs leveraging shipping containers and what sound like a lot of 120mm fans.
It's pretty impressive how far American salaries go in other countries. Between thousands of applications, if you manage to snag a single IT role with a larger corp you're potentially getting the local equivalent of dozens of people's regular income.
Wild that we're still learning new things about ancient architecture! I'd think with all the modern tech at our disposal we'd have full, high res scans of the inside by now.
As much as I love tech in my cars, I’ve found that the more you add, the more will eventually fail. If you really must integrate more software, make it free and guarantee X years of support. If that means a more expensive car, so be it let the market decide if it’s worthwhile. Subscriptions hide the cost and inflate the popularity of vehicles that otherwise may not have been purchased.
I saw a short clip on this project the other day and was thinking along the same lines! They animated the flies’ mouth part (proboscis?) lowering and I was wondering if they were truly reading the motor commands for that from the brain.
Heya! I'll answer each question individually, definitely let me know if you'd like any clarification though :P
TL;DR:
Concurrent bids: First payment to complete wins; everyone else gets auto-refunded and notified. Uses version checking in the database so no one pays for a post that's already been replaced.
Vibe coding: Started from a half-finished project by a dev team that ghosted. Took over and built the rest with Claude Code, but spent roughly half the time on security, performance, and privacy compliance — not just generating code.
LLM content: Uses LLMs to draft technical/promotional writing, then edits and fact-checks. Natural writing style is similar to LLM output anyway.
3AM breakages: Mostly from experimental automation tooling, nothing production-critical.
Now for the full answers:
1. Two people bidding to replace the same message:
- Simple explanation: Optimistic locking with automatic refunds.
- A bit more detail: The first payment to fully process wins. The second (third, fourth, etc.) person gets an automatic full refund and a notification explaining that someone else beat them to it. Under the hood it's a simple "check before you activate" on the actual message acceptance. When you start paying, the system notes which message is currently live. When the payment completes, it checks whether that same message is still there. If someone else already replaced it, the payment gets refunded instead of going through. Realistically, this shouldn't be happening in any normal situation as the backend is quite responsive. But if I got heavy enough traffic (specifically paid message submissions), I'd likely tune the behavior to refresh frontend values even more frequently, same with optimizing the backend to reduce latency.
- Techno-babble: When you initiate payment, the system snapshots the current post's version number and stores it in the Stripe PaymentIntent metadata. When the webhook comes back confirming payment succeeded, it does an atomic PostgreSQL UPDATE ... WHERE id = $1 AND version = $2 with an increment. If updated.count === 0, someone else already won. The payment gets automatically refunded via the Stripe API, and the user gets a real-time WebSocket notification explaining what happened ("Someone else posted while your payment was processing. Your payment has been refunded."). There's also a per-user Redis distributed lock (SETNX with TTL) to prevent the same person from double-submitting, and post numbers use a PostgreSQL sequence that's only consumed after winning the activation race, so there are no gaps in the numbering. The whole activation path is idempotent, so Stripe webhook retries are handled gracefully.
2. Vibe coding: The initial project referenced to build the site was hand-built, unfortunately by a dev team I paid who basically ghosted me halfway through. I got my money back and there's a whole story behind that but basically I got sick of waiting for their bug fixes and was spending so much time troubleshooting, I figured I may as well take full charge. Claude Code got me from there to here. But frankly, about half the time I spent building the site was spent on performance optimization, security hardening, and aligning with GDPR (and California's) privacy standards.
3. LLM influenced responses: Your instinct is fairly good on that! For more technical breakdowns and generic 'promotion' stuff, I draft with LLMs and then adjust based on my own preferences (and after fact checking where relevant). To that end, my natural writing style is a bit stiff/serious so it ends up sounding about the same. You'd be right about it being overengineered due to the low barrier to entry as well. I'm far from new to containerization, but stepping into the K8S world and configuring everything manually was outside my scope when the ends were more important than the means. Not that I don't make significant efforts to learn about the stack I'm using every day I work on it.
4. 3AM breakages: Haha.. a decent chunk, but nothing critical fortunately! Mostly various tools I've been testing out to help with automation/management of the stack. For such testing, I'll sometimes half-build out scheduled/automatic workflows without giving them the same polish I do production stuff. Had a lot of fun fighting Flux between codebase changes, automated dependency PR merges, etc.
Sorry for the wall of text by the way, I haven't received much in the way of genuine intrigue (i.e. things worth responding to in detail) and as you can tell, I'm quite passionate.
Well congratulations! You've produced the thing you wanted to make and that's awesome! And I bet you learned heaps along the way.
We're moving into a really weird time where this grade of thing you have made with its robust infrastructure is going to be absolutely everywhere. Those things won't be the differentiating factor. It will be taste, opinion, and passion.
I'll probably be a meme in ten years for this but I don't think this is the one that's going to take off and make you wealthy(er?). People's brains are too addled by strobing media, mine included, for a simplicity to hold on to them. But I do think you have shown really valuable traits in shipping this that indicate you will have success sooner or later. And you can be proud of yourself for this. Well done.
Much appreciated! It really is quite amazing how 'easy' it is to get going without what used to be multiple textbooks' worth of foundational knowledge. I will say, having reasonable technical background, that I do totally get the hate people have towards vibe-coded apps. I wish maybe they were more discerning with it over blanket-rejection but with some of what I've seen out there, many concerns are quite valid.
I too highly doubt my site will be any significant money maker but despite it being part of the core mechanic, I'm mostly just happy realizing a shower thought in a way that was previously completely unattainable haha. If nothing else, the EFF will be getting at least $17.77 at the end of the month so I can say some non-personal good came of it.
I've got lots of features on both the frontend and backend to prevent automated behavior that could be problematic. But ultimately nothing is stopping someone from throwing a random number into the payment modal to see if it works (though they'd still have to enter an email, zip, expiration, and CVV too).
reply