GithubHelp home page GithubHelp logo

josepdal / dbteamv1 Goto Github PK

View Code? Open in Web Editor NEW
58.0 12.0 129.0 1.3 MB

Join our new proyect, DBTeamV2 with new tg-cli

Home Page: https://github.com/Josepdal/DBTeamV2

License: GNU General Public License v2.0

Shell 9.73% Lua 90.27%

dbteamv1's Introduction

DBTeamV2 is OUT

New tg-cli, working in all supergroups

https://github.com/Josepdal/DBTeamV2














If you are not interested in tg-cli particular options like invite, del_msg, create groups...

We recommend to you use this API Bot written in lua: https://github.com/RememberTheAir/GroupButler from a very good friend.

DBTeam-bot

A Telegram Bot based on plugins using tg.

Bot Commands

Name Description
bot.lua Plugin to manage channels. Enable or disable channel.
commands.lua Plugin to get info about what the bot can do.
(language)_lang.lua Plugin to install a language in your redis db.
export_gban.lua Plugin to export an installer (gban_installer.lua) or a list of all your bot gbans.
giverank.lua Plugin to manage ranks (admins, mods and guests).
id.lua Plugin to get info about telegram accounts.
moderation.lua Plugin to manage users from chats. Kick, add, ban, unban, gban, ungban, kickme all of this with action by reply, by id and by username.
plugins.lua Plugin to manage other plugins. Enable, disable or reload.
rules.lua Plugin to get chat rules.
settings.lua Plugin to administrate a group/supergroup, you can disable photos, stickers, gifs, links, arabic, flood, spam, lock channel members, audios...
spam.lua Plugin to manage spam at groups and supergroups. When someone write a Telegram link to another group or channel, automatically (for example), plugin delete that user from the channel, and delete his message. Then, send a report to all sudo users in a private message with user info, text message and the name and id of that channel.
version.lua Shows bot version

#Commands Usages

