Sometimes we still had errors with App login - FIXED

RUN after - FIXED

ResourcesLib - it is Core Lib now.

You can use it via:

Libs.ResourcesLib.xxx  

or new way (shorter!):

ResLib.xxx

Why we need core Libs?
- It is about speed.
- Installation is not needed

@DemoResBot - migrated to new database now.


We still continue work. Some bugs are possible

We just made some tune work for new database.
@DemoResBot - on old database now and will be moved again to new database something later

We just made one of speed upgrading

50% of traffic is now executed no more than 0.8 seconds! 🎉

Before upgrade it was 1.8 - 2.2 sec 😱

It is more then +100% speed! 🎉🎉🎉

95% of traffic is now executed no more than 2.1 seconds! 🎉

Before upgrade it was 8 secs 😱

It is more then +400% speed! 🎉🎉🎉


Only 5% of traffic take more then 2 secs now!

6 hours stat.
9:20 am - upgrade

Speed Up: PHASE 1
https://telegra.ph/Speed-Up-PHASE-1-08-05

All Speed phases:
https://trello.com/b/aSsZiFlW/bb-speed-development

#WebhookLib new:
#Webhook link with redirect_to param - FIXED

Sometimes this code have timeouts:

var res1 = Libs.ResourcesLib.userRes("cloud1")
var res2 = Libs.ResourcesLib.userRes("cloud2")
var res3 = Libs.ResourcesLib.userRes("cloud3")
..
var res10 = Libs.ResourcesLib.userRes("cloud10")

You can try to use //!noPrePropsLoading flag:

//!noPrePropsLoading
var res1 = Libs.ResourcesLib.userRes("cloud1")
var res2 = Libs.ResourcesLib.userRes("cloud2")
var res3 = Libs.ResourcesLib.userRes("cloud3")
..
var res10 = Libs.ResourcesLib.userRes("cloud10")

it is another props loading method.
BB try load all props by one request to database - it is more quickly.
If you use //!noPrePropsLoading - props loading separately. As a rule - it is slowly but sometimes it can be without timeout.


#noPreLoading

🕹 Update:

Props reading limit is increased from 100 to 200 props

🧶 NEW:

New param user_telegramid is added for Bot.run

Now it is possible to run any bot command for other user by his telegramid:

Bot.run({ command: "otherCommand", user_telegramid: TG_ID })

BJS become more flexible. You can do anything on that command: read another user's props and etc.

NEW! ⚡️⚡️⚡️

You can read and set user's prop by telegramid now:

Bot.setProperty({
    name: "balance",
    user_telegramid: TG_ID,
    value: 10
})

read:

let balance = Bot.getProperty({
name: "balance",
user_telegramid: TG_ID
})

✍️ You can set (or read) property via bot_id.
Then:
you can read (or set) it via telegramid.
💪🏽 It doesn't matter and it will be the same value.

Why is this needed?
Sometimes we don't have user.id:
- for user's forwarded message
- for replies
- and etc

So it is hard to access to user's prop by user.id field because only telegramid are available in such cases.

Very good Youtube videos:

https://www.youtube.com/playlist?list=PLbeq98OlPk4j_8-ZV_zduRYytYTtJQLeB