You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Did you check to see if this issue already exists?
Is this only a single bug? Do not put multiple bugs in one issue.
Is this a backend issue? Use the lemmy-ui repo for UI / frontend issues.
Summary
After the update to 0.19.0, fetching a community from a different instance no longer retrieves the 10 newest posts. I suspect that this is not on purpose as it is not described in the release notes.
For example, I have fetched the community "icebergs" from lemmy.zip (which is running v.0.19.0) into lemmy.ml, and no posts have been fetched: https://lemmy.ml/c/icebergs@lemmy.zip
Steps to Reproduce
Find a community from a different instance that has not previously been seen by your instance
Fetch the external community by searching for it from your home instance, and subscribe
See that no posts have been retrieved
Technical Details
I have tried to follow the logs both when fetching a different instance's community and when using a different instance to fetch one of my communities, but I have not noticed any specific error.
Version
0.19.0
Lemmy Instance URL
No response
The text was updated successfully, but these errors were encountered:
Requirements
Summary
After the update to 0.19.0, fetching a community from a different instance no longer retrieves the 10 newest posts. I suspect that this is not on purpose as it is not described in the release notes.
For example, I have fetched the community "icebergs" from lemmy.zip (which is running v.0.19.0) into lemmy.ml, and no posts have been fetched: https://lemmy.ml/c/icebergs@lemmy.zip
Steps to Reproduce
Technical Details
I have tried to follow the logs both when fetching a different instance's community and when using a different instance to fetch one of my communities, but I have not noticed any specific error.
Version
0.19.0
Lemmy Instance URL
No response
The text was updated successfully, but these errors were encountered: