How to give a new profile a history before login

A browser used for a week carries cookies from dozens of sites, history entries, cache files, page icons and saved settings. A profile made five minutes ago carries none of it.

A VPN changes the address you arrive from and nothing in that emptiness. A virtual machine hands it over one layer up.

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 slot on a site where you supposedly hold an old account is a contradiction inside one visit. The walk removes it where it went: on the platform itself the slot stays empty, because the walk never signs in.

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.

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 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.

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.

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.

Profiles go one after another, so the wait adds up. More than 40 addresses or more than 300 seconds each will not run.

On every address the profile takes six steps in a row: it opens the page, waits, scrolls down, waits, scrolls further and waits before leaving. Three pauses of different lengths, and the longest comes last.

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.

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 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.

Profiles go one after another, so ten profiles make half an hour. 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.

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.

The walk opens a page, waits and scrolls. It does not follow links, clicks nothing and signs in nowhere: it has no logins and no goal beyond the history itself.

So on the platform you created the profile for, the trail after a walk stays empty. The walk gives a profile a past on other people’s sites, not on yours: the first sign-in there you make yourself, and it becomes the first entry in its history there.

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.