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.
11개의 좋아요
Perhaps @neil can ping you about this? We are looking for sites to go in depth on this so we understand it.
7개의 좋아요
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…
2개의 좋아요
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?
2개의 좋아요
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.
1개의 좋아요
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.
1개의 좋아요
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.
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.
16개의 좋아요
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?
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.
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.
1개의 좋아요
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.
2개의 좋아요
Thanks for sharing your stats!
2개의 좋아요
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 
10개의 좋아요
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
3개의 좋아요
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.
11개의 좋아요
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?
3개의 좋아요
정말 훌륭한 아이디어입니다. @Gunnar 님, 잘하셨습니다.
광고 수익 감소에 대한 몇 가지 생각을 나눠보겠습니다. 많은 알고리즘(구글의 페이지랭크 등)과 광고 시스템은 페이지 기반 패러다임에 뿌리를 두고 있습니다. 클릭이 많을수록 참여도가 높아진다고 보는 것이죠. 이것이 그들의 보상 모델의 핵심입니다. 이것이 바로 수익을 얻는 방식이자, 인프레션과 클릭을 기준으로 비용을 청구하는 방식입니다. 페이지 뷰라는 개념을 제거하고 참여도, 체류 시간, 분석 기반 상호작용으로 전환하면 새로운 것이 탄생합니다. 바로 문명적인 토론입니다.
우리가 모두 클릭을 쫓는 것을 멈추고, 질 높은 토론과 참여, 그리고 더 높은 수준의 커뮤니티 의식으로 나아가기를 바랍니다. 그러면 새로운 지속 가능성 패러다임이 등장할 것입니다.
제 의견으로는 커뮤니티 포럼에는 무료 구성 요소와 프리미엄 유료 구성 요소가 모두 있어야 합니다. 예를 들어 커뮤니티 커머스를 들 수 있습니다. 이렇게 하면 광고에 의존하는 포럼 대신, 회원 간 상거래로 부분적으로 자금이 조달되는 커뮤니티를 구축할 수 있습니다. 다소 과한 요구일 수 있다는 점은 알고 있습니다. 하지만 꿈꿀 수는 있는 것이죠.
5개의 좋아요
모든 기능을 다 찾았다고 생각했는데 
일반적으로 기존 커뮤니티가 있는 사람들이 겪는 어려움을 지켜보는 것도 흥미롭습니다. 우리는 처음부터 커뮤니티를 구축하고 있기 때문에 그런 문제는 없습니다. 사실, 모든 것을 설정하는 동안 사람들이 인내심을 가질 수 있도록 하는 것이 오히려 더 어렵습니다.
3개의 좋아요
숙련된 사용자가 항상 이를 처리해야 하는 상황에서도, 스크롤 바의 스케일/정밀도가 실시간으로 바뀌는 것은 여전히 어색하고 불편한 UI입니다. 진정한 UI 검토를 통과할 수 없을 것이라고 확신합니다. 저는 브라우저 스크롤 바가 항상 실제 스크롤 범위를 반영해야 한다는 쪽입니다. 이 모델에는 단점이 없다고 봅니다(구현이 어려울 수 있다는 점을 제외하면).
4개의 좋아요