Conversation

Notices

1. tekk (tekk@social.tekk.in)'s status on Monday, 06-Nov-2017 23:50:01 EST tekk
   Alright, so...does #social *require* salmon now? I did a successful PuSH subscription to my up server from Social, but when Social gets a new notice from its callback to my up server it says it ignores it because it's an inactive feed in the "subscribe" state.
   1. lnxw48a1 (lnxw48a1@nu.federati.net)'s status on Tuesday, 07-Nov-2017 00:29:30 EST lnxw48a1

      in reply to
      @tekk I see those frequently. I'm pretty sure I saw a post somewhere in which someone did a magic SQL incantation that made those inactive subs active, but I've not been able to find it again. !gnusocial
      1. tekk (tekk@social.tekk.in)'s status on Tuesday, 07-Nov-2017 00:56:30 EST tekk

         in reply to
         @lnxw48a1 It's not horribly reasonable to be like "Hey, if you want to follow someone using up, then just remember to tell your instance admin to drop into mysql and enable the subscription" though :(
         1. lnxw48a1 (lnxw48a1@nu.federati.net)'s status on Tuesday, 07-Nov-2017 01:02:00 EST lnxw48a1

            in reply to
            @tekk True indeed. Many subscriptions go inactive when it is time to renew them each 30 days, but I suspect they'd start working if I knew the SQL to emit. It could possibly happen if bandwidth is constricted and subscriptions / renewals time out.
            1. lnxw48a1 (lnxw48a1@nu.federati.net)'s status on Tuesday, 07-Nov-2017 01:08:51 EST lnxw48a1

               in reply to
               Not that this solves your issue. It would help me solve mine.