I'm going to say I had a bit of a laugh here imagining Little Timmy making an account just to view some pixel boobies
I'm not sure if you're asking this rhetorically, but I think the best, easiest course of action would be using cookies - certain other image-hosting websites do this and I think this is probably enough to cover your bum. If there turns out to be issues that stem from it (i.e. angry Christian moms sending colorful emails to Dazz about Little Timmy looking at pixel boobies) then you may want to consider requiring an account to view it.
This would also be best as you can pretty much just...visit TSR at a public place without worrying about seeing NSFW content.
Even better would be to, on a per-profile basis, disable thumbnails for NSFW content by default and enable them only through going to your site profile and checking a box like "Enable thumbnails of NSFW content". Clicking this would require the user to go through a blow-by screen saying "Yes, let me turn on NSFW thumbnails".
Having both options, while initially seeming redundant gives users two lines of defense against those pesky pixel boobies: The cookies (which work for the first sign-in on ANY machine, and is the first line of defense if you forget to unclick "Enable NSFW") and the "Enable" button on the profile (which protect against angry moms)
(and I know how much you dislike redundant features Petie I'm sorry but really dude hear me out on this)
the best option would be adding a third feature; one that gives you a high five for having two excellent lines of defense against getting fired over cartoon honkers
y'all gotta stop thinking of them as "restrictions" and instead as "deterrents"
(11-09-2017, 10:46 AM)Petie Wrote: Do we blanket hide NSFW data and require an account to view it? Do we not tie it to an account and instead use a cookie (like view mode)? Do we continue showing it with the filter when you're logged out and ignore the new system entirely? And automating this change when a user turns 18 is far easier said than done too unless your intent was to not be able to opt out if you're under 18 but in that case, people will just make new accounts.
I'm not sure if you're asking this rhetorically, but I think the best, easiest course of action would be using cookies - certain other image-hosting websites do this and I think this is probably enough to cover your bum. If there turns out to be issues that stem from it (i.e. angry Christian moms sending colorful emails to Dazz about Little Timmy looking at pixel boobies) then you may want to consider requiring an account to view it.
This would also be best as you can pretty much just...visit TSR at a public place without worrying about seeing NSFW content.
Even better would be to, on a per-profile basis, disable thumbnails for NSFW content by default and enable them only through going to your site profile and checking a box like "Enable thumbnails of NSFW content". Clicking this would require the user to go through a blow-by screen saying "Yes, let me turn on NSFW thumbnails".
Having both options, while initially seeming redundant gives users two lines of defense against those pesky pixel boobies: The cookies (which work for the first sign-in on ANY machine, and is the first line of defense if you forget to unclick "Enable NSFW") and the "Enable" button on the profile (which protect against angry moms)
(and I know how much you dislike redundant features Petie I'm sorry but really dude hear me out on this)
the best option would be adding a third feature; one that gives you a high five for having two excellent lines of defense against getting fired over cartoon honkers
y'all gotta stop thinking of them as "restrictions" and instead as "deterrents"
![[Image: 57d2BGH.png]](http://i.imgur.com/57d2BGH.png)