Live data from Hacker News

Introducing Keybase Chat

keybase.io

21–30 of 201 posts

Re: Introducing Keybase Chat

#23
This is fantastic! I've been playing with it for a bit, and I'm loving it.

Question: since (encrypted) chat history is stored on keybase servers, does my chat history count against my KBFS quota? If so, how do I clear it out? If not, how do you mitigate against someone building a pseudo-FS on top of chat messages for free unlimited storage?

Re: Introducing Keybase Chat

#24

Hey malgorithms, this is great! I check the Keybase website every month or so for updates and discovered yesterday that there's a new logo, replacing the old thieving dog/ferret/raccoon with what appears to be a person's head with their hair in a bun holding a key. Can you give some background on the thinking behind this logo redesign? (Sorry it's not a question about chat, per say)

I don't know for sure, but my assumption is that she is 'Alice'[0] which is a common name used when explaining cryptography

[0] https://en.wikipedia.org/wiki/Alice_and_Bob

Re: Introducing Keybase Chat

#25

OP 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…

This is really cool. Question: right now, I have a [deep link to Keybase's encrypt page][1] on my website as "Create encrypted message." Will there be a way to do something similar, but using Keybase Chat(tm)? ("build it yourself" is an acceptable answer in this instance)

[1]: https://keybase.io/encrypt#oddevan

Re: Introducing Keybase Chat

#26
post #7

OP 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…

Firstly, thank you so much! Secondly, I think this is incredibly important moving forward with the proliferation of messaging channels. I want to be able to use one program for all of my different chat sessions. Whether that be adium or pidgin or mIRC or even weechat/bitlebee in a docker container. It would be great if there would be common plugins for common chat clients provided off the shelf. :D

We didn't design Keybase's chat API to match any messaging standard, but the number of calls into it are very few and flexible, and we're open to change.

As it is right now, I imagine it would be very easy to write a library that acts as a bridge to other interfaces, if that's of interest.

There are calls to see into your "inbox" which is the set of conversations, read messages, even peek at unread messages. And of course send messages, too.

Re: Introducing Keybase Chat

#28
post #18

This really does look great. Edit: since I haven't been running Keybase for the past 2 weeks, I missed the fact that they disabled continuous background proof verification due to my concerns: https://github.com/keybase/keybase-issues/issues/2782#issuec... Good on them! The rest of this comment is not actually applicable anymore and you should give Keybase Chat a try :) Original comment: ----------------- My biggest c…

Looks like they did in fact fix it, just forgot to report back. (Just saw a new comment on that issue)

Re: Introducing Keybase Chat

#29

Is it technically possible for Signal/Whatsapp to use Keybase keys in lieu of phone numbers? If so, how practical would it be to add this as an option?

No. And even if it were possible they wouldn't allow it. Their servers are designed to forbid anything different from what they already do. Forget about that.
Post reply on HN