You already linked to this
The reason why Ecto’s
timestamps()are naive by default is backwards compatibility.
In what way doesn’t that address your question?
It is my impression that the core team by convention treats time data without a timezone as UTC.
Confusion typically arises with people coming from other backgrounds who may have been working with a different convention - assuming that timezone free data is recorded with reference to local server time or local client time - which may be immediately convenient in the local context but creates problems in a long term historical or global context.
