jbk

joined 2 years ago
[–] jbk@discuss.tchncs.de 22 points 1 day ago

miku miku beam

blasphemy

[–] jbk@discuss.tchncs.de 1 points 5 days ago

me but reversed

[–] jbk@discuss.tchncs.de 4 points 6 days ago (1 children)

wilsons gonna hate this prank

[–] jbk@discuss.tchncs.de 7 points 1 week ago

ohh my godddd reallllllllll

[–] jbk@discuss.tchncs.de 2 points 1 week ago

i KNEW that what it does seemed a little too fast! idc tho cause it hasn't yet caused any trouble lol

[–] jbk@discuss.tchncs.de 36 points 1 week ago

good for her

[–] jbk@discuss.tchncs.de 7 points 2 weeks ago (1 children)
[–] jbk@discuss.tchncs.de 11 points 2 weeks ago

they taste awesome, right??

[–] jbk@discuss.tchncs.de 1 points 2 weeks ago (1 children)
 
 

While not strictly ISO 8601, it's closely related. RFC 3339 was/is basically a subset of ISO 8601, allowing only what's strictly "needed" or really universal: e.g. 2024-05-27, 2024-03-13 12:34:56Z, etc., nothing like 2018-W06-1 or 2018-036.
Now what's really interesting is how additional data for timestamps was added. For example, specifying the human-readable timezone name, instead of just the UTC offset: 2022-07-08T00:14:07Z[Europe/Paris].

view more: next ›