Plugin Usage
bot.lua #bot on: enable bot in current channel.
#bot off: disable bot in current channel.
commands.lua #commands: Show all commands for every plugin.
#commands [plugin]: Commands for that plugin.
export_gban.lua #gbans installer: Return a lua file installer to share gbans and add those in another bot in just one command.
#gbans list: Return an archive with a list of gbans.
gban_installer.lua #install gbans: add a list of gbans into your redis db.
giverank.lua #rank admin (reply): add admin by reply.
#rank admin /: add admin by user ID/Username.
#rank mod (reply): add mod by reply.
#rank mod /: add mod by user ID/Username.
#rank guest (reply): remove admin by reply.
#rank guest /: remove admin by user ID/Username.
#admins: list of all admin members.
#mods: list of all mod members.
#members: list of all channel members.
id.lua #id: Return your ID and the chat id if you are in one.
#ids chat: Return the IDs of the current chat members.
#ids channel: Return the IDs of the current channel members.
#id : Return the member username ID from the current chat.
#whois /: Return username.
#whois (reply): Return user id.
rules.lua #rules: shows chat rules you set before or send default rules.
#setrules : set chat rules. #remrules: remove chat rules and return to default ones.
moderation.lua #add: replying to a message, the user will be added to the current group/supergroup.
#add /: adds a user by its ID/Username to the current group/supergroup.
#kick: replying to a message, the user will be kicked in the current group/supergroup.
#kick /: the user will be kicked by its ID/Username in the current group/supergroup.
#kickme: kick yourself.
#ban: replying to a message, the user will be kicked and banned in the current group/supergroup.
#ban /: the user will be banned by its ID/Username in the current group/supergroup and it wont be able to return.
#unban: replying to a message, the user will be unbanned in the current group/supergroup.
#unban /: the user will be unbanned by its ID/Username in the current group/supergroup.
#gban: replying to a message, the user will be kicked and banned from all groups/supergroups.
#gban /: the user will be banned by its ID/Username from all groups/supergroups and it wont be able to enter.
#ungban: replying to a message, the user will be unbanned from all groups/supergroups.
#ungban /: the user will be unbanned by its ID/Username from all groups/supergroups.
#mute: replying to a message, the user will be silenced in the current supergroup, erasing all its messages.
#mute /: the user will be silenced by its ID/Username inthe current supergroup, erasing all its messages.
#unmute: replying to a message, the user will be unsilenced in the current supergroup.
#unmute /: the user will be unsilenced by its ID/Username in the current supergroup.
#rem: replying to a message, the message will be removed.
settings.lua #settings stickers enable/disable: when enabled, all stickers will be cleared.
#settings links enable/disable: when enabled, all links will be cleared.
#settings arabic enable/disable: when enabled, all messages with arabic/persian will be cleared.
#settings bots enable/disable: when enabled, if someone adds a bot, it will be kicked.
#settings gifs enable/disable: when enabled, all gifs will be cleared.
#settings photos enable/disable: when enabled, all photos will be cleared.
#settings audios enable/disable: when enabled, all audios will be cleared.
#settings kickme enable/disable: when enabled, people can kick out itself.
#settings spam enable/disable: when enabled, all spam links will be cleared.
#settings setphoto enable/disable: when enabled, if a user changes the group photo, the bot will revert to the saved photo.
#settings setname enable/disable: when enabled, if a user changes the group name, the bot will revert to the saved name.
#settings lockmember enable/disable: when enabled, the bot will kick all people that enters to the group.
#settings floodtime : set the time that bot uses to check flood.
#settings maxflood : set the maximum messages in a floodtime to be considered as flood.
#setname : the bot will change group title.
#setphoto : the bot will change group photo.
#lang : it changes the language of the bot.
#setlink : saves the link of the group.
#link: to get the link of the group.
#muteall: mute all chat members.
#muteall : mute all chat members for time.
#unmuteall: remove mute restriction.
#creategroup: create a group with your bot in a command.
#tosupergroup: upgrade your chat to a channel.
#setdescription: change your channel description.
plugins.lua #plugins: shows a list of all plugins.
#plugins / [plugin]: enable/disable the specified plugin.
plugins / [plugin] chat: enable/disable the specified plugin, only in the current group/supergroup.
#plugins reload: reloads all plugins.
version.lua #version: shows bot version.
# Tested on Ubuntu 14.04, for other OSs check out https://github.com/yagop/telegram-bot/wiki/Installation
sudo apt-get install libreadline-dev libconfig-dev libssl-dev lua5.2 liblua5.2-dev libevent-dev make unzip git redis-server g++ libjansson-dev libpython-dev expat libexpat1-dev tmux subversion
# After those dependencies, lets install the bot
cd $HOME #Do not write this if you are using c9 or not root accounts
git clone https://github.com/Josepdal/DBTeam.git
cd DBTeam
./launch.sh install
./launch.sh # Will ask you for a phone number & confirmation code.

You can also use this command to install the bot in just one step.

sudo apt-get update && sudo apt-get upgrade -y && sudo apt-get autoremove && sudo apt-get autoclean && sudo apt-get install libreadline-dev libconfig-dev libssl-dev lua5.2 liblua5.2-dev libevent-dev make unzip git redis-server g++ libjansson-dev libpython-dev expat libexpat1-dev tmux subversion -y && cd $HOME && rm -rf DBTeam && rm -rf .telegram-cli && git clone https://github.com/Josepdal/DBTeam.git && cd DBTeam && ./launch.sh install && ./launch.sh

Then, you have to install a bot language like this:

#install english_lang
#lang en

Enable more plugins

See the plugins list with #plugins command.

Enable a disabled plugin by #plugins enable [name].

Disable an enabled plugin by #plugins disable [name].

Those commands require a privileged user, privileged users are defined inside data/config.lua (generated by the bot), stop the bot and edit if necessary.

Keep the bot always running

If your bot stops sometimes due to crashes or freezes in telegram-cli, and you want to keep it running all the time you can start the bot this way. Note that it only will be recovering the bot if the problem is a telegram-cli issue, it won't recover of vps hibernation or system problems.

