This way one can blur NSFW on their main they’d use in public, and can have NSFW unblurred on their NSFW alt. account. I know of several Lemmy apps that already do this.
I second this.
I’m currently using multiple apps for multiple accounts, since this multi account stuff is not really optimal in any app I’ve tested so far. Account-specific NSFW would certainly help.
This would be nice, but I think it would also be nice to have a setting where it blurs NSFW on your main feed, but once you go into a community it’s unblurred.
This has been implemented already and will be available in the next release
That’s awesome to hear! Thanks!
That’s a good feature. I think Sync has both these features.
Something I suggested once for the reddit app I used to use that for some reason got downvoted in their sub was an option to make the NSFW filter time or location-based.
Everyone of course uses Lemmy differently. Personally I try to keep all of my NSFW content on a separate account, and on my main I pretty much exclusively stick to communities I’m subscribed to, so I don’t have to worry about too much crazy shit coming through.
That said, something that’s a bit NSFW will sometimes slip by in a normally SFW community, for example, maybe an artsy nude picture will come up in a photograpy community, or a table saw injury that’s a bit gory in a woodworking community. Having NSFW maybe automatically turn off during my working hours, or automatically turn on when I’m at home and off when I leave would give me a little peace of mind about those odd things that slip through without me having to remember to specifically turn it off/on.
Not something I’d consider to be a super high priority, but it’s something that I’d consider to be useful and I have a hunch some others would as well
That seems a little overkill, especially since it’s a feature I doubt very many people would use. Just having it separate for each account would be sufficient, require less processing power and battery, and less time to code.
This is already a feature in connect, so it shouldnt be hard to implement.
