# Unfortunately I had to pull the plug **URL:** \ **Category:** Community Building\ **Created:** [May 12, 2019, 1:41pm UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508 "2019-05-12T13:41:22Z")\ **Posts on this page:** 1\ **Showing post:** 62
**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\ **Post date:** [May 12, 2019, 11:50pm UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/62 "2019-05-12T23:50:18Z")
@eesty thank you so much for posting feedback here, it certainly helps us. I did want to quickly address the various points here: > [@eesty](#): > > A large portion of my user base did not like infinite scrolling. To me it makes sense, but the types of topics on my forum may go on for up to 20,000 posts. I guess you can’t teach on old dog new tricks. This pops up from time to time. A very strong position we have held ever since the project started is that “we will not add pagination”. At a fundamental level, if pagination is a **must** then Discourse is not a good fit. Improving the experience though is on the table, things like allowing users to see bookmarks in the timeline, and fancier timeline controls are things we think about. > [@eesty](#): > > One-click quoting, something which every other platform can do, is three-click process in Discourse. My users read a post, then want to have a “quote” button that loads the quote in a composer, simple. Yes Discourse can “quote” but it takes a few clicks and my users did NOT like this at all. Though we will certainly not be adding this to core, amending post actions is completely doable in a theme component if you must. But keep in mind there is an aspect of “we must have MacDonalds” OK… “here is your unhealthy hamburger” to this. > [@eesty](#): > > Being a large forum with many users having over 20,000 posts, these users constantly hit 502 errors. Why? Well I never quite figured it out, but it seems that Discourse hasn’t quite refined the backend DB queries to handle users with a large history. When ever one of these large users tried to post, start a topic or do anything really, then they would just hang and crash out. Considering these are the influencers of the community, I couldn’t dismiss their complaints. This is something we do work on a lot (and did work on for our current release). It is hard to provide the huge amount of features Discourse has on offer with a very tight performance budget. We try to though, and we definitely made some improvements in the “user with tons of posts” department. @tgxworld even worked on the “giant topic” problem a bit a few month back. There is a fundamental issue though, to get all the features Discourse has you are going to need more server resources than traditional dead simple php forums. > [@eesty](#): > > Finally, revenue. I’ve run Adsense on my community for years and it’s helped offset the server and time costs. Since switching to Discourse my revenue instantly plummeted, down 90%. I gave it a month, I even used AdManager to try to improve things, but nothing was improving and it was burning a hole in my pocket. Be it Ads not showing, impressions plummeting or whatever, it couldn’t go on. > Further, the official discourse ad manager plugin bug on Mobile (screen jumping around) was driving my users away. In my opinion the official ad manager plugin should be pulled back to Beta until this critical issue is resolved. @neil recently spent a fair amount of time on this ad problems, I would be very curious for any specific reproducible issues. We want to improve this. --- _[View the full topic](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508)._