Skip to content
This repository has been archived by the owner on Aug 22, 2022. It is now read-only.

OrbitDB Community Call: Tuesday December 11, 1400UTC #38

Closed
RichardLitt opened this issue Nov 27, 2018 · 14 comments
Closed

OrbitDB Community Call: Tuesday December 11, 1400UTC #38

RichardLitt opened this issue Nov 27, 2018 · 14 comments

Comments

@RichardLitt
Copy link
Contributor

Click here for the agenda and notes.

This will be the next Orbit community call, on December 11 at 1400UTC! Drop your agenda items here or in the notes. Note that this is an hour later than the last call.

Add this event to your calendar using this link.

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/784309963

Or iPhone one-tap :
US: +19294362866,,784309963# or +16699006833,,784309963#
Or Telephone:
Dial(for higher quality, dial a number based on your current location):
US: +1 929 436 2866 or +1 669 900 6833
Meeting ID: 784 309 963
International numbers available: https://zoom.us/u/evzwWgnAi

@RichardLitt RichardLitt added the event A call, meetup, or otherwise time-bound event label Nov 27, 2018
@RichardLitt RichardLitt changed the title OrbitDB Community Call: Tuesday December 11 OrbitDB Community Call: Tuesday December 11, 1400UTC Nov 27, 2018
@tyleryasaka
Copy link

The calendar link doesn't match the date/time listed here.

@RichardLitt
Copy link
Contributor Author

RichardLitt commented Nov 30, 2018 via email

@RichardLitt
Copy link
Contributor Author

It should be the same time? I just checked again, and I see it as 9am EST, which is 2pm UTC.

@tyleryasaka
Copy link

tyleryasaka commented Dec 1, 2018

Sorry, not sure why I thought the time was wrong. Just the date:

screen shot 2018-12-01 at 2 00 14 pm

On second glance, the problem is that the event stops repeating December 10, even though the call is on December 11. (Should be December 11 in both UTC and pacific time).

@RichardLitt
Copy link
Contributor Author

Where are you seeing that? I see it continuing indefinitely. This is odd.

@tyleryasaka
Copy link

Hmm weird. That's how it shows on my my google calendar. 🤷‍♂️

@RichardLitt
Copy link
Contributor Author

That is truly bizarre. Can you try resubscribing to the OrbitDB calendar?

@tyleryasaka
Copy link

I deleted the event and re-added. Same result. idk what's going on - maybe it's just my machine 🤷‍♂️ . Regardless, easy fix and I'm planning to join. 😄

@RichardLitt
Copy link
Contributor Author

I'll flag it as something to keep an eye on in the future. If this happens with anyone else, we'll move to another service.

@haadcode
Copy link
Member

haadcode commented Dec 11, 2018

There's a mismatch for me too: the issues here says 1400 UTC whereas the calendar shows 1500 UTC. Did we get bitten by daylight savings again at some point?

@haadcode
Copy link
Member

Ignore my previous comment, my calendar was in the wrong timezone! :)

@zachferland
Copy link

Going to join, mostly want to ask about payload encryption support in ipfs-log - orbitdb-archive/ipfs-log#191

@haadcode
Copy link
Member

Notes here https://github.com/orbitdb/welcome/blob/master/meeting-notes/2018/2018.12.11.md.

Thanks everyone for joining!

@RichardLitt
Copy link
Contributor Author

Thanks @haadcode.

I opened an issue about scheduling the next call, as the next Tuesday is Christmas. Join in here: #42.

@RichardLitt RichardLitt added Community Call and removed event A call, meetup, or otherwise time-bound event labels Apr 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants