Conversation

Notices

1. nyanide :nyancat_rainbow::nyancat_body::nyancat_face: (nyanide@lab.nyanide.com)'s status on Friday, 08-Nov-2024 22:49:27 JST nyanide :nyancat_rainbow::nyancat_body::nyancat_face:

   • david
   @lukyan @david that can't be entirely true for all implementations, there are implementations which aim for less configuration/maintenance and more mileage, actually that's one of the selling points of honk.
   
   I'm also not sure when I'm supposed to be experiencing the major side effects of the so called pleroma rot, I've been running this multi user instance for a year and the worst issue I've experienced is search not working the way I'd expect it to sometimes. So far this server basically runs itself.
   • Phantasm (phnt@fluffytail.org)'s status on Friday, 08-Nov-2024 23:04:12 JST Phantasm

     in reply to

     • david
     @nyanide @david @lukyan The vast majority of Pleroma DB "rot" and issues can be summed up by two words: skill issue
     DB bloated with relay activities? Delete them.
     DB running slow and bloated? Repack it.
     
     If people neglected self-hosted Mastodon instances like Pleroma ones, Mastodon would probably also encounter a lot of similar issues like Pleroma does.
      and nyanide :nyancat_rainbow::nyancat_body::nyancat_face: like this.
   •  (mint@ryona.agency)'s status on Friday, 08-Nov-2024 23:06:27 JST 

     in reply to

     • Phantasm
     • david
     @phnt @david @nyanide @lukyan Unironically. For quite a while I had performance issues, turns out they were caused by a third-party patching adding scrobbles to profile info, resulting in DB scan basically every post.
     nyanide :nyancat_rainbow::nyancat_body::nyancat_face: likes this.