# Outgoing invites give overdramatic "not secure connection, could be compromised" warning

**URL:** <https://meta.discourse.org/t/outgoing-invites-give-overdramatic-not-secure-connection-could-be-compromised-warning/60355>\
**Category:** Feature\
**Created:** [April 3, 2017, 7:56am UTC](https://meta.discourse.org/t/outgoing-invites-give-overdramatic-not-secure-connection-could-be-compromised-warning/60355 "2017-04-03T07:56:16Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![dylanh724](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dylanh724/32/119642_2.png) [@dylanh724](https://meta.discourse.org/u/dylanh724)\
**Post date:** [April 3, 2017, 8:19am UTC](https://meta.discourse.org/t/outgoing-invites-give-overdramatic-not-secure-connection-could-be-compromised-warning/60355/3 "2017-04-03T08:19:07Z")

</div>

> [@codinghorror](#):
>
> That is from the browser, and has nothing to do with us specifically.

Yea I had a feeling – however, because browsers do this, I still encourage adding a warning if !SSL. It’s quite embarrassing 😕 who would’ve known. I know it’s not a Discourse thing, but it may help future people.

---

_[View the full topic](https://meta.discourse.org/t/outgoing-invites-give-overdramatic-not-secure-connection-could-be-compromised-warning/60355)._