Hi all, I don't have time lately to work on this project, sorry about that. But I want to add channel feature, so I'll have to find it. Expect test branch to be ready in several days (no more than one weak, I hope).
what works with channels: 'channel_list', 'history <channel>' and 'post <channel>'. At least I hope, that it works
what doesn't work: receiving updates about channels (even about messages you sent to channels), and binlog mode of telegram-cli is probably broken
command 'msg <channel>' currently returns server error. I think that it is some feature that is turned off on server now, so I don't want to use msg command instead of post
although there are two different methods now: dialog_list and channel_list. Probably I will need to merge their to one list
There is one more problem, that is interface problem. Message ids. In channels message ids are independent. So first message in every channel has id 1, second id2 and so on. Previous way with using message if for forward, photo load and so on does not work well in this case. It's rather easy to make some kind of long message ids for bots (for example "channel_id:local_id_in_channel", or just 64 bit long), but it's not very easy to use this way if you use this client as main telegram client (as I do). So I need some idea, how to fix it.
Current idea: each message will have permanent_id and temp_id. permanent_id is big (at least 64 bit, but I think it will be 128bit) number (or even string, I think it's better alternative). it is garanteed that you can access message by it's permanent id after telegram-cli restart, and probably (unless it is message to secret chat) after relogin. It's intended use for bots, since they are stubborn enougth to copy long msg id's. For other people there is alternative: temp id. These ids are given, when client receives new message and are started from 1. So they will remain valid only until restart of client, but will be much shorter and more easy to use.
Next iteration of test code commited to test branch on github. What works: I hope it doesn't crash. If it does, please send me backtrace. All methods should work. If not, please let me know. message ids are now temporary. To use permanent ids use --permanent-msg-ids. Also it may be useful to use --permanent-peer-ids. Probably you can send message to peer by permanent id even without [-W] key. What doesn't work: binlogs. Sometimes update duplicates, especially when you send message. Also json, lua and python don't work. It (at least json and lua) will be fixed in one of next commits. Please note, that msg_id from now on will be string, not number.
It's normal, that client writes lines like 'User deleted user#124001773'. It's just some strange stuff, that server sends inside answer on dialog_list and channel_list queries