Перейти до вмісту

Вашою мовою цієї сторінки поки немає. Ви читаєте англійський текст.

Accounts

How to give a new profile a history before login

The profile was created five minutes ago: no cookies, no history, an empty cache. A platform sees that emptiness before the fingerprint, because a browser that has really been used looks different. Below is the order in which a profile builds a past before the first sign-in: where to go, how long it takes and how to set it up.

Команда ARMANOS7 minUpdated

In short

An empty browser stands out. A used browser has cookies, history and cache, a new one has none.

The Cookie robot gives it a past. The profile walks ordinary public sites, and no sign-in is needed anywhere.

Three minutes per profile. Eight addresses at twenty seconds each, and the time is shown before you start.

What a used browser carries

A browser used for a week carries cookies of dozens of sites, history entries, cache files and saved settings. A profile created five minutes ago is empty.

A VPN changes the address you come from and leaves the emptiness of the profile as it is. A virtual machine hands over the same emptiness one level up.

What a site sees on arrival

A page cannot read your history: no site is handed that access. It sees its own side: whether its cookie is there, its storage slot empty, this browser here before.

An empty history on a site where you supposedly have an old account is a contradiction within one visit. A walk through ordinary news and shops removes it on the sites it visited.

A profile's past is one of several conditions

A profile's past works together with the phone, the payment details and what you publish. The Cookie robot closes the most visible thing: an empty history.

Browsing open sites before the login

Cookie robot in the profile menu sends your profile to ordinary public pages before you go there: it opens an address, lets it settle, scrolls, waits and moves on.

The same six steps fall on every address, and with the box Click “Accept” in cookie consent windows ticked a seventh: click Accept in the consent window when there is one.

The cookies are set by the site itself, in the profile's session, through its proxy and with its fingerprint.

They land the way they will tomorrow from your own hand.

  1. 1

    Open

    Go to the address and wait for it to load.

  2. 2

    Settle

    A short pause while the page finishes its scripts and pictures.

  3. 3

    Scroll

    Down by 400 to 1100 points, the way a person skims a page.

  4. 4

    Read

    A second pause. The longest one comes third, just before leaving.

  5. 5

    Scroll again

    Another 300 to 1200 points further down.

  6. 6

    Leave

    A last pause, then the next address.

The Cookie robot window: the number of sites, seconds on each and profiles at once, with Start below.

Thirty addresses of six kinds

The built-in pool holds thirty addresses of six kinds, all over https, none in two kinds at once.

Under What to browse, tick what suits the job: a shop profile leans to Shopping and Search.

Not one address in the pool asks anybody to sign in, and that is deliberate. A profile that hits a sign-in wall gets an empty history and failed sessions.

KindAddressesWhat is inside
Search4Bing, DuckDuckGo, Brave Search, Ecosia
News6BBC, Reuters, The Guardian, AP, Al Jazeera, DW
Shopping5eBay, Etsy, AliExpress, IKEA, Zalando
Reference5Wikipedia, Stack Overflow, GitHub, IMDb, Archive.org
Video and forums5YouTube, Reddit, Pinterest, Twitch, SoundCloud
Everyday5Weather, Booking, Tripadvisor, Allrecipes, ESPN

Why two profiles take different routes

Two profiles that walked the same sites in the same order in the same minute traded one giveaway for another. What ties them now is the route, not the emptiness.

The selection and the order belong to each profile, not to the run.

Each draw is its own and independent: it does not forbid two profiles from overlapping, it simply does not arrange them.

  • Which addresses

    From the kinds you ticked, or a list of your own.

  • In what order

    Its own for every profile, not one shared by the run.

  • How evenly

    Across six hundred draws no address came up first more than fifteen times in a hundred.

How long the walk takes

You see the time before it starts: addresses times seconds, plus three seconds for each move.

The window offers 3, 5, 8, 12, 20 or 30 addresses and 10 to 90 seconds on each, with 8 and 20 by default.

By default profiles go one at a time, so the wait adds up, and the Profiles at the same time field takes up to five.

