asked a great question in the comments on the last post. The kind that deserves more than a one-line reply, because it names an edge case a lot of you are going to hit eventually. 🧺 ➖➖➖
💬 THE ORIGINAL QUESTION
"My question would be about building a resource for lead capture, etc., where we ask members to test it and see flaws etc.? One of my projects is that and no better way to test than to ask a community like this to try it and give feedback? Would this be allowed if that intent is purely laid out at the front?"
Good question. Honest framing. And it exposes a real gap in the rule as written: the rule covers links, but it doesn't cover beta testing.
So let's close the gap. 🧵
➖➖➖
🔍 THE LINE, DEFINED
The rule was never about links. It's about what happens when someone clicks.
Ask yourself: where does the feedback happen?
✅ If it happens IN THE POST, that's building in public. Perfectly fine.
Share the repo. The code. The architecture. Screenshots of the flow. The prompt structure, the offer copy, the landing page as an image instead of a URL. Then ask: "Where are the flaws?"
People will genuinely tear it apart for you, and that thread becomes useful to everyone else building something similar. That's a real post. That's mutual value.
❌ If the feedback requires members to CLICK THROUGH to your own funnel, that's a hard no.
"Go try it at [link] and tell me what breaks" is not testing. It's traffic acquisition wearing a clipboard. 📋
➖➖➖
🧠 WHY THE DISTINCTION ISN'T SUBTLE
Here's the part worth spelling out, because Jacek's case makes it obvious:
If the tool is a lead capture resource, then sending members to it IS the lead capture. Every person who clicks through is a lead entering your funnel. Declaring the intent up front doesn't change what the tool does when they arrive. Honest framing doesn't alter the plumbing. 🚿
A signup flow that harvests emails works exactly the same whether the person arriving knows they're a test subject or not. The test is the extraction. The community isn't your beta lab, and 53,000+ members aren't your sample size.
The rule was never about intent. It's about function. 🤝
➖➖➖
📏 SO HERE'S THE OFFICIAL WORDING
Testing is fine when the feedback happens in the post. Repo, screenshots, artifacts, architecture. Evaluate it here, discuss it here.
If "testing it" means members visit your own funnel, signup flow, or lead capture URL, that's lead capture, regardless of intent, and it's covered by the same rule as every other link you personally benefit from.
Same as before: posts and comments, everywhere except the Connection Hub. Same ladder: warning → removal → ban. Same appeal rights.
Want people to actually exercise the flow live? Ask a moderator first (@David Vogel or @Shirsho Guha). Fair warning, the default is still no. But you already knew that, because you read the last post. 😄
➖➖➖
🤝 WHY TRUST IS THE WHOLE PRODUCT
dropped this in the same thread, and it deserves its own section, because it names the why behind everything above: "The problem isn't that someone benefits from sharing their work. It's what happens when the incentive behind that work is invisible to the people consuming it."
"The writing can be excellent. The information can even be accurate. But if the underlying incentives aren't transparent, trust eventually collapses."
"Trust isn't built by eliminating incentives. It's built by making them visible and keeping them aligned with the people you're trying to help."
He was talking about AI agents, and the parallel is exact: an output can look helpful and convincing while optimizing for an objective the human never agreed to. A post can look like generosity while quietly routing you into a funnel. Same failure mode, different packaging. 🤖
Here's why we guard this so hard: everything valuable in this community is a byproduct of trust. People post half-finished builds and the version that fell over. They share real numbers: what it cost, what broke, how long it took. They paste their client folders and their CLAUDE.md into the feed. Nobody does that in a room they suspect is farming them. The moment members start asking "what's this poster's angle?", the sharing stops. Not because of any rule. Because self-preservation beats generosity every time. And a community that stops sharing is just a marketplace with worse ads. 🛑
Rules don't create trust. They protect the conditions where it can grow. That's the whole job, and it's the reason the line above exists.
➖➖➖
🙏 THE HONEST BIT
Jacek did it the right way: he asked before he posted. That's exactly how this is supposed to work. The rule isn't a trap. It's a fence with a gate, and the gate is "ask first."
Most edge cases aren't someone trying to sneak something past the room. They're someone who didn't know where the line sits. Now there's one more line, and you know exactly where it is.
Keep testing. Keep building in public. Keep the value in the post, not behind the link. ❤️
⚠️ THE ONE EXCEPTION
Yes, there is one. Better to say it out loud than let you find it on your own and wonder.
Instructors for Eduba, Jake's consultancy, are permitted to post links to websites they've created, including ones with compensation streams attached. The same applies to the administrators and moderators of this community.
Before the "rules for thee" comments light up, here's the difference, and it's not a technicality:
1️⃣ This is a handful of vetted people, not a category. A few instructors, plus the admin and mod team, against 53,000+ members. That's not a loophole, it's a staffing model.
2️⃣ Their work is the product this place runs on. Instructors build the courses and material that make this community worth paying for. Admins and mods build and maintain the community itself, often in public. Their links aren't traffic extraction, they're curriculum and infrastructure.
3️⃣ Those links are reviewed before posting and disclosed as staff or instructor work. You will never have to wonder whether one of them is quietly funneling you. The incentive sits on the table, which is exactly the trust principle Bill described above.
And to close the loophole-hunting before it starts: this exception can't be earned, applied for, or inherited. You don't get it by being helpful, being popular, or building the coolest tool in the feed. It exists because these people are vetted, paid, or entrusted by Jake to build and run this place. If that arrangement changes, the exception changes with it.
Everyone else: same rule, same ladder, same door. Ask a moderator first. You know the default. 😄
Now go break something (in the comments). 🚀