Onboarding process for new member

I’m considering migrating from Facebook Groups to a semi-private Discourse instance for an event series I help run. I have read the previous blog posts and Discourse posts about migrating from Facebook groups. However, I have some questions about the on-boarding process of new users, which might be mostly due to my unfamiliarity with the API.

Filtering incoming users

Probably the biggest advantage to Facebook is it’s ability to use a Facebook profile as a proxy of trust. Basically, you can gague how likely a person is to be a spammy jerk by:

  • How many friends they have
  • The other groups they’re a part of
  • Their geographical location
  • (hardcore mode) Getting them to fill out a form with basic questions

Is filling out a form as part of new user joining possible to implement in Discourse to accomplish the same thing? I think this might be possible by customizing the profile creation form?

Making users set up their email settings once accepted

Given I want people to get email notifications based off their geographical location, is it possible to make this part of their account creation process? For example, so that a person who lives in Waterloo isn’t subscribed to the event notifications from Tokyo and Taipei. I’m afraid of users being unable to figure out the category-specific email settings on their own. Also, I’d rather not have to make a how-to and make them read it.

1 个赞

This does not really address all of your issues, but if you are concerned about filtering incoming users, then one of the many options is to disable local registration and only use Facebook / Twitter login.

This way you can still use Facebook as a proxy of trust.

Extreme? yes, but still possible, so I wanted to point it out.

With that being said, Discourse has some awesome anti-spam features built in, so you might end up being pleasantly surprised.

5 个赞

All valid points.

I guess I also want to filter for people who I don’t want at the events, but that hasn’t been a problem before, so maybe it’s an unfounded concern.

2 个赞

One thing you could do is make the candidate write a little bit about themselves and what they hope to get out of your community.

5 个赞

Discourse does a bunch of stuff to keep you from having to worry about spammy jerks. It does this by giving them limited access to start and requiring them to do stuff like read and interact with the site before gaining more privileges. Rather than guessing whether someone is a jerk based on some incomplete information, it bases the decision on their actual behavior.

You can manage people’s access to particular categories by having them join groups (which control access to categories). You can manage groups manually or by allowing people to request membership. You can assign anyone (not just admins and moderators) as a group owner to distribute the work of vetting people’s right to join a group.

There are some example plugins that will assign people to watch certain categories (and get event notifications) depending on their group, though these require modifying the plugin.

2 个赞

It looks like it hasn’t been mentioned yet: Discourse supports custom user fields, and they can be added to the registration page and required if wanted. Users can also require admin approval after registering before being given access, so that admins can review the form responses.

That said, I know very few sites that add mandatory fields to the registration page, and even fewer that use them to approve users joining. As Jay said Discourse does lots of stuff to protect you from spam. Registration flow changes should not be required.

5 个赞

Probably the easiest way to do this is to require a user field that has users select their geographic region. Then you can sort them into groups based on this response.

我们已经在自己的实例中这样做了,但留下了一个令人烦恼(尽管相对较小)的问题:/review 页面中的用户字段没有像 @eviltroutCustom User Field Enhancements 中所做的那样进行良好的排序。这意味着我们的版主/管理员需要的相关决策信息(用于决定 :+1::-1:)被埋没了。

也许我们可以为自己的实例直接进行一些修改(主要管理员是 @pacharanero),但我怀疑这实际上是任何要求在加入时填写数据以决定或控制谁可以加入的 Discourse 实例所面临的问题。

2 个赞

为明确起见——这里的问题是字段显示了,但在审查时顺序不正确,对吗?

4 个赞

是的——顺序有些随机,取决于字段标题上次编辑的时间。

2 个赞

@markvanlan,这可能是个小任务,能帮你熟悉一下审核队列的前端。你能把它加入你的任务列表吗?谢谢。

7 个赞

@nathank 我们已修复此问题,当您更新到最新版本时,用户字段将正确排序。

9 个赞

看起来很棒!这是对一个小但重要的功能的巨大改进。

@eviltrout - 您团队的响应速度令人惊叹。有人愿意倾听像我这样的人的意见,这真是无比强大的力量;这传达出您对我们这些普通用户的高度重视!!!

10 个赞