Can we have some Clarity on how the NSFW tags work? In the old CCHost OCAL there was a NSFW checkbox on upload AND you could add tags later. The end result was that a checkbox was activated (binary 1/0) AND a tag could be there as well. How does the new OCAL NSFW tagging work with Aiki? I'd like to see the display nsfw toggle in the authors "preferences" or perhaps in the manage clipart page. Ciao Chovynz <div class="gmail_quote"> On Sat, May 1, 2010 at 3:49 PM, chovynz <<a href="mailto:chovynz@gmail.com">chovynz@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> That too. Do you need model releases for people? if so that's ... pretty restrictive! How would we provide for that on OCAL? A secondary upload area for "people" clipart, so that anyone can see the release form, and be sure that the image they use IS PD? How far does it extend? How does this apply to vectorised people already on the Database? (e.g. Jon's head. Obviously Jon can release himself, but some other cliparts can't be "proved" in this way.<div><div></div><div class="h5"> <div class="gmail_quote"> On Sat, May 1, 2010 at 3:27 PM, Greg Bulmash <<a href="mailto:oneminuteinspirations@gmail.com" target="_blank">oneminuteinspirations@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> I'm actually more concerned at this point whether the photo he vectorized was one he shot and whether he has the proper model releases to put the image into the public domain in this way. <div><div></div><div> On Fri, Apr 30, 2010 at 7:46 PM, Francis Bond <<a href="mailto:bond@ieee.org" target="_blank">bond@ieee.org</a>> wrote: > G'day, > > we should perhaps also try to add more NSFW tags, and mention them in > the documentation. If you click on the "woman" tag, there are quite a > few that I would consider NSFW. I agree with John that we should keep > them, but I would be much happier if there was a way of not showing > them (and probably have it on by default so that our site is a little > more school friendly). > > Librarians could start off by tagging these as soon as possible. > > On 1 May 2010 10:33, chovynz <<a href="mailto:chovynz@gmail.com" target="_blank">chovynz@gmail.com</a>> wrote: >> I agree with what you said. However in this case, I think it would be >> appropriate to delete. >> NSFW filters simply is not working correctly, and (based on historic >> performance) it could be another month before Whoever it is who can do >> something about it, can get to doing it. >> >> Librarians cannot do anything else. (We can't even delete.) I tried to hide >> it, but since it is still there, there's nothing further we librarians can >> do. It's over to Bassel or Jon (or whoever else has DB access) to do >> something. (Or if there is another solution I'd be glad to hear it.) >> >> And the NSFW issue has been on the bug tracker since before Aiki changeover. >> Admittedly with a different framework, but IMO it would be good to have this >> sorted out ASAP. I don't feel comfortable sharing OCAL with schools until it >> is sorted. >> >> Cheers >> Chovynz >> >> >> On Sat, May 1, 2010 at 2:24 PM, Jon Phillips <<a href="mailto:jon@rejon.org" target="_blank">jon@rejon.org</a>> wrote: >>> >>> No, we shouldn't delete it because it doesn't violate our guidelines, >>> and we have taken a pretty hard stance in the past against this type >>> of activity. With that being said, until we have NSFW filters in >>> place, I think it sounds reasonable to hide files that can't be >>> filtered out. >>> >>> But, we should make sure to file them on the bug tracker under >>> something like Add NSFW/tag filter for site. Users should be able to >>> configure their own filters and by default, we should be very >>> conservative on first visit to the site, IMO, especially on the main >>> page. >>> >>> Thoughts? >>> >>> Jon >>> >>> <snip /> >>> >>> </div></div></blockquote></div></div></div></blockquote></div>