从 Facebook 迁移:具体挑战和一些想法

Why I’m writing about this (introduction)

This was a few weeks back, and life happened in the meantime. To my surprise back then, it indeed seems that “migrating from a successful facebook group to Discourse” doesn’t actually seem to be a common situation here:

Migrating a successful community from Facebook is, however, the situation I’m in, and I think it can explain some of the frustrations I’m encountering getting started with Discourse. Moving a thriving community from a sticky, integrated, established platform like facebook presents different challenges than starting a community from scratch, or moving a struggling/non-thriving community over from some other platform, where things are not working great. As @chapoi says (emphasis mine), it has to do with:

Background about my situation these two topics, if needed:

I’ve just spent some time now going through all the facebook-migration topics I could find to take a shot at synthesising where we’re at regarding this issue, quotes at hand. Some are ancient, but I’ve tried to pick out those that are still relevant for today’s discussion. Forgive the long post (again, I know) but I think there is value in bringing things together.

Why Facebook group migration matters

I’m wondering if the sentiment expressed in this post from 2018 might not explain somewhat why “migrating facebook groups to discourse” isn’t a bigger or more visible preoccupation so far here on meta:

Happy that this seems to be changing:

Beyond my personal issues, why should Discourse/Meta care about facebook group migration? Because Facebook groups are huge. For many people (me included), they are the highest value the platform offers and what keeps people there.

“Competition”

Facebook groups work. I have personally been looking for an alternative for years, and there aren’t many, aside from Discourse. I have known forums which have “bled out” to facebook groups, and this also seems to be an ongoing preoccupation for Discourse communities – the fact that facebook groups represent some kind of competition for the communities we are trying to build on Discourse.

The open web

In addition to that, I believe that for the good of the web (and the world), we need to work on freeing ourselves (collectively) from the tyranny of “Big Platform” (right). I’m not alone. For example:

Building platforms like Discourse or Mastodon is part of that. But we all know that having the tools is not enough. Quoting freely Doctorow’s Law of Enshittification: people won’t leave crap platforms they’re locked into unless there is an extremely strong pull to do so, and a sufficiently frictionless alternative.

Like others, I am doing what I can to pull us in what I feel is the right direction (including contributing to rebooting the blogosphere). Finding a realistic alternative to Facebook groups for community builders like myself is part of that plan. That is why I care.

There are many good people doing valuable things who are trapped on Facebook, and I would very much like to be able to give them a way out.

I want to write another topic on how I see the integration of Discourse with other open source tools can create an ecosystem comparable to what we use Facebook for now.

Switching costs

In the various discussions I surveyed here on Meta, the question of switching costs comes up again and again, in different ways, over the years.

Starting in 2014… to this day:

This is not a detail, or something that can be solved just by telling people to get over it and move. Let’s look at what these switching costs are made of a bit more closely, and what could be done to offset them.

Most “normal people” do not “live online” anywhere else than on Facebook (and maybe Instagram, and WhatsApp group chats). They barely know how to properly search for something with Google, let alone type/copy a URL in their browser address bar. Online is Facebook.

People who are already using Reddit, or Mastodon, or even Bluesky: they are not the problem. But they are a minority.

Platform integration

I think that one thing we all recognise as Facebook’s strength is that it brings everything together in one place.

Here are some advantages of facebook “integration” for a community on that platform (facebook group):

  • integration of community notifications with all the other notifications in Facebook, that the person is already monitoring day in and day out, which creates an easy pull back into the community at no extra cost
  • content from the community just “shows up” in the person’s usual online activities (via the Facebook news feed), also bringing them back to the community without any extra effort on their part
  • members can easily connect outside the community through their facebook accounts (friending, following, Messenger conversations), allowing friendships to grow through the “life already shared on Facebook”, which then in turn benefits the community (stronger relationships between members)
  • the community is very easily found by people who need it, either through search inside Facebook or by leveraging the various networks inside Facebook (other groups, pages, asking on one’s wall, “suggested groups”, etc)

Platform familiarity

For people whose whole online world is pretty much Facebook, offering anything outside of Facebook in itself is already a huge barrier. The simple action of going to a website or installing/using a different app on their phone, which may be trivial to us, is not so for them.

Even if that in itself is not a roadblock, changing tools (for anybody!) is going have a cost. There are differences in how one posts, comments/replies, how notifications are managed, extra features (badges? tags? trust levels? quoting?), how one accesses another person’s “profile”, the design is different…

Offset switching costs by providing more value

We all agree that the key to this kind of migration is to be able to offer more value to community members on Discourse than in the Facebook Group that they know and love, and is seamlessly integrated with the rest of their online life (aka Facebook).

