Trang này chưa có bằng ngôn ngữ của bạn. Bạn đang đọc bản tiếng Anh.
Academy
The first week of a new account
Bài 5 trên 14
Why a young account is fragile
A platform judges an account against its own past, and a new account has none. What it does today is the entire record.
An account with three years behind it can have a strange day and keep its standing. An account three hours old has nothing else to be read by.
Day one before the first login
The first day is setup, and the account is opened at the end of it rather than at the start.
Everything in this list happens before the platform sees anything at all.
- 1
One profile for one account
The use case you pick sets the start page, the tracker lists and the daily numbers.
- 2
An address of its own
The proxy goes in before the first launch: a first login from your home address cannot be taken back.
- 3
The exit named out loud
The start page opens first and shows the address, the country and the engine behind this profile.
- 4
The self test
Test fingerprint in the card menu runs the checks inside a real browser and reports how many passed.
- 5
A history before the account
The cookie robot browses ordinary public sites in the profile, so the account is opened in a browser someone has been using.
- 6
The login, last of all
Sign in, read a few pages and stop. A short first day is a good first day.
The first week in order
Nothing below is enforced by the app and none of it comes from a platform. It is a careful shape for the week, and the numbers beside it are the ones the app carries.
| Day | What the day is for | What waits |
|---|---|---|
| Day 1 | One profile, its address, the first login | Everything else |
| Day 2 | Ordinary reading at a different hour | The first real action |
| Day 3 | The first few actions of the real kind | Volume and a second account |
| Days 4 to 6 | More of the same, under today's number | Flows and schedules |
| Day 7 | The full ceiling is available | Nothing, if the six went quietly |
The ramp day by day
A new profile does not carry its full daily number on day one. It starts at a fifth and reaches the whole figure on the seventh day.
Day one is the day the profile was created, and the same fractions touch every per-action number.
| Day | Share of the ceiling | A social profile |
|---|---|---|
| Day 1 | 20% | 40 of 200 |
| Day 2 | 35% | 70 |
| Day 3 | 50% | 100 |
| Day 4 | 65% | 130 |
| Day 5 | 80% | 160 |
| Day 6 | 90% | 180 |
| Day 7 and after | 100% | 200 |
What the app counts for you
One counted action is one page opened in a profile window. The count belongs to the window that reported it, so a page cannot add to a profile it does not run in.
The day starts over on the change of the UTC date rather than at your local midnight. A deleted profile takes its counter with it.
Counted
A page you open in the profile: an address you type, a link you follow, a redirect that lands somewhere new.
Counted as well
A page a recorded flow opens, because it loads in the same profile window as the rest.
Not counted
Frames inside a page, images, background requests, and the start page the app opens for you.
Not counted either
A tab you opened an hour ago and are still reading.
A warning, not a lock
The bar under the count is green below 80 percent of today's number, amber from there, and red at it. Nothing is prevented at any point.
A block would mean the app deciding for you, on a figure we chose, about an account it knows nothing about. The number sits in front of you so the choice is an informed one.
The per-action numbers beside the bar are shown rather than tallied. A browser sees a page open, not an invitation sent.
Why bulk work costs most early
Fifty accounts signing in inside one minute from one machine read as one script, whatever the fifty names say. In the first week there is nothing else about them to read.
A bulk launch waits a random 3 to 14 seconds before every opening after the first, and that is the most a browser can do here. The rest is the work itself: the same text, the same hour, the same order.
Day seven and after
From the seventh day the full ceiling applies and the card stops naming a warm-up day. It shows how long ago the profile was made instead.
That line is the age of the profile on your machine, not of the account behind it. A profile made today for an account from 2019 still reads day 1 of 7.
What this lesson does not claim
- The day plan here is our advice and not a rule any platform published. No site handed us a figure.
- The app does not count platform actions. Invitations, posts and listings are shown as numbers for the day, and none of them is tallied.
- Nothing in the app stops an action at the ceiling. It counts pages, colours the bar and leaves the decision with you.
- The warm-up counts from the day the profile was created, not from the age of the account behind it.
- A careful week does not make a second account allowed. Some platforms permit one per person, and that rule stays theirs.
Where you can see this yourself
The numbers in this lesson are read out of the product, not chosen for a page.
- The seven fractions of the ramp and the ceiling each use case carries
- packages/shared/src/index.js
- The daily counter and its fresh start on a new date
- apps/desktop/src/lib/pace.js
- The page report that counts, and the start page that does not
- apps/desktop/src/main/browser-preload.js
- The stand that keeps this page honest about the ceiling
- apps/web/test/потолок-это-ориентир.js
Questions
- How long does a new account need?
- The profile counter reaches its full number on the seventh day. The standing of the account itself takes months, and no browser sets that clock.
- Does the app stop me at the number?
- No. The bar turns amber at 80 percent of today's number and red at it, and the decision stays yours.
- I made the profile today for an old account. Does the ramp still apply?
- Yes, because day one is the day the profile was created. The app cannot know the age of the account behind it and does not pretend to.
- Can ten new profiles be warmed up at once?
- The cookie robot runs over a selection and gives each profile its own sites in its own order. Ten accounts created in one hour is still a pattern no browser touches.
- Does a scheduled run spend the same budget?
- Yes, pages a flow opens land on the same counter as your own clicking. A slot missed while the computer slept is not replayed, and a schedule that came from another machine does not run here until you allow it.
See the numbers for your own use case
Each use case carries its own ceiling and its own first day.