#UNIXtime

2025-06-15

Unix Time 1760000000 will be on:

Thu Oct 09 2025 09:53:20 UTC+0100 (British Summer Time) or 08:53.20 UTC

#UnixTime #UnixTime1760000000

vlakicasvlakicas
2025-06-15

It's counting and going... with light effects
( / / )

2025-06-15

So that's Sun Jun 15 2025 16:06:40 UTC+0100 (British Summer Time) for those in the #UK and are playing along 馃檪

#UnixTime # 1750000000 #UnixTime1750000000

Michael :donor:hertg@infosec.exchange
2025-04-17

Kinda annoyed that there wasn't even a spike in traffic on my website yesterday at 2025-04-16T19:07:44+00:00

epochalypse.today/

Was no one watching the bit flip to 01101000 00000000 00000000 00000000?

Anyway, see you guys at 2029-07-18T05:49:52+00:00 when it flips to 01110000 00000000 00000000 00000000, which is when we'll lose the next bit to the epochalypse.

#epochalypse #unix #unixtime #year2038 #year2038problem #y2k38 #software

iokevinsiokevins
2025-04-16
2025-04-13

Unix TIme 1745678910 will occur on Saturday April 26th at 14:48:30 UTC

馃槉

#UnixTime #1745678910

out of bounds, anywhere outsyll@pouet.chapril.org
2025-04-03
Kevin Karhan :verified:kkarhan@infosec.space
2025-03-31

@AaronDavid #DST should be outlawed and #Unixtime mandated globally.

#SaylightSavingsTime

2025-03-21

Unix time of 1750000000 will be on Sunday 15th June at 15:06:40 UTC

#UnixTime

2025-02-25

馃し "Hey, what have you been doing recently? "
馃 "Ehhhhhhm, I created this countdown notification script?!"
馃し "You're weird!"

馃槄

(disclaimer: I'm aware the timer isn't accurate. Just haven't figured out yet exactly why. I think it's because of leap days or something....I'm tired, to be continued 馃榿)

2025-01-27

Unix Time 1740000000 will be coming up on
Wed Feb 19 2025 21:20:00 UTC 馃槉

time.is/Unix_time

#UnixTime

DO8PGG 鈽戯笍do8pgg@ruhr.social
2024-12-31

Ahhh, stimmt. Gleich kommenden wieder dutzende Mails. "Alles gute zum 55 Geburtstag!"

Jau. Der 1.1.1970 ist halt ein sch枚nes Datum f眉r "DU MUSS DEIN GEBURTSTAG ANGEBEN!"-Seiten :-D

#Unixtime

Multi Purr Puss :verified:platymew@layer8.space
2024-12-16

馃У 2/2

Oof, the previous toot might be ambiguous:

1st of all, i'm fine & happy! 馃槂

Because i've DECIDED to be a #hedonist / #atheist! I'm also a #furry-ish kinda "weirdo" (unusual person[-ality]), now. (see also, the "mostly harmless" bit in my bio/profile)

I prefer enjoying my life, while it lasts! 馃嵒

One of my #BucketList items is: surviving the #Y2k38 bug. I really wanna see what happens, when the #UnixTime #Integer rolls over! 馃ぃ (i'm aware of BIGINTDATETIME)

#ThisIsFine 馃惗 馃敟

"Last clustering run: 1/1/1970"
I didn't even know tensorflow existed back then
#unixtime

2024-10-27

For those in the #UK who are confused as to the correct time followng the end of Brisish Summer TIme to #GMT then this might help 馃槈

time.is/Unix_time

#UnixTime #BST #ClocksGoBack

2024-10-26

Apart from the end of British Summer Time tomorrow morning (Sunday) at 02:00 we also have a Unix Time milestone at 03:33:20 UTC when we reach 1730000000 馃檪

#UnixTime #BST #GMT #Y2K38

vlakicasvlakicas
2024-10-25

Unix Epoch in
1730000000 seconds

on date and time:
Sunday October 27th 2024
GMT 03:33:20


Juande Santander-Velajuandesant@santander-vela.net
2024-10-04

Para muchos de vosotros es bien conocido que el momento que los sistemas operativos UNIX utilizan como momento cero desde el que cuentan el tiempo en segundos (la 茅poca UNIX, mala traducci贸n de the UNIX epoch) es el 1 de enero de 1970. Pues bien, hoy se cumplen exactamente 20000 d铆as exactos desde ese momento.

Ese momento me lo record贸 @drang@fosstodon.org con una entrada en el que enlaza a otra entrada de @eddelbuettel@mastodon.social, que demostraba en R c贸mo calcular el n煤mero entero de d铆as transcurridos desde el 1 de enero de 1970 a partir del n煤mero de segundos reportado por el reloj del sistema:

> Sys.setenv(TZ="UTC")> difftime(Sys.Date(), as.Date("1970-01-01"))Time difference of 20000 days

Drang proporcionaba el siguiente c贸digo en Bash (tambi茅n v谩lido en ZSH, o incluso sh; no v谩lido en csh o tcsh):

$ echo $(( $(date +"%s")/86400 ))20000

Yo prefiero hacerlo en Python, donde hay varias maneras de hacerlo:

> # Utilizando divisi贸n entera sobre la 茅poca UNIX> import datetime as dt> dt.datetime.today().timestamp()//8640020000.0

Pero tambi茅n se puede hacer usando los c贸digos de formateo de fechas de la funci贸n date de UNIX (los mismos que utiliza el comando date):

> # Utilizando divisi贸n entera sobre la 茅poca UNIX> import datetime as dt> int(dt.datetime.strftime(dt.datetime.today(), format="%s"))//8640020000

Y una forma m谩s de demostrar que hoy, 4 de octubre de 2024, es el d铆a 20000 de la 茅poca UNIX:

> import datetime as dt> dt.datetime(1970,1,1)+dt.timedelta(days=20000)datetime.datetime(2024, 10, 4, 0, 0)

隆Feliz vig茅simo mil茅simo d铆a!

https://santander-vela.net/2024/10/04/feliz-20000-dias-de-viaje-unixino/

#20000 #bash #Python #R #shell #Unix #UNIXEpoch #UNIXTime

Kevin Karhan :verified:kkarhan@infosec.space
2024-09-09

@echedellelr how about date %s aka. #Unixtime or YYYYMMDD,hhmmssTZ ?

Almost as close as yours...

2024-08-07

Upcoming Unix Time milestone on

Sun Aug 18 2024 16:53:20

when the Unix Time will be 1724000000

馃檪

#UnixTime #1724000000

Client Info

Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst