Hikka Suggestions

[anon97945]

• [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.

[hikariatama]

• [ ] Commit flag for silent pushes
• [x] Rework .blacklist
• [ ] Whitelist for commands
• [x] Targeted security (certain user, certain chat)
• [ ] .stopauth .startauth for web auth button
• [ ] client isolation (get rid of self.allclients somehow)
• [ ] Flag in settings to remove acc from sync (isolate it)
• [ ] Global configuration aka .dlmod --all
• [x] Rework noweb

[anon97945]

• [x] Full uninstall of Hikka from an account. (Delete all Hikka related things. Bots, Chats etc.)

[anon97945]

• [x] Ability to install system requirements via module

[hikariatama]

• [x] Ability to install system requirements via module

.terminal pip3 install -y

[anon97945]

• [x] remove or replace with random phone and other private things from eval output. Like .e reply.sender (phone number)

[anon97945]

• [x] Change the 🔄 Transferring value to userbot... message on remote control.
• [x] Add lang validator

[anon97945]

• [x] send logs (and show in .logs) only from the user, caused this logs (if possible to determine which)
• [x] .cleardb should also get an prompt to make sure it was intended.
• [x] do not remove modules from loader db if they can't be loaded. An broken update removed all of my modules after restart. Annoying for multiple accounts to reload them.
• [x] .ch_hikka_bot | should also have some "default" option, to random botname again.

[hikariatama]

• .ch_hikka_bot | should also have some "default" option, to random botname again.

I can't see any usecase of this feature

[hikariatama]

• do not remove modules from loader db if they can't be loaded. An broken update removed all of my modules after restart. Annoying for multiple accounts to reload them

This is not possible, bc modules in db are updates with ones from self.allmodules.modules, where there are no "not-loaded" modules

[hikariatama]

• Add lang validator

Lang formats are different. Use loader.validators.String or loader.validators.RegExp for more complex langs

[anon97945]

• [x] Add permissions cache: perms = await self._client.get_permissions(chat, user) and the ability to force (recache) get the perms with (chat, user, force)

[anon97945]

• [x] add cache for await message.client(GetFullChannelRequest(channel=<id>))

[anon97945]

• [x] Show Version of the module in .help <module>

[anon97945]

• [x] await utils.asset_channel(client, "Title", "Description", channel=<group/channel/megagroup>) Let us choose the type of chat to create and search for.

[hikariatama]

• [x] Force bound method _mod_get and _mod_set to use module classname instead of strings'es name + Legacy migration

[hikariatama]

• [x] add cache for await message.client(GetFullChannelRequest(channel=<id>))

I don't wanna make cacher for raw api methods, bc sometimes you need to forcefully get a non-cached (actual) result, which with cached raw methods will be impossible. But

• [x] Add cache for client.get_permissions sounds good

[anon97945]

• [x] utils.answer | utils.answer native string support of <br> (replace it with \n) right in utils.answer or so.
• [x] .langforce <langcode> <id> | Add support for forced languages of modules in given chats. Example: German communitys and English communitys. Let Hikka load all strings of the module on start and then check if the chatid, which triggers an command, has a forced language. If yes, use it, else use default userbot lanaguage. Same goes for if string isn't found in that language. Idea behind: not all of my german community is speaking english, nor is the english community speaking german. So i need to host 2 Userbots with the same module just for translation......

[hikariatama]

• .langforce <langcode> <id> | Add support for forced languages of modules in given chats. Example: German communitys and English communitys. Let Hikka load all strings of the module on start and then check if the chatid, which triggers an command, has a forced language. If yes, use it, else use default userbot lanaguage. Same goes for if string isn't found in that language. Idea behind: not all of my german community is speaking english, nor is the english community speaking german. So i need to host 2 Userbots with the same module just for translation......

There will be a multiple languages with priority soon, so it's not neccessary to create .langforce

[hikariatama]

• utils.answer | utils.answer native string support of <br> (replace it with \n) right in utils.answer or so.

Why would anyone need it? =/

[anon97945]

add multiple strings via config -> series(strings) and put them together as one big. since inline doesnt support unlimited message length.

[anon97945]

• [x] asset_channel: on creation optional self-destructive setting by default (telegram native version)