3 ms·

Open VSX (and perhaps VS Code Marketplace) might consider adding support for identity verification through Keyoxide[0]. This would allow interested parties to e

Open VSX (and perhaps VS Code Marketplace) might consider adding support for identity verification through Keyoxide[0]. This would allow interested parties to easily determine whether the user bung87 on Open VSX and the user bung87 on VS Code Marketplace are really the same person and not just someone claiming the same username. There is already support for linking Keyoxide to one's GitHub account and even Hacker News, among other service providers. [0] https://docs.keyoxide.org/advanced/for-service-providers/ https://docs.keyoxide.org/advanced/for-service-providers/

Jarwain 4y ago
Haven't heard of keyoxide before but it looks neat! Reminds me of keybase but decentralized and more focused!
Yolta 4y ago
Main Keyoxide dev here. That's an interesting suggestion, could be very useful! I don't have much experience with Open VSX or VS Code Marketplace. Do they have APIs for accounts?
- nybble41 4y ago
  I'm not affiliated with either, but from looking at some of the extension pages on Open VSX it appears they use GitHub accounts exclusively for publishers—so that part is already handled by the existing GitHub/Keyoxide integration. For VS Code Marketplace, the publisher pages do include a description section which could be used for the identity proof but there doesn't seem to be a (documented) REST API.
- ta8645 4y ago
  Hi there, I took a look at your site home page and docs, and still can't figure out what it is, or why someone would want to use it. Do you have a link to a 10,000 foot overview / simple use-case explanation, for a short-bus person such as myself?
  - masterofmisc 4y ago
    Good overview is here: https://docs.keyoxide.org/getting-started/what-is-keyoxide/ https://docs.keyoxide.org/getting-started/what-is-keyoxide/ From that page: "Keyoxide allows you to prove "ownership" of accounts on websites, domain names, IM, etc., regardless of your username. That last part is important: you could, for example, be 'alice' on Lobste.rs, but '@alice24' on Twitter. And if your website is 'thatcoder.tld', how are people supposed to know that all that online property is yours? Of course, one could opt for full anonymity! In which case, keep these properties as separated as possible. But if you'd like these properties to be linked and, by doing so, establish an online identity, you'll need a clever solution. Enter Keyoxide. When you visit someone's Keyoxide profile and see a green tick next to an account on some website, it was proven beyond doubt that the same person who set up this profile also holds that account."
    - ta8645 4y ago
      Thank you. That's easy enough to understand, even for me ;-) The only piece that might use a bit more illumination, is what kind of people are likely to use Keyoxide to check on your proof of ownership once you've set it up, and why they would do so.

Jarwain 4y ago

Haven't heard of keyoxide before but it looks neat! Reminds me of keybase but decentralized and more focused!

Yolta 4y ago

Main Keyoxide dev here. That's an interesting suggestion, could be very useful! I don't have much experience with Open VSX or VS Code Marketplace. Do they have APIs for accounts?

nybble41 4y ago
I'm not affiliated with either, but from looking at some of the extension pages on Open VSX it appears they use GitHub accounts exclusively for publishers—so that part is already handled by the existing GitHub/Keyoxide integration. For VS Code Marketplace, the publisher pages do include a description section which could be used for the identity proof but there doesn't seem to be a (documented) REST API.
ta8645 4y ago
Hi there, I took a look at your site home page and docs, and still can't figure out what it is, or why someone would want to use it. Do you have a link to a 10,000 foot overview / simple use-case explanation, for a short-bus person such as myself?
- masterofmisc 4y ago
  Good overview is here: https://docs.keyoxide.org/getting-started/what-is-keyoxide/ https://docs.keyoxide.org/getting-started/what-is-keyoxide/ From that page: "Keyoxide allows you to prove "ownership" of accounts on websites, domain names, IM, etc., regardless of your username. That last part is important: you could, for example, be 'alice' on Lobste.rs, but '@alice24' on Twitter. And if your website is 'thatcoder.tld', how are people supposed to know that all that online property is yours? Of course, one could opt for full anonymity! In which case, keep these properties as separated as possible. But if you'd like these properties to be linked and, by doing so, establish an online identity, you'll need a clever solution. Enter Keyoxide. When you visit someone's Keyoxide profile and see a green tick next to an account on some website, it was proven beyond doubt that the same person who set up this profile also holds that account."
  - ta8645 4y ago
    Thank you. That's easy enough to understand, even for me ;-) The only piece that might use a bit more illumination, is what kind of people are likely to use Keyoxide to check on your proof of ownership once you've set it up, and why they would do so.