@kamikazeave
Switched all fingerprints to chrome 105 on android, cycled profiles and tested again. Improved real-time analytics degradation. success. In my view, fingerprinting in chrome 103 and chrome 104 uses the latest he BAS25.2.1, fingerprint Chrome105, modern browsers, BAS25.2.1. The updated fingerprints, which are a mixture of old BAS25.2.0 compliant fingerprints, some non-compliant fingerprints, and non-compliant BAS25.2.1 compliant fingerprints, cancel each other out, so the BAS25.2.0 compliant fingerprints Only prints are printed and the latest BAS compliant fingerprints are counted. The number of recent BAS non-conformances has decreased. So BAS25.2.0 did not decrease.
In a nutshell, the latest BAS compatible fingerprints have recently been updated to match the latest BAS. Add individual modifications and accessories to fit the latest fingers. From the above, it is an old finger that there are places that are not suitable for the latest BAS.
my thoughts. Problem solved for now. Thank you very much.
@kamikazeave said in using YouTube view with a previous BAS version:
Hiện đã bắt đầu với tập lệnh BAS25.2.1 mới nhất
FP Thẻ: Android, Chrome
Được sử dụng để thử nghiệm phát lại.
Phân tích thời gian thực cho YouTube giảm đáng kể
30% số lần giảm
Tốc độ làm việc giảm.
Lưu ý: Phát lại thành công. Chúng ta đang nói về sự suy giảm của phân tích thời gian thực.
↓Hoàn nguyên về BAS25.2.0 trước đó và bắt đầu với tập lệnh
FP Tags: Android, Chrome
Nhận số lượt xem YouTube.
YouTube Analytics không giảm.
hoàn toàn nhanh chóng. Hiệu quả công việc tốt và không bị tụt hạng là rất tốt.
I have also tried with versions, I use BAS 23 it works fine, new versions still have views deducted, are you using BAS verrison now? so that the view repeats well ?
If you do exactly the same as me,
Gradually increases from 5 to 10 without decreasing. very good condition. Latest BAS BAS25.2.1, Fingerprint, 105Chrome, Android, Proxy use Turkish ipv6 housing
If the old version of BAS stops working, it will not be reflected in the real-time analysis, so you can check it visually. A year or two ago BAS browser updates were slower than they are today. Easy to understand. The latest is pretty good if you try it in the above conditions.
As I wrote in the middle of the topic, when acquiring customers for replay, my focus is on speed and efficiency without losing large numbers of customers.
The access method is the shortest and does not decrease. Using playlists. to the customer. Please keep it as it is. Using direct playback https://www.youtube.com/watch?v= is not recommended as it reduces significantly. I used to embed it, but I stopped. The more profitable your playlists and searches, the more customers will come.
The transition is always 1.Playlist Page → 2.Playlist Video.
On IPv6, Android and Chrome, directly jumping and playing a video in a playlist fires the following events:
All the first videos are down. The second video sticks. When implementing with ipv6,
Be sure to do it from the playlist page.
I also tested a house such as ProxyRack with the following route, but the direct 2 access is not reduced. Drop behavior also changes depending on the proxy. We are verifying various things.
I haven't tried it on Microsoft Windows. Android and Chrome are required to handle many customers.
Use Microsoft Windows, Chrome, Proxy, Housing or ipv4 best quality when making money with your personal channel.
I have separate scripts for personal and customer use. Personal channel earnings are based on Microsoft Windows, Chrome, Proxy and Housing
Navigate and play from YouTube Search and Home. When
Offer Android and Chrome playlists to your customers. Reduce drops without wasting access. We are working quickly towards our goal of achieving thousands of plays in the shortest amount of time with the least amount of effort.
@kamikazeave How are things with drop likes?
@venom777
For likes, please use the same country proxy where you created your Google account. It will fail if the proxy country where you created your Google account and the proxy country you are currently using are different.
Apart from that, YouTubeAi is strict on time and intervals. Important here. Fall again at the same pace interval. Because it will fall, it will fall if it is unnatural. Click like random nature. Points are randomly placed. It fails if the country where you created your Google account and proxy is different. Some people continue because they fall quite a bit. It doesn't fall even after 2-1 hours, but the speed is slow. Anyway, start by matching the country you created with the surrogate country. Then you can do whatever you want with a modest speedup.
As a supplement,
Please check with the seller before purchasing a Google Account.
If you create your own Google Account, be aware of your proxy country. Make sure that the country where YouTube Likes Google account is created matches his proxy country. IMPORTANT I have a random country proxy country unknown google account. NO! You have to plan ahead and remember. Everything becomes slow work. Failure.
@venom777 said in using YouTube view with a previous BAS version:
@kamikazeave
Iam maker of youtube premium accounts and viewing via that accounts.
Which version of BAS using and fingerprint, can you tell me more about your settings.
Iam also developer and working in one Youtube View bot for personal earn and use.
If you want telegram contact we can talk about that privatly.
@nejooflixx
Please use the latest BASver latest fingerprint. If you play the revenue income with the old BAS (ver23, ver24), it will be treated as 100% invalid traffic, so in the case of YouTube, the only way is the latest BAS. Use the latest, even if it's heavy!
Fingerprint settings can be found by scrolling up.
@kamikazeave thanks for writing your experience. i have some question about subscribers using BAS . what speed/ hour be used for subscription to prevent drop ?
looking for your expert opinion.
@andy231
Just click the channel page ➡ latest video ➡ channel button on the video page. There are examples of such migration routes. Since the video page is a place that is frequently referenced and clicked, I personally use this transition route.
Also, regarding the time setting of the main subject,
Here's a bad example:
Bad example) Click the channel button exactly at 60 minutes. This pattern always diminishes after a few days regardless of the time and number of times you set it.
This will decrease after a few days. Click the channel button every 20 minutes. This pattern also diminishes over a few days.
Same pattern NO!
good analogy)
After 10 minutes, click the channel button for the first time.
From there, click the channel button after 50 minutes.
From there, click after 43 minutes. From there, click after 16 minutes.
As above, the time should be random.
Again, decrease if the time pattern is the same.
For example, channel button clicks decrease from half a few days of clicks to 50% after 10-30 minutes of waiting. Narrow time interval NO!
Perfect makes the intervals more random by specifying a wide range of random settings between 5 minutes and 1 hour 15 minutes. Subscriptions are important. We see YouTube as a punctual bot. Randomly OK from 5 minutes to 75 minutes. does not decrease. As a side note, for playback the time is less strict. Abnormally reduced after 10,000 playbacks for approximately 1 second. My experience value is 10000 times in 10 to 60 seconds and the number of views does not decrease. Currently, this is the number of customers doing views. Anyway, YouTube channel subscription and YouTubeLIKE, especially these two, the natural time setting is a random time setting with a wide range of intervals.
@kamikazeave said in using YouTube view with a previous BAS version:
answer.
1.1. Follow the answers above to use your account. I have 3000 accounts and 30,000 views are successful. No drop.
- I will answer. 30 days for Android for direct playback, 10-30 drops for 370 views per hour for real-time analytics. 30 days on Microsoft Windows, Chrome, the drop in real-time analytics is even smaller.
I noticed that for YouTube playlists, there are fewer drops than direct playback.
Currently I am using the above ipv6 static and residential, webshare shared rotation ipv4.
Cookies use profile actions. Easy. I remembered what a super veteran developer wrote. I wrote that it's good for your account because the profile folder has a lot of information.
Also, since the current BAS is browser 101, lowering the fingerprint to a low value such as 97 will increase the drop. So I always get the Fingerprint Switcher with a number that is the same as or higher than the current version, after figuring out the best BAS browser. Fingerprint settings when downloading. In the extreme case, if you set your browser version to 90, you will get a lot of YouTubeViews drops below: Probably Youtube
I don't like the old browser ver. Drops even working fingerprints. That is playback. As a side note, if you start fingerprint authentication at the same time as access, it will drop significantly after 5 days, so once you read the fingerprint authentication using only the profile action on the bot that fully downloads and plays the profile, it will not drop. .. Apply in advance. Another Fingerprint Switcer bot is running permanently in about two threads. This is due to logout avoidance, 3000 accounts only, and my own workaround when using a rotation proxy or a different proxy each time. The account doesn't do anything. Normal for 2 years. This also prevents your account from logging out later.undefined my way. Some translations are strange, but thank you for reading.
3000 account and 30000 plays ... How many proxy do you use and how do you reuse one proxy to other account? Do you bind proxy or use different proxy each time ? And how many views from one account per day ?
About 10 times a day per account.
It has 30000 views (3000 accounts).
The proxy uses 96000IP. at this point.
When I wrote the above, IPV6 only had 10000IPs.
not decrease at all. The reason is that fingerprinting updates multiple views X accounts X fingerprints three times a day. because there is
By the time the account entered his second week, the number of views had reached 6000.
Meanwhile, the fingerprint is constantly updated.
Fingerprint all 3,000 accounts by week 3
Updating to another new fingerprint.
We achieved 9000 views in the 3rd week.
Repeat the above three times. We achieved 30,000 views in 24 hours.
By the way, the number of views per day per account is about 10.
If you want to use one proxy for multiple accounts, use proxy action.
Fingerprint updates are automated by proxy bindings. BAS specification! However, when accessing, the script uses a proxy action. !The reason is that 30,000 views is not possible without multiple IPs. In the view, even if the IP is covered by any chance, the fingerprint is not covered. That means that the two views will naturally be established.
@kamikazeave said in using YouTube view with a previous BAS version:
About 10 times a day per account.
It has 30000 views (3000 accounts).The proxy uses 96000IP. at this point.
When I wrote the above, IPV6 only had 10000IPs.
not decrease at all. The reason is that fingerprinting updates multiple views X accounts X fingerprints three times a day. because there is
By the time the account entered his second week, the number of views had reached 6000.
Meanwhile, the fingerprint is constantly updated.
Fingerprint all 3,000 accounts by week 3
Updating to another new fingerprint.
We achieved 9000 views in the 3rd week.
Repeat the above three times. We achieved 30,000 views in 24 hours.By the way, the number of views per day per account is about 10.
If you want to use one proxy for multiple accounts, use proxy action.
Fingerprint updates are automated by proxy bindings. BAS specification! However, when accessing, the script uses a proxy action. !The reason is that 30,000 views is not possible without multiple IPs. In the view, even if the IP is covered by any chance, the fingerprint is not covered. That means that the two views will naturally be established.
Do you update fingerprint on each run or reuse the same fingerprint ?
Each time it runs, the number of views decreases if the fingerprint update and YouTube watch progress scripts are only one time. All work should be two scripts separated by their respective scripts.
Ex) fingerprint update script and view count script. This division of work does not reduce the number of views. came like this
@kamikazeave Don't you get a lot of SMS re-verifications or banned accounts when you change IPs and fingerprints on your accounts that often?
@clarence
I have been using this method for 2 years. Problems with SMS numbers in particular can lead to SMS re-verification and account bans. Here are my thoughts. Her SMS buyers with different phone numbers on many accounts often have duplicate phone verification numbers on Google. This is the number one reason for SMS re-verification and account banning. High prices simply do not suffer. This is just the result of my own experience. We currently have 3000 accounts and no re-verifications or account bans. So I changed her her IP and fingerprint many times, no problem. From this, I personally feel that the SMS number is the cause.
My method of frequently updating fingerprints also avoids Google auto-logout.
That is strange, I also have about 3000 accounts and none of them have a number as recovery option, only email but I still get a lot of SMS verifications out of the blue (by "a lot" I mean every 4 months or so). These numbers then don't get added as recovery-option though, they only are there to annoy you it seems. :)
I have to admit I very rarely change useragents or fingerprints in browsers.
Hi bro!
I have many question on youtube view bot. Can you share your telegram contact again ? I can’t contact with you on it. Because it is only group chanel.
I want to buy some script from you if you buy it.
My telegram user is @mssikejer
Thanks in advance.
@baslunguyen oke i have :D