You need to have tmux or screen installed. Both are pre installed in almost all linux distributions, but in case you don't you can get it this way: sudo apt-get install tmux screen
Tmux and screen are two different terminal multiplexer programs that will be needed in order to use the script.

You can use steady.sh script in two ways: with tmux(recomended) or with screen. You may also mix them, but it is not assured to work.

####Using tmux To start the script with tmux, just run this command in your Bot folder:

tmux new-session -s script "bash steady.sh -t"

Where tmux is the terminal multiplexer, new-session -s means that we want to open a tmux session with a name, script is the name of that session and with "bash steady.sh -t" we are launching steady.sh with the argument -t (tmux mode).
The script will launch and it will show you if there is any error.

The bot will be running in the background even if SSH session closes. You can just detach (get out) the tmux session by typing Control+b and d

If you want to get inside the script session again, type: tmux attach-session -t script
If you want to get into Bot session (reading the messages), write: tmux attach-session -t DBTeam

You can stop the script by pressing Control+C in the script session. Alternatively, you can tmux kill-session -t script or also killing all tmux processes killall tmux. Remember that you can exit without closing the session with Control+b and d.

####Using screen Firstly kill all the telegram-cli and screen processes running on your vps:

killall screen
killall telegram-cli

Then you have to launch the script (you need to be in DBTeam folder):

screen bash steady.sh -s

Now you can close the SSH session and it will be running in the background. You can also just detach the screen by typing Control+a and Control+d

If you want to get inside the session again, type: screen -x
You will be shown a message saying "There are several suitable screens on:" and two lines similar to this ones:

12345.xxxxxxx  (Date)  (Detached)                 
67890.pts.xxx  (Date)  (Detached)           

If you write: screen -x 12345 (the number above), you will be in the telegram session of the bot reading the messages. Writing: screen -x 67890 (the number below), you will be in the script screen. Remember that you can go back with Control+a and Control+d.

To stop all the processes related to the bot and the script, type:

killall screen
killall tmux
killall telegram-cli

Bot status is checked every 10 seconds (default) and printed on the screen. You can change this value editing the script ($RELOADTIME).

The script has more usages, like starting sessions detached. Type bash steady.sh -h to see all the commands and information about the script.

It is also possible to use steady.sh for other bots. You only need to change $BOT variable. This can be usefull to have more bots in the same server (this feature is only avaliable in tmux mode)

Run it as a daemon

If your Linux/Unix comes with upstart you can run the bot by this way

$ sed -i "s/yourusername/$(whoami)/g" etc/telegram.conf
$ sed -i "s_telegrambotpath_$(pwd)_g" etc/telegram.conf
$ sudo cp etc/telegram.conf /etc/init/
$ sudo start telegram # To start it
$ sudo stop telegram # To stop it

DBTeam support and development groups

https://telegram.me/joinchat/C142CD3GT-26EFdxu_lW0g https://telegram.me/joinchat/C142CD5wPizyWWg4R3TJLw https://telegram.me/joinchat/BbkmWz2Ozu7EakNpixOJ5A

DBTeam developers

https://telegram.me/Josepdal https://telegram.me/MaSkAoS

Yagop developer and bot development group

https://telegram.me/Yago_Perez https://telegram.me/joinchat/ALJ3izwBCNXSswCHOKMwGw https://gitter.im/yagop/telegram-bot

Other interesting sites

Donate button http://taligram.org

Contact us

You can contact us in groups said before but if you have an issue please open one.

dbteamv1's People

Contributors

3iran avatar a7f avatar buzz3rs avatar dbteam-es avatar f3ociety avatar gtrabal avatar iicc1 avatar johnmultidroid avatar josepdal avatar kingjan123 avatar lrs955 avatar mustafajr avatar nimagame avatar synk0 avatar tiagodanin avatar wathiq-iq avatar xxdamage avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

dbteamv1's Issues

