Conversation
Notices
-
Ok, what i've found so far:
- @simsa04 @lnxw48a1 and my own account show webfinger errors in the logs.
- Test to check if a cascading threat arrives at gnusocial.cc: https://gnusocial.net/url/5608193. It works fine.
- I'm starting to think that the "only" problem here is the webfinger one, which fails from the second post of a cascading thread (and with individual posts, randomly).
What's left to do:
- Check if cascading threads arrive from a GS account with no previous webfinger errors to another GS, Mastodon and Pleroma (probably tomorrow).
- If that works fine, try to narrow the webfinger errors, file a bug report and hope for @diogo has a clue about this 🙏
-
Ok, sorry for the delay, summer makes everything harder...
- Test with cascading thread, originating from an account with no webfinger errors:
❶ GS thread: https://gnusocial.net/url/5616305
❷ Pleroma thread: https://gnusocial.net/url/5616306
➌ Mastodon thread: no thread, just first post. Besides, i don't know where to pick the link to it...
- I did a "resub-feed.php" (from OStatus scripts plugin) of @lnxw48a1, which renewed the info about his profile.
-
At this point, given that an account from gs.net can send threads to other GS and Pleroma nodes, i'm wondering if:
- There's a bug in Mastodon that prevents GS threads from arriving, and/or i don't know how Mastodon works.
- The three accounts having webfinger issues were @simsa04 @lnxw48a1 and mine, because we were talking over OStatus.
May i ask, @lnxw48a1 if you plan to upgrade to 2.0 alpha and enable ActivityPub soon?
-
1) Ok.
2) At this point, i think the problem lays in using OStatus (which is the only protocol federati is using), hence my question to Walt.
3) Ok.
Not sure about self-@ (i didn't do that in any of my tests), but ok.
-
Thanks, yes, i had read it. What i'm not sure about is if executing the script i've said before has made the trick between your two tests...
-
Sure, go for it! Thanks!