You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd be great to append the timestamp to the message itself. At the moment, messages take ~8 minutes to reach the end user. With timestamps we could at least work around this problem until it is fixed.
The text was updated successfully, but these errors were encountered:
Sometimes people add manual timestamps, because they can only now report an event which was 20 minutes ago. We need to check whether a message already has a timestamp before appending one.
actually we don't have to.
If a person reports an event that happened 20 minutes ago, i would still take x time to be shared. The message would therefore still be out if sync; even with timestamp.
We need to take the time of the message object and use that as timestamp
With your proposal to timestamp everything, out of the tweet 1200 controllers at $place would become 12:20 1200 controllers at $place. It would appear at 12:25.
I think the person always knows better than ticketfrei when the controls happened. Meaning:
if the person already posted a timestamp, we should not add one.
Also, if the report happened not longer than a minute ago, we could leave out the timestamps.
I'd be great to append the timestamp to the message itself. At the moment, messages take ~8 minutes to reach the end user. With timestamps we could at least work around this problem until it is fixed.
The text was updated successfully, but these errors were encountered: