Wala pa ang pahinang ito sa inyong wika. Binabasa ninyo ang tekstong Ingles.
Glossary
WebGL vendor string
A WebGL vendor string is the line a browser returns for the maker of the graphics chip that draws a page.
Where the string comes from
A page asking WebGL who is drawing gets a masked answer first. The real names arrive once the debug renderer extension is switched on, and any page may switch it on without a prompt. The whole reading takes a few milliseconds, shows nothing on screen and keeps answering after storage has been cleared.
The maker name is the coarse half of that answer. It sorts machines into a few large groups and leaves the narrowing to the renderer line beside it. On Windows it is one of the makers of desktop cards; on a Mac it is either Apple silicon or the older Intel graphics.
Your vendor string right now
These values are read in your browser on this page. Nothing leaves it and no request goes out with the reading. The vendor line is the short one and the renderer line beneath it the long one.
Ang inyong makina, ngayon mismo
- WebGL vendor
- sinusukat sa inyong makina
- WebGL renderer
- sinusukat sa inyong makina
- Platform
- sinusukat sa inyong makina
Binasa sa inyong browser at ipinapakita rito. Walang ipinapadala kahit saan.
What the name has to agree with
A maker name is cheap to edit and cheap to contradict. The four readings below are taken by one page in one pass and have to describe one machine. Any one of them can be rewritten on its own, and agreeing with the other three is what rewriting cannot supply.
The renderer line
It names the chip, the graphics layer and the shader levels. A maker that does not appear inside that line is a contradiction on the same screen.
The processor architecture
Client hints report the processor the browser runs on. Apple silicon beside an architecture of x86 is a machine nobody sells.
The platform
A Mac maker on a Windows platform is read faster than an untouched string would be. So is a Windows driver line on Linux.
The drawn frame
Pixels produced by the hardware do not follow an edited name. A page reading both then holds a contradiction instead of a maker.
Where our value comes from
The vendor line is not kept in the profile. It is derived on every launch from the profile seed and handed to the browser before the first page runs. Nothing about the machine is stored as a list of values that could drift apart.
The maker and the chip are drawn as one pair for the platform, so they cannot point at two machines. The chip in that pair then settles the cores, the memory, the system version and the reported architecture.
A value chosen by hand goes through the same rule. A pick that contradicts the cores or the memory is refused by name rather than saved and quietly dropped.
How to check your own
The panel above shows what the browser you are reading this in reports. The self-test lives in the app and runs inside a profile against the engine that profile launched.
It prints the maker the seed asked for next to the one that came back, so a mismatch reads as two lines rather than a score.
Run it in two profiles on one computer. Two makers where there is one machine is the reading worth having, and one pass shows both of them.
What this does not do
- It does not let a profile claim any maker. The pair belongs to a platform, and a Windows chip next to a Mac platform is a louder signal than an untouched line.
- It does not hide that the unmasked reading exists. A browser answering with nothing there is rarer than any particular maker, so the refusal becomes the trait a page remembers.
- It does not change the frame the hardware draws. The name and the picture are two readings, they are covered by different work, and a page is free to take the second one.
- It does not make a profile anonymous. Behaviour, address reputation and account history close more accounts than a maker name does.
Check it
Everything above comes from a file you can open.
- The line the self-test compares against the seed
- apps/desktop/src/lib/fpAudit.js
- Where the maker and the chip are drawn as a pair
- packages/shared/src/index.js
- The acceptance run of the build shipping today
- engine/приёмка-отчёт.json
- A build is not accepted until these hold
- engine/scripts/engine-invariants.js · engine/scripts/accept-engine.js
Questions
- Why does my browser answer WebKit?
- That is the masked answer WebGL gives by default. The maker appears only once the debug renderer extension is enabled, and the panel above enables it to read the two lines.
- Is the maker name enough to identify me?
- On its own, no. It sorts machines into a few large groups, and the identifying work is done by the renderer line and the drawn frame beside it.
- Do two profiles report two makers?
- They can. On our engine the pair is drawn per profile from what that platform really reports, so two profiles on one computer describe two machines.
- Does a VPN change it?
- No. A VPN changes the address your traffic comes from. This line is produced on your machine and never travels through the network.
- Can I pick the maker by hand?
- Yes, from the values a real machine of that platform reports. A pick that contradicts the cores or the memory is named back to you instead of being saved and lost.
See what your own profile answers
The self-test runs inside a profile and reports all 29 measurements by name, green and red alike.