By number, more than 40 addresses or more than 300 seconds each will not run.

8 addresses, 20 seconds each
about 3 minutes per profile
12 addresses, 30 seconds each
about 7 minutes
20 addresses, 45 seconds each
about 16 minutes
30 addresses, 60 seconds each
about 32 minutes

The seconds you pick are a middle, not an exact figure: the real pause lands at 60 to 140 percent of it, and the scroll depth differs.

Six or seven steps on every address

Without the cookie consent box the profile takes six steps in a row on every address: it opens the page, waits, scrolls down, waits, scrolls further and waits before leaving.

Three pauses of different lengths, and the longest comes last.

With that box ticked, and it is ticked from the start, a seventh step follows the first pause: the robot clicks Accept in the consent window, and with no window it moves on.

The pauses are cut from the time you gave to an address: a quarter, three tenths and almost a half.

So two walks with the same time per address still move to a different rhythm, and a platform sees a person rather than a metronome.

How many addresses of each kind

The six kinds in the pool are uneven: news has six addresses, search four, shopping, reference, video and forums and everyday five each. Thirty in all.

The walk takes addresses from the kinds you left ticked in the window, and the fewer the kinds, the smaller the choice.

Leave only Search ticked and the walk goes to four addresses, however many you asked for: it cannot take more than that kind holds.

Eight addresses make three minutes

Eight addresses at twenty seconds each come to about three minutes per profile: the pauses inside an address add up to those same twenty seconds rather than on top of them.

By default profiles go one at a time, so ten profiles make half an hour, and five at the same time cut that to about six minutes.

The window shows the time estimate before the start, and it is counted by the same shares as the pauses themselves, so the length holds no surprises.

Your own list instead of the pool

The Cookie robot window has a Use my own list instead field: one address per line, up to sixty.

As soon as there is a single line in it, the pool of thirty is not used at all, and the What to browse boxes above it stop mattering.

Only addresses that begin with http or https are taken. If the list has a line without that beginning, the window does not start the run and names those lines, so paste full addresses rather than bare site names.

The time estimate in the window recounts itself for your list.

What stays with you after the walk

The walk opens a page, waits and scrolls, and with the consent tick it presses "Accept" in the cookie consent window.

It does not follow links or sign in anywhere: it has no logins, only a history.

The walk gives a profile a past on other sites. On the platform you made the profile for, you make the first sign-in yourself, and it becomes the first entry of the history there.

The order of the first hour

The proxy goes on before the walk: a past picked up through another exit is worse than none. The login comes last, better the next day.

Count what the day costs. Eight addresses are the whole first day of an ads profile and a fifth of a social one.

  1. 1

    The exit first

    Attach the proxy and check the address: the walk goes out through it.

  2. 2

    Then the walk

    Eight addresses at twenty seconds each is about three minutes per profile.

  3. 3

    Count the pages

    Every page opened goes into the profile's day: on day one an ads profile has 8 of 40, a social one 40 of 200.

  4. 4

    The login last

    Open the account once the task centre says the run has finished.

Common questions

Do empty cookies on their own get an account banned?
No. It is one argument, not a verdict, and a platform decides out of many. But hiding it costs three minutes.
How many sites should I take the first time?
Eight by default, about three minutes per profile. More than thirty out of the built-in pool is not possible: it holds exactly thirty addresses.
Does anything have to be signed into during the walk?
No, and not one address in the pool asks for it. A profile that hits a sign-in wall leaves an empty history and failed sessions.
Can I walk ten profiles at once?
Yes, and each ends up with its own list. By default profiles go one at a time: ten profiles at three minutes each is half an hour. The Profiles at the same time field takes up to five.
Which address does the walk go out through?
Through the proxy of the profile that is walking. Attach the exit before the walk, not after: a past through another address is worse than none.
Does this replace warming up over days?
No, this is its first hour. The daily ramp starts at a fifth of the daily figure: 40 pages for a social profile instead of 200, 8 for ads instead of 40.

Give a profile three minutes of past

The Cookie robot walks the chosen sites inside the profile by itself: the time is shown before it starts.