Conversation

Notices

1. Embed this notice
   Administrize (admin@cawfee.club)'s status on Wednesday, 14-May-2025 21:50:09 JST Administrize
   One two. One two. Is this thing on?
   
   *ahem*
   
   Brothers, xisters, welcome back. As you probably know, Cawfee Club has unprecedently been down for a month. What started as a weekend maintenance, kept dragging on and after a week or two, I became increasingly despondent and my mental state spiraled downwards. It was pretty much this feedback loop when the longer the instance was down, the less I felt like fixing things. So yeah, you could say it's my fault.
   
   I could apologize endlessly, but for now, just seeing the levels of activity on here so high after only a few hours moves me beyond words. I really love you guys, and I missed you a lot.
   
   A thorough explanation will come later. For now though, there's a particularly vile bit of disinformation I have to debunk - this downtime was NOT caused by updating Pleroma. I did not update Pleroma. I'm looking at you, hakui.
   
   That being said, we'll be federating in whitelist mode for at least a day or two so that the server is not overloaded by catching up on too many posts. I'm open to adding any instances to the whitelist, just tell me the domains in response to this post.
   • nyanide :nyancat_rainbow::nyancat_body::nyancat_face: likes this.
   • nyanide :nyancat_rainbow::nyancat_body::nyancat_face: and snacks repeated this.
   • Embed this notice
     nyanide :nyancat_rainbow::nyancat_body::nyancat_face: (nyanide@lab.nyanide.com)'s status on Wednesday, 14-May-2025 21:50:17 JST nyanide :nyancat_rainbow::nyancat_body::nyancat_face:

     in reply to
     @admin Cool
   • Embed this notice
     :blobcatflower: (methyltheobromine@netzsphaere.xyz)'s status on Wednesday, 14-May-2025 21:53:58 JST :blobcatflower:

     in reply to
     @admin tl;dr the feds took over cawfee club
     snacks likes this.
   • Embed this notice
      (mint@ryona.agency)'s status on Saturday, 31-May-2025 07:29:34 JST 

     in reply to

     • r
     • Vokainen
     @admin @vokainen099 @r As a fellow custodian of records, pruning objects with no criteria other than them being "old" is shameful. Protip: you could just yeet all Like and EmojiReact activities with no downsides (as they are recorded in object itself and the API just grabs them from its key) and thus slim down the DB even further. This might or might not break retracting them for local users, so limit it to non-local activities just in case. I recommend doing it offline with SET session_replication_role = 'replica' to make it fast.
   • Embed this notice
     Administrize (admin@cawfee.club)'s status on Saturday, 31-May-2025 07:29:35 JST Administrize

     in reply to

     • r
     • Vokainen
     @vokainen099 @r Sure.
     
     >How much space did it save in the end?
     If I remember correctly, 34 GB. The objects table got pretty much halved. As for activities, only about 2 GB got removed after 16 hours of running it on my laptop. When it ran directly on Cawfee for weeks, it was probably even less, but that's the throttled block storage for ya.
     Of course you'll have to squash/repack afterwards to reclaim the space.
     >Did you also pass the --prune-orphaned-activities argument?
     Yeah. That's the slow part. The queries have multiple joins, phnt said it can't really be done any other way. But years ago when only Akkoma had this, I took their commits and it took less than a day. (https://info.cawfee.club/soti-2024-04.html) The Pleroma implementation is different.
     It didn't even get to the second query.
   • Embed this notice
     Vokainen (vokainen099@cawfee.club)'s status on Saturday, 31-May-2025 07:29:36 JST Vokainen

     in reply to

     • r
     @r @admin Second this. Just curious what was going on, though I can wait the later writeup
   • Embed this notice
     r (r@freesoftwareextremist.com)'s status on Saturday, 31-May-2025 07:29:37 JST r

     in reply to
     @admin How much space did it save in the end? I was kind of thinking about doing the same thing. Did you also pass the --prune-orphaned-activities argument?