Five mistakes and what they cost

Every mistake below is one the app already refuses or warns about, which is how we know people meet it. The costly ones end the same way: two accounts answering with one and the same thing.

Lezione 13 di 14

How these five were chosen

They are taken from the refusals and warnings the app prints. A mistake nobody runs into does not get its own message.

The table is the whole lesson in one place. The sections after it say what was done and what a platform reads.

The mistake	What can be read	What closes it
An unchecked exit	A clock and a language that need not match the address	One press of Test on that row
A rotation on trust	The address of the session before it	The line that says changed or still the same
One exit on many profiles	One way out with several identities behind it	The library spread across the selection
One profile open twice	Two live sessions of one account	The question the app asks before a takeover
Too many windows	A burst of sessions from one machine	The queue that waits for a free slot

An unchecked exit

A window opens on an address nobody has measured since the day it was bought. A dead address loads nothing and the launch is wasted.

The costlier case is an address that answers while its country stays unknown. The clock and the language of that profile are then set without a country to follow and may not match the address.

What happened
A profile was launched on a library row nobody had checked since the seller sold it.
What a platform reads
A clock and a language list that need not agree with the address the request came from.
What to do instead
Press Test on that row. The answer is the exit address, its country and the time to the first response.

A rotation taken on trust

The seller answered, so the address changed. Sellers accept that command far more often than modems act on it.

So the address is measured before the command and again after it, and you are told which of three things happened: it changed, it is still the same, or it could not be checked yet.

What happened
A rotation link was walked and the next window was opened without reading the answer.
What a platform reads
The address of the session before it, now carrying a second account.
What to do instead
Read the line under the row. A profile switched to ask for a fresh address before each launch stays closed when the command fails.

One exit behind many profiles

Two accounts leaving through one address is the same link as two accounts on one machine, seen from the other side. It costs a platform nothing.

The library counts this for you. Every row says how many profiles stand behind that address, and a button lists them by name.

What happened
A batch of new profiles was given the address that was bought first.
What a platform reads
One way out with several identities behind it, and that is the cheapest link a platform can make.
What to do instead
Select the profiles and spread the library across them. Each one takes the next entry in turn and windows that are open are skipped.

One profile open twice

One profile folder must never be shared by two browsers, so a second copy of the same profile does not start. On this computer that is the end of it.

Across two computers it is the expensive one. The app asks before a takeover and names the machine holding the profile and since when.

What happened
The same profile was started on a second computer, or a flow was run on a window that was already open.
What a platform reads
Two live sessions of one account from two places at once.
What to do instead
Close the window where it is already open, or take the profile over and let the windows on that side close.

Too many windows at once

The refusal to open one more is the mild half of this. The other half is that many browsers knocking on one platform from one machine look like what they are.

Nothing already open is closed. How many windows a machine holds is computed from the memory it reports rather than written into the app.

What happened
Start was pressed on a long selection, and the number in the refusal was read as the ceiling.
What a platform reads
A burst of sessions from one machine inside one minute.
What to do instead
Let the queue carry it. A bulk launch, a flow run and a schedule wait for a free slot instead of writing the profile off.

The mistake with no browser answer

Timing, content and account history stay yours. Fifty accounts posting one text in one minute need no shared address to be linked.

Nothing in the app will ever print a refusal for this one. That is why it sits at the end.

What this lesson does not claim

It does not rank these five by how often they happen. They are chosen from the lines the app prints, and the app keeps no count of causes.
It does not cover the rules of any one platform. A second account may be against them, and no browser setting changes that.
It does not promise that spreading the library gives every profile its own way out. A pool shorter than the selection repeats itself.
It does not claim a profile refuses to open on an unchanged address. The switch before a launch stops it when the command fails, not when the address came back the same.
It does not say how many windows your machine holds. That number follows the memory it reports and changes with the machine.

Where you can see this yourself

Each claim above is one place in the code and one stand.

The proxy check takes the launch road, and the exit country is resolved where the clock reads it: apps/desktop/test/proxy-check-uses-bridge.js · apps/desktop/test/exit-geo.js
A rotation reports three distinct answers rather than folding them into two: apps/desktop/test/proxy-rotation.js
The library is spread one entry at a time, and an open profile does not eat its place: apps/desktop/test/proxy-round-robin.js
A profile already open elsewhere is not opened twice, and the open ceiling follows the machine's memory: apps/desktop/test/profile-busy.js · apps/desktop/test/предел-открытых.js

Questions

Which of the five is the worst?: One exit behind many profiles and one profile open twice. Both hand a platform a link it need not work for.
Does the app stop me from making these?: It stops two of them: a profile already open elsewhere and one window past the ceiling. The other three are lines you have to read.
The seller said the rotation worked, so why does the app disagree?: It does not disagree. It asked the proxy for its address afterwards and got no answer, which is what a modem in the middle of reconnecting looks like.
Can I put one address behind several profiles on purpose?: People do, for accounts that are meant to look related. The count on the row is there so this stays a decision rather than an accident.
Why is behaviour last and not first?: Because the four before it are closed by settings and behaviour is not. Putting it first would suggest the others do not matter.

Next to this

Check the exits before the next launch

Check all walks the library one row at a time and says how many answered.

How to check a proxy Academy