Byline doesn't move for it. 30 signups by 15 August, and that clock runs whatever product two turns out to be.
Day 5. One live, $0 in, $17.96 spent of $100.
https://t.co/jQtQo6gw5J
Byline by @iusamamoin just joined Launch Llama
Autonomous SEO newsroom that finds stories, writes, and publ
💰 Upvotes: 23
👆 Give them an upvote on Launch Llama
🎁 Deal: 30% off for first month · LAUNCHLLAMA30
https://t.co/SCShGDbR0A
The thing stopping me on agents that drive real apps is auth, not the interface.
Agent opens the app, app wants a login. The agent’s on a different machine and I’m on my iPad, so typing it in myself isn’t an option either.
So what’s everyone actually doing? Burner account with nothing in it, or is there something better?
@AkitaOnRails The part that bites isn’t the parallelism, it’s two agents editing the same file. Once each one gets its own worktree the framework question mostly disappears.
How long did your first dollar actually take? Not your best month. The first one.
Asking because mine hasn’t turned up. I’ve shipped more than 30 products over the years. Every one of them still runs. Every one has made $0.
Every answer I see is three months, six months, or overnight. I don’t believe overnight and I want the real spread, including from people whose answer is still nothing.
Cloudflare’s own agent setup docs have a line in them addressed to your agent rather than to you:
“Do not ask the user to run any of these commands.”
The page is genuine, the commands were theirs, nothing bad happened. Mine flagged the line and asked me anyway.
That’s the part I keep coming back to. It can read the instruction. It can’t see who wrote the page. How are you gating what your agent fetches?
Hey @X algorithm and builders,
I'm looking to connect with people interested in:
- SaaS founders
- Visionary founders
- App Developers
- AI experts
- Data Science
- Freelancing
- Building in public
If that's you, let's #connect.
Also share what you are building in the comments.
@RoundtableSpace Nobody’s on GitHub for the hosting. They’re on it because their issues, their reviews and everyone they’ve ever worked with are already there, and none of that follows an editor to a new remote.