306
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 28 Jun 2023
306 points (98.1% liked)
Asklemmy
43958 readers
2028 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
I tried out my own, one person instance, and I had a hard time getting comments to pull in. I would have to browse to the original instance to view all of the comments. Have you found a good way to overcome that?
I switched back to a more public instance just because I found the process of going out to view the content, back to my own instance if I wanted to comment, then back to the original again to keep reading the discussion very tedious.
Being on a more populated server seems to give most if not all of the comments directly.
When you first subscribe to a community it only pulls in the last 20 or so posts and I think a limited amount of comments, and then everything going forward. This seems to be a common point of confusion for a lot of instance admins.
Presumably this is to prevent a possible DDoS/performance failure vector as it would be trivial to setup a large swarm of instances on tiny VM's and then simultaneously start hitting massive communities from a single instance and requesting a large body of historical content.
Edit: Also when you first setup and start subscribing to a large number of instances, this initiates a LOT of communication and database writes. Lemmy still has some performance bottlenecks. Once everything is initially synced and settled it runs fine. I have a friend running their instance on a $5 Linode instance that only has 1vCPU and 1GB of RAM without any issues, and they're hosting users.
I ran mine for a couple weeks, and communities I'd been subscribed to from day 1 were still missing most comments on the posts unless I clicked through to their page. Maybe there was something funky with my install, but I used Lemmy's ansible scripts to deploy so I don't know what else I could do.