0
0

[–] shh_coffee ago 

Beat me to the punch. I was going to say the same thing.

I have a really terrible internet connection and I like to tab up a bunch of comment threads at once so while the internet is flaking, I still can read up on stuff and comment back when the signal decides to come back. With the threads collapsed so soon, I'm forced to load up new pages that take forever for me sometimes.

I know it's a small gripe and for the moment it's probably what's best for the servers but down the road it would be nice to have a configurable option of how many comments to show before collapsing.

0
1

[–] nanowerx 0 points 1 point (+1|-0) ago 

Probably for the best right now with all the server bombardments...cuts down on the bandwidth a little so at least some of the site is functioning during spikes. But, yeah, I really hope this is fixed soon. I really like reading commentary way too much.

0
3

[–] 730T 0 points 3 points (+3|-0) ago 

I came here to post this. This definitely has to be improved, or have an option to manually set number of comments you wanna see.

0
3

[–] Mr_Winsterhammerman 0 points 3 points (+3|-0) ago 

I definitely agree and it's slightly annoying. I have zero admin experience but I presume the site only loads the top few levels of comments in order to take some strain off of the already overburdened servers (no sense loading content that users may not care about). Hopefully this won't be an issue in the near future. For the time being I think a viable compromise would be to embed the comments behind the "continue this thread ->" on the same page instead of loading a new page.

Come to think of it, wouldn't the current method of loading an entire new page hammer the servers harder than embedding a few more comments on one that's already been loaded?

0
0

[–] Vheissu_ ago 

Although I have no more information than you do, what you have said is most likely correct. Whenever a page is loaded, the contents of the page itself like the title and description are most likely being cached. However, the comments section is dynamic and therefore every time someone loads the page that is another request and presumably expensive database operation (depending on the type of query and how your database is configured).

The current method is how I would handle reducing load. Whoever is handling this stuff at Voat is banking on the fact that not everyone will click the continue viewing link therefore potentially saving a few hits to the database. Rather than assuming everyone wants to see every comment, they know only a certain subset of visitors actually will. Reddit limits threads on a submission presumably for this reason, but they have more server resources at their disposal, so the depth they allow is greater than Voat currently does.

0
2

[–] Randomacts 0 points 2 points (+2|-0) ago 

That sounds right to me, new text isn't that much data.. a new page however is a bit.

0
1

[–] ten-thirty 0 points 1 point (+1|-0) ago 

Could anyone who knows about admin address this? I'm curious.

0
6

[–] 600445? 0 points 6 points (+6|-0) ago 

Voat could put a system in place where instead of a link saying to continue the thread, there would be a simple link that shows the comments right below in the same page to improve convenience for those who want to read all of the comments and preventing side scrolling for those who only with to see the parent comments and a few child comments.

0
3

[–] kuuttis [S] 0 points 3 points (+3|-0) ago 

I like that idea too. Just like we have the "Load more" button at the bottom right now. Comments should be loaded on the same page for those who want to read them all. As it is now when I click the "Continue thread" link it takes me to another page and is kinda annoying to load up pages multiple times

0
0

[–] Kvoat ago 

I'd like a "Load all" button somewhere, because I like to Ctrl+F for things a lot in the comments, and like you I would like them all to be loaded on the same page for at least double the amount of levels it goes to currently.

0
3

[–] 600913? 0 points 3 points (+3|-0) ago 

That annoyance is multiplied when browsing on mobile because you have to hope that the browser saved the session on the previous page and you won't have to wait for it to reload and scroll back down to where you were.