qustion

@iicc1 Boy If VPS is Rebooted steady.sh can Re launch Bot ??
I want Write reboot with steady.sh but i want know this script can be Re launch Bot after reboot ??
this is not creazy Ideas i want Write reboot vps at 6:00 Morning :)
all people is sleeped its good for Refresh Vps 👻
so say me Boy If VPS is Rebooted steady.sh can Re launch Bot or not!
thank you!

BOT RUNNING! {steady.sh}

CHECKING PROCESSES...
RUNNING 1 TELEGRAM-CLI PROCESS
ATTACHING TMUX AS DAEMON...
NEW TELEGRAM-CLI PROCESS: 3912

TIMES CHECKED AND RUNNING: 0
TIMES FAILED AND RECOVERED: 0

BOT RUNNING!
TIMES CHECKED AND RUNNING: 1
TIMES FAILED AND RECOVERED: 0

BOT NOT RUNING, TRYING TO RELOAD IT...
TIMES CHECKED AND RUNNING: 1
TIMES FAILED AND RECOVERED: 1

BOT NOT RUNING, TRYING TO RELOAD IT...

install

sh install
Already up-to-date.
patching file tg/configure.ac
Hunk #1 FAILED at 61.
Hunk #2 FAILED at 193.
2 out of 2 hunks FAILED -- saving rejects to file tg/configure.ac.rej
./launch.sh: línea 100: autoconf: orden no encontrada
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in /home/wunerrahdev/DBTeam/tg': configure: error: C compiler cannot create executables See config.log' for more details
Error. Exiting.

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by telegram-cli configure 1.0, which was
generated by GNU Autoconf 2.69. Invocation command line was

$ ./configure

---------

Platform.

---------

hostname = wunerrahdev-HP-Compaq-8000-Elite-CMT-PC
uname -m = x86_64
uname -r = 4.4.0-116-generic
uname -s = Linux
uname -v = #140~14.04.1-Ubuntu SMP Fri Feb 16 09:25:20 UTC 2018

/usr/bin/uname -p = unknown
/bin/uname -X = unknown

/bin/arch = unknown
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown

PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /usr/sbin
PATH: /usr/bin
PATH: /sbin
PATH: /bin
PATH: /usr/games
PATH: /usr/local/games

-----------

Core tests.

-----------

configure:2755: checking for gcc
configure:2771: found /usr/bin/gcc
configure:2782: result: gcc
configure:3011: checking for C compiler version
configure:3020: gcc --version >&5
gcc (Ubuntu 4.8.5-2ubuntu1~14.04.1) 4.8.5
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

