Această pagină nu este încă în limba dumneavoastră. Citiți textul în engleză.
Academy
What a browser cannot fix
Lecția 14 din 14
Where a browser stops
A profile is a separate browser: its own folder on disk, its own derived device, its own way out to the network. Two profiles have nothing in common that a platform could compare.
That is the whole of what any browser does, ours included. Everything that travels with you rather than with the machine arrives at both accounts unchanged.
What a profile leaves alone
The first lesson of this course listed four signals and said the last of them has no browser answer. This is that row written out.
| What links two accounts | Where it lives | What a browser can do |
|---|---|---|
| Behaviour | Your hours, your speed, the order you do things in | Count pages and show a pace |
| Money | One card, one bank account, one payout name | Nothing |
| Identity checks | A document photo, a selfie, a phone number | Nothing |
| Content | The same bio, the same photos, the same links | Nothing |
| Platform ties | Follows, invites, reviews, messages between your own accounts | Nothing |
| The rule itself | One account per person, stated in the platform's own terms | Nothing |
Behaviour is a signature
You work at the hours you are awake, click at the speed you read, and write the way you write. A dozen accounts doing that at once look like a dozen copies of one person, because that is what they are.
A platform needs no device reading for this. It compares your accounts to each other and to everyone else's.
The pace hint and its limit
ARMANOS counts one thing about the way you work: pages opened in a profile today, against a recommended number for that use case. A new profile starts low and grows to the full number over its first week.
That number is advice, and the app never stops an action. It also sees only that a page opened, not that the page was an invitation being sent, so the numbers for single actions are shown rather than tallied.
One card is one person
On ad accounts and marketplaces the payment method is the identity. The same card on two accounts is a link the platform makes on its own side, and no browser setting reaches it.
The same holds from the other direction. One payout name behind several seller accounts joins them in the minute money moves.
Documents and the person behind them
When a platform asks for a document photo or a selfie, it is asking about a person rather than a machine. One person has one set of documents.
ARMANOS can produce the sign-in code for an account you already hold, so a phone is not part of every login. It cannot produce a second person.
The same words in two places
Two shops with the same product photos, two profiles with the same bio, two proposals opening on the same sentence. None of that needs a technical reading to come out as one seller.
Automation sharpens this rather than softening it. A flow can wait a random number of seconds before the next step and will still type the sentence you wrote for it.
Ties inside the platform
Your accounts can point at each other with no help from a browser: one follows another, one invites another, one leaves a review under an order the other shipped.
A message between two of your own accounts is the plainest case of all. Both halves of it sit on the platform and neither half passes through your device.
Where the work is yours
The list above is not a set of settings. It is a way of working, and most of it is decided before a profile is even open.
One account, one story
Different photos, a different bio and a different way of writing, chosen once and kept.
Separate money
Whatever pays for one account is better off not paying for the next one.
Your own rhythm
Each account worked at the hours you would really work it, not all of them in one sitting.
The platform's own rule
Many platforms allow one account per person, and they state it openly in their terms.
What this lesson does not claim
- It does not tell you how to get around anything on that list. There is no browser setting for a single item of it.
- Many platforms allow one account per person, and that is written in their own terms. Neither this lesson nor the app changes it.
- The app counts pages opened in a profile. It does not count platform actions, and it stops none of them.
- The pace numbers in the app are our own defaults. No platform published a figure to us.
- Nothing here is guidance about one particular platform. Their rules differ and they change.
Where you can see this yourself
Every line about the app on this page is something its own code says out loud.
- The daily counter counts pages opened and blocks no action
- apps/desktop/src/lib/pace.js
- A page count belongs to the window that reported it and never to a profile named inside the message
- apps/desktop/test/page-ipc-trust.js
- A profile's isolation is its own browser folder and reaches no further than the machine
- apps/desktop/src/lib/forkEngine.js
- A sign-in code is built from a secret you already hold
- apps/desktop/src/lib/totp.js
Questions
- Then what is a browser for?
- It takes the device, the session and the exit out of the comparison. Those are the signals no amount of care removes.
- Would a second card solve the money link?
- Two cards in one name are still one name, and a browser sees neither of them. This lesson does not arrange your payments for you.
- Does the app hide what I post?
- No. It opens pages, and the words and pictures in them are yours.
- If I never repeat a sentence, is that enough?
- You have taken one item off the list. Hours, money, documents and platform ties are still on it.
- Why does the course end here?
- Because the first lesson named four signals and left the last one open. This is that one, spread over a whole lesson.
The whole course in order
Every lesson takes one signal off the table, and they build on each other.