This post, a day before yours on the lemmy_support@lemmy.ml community, is describing some similar behavior, with some CPU usage at start (at least on the first boot; not clear whether that is a one-off on migration from the text) and then federation problems with 0.19.1:
After upgrading Lemmy from 0.18.5 to 0.19.1, the lemmy_server process is taking up 200-350+% of my CPU…It seems like my instance isn’t federating properly now tho.
I got som weird behaviour, like nothing worked very well, with 0.19.0 so I updated to 0.19.1 and after quite a while (small instance, beefy PC) it starts to work again, it seems.
Except I am now a moderator everywhere. Maybe it doesn’t work, I won’t try, except asked, so can someone make a post that I can sticky or delete just to see what’s happening?
The lemmy frontend will come up fast, but you would see an error and a popup telling you that lemmy is still starting. If you can see content, then the DB migration is finished already. The 1.3.0 branch of ansible doesn’t have any changes which would cause performance impact. Currently it just adjusts the readme and adds pictrs 0.4.7.
I have the same problem with Jerboa, yet if I accesses Lemmy through a web page, my account is fine. I installed Eternity on the phone and my Lemmy account has no problems on that app. Another data point that this is probably a Jerboa issue.
As someone who is against use aggregate scores and pleased to see it removed I can understand the desire to make it available to admins/moderators to assist in their actions.
I think making the numbers available only for admins/mods would make sense, though I also feel it starts to get to be an arbitrary divide.
I also have to wonder if an admin/mod couldn’t simply use the view of the user’s posts/comments we all have access to along with the various sorts available. Want to know if a user posts generally well received stuff … look at their posts and sort by “Top all time”. Want to know if they’re regularly posting stuff that is poorly received, sort by “Controversial” (which is new) or just “New”. I’d suspect that in the end integrating this sort of lookup into the moderation tooling so that it’s easier/quicker to do would be more worthwhile than persisting with user aggregates.
You can also have a look at how other people did it. There should be a button somewhere to view the source text of any post or comment. In the Lemmy web-interface this button is hidden behind the three dots icon.
Try select * from instance where domain = ‘popular.instance’; and see the last time it was updated via the updated column. I’ve been having to update that column with update instance set updated = now(); because once that timestamp becomes older than 3 days your instance assumes it’s “dead”.
I checked a few instances and they were all last updated on November 18th. I ran that query and updated the updated field to now for all rows, but they aren’t continuing to update after that, and no traffic is coming through.
This seems like a weirdly unnecessary way to not quite manage to duplicate what lemmy has been designed to do.
How do I make it just work with just my original account?
You go to the community list for your instance and do a search on the URL of the community you’re interested in. Then (assuming that your instance is federated with the other one) your instance will create its own mirror of the community, and you’re done.
I agree it’s probably weird, unnecessary? eh depends on use case. lemmy (atleast the website) seems to meet me halfway with why I would use Bookmarks to begin with. one thing I can’t seem to figure out is how to set custom categories for Lemmy communities that I subscribe to/order them without having to unsubscribe and subscribe again to communities, in the web interface.
one thing I can’t seem to figure out is how to set custom categories for Lemmy communities that I subscribe to/order them
Yep. Lemmy doesn’t provide any community management tooling, which is a shame, because a little can go a long way. Some clients provide some help, but generally it seems to be a lacking feature set.
Upgrade your storage. 160GB is nothing and 1TB SSDs are cheap
You could delete pictures, but then the posts are broken
You could archive old pictures. The pictures will have a longer load-time. Also I don’t think archiving pictures is a feature of lemmy, so you would have to implement it yourself
Edit: I think postgres is so big, because of backups. You could delete those, but that’s risky
Since I currently use Hetzner the only way to get more space is to upgrade the server (at a not inconsiderable cost).
The alternative might be to purchase SSD block storage volumes which are definitely lower priced (5€ per month for 100GB) however it would be interesting to know if there is a guide for Lemmy for this or if others have had positive experience doing this.
Since this problem I think is quite common (at least from reading a few threads and comments around) it might be interesting to create a guide especially regarding the part of having lemmy use this/mounted volume instead of the default one.
I in the meantime will try to look around for some information on how this can be done, any advice is definitely welcome.
Ok, I think it may just be some syncing issues. I can see comments/reactions slowly start pouring in.
I recall a similar experience when using matrix chat for the first time. Everything is synchronizing very slowly for the first time creating very confusing experience for new users.
Thanks. Yeah, losing the account kind of sucks but not the biggest deal. The ability to instance-hop is a great strength of the fediverse, even if it does mean I have less faith that my accounts are permanent.
I'm really sorry for what happened to you. And I'm really disappointed because lemmy allows fascist instances and fascist friendly instances to stay, like lemmy.ml, the bears, the grads, and others. Why can't they just leave like exploding-heads did? Why right fascism is bad and left fascism is good, when fascism is fascism after all?
lemmy_support
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.