xelaj/mtproto

In Telegram's MTProto, certain requests requiring InputUser, InputChannel, or InputMedia require a specific access_hash parameter. Telegram does not publicly document the internal structure or the exact algorithm used to generate this hash. To use these objects in your API calls, you must first retrieve the hash from a successful response from Telegram.

Methods for obtaining hashes

Resolving a User by Username (InputUser)

You can obtain a user's id and access_hash by resolving their username using the contacts.resolveUsername() method. The resulting Contacts.ResolvedPeer object contains a users slice; the User constructor within this slice holds both the id and the required access_hash.

Resolving a Channel by Invite Link (InputChannel)

[Note: The provided source content ends before detailing the specific implementation for resolving channels via invite links.]

You can interact with Telegram using two patterns:

1. Generic MakeRequest: Pass a specific parameter struct (e.g., <MethodName>Params) to client.MakeRequest. You must then type-assert the result to the expected response object.
2. Typed Helper Methods: Use direct method calls on the client (e.g., client.GetSomeInfo(args)) which are automatically typed according to the TL API specification.

The library handles encryption, key exchange, and session management automatically.

// Pattern 1: MakeRequest
func main() {
    client := &Telegram.NewClient()
    result, err := client.MakeRequest(&telegram.GetSomeInfoParams{FromChatId: 12345})
    if err != nil {
        panic(err)
    }

    resp, ok := result.(*SomeResponseObject)
    if !ok {
        panic("Oh no! Wrong type!")
    }
}

// Pattern 2: Typed Helper Methods
func main() {
    client := &Telegram.NewClient()
    resp, err := client.GetSomeInfo(12345)
    if err != nil {
        panic(err)
    }

    println(resp.InfoAboutSomething)
}

To use the MTProto library for a Telegram bot (which provides access to the full Telegram API instead of the limited Bot API), follow these steps:

1. Create a Bot: Use @BotFather on Telegram to create your bot and obtain a TgBotToken and TgBotUserName.
2. Register an App: Visit my.telegram.org/apps to register your application and obtain an App api_id and App api_hash.
3. Configure Credentials: Populate the required configuration constants in your Go code with your credentials and the appropriate server addresses.
4. Run the Bot: Execute the application using go run main.go.

const (
	// from https://my.telegram.org/apps
	TgAppID       = XXXXX                // integer value from "App api_id" field
	TgAppHash     = "XXXXXXXXXXXX"       // string value from "App api_hash" field
	TgTestServer  = "149.154.167.40:443" // string value from "Test configuration" field
	TgProdServer  = "149.154.167.50:443" // string value from "Production configuration" field

	// from https://t.me/BotFather
	TgBotToken    = "XXXXX"  // bot token from BotFather
	TgBotUserName = "YourBotUserName" // username of the bot
)

If you want to support the mtproto project but do not wish to write Go code, you can contribute through several non-coding activities:

Spread Information

• Write tutorials or reviews: Create cheatsheets, tutorials, or honest reviews on development forums and blogs such as golangbridge, Google Groups, Y Combinator, Habr, or Yandex Zen.
• Social Media: Share the repository link on Twitter, Reddit, Facebook, or other social platforms.
• Word of Mouth: Share the project with colleagues or friends, especially teams working with the Telegram API.

Bug Reports and Questions

• Report Bugs: If you find a bug, create an issue in the repository to help improve stability.
• Ask Questions: Use the issue tracker to ask questions regarding the package's functionality.

Documentation Improvements

• Add missing info: If you discover a non-obvious way to use a feature, contribute that knowledge to the documentation.
• Identify gaps: Inform the maintainers about specific topics not covered by the current docs.

Improve TL Schema

• Add documentation to TL schema: Since the native Telegram TL schema lacks documentation, you can contribute by copying and pasting relevant information from official Telegram documentation into the schema files.

Propose New Ideas

• If you have additional ideas for non-code contributions, submit them via a Pull Request (PR).