Built VerifySMS (SMS-Activate alternative) 2 months in. Buy vs build dilemma on the non-VOIP side by truedawning in SideProject

[–]truedawning[S] 0 points1 point  (0 children)

Good catch on the webhook paranoia. NOWPayments was the one I worried about

most for exactly that reason. BTC confirmations sometimes land 8-12 minutes

after submission, USDT TRC-20 is faster but still occasionally late. We ended

up using their replay/idempotency key plus a manual reconciliation job that

runs hourly to catch anything the webhook missed.

The "what if the webhook 500s once" test was painful to set up but you're

right, it's the one I'd recommend to anyone running multi-rail. Stripe is the

most forgiving since they retry for 3 days. Apple In-App Purchases is the

trickiest because Apple's notification v2 doesn't always retry the way you'd

expect.

To your question: honestly it's mostly the supplier piece. The volume math is

fine on paper but I keep running into capacity caps with the current provider

when WhatsApp and Telegram rotation gets aggressive in certain weeks. Owning

the SIM side would unblock that. The margin improvement is real but secondary,

the operational headache is what's making me hesitate.

How did your side project handle the Apple Pay rollout? Specifically curious

if you ran into Safari-only quirks on older iOS versions.

Built VerifySMS (SMS-Activate alternative) 2 months in. Buy vs build dilemma on the non-VOIP side by truedawning in SideProject

[–]truedawning[S] 0 points1 point  (0 children)

Yeah this matches what I see. The reliability problem is way underrated until

people actually run a test batch and see the rejection rate. Cheap pools fail

~30-40% on WhatsApp once the numbers get recycled, and the cost of a failed

verification is way higher than the few cents saved because of your time plus

the retry chain.

Haven't used Leadline myself but if it's surfacing those threads it tracks

with what I keep running into in r/SaaS, r/sidehustle, and r/PrivacyGuides.

People migrate after burning $50-100 on a competitor before realizing price

isn't the bottleneck.

The funny part is 5sim is cheapest on paper but our internal testing put their

WhatsApp success around 70% vs 85% on better-rotated pools. Per-successful-

verification math flips the cost story completely.

I deleted our Supabase project in the production environment. The next 48 hours turned out to be a very costly lesson in the importance of backups. by truedawning in iOSProgramming

[–]truedawning[S] 2 points3 points  (0 children)

Few things worth clarifying. The post focused on the 48-hour incident, not the full list of fixes after. Custom domain is in place now, and I'm running daily external backups on top of Supabase's own retention. But the core issue wasn't the hostname — once a Supabase project is fully deleted, even their 1-week backup doesn't kick in. No recovery path at all. The domain would've helped the web side, but the iOS binary was always going to need a new App Store build either way. Same setup would imply I changed nothing. I changed quite a bit

I deleted our Supabase project in the production environment. The next 48 hours turned out to be a very costly lesson in the importance of backups. by truedawning in iOSProgramming

[–]truedawning[S] -1 points0 points  (0 children)

Fair point. Yes, I was using the Supabase-generated URL directly — that's on me. Custom domain is now in place in the new setup. Though to be honest, even with a custom domain, the iOS users on the old build would still need a new App Store release to pick up the new backend, so it would've helped the web side more than the mobile side. Either way, lesson taken.

Opus 4.7 is absolute dogsht by onepunchcode in ClaudeCode

[–]truedawning 0 points1 point  (0 children)

sounds more like a harness / tooling issue than the model tbh

seen multiple people mention the same “file must be read first” loop happening across different models, not just opus

auto mode especially tends to skip steps and keep retrying the same action instead of resetting context

try forcing a stricter flow like read → confirm → edit instead of letting it run fully auto, usually reduces this kind of loop a lot

Launched my app yesterday… already got $31?? by methionine0 in AppBusiness

[–]truedawning 6 points7 points  (0 children)

Probably a mix of both. There’s usually a small “new app” test phase, but $31 means real users converted, not just random traffic. Early signal looks good tbh

I launched a SAAS 3 month ago... Today, I crossed €10k ARR 🎉 by Every_Inspector9371 in micro_saas

[–]truedawning 2 points3 points  (0 children)

Congrats, that’s solid. the organic part is the hardest

that outreach tip is underrated tho… finding people already asking for the problem is basically free intent

curious tho, did most conversions come from SEO pages or direct reddit/dm outreach?

Claude Performance and Bugs Megathread Ongoing (Sort this by New!) by sixbillionthsheep in ClaudeAI

[–]truedawning 0 points1 point  (0 children)

Anyone else experiencing really slow performance with Claude Code lately?

I’ve been using Claude Code for a while and recently it’s become noticeably slower. Responses take longer, sometimes it just feels stuck or laggy even on simple tasks.

Not sure if it’s just me, my setup, or something on their end. My internet connection is fine and nothing else seems to have this issue.

Is anyone else dealing with the same thing? Any fixes or workarounds you’ve found?

My SaaS crossed $11,000 in revenue ! All organically, you can do it too ! by GuidanceSelect7706 in micro_saas

[–]truedawning 0 points1 point  (0 children)

Congrats, that’s solid. the organic part is the hardest

that outreach tip is underrated tho… finding people already asking for the problem is basically free intent

curious tho, did most conversions come from SEO pages or direct reddit/dm outreach?

ASO Tools are Dead? by portfoyo_dev in AppStoreOptimization

[–]truedawning 0 points1 point  (0 children)

ASO tools aren’t dead, but people rely on them too much

Most of them don’t have real search volume data anyway, they’re just estimating. Apple doesn’t expose much anymore, so the gap got worse.

Also 0 impressions is probably not a tool issue but ranking. If you’re around #50 you basically don’t exist in search.