3 797
Obunachilar
-224 soatlar
-177 kun
-6730 kun
Postlar arxiv
3 797
Discover MetaL Builders — a place for the stories, projects, and people of the Bots.Business community.
Intro:
https://www.youtube.com/watch?v=j1FjnZ8efS4
🏆 Three completed MetaL seasons and $1,375 in season rewards
🔍 Hidden quests and the stories behind the leaderboard
🛠 Bots, tools, and ideas built by the community
🎂 Ten years of Bots.Business history
Explore the website → https://metal.builders
3 797
Discover MetaL Builders — a place for the stories, projects, and people of the Bots.Business community.
🏆 Three completed MetaL seasons and $1,375 in season rewards
🔍 Hidden quests and the stories behind the leaderboard
🛠 Bots, tools, and ideas built by the community
🎂 Ten years of Bots.Business history
Explore the website → https://metal.builders
3 797
📚 We’ve completely rebuilt the Bots.Business Help Center
We updated everything — the structure, learning materials, BJS examples, and app screenshots.
Up-to-date instructions and screenshots. New mobile screenshots show where to find each screen and what to tap.
A clearer start for beginners. You can go from creating your first bot to building a working menu. You don’t need programming skills to get started.
JavaScript basics with real BJS examples. Variables, conditions, loops, and functions are explained through practical bot-building tasks.
Three learning paths: your first bot and menu → data and dialogs → HTTP, webhooks, and Mini Apps. Each stage has a clear result and a way to verify it.
Updated references and ready-to-use recipes. Current BJS methods, libraries, data handling, file sending, and integrations. Examples were checked against the actual app code.
Better reading on mobile. Step-by-step instructions, clearly labeled code examples, highlighted requirements, and expandable explanations.
Tips from Mel. She points out the parts that are easy to misunderstand and helps explain tricky concepts.
Better troubleshooting. Guides now take you from the symptom → to the check → to a specific action.
You can now use the Help Center in the way that works best for you: learn step by step, quickly find a recipe for a specific task, or open the reference for the BJS method you need.
👉 https://help.bots.business
3 797
⚠️ Telegram Service Issues
Telegram is currently experiencing regional service issues, primarily affecting users in Asia and Oceania. The incident may be related to Telegram’s DC5 infrastructure in Singapore, although Telegram has not officially confirmed the cause.
Some users may experience:
• Slow or unresponsive bots
• Delays when sending or receiving messages
• Slow Telegram app performance
• Temporary connection errors
If your bot has suddenly become slow or stopped responding, the issue is most likely on Telegram’s side—not with your bot’s code or account.
No action is required. Please wait while Telegram restores normal service. We will update this post when more information becomes available.
3 797
🎉 Promise kept!
During the MetaL event, we made a simple promise:
If a participant wins the MetaL event three times in a row - finishing 1st or 2nd place each time - we will send them $180 for a monitor.And now the condition has been completed. ✅ The winner received a $180 monitor reward. Congratulations! Consistency, effort, and results matter. #epicQuest
3 797
🏆 Metal Trust Season 3 is finished
The season is officially over.
We rewarded 17 participants (+2 extra members) with a total prize pool of $570.
Winners:
anu* — 4989 MetaL — $250
kri* — 3195 MetaL — $120
mhd* — 2804 MetaL — $60
naa* — 1908 MetaL — $10
ffw* — 1335 MetaL — $10
pra* — 1190 MetaL — $10
sya* — 1132 MetaL — $10
fox* — 628 MetaL — $10
ado* — 610 MetaL — $10
upl* — 536 MetaL — $10
son* — 497 MetaL — $10
rej* — 453 MetaL — $10
upl* — 350 MetaL — $10
ptm* — 333 MetaL — $10
abh* — 322 MetaL — $10
viv* — 293 MetaL — $10
son* — 282 MetaL — $10
Congratulations to all rewarded participants.
Thank you for taking part in Metal Trust Season 3.
The season was difficult, but it helped us see what must be improved before the next Seasons.
We will continue improving the rules, anti-fraud checks, and reward system to make future seasons more fair and more trusted.
3 797
Congratulations to the winners!
All rewards will be credited within three days.
Please check your wallet within 24 hours! If your wallet is missing, your reward will NOT be paid and claims will NOT be accepted!
- The first-place participant is disqualified.
3 797
MetaL Season Update
We have an additional review of suspicious activity in the current MetaL Season.
We found strong signs of artificial traffic generation through webhook calls: a group of similar bots was creating a large number of events by sending and immediately deleting messages. This pattern does not look like real user activity.
As a result:
- The participant
upl*, who was in 1st place, has been removed from the Leaderboard and excluded from the current MetaL Season.
- @coderajinkya has been removed from the admin team until the situation is fully clarified.
- MetaL rewards for Active AD have been disabled.
This ad type currently has a very small volume, so it is safer to remove rewards completely than to fight possible abuse manually.
MetaL should reward real activity: real bots, real users, and fair competition.
Artificial traffic, fake events, and attempts to manipulate the system are not allowed.
See detailed report in attachment3 797
🤖 Bots.Business now supports MCP
With MCP, compatible AI clients can connect to your Bots.Business account and help you manage bots directly from chat.
You can use AI to create bots, edit commands, work with BJS code, check settings, fix errors, and improve bot logic.
MCP server URL:
https://appapi.tgbot.ai/mcpAfter connecting, you will log in through Bots.Business and authorize access to your account. New to AI bot creation? Start here: https://bots.business/chatgpt It is the simpler way to create and edit Bots.Business bots with AI. MCP is for users who want to connect Bots.Business with external AI tools and work from their own AI client.
3 797
MetaL Trust Season 3
he Challenge We Are Facing
We want to be as transparent as possible about the situation surrounding MetaL Trust Season 3.
During our data analysis, we identified significant volumes of artificial traffic. These are not isolated incidents or statistical noise. We are seeing signs of large-scale activity that does not match the behavior of regular users.
Before getting to the core of the issue, we would like to highlight an important point.
We appreciate that participants study the system, explore opportunities, experiment, and take additional steps to achieve better results. This reflects an entrepreneurial mindset, a willingness to understand how things work, and a drive to find a competitive advantage.
If viewed purely as an attempt to exploit system mechanics to achieve a goal, traffic manipulation does involve a certain degree of ingenuity. Yes, it is a controversial tactic. Yes, it represents unfair competition. But the fact that people carefully analyze the rules of the game and look for ways to gain an advantage demonstrates initiative and resourcefulness.
However, this does not mean that we encourage such behavior.
Our position remains unchanged: we support a win-win strategy in which all participants in the ecosystem benefit. The best results should come from creating value for users, not from manipulating the system or harming competitors.
At first glance, the solution seems simple: identify the offenders and penalize them.
But the situation is much more complicated.
Let's consider two scenarios.
Scenario #1
A participant deliberately generated artificial traffic for their own bots and gained an advantage over other participants.
In this case, the situation is fairly straightforward: such results cannot be considered fair.
Scenario #2
The artificial traffic was directed at a competitor.
For example, someone could intentionally inflate another participant's bot metrics so that the bot would later appear suspicious and become subject to penalties.
In this case, the affected participant becomes a victim of manipulation. And this is where the main problem arises. At this point, we can detect signs of artificial activity.However, we cannot reliably determine: * who initiated the manipulation; * whose interests it served; * whether the bot owner organized it or was actually its victim. Because of this, every possible solution has significant drawbacks. Possible Option #1 Exclude artificial traffic from the results calculation and remove any MetaL earned through such activity. At first glance, this seems fair: participants are rewarded only for real users, while artificial activity provides no benefit. However, there are several serious issues with this approach. First, it is impossible to separate artificial traffic from legitimate traffic with complete accuracy. Any analytical system has a margin of error. This means that some artificial traffic may remain in the results, while some legitimate traffic may be mistakenly excluded. Second, this approach does not truly solve the problem of future manipulation. If a participant knows that, in the worst-case scenario, the artificial traffic will simply be removed from the calculation, the risk is minimal. If the manipulation goes undetected, they gain an advantage. If it is detected, they simply return to their original result. This creates a situation where attempting manipulation becomes a rational strategy and may only become more sophisticated in future seasons. Possible Option #2 Exclude artificial traffic from the results calculation, remove any MetaL earned through such activity, and additionally penalize participants whose accounts show signs of manipulation. This approach appears stricter and may reduce the incentive for abuse. However, it introduces another problem. We cannot reliably determine who actually organized the manipulation. If a participant genuinely generated artificial traffic for themselves, a penalty may be justified. But if the manipulation was orchestrated by competitors specifically to target them, t
3 797
The Apdex score for the last 3 days is not good, with a total downtime of 1 hour.
We are investigating this issue now.
You can check it on status.bots.business.
