If I don't have a keybase account, can I use this app?
Introducing Keybase Chat
51–60 of 201 posts
Re: Introducing Keybase Chat
#52Hey 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)
Looks like it's a bit more friendly than some creepo raccoon
Huh.
Re: Introducing Keybase Chat
#53Re: Introducing Keybase Chat
#54Re: Introducing Keybase Chat
#55Re: Introducing Keybase Chat
#56Re: Introducing Keybase Chat
#57OP 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…
Wondering if you can clarify a bit—what parameters cause a chat to/not to show up in the GUI? Different topics? Different channel names? I have a use for this immediately and am excited to give it a shot!
Re: Introducing Keybase Chat
#58OP 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 awesome! Thanks! Wondering if you can clarify a bit—what parameters cause a chat to/not to show up in the GUI? Different topics? Different channel names? I have a use for this immediately and am excited to give it a shot!
For example:
keybase chat send friend1,friend2\
--topic-type=dev\
--topic-name=KEYBASE-SYSOPS\
"server-restart [reason:hot and bothered]"
I'll never see this in the GUI but you and your friend1 and friend2, can access the messages through the chat API. The topic-name can be whatever you want, and it allows you to structure messages into channels.----
If you're using the JSON api - which makes more sense if you're programming it - take a look at `keybase chat help api` to see some examples of how to structure the JSON going in. Anywhere you see a `channel` object, you can add `topic_type` and `topic_name` to them. Both should be strings.
Re: Introducing Keybase Chat
#59Earlier quoted context omitted.
Isn't that boilerplate legalese for a service that lets you upload, edit, and share media?
there are key additional phrases that subtly make it different, like the fact, that this is transferable. And though not uncommon, using the term "provision of service" leaves the door wide open to your contents usage, because the lisc. is non-revocable, and perpetual. If say, in 3 years from now as a provision of their service they offer analytics, or direct marketing. they can use any of your content for that. I ge…
Re: Introducing Keybase Chat
#60OP 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…
> Undocumented in the post: you can invent channels > for app-to-app communication from the JSON API. Is everything accessible from the JSON API? Like, say I wanted to create a mashup of GitHub and Keybase, could I do so?