# 不幸的是，我不得不终止项目。

**URL:** <https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508>\
**Category:** Community Building\
**Created:** [2019年五月12日 13:41 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508 "2019-05-12T13:41:22Z")\
**Posts on this page:** 19\
**Page:** 5

<div class="post-metadata">

**Author:** ![bartv](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bartv/32/130052_2.png) [@bartv](https://meta.discourse.org/u/bartv)\
**Post date:** [2019年五月17日 20:11 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/83 "2019-05-17T20:11:37Z")

</div>

> [@DoMiN8ToR](#):
>
> Even worse, revenue declined terribly, only 30% of ad revenue was left after the migration.

I would be very interested to have a separate conversation about this, because I noticed _the exact same thing_. I have two websites, one Discourse and one WordPress. The RPM of my Discourse is also only 30% of what I see on WordPress. I’m not saying this is Discourse’s fault, but I’d like to look a little deeper into this with other Discourse admins, figure out which factors contribute to this, and see if we can find ways to improve that.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [2019年五月17日 22:28 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/84 "2019-05-17T22:28:28Z")

</div>

Perhaps @neil can ping you about this? We are looking for sites to go in depth on this so we understand it.

---

<div class="post-metadata">

**Author:** ![DoMiN8ToR](https://avatars.discourse-cdn.com/v4/letter/d/b2d939/32.png) [@DoMiN8ToR](https://meta.discourse.org/u/DoMiN8ToR)\
**Post date:** [2019年五月17日 23:49 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/85 "2019-05-17T23:49:19Z")

</div>

> [@bartv](#):
>
> I would be very interested to have a separate conversation about this, because I noticed _the exact same thing_

I’ve recently sold the site, so I can’t help much anymore. But I think it’s the combination of infinite scroll and the limited number of ad spots in the ad plugins.

With Vbulletin I knew all code pretty much by heart (as I know the infamous PHP/MySQL combination well). Discourse, being Ruby and Ember, appeared to be a too steep learning curve to get it right myself. I hope for OP (and others) that the team finds ways to increase revenue for everyone…

---

<div class="post-metadata">

**Author:** ![Ubik](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ubik/32/89095_2.png) [@Ubik](https://meta.discourse.org/u/Ubik)\
**Post date:** [2019年五月18日 00:23 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/86 "2019-05-18T00:23:19Z")

</div>

> [@TheBestPessimist](#):
>
> The sidebar on the … side… helps with this navigation even more, as it’s so easy to search for the post i desire.

Could sidebars be marked with 4 divisions, no numbers, just a visual cue so people can see roughly where 25%, 50% is, especially on a topic that’s into the high thousands?

Or would this not be possible?

 ![25percent](https://global.discourse-cdn.com/meta/original/3X/9/5/95694ec33a911403ea80f9f458eda9d1c649b048.jpeg)

---

<div class="post-metadata">

**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\
**Post date:** [2019年五月18日 00:33 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/87 "2019-05-18T00:33:54Z")

</div>

I’m sure you could do something with CSS if you really wanted to add it to your site. I don’t think it would make a lot of sense for the majority of communities, because the percentage along the bar doesn’t necessarily translate to anything.

---

<div class="post-metadata">

**Author:** ![orangeandblack5](https://avatars.discourse-cdn.com/v4/letter/o/edb3f5/32.png) [@orangeandblack5](https://meta.discourse.org/u/orangeandblack5)\
**Post date:** [2019年五月18日 00:33 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/88 "2019-05-18T00:33:58Z")

</div>

I think we can do better than that if we’re going to start adding things to the timeline across all of Discourse.

Not a bad idea, to be clear, just a low bar if we’re going to be doing timeline improvements.

---

<div class="post-metadata">

**Author:** ![marianord](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/marianord/32/90502_2.png) [@marianord](https://meta.discourse.org/u/marianord)\
**Post date:** [2019年五月18日 02:31 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/89 "2019-05-18T02:31:26Z")

</div>

> [@DoMiN8ToR](#):
>
> Even worse, revenue declined terribly, only 30% of ad revenue was left after the migration.

I migrated from SMF to Discourse, I did had an ad revenue decline (and visits). But currently, after almost a year I’d say I’ve recovered all my revenue, my community is more active, specially for the improved performance on mobile.

 ![imagen](https://global.discourse-cdn.com/meta/original/3X/8/2/822bef9ab318d8c29b8cd07e0d7044e3edf929cb.png)

I did the migration between February and March 2018, when the steep decline shows. From there, you can see an upward trend that hasn’t stopped.

The hardest part was the reindexing of all the topics back into Google.

---

<div class="post-metadata">

**Author:** ![TheBestPessimist](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/thebestpessimist/32/247704_2.png) [@TheBestPessimist](https://meta.discourse.org/u/TheBestPessimist)\
**Post date:** [2019年五月18日 05:13 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/90 "2019-05-18T05:13:19Z")

</div>

> [@Ubik](#):
>
> Could sidebars be marked with 4 divisions, no numbers, just a visual cue so people can see roughly where 25%, 50% is, especially on a topic that’s into the high thousands?

I can understand why would you want that? The _(is it called timeline? i remember there was a “nomenclature” post somewhere, but i lost it ☹)_ timeline is very easily usable right now. nothing is loaded as long as you keep it clicked (no needless resource usage), you have the back button easily reachable You have the date (in case someone says “March 1989”) Everything feels really nice and “at its place”. Adding the 25% markers would bring unnecessary noise.

Btw, @ staff, why did the “Back” button disappear at the end?

---

<div class="post-metadata">

**Author:** ![Ubik](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ubik/32/89095_2.png) [@Ubik](https://meta.discourse.org/u/Ubik)\
**Post date:** [2019年五月18日 08:36 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/91 "2019-05-18T08:36:08Z")

</div>

> [@TheBestPessimist](#):
>
> I can understand why would you want that?

_I_ don’t, apologies for not making that clearer, I was just wondering if 3 markings on the bar would be an easy way to make it feel more navigable for some people. It’s not a personal request though.

---

<div class="post-metadata">

**Author:** ![TheBestPessimist](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/thebestpessimist/32/247704_2.png) [@TheBestPessimist](https://meta.discourse.org/u/TheBestPessimist)\
**Post date:** [2019年五月18日 08:50 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/92 "2019-05-18T08:50:08Z")

</div>

> [@TheBestPessimist](#):
>
> I can understand why would you want that?

> [@Ubik](#):
>
> I don’t, apologies for not making that clearer

Nah, it’s my fault here, shouldn’t have said that YOU want it, i was talking generally, just that i used the bad addressing.

---

<div class="post-metadata">

**Author:** ![jtbayly](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jtbayly/32/119510_2.png) [@jtbayly](https://meta.discourse.org/u/jtbayly)\
**Post date:** [2019年五月18日 11:33 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/93 "2019-05-18T11:33:19Z")

</div>

The bigger problem is that if they were percentage based, the posts they took you to would constantly change. But they look like static references.

---

<div class="post-metadata">

**Author:** ![gingerbeardman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gingerbeardman/32/540824_2.png) [@gingerbeardman](https://meta.discourse.org/u/gingerbeardman)\
**Post date:** [2019年五月26日 23:08 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/94 "2019-05-26T23:08:55Z")

</div>

Thanks for sharing your stats!

---

<div class="post-metadata">

**Author:** ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)\
**Post date:** [2019年六月15日 05:39 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/95 "2019-06-15T05:39:42Z")

</div>

With the support and input of @Merlls_Rizzini I have created this plugin which addresses some of this feedback, so now you have options and can happily adopt Discourse regardless of your views on quoting 🙂 💪

[https://meta.discourse.org/t/fast-quote-plugin/120427](https://meta.discourse.org/t/fast-quote-plugin/120427)

---

<div class="post-metadata">

**Author:** ![Andy02](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/andy02/32/119498_2.png) [@Andy02](https://meta.discourse.org/u/Andy02)\
**Post date:** [2019年六月15日 07:16 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/96 "2019-06-15T07:16:51Z")

</div>

> [@DNSTARS](#):
>
> We have some larger rolling topics (1500 posts odd) and I get one of the high trust chaps to put a table of contents into it.

That would be a cool plugin. If users could choose to add tags to their posts which would automatically be turned into a contents page at the top.

Or experienced users could tag the important posts as they go for the same purpose

---

<div class="post-metadata">

**Author:** ![JimPas](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jimpas/32/148179_2.png) [@JimPas](https://meta.discourse.org/u/JimPas)\
**Post date:** [2019年六月18日 00:29 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/97 "2019-06-18T00:29:48Z")

</div>

On the Tomnod forum we decided that topics with many replies be broken down by year… having the topic name preceded with the year. A couple have been broken down into “quarters” or every 3-months. This has made a big difference by not having to scroll forever and a day. In almost all cases, a reference link is inserted by the moderator back to the previous topic (with the same name but an earlier date. The "old"topic also has a link to the newer topic as the last entry, then that topic is closed. In 4 years no one has complained. Of course, a search query will point one to whichever “dated” topic(s) is/are relevant. Just one possibility to think about.

---

<div class="post-metadata">

**Author:** ![Cécile\_Savoie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/c%C3%A9cile_savoie/32/142370_2.png) [@Cécile\_Savoie](https://meta.discourse.org/u/C%C3%A9cile_Savoie)\
**Post date:** [2019年六月23日 18:22 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/98 "2019-06-23T18:22:41Z")

</div>

How about considering the following : 1 more click = half a second to think before one writes, so that one has a tiny bit of time to make sure one is bringing value to the post one is **reacting** to?

---

<div class="post-metadata">

**Author:** ![asirota](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/asirota/32/197298_2.png) [@asirota](https://meta.discourse.org/u/asirota)\
**Post date:** [2020年十二月5日 13:13 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/103 "2020-12-05T13:13:20Z")

</div>

这真是一个绝妙的主意。做得好，@Gunnar！

关于广告收入下降，我有几点思考：许多算法（如谷歌的 PageRank）和广告系统都完全基于以“页面”为核心的范式。点击量越多，意味着参与度越高。这恰恰是其奖励机制的核心所在。你们靠这种方式获得报酬，他们则按这种方式收费：即按展示量和点击量计费。当你摒弃“页面浏览量”这一概念，转而关注参与度、用户在站停留时间以及基于分析数据的互动时，便会催生出一种全新的模式：理性的公共讨论。

希望我们都能不再追逐点击量，转而追求高质量的讨论、互动以及更强的社区归属感。一种新的可持续发展范式也将随之诞生。

我认为，社区论坛应当同时提供免费的组成部分和付费的高级组成部分，例如社区内的商业活动。这样一来，我们便不再依赖广告支持的论坛，而是开始构建由会员间商业活动部分资助的社区。我知道这要求颇高，但我可以做梦。

---

<div class="post-metadata">

**Author:** ![Tris20](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tris20/32/264639_2.png) [@Tris20](https://meta.discourse.org/u/Tris20)\
**Post date:** [2022年一月11日 22:34 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/104 "2022-01-11T22:34:04Z")

</div>

当我以为我已经找到了所有功能时 😲

总的来说，看到现有社区的人们遇到的困难很有趣。我们正在从零开始建立自己的社区，所以没有这样的问题。事实上，我发现很难让人们在我配置好一切之前保持耐心。

---

<div class="post-metadata">

**Author:** ![staggart](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/staggart/32/284327_2.png) [@staggart](https://meta.discourse.org/u/staggart)\
**Post date:** [2022年十二月24日 19:26 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/105 "2022-12-24T19:26:52Z")

</div>

> [@merefield](#):
>
> 每添加一个“无限滚动块”，Chrome（至少）的滚动条都会重新调整比例以准确反映您所在的位置。

滚动条动态改变比例/粒度仍然很蹩脚，而且用户界面很尴尬，即使是经验丰富的用户也必须一直处理它。我相信它永远无法通过真正的 UI 审查。我属于浏览器滚动条应始终反映真实滚动范围的阵营。我认为该模型没有缺点（除了可能难以实现）。

[上一頁](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508.md?page=4)