configure:3031: $? = 0
configure:3020: gcc -v >&5
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.8/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.8.5-2ubuntu114.04.1' --with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.8 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.8 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libmudflap --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.8-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.8.5 (Ubuntu 4.8.5-2ubuntu1
14.04.1)
configure:3031: $? = 0
configure:3020: gcc -V >&5
gcc: error: unrecognized command line option '-V'
gcc: fatal error: no input files
compilation terminated.
configure:3031: $? = 4
configure:3020: gcc -qversion >&5
gcc: error: unrecognized command line option '-qversion'
gcc: fatal error: no input files
compilation terminated.
configure:3031: $? = 4
configure:3051: checking whether the C compiler works
configure:3073: gcc conftest.c >&5
/usr/bin/ld: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.27' not found (required by /usr/bin/ld) collect2: error: ld returned 1 exit status configure:3077: $? = 1 configure:3115: result: no configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "telegram-cli" | #define PACKAGE_TARNAME "telegram-cli" | #define PACKAGE_VERSION "1.0" | #define PACKAGE_STRING "telegram-cli 1.0" | #define PACKAGE_BUGREPORT "" | #define PACKAGE_URL "" | /* end confdefs.h. */ | | int | main () | { | | ; | return 0; | } configure:3120: error: in /home/wunerrahdev/DBTeam/tg':
configure:3122: error: C compiler cannot create executables
See `config.log' for more details

----------------

Cache variables.

----------------

ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_LIBS_set=
ac_cv_env_LIBS_value=
ac_cv_env_LUA_INCLUDE_set=
ac_cv_env_LUA_INCLUDE_value=
ac_cv_env_LUA_LIB_set=
ac_cv_env_LUA_LIB_value=
ac_cv_env_LUA_set=
ac_cv_env_LUA_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_prog_ac_ct_CC=gcc

-----------------

Output variables.

-----------------

CC='gcc'
CFLAGS=''
CPP=''
CPPFLAGS=''
DEFS=''
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
EXEEXT=''
EXTRA_LIBS=''
GREP=''
LDFLAGS=''
LIBOBJS=''
LIBS=''
LTLIBOBJS=''
LUA=''
LUA_EXEC_PREFIX=''
LUA_INCLUDE=''
LUA_LIB=''
LUA_PLATFORM=''
LUA_PREFIX=''
LUA_SHORT_VERSION=''
LUA_VERSION=''
OBJEXT=''
OPENSSL_INCLUDES=''
OPENSSL_LDFLAGS=''
OPENSSL_LIBS=''
PACKAGE_BUGREPORT=''
PACKAGE_NAME='telegram-cli'
PACKAGE_STRING='telegram-cli 1.0'
PACKAGE_TARNAME='telegram-cli'
PACKAGE_URL=''
PACKAGE_VERSION='1.0'
PATH_SEPARATOR=':'
PKG_CONFIG=''
PYTHON_BIN=''
PYTHON_CFLAGS=''
PYTHON_FOUND=''
PYTHON_INCLUDE_DIR=''
PYTHON_LIB=''
PYTHON_LIBS=''
SHELL='/bin/bash'
ac_ct_CC='gcc'
bindir='${exec_prefix}/bin'
build_alias=''
datadir='${datarootdir}'
datarootdir='${prefix}/share'
docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
dvidir='${docdir}'
exec_prefix='NONE'
host_alias=''
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${datarootdir}/info'
libdir='${exec_prefix}/lib'
libexecdir='${exec_prefix}/libexec'
localedir='${datarootdir}/locale'
localstatedir='${prefix}/var'
luadir=''
luaexecdir=''
mandir='${datarootdir}/man'
oldincludedir='/usr/include'
pdfdir='${docdir}'
pkgluadir=''
pkgluaexecdir=''
prefix='NONE'
program_transform_name='s,x,x,'
psdir='${docdir}'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='${prefix}/etc'
target_alias=''

-----------

confdefs.h.

-----------

/* confdefs.h */
#define PACKAGE_NAME "telegram-cli"
#define PACKAGE_TARNAME "telegram-cli"
#define PACKAGE_VERSION "1.0"
#define PACKAGE_STRING "telegram-cli 1.0"
#define PACKAGE_BUGREPORT ""
#define PACKAGE_URL ""

configure: exit 77

spam.lua -- no username means --> no report

in one of the SuperGroups

Preprocess bot
Preprocess settings
Preprocess moderation
*** 1458145079.589744 lua: plugins/moderation.lua:399: bad argument #1 to 'len' (string expected, got nil)

:-/
commented these codes and problem gone XD
-- hash = 'antibot:'..msg.to.id
-- if redis:get(hash) then
-- if string.sub(msg.from.username, (string.len(msg.from.username)-2), string.len(msg.from.username)) == 'bot' then
-- kick_user(user_id, chat_id)
-- end
-- end

and

Preprocess bot
Preprocess settings
Preprocess moderation
Preprocess stats
Saving user user:xxxxxxxxx
msg matches: [Tt][Ee][Ll][Ee][Gg][Rr][Aa][Mm]%.[Mm][Ee]
*** 1458125662.060747 lua: plugins/spam.lua:15: attempt to concatenate field

'username' (a nil value)

Use or in between

the one i made correct is attached below and cause github does not support lua, I added txt extension

attachment

spam.lua.txt

Its not working in a group

The Bot is working in a supergroup with 40 members. But in a supergroup with 20 members, the bot is not working.

#BOT HAVE 2 PROBLEM

1- BOT Crashing for 5 min after ./launch.sh

*** 1456859482.006978 lua: attempt to call a nil value

*** Error in `./tg/bin/telegram-cli': double free or corruption (fasttop): 0x000000000e59033
0 ***
SIGNAL received
h./tg/bin/telegram-cli(print_backtrace+0x20)[0x46edb0]
./tg/bin/telegram-cli(termination_signal_handler+0x64)[0x46ee34]
/lib/x86_64-linux-gnu/libc.so.6(+0x36d40)[0x7f0106599d40]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x39)[0x7f0106599cc9]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f010659d0d8]
/lib/x86_64-linux-gnu/libc.so.6(+0x73394)[0x7f01065d6394]
/lib/x86_64-linux-gnu/libc.so.6(+0x7f66e)[0x7f01065e266e]
./tg/bin/telegram-cli[0x4929ff]
./tg/bin/telegram-cli(tglq_query_result+0x10f)[0x4986ef]
./tg/bin/telegram-cli[0x490fda]
./tg/bin/telegram-cli[0x4b64fb]
/usr/lib/x86_64-linux-gnu/libevent-2.0.so.5(event_base_loop+0x754)[0x7f01079d6f24]
./tg/bin/telegram-cli(net_loop+0xa6)[0x470336]
./tg/bin/telegram-cli(loop+0x187)[0x471637]
./tg/bin/telegram-cli(main+0x2e5)[0x46d615]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f0106584ec5]
./tg/bin/telegram-cli[0x46d725]

