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?
@andstatus [ESP] Te damos la bienvenida a gnusocial.net. Varias cosas:
- Es NECESARIO responder a este mensaje para levantar el aislamiento inicial de tu cuenta. - Si no lo has hecho, configura un correo electrónico para recibir notificaciones. Sólo las cuentas con el correo verificado podrán publicar. - Las cuentas sin actividad y que continúen aisladas serán borradas al cabo de un mes. - Puedes consultar la documentación en el siguiente enlace: https://gnusocial.net/url/2660107
[ENG] Welcome to gnusocial.net. Several things:
- You MUST answer to this notice in order to get your account initial sandboxing uplifted. - If you haven't done it yet, set up an email address to get notifications. Only accounts with a confirmed email will be able to post notices. - Sandboxed accounts without activity will be deleted after one month. - You can read the docs in the following link: https://gnusocial.net/url/2660107
- @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 🙏