Every online claim has a history
Before relying on a claim, look for its original publication, attribution, later copies and subsequent changes.
Read the note ↗SHORT READS
Practical notes, without overclaiming
Browse by subject or filter the cards. These general notes are not an expert report or the result of a personal investigation.
Organise files so you can revisit them
Clear filenames, useful dates and a distinction between originals and edited versions reduce mistakes.
Read the note ↗Know what a tool can and cannot prove
Software may compare data without establishing whether an identity, statement or surrounding event is genuine.
Read the note ↗Prepare a website before publishing
Start with audience, page structure and reader journeys before choosing visual decoration.
Read the note ↗Check unexpected requests
Use an independent channel to verify requests for payment, remote access or authentication codes.
Read the note ↗Make outputs easy to check
Clickable references, relevant context and a note about uncertainty make later review easier.
Read the note ↗
RESPONSIBLE USE
Good judgement stays with the user
Access to information does not guarantee accuracy or grant unlimited rights to reuse it. For activity affecting other people’s rights, check the applicable rules and seek qualified professional guidance where needed.
Source assessment
Every online claim has a history
Begin with the earliest identifiable source you can find. A screenshot on its own may not establish when the underlying material first appeared.
If versions conflict, record the differences rather than picking whichever seems more convincing.
File handling
Organise files so you can revisit them
Use one folder for files as received and another for annotated or converted working copies.
A short register of filenames, formats and dates helps prevent confusion as the collection grows.
Interpretation
Know what a tool can and cannot prove
Matching names, pictures or text may arise from copying, coincidental similarity or other explanations.
Treat a software-generated result as an observation to examine, not a definitive attribution.
Publishing
Prepare a website before publishing
A clear page plan prevents multiple menu items and articles from competing to answer the same reader question.
Then give each section a specific purpose and a straightforward way to get in touch.
Safety
Check unexpected requests
For an urgent or unusual request, leave the conversation and return through an independently known official website or number.
Following a suspected compromise, secure affected accounts before returning to normal use.
Outputs
Make outputs easy to check
Keep the full source address wherever it may legitimately and technically be shared.
Record access dates and unresolved limitations so future readers know exactly what the output does and does not contain.
Have a problem worth solving?
An initial description is enough to explore what kind of technical support would be useful.