[Bug]: Lemmy 0.18.0 no longer federates outbound with non-Lemmy instances · Issue #3354 · LemmyNet/lemmy
github.com
Requirements Is this a bug report? For questions or discussions use https://lemmy.ml/c/lemmy_support Did you check to see if this issue already exists? Is this only a single bug? Do not put multipl...

Requirements

  • [X] Is this a bug report? For questions or discussions use https://lemmy.ml/c/lemmy_support
  • [X] Did you check to see if this issue already exists?
  • [X] Is this only a single bug? Do not put multiple bugs in one issue.
  • [X] Is this a backend issue? Use the lemmy-ui repo for UI / frontend issues.

Summary

Summary

Communities on Lemmy instances can no longer be found or followed from the Fediverse outside of Lemmy. Apparently, this started with 0.18.0.

It is no longer possible to find them by searching for them, it is no longer possible to subscribe to them, it is no longer possible to see posts from them. It is still possible to post to them from outside, though.

Instances I know to be hit by the bug

Steps to Reproduce

Search for communities

Example on Lemmy’s side: the main community on sh.itjust.works which recently upgraded to 0.18.0, at which point outbound federation ceased to work. Other communities on sh.itjust.works behave the same. It has been reported that lemmy.ca has the same issue.

Example on the non-Lemmy side: Mastodon 4.1.0. The same thing has been proven to happen on Hubzilla 8.4.2, including with a community that has already been subscribed to about a week ago, prior to the Lemmy 0.18.0 upgrade on sh.itjust.works. Before Lemmy 0.18.0, searching for Lemmy communities worked on both Mastodon 4.1.0 and Hubzilla 8.4.2.

  1. Copy the URL of a community on a Lemmy 0.18.0 instance; in this example, https://sh.itjust.works/c/main.
  2. Go to any Mastodon instance. Being logged in is not required.
  3. Paste the copied URL into the search field.
  4. Hit Enter.

Expected result/result before the 0.18.0 upgrade: The main community on sh.itjust.works appears as the only search result. If logged into this Mastodon instance, the community can be subscribed to with one click.

Actual result: No search results; “Could not find anything for these search terms” instead.

Directly subscribe to communites without searching for them first

Disclaimer: This requires a Hubzilla channel and being logged into it.

The same Lemmy-side example as above will be used; the same explanations are still valid.

On the non-Lemmy side, the example is Hubzilla which does not require to search for a community to subscribe to it, just to illustrate that this doesn’t work either.

  1. Copy the URL of a community on a Lemmy 0.18.0 instance; in this example, https://sh.itjust.works/c/main.
  2. Go to a Hubzilla instance on which you have your channel. Log in if necessary.
  3. Navigate to the Connections page.
  4. Click the green Add button.
  5. In the field that says, “Enter channel address”, paste the copied URL.
  6. Click the green + button.

Expected result/actual result before the 0.18.0 upgrade: The connection is created. The connection configuring window opens so you can adjust it. The community appears amongst your connections.

Actual result: The page flicks briefly. The connection configuring window does not open. The community does not appear amongst your connections. The connection is not created.

Receive and read posts from subscribed communities

This can only be reproduced with communities which have been subscribed to prior to the 0.18.0 upgrade, but which run on 0.18.0 now. The requirement for a step-by-step reproduction would be to already have subscribed to a community which is on 0.18.0 now from an account/channel on an instance of a project that isn’t Lemmy (e.g. Mastodon). For reasons mentioned above, this requirement cannot be established currently.

Technical Details

I’m not an admin, so no access to logs here, only external observations by a Hubzilla user.

Version

0.18.0

Lemmy Instance URL

No response

Originally posted by JupiterRowland in #3354