Discourse Keybase Proof

[kb_xgess (Alex Gessner)]

hell yeah! nice work.

[emanuele (Emanuele Tamponi)]

And you can see it in Discourse too! You might want to try to revoke it from there to see if it works (you should see a “Revoke” button too)

[Avamander]

Just mentioning that Privacy Badger blocks the Keybase proof status badge, so it would be nice if its alt-text could contain the status itself for those users.

[Falco]

Revoking works, just tested and then re-did the proof. Amazing work!

I have a lot of feedback for both Keybase and the plugin, specially UX which is very rough all around.

I will take some time and write those down later today.

[Avamander]

I also have to mention that unlike all the other proofs (for example GitHub) the current Discourse proof contains no nice description on how to verify the proof command-line. It just feels a bit too laconic.

[emanuele (Emanuele Tamponi)]

that would be good but it would require some refactoring and additions to the plugin would you mind adding it to the issues of the GitHub repo so that we don’t lose track of it? thank you!

[Falco]

Discourse plugin feedback

for @emanuele

The plugin should have some discoverability in Discourse. Also, after the user does the identity dance, that should be visible for other users, as this is the plugin raison d’être, to show off that this user on this forum is thattwitterguy, thisredditaccount, thoseHNaccounts, etc.

The Keybase extension on Twitter adds this to a profile:

We could do something similar for user-cards:

And, behind a site setting to posts:

Also, on the user profile we should remove the current UI:

And break it into two things,

First to show the identities:

And then on profile to revoke proofs:

When the user doesn’t have a Keybase linked yet it should redirect the user to Keybase to start the process.

Which brings me to

Keybase Feedback

for @kb_xgess

We desperately need a straightforward way to push the user to the appropriate place in Keybase where he can start the proof, aka this screen:

Looks like you guys do all this on modals, that lack a proper URL and can’t be linked

And we need to come up with a guide for Discourse admins about how they can submit their sites for Keybase approval.

[emanuele (Emanuele Tamponi)]

Hi @Falco,

as you might have noticed, I don’t have much time at the moment to work on this plugin anymore.

Anyone that has interest, please feel free to fork / provide PRs / create a new one.

Thanks for the feedback

[nealmcb (Neal McBurnett)]

Thanks, @emanuele and everyone else for all your work here!

I just added three issues to the Issues at etamponi/discourse-keybase-proofs-plugin. Two are simple attempts to capture a few of the issues raised here.
The third is the one I’m most curious about. Can someone (here or there) document the current status, what works, how you try it out, what doesn’t work, etc? I.e.:
https://github.com/etamponi/discourse-keybase-proofs-plugin/issues/6

[Avamander]

@kb_xgess

I think that if Keybase provided a way to link to the modal someone might have bigger interest in finishing this.

[kb_xgess (Alex Gessner)]

All right! We have implemented this in the recent release of the Keybase client and updated our docs appropriately. So, if you have Keybase installed on your device the following link should deeplink you right into the flow: keybase://profile/new-proof/mastodon.social/megafauna

[kb_xgess (Alex Gessner)]

@Avamander @nealmcb @emanuele please let me know if I can help with anything to push this over the finish line.

[nealmcb (Neal McBurnett)]

고맙습니다, 여러분. 요약을 드리면 다음과 같습니다:

• 여기의 목표는 무엇인가요? 우리는 세계가 **허위 정보(disinformation)**로 넘쳐난다는 것을 알고 있습니다. 저는 이것이 인터넷 사용자가 인터넷 콘텐츠 뒤에 누가 있는지 알 수 있도록 돕는 데 중요한 단계라고 생각합니다. Keybase는 요즘 정체성을 확립하고 콘텐츠를 안전하게 보호하는 훌륭한 방법으로서 점점 더 많은 주목을 받고 있으며, 따라서 여러분이 이 플러그인을 마무리하여 사람들이 Keybase를 통해 자신의 Discourse 프로필과 관련 콘텐츠를 소유권 주장(claim)할 수 있도록 도와주기를 바랍니다.
• @emanuele 님은 위에서 @Falco 님이 테스트한 대로 필요한 기능을 대부분 지원하는 **discourse-keybase-proofs-plugin**을 만들었습니다. 해당 GitHub 이슈에서 언급했듯이, 발견성(discoverability), 문서화 및 테스트에 대한 일부 세밀한 작업이 필요합니다.
• @kb_xgess 님은 @Falco 님의 요청에 따라 플러그인이 사용자와 협력하여 새로운 증명을 확립하는 것을 더 쉽게 만드는 새로운 Keybase 기능을 시연했습니다. 즉, 인증 플로우로 사용자를 딥링크(deeplink)하는 Keybase URL입니다. 그가 제공한 예시 URL은 mastodon.social 서버의 megafauna 사용자를 위한 것입니다. 단순히 경로 요소를 적절히 설정되고 인증된 Discourse 서버의 사용자를 가리키도록 변경하면 됩니다.

Emanuele 님은 더 이상 Discourse 플러그인 작업에 적극적으로 참여하지 않으므로, 누군가가 이를 인수하여 Falco 님이 권장하는 UX 요소를 추가하고, 새로운 URL을 활용하며, 테스트 서버를 인수해야 합니다.

그동안, yoursite.com/.well-known/keybase.txt에 하나 이상의 증명을 통해 소유권을 증명하는 “구식 Keybase 방식”(예: Keybase CLI로 생성된 keybase prove https meta.discourse.org)을 사용할 수 있음을 참고하시기 바랍니다. 이와 관련하여 플러그인의 선택적 개선 사항이 있습니다. 특정 Discourse 서버가 인증받아야 하는 필요성을 우회하기 위해, 해당 범용 HTTP 증명 방식을 지원하도록 추가하는 것입니다(위에서 Discourse Keybase Proof - #36 by pfaffman 에서 논의됨).

참여해 주셔서 감사합니다!

[codinghorror (Jeff Atwood)]

Keybase가 Zoom에 의해 인수합병(acqui-hire)되었고, 현재 Keybase는 명확한 미래가 없는 좀비 제품이므로 이 문제를 닫겠습니다.