keybase / keybase-issues

A single repo for managing publicly recognized issues with the keybase client, installer, and website.
902 stars 37 forks source link

More Services - like Jabber/XMPP, Facebook, etc. #389

Open eingemaischt opened 10 years ago

eingemaischt commented 10 years ago

Hi,

will there be an API or a documented workflow to propose a new service?

With Jabber, Facebook or even Threema, textsecure etc. on android the service would be even more usefull..

MattSurabian commented 10 years ago

The issue here is that these services are "private" in nature so the concept of a public record is lost. It's very valuable to have transparency for service proofs so users can look at a keybase profile, click on a given service and see the proof right there. If the proof disappears so does the verification. Without this, users are forced to take a third party's word for each verified ID and invalidation becomes completely invisible, impossible, or contrived depending on the service.

Services like threema, Jabber, etc have no public record at all. Even something relatively public like Facebook would require users attempting to verify someone's identity to have a Facebook account in order to see a wall posting or whatever they're called.

I think it's outside the scope of keybase to attempt to be a one stop shop for all a users online identities and personally I wouldn't want to see features like this be added when the side effect is reduced transparency and no additional security.

dgw commented 10 years ago

For what it's worth, Facebook does allow public profiles that are viewable without being logged in—or did at one point, if that's no longer the case. Proof on a Facebook profile could be via a profile field that appears on such a public page, like the "About Me" section (if set to do so). But I do see how private services or services with no inherent record wouldn't be particularly useful or even feasible to support in Keybase.

I am, however, behind the idea of supporting more services. I'm not sure, for example, how one would go about verifying ownership of a hosted blog at WordPress.com, Blogger, or tumblr (for a few examples), even though those are public—because the current website verification method relies on a very specific file URL that might not be possible to create on such a hosted platform. Whether those particular services are candidates for support or not, expansion of the list can only make Keybase more useful, right?

MattSurabian commented 10 years ago

@dgw Definitely. I'm all for additional public services and looking forward to seeing what keybase decides to add in the future.

zQueal commented 10 years ago

As stated here there are many public services on the way -- however, just keep in mind that each platform is different offering different challenges with each. It's going to take some time.

malexmave commented 10 years ago

XMPP has a system called PubSub. Perhaps one could do something with that for verification purposes.

ghost commented 10 years ago

However annoyingly corporate it may be, LinkedIn has public profiles, and is widely used. And it's not where children soil themselves in public.

schiessle commented 10 years ago

Let me throw in some more ideas. I would really like to see support of some of the free and distributed networks like Status.Net/GNUSocial, pump.io, Diaspora, Friendica,...

I think Gitorious, as the free software answer to Github, would be also a good match.

zQueal commented 10 years ago

Made a thread: #518

cedwardsmedia commented 10 years ago

The ability to verify a Facebook page would be great. Perhaps Keybase could do the same thing with Facebook (public profiles and pages) that it does with Twitter and check for a given value in a post.

zQueal commented 10 years ago

Well, Facebook gives you the ability to make an individual post public, which would make Facebook really awesome for verification, as it would be pretty easy. Not sure why anyone would want to verify their private Facebook account though.

cedwardsmedia commented 10 years ago

That's true. I'm sure someone would find a reason, so the concept would work either way.

I do love the idea of Keybase and I love that it provides a way to both validate the key and validate our identities and properties around the web.

On Apr 15, 2014, at 7:08 PM, Zach Queal notifications@github.com wrote:

Well, Facebook gives you the ability to make an individual post public, which would make Facebook really awesome for verification, as it would be pretty easy. Not sure why anyone would want to verify their private Facebook account though.

— Reply to this email directly or view it on GitHub.

hersche commented 9 years ago

when a post-signature would work on facebook, it's may not that hard to merge that for diaspora too?

kb is a nice idea!

dreamflasher commented 7 years ago

So by now we have Facebook in the list of supported services. It would be really great to have Jabber in there, too. And yes it's possible, because the profiles are public. For example one could include it in the about free text.

zQueal commented 7 years ago

518