djc / awmy Goto Github PK

Hi there! This is a really awesome little tool!

I've build a small landing page for entry into our own meetings, to help make ensure folks in our community know what they are consenting to on arrival at a video meeting:
https://edgi-video-call-landing-page.herokuapp.com (click the sample link to see the page itself)

It's nothing fancy (which is good). But it's unfortunately very single-purpose. I was wondering whether you might be open to discussion on add two features to yours that would allow us to start using the same codebase :)

As I see it, two thing would works:

1. a linked button to enter the meeting
2. a place for description, accepting markdown

Curious your thoughts. Thanks again for the awesome tool!

...probably due to taking the wrong time into account when calculating, when the next even is going to be.

Example:
http://arewemeetingyet.com/Los%20Angeles/2015-03-10/12:00/b/Tb

So, for me being in Europe the next event should be today, however the page says:

Next occurrence, your time (UTC + 01:00):
Tue, 24th Mar, 20:00
(2 weeks from now)

Example: A fictitious meeting titled 'foo/bar'
http://arewemeetingyet.com/Brisbane/2014-03-16/22:00/foo/bar

The meeting title displayed is 'foo'
The template is pre-populated with 'bar'

Both should use 'foo/bar'

For the foo/bar thing, maybe we can pick up "foo/bar" as the title?
E.g. take all elements after the time or repeat mode and concatenate
them back together with slashes? I think that might be the least
surprising behavior.

(Originally reported on Bitbucket as #3.)

Just used the TB meeting ICS link
http://arewemeetingyet.com/Los%20Angeles/2015-04-07/12:00/b/Thunderbird%20Meeting

Afais the ICS data is incomplete to resolve it for other timezones (like mine living in Germany).
You have

    DTSTART;TZID=America/Los_Angeles:20150421T120000

But there is no VTIMEZONE block like this:

    BEGIN:VTIMEZONE
    TZID:Europe/Berlin
    X-LIC-LOCATION:Europe/Berlin
    BEGIN:DAYLIGHT
    TZOFFSETFROM:+0100
    TZOFFSETTO:+0200
    TZNAME:CEST
    DTSTART:19700329T020000
    RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
    END:DAYLIGHT
    BEGIN:STANDARD
    TZOFFSETFROM:+0200
    TZOFFSETTO:+0100
    TZNAME:CET
    DTSTART:19701025T030000
    RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
    END:STANDARD
    END:VTIMEZONE

For an international meeting it makes sense to have it complete?

http://arewemeetingyet.com/London/2010-05-01/13:00/b/Test

and

http://arewemeetingyet.com/London/2010-12-25/13:00/b/Test

Should yield the same times, but don't. This is likely because the offset at the reference date is different, and AWMY somehow fails to account for that difference.

(Originally reported by me as #2 on Bitbucket.)

Using innerHTML is generally a bad idea unless you escape the data. Please check this URL:

http://arewemeetingyet.com/Berlin/2018-01-01/13:01/%3Cimg%20onerror%3D%22alert%28%27xss%27%29%22%20src%3D%22asdadsasdads%22%3E%3C%2Fimg%3E

Suggest to change everything to .textContent unless necessary and escape url content everywhere else.

Steps to reproduce:

1. Create a meeting URL with %26 in the title. Example: http://arewemeetingyet.com/Brisbane/2014-03-15/22:00/Q%26A
2. Click 'Use as template'
3. The title field should contain & and not %26

The day number has the wrong ending for twelve. It should be twelfth instead of twelfnd.

Example: http://arewemeetingyet.com/Berlin/2015-03-12/21:00/b/Zweiw%C3%B6chentliches%20Meeting%20der%20deutschsprachigen%20Mozilla-Community

Steps to reproduce:

1. Visit any meeting. Example: http://arewemeetingyet.com/Brisbane/2014-03-15/22:00/Meeting
2. Click 'Use as template'
3. Select 'Weekly'
4. Press 'Go to URL for meeting'

The URL should contain /w/ once to denote a weekly-repeat.
Bug: the URL contains /w/w/

Same issue for bi-weekly (but /b/b/ rather than /w/w/)

The US and Canada changed to DST on March 8. This is not reflected in arewemeetingyet.com. For example, this meeting link should show Pacific Time as UTC-7, but shows it as UTC-8.

From Gerv:

Do you think perhaps the AWMY link creation form could pop up an "are you sure?" warning if the meeting is arranged for between 8pm and 6am in the timezone where the meeting is being held? That might prevent errors like the below, where a meeting was arranged for 1am when they wanted 1pm...

(Originally reported on Bitbucket as #4.)

http://arewemeetingyet.com/ is currently down:

This site can’t be reached

arewemeetingyet.com refused to connect.
Try:

Checking the connection
ERR_CONNECTION_REFUSED

According to awmy the 11th is a Monday.
But it's a Tuesday :)

Example: http://arewemeetingyet.com/Los%20Angeles/2013-03-11/08:00/example
(My timezone is UTC+1, if that's required for reproducing.)

Entering a slash in the template form encodes the slash as %2F
This causes a file not found error on arewemeetingyet.com

Example: http://arewemeetingyet.com/Brisbane/2014-03-16/22:00/foo%2Fbar

I noticed something (and hopefully a pattern) to help identify it:
ex: http://arewemeetingyet.com/New%20York/2014-08-27/15:00/w/Test

As I'm living in UTC + 2H and New York is UTC-4H, the next meeting should be today : 3rd of Sept 2014, 21:00 (PM) (UTC+2H)
But it displays 10th Sept 21:00.

It seems that this happens when the time of the meeting is past in my zone (20:37 > 15:00) but not past in the meeting zone (14:37 < 15:00).

I hope this is clear :s

Would be nice of awmy could keep meetings stored and tell people if their proposed meeting time conflicts with other standing meetings. This would be very useful since we are a global org with so many teams.

Dear Dirkjan, thanks for creating the code that's used on http://arewemeetingyet.com

There seems to be a bug with the following configuration:
Timezone: LosAngeles
Date: today (for example 03/07/2019)
Time: the following hour
(look at https://www.timeanddate.com/worldclock/usa/los-angeles for the current time, change the form to use the following full hour. For example, it it's 02:01 a.m., enter 03:00 a.m. in the form.)
Repeat: bi-weekly
http://arewemeetingyet.com/Los%20Angeles/2019-03-07/03:00/b

Expected:
Form should show Next Occurrence is today (March 7), in less than 59 minutes.

Actual behavior:
Form shows next is on March 21.

This would be handy!

...but it is not.

Trying to submit without a page title shows a tooltip:
"Please fill out this field".

Hi, first of all thanks for this useful tool.

I'm trying to setup a date but it seems to be impossible to set it in June, exactly 2016-06-03 in Europe/Rome date zone.

I've entered 15 for time not 15:00 and that brought me to a nan error..
As I knew what was wrong - I went back and correct it but maybe some people will be stuck there as they will not get it from first step what's the error

PS: Awesome work btw!

a testerror:
testerror
Your time (UTC ): undefined, NaNth undefined, -0NaN:-0NaN (NaN second from now)
For your calendar: undefined, NaNth undefined, -0NaN:-0NaN (in timezone Europe/Bucharest, UTC + 02:00)