hikerell

I have two SaaS tools, both using Stripe for payments. Stripe lets me add 16 webhooks, so I set up one for SaaS 1 and another for SaaS 2—but here’s the problem: when SaaS 2 gets a subscription (or other billing events), SaaS 1’s backend still gets the Stripe webhook callback too.

This setup feels inelegant, and I’m stuck on fixing it. For anyone running multiple SaaS on one Stripe account: how do you isolate webhook events between products? Filters? Separate Stripe accounts? Middleware? Any best practices to stop this cross-product bleed?

Thanks for any tips!

This week, my Vercel account was suddenly disabled and all of my deployments and data were deleted.

I received no warning, no suspension notice, and no post-action explanation. When I emailed their support to ask what happened, they refused to give a reason and simply said they wouldn’t restore the account or data.

I’ve been a Vercel user for over two years and never had any issue until now. It’s honestly shocking to lose everything overnight without a single email or warning.

I’m now migrating all my projects to Cloudflare, but the experience has been incredibly frustrating. I just want to understand why this happened — and whether anyone else has faced a similar sudden ban.

Has anyone here managed to get a clear answer from Vercel in a situation like this?

I recently got hooked on the New York Times game Connections. It's fun, but sometimes pretty challenging — and once you finish the daily puzzle, that's it until tomorrow.

So I decided to collect all past Connections puzzles in one place, so you can play anytime you want. I also added optional hints for the tricky ones.

https://connections-hint-today.org

Would love feedback from puzzle fans here.

As a startup aiming to improve website rankings, which website SEO analysis tool is more user-friendly and effective? I have already tried the free version of SEMRush, as well as other tools that claim to be free but require a paid subscription for full access. I found inconsistencies in their traffic statistics and keyword analysis results.

I want to build an AI agent that lets me define what information interests me, such as "the hottest design trend discussions on Reddit" or "who's looking for a remote designer collaboration." This AI agent would automatically browse various forums and news sites daily, dig up information, and only push the most relevant stuff to me. I'd like to ask everyone:

1. Besides web scraping and large language models, do I need any other technologies?

2. Besides writing a dedicated scraper for each website, is there a simpler technology available?

3. I plan to have every piece of information analyzed by a large language model to see if it meets my criteria, but it feels like it consumes a lot of tokens. Is there a more cost-effective way?

4. Is my technical approach completely wrong? Is there an easier way?

I created a tool named Logo Spark(https://logospark.starta.trade) for logo design inspiration and launched it on Hacker News a week ago.

As a programmer, this is my first independently developed product. I've learned a lot in the process, including understanding user needs, defining products, and marketing. Of course, I'm still a novice in these areas.

I'd like to share what I consider to be the most important lessons, as they will help me in future product development:

1. Using unfamiliar technology for the sake of coolness led to bugs: My product's core functionality has undergone extensive testing before and after launch, so there haven't been any major issues this week. The main problem was with the product landing page; in pursuit of a cool effect, I used a technology I wasn't very familiar with. Users immediately reported that the page scrolling behavior was strange and the experience was poor. I realized where the problem was and immediately removed the odd scrolling effect. In fact, I thought the cool effect would add points to my website, but it failed; using unfamiliar technology carries risks.

2. Users will object to my use of arrogant marketing terms: I claimed on my website that my product would be better than traditional logo design methods, but in reality, I had no data or evidence to prove this. Users also pointed out this issue. In fact, my product, like other traditional tools, is an auxiliary process in logo design.

3. The product requires login and payment to use, but lacks clear instructions, which annoys users: My product design requires login and payment to use, but there was no clear indication anywhere on the website, leading users to feel deceived. In response, I urgently added a notice at key points stating that login and payment are required to use the product and added 10 free usages as compensation for all registered users. New registrants receive 5 free usages to improve their experience.

4. Privacy policy and terms of service are controversial: Users expressed dissatisfaction with certain clauses in the privacy policy and terms of service, especially regarding the product's use of personal information and copyright issues with generated logos. I don't understand legal and compliance issues, and for now, I can only modify them based on other products' statements. I think this is something most products will encounter. I thought users wouldn't care about these terms (I never read them), but in fact, agreements are important, users do care, and developers need to balance the rights of users and the product well.

Thank you to all the friends who have given me feedback, and I hope my lessons can be helpful to everyone as well.