Conversation

Notices

1. Oneesan succubus (lain@pleroma.soykaf.com)'s status on Thursday, 08-Mar-2018 07:30:20 EST Oneesan succubus
   I just merged the activitypub branch into develop, so if you run that branch, you'll get AP support with the next update.
   
   THIS MEANS THAT PLEROMA NOW SUPPORTS FEDERATION OVER ACTIVITYPUB.
   
   Before upgrading, please read through https://blog.soykaf.com/post/activity-pub-in-pleroma/. The needed migration can take a LONG time (up to a few hours, although probably just some minutes), so expect some downtime.
   
   If you experience problems or encounter bugs, please report them at https://git.pleroma.social/. There will probably be some, but we'll fix them fast.
   1. It's a me (feld@bikeshed.party)'s status on Thursday, 08-Mar-2018 08:55:22 EST It's a me

      in reply to
      @lain On my fairly beefy hardware I was seeing ~10-15 seconds for every 10k activities that needed to be modified. Not too bad. I have been on here for about 6 months and had 350,000 activities. Under 10 minutes to do the migration.
      
      It's possible this could go faster if you increased your work_mem in Postgres up from the default 4MB to ... maybe 8MB? But you might not want to keep that permanently as you will see much higher memory usage.
   2. Biggest :valve_1::valve_2: shill :flag: (hj@shigusegubu.club)'s status on Thursday, 08-Mar-2018 08:52:39 EST Biggest :valve_1::valve_2: shill :flag:

      in reply to
      @lain on sgsgb db migrations took roughly 13 minutes