Being in control of the Facebook group you are migrating from gives you some control to limit the experience on the Facebook side as you build up the Discourse side:

There is no shortage of ideas on this matter – the flexibility of Discourse makes a lot of things possible, too.

However, the more established the community on Facebook, the more difficult it will be to attract enough initial members to get some momentum going for that value to be made visible.

Let’s not forget user experience

A lot of the discussion regarding how the community on Discourse needs to provide value that members will not find on Facebook focuses on features and discussion. This is perfectly valid. Discourse has many features that can be used to provide a richer “community experience” than facebook groups. But that is not enough.

I think this is missing the point that unless the access to said great content functions “well enough” for people, it means nothing:

Facebook has invested huge sums of money in making its platform as frictionless and sticky as possible, to keep people there. That is the benchmark (of frictionlessness) that Discourse is up against, when it comes to migrating communities from Facebook.

I think this is an important point. The interface you are used to will always feel “easier” to use, because you’ve been doing the same thing with it for years. The interface of the new platform will not only have to be as good, but better, because you are not committed to it yet – if you hit any snag, you are likely to turn away, particularly if there is a nice cushy comfortable familiar alternative waiting for you there.

UX/design/interface are paramount – especially in a context where your users are people who have been conditioned to one way of doing things for many years, and where getting an initial critical mass of members to the new platform to jumpstart the migration is necessary to create the added value which will convince the bulk of the community to take the plunge.

The best features in the world for community-building have no value in of themselves – only through enough people using them. And what will “make or break” having people staying around to use them is their first contacts with the interface.

There are also features, which we may consider as “added value”, like titles for topics, which can actually generate a lot of friction (and therefore decreased user experience for the new member trying to contribute). See conversation following here:

And what about admins and community builders?

The first-line “users” of Discourse are the community admins and builders. Without them, no community member will even set foot on the platform. Here, too, the bar facebook sets is very high:

Discourse is far superior in terms of capacity, features, independence, moderation tools, etc. It’s a no-brainer. But the experience of setting things up (I’m not talking about installation, because that is a one-time overhead that can be dealt with) is infinitely more complex than for a facebook group.

Of course, the tool is more powerful, has more functionality, so some of that is normal. And if you’re starting from scratch with your community, it’s probably manageable. But if your competition for your future Discourse community is your own thriving Facebook group, you are going to have to do a lot of tweaking and fiddling and preparing and organising and adjusting and customising and setting-fixing upfront, to make sure that the precious and valued community members you have managed to talk into going along for the ride to your “new digital home” don’t have a disappointing first contact with the platform. And as I’ve tried to demonstrate in this topic, the bar for that is going to be higher than “out of the box” Discourse.

When we talk of user experience (I know the Discourse Team is aware of this, of course) we are also talking about the admin’s user experience. So how does that experience of trying to set up Discourse to migrate a facebook group to go for the Facebook-wannabe-Discourse community builder? This is what I’ve been trying to give feedback on and share in some of my previous topics and posts, and I sometimes got the impression I was misunderstood.

Wrap-up

First, sorry for writing so much, and for all the quotes. But I wanted to show that this is not a fringe, isolated issue that I’m dealing with. I certainly have my shortcomings, but there is a wider “facebook migration” issue at stake here. I also don’t want anybody to think I’m ungrateful or overly critical of Discourse and all the wonderful people contributing to it. I think it’s a great platform and I’m going to make it work for my community, but I think it has even more potential, which I’d love to see it reach!

The key points I’d like to make:

  • facebook group migration is a “use case” that might be worthy of more attention than it has had over the last years (at least, as is reflected on Meta)
  • both admins and members “coming from Facebook” arrive with high expectations in terms of frictionlessness (and integration)
  • setting up a Discourse instance for a facebook group migration has different “requirements” in terms of community builder work than creating a new community from scratch or setting up a good home on Discourse for one that is struggling elsewhere
  • the migration strategy, in terms of added value to be provided on the Discourse side to draw users in, cannot limit itself to content and interaction quality, but must also include interface/UX for naive/facebook-formatted users
  • the main obstacles I see so far to Discourse being a “competitive” alternative to Facebook groups are the complexity of initial configuration for a community builder who is discovering the tool, and the “functionality overwhelm” of the interface for new community members who might not have very high digital literacy (which increases the burden on the community builder)

As far as my community migration is concerned, I’m looking forward to sharing more about the “migration strategy” aspect once I’ve managed to untangle myself from all the configuration and setup stuff.

I’m of course happy to hear about other “facebook migration” stories, and obviously, any responses to what I’ve laid out here. Again, sorry for being so verbose.

