All about exteraGram chats
⚠️ Note: For optimal display of all elements and a comprehensive experience, it is highly recommended to view this article in a web browser.
This material utilizes deep links (direct links to specific internal sections of the app settings) that are functional starting from version 12.0.1 — updating to the latest release is highly recommended for the best experience.
Think of this article as a mini-constitution for exteraGram chats.
﹡Part of these rules is aligned with the AyuGram forum rules, so the similarity is intentional.
First of all, which chats are we talking about?
Foremost, there is the exteraGram forum itself and its affiliated chats:
- exteraGram Beta;
- MeowPlugins;
- exteraGram Utilities;
- exteraGram Supporters;
- exteraGram Private Beta;
- 152 мм ЭКСТЕРАГРАМ;
- AyuGram also has rules for this forum that are interconnected with this article.
By joining any of these chats, you acknowledge that you have read these rules and agree to be bound by all terms and conditions without reservation.
For now, we will focus specifically on the forum to avoid duplicating information for other chats, as the rules are identical across the board.
Introduction
What is the difference between a forum and a group?
If you are used to regular chats, a forum might seem intimidating at first, but it is actually quite simple. Technically, it is the same group, just divided into separate «rooms» — topics. This allows for structured communication: one thread is dedicated to bug reports, another to general socializing, and these streams never cross.
Forums operate under a two-tier system of order that is essential to keep in mind:
- General rules. These serve as the foundation and the "constitution" of the entire project. They apply globally, covering every corner of the forum without exception.
- Topic rules. These are local guidelines and refinements tailored to the context of a specific section. They supplement the general rules but do not override them (unless otherwise specified).
Consequently, whenever you enter a new section, it is as if you are crossing into a new jurisdiction. Your first step should always be to check the pinned message. That is where you will find the local specifications and unique requirements applicable to that specific discussion thread.
Don’t see the forum topics? The issue lies with your client.
If you see one continuous chat stream instead of a structured forum with distinct sections, you are likely using a client that lacks support for this feature.
Telegram X and other clients built on the Telegram X engine do not support forum mode. To these clients, our forum appears as a standard group.
Consequently, you will end up posting in the "General" topic (i.e., Off-topic) or in whichever topic was automatically selected by a reply to another member's message.
To view and navigate these topics correctly, you will need to download a client based on the official Telegram codebase or the oftg app itself.
It is also possible that the «View as messages» feature is enabled in your oftg client. To restore the standard layout, while inside the chat, tap «︙» ➝ «View as topics».
Before posting a message, please consult the FAQ. All essential links can be found in the forum header.
General rules for exteraGram chats
We have established this space for respectful and productive communication.
Before engaging in any activity, start with the rules.
Understand the core principle: ignorance of the rules is a personal choice that does not exempt you from the consequences. Disregarding our principles will result in a swift and irreversible expulsion from the community.
This text serves as the primary source and holds ultimate precedence over any other versions or interpretations of the rules. In the event of any discrepancies, this specific article shall be considered the absolute authority.
For quick access to a condensed version of the rules, use the /rules or .rules commands in the chat.
- Language of communication: The official languages of communication are russian and english. The choice of language depends on the specific forum topic (more on this below).
- Reasonableness and common sense: This is the fundamental principle of our community. We do not require you to master every technical nuance, but we do expect balanced, calm, and constructive behavior. While the concept of «reasonableness» may seem subjective, the boundaries of acceptable conduct are intuitive to any civilized person. The Administration reserves the right to evaluate your actions. If a user's behavior becomes toxic or destructive, we will intervene — even if no specific rule has been formally violated.
- Warning System: We believe in second chances, but not in infinite patience. Therefore, a four-strike system is in effect. Receiving a fourth warning will lead to an automatic and permanent ban.
- Administrative decisions: Decisions made by the Administration are final. The Administration reserves the right to adjust disciplinary measures at its sole discretion, particularly in cases of repeat offenses.
- Federal ban (Fban): This is a global blocking system operating within a network of interconnected chats (a federation). Committing a severe violation in one chat results in an automatic ban across all others. One transgression, and every door within the network is closed to you. This type of ban is non-appealable.
- Multi-accounting: Creating and/or using "backup" accounts to circumvent penalties imposed on a primary account is strictly prohibited. If identified, such accounts will be banned without warning or the possibility of appeal.
- What about plugins? Answer.
- Spam and advertising: Any attempt to distribute spam, solicitations, advertisements, or referral links will be your final act within our community.
- Forbidden topics:
• 18+ content: The publication of any adult materials — including pornography, erotica, shock content, and scenes of violence («gore») — is strictly prohibited, regardless of context. Your «funny» gif featuring cruelty is an instant ticket to a permanent ban.
• Politics and misinformation: Our forum is a zone free of politics, campaigning, and the dissemination of deliberately false information (fake news). Leave such matters at the door.
• Extremism: Promotion of nazism, justification of terrorism, or any other extremist manifestations will not be tolerated. Zero tolerance. No exceptions. • Doxing, stalking, and threats: The disclosure of personal information (including fabricated data), threats, or any form of harassment — including those facilitated by plugins — is forbidden. Any attempt, or even a hint of an attempt, to ruin someone else's life will result in the termination of your stay here. Do not even contemplate initiating a discussion on this subject within the forum.
Penalty: Mute and/or warning. In particularly severe cases — Fban.
- Offtopic: Any message that does not align with the specific theme of the section will be deemed offtopic. For casual conversation, please refer to the designated threads: «Offtop 🇺🇸» and «Офтоп 🇷🇺». Systematic violation of this rule will result in a long-term transition to «read-only mode».
- Insults and toxicity: Insulting forum participants or the administration, including via private messages, is strictly prohibited. We maintain a zero-tolerance policy toward any form of aggression.
- Malicious interference: Any actions intended to disrupt the stable operation of the chat or cause discomfort to its participants are forbidden.
Such actions include:
• utilizing crash exploits that cause application failures;
• abusing formatting (e.g., through plugins) to break the chat layout;
• and posting «heavy» or flickering media files that hinder comfortable communication. - Provocations and testing the administration's patience: Attempts to «walk the line», searching for loopholes in the rules, trolling, or deliberately creating conflict situations are prohibited. Anyone who believes they can outsmart the system will be made a public example for others. Punishment will be swift and severe.
Penalty: Warning and/or mute; a ban remains a possibility.
- Flooding: Senseless and/or repetitive messages, abuse of CAPS LOCK, or excessive use of stickers/emojis that disrupts the flow of conversation.
- Abuse of mentions (@): Disturbing the administration or participants with mentions without a compelling reason. If you require assistance, there is no need to tag the entire moderation staff — your query will be seen regardless; please exercise patience.
- Incorrect client naming: Please show respect for the projects. The correct name is exteraGram. Acceptable abbreviations include «etg» and «extera». This rule applies to both exteraGram and our sister project, AyuGram.
- Issues resolvable via FAQ and search: Before asking a question, attempt to find the answer yourself by utilizing tools such as the FAQ and the chat search function. Questions regarding AyuGram must be directed to the corresponding chat; failure to comply will result in being sent into oblivion (i.e., being permanently removed or ignored).
- Visual noise: Reaction abuse and the use of userbots to automate "tasks" that create visual chaos are prohibited. Disregarding a warning will lead to a ban.
- Posting as a channel (reposts): Direct reposts are forbidden. Our community is not a news aggregator.
• Exceptions are made for official administration channels, as well as links to Telegram Info and Beta Info.
• How to share information correctly? Forward the message, but ensure you hide the sender's name and remove all mentions or links to the source channel.
5. Recommendations and etiquette
- Framing questions and requests for assistance: Vague inquiries such as «it’s not working», «help», or "everything is broken" — submitted without providing necessary context (client version, OS version, steps to reproduce, etc.) — will be disregarded. Users who persistently post vacuous queries will be restricted to read-only mode to familiarize themselves with the FAQ and community guidelines.
- Be constructive: Criticism is welcome, provided it is well-reasoned and aimed at product enhancement rather than directed as an affront to developers or fellow users.
- AyuGuardian bot in the exteraGram chat?! Yes, despite the "ayu" prefix, this is the primary and official bot for the exteraGram and AyuGram chats, serving to assist the moderators. It was covered in this article.
Remember: rules are in place to ensure that communication remains a pleasure rather than a headache. Abide by them, and you will always be a welcome member of our community.
Now, let’s take a closer look at each forum category in detail.
Greetings | Приветствие
This is a service section — the «foyer» of our forum, so to speak. There are no discussions here; in this thread, a bot automatically greets every new member.
To gain access to the chat and start participating, you must complete a simple verification process:
- Click the «КНОПКА | BUTTON» provided by the bot.
- Review the community rules (it’s in your own best interest).
- Complete the captcha (don’t worry, it’s not that captcha from the AyuGram forum).
APKs [Release / CI]
This is an information section where you can find changelogs and APK files for both stable and beta versions, sourced from the official «exteraGram», «exteraGram Beta», and «extera Releases» channels.
AI Chat
This is also an informational category, which provides guidance on:
- How to use the AI Chat.
- What data needs to be entered into the fields and exactly where to obtain it.
«Офтоп 🇷🇺» and «Offtop 🇺🇸»
Offtopic (from the english «off topic» — meaning outside the subject) is a space for conversations unrelated to client development. These threads serve as a filter, separating valuable technical data from everyday human interaction.
You have carte blanche here: discuss anything from global warming to your PC’s architecture — just keep it within reason and avoid the absurd. We do not restrict topics as long as basic social norms are upheld.
However, remember: freedom is not anarchy. Spam, advertising, and outright erratic behavior remain strictly prohibited — punishment is swift and severe.
To prevent the chat from devolving into a Tower of Babel, we require adherence to clear standards. Please note the fundamental difference:
- In technical sections («Plugins», «IconPacks», «Bugs», «Suggestions»), a hybrid linguistic style (russian-english) is permitted to facilitate rapid problem-solving.
- Within the «Офтоп 🇷🇺» thread, communication is to be conducted exclusively in russian.
- In the «Offtop 🇺🇸» thread, communication must be strictly in english.
- Not proficient in the language? Utilize the translator provided within the oftg.
- Transliteration is strictly prohibited in any form.
Kindly ensure you do not misplace your posts across different threads. This is essential for maintaining the structure and order of the community.
exteraGames
This section has been established specifically to satisfy your cravings for digital hedonism.
Here, you are welcome to use gaming emojis (🎰, ⚽, 🏀, 🎯, 🎲) and utilize inline bots for mini-games (with the exception of bots burdened by intrusive built-in advertising or links to unverified sources).
In this space, you are free to test lady luck and indulge yourself to your heart's content without the fear of administrative backlash.
However, keep in mind: there is a time and place for everything. Any attempt to play in the wrong thread will result in a mute.
IconPacks | Иконки
This thread is dedicated to the discussion of in-client icon packs. Please refrain from off-topic remarks.
exteraIcons is the official channel for sourcing icons.
Plugins | Плагины
This thread is dedicated to the discussion of plugins and their implementation.
Off-topic discussion is strictly prohibited.
Useful resource links:
- exteraPlugins — the official channel for information regarding the plugin system and all related matters.
- exteraGram Utilities — a channel featuring verified plugins from the exteraGram/AyuGram community.
- exteraPlugins Robot — the official bot of the exteraGram Utilities channel, designed for publishing and updating custom plugins and icon packs, providing a convenient way to search for and select "utilities".
The distribution of plugins that meet the following criteria is prohibited:
- Designed for spamming, automated posting, artificial engagement manipulation (boosting), or mass messaging;
- Intended to harm users, including doxing, stalking, data theft, or espionage;
- Contain malicious or suspicious components, such as viruses, stealers, miners, or backdoors;
- Interfere with the badge or verification system, with the sole exception of labeling one's own channel as "official" or identifying the author as a developer;
- Restrict access to official resources or distort information sourced from them.
- Duplicate the functionality of the exteraGram/AyuGram client or the official Telegram app without providing distinct unique utility;
- Entirely replicate existing plugins without offering significant enhancements;
- Address trivial tasks that do not warrant a dedicated plugin;
- Are "joke" plugins that lack any practical value;
- Are evidently AI-generated and lack proper refinement or quality assurance.
This rule applies to all plugin channels within the trusted folder and associated community platforms.
﹡While developing plugins for research purposes or personal use is permitted, the publication, distribution, or promotion of such plugins is strictly punishable by a ban.
Assisting other participants: The proper way
Now you have reached the technical sections, which touch upon the very threads of the client's existence. But before we begin, I must reiterate: off-topic chatter in these threads is unwelcome. In «Suggestions | Предложения» and «Bugs | Баги», no one wants to clean up the mess you are bound to create.
Have you noticed a member asking a question in the wrong thread, or perhaps someone who is about to — or already has — violated the rules? There is a correct and tactful way to assist them without creating unnecessary noise or drawing administrative ire.
Simply reply to their message using the «Reply» or «Quote» function. Then, via the specialized forwarding menu, select «Reply in Another Chat» and redirect your response to the «Офтоп 🇷🇺» or «Offtop 🇺🇸» thread. Respond in the same language used in the incoming message.
In this manner, your assistance will reach its intended recipient, while the specialized thread remains in impeccable order.
Suggestions | Предложения
Before pitching your idea, it is essential to grasp the core philosophy behind exteraGram.
We aren't a carbon copy of someone else’s features. We refuse to join the rat race, chasing every Telegram update, and we have no intention of turning the app into a cluttered bazaar by mindlessly copying everything in sight.
Our priority is originality. We only implement features that offer a truly novel experience and genuine utility, rather than simply bloating the app's footprint.
Want to see your idea come to life rather than being laughed off and scrapped? Then read closely and execute it with style.
Step 1: Review the list of rejected ideas
First and foremost, consult the pinned message titled «Rejected suggestions».
Consider this a filter designed to save both your time and ours. This list encompasses ideas that run counter to our strategic direction.
The rules are straightforward: if your proposal duplicates an entry on this list, it will be automatically discarded. If an idea has been rejected or is already listed there, you can fill that missing piece of the puzzle yourself via our plugin system — complete with plugin development documentation to boot.
Step 2: Structuring your concept
Your idea must be as precise as a technical specification. «I want a button» is not a proposal. To ensure we understand your vision, your pitch should answer these three questions:
- What problem does my idea solve? Describe a specific pain point or a scenario where the current functionality is insufficient.
- Why is this necessary for the client? Explain how this feature aligns with exteraGram’s philosophy of uniqueness, rather than simply imitating competitors.
- How should it work? Briefly outline the intended logic behind the feature’s operation.
A well-drafted technical specification is a sign of respect for the developers time and the most effective way to ensure your voice is heard.
A crucial remark
History has shown instances where features from the «rejected list» eventually made it into a release. However, this is no excuse to disregard the list or resubmit previously declined ideas.
Bugs | Баги
Your bug report is our primary instrument for troubleshooting and fixes. To ensure it acts as a surgeon’s scalpel rather than a jumble of incoherent text, please adhere to this impeccable structure.
Step 0: Check the list of rejected bugs
Before you begin drafting your report, consult the pinned message in the topic. There you will find a list of bugs that are either already known or have been rejected. It is quite possible that the issue you’ve encountered is already on our radar and does not require a new submission.
Step 1: Is this definitely our bug?
This is a critical verification step that will save time for both you and us.
Ensure that you are using the official client of the same version as your exteraGram build.
- If the bug persists in the official client: The root cause lies on Telegram's side. In this case, you should report the issue directly to the official client developers after reviewing their submission guidelines.
- If the bug is absent in the official client: You’ve come to the right place. This is an exteraGram error, and we are ready to investigate it. You may proceed to the next step.
A vital vuance: Some bugs in the official client are intermittent and difficult to replicate on the first try. Therefore, even if you were unable to reproduce the error in the official app, our analysis may still conclude that its source lies within the official source code. We ask for your understanding in such cases.
Step 2: The structure of a flawless report
1. Client version and build type
□ Exact version: You must specify the full version and build number — for example, v12.2.10 (63419). This information is located at the very bottom of the settings menu.
Note: Banish the phrase «I have the latest version» from your vocabulary. It is mere white noise to a developer, as updates can be released several times a day. Reports containing this phrase will be disregarded.
- Important! Ensure you are actually using the most current version of the client. If not, update your app before submitting a report.
□ Specification: Specify whether you are using the Full or Lite version. They are easy to distinguish:
- Lite: The lightweight version (plugins and Yandex.Maps have been stripped out).
- Full: The complete version with all features intact.
2.Technical specifications
Provide detailed information about your device; we only need:
OS Name and Exact Version (e.g., Android 14, HyperOS 1.0.5).
Device Model (e.g., Pixel 8 Pro).
3. Crash logs and the plugin system
Let’s start with the terminology.
A crash log is generated when the application crashes, automatically copying the error log to your keyboard’s clipboard.
Our client features a plugin system, which can occasionally be the source of stability issues.
To save time — both yours and the developers — let’s learn how to pinpoint the «culprit» behind a failure.
□ Case №1: Plugin or client fault?
If, after a crash, you paste the text from your clipboard into a notes app or a chat and see any of the following keywords:
Verdict: If you find even one of these terms, the issue lies strictly within one of your installed plugins. However, if the crash log does not contain any of these keywords, it is a client-side error. In that case, proceed to the next stage of drafting a proper bug report.
Use the process of elimination. Disable your plugins one by one in the exteraGram settings and monitor the app's performance. As soon as the crashes stop, you have found the "culprit". You should report this bug directly to the specific plugin's author (via DM or their dedicated community chat), providing the crash log and your feedback.
If the app crashes but fails to copy a crash log to your clipboard, there is still a solution.
Download and install the LogFox app from GitHub. Launch LogFox using your preferred method (Root, ADB, Shizuku), then reproduce the crash to capture the log.
Within the LogFox app, navigate to «Crashes» ➝ «exteraGram» ➝ «Zip», save the error as a .zip file to your device's internal storage, and then proceed to the final stage of drafting your bug report.
4. Camera issues
In the event of specific camera-related bugs, please include the camera’s technical parameters found in the «Chats» section. Once done, proceed to the final stage of formatting your bug report.
5. Proper bug report formatting
- Steps to reproduce. Your report only becomes truly valuable if we are able to replicate the error ourselves. Describe the issue step-by-step, much like a recipe: specify exactly what you tapped, what you opened, and the precise moment everything broke down.
- Visual confirmation. While text is useful, visual evidence is superior. The ideal supplement is a screen recording or a series of screenshots that clearly illustrate the essence of the problem.
- Crash logs and lengthy descriptions. Always place them in a separate collapsed quote so that bulky text does not hinder the analysis. To use collapsed quotes: highlight the required text snippet, select «Quote» from the menu, and then click «Collapse» — you’re all set.
- Long crash log? Save the log as a
.txtfile and attach it to your bug description.
Here are examples of ideal bug reports:
Yes, this is a lengthy article, but these guidelines will make things easier for everyone — admins and moderators as well as chat members. Otherwise, the question «Why was I punished?» might be met with stony silence… though in reality, it’s quite simple: you simply ignored the rules, and that is that.
This article will be supplemented and updated periodically, so be sure to check back from time to time.
That is precisely what the indicator at the bottom is for.