root@localhost:~/py#

2- If Admin Mute Sodu in Group So sudo is muting !!!!!!!!!!!!!!!!!!!!!!!!!!1
its so big problem...

new plugin

writ new plugins for left bot of channel and group and supergroup

can?

module 'serpent' not found:

** 1456740639.528893 lua: .///bot/utils.lua:5: module 'serpent' not found:
no field package.preload['serpent']
no file '/usr/local/share/lua/5.2/serpent.lua'
no file '/usr/local/share/lua/5.2/serpent/init.lua'
no file '/usr/local/lib/lua/5.2/serpent.lua'
no file '/usr/local/lib/lua/5.2/serpent/init.lua'
no file '/usr/share/lua/5.2/serpent.lua'
no file '/usr/share/lua/5.2/serpent/init.lua'
no file './serpent.lua'
no file '.luarocks/share/lua/5.2/serpent.lua'
no file '.luarocks/share/lua/5.2/serpent/init.lua'
no file '/usr/local/lib/lua/5.2/serpent.so'
no file '/usr/lib/x86_64-linux-gnu/lua/5.2/serpent.so'
no file '/usr/lib/lua/5.2/serpent.so'
no file '/usr/local/lib/lua/5.2/loadall.so'
no file './serpent.so'
no file '.luarocks/lib/lua/5.2/serpent.so'

channel_leave

Lua [plugins] :

channel_leave("channel#id"..msg.to.id, ok_cb, false)

tg [lua-tg.c]:

lq_channel_leave

    case lq_channel_leave:
      tgl_do_leave_channel (TLS, lua_ptr[p + 1].peer_id, lua_empty_cb, lua_ptr[p].ptr);
      p += 2;
      break;

  {"channel_leave", lq_channel_leave, { lfp_channel, lfp_none }}

Terminal

cd bot 
cd tg 
make 

open pull request

#FIX MUTE ALL

Fix muta all languange . if we enable/diable this plugin, but dont send mute all command. i think U dont add mute all to ENGLISH_lang

why?

Hello mr. why tmux is run on my session but if bot crashed, tmux is runing and show BOT RUNING! but Bot is Crashed and dont receipt msg !! how can fix this problem ?
my bot is cloned by your github and i dont think need to change steady.sh information so why bot is dont receive massage while tmux is runing !!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.