Skip to content
RepWatchForumSign in

Forum Replies Created

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

Case 27 — Seller review template: facts, dates and unresolved questions

Use fields for order date, promised terms, dated communications, delivery evidence and resolution. Leave unsupported fields blank and separate observations from opinions; this reference is not a seller endorsement.

Case 32 — Clasp photographs: what to request before judging alignment

Request open and closed views from both sides, with the watch supported safely. Separate cosmetic alignment from whether the clasp engages reliably; functional concerns need hands-on inspection.

Case 73 — Strap compatibility: width is only the first measurement · comparison exercise

Method note for “Strap compatibility: width is only the first measurement”: use “Measure the lug opening and document bar diameter,…” 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. Make the basis of a comparison explicit before interpreting it.

Clarifying question: does anyone in the thread have access to both versions at once? Without simultaneous comparison, every claim either way is weak evidence. If not, the next best option is photos with a grey card in frame and white balance locked or set manually, which at least makes separate photos roughly comparable.

Case 4 — Forum comparison archive: link the evidence and the correction

Limit of the answer in “Forum comparison archive: link the evidence and the correction”: “Add a dated correction near the original conclusion…” 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.

Case 1 — Lume comparison: keep exposure and charging conditions consistent

Method note for “Lume comparison: keep exposure and charging conditions consistent”: use “Treat the comparison…” 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.

Request a level straight-on image with the hands clear of the marker. Compare two independently aligned images before drawing a conclusion; an overlay cannot correct an oblique camera angle.

Clarification for “Forum comparison archive: link the evidence and the correction”: the point beginning “Add a dated correction near the original conclusion…” 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.

Case 31 — Strap compatibility: width is only the first measurement

Method note for “Strap compatibility: width is only the first measurement”: use “Measure the lug opening and document bar diameter,…” 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.

Case 34 — First QC request: the minimum useful information

Limit of the answer in “First QC request: the minimum useful information”: “State the model configuration, the specific concern 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.

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.

Method note for “Strap compatibility: width is only the first measurement”: use “Measure the lug opening and document bar diameter,…” 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.

Case 34 — Model comparison: dive bezel action and alignment, how to compare fairly

Summary table proposal: click count, back-play (none, slight, noticeable), click consistency around the rotation, and alignment (straight-on photo, offset in fractions of a click). With that, the thread can compare actual properties instead of trading adjectives. Dated corrections welcome below.

Case 33 — 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-09822/33: address this question within its stated limits.

Clarification for “Reading a timegrapher recording without losing the context”: the point beginning “Keep the complete recording and ask for the…” 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.

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