Not sure where the settings actually live, so I can’t say whether this is backend or frontend, but I have been thinking that nsfw post handling could be improved.

Specifically, I’ve been thinking about (and actually been considering implementing) some new per-user settings:

• Don’t show nsfw posts from other instances in the “all” feed.
• Don’t show nsfw posts in the “local” or “all” feed at all.
• Always show nsfw posts from communities the user is subscribed to, regardless of the above two options.

Should cut down on any drama caused by someone registering on a random instance and subbing to gfur. :P

EDIT: Looking at the replies, it looks like a simple site wide toggle a-la Furaffinity might be easier to implement and more egonomic.

So, I don’t disagree with the decision to fork (especially because of the hardcoded donation URL). I am concerned about fracturing of the codebase, so I have a few questions:

• Will this fork always be a sequence of commits based on some Lemmy version, or do you expect history to diverge (git rebase vs merge)?
• Will there be an effort to upstream useful changes into Lemmy proper (a lot of the changes suggested are things that might be desirable for Lemmy in general).
• There’s a number of other communities with a desire to use a forked Lemmy version, do you intend this fork to be useful for them, or is this purely for pawb.social?

And perhaps most importantly:

• Will the name be changed from Lemmy to something else if there are significant changes.