Everything about the AyuGram forum

The act of joining our chat serves as your unconditional confirmation that you have read the following rules and fully agree to all of our terms.

A foreword…

For those who do not know or understand the difference between a group and a forum.

A forum, in this context, is the same kind of chat as a group, but it consists of several topics. Each topic has its own subject matter and may have its own specific rules in addition to the general ones.

We won't break down every topic here, as each has its own rules and specifics — the best course of action is to read the pinned message in each one.

In Telegram X, there is no concept of a «forum»; there is only a single, unified chat.

This means you will either be writing in the main topic (i.e., the off-topic channel) or into the topic where the message you are replying to is located.

To see the topics themselves, you will need to download a client based on the official Telegram codebase, or the official Telegram client itself (oftg).

It's also possible that you have the «View as a Single Chat» function enabled in the oftg. To switch it back: tap the «︙» menu ➝ «View as Topics».

Yes, this is precisely the issue that leads to users asking things like, "Where can I download it for Android or PC?" and so on.

Now, let's move on to the rules.

General rules

Welcome to the AyuGram chat!

This space was created for respectful and productive communication.

Before you begin, understand one crucial point: ignorance of the rules is your personal choice, but it will not absolve you of the consequences. Ignoring them will lead to a swift and inevitable removal from the community.

This list is the primary source and holds the highest legal priority over any abbreviated versions of the rules. For quick access to a summary, use the commands .rules or /rules in the chat.

Perceive these rules not as walls that limit your freedom, but as the load-bearing structures of the building we all inhabit. They provide safety, predictability, and comfort, protecting our shared space from chaos, spam, and toxicity.

Every point here is not an administrative whim, but a carefully calibrated element necessary for maintaining a healthy and productive atmosphere.

By familiarizing yourself with them, you are not just avoiding restrictions — you are gaining the key to comfortable and respectful dialogue. Your participation in the life of the community begins with understanding and accepting these principles.

Appeal process: Do you believe the restriction placed upon you is unjustified?

You may contest the imposed restriction by filing an appeal through our bot. To do so, create a ticket or reply to the warning message you received from the bot.

Before you do so, it is important to understand several key points:

• A pardon is not guaranteed. The chance of having a restriction lifted is not always present. The outcome of each appeal is determined by the severity of the offense committed — ranging from an unintentional mistake to a gross violation of the rules.
• Strong arguments are required. Explanations along the lines of «I didn't know the rules» or «it was an accident» will not be considered and are not grounds for reconsidering the decision.

Rest assured, no correctly submitted application goes unnoticed.

Forum specifics

Or, what every AyuGram member must read after finishing the main rules.

Quiet / Rest mode

To ensure all members can rest comfortably, a night mode is active in the chat.

Hours: Daily from 00:00 to 09:00 Moscow Time.

During this period, the chat switches to a relaxed, text-only format. No stickers, GIFs, or other visual clutter.

The key rule: During night hours, it is strictly forbidden to contact administrators via private messages.

If you have an urgent question, we ask you to first carefully study the FAQ. Otherwise, please wait for the chat to "wake up" and for the support bot to become active.

Message links not working?

Let's say you ask for help and receive a link in response, but when you click on it, it doesn't take you to the correct message, and instead you see «Message not found or has been deleted from the discussion».

So, what could this be, and what should you do?

This is due to a technical limitation.

Let me explain.

Due to the message limit on the forum, navigation via some links has stopped working (with the exception of the off-topic and iOS topics), and it's all the official Telegram client's fault.

Because old messages are overwritten by new ones, valuable information is permanently lost.

This is why, from time to time, you might see the unread message counter showing a negative value or NaN.

For this reason, the FAQ and the Android / Desktop release topics have been migrated to channels, where they remain safe and sound:

• AyuGram FAQ
• AyuGram Releases

Therefore, stop linking to messages in old topics. They're dead. Use links to active discussions or to posts in our channels.

Schrödinger's messages

Perhaps there is nothing more frustrating than a message that mysteriously disappears right after you send it. The first thing that comes to mind is that the administration deleted it. However, in most cases, the cause lies in a technical glitch within Telegram itself.

This all happens precisely because of the aforementioned technical limitation of the official Telegram client.

Such «magic tricks» can spoil one's first impression of the chat and create unnecessary suspicion.

How to be sure it's a bug and not moderation?

If you are sure you have not broken any rules, but your message has vanished, follow these three simple steps to get it back:

1. Clear the Telegram database. (Settings ➝ Data and Storage ➝ Storage Usage ➝ Clear Database).
2. Force-stop the client through your device's system settings.
3. Re-open the chat.

