Conversation

Notices

1. Maiyannah Bishop (maiyannah@plateia.org)'s status on Monday, 01-Jan-2018 23:20:28 EST Maiyannah Bishop
   Gonna be honest, 99% of the reason I keep this instance is up is for all the bitching about Mastodon I do occasionally take a hack at trying to fix how it's fucked up federation again.
   
   But it's been an uphill battle.  For each mastodon federation problem that I fix, there's 10 more that are just as bad to fuss with. And sometimes the fixes that would be easy would break federation with other things.
   
   This is a lot of the reason I get pretty sour about Mastodon, personal experiences aside.
   
   I'll probably relaunch plateia when the Diaspora federation is complete and let it re-network.
   1. Maiyannah Bishop (maiyannah@plateia.org)'s status on Monday, 01-Jan-2018 23:25:25 EST Maiyannah Bishop

      in reply to
      Incidentally, there are proper ways (ie a script) to retire and relaunch a node that you can do, as long as the node is still operating of course.  So you can just do that to salt the earth and it should be fine as long as it federates.  If it doesn't, GS/pA should correct data if there's issues.  No idear about Hubzilla or Friendica or Mastodon in that regard though.
      1. mike (mike@loadaverage.org)'s status on Wednesday, 03-Jan-2018 18:39:55 EST mike

         in reply to
         Hubzilla is completely self-healing in its own network (with about a 24 hour granularity), but for other networks it only probes and corrects once a month because probing for all the different protocols involves a fair bit of resources.
         
         Diaspora will never correct "basic communication data", caching it forever. That's why my home site can only talk to newer Diaspora instances; as it was once a Friendica site and they are still holding the old public key for my webfinger address. Hopefully I'll be able to correct this by sending an account_migrate message once they finally make that work.
         
         GS also holds basic comms data forever from my experience; hopefully this has been fixed but I haven't seen it from here. We changed our feed url slightly a year or two ago and many GS sites still insist on using the old one, so it seems pretty slow to correct.
         
         I can't comment on Friendica or Mastodon.
         1. Maiyannah Bishop (maiyannah@plateia.org)'s status on Wednesday, 03-Jan-2018 18:51:18 EST Maiyannah Bishop

            in reply to
            @mike Feeds should self-heal in GS when they renew the hubsub since it basically deletes and recreates them when it renews it.  But GS has a bug where it can get stuck on old ones, that got fixed a bit ago.  A lot of GS instances are pretty dated though.
            
            Mastodon basically keeps hubsubs forever and ever though unless a renew request is explicitly set so yeah.
            1. Maiyannah Bishop (maiyannah@plateia.org)'s status on Wednesday, 03-Jan-2018 19:06:18 EST Maiyannah Bishop

               in reply to
               @mike The bug incidentally was that feeds placed in an 'inactive' state would end up stuck such that they couldn't be corrected.
               1. mike (mike@loadaverage.org)'s status on Thursday, 04-Jan-2018 02:14:39 EST mike

                  in reply to
                  Yeah, that sounds like a perfect match for what I experienced. Thanks. We've got two feeds - a legal one and an OStatus one with fixes for a lot of quirks and bad behaviour by GS and mastodon. Some older GS sites are stuck with the legal feed and they can't deal with it so a lot of content ends up being buggered on their side. We can't fix it because we can't get them to use the feed which was butchered especially for their consumption.