contacts: format_timestamp treats Unix seconds as days #76

New issue

Closed

opened 2026-04-20 08:01:02 +00:00 by zaelgohary · 1 comment

zaelgohary commented

2026-04-20 08:01:02 +00:00

Member

contact_detail.rs:273-287 does let days = ts / 86400 then checks against 365.

created_at / updated_at are Unix seconds (~1.7e9), so every real timestamp renders as ~55 000 years ago.

Fix: match the messaging pattern — diff against platform::current_timestamp_ms() / 1000, format relative or absolute based on age.

`contact_detail.rs:273-287` does `let days = ts / 86400` then checks against 365. `created_at` / `updated_at` are Unix seconds (~1.7e9), so every real timestamp renders as ~55 000 years ago. Fix: match the messaging pattern — diff against `platform::current_timestamp_ms() / 1000`, format relative or absolute based on age.

zaelgohary self-assigned this

2026-04-20 08:01:02 +00:00

~~zaelgohary referenced this issue 2026-04-20 08:10:23 +00:00~~

contacts: polish detail view — header, status pill, unified layout, parallel fetch #80

zaelgohary commented

2026-04-20 09:04:35 +00:00

Author

Member

Dropping this. We decided not to show Created/Updated to users, so no formatter is needed. #77 still covers the server-state correctness piece (form no longer zeroes stored timestamps).

zaelgohary closed this issue

2026-04-20 09:04:35 +00:00

zaelgohary referenced this issue from a commit

2026-04-20 09:10:06 +00:00

contacts: hide timestamps from detail view, breadcrumb uses name, uniform field rows