After these steps, the «phantom» message should reappear. Unfortunately, this is one of those unpredictable and «generous» bugs that Telegram bestows upon forum users, and there is nothing we can do about it.

The grand illusion and the harsh reality

— Can I find out who my boyfriend/girlfriend/friend is talking to right now?

— Oh, has AyuGram been released for my iPhone?

What do these questions have in common? They are the classic prelude to a scam whose sole purpose is to steal your money. The methods may vary, but the outcome is always the same.

This topic is so beaten to death that we had to create a separate expose channel to cover it, which is both ironic and sad.

IMPORTANT INFORMATION:

• iPhone theft via iCloud: A non-trivial threat
• Impostor clients with "unique" features
• AyuGram on iPhone: Pure fantasy
• DoxGram Leaks

What should you do?

The goal of such manipulations is phishing, aimed at stealing your credentials and financial funds.

The scenarios mentioned above, as well as data theft via iCloud and the distribution of clients with malicious functionality, are all methods of social engineering.

Think critically and stay vigilant. Do not fall for provocations and tempting offers, no matter how convincing they may seem.

Your vigilance is your greatest asset.

To increase your awareness, subscribe to our chat and carefully study the FAQ — these two resources are closely interconnected and contain answers to most questions.

If you've read this far, congratulations.

Your patience and desire for knowledge are worthy of respect, even if you didn't learn anything new. As the old wisdom goes:

Repetition is the mother of learning.

As a small reward for your diligence, we recommend checking out our entertainment channel, where we collect funny and curious moments from the life of the AyuGram community.

A list of official chats and channels related to the development of AyuGram and exteraGram

• exteraGram:
• Official Website
• GitHub
• exteraGram channel
• exteraGram Beta channel
• Releases (Android)
• FAQ
• Forum and chat for communication
• About plugins
• Channel with verified plugins
• AyuGram:
• Channel
• Forum
• GitHub
• FAQ
• Releases (Android, Desktop | Windows/Linux/macOS)
• FCM Releases

New here?

First time in our chat?

To ensure your introduction to the client is as pragmatic and productive as possible, we have implemented a captcha.

Follow this simple checklist to successfully join the ranks of AyuGram users or members of the AyuGram chat:

1. Pass the captcha: To access the chat, you must pass a verification through our bot. If you have done this before but lost access, repeat the procedure. Ensure that you have allowed the bot to send you messages.
2. Study the FAQ: Familiarize yourself with the FAQ by reading it in its entirety. Do not just randomly click on the captcha answers hoping to stumble upon the right one — read the FAQ thoughtfully and completely.
3. Yin and Yang: You have two bots at your disposal. AyuTyan (@ayutyan_bot) If you've checked the FAQ and still can't find an answer, please reach out to our support bot. AyuGuardian (@AyuGuardianBot) is required for passing the captcha and also serves as an administrative regulator. It is useful for regular users when they forget the rules and need a refresher, or if violations are found in the chat, in which case the /report command is used. A false report will result in punishment for the user who sent it.
4. Feedback: If restrictions are not lifted after successfully passing the captcha, or if you find an error in the bot's operation, please report it to @ayutyan_bot. We strive to fix such issues in real-time.
5. Why a new bot? That's just how things turned out.

Yes, you heard that correctly. You must pass a verification to write anything in the chat, but this does not prevent you from downloading and installing the application.

By adding a captcha, we solved several problems:

• We reduced the frequency of silly and repetitive questions in the chat. We grew tired of seeing the same questions asked endlessly, so we gave you a bit of "self-reliance" to find the answers to your questions.
• Flowing from the first point is the second: no ads, scams, or flooding. Be aware that your very first message in the chat undergoes a strict evaluation. It serves as a precise indicator of your intentions and can instantly determine your future right to participate in the community. We do not waste time on warnings for those who come with destructive intent.
• Claim you didn't see that question in the captcha? Fine. Then type .rc and re-read the FAQ from start to finish.
• Do you find our requirements overly strict? We consciously forgo tact and pleasantries when dealing with rule-breakers. Excuses are not accepted. We concede that first impressions can be misleading; however, the administration's prerogative will always be to maintain internal order and our own peace of mind. If our principles are off-putting to you, then perhaps this community truly is not for you.

Bots

To assist and maintain order in the chat, several bots are at your disposal. Please familiarize yourself with their functions and available commands.

AyuTyan (@ayutyan_bot) — Support bot

This is your primary assistant for resolving issues for which you could not find an answer in the FAQ.

