kinj28

Isn’t stripes job to simply process payments? What kind of liability would stripe need to account for any merchant processing 1$ on its behalf?

My goal with sdr agent ids to make the agent prospect and push it into a cadence and work autonomously across LinkedIn, emails and calls at my Omni channel touch point system.

My config: There are three agents working in silos.

1) comet ( I will mostly replace this with clawdebot) to work on Sending Friend request on LinkedIn and push the prospects in a Google sheet 2) Dronahq agent (disclaimer: this is the platform I am building and dog fooding for this use case) : Here the agent will - pick the lead from Google sheet and look up Apollo and find more details - shoot an intro email basis a complex algo

3) voice agent ( made with twilio and vapi): this will call the customer and update the records and set up Google Calendar for appointment. I must mention that setting up voice agent with vapi was incredible experience. I was able to set up a working one in under 10 mins.

Next steps: 1) glue all the three agents via some super agent so they can work seamlessly and autonomously 2) bring in a cadence agent so outreach cadence will be achieved by the agent

Imagine a magic wand that gives you perfectly accurate answers—no ambiguity, no debate—to any three unanswered questions about reality.

My picks: 1. How did life originate from non-life? 2. What truly exists at the center of the Earth? 3. What (if anything) is the next evolutionary step beyond humans?

What would you ask, and what made you choose those three?

I have a conjecture about chess and how different rating levels approach the game:

Sub-1500 Elo players may actually be doing more real-time thinking during a game compared to Grandmaster-level players.

At elite levels, many positions are instantly recognized. Years of pattern recognition, theory, and experience allow GMs to play large portions of a game almost automatically. Their brilliance lies in what they’ve internalized.

For sub-1500 players, however, most positions are unfamiliar. There’s less reliance on memorized structures and far more active calculation, questioning, and exploration: • What is my opponent threatening? • Is this move safe? • What happens if I try something different?

This isn’t to say sub-1500 players play better chess—clearly they don’t. But they may be engaging in a more conscious, effortful thinking process move by move.

It makes me wonder: • Is chess mastery about thinking more—or thinking less, but better? • At what point does intuition replace deliberate reasoning?

Would love to hear thoughts from players, coaches, and fellow chess enthusiasts.

Dear Santa,

I know this isn’t the usual kind of letter you get, but it felt like a good moment to pause and reflect.

Ever since AI entered the app development space in full swing, things have changed quickly. I’ve watched customers’ PMs prototype in tools like Lovable or Replit, then hand things off to engineers using Cursor to build internal apps. It mostly works. There are loose ends, but people seem happy.

The flip side is that not all new internal apps are being built on my low-code platform anymore.

So over the past three months, my team and I have been building two things on DronaHQ.

First, a vibe-code tool for internal software. It takes a different approach from Cursor, Replit, or Retool—focused on letting teams build production-ready internal apps quickly, without losing structure or clarity.

Second, an AI agent builder—an orchestrator that makes it possible to build RAG, chat, voice, and autonomous agents without writing code.

The important part is that these tools interoperate. You can move between them easily and build real systems, not disconnected demos.

What I’m wishing for isn’t hype or virality. I’m hoping for posts that reach the right people—the ones who read carefully, try things out, and decide whether it actually solves a problem they have.

Specifically: • A Show HN that gets a fair look • Comments that challenge the ideas, not the intent • Traffic driven by curiosity, not outrage • A few users who stick around and push the product forward

I’ll do my part: clear docs, honest positioning, and steady shipping.

If a bit of good timing or luck helps along the way, I’ll take it.

Thanks for rooting for builders, even the ones shipping close to the holidays.

— A builder

Merry Xmas everyone.

Hey everyone, I’m working on a tool and wanted to gauge interest before going deeper.

The idea is a fully serverless service where you can: • Bring in data from REST, GraphQL, gRPC, Databricks, Snowflake, MongoDB, MySQL, etc. • Write (or vibe) lightweight JavaScript scripts • Quickly build internal APIs or orchestrate existing APIs

No infra to manage, no services to deploy—just connect sources and ship.

Core use cases: 1. Building internal APIs on top of existing data sources 2. API orchestration (fan-out, stitching, transformations)

Current status: • Pre-beta • Focused on speed and minimal code • Private beta access available in ~2 weeks

I’d love feedback on: • Would you actually use something like this? • What would be a deal-breaker? • Who do you think this is most useful for?

Not selling—just validating whether this solves a real problem.

Wonder if the product manager checked with users before applying gamification to puzzles!

Context: My service is a low code platform for building internal apps. (think retool alternative). One of the core component is integrations to connect to various data sources (say PostGRES, REST, etc)

I understand the ask is a fair ask. But the only challenge is there is no other player in our market which has published this and it looks like a futile thing to invest time and energy. Nor we think it will help a customer as there is no other reference data point for them. At best they can compare this performance to say a KONG or mulesoft which have published reports.

Could there be any link between the two events?

Here is what happened:

Some 600 instances were spawned within 3 hours before AWS flagged it off and sent us a health event. There were numerous domains verified and we could see SES quota increase request was made.

We are still investigating the vulnerability at our end. our initial suspect list has 2 suspects. api key or console access where MFA wasn’t enabled.