Quote:
Originally posted by malakajoe
Still waiting. I am trying to give you what you want...an answer to your stupid aroused genital bullshit.
I gave you an answer..you couldn't read between the lines. I will further explain why it is bullshit what you write, but if you respond to my post about your "most advanced" website cookie crap.
|
It's not just about cookies.
And the controls which I should be working on now but I am taking the time to respond to your questions are currently broken.
They are broken because I was creating a "community" for a particular supplier that cancelled. The supplier requested anonymity and that will be honored.
Anyways ...
It's a combination of things that will be reactivated hopefully this weekend if I stay out of GFY.
#1: The website uses self expiring URLS so if a Parent goes into the site and a child uses the computer later - the pages will not be accessable again. There is only one way into the website and that is from the homepage.
#2: If the cookies were set - then deleted or tampered with - then the Parent was warned when they logged in again.
#3: The starter Table of Contents was customizable and articles could be blocked. You did/do that by dragging the left window frame to the right and clicking on the delete link.
#4: Graphics could be turned off/on.
#5: Background graphics could be turned off/on.
#6: Popups could be turned off/on.
#7: Advertising could be turned off/on.
#8: Content from the Archives could be added to the starter Table of Contents (TOC).
#9: External links to other websites could be added to the Archives which could be added to the Parents TOC.
#10: Invidividual videos linked in the articles could be blocked.
#11: The website was rated with ICRA.org to have the most extreme content rating possible so JUST entering a password into 95% + of web browsers completely disabled the website.
side note: at one time I tried to code my website controls to work with RASCi / ICRA.org controls so that if "explicit" nudity was blocked but not "partial" nudity or if slang/curse words were blocked then those specific pages were blocked - AND - not others. I found it too complicated and web browser buggy/specific
#12: Changing controls and changing them back informed the member by email if they decided.
#13: At one time if anyone logged in - you were emailed.
#14: Links to explanations of background images could be disabled.
And there is probably more I am just not thinking about right now.
I've tried lots - and - done lots.