51–60 of 87 posts
Earlier quoted context omitted.
Yes, I don't understand american/English dates and time. I don't know when "04/06/2019 09:00 PM" is. Is it April or June? 0900 or 2100? Let me send an ISO8601 time as all other APIs accept.
AM / PM clears up the 0900 vs 2100 ambiguity, but agreed re; American date formats.
Earlier quoted context omitted.
Americans use DD/MM/YYYY (regardless of delimiter being e.g. / or - or .). We Dutch use MM/DD/YYYY. The latter results in sorting correct on month if its annual data. Over multiple years it breaks. ISO 8601 has my preference, though in MS Office I need to set to Japanese cause my version lacks the setting. 9.00 PM is very clear to mean 21.00 in 24H format. What isn't clear is if 9.00 is 12H or 24H format. 9.00 AM or…
This is incorrect, Americans use MM/DD/YYYY, and from my understanding most of the rest of the world (I think the Netherlands too) use DD/MM/YYYY
I love the idea of a calendar API (another example is Nylas - https://www.nylas.com/products/calendar-api/) b/c it means I could build for EVERYONE and not just a gsuite specific app (which is what I tend to do for simplicity of APIs). The problem I've seen with these is an inability to grow / monetize at the rate startups need to, and, while I love this, things I'm curious about are:
1. How big is this market?
2. Has anyone innovated on pricing here?
3. Are there really well-adopted calendar APIs you need to design for other than Exchange and GSuite?Earlier quoted context omitted.
This is incorrect, Americans use MM/DD/YYYY, and from my understanding most of the rest of the world (I think the Netherlands too) use DD/MM/YYYY
While I believe that most (?) of Europe uses DD/MM/YYYY, I am pretty sure that most of South East Asia (dunno about India and Nepal) use YYYY/MM/DD.
I think you might have meant East Asia. I know Japan primarily uses YYYY/MM/DD.
Singapore, Malaysia, Indonesia, Thailand, Vietnam, Cambodia, Laos, Myanmar, etc (South East Asia) conventionally use DD/MM/YYYY. Interestingly, the Philippines seems to use MM/DD/YYYY.
This looks useful: https://en.wikipedia.org/wiki/Date_format_by_country
Earlier quoted context omitted.
AM / PM clears up the 0900 vs 2100 ambiguity, but agreed re; American date formats.
Yes, I'm not trying to claim that AM/PM is ambiguous, but that me as a person not used to the system (basically everyone except US and a few other countries) have no idea which is which. :)
Earlier quoted context omitted.
Americans use DD/MM/YYYY (regardless of delimiter being e.g. / or - or .). We Dutch use MM/DD/YYYY. The latter results in sorting correct on month if its annual data. Over multiple years it breaks. ISO 8601 has my preference, though in MS Office I need to set to Japanese cause my version lacks the setting. 9.00 PM is very clear to mean 21.00 in 24H format. What isn't clear is if 9.00 is 12H or 24H format. 9.00 AM or…
This is incorrect, Americans use MM/DD/YYYY, and from my understanding most of the rest of the world (I think the Netherlands too) use DD/MM/YYYY
I'll admit I might be annoying to others ... my wife is specifically irritated when I write a time in military format (but my son has no problem reading it from my phone).
Earlier quoted context omitted.
For me it clears it up only 92% of the day. I couldn't tell you when 12:xx AM/PM is right now.
PM means post meridiem. That's Latin, but you don't have to remember it. If you simply remember the P means 'post', and the 'M' means the exact middle of the day (12 noon) then you know 12 PM is 12.00 (after noon hence afternoon) and 12 AM is after midnight or 0.00 (the hour after previous day's 23.00 / 11 PM). Then you just need to remember morning is AM, afternoon is PM, evening is PM, and night is AM. That's it. Y…
Although I am looking for something like this,convier.me's example script didn't work for me: curl https://convier.me/api/event \ -H 'Authorization: Bearer YEAH_SURE...' \ -d 'event[start][date]=05/26/2019 08:00 PM' \ -d 'event[end][date]=05/26/2019 11:00 PM' \ -d 'event[organizer][name]=Tony Stark' \ -d 'event[organizer][email]=ironman@avengers.com' \ -d 'event[summary][text]=Endgame premiere' \ -d 'event[descriptio…
Thank your for your feedback. I fixed that. Sorry about that.