telegram

type CallbackQuery ¶

type CallbackQuery struct {
	ID      string   `json:"id"`
	From    *User    `json:"from"`
	Message *Message `json:"message"`
	Data    string   `json:"data"`
}

CallbackQuery is an inline-button tap (used for the delete confirmation).

type Chat ¶

type Chat struct {
	ID int64 `json:"id"`
}

type Client ¶

type Client struct {
	// contains filtered or unexported fields
}

Client talks to one bot (identified by its token). It's cheap to construct and safe for use from the single bot loop plus the occasional handler-driven send.

func NewClient(token string) *Client

func (c *Client) AnswerCallback(ctx context.Context, id, text string) error

func (c *Client) EditMenu(ctx context.Context, chatID, messageID int64, html string, rows [][]InlineButton) error

func (c *Client) GetMe(ctx context.Context) (*User, error)

func (c *Client) GetUpdates(ctx context.Context, offset int64, timeout int) ([]Update, error)

func (c *Client) SendDocument(ctx context.Context, chatID int64, filename, caption string, r io.Reader) error

func (c *Client) SendMenu(ctx context.Context, chatID int64, html string, rows [][]InlineButton) error

func (c *Client) SendMessage(ctx context.Context, chatID int64, html string) error

func (c *Client) SendPhoto(ctx context.Context, chatID int64, filename, caption string, r io.Reader) error

type InlineButton ¶

type InlineButton struct {
	Text         string `json:"text"`
	CallbackData string `json:"callback_data"`
}

InlineButton is one inline-keyboard button (label + callback payload).

type Message ¶

type Message struct {
	MessageID int64  `json:"message_id"`
	From      *User  `json:"from"`
	Chat      Chat   `json:"chat"`
	Text      string `json:"text"`
}

Message is the subset of a Telegram message the bot acts on.

type Panel ¶

type Panel interface {
	ListUsers() ([]model.User, error)
	CreateUser(name string, dataLimit, expireAt int64) (*model.User, error)
	DeleteUser(id int64) error
	SetUserEnabled(id int64, enabled bool) error
	ResetTraffic(id int64) error
	BackupManifest() backup.Manifest
	Location() *time.Location
}

Panel is the slice of the core Manager the bot drives. Defining it here (rather than importing core) keeps the dependency one-way — core never imports telegram — and makes the bot trivially testable with a fake.

type Service ¶

type Service struct {
	// contains filtered or unexported fields
}

Service is the running bot: it long-polls for updates and pushes scheduled backups. The whole UI is inline buttons — the only text a user ever types is "/start <code>" to link, and (when prompted) a new user's name. It re-reads settings every cycle, so enabling/disabling, rotating the token, or changing the schedule all take effect without a restart.

func New(panel Panel, st *store.Store, dataDir string) *Service

func (s *Service) Run(ctx context.Context)

type Update ¶

type Update struct {
	UpdateID int64          `json:"update_id"`
	Message  *Message       `json:"message"`
	Callback *CallbackQuery `json:"callback_query"`
}

Update is one polled event: a message or a callback-query (inline button tap).

type User ¶

type User struct {
	ID        int64  `json:"id"`
	Username  string `json:"username"`
	FirstName string `json:"first_name"`
}

User / Chat carry only the identifiers the bot needs.