🦌 Hikka ㉿ Userbot news

⚠️ Some of the official Hikka bots were deleted by Telegram without notice. That's why the HikariPay, HikariChat and other bots are not available, along with HikariChatFull and other features. I can't give you an ETA for restoration, neither am I 100% sure these services will be restored whatsoever.

❗️ Centralized Heta installation might not work correctly until update v1.6.4. It'll show the error message when you try to install module via it. Possible alternatives: — Use download links (search for module, copy link, .dlm <link>) — Use .heta command — Use @your_hikka_bot heta menu Do not report it as error since it's a known issue!

🐙 This is the new appearance of download buttons in channels. P.s: However old buttons with ⛩ are still working

🌘🌘🌘 1.6.3 released - Add argument item_type to db.pointer to provide interface for NamedTuple objects - Add correct exception propagation to inline units - Add -fs arg to .lm command - Add IDM flush_loader_cache - Add ability to cancel QR login using keyboard interrupt - Add custom security groups - Add automatic NoNick for tsec methods - Add external debugging feature (off by default) - Fix form invoke error message - Fix Backuper - Fix backward compatiblity with security groups SUDO (0x2) and SUPPORT (0x4) - Fix quickstart language buttons translations - Fix language buttons disabling on restart - Migrate inline heta search to userbot instead of centralized service - Cosmetical changes

.fadd hikka

🌘🌘🌘 1.6.2 released - Fix security issue with edited channel messages - Add interface to interact with raw pointer data (.data attribute) - Translation fixes - Randomize device_model to bypass fraud detection - Pass proper device information to Telegram - Update hikka-tl in accordance to upstream telethon v1 - Update hikka-pyro in accordance to upstream pyrogram - Rename packages so that they don't conflict with originals - Partially migrate to pathlib - Code cleanup - Add ability to log in using QR code and --no-web - Disable web interface for Termux and fallback to CLI login instead - Add fancy ANSI banners - Add guidelines to --no-web login - Fix session not being saved after logging in using QR without 2fa - Minify static assets in web - Replace snowfall with sakura flowers - Update Termux installation design - Whitelist requests in APILimiter to ignore internals - Start web when using .weburl and --no-web is used - Add inline commands targeted security rules control - Completely remove security groups sudo and support - Fix proxy-pass - New core modules: UnitHeta, Translator - New watcher tags: no_pm, no_channels, no_groups, no_inline, no_stickers, no_docs, no_audios, no_videos, no_photos, no_forwards, no_reply, no_mention, mention, only_reply, only_forwards - Remove default presets since they are the security risk - Update and extend Tatar translation pack - Restrict setting s as command prefix, since it will break command setprefix - Transfer all previously non-essential modules to core ones - Add alternative translation mechanism using YAML

If you are from country, which doesn't have its national language supported (excluding Ukraine, Kyrgyzstan and Belarus), or you just speak another language with good proficiency level, send your language to @hikka_talks. This will help to analyze the community preferences in terms of translations.

Regarding issue #93 A "sudo" user can add and remove "owner" users In the next minor update (1.6.2), groups will be removed. They confuse new users. They even confuse old ones. If you use them (groups) now, you should migrate to .tsec rules instead, otherwise users with access will lose it.

I got strange message from Telegram, what does it mean? Lemme explain. You can no longer login with custom client using SMS. Does it affect you in any way? No. You can still receive login codes to unofficial clients, you can still login using Telegram codes. The only restriction is that you can no longer login using SMS. That's it.

*later*: How proxy works? Hikka creates second client using pyrogram for dragon modules. This client THINKS, that it's connected to the actual Telegram servers, but in fact, it just sends requests to Telethon client, which sends them to servers and gives Pyro result back. This brings the problem - suspicious activity. Imagine that you have your phone and your PC both using the same session. Both of them get updates. This is the warning sign for Telegram algorithms "something's not right". That's why it's required to proxy requests like this: Pyro <-> Telethon <-> Telegram \ ^       \     |        \    v          Cacher This way, Telethon requests something, caches it, and when Pyro requests the same thing, Telethon just returns it as other official client would do instead of making new request. Still, it takes time, which I don't have currently, to implement. Avoid Dragon modules if possible.

Important notice about the situation around miyahost. I'm trying to get full info regarding this incident, both from owner and from other developers. Due to high loads I'm not in resource to continue investigation and/or publishing new updates just yet. The host will certainly be removed from official ones when I find right amount of time for it. My sincere apologies to ones who were scammed by it, but since it's not owned/controlled by me, I can't somehow affect the overall outcome.

⚠ Until the new version gets released, it is highly recommended to avoid using Dragon userbot adapted modules whatsoever. If you already have them installed, uninstall all of them and restart. I'll explain it later.