When creating a request (ticket), please remember that there is a live person on the other side of the screen. Therefore, be polite and describe your problem in as much detail as possible: what you did, what you attempted to do to solve it, and what the result was.

AyuGuardian (@AyuGuardianBot) — Guardian of order

This bot performs several key functions for both new and long-standing members of the chat.

• For new members: It is required for passing the captcha upon first entering the chat.
• For all users:
• To be reminded of the rules: If you have forgotten a rule and wish to refresh your memory, the bot will always come to your aid.
• To report a violation: If you notice a violation in the chat, use the /report command. Your request will be forwarded to the administration.
• For the administration: It serves as the main tool for moderation and maintaining order.

Important: Abusing the report function and sending false complaints will result in punishment.

Available commands

The prefixes for using commands are . and /.

• setlang — Sets or changes the language for the bot (affects the captcha and tickets).
• start — Activates the bot and brings up the main menu in a private message.
• rules — Displays the full text of the chat rules.
• report — Sends a complaint to the administration. Use this in reply to the offender's message, briefly stating the reason. False reports are punishable.

Rule for command usage

• The use of any command not included in the list above will result in being automatically placed in read-only mode (mute) for a period of 8 hours.

This restriction is final and not subject to appeal.

This rule has been implemented to prevent flooding and to maintain order in the chat.

Now, let's go over the rules for each forum topic.

Offtop | Оффтоп

Here you can chat about various topics, as long as you don't violate the main rules. Be warned, our chat is teeming with Linux users!

Information topics

These sections contain comprehensive and up-to-date information that will serve as a reliable guide to our project.

Topics:

• «FAQ | Справочник»: Your first stop for solving common questions.
• «Android | .apk», «Desktop | Windows/Linux/MacOS», «iOS | .ipa»: Everything for Android, Desktop, and iOS users.

Specialized topics

These sections were created to make our communication as productive as possible.

This is where your valuable ideas, detailed bug reports, and honest feedback help us make AyuGram better every day.

Topics:

• «Suggestions | Предложения»: For your ideas on improving functionality.
• «Bugs | Баги»: For detailed reports on technical errors.
• «Reviews | Отзывы»: For general impressions and detailed opinions.

Make sure to read the pinned messages in these topics.

How to help a user without breaking the topic's rules?

Noticed a member asking a question in the wrong topic, or perhaps accidentally breaking the rules? There is a proper and tactful way to help them, without creating unnecessary noise or drawing the attention of the administration.

Simply reply to their message (using the «Reply» or «Quote» function), and then, through a special menu, move your response to the «Offtop | Оффтоп» topic and offer your advice there.

This way, your help will reach the intended recipient, and the main topic will remain in perfect order.

Schematically:

To avoid situations like this:

Suggestions | Предложения: How to propose an idea that will be heard?

Before suggesting an idea, it is crucial to understand the core philosophy that drives AyuGram and exteraGram.

We do not chase every Telegram update or copy features from other clients. Our priority is exclusive functionality that offers users something truly new and useful.

To ensure your suggestion is considered and not lost in the noise, follow these steps.

Step 1: Review the list of rejected ideas
This is not a formality; it is your primary filter. Carefully study the pinned message in the suggestions topic.

This list reflects our strategic direction and helps you understand which ideas are fundamentally misaligned with the project's concept. A suggestion that duplicates an already rejected idea will be ignored. Also, be sure to specify the platform for your suggestion (#mobile or #desktop).

Step 2: Formulate your suggestion
Your idea should not be a fleeting impulse, but a substantive and well-argued proposal. Ask yourself these questions:

• What problem does my idea solve? Describe a specific scenario where your feature would be useful.
• Why is this needed specifically in AyuGram/exteraGram? Justify why this suggestion aligns with our philosophy of unique features.
• How should it work? Try to briefly describe the logic of how the proposed feature would operate.

A well-thought-out suggestion is a sign of respect for our work and the best way to be heard.

Important note

Yes, it may happen that an idea from the rejected list will eventually be implemented. The decision on priorities and feature implementation always remains at the developer's discretion.

However, this is not a reason to ignore the list and repeatedly propose rejected ideas.

Bugs | Баги: How to write the perfect bug report?

Your bug report is our primary tool for fixing errors. To ensure it acts as a surgeon's scalpel rather than a jumble of incoherent text, follow this impeccable structure.

Step 0: Check the list of rejected bugs

Before you begin writing a report, take a look at the pinned message in the thread. It contains a list of already known and rejected bugs. It is quite possible that your issue is already known and does not require a new report.

Step 1: Is it really our bug?

This is a crucial check that will save both your time and ours.

Check for the bug in the official Telegram client.
Ensure you are using the official client of the same base version as AyuGram.

