Spyke
infosec.pub

There was a timezone issue with their code. Mastodon, in the mastodon way, found a way to contact the site owner and they got everything fixed. People can be great, when given the chance.

14
Icalasarireply
kbin.social

I am so used to the internet being cynical that I forgot people can be nice

10

Same here. I reread the message chain several times before it sunk in that they were being kind and not dickish haha

1

probably just didn’t take into account time zones so it’s different based on the offset (likely to UTC)

4

can star trek make an episode about squaresoft putting out an hd remake of final fantasy ix in 2025 next then?

12

Something I find funny is that a lot of people who don’t know Star Trek that well and have only seen a couple of episodes assume Star Trek is the super optimistic view of humanity that is unrealistically positive about humanities future when if you actually look at the timeline in the 2000s and 2100s Star Trek is actually seriously apocalyptic. Humanity doesn’t turn to a good future out of some inevitable human kindness, it tries violence over and over again until some crazy guy makes a warp engine out of the rubble of destroyed civilization and the Vulcans show up.

9
lemmy.world

How did you get a screenshot 2 days in the future? When I click on it mine is 249 days, 20hours, 16minutes......

8
aubertlonereply
lemmy.world

I mean wouldn't any sensible developer just use one of the many npm packages that do count down from UTC?

Which would also be using JavaScript?

Sorry I don't mean to quibble it's just that imo JavaScript has nothing to do with this faulty countdown, it has to do with the developer overlooking edge cases.

4

I have seen this episode.

That is EXACTLY why I don't understand why someone wouldn't just use an NPM package that already has all that stuff sorted out. Could you imagine trying to code to deal with different time zones?

Forget about it.

1
el_abueloreply
lemmy.ml

So because they messed up, they're not a sensible developer? Jeez...I sure wouldn't like to work with you.

Mistakes are part of life, especially when your job is solving problems, and thus you can be both a sensible developer and still make mistakes.

If you're not making mistakes, you're not trying hard enough.

2

...

You make it sound like I verbally abuse people for bad code.

It's famously difficult to implement your own time-based systems that also deal with timezones.

Ya know, I'm fairly certain I wouldn't want to work with someone like you either, who seems to jump to conclusions based on an off-hand comment I made that wasn't meant to be particularly cynical.

My main point of the previous comment is that it has nothing to do with JAVASCRIPT, just the developer on the other end. Drawn whatever conclusions you want from that assertion

1
4amreply

Wouldn’t those also reflect an error in the local system clock if it was not set correctly?

1

Can we speed them up? I'm not sure we're going to last that long.

2

I think its silly when star trek tries to predict the upcoming decades. I liked the original series when they went back to the great depression

1

You reached the end