search

keybase / keybase-issues

A single repo for managing publicly recognized issues with the keybase client, installer, and website.
902 stars 37 forks source link

Support All Mastodon Instances #3385

Open jonaharagon opened 5 years ago

jonaharagon commented 5 years ago

Mastodon support (#2948) seems to have been added today 🎉

Unfortunately, it seems to only be supported on a couple arbitrary instances (https://github.com/tootsuite/mastodon/pull/10013#issuecomment-468790773) rather than any instance updated to at least 2.8.0rc1 when Keybase support was added to Mastodon. This defeats the entire point of Mastodon, which is to promote decentralization, so the recent addition of support is really an unacceptable solution. Please add the ability to verify an account on any up-to-date Mastodon instance.

kgamecarter commented 5 years ago

I need verify pawoo.net. Mastodon hosted by PIXIV. Please support.

ValiantNinja commented 5 years ago

I'd love to +1 this, it's extremely frustrating to be limited to five specific instances when Mastodon is built around the Fediverse. Not everyone is using these instances and it'd be nice to verify that whatever instance I or anyone decides to use, public or private instance. The five listed are big, but they're not the only thing Mastodon has to offer. This might be an experimental decision but if it's planned to stay for the foreseeable future, it's a very bad idea.

phoe commented 5 years ago

Mastodon is a decentralized service by design. Please support that idea by allowing any Mastodon instance to utilize your functionality.

Amolith commented 5 years ago

It doesn't really make sense to me that only 6 (at the time of writing) Mastodon instances are supported for this. That defeats the whole purpose and makes it seem like those are the only instances "worth" joining because they're . . . I don't know . . . verified, sponsored, endorsed, whatever by Keybase. It makes a lot more sense to have one entry for Mastodon, be given some text to paste into a toot, click the hamburger menu, copy the link, then paste it into Keybase. I'm not sure how this verification or proof system is implemented right now but I don't see why only six instances are listed as options.

nathanblaubach commented 5 years ago

They have addressed this issue in a toot:

https://mastodon.social/@keybase/101903490896785857

vpzomtrrfrt commented 5 years ago

What's up with this then? https://microblog.shivering-isles.com/@sheogorath/101935019620151357

phoe commented 5 years ago

Via https://keybase.io/blog/keybase-proofs-for-mastodon-and-everyone :

Like a Mastodon instance, we reserve the right to work with whichever partners we prefer. We specifically will avoid at least these sites:

  • (...)
  • sites which feel tiny and spammy. We don't want 10,000 partners with 5 members each; if you run, say, a family or apartment website, you don't need to do this integration. Just prove ownership of the domain in the old Keybase way, putting your family's proofs in yoursite.com/keybase.txt

I assume that if I run a personal Mastodon instance on my own server for me only, it will be impossible for me to prove my identity via Keybase.

junderw commented 5 years ago

it will be impossible for me to prove my identity via Keybase.

  1. mymastodon.xyz hosts your mastodon.
  2. There's only one user. You.
  3. You perform a domain proof for mymastodon.xyz
  4. If people can't put 2 and 2 together, I fear for the future of society.

Yeah, you don't get the flashy "KEYBASE USER XYZ" badge on your Mastodon, but if the goal is to prove the link, the UI shouldn't matter.

jonaharagon commented 5 years ago

@junderw one of the issues is that Keybase supports encrypted chats based on your usernames. If phoe isn't able to add their Mastodon profile to their Keybase account, people won't be able to send a message to @phoe@mymastodon.xyz in the Keybase client or CLI.

Of course, they could just send a message to mymastodon.xyz in Keybase, but that would require the sender to specifically notice that phoe is on a single-user instance and isn't allowed to have their Mastodon profile on their Keybase profile. And that's not even considering the scenario where a domain is shared with a family or some friends, and there's 3 or 4 people that are using it, can't verify their profiles, but wouldn't necessarily want to receive messages sent to just the domain.

In an ideal world, if I notice a Mastodon user I want to start an encrypted chat with, I should be able to quickly do so in Keybase with their username alone without having to look at their profile to see if Keybase whitelisted their server beforehand.

If Keybase was just an identity-linking tool this wouldn't be an huge issue, but Keybase apparently wants to become the next Slack, GitHub, etc., so they need to consider scenarios like this.

Laurelai commented 5 years ago

Why are you deliberately excluding small instances when most of the fedverses instances are small. This isnt mastodon integration this is integration with specific instances. Which isnt what anyone wanted.

malgorithms commented 5 years ago

Why are you deliberately excluding small instances

to clarify (and @junderw asked the question above, quoting the FAQ):

keybase isn't deliberately excluding small instances; we're working through getting all interested instances added (we're up to over 70 today, and we're increasing our automation of it), and making sure everything goes smoothly. This includes small instances, so if you run a mastodon instance with 5 people, that's fine. Our goal from the beginning has been that Mastodon instances can choose to use (or not use) the Keybase integration, and Keybase will choose to support them back. (With some illegality / advertisement exemptions; just like a mastodon instance might not want to use Keybase, we're not interested in some rare instances.).

That comment in Keybase's FAQ was to dissuade people from programming Keybase integrations from scratch, if all they've got is a personal website. With Mastodon the integration is done, so we will include you if you're interested.

Things were not getting flipped on all at once because there's still a bit of manual work we need to do for each instance. Also there are subtler details; we ship an app on all platforms, not just a website, and people update the app at their own rates. Bombarding particularly old versions of our app with suddenly all these new proof types causes UX problems. So we've had to ease into it.

Again, if anyone is missing and wants to get up faster in the queue, the blog post mentions who on the team to ping. We'll get you in there!

Laurelai commented 5 years ago

Ok thank you.

rugk commented 5 years ago

Also related: Do not list all domains in this huge list of instances, an UX issue: https://github.com/keybase/keybase-issues/issues/3393