Conversation

Notices

1. Mike Macgirvin (mike@macgirvin.com)'s status on Sunday, 22-Oct-2017 07:15:46 EDT Mike Macgirvin
   Sorry about this simple question but the connection from diaspora to hubzilla doesnt work.
   
   Protokoll is enabled an postings are postet proper on diaspora site.
   
   Any hints?
   1. Mike Macgirvin (mike@macgirvin.com)'s status on Sunday, 22-Oct-2017 08:12:18 EDT Mike Macgirvin

      in reply to
      It works in current RC (i just checked). You can simply git checkout 2.8RC or wait until it's released (possibly next week).
   2. Mike Macgirvin (mike@macgirvin.com)'s status on Sunday, 22-Oct-2017 14:51:05 EDT Mike Macgirvin

      in reply to
      you have to enable the protocol  at the administration level,
      but also at user level,
      in practice, enable 2 times.
   3. Mike Macgirvin (mike@macgirvin.com)'s status on Sunday, 22-Oct-2017 15:33:11 EDT Mike Macgirvin

      in reply to
      It has been working correctly to my knowledge. Please note that the protocol must be enabled by every member who wishes to use it, as the channel cloning feature and location independence will not work correctly with Diaspora connections.  See settings/featured (Diaspora Protocol Settings), tick the box to turn the connector on for this channel and submit.
      
      If you've already done this and are still encountering issues, we need a better description of what functionality isn't working correctly in order to track it down.
   4. Mike Macgirvin (mike@macgirvin.com)'s status on Sunday, 22-Oct-2017 16:36:21 EDT Mike Macgirvin

      in reply to
      @Mike Macgirvin i had a private conversation with @Holger this afternoon.
      He could not connect from diaspora to hubzilla and seeing some Fehler im Log: "diaspora_decode: mod-diaspora: Could not retrieve author key" errors in the log. This was on RC branch.
      I could not reproduce this on my hub but than this is an older one... It might be an issue with new installations... I am afraid this will need some investigation...
      
      Anyway, Holger seems to be back at master branch now here:Embedded content
      https://allnet.hfrc.de/channel/holger
      
   5. Mike Macgirvin (mike@macgirvin.com)'s status on Monday, 23-Oct-2017 06:08:49 EDT Mike Macgirvin

      in reply to
      @Mike Macgirvin it does not work with a fresh installed for some reason. Connecting from diaspora to hubzilla ends up with:
      2017-10-23T09:33:53Z:LOG_INFO:3b5f3de55a25e15d92717508c139e812:Wfinger.php:31:init: webfinger: acct:hztest@hub.mariovavti.com
2017-10-23T09:33:53Z:LOG_INFO:25c7650c9759db725e5d08593ed079a2:Hostxrd.php:11:init: hostxrd
2017-10-23T09:33:53Z:LOG_INFO:7d7d5b66041fd9ec54e8f1e86e4601c0:Xrd.php:13:init: xrd: acct:hztest@hub.mariovavti.com

      
      while on my old hub with same code it works as expected :astonished:
   6. Mike Macgirvin (mike@macgirvin.com)'s status on Monday, 23-Oct-2017 15:08:07 EDT Mike Macgirvin

      in reply to
      Whenever I see something fail with a '.well-known' service I have to wonder first if LetsEncrypt has done something new to break it. I do have a check which looks for .well-known/.htaccess and moves it if it appears (as it makes all .well-known services except acme-challenge "deny all" - including our own). I don't know (at all) what they do for nginx; but presumably they attempt something similar.
      
      [edit: and they keep changing the ways that they break .well-known. It's an arms race to keep our services working]
      
      [edit2: in this case it turned out that some new changes and "requirements" were added to the Diaspora protocol without telling anybody or documenting them adequately. I caught one of them because it triggered an alert in my email, but the second one flew under the radar.]