The Runny Egg Problem

QR codes are like runny eggs.

June 18, 2025

When they're done right, they're perfect! It's an instant connection between physical and digital, no typing URLs, no friction. But when they're done wrong, they're dangerous. Malware, phishing, redirects to who-knows-where.

The problem is you can't tell the difference until after you've taken the risk.

So most people just avoid them entirely. Which is a shame, because the good ones are really useful.

You trust runny eggs when:

• You know the chef
• You trust the restaurant
• The kitchen has a good reputation
• There are consequences if they get it wrong

QR codes work the same way. You need to trust the source.

When you use a generic shortener service, you see something from bit.ly or tinyurl.com followed by a random string of numbers. You have no idea who created it or where it really goes. It could be anyone sending you anywhere.

I'm building something where organizations can create QR codes that appear under their own domain. So instead of scanning a code that goes to some random shortener, you scan one that goes to a URL you recognize.

The organization controls what you see. I just handle the infrastructure.

It's like the difference between a runny egg at a gas station versus one at a restaurant you trust. Same basic thing, completely different risk profile.

Why This Matters

Right now, QR codes are underused because people don't trust them. But they could be incredibly useful for:

• Tourism recommendations to vetted destinations
• Event programs that update in real-time
• Educational materials that link to current resources
• Business cards that connect to live information
• Marketing materials that track engagement

The technology isn't the problem. The trust is the problem.

If we can solve trust, QR codes become much more useful. And trust comes from knowing who's behind them.

Trust Works Both Ways

When you scan a QR code, you're trusting whoever created it. That's unavoidable.

And when an organization uses my platform to create QR codes, they're trusting me not to mess up their reputation. If I screw up the infrastructure or let bad actors use the system, it reflects on them.

So I have to be very careful about who I work with, and they have to be careful about what content they serve. Everyone's reputation is connected.

The Bigger Picture

Imagine if you could scan QR codes knowing exactly who was behind them, what you were going to see, and that it was safe. Suddenly they become useful for all kinds of things.

The technology isn't the hard part. The trust is the hard part.

I'm working on this because I think the trust problem is solvable, but it requires thinking about QR codes differently.

It's much more than a technical challenge -- it's fundamentally a relationship challenge.