Show HN: Natural Language Time Zone Converter

#1

Post by hpoydar » Tue, Oct 27, 2015, 10:08 PM UTC

Show HN: Natural Language Time Zone Converter
slashtz.com

Re: Show HN: Natural Language Time Zone Converter

#2

Post by digital_ins » Wed, Oct 28, 2015, 3:42 AM UTC

This is the best thing I've seen in a long long time. I spend most of my days co-ordinating between timezones for my phone calls and this would really make my life much easier. Coming from an NLP background, I can say that the front-end simplicity does mask a whole lot of back-end complexity.

Quick question, how're you handling daylight savings? Do you rely on the in-browser JS to figure it out? Or are you using something like moment.JS to handle this for you?

Re: Show HN: Natural Language Time Zone Converter

#3

Post by tech_crawl_ » Wed, Oct 28, 2015, 4:59 AM UTC

Nice work man. This is a great project.

Re: Show HN: Natural Language Time Zone Converter

#4

Post by hpoydar » Thu, Oct 29, 2015, 4:23 PM UTC

digital_ins wrote: post #2

This is the best thing I've seen in a long long time. I spend most of my days co-ordinating between timezones for my phone calls and this would really make my life much easier. Coming from an NLP background, I can say that the front-end simplicity does mask a whole lot of back-end complexity. Quick question, how're you handling daylight savings? Do you rely on the in-browser JS to figure it out? Or are you using some…

Thanks! We actually started with NLP libraries, but fell back on plain old regex, which in the end was the right tool for the job, though it got a bit hairy. (Nice to hear from someone who can appreciate it.) As for daylight savings, we use the browser to get a current GMT offset on your first request and determine an Olson TZ, which we cookie. Subsequent requests are passed off to a Node instance for processing along with the time zone, which also processes posts from Slack and HipChat. And yes, MomentJS and Moment Timezone are the workhorses here.

Re: Show HN: Natural Language Time Zone Converter

#5

Post by digital_ins » Fri, Oct 30, 2015, 1:35 PM UTC

hpoydar wrote: post #4

digital_ins wrote: post #2

This is the best thing I've seen in a long long time. I spend most of my days co-ordinating between timezones for my phone calls and this would really make my life much easier. Coming from an NLP background, I can say that the front-end simplicity does mask a whole lot of back-end complexity. Quick question, how're you handling daylight savings? Do you rely on the in-browser JS to figure it out? Or are you using some…

Thanks! We actually started with NLP libraries, but fell back on plain old regex, which in the end was the right tool for the job, though it got a bit hairy. (Nice to hear from someone who can appreciate it.) As for daylight savings, we use the browser to get a current GMT offset on your first request and determine an Olson TZ, which we cookie. Subsequent requests are passed off to a Node instance for processing alon…

hahaha, yeah, good ol' getTimeZoneOffset() being put to work. It's shocking how crappy JS' date object is, it's near impossible to do anything powerful with it without resorting to obnoxiously-structured regex.

Once again - great job! I'm building complex conversational interfaces and even I think that this really is something.