Sal, I got some error here: couldnt_get_posts. That appears every time that I try to visualise the instance through the "Subscribed" communities.
The error does not appear if I browse the instance through "Local" or "All", nor if I check the list of communities that I'm subscribed to. The error happens across devices and front-ends (tested with Linux Firefox, Android Firefox, Jerboa).
EDIT/UPDATE: I unsubscribed manually to a few communities each time, checking if the front page loaded fine. Eventually, it did.
Re-subscribing to either !technology or !fediverse seems to trigger the error again.
That's the same error I was asking about below, and wondering if I had to do with the current status of collecting all the content. If so, it sounds like it could be another day or two before we can view our front pages again?
For now, one option is to temp change your settings to browse by "Local" or "All". Or alternatively temporarily unsubscribe off a few comms; if you're subscribed to a small number of comms, some trial and error might help you to find which ones are causing the issue. (For me it was two LW comms).
Check if you're subscribed to any of those communities: !technology , !comicstrips or !memes. If you are, try to unsubscribe and see if your front page works again. For me it did the trick.
!fediverse was also giving me problems, but apparently it's fine now, so odds are that the problem will eventually go away on its own.
All of this sounds like the issue is related to the new server still loading up the communities. I'm subbed to a pretty good list so it's probably best just to wait for the server to catch up. Thanks for the info though!
Unsubscribing from comic strips did the trick a couple days ago, thanks! And just now I’ve subscribed back and everything is normal. So feel free to subscribe again.
(@Shdwdrgn ) I think it is related with the processing of so many activities per second while syncing with Lemmy.World.
I have tried changing some rate limits and the number of maximum database connections, but I get similar errors while moving around the site. The server is running well below 100% on all metrics, and the logs don't produce an obvious error. I will wait until we catch up with Lemmy.World and see if that fixes the issue. If it doesn't, then I will trouble shoot more in-depth.
Thanks! The database is currently fetching lemmy world data as fast as possible, so this might be saturating the database. Once the syncronization is tested, I will try to tune postgres if it still happens.
Great, thanks for letting me know!! I did a bit of research and I think that the next time I need to upgrade the instance I will move it to a dedicated server instead of a virtual private server. But hopefully it runs smoothly for some time! :)
Hey @RobotToaster , @lvxferre , and @Shdwdrgn - we are now in sync with lemmy.world and the database under much less stress. This seems to have fixed the problems that I observed on my end. Are your problems also resolved?
Ah! It looks like it JUST fixed it, I had checked about 15 minutes ago and still couldn't get my subscribed list to load, but it does appears to be loading up now. I'll reset my preferences and keep an eye on it through the day -- hoping for the best!
It should have been fixed about 13 minutes ago! Thanks for checking! If problems persist I will try to fine-tune the database settings as suggested above.
There was a brief outage soon after I left that last reply, assume you were doing another round of maintenance at the time, but otherwise it's still looking good from here.
Ah, thanks. I think that was when I reboot the instance to change a setting that controls how post thumbnails are generated, as the new setting was failing to generate thumbnails for many posts.
Hey friend. Been playing on my mander account for the last week without any issues. Hope you are able to find out the cause of your disconnects. Good luck.
Good to hear! But this one was not me. I could not figure out the root cause, and nothing of significance has changed... Hopefully whatever caused the issue does not reoccur!
I like the idea of downvotes, and no nobody on this instance is really abusing them
If they were being abused, then publicly viewable votes would probably hinder that a little bit. So far tho, it doesn't look like there is any need for something like that imo
On other matter: I'm planning to create a Linguistics community here, would it be OK? I noticed a few comms about other human sciences, but asking it to be sure.
I've long had concerns with up/down votes and like/dislike, especially the down/dislike. Nothing major, and I have no real solutions.
My concerns are only to do with the ambiguity. There are so many different reasons why someone might vote one way or the other or even just not vote at all that I think it's kind of weird that compiling the votes into a score seems to mostly work pretty good. That ambiguity means that it's difficult to derive meaning from any individual vote, which I think argues in favour of keeping it somewhat private. Just because a non-admin can jump through hoops to get someone's voting history, doesn't mean it should be deliberately made public.
As for keeping down votes, I'd be reluctant to mess with a system that works as well as it seems to. Personally, I very rarely downvote, as even that is more engagement than I'm willing to provide. In fact, one of the things I like about the client I use, Thunder, is that I have to long press a comment in order to vote. That little bit of friction means that I vote less often. When I vote, it's because I really mean whatever I intend the vote to mean.
This hides the button and the results from the UI - other instances can still vote, but it's not displayed. This change would be easy to implement and revert messing up anything. Personally, I do think that having up/down votes is a useful metric more often than it is abused. Disabling down-votes might be a good match for an instance dedicated to, for example, sharing one's own art, as users might feel more comfortable sharing in such a space.
There is a toggle in the admin settings to enable/disable downvotes, and several instances do disable them.
I didn't realize that.
Strictly as a user, from what I can tell, there doesn't seem to be anything that resembles rampant abuse of downvotes. I'm glad that is what is visible at the admin level.
Carry on, you're doing great work as a community builder/manager.
Hi! I think that no "local" user had subscribed to those communities, so this instances had not fetched those posts.
However... As soon as you fetched the community, the first 10 posts should have been automatically fetched. But you are right, the posts were not fetched as they usually are. Future posts should be fetched. My suspicion is that this could be related to the new federation queue system, but I am not sure. I also don't know if this is affecting only how posts made before the update are fetched, or if this will also affect newer posts.
Resetting the server helped push the posts through, and new posts appear to also go through.
But I was not able to identify the source of the problem. It could be related to the new federation queue. I did not see any relevant errors in the logs, so all I know is that the reset worked - at least for now. I'll see if it happens again or if others reports seeing the same.
Mander
Top