i just built https://compeddit.pages.dev/v=1
which helps you track your competitors over reddit your competitors raised pricing by 40% their users left. you didn't even get to know even after they were ranting this on reddit. never let it happen again. try Compeddit.
would love feedback and suggestions.
We built MailClean after seeing one common problem again and again email campaigns fail not because of bad copy but because of bad email lists Businesses were sending emails to invalid, fake, and risky addresses without realizing it MailClean fixes that before you hit send
Since my last GrowHouse update, the project has moved further from architecture on paper into systems that actually feel alive.
The big shift is that the MMO side is starting to behave less like a static feature set and more like a living world with memory, daily rhythm, and player-facing identity.
Recent progress includes:
a deeper Underworld consequence layer, where runs leave behind heat, stash risk, district memory, and faction reaction state
faction reputation effects that begin to shape how the world responds to the player
a daily Blaze writing system that can generate a fresh briefing and a new set of contracts using the same AI personality/control rail already running across the ecosystem
a 100-level title ladder and achievement skeleton to start turning progression into visible identity rather than hidden math
continued work on explainable AI layers, where Blaze is tied to mood, receipts, recommendations, and bounded world guidance instead of acting like a random flavor bot
I'm sure a lot of you get to the point where you want to have a video created for your app/project. I did as well, and as a bootstrapped solo founder I've had a hard time justifying the $500+ cost for a 30s video that may or may not look the greatest. Not to mention the time it takes to find the right creator. It caused me to put off getting one created for too long so I decided to create an app to do it instead where I have full control. Looking to launch on PH once I've gotten a little feedback.
Every API testing eval we found either required source code access, relied on rich documentation, or measured output format rather than whether a test would catch a real failure.
So we built APIEval-20. Twenty scenarios across e-commerce, payments, auth, scheduling, and user management. Each scenario gives a model exactly two things: a JSON schema and a sample payload. No implementation details, no docs, no further context. The model has to generate a test suite from that alone.
The bugs are planted in live reference implementations. A bug is only caught if a generated test produces a response that deviates from correct behavior when run against the implementation. Submit through the hosted eval harness and get a score back.
Scoring weights bug detection at 70%, API surface coverage at 20%, and test efficiency at 10%.
I kept buying furniture I thought would look great, only to realize it didn't fit the space at all. Every design tool I tried felt like homework. I just wanted to say "design my dining room, replace with this table I want to buy"
We scanned 1000 random Product Hunt project URLs using the DLX7 free security scanner. The results were highly consistent. Most applications landed between C and B. At a glance, that appears acceptable. It is not.
