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