If I don't have a keybase account, can I use this app?
Introducing Keybase Chat
31–40 of 201 posts
Re: Introducing Keybase Chat
#32Umm has anyone read the lisc. for this application?
When providing Keybase or the Service with content, such as your name, username, photos, social media names, data or files, or causing content to be posted, stored or transmitted using or through the Service (“Your Content”), including but not limited to the Registration Data and any other personal identification information that you provide, you hereby grant to us a non-exclusive, worldwide, perpetual, irrevocable, royalty-free, transferable (in whole or in part), fully-paid and sublicensable right, subject to the Privacy Policy, to use, reproduce, modify, transmit, display and distribute Your Content in any media known now or developed in the future, in connection with our provision of the Service. Further, to the fullest extent permitted under applicable law, you waive your moral rights and promise not to assert such rights or any other intellectual property or publicity rights against us, our sublicensees, or our assignees.
That's a bridge too far, and someone needs to dial this back.
Re: Introducing Keybase Chat
#33Awesome! I've been using this for the past few weeks on and off, and the user experience is very pleasant.
Now that I know about the JSON API for chatting, I'll have to add it to my unofficial Ruby interface[1].
Re: Introducing Keybase Chat
#34Umm has anyone read the lisc. for this application? https://keybase.io/docs/terms When providing Keybase or the Service with content, such as your name, username, photos, social media names, data or files, or causing content to be posted, stored or transmitted using or through the Service (“Your Content”), including but not limited to the Registration Data and any other personal identification information that you pr…
Isn't that boilerplate legalese for a service that lets you upload, edit, and share media?
Re: Introducing Keybase Chat
#35this looks like a great codebase! thanks so much for open sourcing this.
Re: Introducing Keybase Chat
#36Umm has anyone read the lisc. for this application? https://keybase.io/docs/terms When providing Keybase or the Service with content, such as your name, username, photos, social media names, data or files, or causing content to be posted, stored or transmitted using or through the Service (“Your Content”), including but not limited to the Registration Data and any other personal identification information that you pr…
Note the "in connection with our provision of the Service". This largely looks to me like a standard set of terms that they require in order to not get sued for shuffling around your content just to provide the service you're signing up for.
While the rest of the paragraph looks standard to me, I'm not completely sure about that last sentence. Is that what you're wondering about?
Re: Introducing Keybase Chat
#37OP here! I had to trim the post down for brevity, but I thought the HN community in particular might be interested in the API side of things. Undocumented in the post: you can invent channels for app-to-app communication from the JSON API. For example, it's possible with Keybase chat to have a program posting encrypted messages for another person or program, without cluttering up the visual chat interface. Also - to…
Q: group chats? Seems like it could be done by encrypting (and sending) the message to all recipients, so it's not particularly efficient, but it's a valuable UI thing.
Re: Introducing Keybase Chat
#38OP here! I had to trim the post down for brevity, but I thought the HN community in particular might be interested in the API side of things. Undocumented in the post: you can invent channels for app-to-app communication from the JSON API. For example, it's possible with Keybase chat to have a program posting encrypted messages for another person or program, without cluttering up the visual chat interface. Also - to…
Huh, the channels support is just in time to replace App.net (or maybe "to do App.net right", since it didn't really get off the ground.)
Re: Introducing Keybase Chat
#39OP here! I had to trim the post down for brevity, but I thought the HN community in particular might be interested in the API side of things. Undocumented in the post: you can invent channels for app-to-app communication from the JSON API. For example, it's possible with Keybase chat to have a program posting encrypted messages for another person or program, without cluttering up the visual chat interface. Also - to…
Thank you and the Keybase team for this. Unlike other services, I think KB has solved the online identity authentication issue.
There's one hurdle I need to work through to get going on chat. Thus far I've avoided uploading my private GPG key to my Keybase profile, or even copying it to other devices (call me paranoid). Unfortunately this apparently means I can't authorize any other devices (see error message: http://imgur.com/a/UOftN). I assumed device keys were meant to solve this problem, but maybe not. Is there a supported way to make a subkey (GPG or otherwise) of my primary private GPG keypair, so other devices can securely authenticate against my KB profile?
EDIT: I haven't yet started using device keys. Maybe they would work?
Re: Introducing Keybase Chat
#40Umm has anyone read the lisc. for this application? https://keybase.io/docs/terms When providing Keybase or the Service with content, such as your name, username, photos, social media names, data or files, or causing content to be posted, stored or transmitted using or through the Service (“Your Content”), including but not limited to the Registration Data and any other personal identification information that you pr…
> in connection with our provision of the Service.
This is pretty much boilerplate legalese that's generally intended to mean "you can't upload a file to your public folder, then sue us for copyright infringement because that file is in a public folder".
Lawyers seem like to cover their clients' asses as much as possible, but for a service like this that's designed for privacy-conscious people it'd do them well to step back and think about how the license comes across to privacy-conscious laypeople.
From what I've seen of Keybase, from back when they were just an alternative to the PGP Web of Trust to now, I don't think they're genuinely planning anything nefarious (but they'd still do well to have a ToS that reflects that).