Remix.run Logo
johndoylecape 13 hours ago

Doyle here :) I'm very proud of my military service!

Prior to Cape, I led the national security business at Palantir. That experience was actually the catalyst for Cape. It’s where I first learned about the massive array of vulnerabilities that exist in our current cellular networks. I saw how those gaps impacted not just government organizations, but everyday people, and I realized that the mobile phones we carry every day are perhaps the single largest risk to our privacy.

I needed that experience to understand the depth of the problem, but once I left to start Cape, that connection ended. Cape has no ties to Palantir. We aren't a subsidiary, we aren't a "front," and we don't share data with them. The only thing we took from Palantir was the desire to fix a broken system. If you want to see me and some of the rest of our founding team talk more about this topic, you can watch this video on our Instagram page here.

Another related theory I’ve seen online is that Cape is a honeypot for law enforcement. Cape is not a honeypot. It’s so hard to prove a negative, but at least I can say it clearly and out loud: Cape is not a honeypot.

We are a group of individuals who deeply value privacy. That mission carries across everything we do, from our work with the US government and allies, to everyday people, and everything in between.

We are incredibly proud to work with people who protect our country by ensuring they have secure, trusted communications wherever they are. https://www.bloomberg.com/news/articles/2024-04-18/us-navy-t...

We also work with the EFF to provide investigative journalists and activists with free Cape service so they can do their work safely. https://www.cape.co/journalists-and-activists

We partner with non-profits to support victims of domestic abuse who are facing cyber-stalking and digital harassment. https://www.cape.co/break-free

We are a young company growing exponentially, and we don't plan on slowing down. We know we have to earn your trust every day. The truth is, no one else is building a high-quality, first-class solution to these specific cellular problems. We are committed to being the ones who do it right.

Ms-J 13 hours ago | parent | next [-]

Someone doesn't need to work for Palantir or the military to understand that cellular security is fundamentally broken and completely insecure.

That is a lot of highly polished for the camera media you dropped into that post. The way that you word things, such as "Cape is not a honeypot." but don't delve any deeper, to start, gives someone less than zero confidence or trust in your words.

I have seen enough in the industry to say that your words are meaningless.

j-bos 9 minutes ago | parent | next [-]

> The way that you word things, such as "Cape is not a honeypot." but don't delve any deeper, to start, gives someone less than zero confidence or trust in your words.

Neither or against either perception but this reminds me of https://barrypopik.com/blog/i_know_its_not_true_but_lets_mak...

alek-cape 12 hours ago | parent | prev [-]

John's account was throttled since it's new. Posting this on his behalf. ----

You're right that you don't need to do those things, but I would argue that my background made me uniquely situated to understand and care about these problems deeply enough to spend years of my life building a company in response.

I say "Cape is not a honeypot" a lot just so I don't appear to be mincing words. If you want to delve deeper on how we treat customer data, a couple of good resources are our privacy policy: https://www.cape.co/privacy-summary

And our trust page: https://trust.cape.co/

You can also check out our blog for a bunch of posts on specific features we've built, etc.

dang 8 hours ago | parent | next [-]

Yikes, sorry guys (I'm a mod here). I've marked his account (and yours!) legit so this won't happen again.

It's my least favorite thing about HN that high-quality new accounts, such as founders jumping into threads about their work, sometimes get throttled by the software. Gah.

johndoylecape 2 minutes ago | parent [-]

Thanks! No worries. I'm trying to respond to a few more comments, but seems like the thread is winding down.

UnreachableCode 5 hours ago | parent | prev | next [-]

What about some form of external auditing down the line to add legitimacy to these honeypot claims? Maybe open sourcing the technology as well?

bsstoner 4 hours ago | parent [-]

We’re working on an audit now. There’s an RFC on Reddit looking for input: https://www.reddit.com/r/CapeCellular/s/zTn7HQ0emo

12 hours ago | parent | prev | next [-]
[deleted]
close04 5 hours ago | parent | prev [-]

> but I would argue that my background made me uniquely situated to understand and care about these problems deeply enough to spend years of my life building a company in response.

Maybe but this line of argumentation also opens the door to more criticism. Anyone looking at Palantir from the outside only knows their reputation and involvement in unsavory projects before taking a job. You chose to take the job with that knowledge covering most of your field of view. You stayed to work for that company contributing to that kind of work. That's a signal that's brighter than the valuable experience you gathered there. Tech can be learned but the values needed to support or even tolerate Palantir's activities don't get easily changed.

The premise of your company pivots on trust, not technology, the same tech is known and available to everyone else too. And it's trust in you that you will do what you say, not that you can do what you say. The latter is a given, you clearly have the knowhow. The former is putting any promise in doubt.

> Cape routes your traffic through our US-based mobile core.

This sounds like an anti-feature when it comes to privacy or the paranoid.

> I say "Cape is not a honeypot" a lot just so I don't appear to be mincing words.

I appreciate you saying it but Crypto AG probably also said that a lot (figuratively).

> Cape does not keep this data.

Unfortunately you are limited in what you can do here. Having or processing this data for any amount of time, even without keeping it, puts you in the position to be compelled to provide it.

bsstoner 4 hours ago | parent [-]

This is valid feedback and it’s on us to earn trust over time through our actions. I will say that Cape is a company of almost 100 people from many different backgrounds. Prior to Cape I spent almost a decade at DuckDuckGo. We’re a group of people that is frustrated with the status quo in the telco industry and want to do better.

One of the efforts we’re working on now is an audit of our data retention claims. We recently posted an RFC on Reddit if anyone from this community has input: https://www.reddit.com/r/CapeCellular/s/zTn7HQ0emo

We plan to continue to do more things like this that increase transparency and build trust over time.

birdsongs 7 hours ago | parent | prev | next [-]

> That mission carries across everything we do, from our work with the US government

Can you expand on this? Because currently, the US government is not someone I want the companies I use to work with.

> The only thing we took from Palantir was the desire to fix a broken system.

What broken system does Palantir fix?

J57E6H2hxM 2 hours ago | parent | prev | next [-]

Hey John, how did being a GB shape your later career? Were you an Echo?

Currently in cyber as a Guard O/civ and also considering SFAS. Thank you!

johndoylecape 10 minutes ago | parent [-]

Hey thanks for the question! I was indeed an Echo. I loved my time in SF, and I learned a lot about being a good teammate and doing hard things in ambiguous environments, and a bit about secure comms. The first two will help at any startup, and the 3rd doesn't hurt at Cape...

Only you know if you want to jump into SFAS. I knew I'd always regret not doing it, which made the decision easy for me.

pjc50 4 hours ago | parent | prev | next [-]

> I led the national security business at Palantir

> group of individuals who deeply value privacy

.. do you see the problem here?

wiredpancake 12 hours ago | parent | prev [-]

[dead]