| Technical Help Discuss technical support issues here. |
| |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #1 (permalink) |
| Evil Dolly ![]() ![]()
Latexified
| PG protection: search and teleport I've actually just asked Chalice for some thoughts but I think this is urgent and of bigger interest, so I would ask all of you for feedback. There is this big mess about the PG filtering http://jira.secondlife.com/browse/VWR-12977 and we had some long discussion in Plurk http://www.plurk.com/p/qsuo5. Please read that, there are a lot of very good arguments. This here is about a technical implementation only, LL objects the idea of filtering PG for some unclear reasons and I as others are afraid the issue goes down the same drain as openspaces/homesteads. The only way to prevent that is to react fast and provide that feature in a way LL can not ignore The idea is to create some protection feature that would: 1) filter search results based on a selection checkbox [ ] PG [ ] Mature [ ] Adult (difficult due to usage of server based html search, Rika had the idea of putting some greasemonkey scripts into the built in mozilla browser) 2) save the last location and check it against the one you logon next time if it is not the same / not PG 3) checks TP locations to have the same rating and give a warning before TPing from Adult to PG If you would like to contribute, have ideas or feedback, please post them here. Something has to be done fast to prove LL wrong and force them to implement such filtering into 1.23 before it becomes publically available and people start getting ARed and banned. Thanks! Boy
__________________ Cool Viewers for Virtual Worlds: http://my.opera.com/boylane Be plurked: http://plurk.com/BoyLane/invite |
| | |
| 2 Users Said Thanks : |
| 1 User Agreed: |
| | #2 (permalink) |
| The Purple ![]() ![]() ![]() ![]()
Kinda at work. Somewhat.
Join Date: Dec 2007 Location: Somewhere purple, Germany
Posts: 3,096
My Mood: | As I noted, the search results already have a pg, mature, and adult checkbox in the newest client code, so weeeeee! as for 2 and 3, they basically both need to make use of the search, the web-search in the case of 2), the client-based internal query about a sim in the case of 3), and both need to delay the login and/or TP until that info is grabbed. I think 2) might be the most complex to implement.
__________________ "Have you ever noticed that anybody driving slower than you is an idiot, and anyone going faster than you is a maniac?" - George Carlin |
| | |
| 1 User Said Thanks: |
| | #3 (permalink) |
| MS: Main Landscaping ![]() ![]()
always in need of coffee
Join Date: Aug 2008 Location: US
Posts: 419
SL Join Date: Septemper 06'
Business: MS: Main Landscaping | I hope people remember and take into consideration that many who want this implemented are not asking for it because they want to block PG content forever. It's a very important feature that will save not only residents, but also LL time and effort when it comes to abuse reports. I don't post here too often and definitely not to promote my blog, but I did a post as to why this feature is important to me. I live life in SL basically in a PG sort of way. I don't have sex, I don't run around with bit parts showing and I spend most of my days at the shelter. However, there are times I'm filming that requires non-PG acceptable attire. It is important for me and should be for others to self block PG along with adult content so we don't offend even by accident due to sim crashes, griefers sending us flying, etc and then have to prove our way of an AR or take the warning and hope it never happens again so our record remains as clean as possible. here is my link for those interested in reading it: Adult Content, PG land and Skins that look like Clowns. It’s JIRA TIME! « Misty is Foreverlost (misplaced the map again!) Please vote. |
| | |
| 1 User Said Thanks: |
| | #4 (permalink) |
| Member ![]()
Lullin' at yer damn dirty cat
| I'd like to point out that SEARCH in 1.23 DOES allow you to untick the box and eliminate PG returns from search. But, this is NOT the same as allowing you an option whereby that option is grayed out (if you wish) so you do not accidentally search with it and teleport to a location when you may be wearing clothing or a tag or any number of objects that may be inappropriate for that region. In the opposite direction, Adult and Mature tickboxes ARE grayed out if you have selected NOT to view that content. Additionally, UNLIKE receiving a teleport to a Mature or an Adult region where you are prompted that you are entering an area where you may view content that you may not wish to view, there is no prompt or warning whatsoever that you are teleporting away from a mature or adult region where what you are wearing might result in an abuse report being filed against you because it has been deemed inappropriate for PG areas. No one should run the risk of placing their account in jeopardy simply because they were tired, distracted, mis-clicked or received a teleport from a friend who just happened to be in a PG area. The addition of a feature that allows residents to block PG areas simply allows residents to act responsibly so they do not inadvertently present content that has been deemed inappropriate in those areas. It is a sane and rational request that furthers the goals of the guidelines set for PG areas while allowing residents an option to respect those guidelines and avoid putting their accounts at risk. |
| | |
| 1 User Agreed: |
| | #5 (permalink) | |
| Evil Dolly ![]() ![]()
Latexified
| Thanks Chalice, I really haven't touched 1.23 code myself but I will very soon. The PG checkbox available in search is the only logical thing that makes sense, so I guess we can remove 1) from the list. This is already a major step foreward. And completly inconsistent to what the Lindens that commented in Jira said that this would be impossible to implement in a recent viewer. They should really ban incompetent marketing (?) folks from posting . Shame on you Lindens!2) This was said to be taken care of by LL, of course by the marketing folks again. We can not trust them, so this remains a major problem 3) This hopefully is easy to implement. I really need to get my hands on the 1.23 code ![]() Quote:
| |
| | |
| 1 User Said Thanks: |
| | #7 (permalink) |
| The Purple ![]() ![]() ![]() ![]()
Kinda at work. Somewhat.
Join Date: Dec 2007 Location: Somewhere purple, Germany
Posts: 3,096
My Mood: | Hmmh. This is news to me..that the viewer does this, I mean. Interesting. Depending on how much of that is done viewer-side, it should be easy to implement the same thing if TPing to a PG place. |
| | |
![]() |
| Thread Tools | |
| Display Modes | |
| |