The most fresh and updateable Telegram userbot. By one of the most active contibutors to GeekTG

Before continuing, check the mark below

• [x] My suggestion is not about illegal stuff, doesn't violate Telegram EULA and human rights.

Short description of idea: In silent_tags.py there will be a message in the silent-tags group. Since i can't unread send my own messages I don't see when someone tagged me and I do need to check that group manually.

my idea is that the bot sends it instead of the user and so you can see an unread notification. So you can see directly and at a glance that you have been tagged. Since the group is muted anyway, you won't get a notification.

If you have an existing implementation of this idea, e.g. in a another userbot, attach it here:

Any additional information: Reference: https://mods.hikariatama.ru/view/silent_tags.py

Йе, уроки закончились, значит сегодня суббота Я захожу на Twitch и пишу кому-то в чат: «Поплачь, блядота» Чтобы не плакала девочка надо написать пару пиздатых паст Мне похуй на это, я очень классный пац, йе Я захожу на Twitch и пишу всем оскорбления Заниматься вот этой хуйнёй вообще-то мне честно не лень, бля Я очень классный, я обожаю смотреть Братишкина и Мазеллова Я ещё спорю чей чат намного пиздат чё, ну я считаю что у Мазеллова, реально У Мазеллова самые охуенные треки, «Маз Корж» — изобретение века, ну что ж Охуенно, спасибо, зачитал как бог, йе Боже, как же он читает, как же он фристайлит, как мы его все понимаем, йе — О, Жожо в чате, ты чё про Гаечку пиздел? — Да я просто сидел и читал рэпак и сидел без дела, она зашла мне в чат, выписала какую-то хуйню в субботу, ну я ей просто сказал: «А ну-ка, ну-ка, поплачь, блядота», йе

[Припев] Поплачь, блядота Поплачь, блядота, у-у Поплачь, блядота Поплачь, сегодня суббота, йе Поплачь, блядота Поплачь, блядота, у-у Поплачь блядота Поплачь, ведь сегодня суббота, йе

[Куплет 2] Очень классный пац Сидим в TikTok'е, залипаем классно Охуенные классные TikTok'и с Иваном Золо, во, мне не пофиг Так нравятся TikTok'и Эвелона, он охуенно снимает и клёво С кем-то там, с Некоглаем, ну, честно это хуйня нереальная, у-у

[Припев] Поплачь блядота, кхм Поплачь блядота Поплачь блядота Ведь сегодня суббота, о-о-о Поплачь блядота Поплачь блядота Поплачь блядота Хорошо, что сегодня суббота

[Куплет 3] Я захожу на Twitch, посмотреть кто стримит Я сижу один и дрочу за компом в своей квартире Мне если честно вообще никто не нравится из стримеров в принципе Но я считаю что лучше всех — это Дмитрий Ликс Потому что он старый и классный Старый и пиздатый Старый и крутой Старый и клёвый Я мечтаю чтобы он был учителем в моей школе Он очень классный чел, мне он очень нравится Хочу чтоб Дмитрий Ликс меня прям выебал в задницу, йе

[Припев] Поплачь блядота, у-у Поплачь блядота Поплачь блядота Знаю что сегодня суббота, йе, йе Поплачь блядота Поплачь блядота Поплачь блядота Ведь сегодня суббота, хули

• [x] My suggestion is related to Hikka userbot itself. It's not about illegal stuff, doesn't violate Telegram EULA and human rights and is not related to modules.

Describe the suggestion .config can apply settings, which is awesome, but it should have some kind of true/false recognition or true/false. Right now i could use tru or on and will catch an error than. (example silent_tags.py). It could be checked when the .config says Default: False.

Additional context Maybe something like this (or a better one)

> 
> def to_bool(value):
>     if str(value).lower() in ("true"):
>         return True
>     if str(value).lower() in ("false"):
>         return False


> if not isinstance(to_bool(args[1]), bool):
> 	return await utils.answer(message, self.strings("error", message))

Since the Hikka userbot is based on FTG, GeekTG, etc., and there are no so-called "advertising Trojans" in them, it also shouldn’t have functions that make the user a slave of his own bot, forcing him to subscribe to the channel to install module and automatically putting reactions to posts with modules in the developer channel of these modules.

This functionality isn’t spelled out anywhere (for the end user), except in the code and changelogs, therefore he does not even think about it when he installs the bot according to the instructions.

Based on the absence of this functionality in other userbots on which Hikka is based, you should equate them and not add functionality hidden from the end user without notifying him in advance even before installing the userbot, or notify the user of the presence of such functionality in any most noticeable way, or implement the possibility of disabling this functionality if user doesn't want to subscribe on any channels, and even more so doesn’t want to put reactions without knowing it.

• [x] This bug is related to Hikka userbot itself. It is not related to modules.

Describe the bug WebUI Inlinebot is buggy. When i try to add a username i get Custom bot setting error. When i use it without a name i get Login confirmation error but if I try it repeatedly, about once every 3 seconds (still getting the error), it eventually works. You can see it best when BotFather starts creating.

To Reproduce Steps to reproduce the behavior:

1. Go to webui
2. Add new phone
3. fully login
4. at inline bot creation put in a username (or without username for other error)
5. See error

Screenshots

Userbot installation info:

• Platform:

• [ ] 🕶️ Termux

• [ ] ✌️ lavHost

• [ ] ☁️ Okteto

• [x] 🐳 Docker

• [ ] 🌺 Other platform

• Hikka version: 1.1.22 #90b5ab0b (https://github.com/hikariatama/Hikka/commit/90b5ab0b4d413d4d5e299ad2135b23dbb1f8beab)

Additional context Add any other context about the problem here.

Before continuing, check the mark below