I know this looks a little like a quote-dump at times and there is some redundancy, sorry about that. I’ve added years in the source mentions if they aren’t recent, as I know Facebook and Discourse have evolved over the years – although I’ve paid attention to only keep quotes that still seemed valid today.

1 个赞

哎呀,所有的帖子标题都出现在了引文的上方。正试图修复这个问题。Markdown 看起来是正确的,为什么会这样呢?

我认为它试图强调这不是对该主题的引用,而是您引用了另一个主题。该链接提供了一种方便的方式来查看该主题以获取更多上下文。

我不认为有简单的解决方法。您可以通过删除主题和帖子属性来删除所有 Discourse 的魔力:


[quote="stephtara"]
在过去的几天里,我意识到这是我遇到的问题的关键因素,直到现在这可能有点盲点。
[/quote]

它显示如下:

而不是像我在编写时(右侧“预览”面板)显示的那样:

所有帖子标题都占据了所有的“注意力” :cry:,我必须说这让我的主题几乎无法阅读 :sob:

哦,我明白了……问题在于它强调了主题,而我想要突出的是引文,而不是主题……

1 个赞

但那样就没有点击到帖子的方法了……也许我应该把整个主题放在回复里 :sweat_smile:

(作者已删除帖子)

如果我这样做,是否有“短代码”的方式来链接到原始主题/来源?

链接引用的外观对于这里的常旅客来说应该非常熟悉——我怀疑它有多分散注意力。我根本没注意到。:wink:

1 个赞

这是一个关于从 FB 迁移到 Discourse 的有说服力的案例。我猜想许多社区使用 FB 群组(以及 Discord——呸)是因为它们是“免费的”,任何有成本的替代方案都很难推销。但有些人会看到其价值。我希望看到更多地远离 FB 这样的企业围墙花园。我猜想理想情况是 a.) 一个一体化的抓取和迁移工具,以及 b.) 一个对迁移用户来说尽可能熟悉的预配置 Discourse 设置。

1 个赞

谢谢!我还是把它们都修复了(并提交了一个错误报告——待定——因为我觉得我在可视化编辑器中看到的内容应该与发布的内容相匹配!)

@ToddZ 很高兴听到这个消息!老实说,我不确定“免费”是社区聚集在 Facebook 上的最主要原因。我认为是因为人们已经“在那里”了,而且建立一个社区超级简单(十几次点击),邀请你的朋友,他们再邀请他们的朋友,就这样开始了。现在,免费这一点确实意味着,即使是支付基本托管套餐(每月 20 美元)的提议也会非常难以推销。如果基础套餐能满足我社区的需求(目前不能),我会为我的社区付费的。

如果我们做一些设想:我认为一个真正有趣的第一步将是:

  • 一个标准的设置/配置“包”,可能捆绑了一些插件和组件
  • 一个真正的“假脸书”基础主题(试用了当前的主题,还没有达到要求,尽管我很喜欢这个想法)

这些加在一起,能让“开箱即用”的 Discourse 变成某种东西,表面上可能稍微简化一些,但不会让 Facebook 迁移过来的用户感到太陌生。

这还可以附带一个用户友好的向导,用“人类语言”收集社区建设者关于社区某些方面所需的信息,以便做出配置选择——然后设置相应的配置。

例如,可能会问这样的问题:

  • 社区的普通成员预计技术水平如何?
  • 你希望人们收到大量电子邮件通知,还是不希望?
  • 社区中的所有成员都能相互聊天和私信对你来说重要吗?
  • 你是想把所有人都放在一个“论坛”(即分类)里,还是有多个?
  • 除了版主之外,你的社区中是否有需要对全部或部分社区拥有“特殊权限”的用户组?

这些只是我随口想到的,对 Facebook 群组管理员进行一些用户研究可能会有助于确定需要询问哪些信息。

就我所知,这种更人性化的设置界面对其他首次使用 Discourse 的管理员也会很有用——比 Connecting site settings to documentation 更进一步,那已经是一个很棒的计划了!

当涉及到抓取/复制内容时,我不确定这到底有多大用处。在一个理想的世界里,Facebook 会有一个真正的导出按钮,那会很棒,但这种情况不会发生。我曾尝试用浏览器脚本来保存帖子和评论串,但使用起来非常繁琐。

对于我的社区来说,有一些重要的帖子我们会手动复制过去,但 Facebook 上的大部分内容恐怕只能留在那里了…… 我认为开发一个完整的抓取/导入系统所需的工作量可能不值得。

然而,有趣的是(这更多属于我尚未详细说明的“迁移策略”章节),是那些有助于在 Facebook 中“植入”Discourse 主题的工具,以鼓励人们去 Discourse 上查看它们,就像 @oshyan 提到的那样。这将在迁移阶段在一定程度上帮助弥合“集成差距”。