⛔ DO NOT SHARE YOUR BOT TOKEN.

If you make any request to any external url with token please note: your bot token can be stolen!

It is not safe!

⛔️ Don't use ad blockers.
- your token can be stolen
- in the end, we will just remove the free plan with ads

Why is there a free plan with ads?
We sell ads in bots and pay for servers, development and support.
Free ad bots only exist because we have advertisers.
If there is no ads, no advertisers, no revenue, we will remove the free plan. It's simple.

We don't want to fight ad blockers. We'll just disable the free plan. This can happen within 15 - 30 days.

⚠️ To begin with, for all accounts that use an ad blocker, we issue a warning:
- the limit for the current accounting month will be halved from 500,000 to 250,000 iterations (but you will get 500,000 again next month)
- +31 days will be added until the next reset.

If the situation worsens, you may:
- account deleting
- blocking bots by the name of the bot (you will need to change the nickname of the bot to run it on BB. Resetting the token will not help in this case)
- reduction of limits on a free tariff plan with advertising, or removal of this tariff plan altogether.

Downtime in progress

Still downtime

Uptime 🫣

Downtime

Uptime

We have DDoS attack.

1 bug was fixed, 1 core lib was upgraded, servers health performed during attack.

Thank you, attacker 💜

What's happened?

Dear users, customers. We've had a lot of good changes lately. The project is getting better and evolving.

- We have an integration with AI.
- Added VS code plugin

Users still love the free plan with ads. It really offers great opportunities. We have increased the limit to 500,000 iterations per month. It became possible only thanks to advertisers.

Therefore, we have taken the blocking of advertisements very seriously.

This fact, and the fact that a new Captains policy has been introduced, has likely led to dissatisfaction among some users.

Apparently, there was a cooperation of individual users and an attack on the BB servers was formed.

We are investigating this incident and restoring functionality. We make every effort to protect the interests of all users.

Dear clients.
We have Community. And the Community needs strong leaders. We will now call them Captains.

If you are an active user or client, namely:
- you spend more than 200,000 iterations per month
- either you buy a cloud and do it often
- buy advertising
- sell something near the project

please nominate the Captain. Your opinion is especially valuable.

We have attack again

⛔️ ONCE AGAIN !!!
DO NOT SHARE YOUR BOT TOKEN.

If you make any request to any external url with token please note: your bot token can be stolen!

It is not safe!

We still under attack.

Some services was restored.

All Clouds have +2 days

Today timeout errors - fixed

#json #jsonerror #content
What Is JSON and How to Handle an “Unexpected Token” Error

JSON, which is an acronym for JavaScript Object Notation, is one of the most popular data formats used for transmitting data. It is a lightweight format and consists of name-value pairs. Values can be strings, arrays, or any other data that can be serialized.

It is JSON example:

{
    "name": "animals",
    "animals": [
        "Dog",
        "Cat",
        "Mouse",
        "Pig",
        "Bear"
  ],
  "hobbies": {
        "football": false,
        "reading": true
  }
}

Unexpected Token < in JSON at Position 0
From time to time when working with JSON data, you might stumble into errors regarding JSON formatting. For instance, if you try to parse a malformed JSON with the JSON.parse() function or use the .json() method on the fetch object, it can result in a JavaScript exception being thrown. But don’t worry, it’s not the end of the world and we can handle it. There can be different causes for this happening so let’s see what we can do about it.

If you have a file with JSON data, one of the first things to do is to ensure that the data is formatted correctly. There are a few sites that can help you with that. These formatters not only will check if your JSON is formatted correctly, but they can also fix some of the errors, beautify it, or make it compact.

https://jsonformatter.org/
https://jsonformatter.curiousconcept.com/
https://codebeautify.org/jsonvalidator

So if you have:

JSON.parse(content)

and error - try to inspect your JSON with:

throw new Error("My JSON: " + content)  // we just throw error with JSON content
JSON.parse(content)

Go to Error Tab > copy past text after "My JSON: " > go to http://jsonviewer.stack.hu or another and check your JSON

BB AI bot now can help in the group chats.

You can install this bot from the Store.

New 🥳
Prop saving for any bot in your account.

Bot.setProperty({ name: "MYPROP", value: 10, bot_id: OTHER_BOT_ID})

let myprop = Bot.getProperty({ name: "MYPROP", bot_id: OTHER_BOT_ID})

User.getProperty & User.setProperty are also available for another bot.

We have new error:

You have much more background tasks rigth now. Limit is: 5. All active tasks - REMOVED. Commands for run_after:  and others...

If you have such error you need to reduce your background tasks.
Try to remove not needed Bot.run with run_after or try to make run_after with more bigger delay

Please note: run_after must be more then 60 - 120. With less value it is not stable.

Run after must be more stable now

We can have only 5 active tasks in background in one moment per bot.

Yes, of course you can have 100 and more future background tasks in total.
But if you have more then 5 tasks for running in one moment you will have this error.