#unixtime

[sudrien-scratched013]

Happy 1700000000 unixtime

[alistairmcclymont]

http://www.alistairmcclymont.com/unixtime/

moving on from the iphone app version of this artwork its been entirely remade in web code - much more accessible and enables me to use the principle to do something a bit experimental.

[asaaki]

Playing again with some #Arduino. 🎛️🕐⚡👨‍🔧 #Kabelsalat #embedded #board #microcontroller #tech #hardware #wire #lcd #rtc #time #unixtime #fun (hier: Berlin, Germany)

[gaeraecom]

[jacob-cs]

from_unixtime() converting unix timestamp to mysql timestamp

FROM_UNIXTIME(unix_timestamp), FROM_UNIXTIME(unix_timestamp,format)

Returns a representation of the unix_timestamp argument as a value in 'YYYY-MM-DD HH:MM:SS' or YYYYMMDDHHMMSS.uuuuuu format, depending on whether the function is used in a string or numeric context. The value is expressed in the current time zone. unix_timestamp is an internal timestamp value such as is produced by the UNIX_TIMESTAMP() function.

If format is given, the result is formatted according to the format string, which is used the same way as listed in the entry for the DATE_FORMAT() function.

mysql> SELECT FROM_UNIXTIME(1196440219);         -> '2007-11-30 10:30:19' mysql> SELECT FROM_UNIXTIME(1196440219) + 0;         -> 20071130103019.000000 mysql> SELECT FROM_UNIXTIME(UNIX_TIMESTAMP(),     ->                      '%Y %D %M %h:%i:%s %x');         -> '2007 30th November 10:30:59 2007' Note: If you use UNIX_TIMESTAMP() and FROM_UNIXTIME() to convert between TIMESTAMP values and Unix timestamp values, the conversion is lossy because the mapping is not one-to-one in both directions. For details, see the description of the UNIX_TIMESTAMP() function.

[karltryggvason]

Unix time and the year 2038 problem

Unix time1 is an important concept in contemporary computing:

Unix time, or POSIX time, is a system for describing instants in time, defined as the number of seconds that have elapsed since 00:00:00 Coordinated Universal Time (UTC), Thursday, 1 January 1970 not counting leap seconds. It is used widely in Unix-like and many other operating systems and file formats. Due to its handling of leap seconds, it is neither a linear representation of time nor a true representation of UTC.

--Unix Time | Wikipedia

If you read this post around the time I published it the unix time should be somewhere around 1.376.173.661

1767696870

The current unix time

var c; tickTockClock = function(){ window.clearTimeout(c); var d = new Date(); var t = Math.round(d.getTime()/1000).toString(); document.getElementById("clock").innerHTML = t document.getElementById("clockheading").innerHTML = "The current unix time" c = window.setTimeout('tickTockClock()', 1000 ) } tickTockClock();

Apparently nerds out there celebrate or observe significant events in unix time like the Unix Billenium at 01:46:40 UTC on 9 September 20012. Another significant date will occur in 2038:

The year 2038 problem may cause some computer software to fail at some point near the year 2038. The problem affects all software and systems that both store system time as a signed 32-bit integer, and interpret this number as the number of seconds since 00:00:00 UTC on Thursday, 1 January 1970. The furthest time that can be represented this way is 03:14:07 UTC on Tuesday, 19 January 2038. Times beyond this moment will “wrap around” and be stored internally as a negative number, which these systems will interpret as a date in December 13, 1901 […] Because most 32-bit Unix-like systems store and manipulate time in this format, it is usually called Unix time, and so the year 2038 problem is often referred to as the Unix Millennium Bug.

–The year 2038 problem | Wikipedia

Wikipedia has a good gif explaining the concept:

The whole Wiki article and related links are a good read. But my favorite part has got to be this:

Current Players of the game Candy Crush, and other games or Apps which are programmed to impose waiting-periods, are running into this problem when they attempt to work-around the waiting-period on devices which harbor the coding by manually setting their device’s, (such-as the Nexus 7®), date past 19 January 2038.

It doesn’t cite sources, so maybe it’s just bs. But I just love the thought of someone cheating so much in Candy Crush that the clock on his or hers device is set to the year 2038! Cough up some dollars, ask your friends for a few lives, or better yet go easy on the Candy Crush mate!

Anyway doomsday prophesizers could probably do worse than picking Tuesday, 19 January 2038 for their next upcoming apocalypse3. If you are programming you could go with 64 bit dates, that should sort you out until december 4th in the year 292,277,026,596. But it would probably be best to go with 128 bits, future-proofing, better safe than sorry and all that…

“It’s a unix system, I know this“ ↩

I hereby pledge to celebrate the second billenium: 03:33:20 UTC on 18 May 2033, hope you join me! ↩

Since the Mayans and 2012 didn’t work for them ↩

[hazbon]

日付～UNIXタイムスタンプ変換 日付からＵＮＩＸタイムスタンプを計算します。 普通の人はあまり使わないかも・・・ ＷＥＢプログラミングで日時で制御するときなどに使います。 例えば、何日の何時に締め切りますなど。 2011年10月10日00時00分00秒の　UNIXタイムスタンプ：　1318172400

[hwmemo01-blog-blog]

Windows Powershellでズレてないunixtimeを取得 #powershell

UnixTImeを取ろうと思ったら "Get-Date -UFormat %s" で済みそうだと思うじゃん。

でもこれ現在のローカル時間をそのまま秒に直しただけのものみたい、つまり結果がTimezoneに左右される。ちょっと目的とちがうなあ。

ということで1970年からのDiffを取ることに。

$utime = [int][double]::Parse($(New-TimeSpan $([datetime]'1/1/1970') $([TimeZone]::CurrentTimeZone.ToUniversalTime((get-date)))).TotalSeconds)

Powershell備え付け、てんこ盛りのナイス関数群で何とかなるんだけどさあ、なんだかなあ。