Post 3486632 by stjohn@jank.town
 (DIR) More posts by stjohn@jank.town
 (DIR) Post #3483995 by lambadalambda@pleroma.soykaf.com
       2017-04-05T09:56:59.416464Z
       
       1 likes, 0 repeats
       
       and another one.
       
 (DIR) Post #3483996 by lain@pleroma.soykaf.com
       2019-01-28T21:34:36.696352Z
       
       0 likes, 0 repeats
       
       @stjohn vaccum analyze :)
       
 (DIR) Post #3484139 by 25001.foxhkron@cybre.club
       2019-01-28T21:39:13.728801Z
       
       1 likes, 0 repeats
       
       @lain @erroruser@example.com @lambadalambda This doesn't look right lol (wrong parent post?)image.png
       
 (DIR) Post #3484195 by kaniini@pleroma.site
       2019-01-28T21:40:19.581377Z
       
       0 likes, 0 repeats
       
       @foxhkron @lain @lambadalambda the real question is why did an erroruser show up.
       
 (DIR) Post #3486632 by stjohn@jank.town
       2019-01-28T22:41:26.476458Z
       
       1 likes, 0 repeats
       
       @lain @lambadalambda @lain Ah yeah, I tried that when I was searching for Pleroma slow DB queries (I think someone mentioned it in a ticket on GitLab), but I'm afraid it didn't do anything. I'm not intimately familiar with PostgreSQL or the Pleroma code, so I'm obliged to accept the advice of my search engine! The problem seems to have gone away on its own after I ran the latest upgrade migrations this morning. I remain mystified, but relieved all the same :P
       
 (DIR) Post #3486833 by 25001.foxhkron@cybre.club
       2019-01-28T22:55:55.778923Z
       
       1 likes, 0 repeats
       
       @kaniini @lain @lambadalambda CybreClub or Soykaf being drunk, I guess