Live data from Hacker News

Mastodon and Keybase

keybase.io

1–10 of 192 posts

Re: Mastodon and Keybase

#2
From: https://keybase.io/docs/proof_integration_guide

> To send us the config, you can send us the public URL for your config file or attach it directly in a Keybase chat message to @mlsteele or email miles@keyba.se. In our example the file is hosted at https://keybase.io/.well-known/example-proof-config.json.

Will this always require manual step (sending config by e-mail) or is there some automation planned?

Re: Mastodon and Keybase

#3
post #2

From: https://keybase.io/docs/proof_integration_guide > To send us the config, you can send us the public URL for your config file or attach it directly in a Keybase chat message to @mlsteele or email miles@keyba.se. In our example the file is hosted at https://keybase.io/.well-known/example-proof-config.json . Will this always require manual step (sending config by e-mail) or is there some automation planned?

Assuming my understanding of this is right, I can't see Chris and team publishing an automated platform for proof integration until they find a solution against impersonating established platforms.

Edit: Disregard, chris/malgorithms answered above.

Re: Mastodon and Keybase

#4
post #2

From: https://keybase.io/docs/proof_integration_guide > To send us the config, you can send us the public URL for your config file or attach it directly in a Keybase chat message to @mlsteele or email miles@keyba.se. In our example the file is hosted at https://keybase.io/.well-known/example-proof-config.json . Will this always require manual step (sending config by e-mail) or is there some automation planned?

Good q - this step will likely be automated soon. Still, there will always be one final step of our approving any integration, otherwise there would be 10,000 pr0n sites or ad sites. (We mention this in the FAQ.) But we can automate everything up to turning it on.

For now, we want to talk to everyone working on integrations, so we can see what steps are working and what are confusing, what could be improved, etc. So we're talking to everyone doing an integration.

Re: Mastodon and Keybase

#5
I wonder if the Mastodon community will pick up Keybase chat as the de facto chat option with this integration in place. Chat or private messaging has always been considered the weak link of the fediverse since it's easy for bad servers to mishandle "private" toots.

Re: Mastodon and Keybase

#7

I wonder if the Mastodon community will pick up Keybase chat as the de facto chat option with this integration in place. Chat or private messaging has always been considered the weak link of the fediverse since it's easy for bad servers to mishandle "private" toots.

Do you mean for encryption or do you mean using their servers also?

Re: Mastodon and Keybase

#8
This sucks -- not all Mastodon instances will be able to use this. It's subject to approval by keybase, ensuring only big instances can use this. A step backwards a proper decentralized network…

Re: Mastodon and Keybase

#9
post #8

This sucks -- not all Mastodon instances will be able to use this. It's subject to approval by keybase, ensuring only big instances can use this. A step backwards a proper decentralized network…

I would imagine they're happy to support small instances if they have a legitimate userbase... why not ask them and report back?

Re: Mastodon and Keybase

#10
post #6

I never understood keybase as a useful product. What do you use keybase for?

I think their goal is to do everything (or a large subset of things) Slack/Google Drive/GitHub can do, but with end-to-end encryption and easy discovery (look someone up no matter where on the internet you know them from).
Post reply on HN