目前，用户可以直接在邀请框中输入他人的电子邮件来邀请他人。
如果能使用简单的邀请名称（例如被邀请者的用户名）加入论坛，将会更加便捷和简单。这样，人们甚至可以在网络之外（例如在现实活动中）使用邀请额度。
想象一下，我参加了一个研讨会，发现许多人与我们的讨论论坛相关，我想邀请他们加入。我需要收集大量电子邮件，并在研讨会结束后逐一发送邀请。
但如果采用这种方式，我可以轻松地将我的用户名告诉他们，让他们在邀请字段中输入该名称加入论坛，从而从更高的等级开始。
您怎么看？
how will you do that if you don’t have my email?
steps are:
- you ask for my email,
- I pass it to you,
- you start the app,
- invite me using one of the invite buttons,
- I proceed with the sign up process.
while there can be less steps:
- you give me a name (Stephan),
- I start the app,
- I go to the signup panel and add your name there,
of course the second process is what happens most of the time, and only the link between people and the credit is missed.
So what’s the benefit of adding a username at signup? If the user is able to find the community and register, what do they gain by populating that extra field? Are you just looking to collect a list of people you’ve referred in? What’s the benefit to them?
Invites typically serve the following purposes:
- Bring a person to your community and direct them to a specific topic - just entering your username wouldn’t achieve that
- Bring a person to your private community and grant them access - this would defeat the security of private communities
- Bring a person to your public community and automatically add them to a group to see other things - see (2)
In those cases they receive an email that once they click the link gives them a frictionless sign-in, the email address is already verified so they either use the suggested username, or pick their own, then move on.
You significantly oversimplified what will be required of users in your example, they’re going to need to remember lots of additional information and complete several additional steps:
- Where to browse
- What to look for when they get there
- Who referred them
Then they’ll need to manually register and validate their email address. If there are any groups or privacy involved there’s also additional administration steps on top.
They don’t just “start the app” - there is no app which magically routes users to particular discourse instances based on referrer username, usernames aren’t unique between instances. Adding an app at this stage just complicates matters - if it’s a site-specific app they’ll need to also know what it’s called and install it, if it isn’t and you’re just referring to the Discourse Hub they will still need to install that and provide a URL.
That doesn’t sound particularly user-friendly.
With the invite link you avoid a couple of those pain-points, the where, what and who is contained. If you don’t like the length and complexity of that URL and plan to re-use a single invite there are a ton of URL shortening options out there. I’ve done this a number of times myself, putting links in presentation decks, on hand-outs and other materials.
The above suggests you’ve not thought this through at all. Consider the benefits to the other party and how realistic it really is.
3 个赞
the benefit would be for them as well as invitee: some credit which results in their trust level (i.e. gamification).
this can only be meaningful if one can use his trust level somehow (to have extra access in the forum).
this is great, and can happen in the new scenario as well: once you give your invitation-name to me, if I use it in the sign up box, then I can skip the email verification step; because of your credit.
But that’s not verification, forum usernames are public. It will take seconds for spambots to realise that they can bypass the email verification field were that ever implemented.
Do you understand why email addresses need to be verified? If mail carriers such as Mailgun see many email bounces or receive spam reports for messages they will terminate the mail accounts of communities, cutting off email entirely. All because you don’t want to send or share an invite URL.
3 个赞
the invitation-key doesn’t need to be the username, it was just an example!
it can be a simple name which is unique per user.
you may have internet access all the time and you may know the email for all of your real world friends/colleague, not applicable to everywhere in the world.
So now it’s a fourth thing they need to remember?
You’re making remembering invite URLs sound easy in comparison 
you can think of some variation of the invitee email which would be hard for spam-bots to guess. e.g. if your email is stephan.tester@gmail.com, then the invite code can be simply stephan.tester123!
everyone know their own email. don’t they?
Creating unique codes per-invite would require you to have internet access, no? If not then it’s something you can brute force.
It wouldn’t bypass the need to verify email, there is no substitute to sending an email to a mailbox and having the recipient follow a link or enter a received code, that’s why it’s still done everywhere.
a unique code per user name is enough, not per invite.
yes, I can see the problem with the verification email. the main idea was about being able to gamify the invites and use the credit, bypassing the email was just a suggestion coming up from the fruitful discussion, which is really not applicable.
I think what is misleading is the term “invite”.
All accounts need a username and a valid email address. Typically a member supplies these when they register.
It sounds like what you have in mind is more like a “pre-registration” where you supply the username and email address and they follow a link to activate the account.
I guess this could be done but I don’t know how things could be worked out to give you “invite” credit.
Isn’t this possible with bulk invites plugin @techAPJ?
4 个赞
Yes, that is correct.
@Pad_Pors I think this is closest to what you are looking for?
Using the above plugin you can simple hand out invite tokens to the people without needing to invite them manually.
5 个赞
cool thanks , just to understand it clearly: using the plugin:
- admins can create several invitation-keys for users.
- each key works for a particular email.
is it working like that?
though not necessary, I think one can think on a simpler routine where trusted-users can invite others and get the credit.
I agree with @Stephen that the invitation buttons are great, but at least in our community (which is still young) people prefer to use word of mouth rather than a button!
hey! there is a community here you will enjoy being part of!
now imagine this dialogue:
hey! there is a community here you will enjoy being part of. if you come, tell Samuel has introduced me! this way you’ll be trusted simpler from the beginning.
Yes, admin can create (generate) several invitation-keys (invite tokens).
No invite tokens are not linked/restricted to an email. While redeeming/accepting the invitation user has ability to provide email and choose username.
4 个赞
I followed the plugin discussion, and seems to me the plugin is not doing much in the favor of a simpler invitation process to be used in conference cases:
What this particular use case is reusable invites perhaps with a limited time frame. Then you could flash your url on a slide and people could copy it and do what you want.
The other solution is to allow users to request accounts, but that won’t give users credit for the invites.
OMG @codinghorror，我今天真的太需要这个功能了。
我需要邀请 50 人加入论坛，但我没有他们的邮箱地址。我只想在一个 WhatsApp 群组里分享一个代码，让大家都能加入。
目前看来，完全没有干净利落的方法来实现这一点。既然这件事对我而言相当紧急，我今天就会先临时拼凑一个简陋的解决方案。
我的想法是：
requires approval : true
auto approve code : 默认为空。如果在注册时用户输入了任何内容，系统会提示其输入审批代码；如果匹配，用户将自动获得批准。
这样一来，我就可以在 WhatsApp 群组里分享审批代码 12345abc，让群成员在圈子内互相传播。一旦论坛有了足够多的用户，就可以切换到更安全、更受控的模式。
这对我来说无关名誉，关键在于能否从其他渠道快速、半安全地为一个论坛引入大量用户。
10 个赞
所以这是关于仅限邀请/ 所有用户必须由工作人员批准 的网站吗？如果是这样，这个帖子的标题写得非常糟糕，让我现在来修正一下。
就绕过邀请/审批而言，我对此没有任何异议。
5 个赞