Add Telegram

Goldstein

Click “New group”, enter group name, add any dummy user as a second (we can suggest adding Keyoxide bot, it doesn’t really matter).
In your new group, click on three dots → manage group → group type → public and choose any username.
In manage group → permissions uncheck all the checkboxes, so nobody but you can send a message.
Set the description to fingerprint.
Done! Now my PR would recognize this group as a proof of your identity.

Goldstein

Step 3 is optional, but probably makes sense, since proof will be posted in public.

yarmo

Must have done something wrong on my first attempt. Yup, this works, thanks for the instructions!

yarmo

Ok, tested with your code and it works fine! Marvelous work, the method you are proposing seems solid to me. I'll need to think about it a bit more, see if I can find flaws but we'll likely go this route.

Now let's refine that PR and get it merged!

yarmo

Goldstein There’s an another interesting question: what should be verified? Telegram username is user-readable, but also easy to change. Telegram id is immutable, but is kinda useless

I am still a bit divided on this.

Username pros:

can directly be used to make the personal URL
is human readable
easy to find from the clients

Username cons:

not immutable (-> people changing their username just need to update the claim)

ID pros:

immutable
username for personal URL is still available from the API call (see https://community.keyoxide.org/d/34-add-telegram/16)

ID cons:

not human readable
hard to find from the clients

Looking at the pros and cons, I think the username is the best fit. All opinions welcome on this one (pinging @wiktor)

---update

Do we need anything at all? If DOIP detects a single administrator, that will automatically be the telegram account to verify. If for some reasons there are multiple admins (people helping others with creating their proof group?), the claim MAY add a username= parameter or a id= parameter simply to let DOIP know what account to verify.

---update2

if (admin.status === 'creator') {
    creator = admin.user.username
}

Isn't this the argument we don't need anything at all? Surely, there can only be one creator, so that must be the account to verify.

Goldstein

Yes, we could include only the channel link, but I don’t like that it’s hard to open the user account with only a channel link. Maybe I’d even suggest a reverse strategy:

https://t.me/goldsteinq?proof=hoCheiya5tie8aevei5da4xa4aequ4lo

which leads to a user account when clicked (and Keyoxide can easily form a proof link to display in UI).

yarmo

Goldstein

I'm so glad you are proposing this strategy, I was thinking of the same thing! It has an upside and a downside.

Upside: you link straight to where you want to be, the profile
Downside: it will be near impossible just by clicking the link to find the proof for manual verification

I want to believe that the downside is mitigated because, well, that's what Keyoxide is for! But as you mentioned, Keyoxide will show a link to the actual proof for manual verification. If you are a hardcore user that skips Keyoxide's UI, well then you probably have the knowledge to figure out that the ?proof= parameter represents the public group with the proof.

I think I prefer this https://t.me/USERNAME?proof=GROUPNAME strategy.

Goldstein I’d also like to note that the channel/group usernames, just like, ehm, user usernames are mutable.

True, hadn't considered that. But let's face it, you really have to try and sabotage yourself to change the name of the proof group. If one wants to, great! Their responsibility to update their claim. The documentation will state what happens in such cases.

Goldstein

I’d also like to note that the channel/group usernames, just like, ehm, user usernames are mutable.

yarmo

Looking at the https://t.me/USERNAME source code, they actually do use URIs!

tg://resolve?domain=USERNAME

Since https://t.me/USERNAME appears to automatically attempt to open that URI, I don't it's worth it to prefer the URI over the URL. If the verifier doesn't have a native Telegram app, the URI will be useless, at least the URL gives them some information.

Goldstein

Yes, they do use URIs, but I don’t like them for the same reason.

While testing, I noticed one more interesting moment: it takes some time for description change to reflect in the Bot API. Perhaps documentation should mention that check could fail for the first few minutes or so.

yarmo

Did some more testing but it looks all good to me. Just merged the PR 🚀

https://codeberg.org/keyoxide/doipjs/pulls/24

Are you ok with me thanking you in the changelog?

Goldstein

Yes, of course! Probably Keyoxide UI needs to be updated too?

yarmo

We'll just need to release a new doip.js version and update that dependency in Keyoxide. Other than that, doip.js really handles all the work, Keyoxide is mostly just UI.

« Previous Page