I've been trying to follow two groups on slrpnk.net using my (main) account on hachyderm.io. The groups initially show as followed, but I get no posts in my feed. I've tried creating new test accounts, one on mastodon.social, one on hachyderm.io, to follow those groups - the account on mastodon.social starts getting posts right away.
Are there known federation issues with hachyderm.io? I've reached out to the admins on their side, they see some intermittent 503's from slrpnk.net, but not a general block.
The groups I'm trying to follow are https://slrpnk.net/c/electricvehicles and https://slrpnk.net/c/energy . I've reached to moderator ( @[email protected] before too and they weren't aware of any limitations placed.
Anyone?
Hard to say if this is a specific issue with our Lemmy instance, or some incompatibility between Lemmy and Mastodon.
Edit: it seems like hachyderm.io requires signed fetches, which we (and Lemmy in general) currently don't have enabled. It looks like it will become the default for Lemmy version 0.20 thought.
Oh, right. Is turning signed fetch on something that could be considered?
It currently requires messing with the database directly, which is a bit annoying. I think since the next Lemmy release that should enable it by default is probably coming early next year, we might just wait for that.
Since the fixes referenced in https://github.com/LemmyNet/lemmy/issues/4451 and https://github.com/LemmyNet/lemmy/issues/868 were merged, respectively, in March 2024 and February 2024, before 0.19.4 release, I'm afraid there's no UI option to enable those coming.
From what I see in migrations, if I understand correctly, https://github.com/LemmyNet/lemmy/blob/main/migrations/2024-10-29-090055_private-community/up.sql changes the default to true - this would have been part of 0.19.7 release already... and it still doesn't work for this slrpnk.net instance.
Have you tested if any other smaller Lemmy instances that likely have not enabled this manually work?
I don't see a reason why our instance should be special in that regard. So maybe it is an upstream bug?