neue medienordnung plus - nmoplus@hub.freecommunication.org

Time of client device in hubzilla timestamps - a bug or feature?

Mon, 20 Nov 2017 11:22:50 +0100

I browsed the thread start.hubzilla.org erroneously as open hub declared from 19.11.2017 with one Raspberry PI. Can you find one bug here?

Is it a bug or feature, that hubzilla use time of client device in hubzilla timestamps? In my opnion, is it a bug. Please Vote: Bug - yes or no?

#BugOrFeature #timestamp #clientDevice @Hubzilla Development+ @Hubzilla Support Forum+

BugOrFeature clientDevice timestamp bugOrFeature

show all 6 comments

mrjive

Mon, 20 Nov 2017 11:40:06 +0100

Does your ruspberry have the right date and time? I see 17:12 as current time, bit I bet it's not the correct time, right? Maybe it's just this...

Alexandre Hannud Abdo

Mon, 20 Nov 2017 12:00:35 +0100

Seems to be a feature. I wanna know the time in reference to my time, not the server's time.

neue medienordnung plus

Mon, 20 Nov 2017 12:22:54 +0100 last edited: Tue, 21 Nov 2017 17:34:50 +0100

@alexandre Mean you, is it no bug - s. Screenshot - for Raspberrry time 14 may 2017 ? My Raspberry have false time (may 2017)

I wanna know the time in reference to my time, not the server's time.

In my opinion it is useful for time-Tags in those events as sent time of message in ZOT-Netzwerk use the UTC https://en.wikipedia.org/wiki/UTC .

Alexandre Hannud Abdo

Mon, 20 Nov 2017 12:27:40 +0100

Perhaps it should say '6 months in the future' ;)

Maria Karlsen

Mon, 20 Nov 2017 19:33:51 +0100

What is in your channel settings? (Settings => Channel Settings => Time Zone) You can pick UTC (Other) or any other time zone of your choice.

neue medienordnung plus

Tue, 21 Nov 2017 09:03:16 +0100 last edited: Tue, 21 Nov 2017 17:33:09 +0100

My channel settings was Timezone: Berlin. I tryed with Timezone: UTC - produced no improvement, no changes for displayed timestamp.

//EDIT: The bug is caused by assumption, that time of client device is correct. If client device time is wrong is time information also buggy.
//EDIT2: no changes for age of posts.