Feature #6284

Display time in local timezone

Added by intrigeri about 12 years ago. Updated about 6 years ago.

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Internationalization
Target version:
Start date:
2015-10-27
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

Currently, the displayed time (in the GNOME clock applet) is UTC, which is uninteresting at best for most users.

An idea would be to have a custom clock applet.

Team: sajolida, ? (coder)


Subtasks

Feature #10434: Document differences between displayed time zone and time zone reported by programs Confirmed

0


Related issues

Related to Tails - Feature #5842: Document timezone Resolved
Related to Tails - Feature #5306: Prevent gweather from disclosing customized location Resolved
Related to Tails - Bug #7103: Verify that GnuPG does not leak timezone in email signatures Resolved 2014-04-17
Related to Tails - Feature #14544: Spend software developer time on smallish UX improvements In Progress 2018-08-31
Related to Tails - Feature #7439: Decide whether to remove the "clock synchronization" notification Confirmed 2014-06-22
Has duplicate Tails - Feature #10819: Allow changing timezone in session Duplicate 2015-12-31
Blocks Tails - Feature #5774: Robust time syncing In Progress 2015-05-17
Blocks Tails - Feature #12094: Persistence preset: localized timezone for displayed time Confirmed 2016-12-28

History

#1 Updated by OneST8 about 12 years ago

Just a quick note that I’ve started writing a suitable panel applet clock as per mailing list discussion.

#2 Updated by intrigeri about 12 years ago

  • Status changed from Confirmed to In Progress

OneST8 wrote:
> Just a quick note that I’ve started writing a suitable panel applet clock as per mailing list discussion.

Great!

#3 Updated by BitingBird about 11 years ago

When it’s done, modify the FAQ accordingly.

#4 Updated by intrigeri about 11 years ago

  • related to Bug #7103: Verify that GnuPG does not leak timezone in email signatures added

#5 Updated by intrigeri about 11 years ago

Pinged Kevin about it, asking for a status update.

#6 Updated by intrigeri about 11 years ago

  • Priority changed from Low to Normal

Raising priority, as that’s the shortest path to fixing a hole in the roof (Feature #5306), and most of the work was done already.

#7 Updated by BitingBird about 10 years ago

(also, it’s asked quite often on irc. maybe priority should be raised further, or a milestone set)

#8 Updated by OneST8 about 10 years ago

Sorry for dropping the ball.

Will look into finishing the project ASAP.

#9 Updated by intrigeri about 10 years ago

> Will look into finishing the project ASAP.

Woohooo! :)

#10 Updated by BitingBird about 10 years ago

  • Assignee set to intrigeri

intrigeri, can you please add OneST8 to the project’s contributors and re-assign the ticket to them :)

#11 Updated by intrigeri about 10 years ago

  • Assignee changed from intrigeri to OneST8

#12 Updated by intrigeri about 10 years ago

#13 Updated by intrigeri about 10 years ago

  • Target version set to Hardening_M1

This blocks the new design for Feature #5774, so setting the same target version.

OneST8, any news? If you don’t have time to work on it, that’s fine: just say so, and we’ll (try to) find someone else to complete the great work you did :)

#14 Updated by sajolida about 10 years ago

  • Description updated

#15 Updated by sajolida about 10 years ago

  • Target version changed from Hardening_M1 to 2017

#16 Updated by intrigeri about 10 years ago

  • Assignee deleted (OneST8)

The “almost ready” proposed implementation we had a couple years was in Python (https://git-tails.immerda.ch/kevin/clock/), and it likely should now be adjusted for GNOME Shell (so JavaScript).

#17 Updated by intrigeri about 10 years ago

There’s https://github.com/kckrinke/tailsclock as well, which might have more stuff.

#18 Updated by intrigeri about 10 years ago

#19 Updated by Dr_Whax about 9 years ago

  • Target version deleted (2017)

#20 Updated by OneST8 about 9 years ago

I am very sorry for this project.

The code is on github[0] if anyone wants it, but as a personal stance against the trends of the Tor project this year, I’ve purposefully held off doing anything to help them or their surrounding projects. I don’t care where project funding comes from but I do care about how the project members conduct themselves and as such I am removing myself from any voluntary efforts to assist their supposed causes.

I value and respect the needs of those users that depend on Tor (and Tails) but clearly the waters are polluted and it seems that nobody should consider Tor trustworthy any more. This was my personal, private, torstrike[1] before that became a thing.

I’m removing myself from all notifications on this (and other such threads). If/when Tails finds a Tor replacement, I would reconsider my choice in “voting with my volunteer hours elsewhere”. I know I’m just a flea in this project-space, but due to the highly sensitive and easily personally damaging nature of these projects; I’m forced to be cautious about my personal involvement and so never put more than a proverbial toe into these waters.

Again, I apologize for being involved and then bailing out due to my personal levels of paranoia.

[0] https://github.com/kckrinke/tailsclock
[1] http://pastebin.com/eMzJ8ZuH

#21 Updated by intrigeri about 9 years ago

  • blocks Feature #12094: Persistence preset: localized timezone for displayed time added

#22 Updated by Anonymous about 8 years ago

  • blocked by deleted (Feature #12094: Persistence preset: localized timezone for displayed time)

#23 Updated by Anonymous about 8 years ago

  • blocks Feature #12094: Persistence preset: localized timezone for displayed time added

#25 Updated by sajolida about 7 years ago

  • related to deleted (Feature #10819: Allow changing timezone in session)

#26 Updated by sajolida about 7 years ago

  • has duplicate Feature #10819: Allow changing timezone in session added

#27 Updated by sajolida about 7 years ago

  • related to Feature #14544: Spend software developer time on smallish UX improvements added

#28 Updated by sajolida about 7 years ago

A technical friend of mine contacted about how to change time in her Tails. She said it was needed for Tor to function. I understand that synching the time to UTC and at the same time warning people that a good clock is needed for Tor might be very confusing: they might think that the clock in UTC is unsynced. Getting rid of the warning would solve this.

#29 Updated by sajolida about 7 years ago

  • related to Feature #7439: Decide whether to remove the "clock synchronization" notification added

#30 Updated by intrigeri about 7 years ago

  • Subject changed from Display localized timezone to Display time in local timezone

#31 Updated by Anonymous about 6 years ago

  • Status changed from In Progress to Confirmed