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
Is this a UI / front end issue? Use the lemmy-ui repo.
Issue Summary
Federated NSFW communities are not discoverable via the "Communities" tab
Steps to Reproduce
Open up Lemmy on an instance with NSFW enabled
Click "Communities"
Search for the name of a NSFW instance on a different instance (not in fully qualified !name@instance but rather just as name)
Note: searching this way does work for SFW communites
Observe that it does not come up
Technical details
While I do not have logs as I am only a user, I suspect it is an issue with NSFW communities not being publicly viewable without an account, however I think it would be reasonable that they should be searchable if the account you are on has nsfw enabled.
Federated NSFW communities do come up if you search their fully qualified name !name@instance
The text was updated successfully, but these errors were encountered:
I also noticed that since their 0.18.0 upgrade? it seems that https://lemmynsfw.com/api/v3/community/list has stopped returning NSFW communities. (I am unauthenticated)
The backend change to allow listing of these is implemented in #3363
This is nowa UI issue - We need to add a toggle on the community list page "Show/Hide NSFW" - With the default to whatever the user has configured (or false if they are logged out)
Issue Summary
Federated NSFW communities are not discoverable via the "Communities" tab
Steps to Reproduce
!name@instance
but rather just asname
)Technical details
While I do not have logs as I am only a user, I suspect it is an issue with NSFW communities not being publicly viewable without an account, however I think it would be reasonable that they should be searchable if the account you are on has nsfw enabled.
Federated NSFW communities do come up if you search their fully qualified name
!name@instance
The text was updated successfully, but these errors were encountered: