Saltar a los artículos
Footbillion
Volver a la revista

Compartir y comunidadArtículos en inglés

What a shared result page shows, and what it hides

A result page shows the mode, day, score, maximum and round values. It never shows answers, player names, email or question details. Here is the full picture.

Four illustrated football fans share blank scorecards around a miniature stadium.

A shared result page is a deliberately small view of a completed match. It lets another person see the score without giving them your private gameplay screen, your answers or access to your account. Understanding that boundary helps you choose what to share and what to keep in your own notes.

The page is public to anyone holding the full result URL. A friend can open it without signing in and without using the browser that played the match. That convenience is the point of the link, but it also means a recipient can forward it.

The information a reader can see

For a normal single-player result, the page presents the mode, the relevant day, the total, the maximum for that match and the round-value pattern. The pattern gives a quick impression of where points were earned or missed. It does not identify the questions behind those values.

For an archive game, the displayed historical day refers to the archived board. Its available set can be smaller than the original daily board because current overlaps are withheld. For a duel, the page shows two separate player totals, their round patterns and the winner or draw. It labels them Player 1 and Player 2 rather than revealing account names.

The £ symbol represents virtual transfer-value scoring. It is not a payment, prize balance or estimate of real money earned. Nor do the colours report live answer percentages; the underlying answer values are editorial game settings.

The information deliberately omitted

The public result does not contain answer text, player names, email addresses, question IDs, prompts, source lists or the private match state. It is therefore different from the review that a player may see within their own game.

That difference matters when choosing between a screenshot and a link. A screenshot can include whatever happens to be on your screen, including answers or browser details. A result link uses the narrower saved-score view. Choosing a link or a scorecard explains the two copy actions without changing that public boundary.

The page reads a completed result saved by the server. Its score is not taken from editable text in the chat message around it. However, because the page does not name the owner, it does not independently prove that the person forwarding the link was the player.

For a friendly competition, ask participants to submit their own results under an agreed name. For a duel, add the player-name mapping in your message if both participants are comfortable with that. Sharing a duel result covers that specific format.

Search visibility is not access control

Result pages ask search engines not to index them. That reduces their role as searchable content; it does not make the URL private once it has been posted publicly. Anyone with the address can view the same spoiler-free score.

Keep the entire URL intact, including its token. That token is scoped to the result and is needed to open it. It does not sign the reader into your account. Security-key changes or deletion of the underlying result can make an old link stop working, so do not treat it as an unconditional permanent archive.

Your private ability to revisit matches is a separate matter. Read keeping guest and account history before clearing browser data or changing how you sign in.

Finish a game, copy its result link, and share the score with a clear understanding of exactly what the reader will see.

Pon a prueba tus conocimientos de fútbol.

Siete preguntas. Respuestas menos obvias. Un nuevo reto cada día.

Jugar el reto diario