I switched to 18.1 this weekend, and the cpu is basically bored now ;)
I switched to 18.1 this weekend, and the cpu is basically bored now ;)
What the Wandermeister over here said.
Object storage generally is much cheaper than vm disk space (I got 1TB for $5/month at vultr). And the sooner you do it, the better - the migration process took 3 hours for me yesterday, transferring just over 102k files (34 GB).
Hole in their pocket?
Use rsync to get the bulk of the data over (even if it’s mid write) one or more times, then stop the stack on the origin server, and run rsync again. It should be much faster.
I think that’s more of a client issue than a server issue though.
Yeah, my instance doesn’t have a lot of users, but it does have a lot of posts (few thousand per day). It might be all the updates it’s sending out.
I guess I’ll just have to give 0.18 a try then.
Depends on where it was posted. That has no place in !technology@lemmy.ml, for example. Context is key.
Edit: I see now that it was posted to !worldnews@lemmy.ml. Which is indeed more relevant (haven’t read the article). Still, every lemmy instance has it’s own moderators and moderator styles. If you don’t agree with the moderators of this community, then by all means subscribe to a different one, to get your varied mix of news.
All in all I don’t see this as a problem with the Lemmy instance, just possibly with that specific community. It definitely isn’t a Lemmy Support issue though.
I wouldn’t be surprised if they had, actually.
Still, a spam bot can just use the free license - they won’t make nearly as much api requests as a proper app would.
The ones that make 60 posts per account per hour are easy to detect no matter how they post.
Storage on the vm won’t be too much of an issue, as long as you make sure to use Object Storage (s3) for pict-rs from the start. For Lemmit (just a few users, but hundreds of communities and over 150k posts) I’m doing fine with just 2 GB of memory, 1 vcpu, and 2 GB of disk storage for postgres. The storage bucket is sitting at 36 GB.
You might want to scale up cpu and memory for more users as you grow, but you’d be surprise with how little resources you can get away.