61–70 of 201 posts
This looks great, but if you want this to work, you need Android and iOS support. When is that going to happen? Is that going to happen?
Apparently it is coming.
ahahah, that's great!
What is this paper key? I don't want a paper key! Now I have to write this and keep it in my pocket? No!
That way, you don't have to rekey all your services if you lose it and access to all your devices, like I did.
Protip: Use the paper key. Keep it safe. You never know when you'll have to use it.
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)
As for brand messaging: the thieving kangarooster was suggestive of spy-like activity, which was playful but many people thought it sent the wrong message.
I personally like the message of the key in the hair...I mean I haven't thought it through in some deep way, but it's sort of like seeing a pencil in someone's hair: it's suggestive about their personality, and a pencil is an easy-to-use tool. A key in there feels good like that, like you can just grab it and use it easily. But that's just my own personal, previously unshared, take on why I like it.
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…
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…
Just installed and it's still asking me for an invite code on the Fedora RPM.
Sorry, I'm a little confused: is this a chat app client that still requires a central server to route messages around?