• [x] My suggestion is related to Hikka userbot itself. It's not about illegal stuff, doesn't violate Telegram EULA and human rights and is not related to modules.

Describe the suggestion I don't know how it is currently handled, but when I currently produce an error, the bot apparently tries to establish a TCP connection with all logged-in bots. On the one hand, this produces spam in the log and apparently the target also has some kind of DDoS protection, since not all of my accounts can connect and produce a timeout.

If the connection is tried even with a "no error", this is of course even more unnecessary traffic.

Only the necessary/triggered bots should try to establish a connection.

Pull Request #84 refactored by Sourcery.

If you're happy with these changes, merge this Pull Request using the Squash and merge strategy.

NOTE: As code is pushed to the original Pull Request, Sourcery will re-run and update (force-push) this Pull Request with new refactorings as necessary. If Sourcery finds no refactorings at any point, this Pull Request will be closed automatically.

See our documentation here.

git fetch origin sourcery/v1.6.0
git merge --ff-only FETCH_HEAD
git reset HEAD^

Help us improve this pull request!

• Bring support for Dragon Userbot modules
• Make db attribute of Modules public
• Mess up with some translations
• Fix .helphide command
• Fix visual bug with phone input field in web
• Fix proxy-passing in web
• Fix EntityLike validator
• Fix stringifying error in logging
• Fix command escaping when using layout translated prefix
• Patch .info, utils.answer etc to support forums (topics)
• Drop Okteto support
• Show Hikka platform and version in Telegram sessions list
• New type DragonModule
• New argument of get_prefix - userbot. Pass in "dragon" to get its prefix
• New attribute of Modules - dragon_modules
• New attribute of CustomTelegramClient - pyro_proxy. Use pyrogram methods natively
• New appearence of help command
• New module loading animation
• New README.md with installation steps and new web recording
• New utils.atexit method
• New utils.get_topic method
• New utils.answer_file method
• New utils.get_cpu_usage method
• New utils.get_ram_usage method
• New restart process, which correctly kills all child processes and threads
• New interactive web werkzeug debugger (view pin using .debugpin command)
• New QR login flow
• New license banners
• New error-specific messages for RPCErrors, FloodWaitErrors, NetworkErrors
• Send start hook to InfiniteLoop instances with autostart flag only after client_ready
• Replace __getattr__ in Module object with properties for commands and handlers
• Move from monkey-patching concept of filling modules' attributes to native one
• Minor and major bugfixes, adapt to topics
• Kazakh translation pack
• Italian translation pack
• Partial Tatar translation pack
• Logging tweaks
• Add caller field to inline units
• Add ability to get module help by command alias
• Add ability to decorate aliases with @loader.command decorator
• Add credits to developers and translators
• Add support for multiple usernames
• Add topic guesser in send_message, send_file in order for old modules to work properly
• Add local storage fallback in case remote end is not available
• Add self.invoke method for modules
• Fresh Christmas web design
• EULA warning for lavHost and MiyaHost
• Support for Python 3.10

Pull Request #80 refactored by Sourcery.

Since the original Pull Request was opened as a fork in a contributor's repository, we are unable to create a Pull Request branching from it.

To incorporate these changes, you can either:

1. Merge this Pull Request instead of the original, or

2. Ask your contributor to locally incorporate these commits and push them to the original Pull Request

   Incorporate changes via command line

   git fetch https://github.com/hikariatama/Hikka pull/80/head
   git merge --ff-only FETCH_HEAD
   git push

NOTE: As code is pushed to the original Pull Request, Sourcery will re-run and update (force-push) this Pull Request with new refactorings as necessary. If Sourcery finds no refactorings at any point, this Pull Request will be closed automatically.

See our documentation here.

Help us improve this pull request!

Pull Request #78 refactored by Sourcery.

If you're happy with these changes, merge this Pull Request using the Squash and merge strategy.

NOTE: As code is pushed to the original Pull Request, Sourcery will re-run and update (force-push) this Pull Request with new refactorings as necessary. If Sourcery finds no refactorings at any point, this Pull Request will be closed automatically.

See our documentation here.

git fetch origin sourcery/v1.5.3
git merge --ff-only FETCH_HEAD
git reset HEAD^

Help us improve this pull request!

Pull Request #76 refactored by Sourcery.

If you're happy with these changes, merge this Pull Request using the Squash and merge strategy.

NOTE: As code is pushed to the original Pull Request, Sourcery will re-run and update (force-push) this Pull Request with new refactorings as necessary. If Sourcery finds no refactorings at any point, this Pull Request will be closed automatically.

See our documentation here.

git fetch origin sourcery/v1.5.2
git merge --ff-only FETCH_HEAD
git reset HEAD^

Help us improve this pull request!

• [x] silent_tags.py | blocked user list won't refresh/doesn't work. I use silent_blocked true, but it still appeases in the logchat.

should be : if self.config["ignore_blocked"] or self.config["silent_blocked"]:

instead of: if self.config["ignore_blocked"]

https://github.com/hikariatama/ftg/blob/af63c0c9c2459adf019465a9e5fa2c86747cbf08/silent_tags.py#L167

• [x] My suggestion is not about illegal stuff, doesn't violate Telegram EULA and human rights.

silent_tags.py:

• [x] Add a global white/blacklist switch for id related configs.

• [x] This bug is related to Hikka userbot itself. It is not related to modules.

Describe the bug

• [X] alias still won't survive a reboot. (Fixed in 1.1.27)

🔮 Version: 1.1.24 #3453fb98

• [x] My suggestion is related to Hikka userbot itself. It's not about illegal stuff, doesn't violate Telegram EULA and human rights and is not related to modules.

Describe the suggestion Change the restart message when the bot has fully loaded.