• If the bug is also present in the official client — its cause lies with Telegram. In this case, you should report the issue directly to the developers of the official client, after reviewing their guidelines.
• If the bug is not present in the official client — you've come to the right place. This is an AyuGram error, and we are ready to investigate it. Proceed to the next step.

Important nuance: Some bugs in the official client do not manifest immediately and are difficult to reproduce on the first try. Therefore, even if you were unable to replicate the error in the official Telegram client, after analysis, we may still conclude that its source lies within the official code. We ask for your understanding in this matter.

Step 2: The structure of an impeccable report

1. Platform and client version

• Platform tag. At the very beginning, specify #mobile or #desktop.
• Exact version. You must provide the full version number and release date (e.g., v11.12.1 20250827). This information can be found in the settings under the logo. The phrase "the latest version" will not be accepted.
• Up-to-date. Make sure you are using the most current version of the client. If not, update before submitting the report.
• Build type (Android only). Clearly state which build you are using: vanilla, fcm, or fcmweb.

2. Technical specifications

Provide detailed information about your device:

• Operating system name and exact version (e.g., Android 14, HyperOS 1.0.5; Windows 11 23H2).
• Device model (e.g., Pixel 8 Pro, MacBook Pro M3).

3. Plugin system (Android only)

This is a critically important step for diagnostics:

• Completely disable the plugin system in the exteraGram settings.
• Check if the bug is still reproducible without them.
• If the error persists, attach a text list of all your plugins to the report.

4. Camera issues

In the case of specific errors related to the camera, attach its technical parameters from the «Chats» section:

5. Description and logs

• Steps to reproduce. Your report will be invaluable if you provide crystal-clear, step-by-step instructions for reproducing the error.
• Visual confirmation. The best addition would be a clear screen recording or a series of screenshots.
• Crash logs. If the application crashed, the system automatically copies a technical report (crash log) to the clipboard. You must paste it into your report.

6. Formatting rules

To prevent large blocks of text from hindering analysis, use collapsible quotes (highlight the desired text fragment, select «Quote» from the menu, and then press «Collapse»).

• Crash logs and long descriptions. Always place them inside a separate collapsible quote.
• The main rule: It is strictly forbidden to combine the text description of a bug and a crash log within the same quote. These are two different elements and must be kept separate for ease of analysis.

Final check: Three questions to ask yourself

Before you hit "Send," ask yourself these questions:

1. Is this definitely an AyuGram bug and not an issue with the official Telegram?
2. Am I not creating a duplicate of an already existing report?
3. Is my report concise, perfectly clear, and does it contain all the necessary information?

We demand respect for our time and for order in this topic. Any disregard for the forum rules will be punished without delay.

Want to do it perfectly? Look at the examples of ideal reports below.

Procedure during temporary chat restrictions

In the event that the chat is temporarily closed or existing restrictions prevent you from attaching all necessary media files, you should prepare the bug report in your personal «Saved Messages» chat.

Format your message in full compliance with the rules, attaching all the necessary information. As soon as the restrictions are lifted and the chat reopens, you must forward the fully prepared report to the appropriate topic.

You can also use this method when the chat is unrestricted to avoid cluttering the admin logs.

Exceeding the Telegram character limit

Is your report too good for a single message?

If the total length of your report (description and crash log) exceeds Telegram's character limit for a single message, you must do one of the following:

1. Split it into two messages: The first message must contain the full text description of the bug (don't forget the technical information about your device and the client), and the second, sent immediately after, must contain exclusively the crash log itself.
2. Use a text file: Place the entire crash log into a separate text file (.txt) and attach it to your message containing the description.

Reviews | Отзывы

1. Inappropriate humor and off-topic

Any messages unrelated to the topic of discussion are strictly prohibited. This applies to both outright spam and inappropriate jokes or gags (for example, comments like «it even gets a signal in the parking lot»).

Penalty: Read-only mode for a minimum of three months.

2. Constructive criticism vs. Baseless negativity

We welcome constructive criticism. If you dislike something about the client, describe what it is and why. Your well-reasoned feedback will be heard.

However, messages consisting solely of baseless negativity («crap», «garbage», etc.) will be deleted without warning.

Penalty: Deletion of the message and a permanent ban for the author.

3. Questions already answered in the FAQ

Before you post about a problem, you are required to read the FAQ.

Messages about high battery drain, notification issues, and other topics already covered in detail in the documentation will be deleted. This is not an arbitrary rule; it is a matter of respect for the time of other members and the developers. Your unwillingness to read is your problem, not ours.

That's all for now.