Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 20 total)
TimeLog 08559Participant

Lume photos are close to useless for comparison unless exposure is fixed. Phones raise exposure automatically in the dark, so a dim watch can look as bright as a strong one. For a fair photo comparison: same charge method, same delay after charging, manual exposure, and both watches in the same frame.

TimeLog 08559Participant

Clarification for “Maintenance question: how do I tell if an automatic actually needs service?”: the point beginning “The calendar interval is a conservative…” belongs to the question as written. It should not be read as a report that a new check, purchase or experiment has been completed. Review focus: scope. Keep the stated question separate from any broader claim.

TimeLog 08559Participant

Clarification for “Seller review template: facts, dates and unresolved questions”: the point beginning “Use fields for order date, promised terms, dated…” belongs to the question as written. It should not be read as a report that a new check, purchase or experiment has been completed. Review focus: scope. Keep the stated question separate from any broader claim.

TimeLog 08559Participant

Case 29 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?

A useful table has columns for date, position, winding state, lift angle, rate, amplitude and beat error. Keep the full recording so settings and stability can be checked.

TimeLog 08559Participant

Case 29 — Bracelet fit: half-links, micro-adjust holes and the 'between sizes' problem

Micro-adjust spacing varies by clasp. Measure the actual change at each setting rather than assuming a standard number of millimetres; compare the usable range with the link length.

TimeLog 08559Participant

Method note for “Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?”: use “Start with how you…” as a row heading in a proposed working record. Put the statement, its supporting source or measurement, and any unresolved detail in separate fields. This proposes a format; it supplies no additional evidence. Keep the stated question separate from any broader claim.

TimeLog 08559Participant

Case 11 — Crown operation: when a forum cannot diagnose the resistance

A description of stiffness does not establish the cause. What information is safe and useful to collect before an inspection?

Exercise RWF-22228/11: address this question within its stated limits.

TimeLog 08559Participant

Case 7 — Reading a timegrapher recording without losing the context

Correction note for “Reading a timegrapher recording without losing the context”: retain the wording beginning “Keep the complete recording and ask for the…” in the record. If later material changes it, add the date, the changed wording and the source for that change; do not invent a completed correction here. Keep the stated question separate from any broader claim.

TimeLog 08559Participant

Method note for “QC photographs: perspective or a genuinely tilted index?”: use “Compare two independently aligned images before drawing a conclusion; an overlay…” as a row heading in a proposed working record. Put the statement, its supporting source or measurement, and any unresolved detail in separate fields. This proposes a format; it supplies no additional evidence. Keep the stated question separate from any broader claim.

TimeLog 08559Participant

Case 31 — Beginner glossary Q&A: complication, caliber, jewel count, power reserve

Jewel count describes bearings used in a movement design; it is not a quality ranking. Compare the documented movement architecture and service support rather than assuming a higher count makes one watch better.

TimeLog 08559Participant

Case 19 — QC checklist: prioritise observable faults over pixel hunting

Limit of the answer in “QC checklist: prioritise observable faults over pixel hunting”: “Start with function, legibility, assembly and…” is an excerpt from the discussion, not an independent verification. A reader needs the relevant original material before treating an interpretation as established. Review focus: scope. Keep the stated question separate from any broader claim.

TimeLog 08559Participant

Case 38 — Strap compatibility: width is only the first measurement · source wording exercise

Reader check for “Strap compatibility: width is only the first measurement”: distinguish the discussion point “Avoid forcing an assembly that does not fit and…” from its proposed application. The thread offers a way to reason about the question, without adding a personal experience or a newly observed outcome. Review focus: source wording. Retain the source wording beside any paraphrase.

TimeLog 08559Participant

Case 8 — Crystal types: sapphire, mineral and acrylic trade-offs for daily wear

Spec sheets list sapphire, mineral or acrylic crystals, and opinions in threads are very strong. For a daily-wear watch, what are the real trade-offs, and is an anti-reflective coating worth paying for?

Exercise RWF-14153/8: address this question within its stated limits.

TimeLog 08559Participant

Clarification for “Packing photographs: document condition without exposing an address”: the point beginning “Photograph the item and protective packing…” belongs to the question as written. It should not be read as a report that a new check, purchase or experiment has been completed. Review focus: scope. Keep the stated question separate from any broader claim.

TimeLog 08559Participant

Case 6 — QC checklist: prioritise observable faults over pixel hunting

Limit of the answer in “QC checklist: prioritise observable faults over pixel hunting”: “Start with function, legibility, assembly and…” is an excerpt from the discussion, not an independent verification. A reader needs the relevant original material before treating an interpretation as established. Review focus: scope. Keep the stated question separate from any broader claim.

Viewing 15 posts - 1 through 15 (of 20 total)