apepenkov

Results 14 comments of apepenkov

That's not a bug. Asking user for password wasn't implemented in gui.py, and if you would like to do it - you can create a PR.

![IMG_20200127_151847](https://user-images.githubusercontent.com/39992738/73174277-6784d300-4118-11ea-8cc9-430abf704fa6.jpg) I guess, get_messages shall be [TotalList, Message]

functions.messages.GetCommonChatsRequest ![изображение](https://user-images.githubusercontent.com/39992738/74944563-4c4f6f80-5407-11ea-99ed-c9c65199b8ad.png) add int

same for functions.photos.GetUserPhotosRequest. I guess to TypeInputUser shall be added string(for username) int (for id), User (currently it's not there)

> @apepenkov Not sure if those should be included, since the raw API obviously doesn't take ints, it's just telethon converting them. Would be better to reduce the necessity of...

![image](https://user-images.githubusercontent.com/39992738/81498324-ee774900-92cc-11ea-88fc-0ddc240de0f4.png) send_message doesn't accept types.InputPhoto as file

send_message doesn't accept types.InputMediaInvoice as file ![image](https://user-images.githubusercontent.com/39992738/82490237-a980bd00-9aeb-11ea-8974-9c5af1957620.png)

Getting message from inline doesn't really work, unless peer is known. Not sure if it should. Needs to be investigated

For the editing of inline messages - there are multiple options what to do with it. - leave users to use raw api - create separate friendly method for editing...

Note - message id, that is unpacked from `types.InputBotInlineMessageId`/`types.InputBotInlineMessageId64` (in case of PM or simple chat) is sender's message id, not even bot's.