Hacker News Reader

Comment by lovedswain | Hacker News Reader

I guess a leak requires private data to be exposed, this is just a collection of public data.

Is it public info who invited you to the Clubhouse app? If not, that would assume some kind of breach, since that info is part of the leak.

> Is it public info who invited you to the Clubhouse app?

Yes: that is public info. This is all no more a "leak" than the original service is a "leak" of itself.

Besides, the name, username, profile picture, etc are publicly accessible via permalinks

For example: https://www.joinclubhouse.com/@clubhouse

Everyone can see who invited you to Clubhouse down in the bottom of the profile.

It's not only public, it's central to the whole concept. You can always walk up your tree to see who the original member in your line is.

I agree. This "hack" is the equivalent of any search engine indexing public Facebook or LinkedIn profiles.

Same as the recent FB and Linkedin incidents. It's all scraped data. Doesn't mean that collecting public data at scale is not something bad

Which one are you referring to? The recent millions of contacts that were exposed from FB contained phone numbers. It had my phone number and it's not public.

Still just scraping. They iterated every phone number on the planet.

https://twitter.com/mikko/status/1379686946117668867

It's a fabulous resource, I've already used it to identify unknown numbers sending me messages on Signal

Is now.

Yup, wrong tense used. :(

Reply on news.ycombinator.com