Lemmy.zip owner & admin
Contact me via hello@lemmy.zip


  • Elsewhere: me.lemmy.zip - See my accounts across the internet
  • 261 Posts
  • 599 Comments
Joined 3 years ago
cake
Cake day: June 10th, 2023

help-circle




  • The actual lemmy database sits around 110GB at the moment. And that’s with almost 3 years of posts/comments from all over the fediverse, so I think that’s a reasonable storage amount.

    I don’t know of a way of seperating out local vs federated in terms of content to be able to check it’s size, it’s all held in the same table(s) with a local flag if local. There is probably a way, I’d need someone smarter than me to work it out though.

    A surprising risk to storage at one point was prometheus and keeping hold of massive amounts of log files so that we could work out when and where we were being attacked from. By implementing a full challenge in cloudflare, we’ve been able to stop that which is why that graph comes down a bit.

    The biggest storage issue is images, which is 2.1TB at the moment. There is a way to clear this up a bit with some software, but it’s apparently got risk, so low down the priority list at the moment as object storage is cheap and doesn’t affect the server directly.







  • I agree with you.

    Piefed is great, but there is so much bias built into it. Say what you want about lemmy’s devs, AFAIK there is none of their bias built in to lemmy.

    The whole jump to piefed movement has not sat well with me. I get the extra features, but for it to really be something for everyone the dev has to consider their approach. Who knows what might be targetted next because the dev doesn’t like it. (Hyperbole btw, but its akin to censorship)

    Calling piefed.zip negligent because we give users control of their experience speaks volumes about either a poorly thought out system or a purposeful bias which shouldn’t exist in federated services. At least add the csam or far right instances to it if its a genuine tool, or remove it entirely