
Keep these fields in the source log
- Native URL and post identifier
- Account, date and context
- Profile claim or independent confirmation
Public research resources · FR / EN
How can a post be documented without premature author attribution ? Practical method, external tools, source log and interpretation limits.
External services · no results hosted here · queries sent only when you click a provider link.



A matching alias or reused photo does not link two accounts to a person. Available results also depend on server and viewing account.
Entries draw on the providers’ portals or documentation. Each entry shows its latest review date. Check the provider for current access conditions, pricing and quotas.
All words must match. Word order, accents and case do not matter.
4 entries displayed
Search public posts, terms and accounts in their publication context.
Limit: A display name does not establish identity; retain URL and timestamp.
Record reviewed
Understand search in the federated network and access relevant instances.
Record the post URL on its origin server, the full account handle with its domain and the access date. Note the server from which you ran the search.
Limit: Search depends on the server, indexing and settings; it is not exhaustive.
Publisher reference · Record reviewed
Search repositories, documentation and public software project traces.
Limit: An account or commit does not prove legal identity; do not use exposed secrets.
Publisher reference · Record reviewed
Distinguish researchers and examine public information in an ORCID record.
Retain the ORCID identifier and the origin of displayed affiliations or works, then compare with the relevant publication or institution.
Limit: Fields have different origins and visibility; a record is not universal identity verification.
Publisher reference · Record reviewed
No matching catalogue entry. Try another term or reset the filters.






Read the original record
Services using ActivityStreams describe objects and activities. Do not automatically apply these fields to other platforms.
| Item | Record to retain | Limit |
|---|---|---|
| Object | id and URL of the original publication. | A relay can have a different identifier from its object. |
| Dates | published and updated when provided. | Update time and initial publication time are distinct. |
| Attribution | attributedTo and the account relaying the object. | A declared attribution does not establish the author’s civil identity. |
Reading exercise · fictional scenario
An established account with a consistent history suddenly requests an urgent payment and refuses a call through the usual channel.
Before opening the explanation, separate what is observed from what is inferred. Identify the missing check that prevents the broader conclusion.

Its history proves the known person made the request.

History informs the account assessment. It confirms neither current control nor authorisation of the new request.

Retain the message and check the requested action through the known channel; distinguish authentic account from authorised message.
This exercise illustrates an interpretation error. It describes no real person, organisation or client case.
On the selected provider’s website, in a new tab. IIS does not retrieve, host or display investigation results. Directory filters only filter the editorial catalogue.
The launchpad builds links inside your browser, without sending the query to IIS or storing it in browser storage. Clicking a prepared link sends the query to the named provider, under its own rules.
No. Access may require an account, subscription, software or quota. The catalogue is available in French and English; providers set their interface languages, coverage and conditions.
No. Index coverage, spelling, language, access limits and capture dates can explain a missing result. Record what was searched and what remains unknown.