# Tokens de convite aceitos e transformados em ROT13

**URL:** <https://meta.discourse.org/t/invite-tokens-accepted-and-rot13-transformed/90316>\
**Category:** Support\
**Created:** [Junho 20, 2018, 2:40pm UTC](https://meta.discourse.org/t/invite-tokens-accepted-and-rot13-transformed/90316 "2018-06-20T14:40:53Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![alxpck](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/alxpck/32/243713_2.png) [@alxpck](https://meta.discourse.org/u/alxpck)\
**Post date:** [Junho 21, 2018, 10:26am UTC](https://meta.discourse.org/t/invite-tokens-accepted-and-rot13-transformed/90316/8 "2018-06-21T10:26:15Z")

</div>

Two things:

1. a ROT13 email address still has an @ in it, so in our case that wouldn’t be a useful lookup

2. we’re specifically using the invite plugin BECAUSE it doesn’t have an invite page. The ability to take our paid users directly into Discourse with a username of our choosing (their first and last name combined). The benefits we get far outweigh the inconvenience we’re experiencing with this issue. **Please, please don’t add an invite page to the invite token plugin.**

Adding an additional click to the token sounds like an elegant solution to our issue.

---

_[View the full topic](https://meta.discourse.org/t/invite-tokens-accepted-and-rot13-transformed/90316)._
