Leave no one wants you here mr muskrat
Ensign "Junior Engineer #4" will be missed dearly
Lightly used, not in any wars
It can ship itself! Same day-delivery!
That's why you have failover; you never have to fight terrorists to keep your contractual uptime agreements!
It'll be a pain to clean I would assume
Poor wide Kim
The sneaky play is to copy over all her tabs when she's sleeping, then see if she notices. Either that or just slowly start closing her oldest tabs and see if/when she notices, then get her to move over when it's managable
Just don't get any egg into the gas
I wish I could do that, but they just don't seem to really care
I always suggest FOSS options when they apply!
I want to say the first, but it's the second
I like the crossing of the toothbrush and toothpaste like two swords
Local Instance Processing After Unsubscribed Fix
Does anyone know any sort of solution to this issue: https://github.com/LemmyNet/lemmy/issues/3568
Formatted Instance and Now Doesn't Work
I accidentally formatted the data directory containing all of the data for my Lemmy instance, and now when I try to remake the instance it works fine till I connect the domain to the server, where it proceeds to stop working. Looking at the logs I think it might be because all of the instances are trying to send their posts to a user which doesn't exist anymore, is there a way to fix this?
Lemmy Instance Not Syncing Correctly
I'm trying to set up a personal Lemmy instance, and I've got it running but it doesn't seem to sync very well with posts and comments made before the instance was created. I ran [lemmony] (https://github.com/jheidecker/lemmony) to get the /all to work correctly and to start syncing communities, but now when I go to some communities and I look at the posts created before I subscribed to the community, they either don't show up or don't have the correct number of upvotes/comments. Also, when I search for communities, next to the community name is only the number of users from my instance subscribed, not the actual number of subscribers to the community. Is there a way to fix this?