# Using Events for Discourse 3.0 webinar?
**URL:** https://meta.discourse.org/t/using-events-for-discourse-3-0-webinar/252540
**Category:** Site feedback
**Created:** [January 18, 2023, 10:25pm UTC](https://meta.discourse.org/t/using-events-for-discourse-3-0-webinar/252540 "2023-01-18T22:25:21Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@nathank](https://meta.discourse.org/u/nathank)
#### Post date: [January 18, 2023, 10:25pm UTC](https://meta.discourse.org/t/using-events-for-discourse-3-0-webinar/252540/1 "2023-01-18T22:25:21Z")
> [@Discourse: v3.0 is here! Join our live webinar (January 24th @ 10am PST)](https://meta.discourse.org/t/discourse-v3-0-is-here-join-our-live-webinar-january-24th-10am-pst/251997):
>
> Now that [Discourse 3.0 is here](https://meta.discourse.org/t/discourse-3-0-is-here/251372), come to [our webinar](http://bit.ly/3GHe4sM) to see what’s new, including real-time chat and the new sidebar! Join @jonobacon & @codinghorror on 2023-01-24T18:00:00Z (UTC) as we give a live demo and answer any questions about the upgrade. And for the Meta aficionados, there will also be the chance to catch a rare glimpse of some other members of the Discourse Team discourse, with @tobiaseigen, @cocococosti, and @joshua.m also appearing as guest panellists too. partying_face …
We need to register all our details?!? But you already have them.
Might I suggest making use of the #events part of #calendar to manage this instead of offloading it to the unintegrated Zoom? And maybe considering using Jitsi or some other open source solution?
Or at least the Zoom webinars TC?
---
### Author:  [@HAWK](https://meta.discourse.org/u/HAWK)
#### Post date: [January 19, 2023, 1:10am UTC](https://meta.discourse.org/t/using-events-for-discourse-3-0-webinar/252540/2 "2023-01-19T01:10:57Z")
> [@nathankershaw](#):
>
> We need to register all our details?!? But you already have them.
We haven’t ever sought permission to use details from Meta accounts for other things so they are separate/protected.
---
### Author:  [@nathank](https://meta.discourse.org/u/nathank)
#### Post date: [January 19, 2023, 11:09pm UTC](https://meta.discourse.org/t/using-events-for-discourse-3-0-webinar/252540/3 "2023-01-19T23:09:39Z")
> [@HAWK](#):
>
> We haven’t ever sought permission to use details from Meta accounts for other things
I guess the key is whether this event is arranged by [meta.discourse.org](http://meta.discourse.org) or by CDCK itself (if those entities are truly separate).
Personally, if I RSVP’d within [meta.discourse.org](http://meta.discourse.org) I’d expect my data to be utilised for something like this. Ditto for a [zoom.org](http://zoom.org) webinar ‘owned’ by CDCK.
In my domain (health) ‘privacy’ is often used as an inappropriate excuse by those who don’t want to go to the trouble to safely share data in ways that benefit the user (in our case the patient). And patients generally suffer as a result while the corporate butt is covered. Not cool.
---
### Author:  [@HAWK](https://meta.discourse.org/u/HAWK)
#### Post date: [January 19, 2023, 11:37pm UTC](https://meta.discourse.org/t/using-events-for-discourse-3-0-webinar/252540/4 "2023-01-19T23:37:35Z")
> [@nathankershaw](#):
>
> I guess the key is whether this event is arranged by [meta.discourse.org](http://meta.discourse.org) or by CDCK itself (if those entities are truly separate).
They’re the same and it’s organised by CDCK.
I hear you, but this is a long standing puzzle that we’re working through with privacy lawyers across a lot of planes. It stems from being a product-led company for so long. Now we have marketing there is lots to untangle.
It’s a work in progress.