hailthefish

omni-incompetent computer idiot

  • she/her || they/them

jkap
@jkap

which is a lot more than i would have expected given it only shipped 164 beats ago


zumphry
@zumphry
This page's posts are visible only to users who are logged in.

You must log in to comment.

in reply to @jkap's post:

As a local swatch enthusiast I am excited about this. I think the Date section of the timestamp is incorrect in swatch mode though, as its using the local date rather than the date after conversion to .beats, e.g. the timestamp "2022-12-29T18:32:20.242-06:00" -> Should be "Dec 30, 2022 @063" but is displayed as "Dec 29, 2022 @063". Though I don't think anyone will actually notice or care who isn't an insane person like myself.

i do kinda wish this used utc+ or -12 instead of just going with "where swatch is" for the universal timezone but i suppose implementing that would kinda be making a separate standard from Swatch Internet Time

not that im opposed to cohost internet time ofc but it def complicates it a little

in reply to @jkap's post: