Actually, here we don't want to use `short_desc`. Or else the `event.description` doesn't get displayed if an event as a `short_description`.

And this presents a problem. Kinda a big one. 
First of all, there are events that have complex pieces of HTML in the description. E.g [this one](https://air.mozilla.org/fireside-chat-2/)
There are a couple of those. Like 3-5. 

So, going back to ` <p>{{ event.description|carefulnl2br|safe }}</p>` is a good start. 
However, in the future we're going to want to open up the editing of event metadata to signed in contributors and staff. Maybe even one day to anybody with a Mozillians account. Not sure yet. 
When we do that we need to start being more vigilant. Not that we necessarily think people are malicious but they could accidentally make mistakes and paste something really bad in that causes a security problem or just outright breaks the page. 

I think that we'll simply deal with that that day and focus on the short description for now. 
I envision we might need some sort of rule if the event is a certain shortlist of hardcoded titles, then we allow tags like `<iframe>` or `<script>`. Just to tie us over from our troubled past.