#1934 new defect

abolish timezones

Reported by: davidsarah Owned by:
Priority: normal Milestone: eventually
Component: dev-infrastructure Version: n/a
Keywords: twisted standards time pratchett aliens error aesthetics interstellar-exploration Cc:
Launchpad Bug:

Description (last modified by daira)

Timezones are inconvenient for project development and programming. This ticket is for brainstorming possible approaches to this problem.

Suggestions so far:

  • build a ring world.
  • flatten the earth somehow.
  • have everyone adapt their working hours to UTC.
  • http://twistedmatrix.com/trac/ticket/5000.
  • relocate to the Discworld, then stop its sun from orbiting (note: the latter may have undesired side-effects).

Change History (16)

comment:1 Changed at 2013-03-19T23:25:21Z by davidsarah

  • Keywords twisted standards added

comment:2 Changed at 2013-03-19T23:26:12Z by zooko

I'd just like to point out that "flatten the earth" would not really achieve the goal of this ticket. It might have other benefits though, so perhaps we should move it to a separate ticket.

comment:3 Changed at 2013-03-19T23:26:26Z by zooko

  • Description modified (diff)

comment:4 Changed at 2013-03-19T23:26:39Z by zooko

  • Description modified (diff)

comment:5 Changed at 2013-03-19T23:29:26Z by davidsarah

  • Version changed from 1.9.2 to n/a

comment:6 Changed at 2013-03-20T21:39:12Z by davidsarah

  • Description modified (diff)
  • Keywords pratchett added

comment:7 Changed at 2013-07-08T19:45:24Z by daira

  • Description modified (diff)

At LeastAuthority.com we have had considerable success with the "have everyone adapt their working hours to UTC" option. I recommend it!

comment:8 follow-up: Changed at 2013-07-08T20:50:23Z by nejucomo

I realize this isn't a strict requirement, technically, but having a universal LAFS grid could be a useful "stepping stone" feature for constructing a ring world. See #2009.

Also, as kind of a branding thing, if other intelligences discovered our ring world, but found we did not have a universal grid, wouldn't it be kind of embarrassing? What if we send a readcap to our greeting of peace and mutual prosperity, only for them to discover they are on the wrong grid?

comment:9 in reply to: ↑ 8 Changed at 2013-07-14T15:40:17Z by daira

Replying to nejucomo:

Also, as kind of a branding thing, if other intelligences discovered our ring world, but found we did not have a universal grid, wouldn't it be kind of embarrassing? What if we send a readcap to our greeting of peace and mutual prosperity, only for them to discover they are on the wrong grid?

You're absolutely right. We'd better fix #403 stat before SETI succeeds.

comment:10 Changed at 2013-07-14T15:42:38Z by daira

  • Keywords aliens error aesthetics added

comment:11 Changed at 2013-08-08T23:10:35Z by daira

  • Keywords interstellar-exploration added

There may be unexplored synergies between this ticket and LeastAuthority's interstellar exploration goals. Exciting!

comment:12 Changed at 2015-06-01T00:21:55Z by mik

This is a misfeature - timezones are an enormous boon to capacity management.

For example, if you had everyone kick off a backup at 3am local time, then the spread of 3am around the world would allow you to have much lower throughput systems than if it was the same everywhere (you would have a massive spike at 3am).

This is also why ISPs have both "business" and "residential" products - very few successful ISPs would target only one of the two. Generally they have a mostly-uncontended daytime load ("business") then let the cheaper residential customers fight over the same capacity when they get home from work.

See also follow-the-sun support - this is a method of providing 24hr support teams without having a graveyard shift.

In short, LAFS grids are likely benefiting from disperse timezones.

comment:13 Changed at 2016-01-05T16:38:30Z by daira

  • Keywords joke removed

comment:14 Changed at 2016-02-02T19:26:33Z by warner

The buildbot's github_posthook has been intermittently broken since 25-Oct-2015. This is the mechanism by which Github notifies our buildbot that a change has been committed, so it can kick off the unit tests, tarball-building, etc.

Eventually, "intermittent" was refined to mean "only broken for Daira's commits". Daira lives in a timezone which moved from +0100 to +0000 on 25-Oct-2015. Github apparently emits "timestamp" values that are formatted like 2016-01-31T11:02:50-08:00 for any timezone that's not exactly +0000, but like 2016-02-02T18:55:34Z when the timezone is exactly +0000. The github_posthook regexp which attempted to parse these fields (and recover a sensible seconds-since-epoch value from it) failed to handle the "Z", throwing an exception, and not registering the commit.

After I've fixed the regexp, maybe I'll ask GitHub to contribute some cycles towards http://twistedmatrix.com/trac/ticket/5000 . I suspect it will help resolve (or at least mask) their uptime issues as well :).

comment:16 Changed at 2016-11-07T14:36:56Z by leif

The New York Times is on to this now http://www.nytimes.com/2016/11/06/opinion/sunday/time-to-dump-time-zones.html which led twitter to show me this argument against https://qntm.org/abolish

Note: See TracTickets for help on using tickets.