New values for identity/age verification in llRequestAgentData?

Does anyone know what the options will be to return the 'identity/age verified' information using llRequestAgentData? I looked through the wiki and jira and have not found any information there.

integer iTest = -1;

default 
{
    touch_start(integer num_detected) 
    {
		a++;
		llRequestAgentData(llDetectedKey(0), a);    }
    dataserver(key queryid, string data) 
    {
        llSay(0, "results = " + data);
    }
}

Tested with this script and went up to "16". The only integers that will return results are still 1 - 4 & 8.

Translation: No you can't get that information using llRequestAgentData yet.

Which means it shouldn't be available through script either or it would be pointless to not show it on your profile.

That would fit with the existing values you can request...

DATA_ONLINE 1
DATA_NAME 2
DATA_BORN 3
DATA_RATING 4
DATA_PAYINFO 8

After looking at the new release candidate it appeared they were possibly mixing the new values into the PAYINFO return. My profile shows 'Payment Info Used - Not'. I assume the 'Not' was the beginning of not verified or something like that. I seem to remember them saying that the IDV would replace the payment info, so based on the way the data was displayed I was thinking that maybe the PAYINFO was going to be expanded to return a wider range of values that it used to.

Thats interesting. I did not realize that. I wonder why they are bothering to have the client display it when no one is supposed to see it. I sure won't need to see it in my own profile. Maybe they think we need it there in case we can't remember whether we are verified or not.

I'd also like to know why it's being hidden. People who make vendors for adult products would probably like scripted access... (edit: or, rather, people who use vendors for adult products would probably like the vendors to allow them to say "this item's for verified-only accounts.)

As I understand it.. it's so that you can't look at someone else's profile, see that they are age verified, and from that fact conclude "ah, he/she must be involved with porn." (After all, why would they have bothered verifying otherwise?) If that happened, there would be a lot of pressure on people _not_ to age verify, or to make alts to become age verified.

Of course, you can see that someone else is verified by seeing them on an adult parcel, but then they are seeing you there at the same time.

The client isn't supposed to display it, so I suspect the "not age verified" message will disappear entirely. Vendors of adult items will have to be on adult land so that issue will be moot.

They might put it into PAYINFO, afterall PAYINFO is a bit field.

seems kind of conflicting, according to LL's own statement, the info won't be readable by other residents, and they seem to be pushing the theory that if you have content that only verified accounts should access then it MUST be on land that restricts unverified accounts (which is done through the parcel controls not scripting)....

... on the other hand, if you look at a persons profile, inworld right now, you'll see messages like "Payment info used, not" with the last part being cut off (something like notverified or somesuch)

personally I think it'd be more effective to allow it to be accessed via script, instead of borking around with subdividing parcels, although this could be seen as a move to clear up 'mature' results in the search engine... since it'll be tied to the land it's on, a search for content that doesn't include mature items will then only return parcels without the new flags...

atm it doesn't seem that any of this info is actually being used by the server, newly flagged parcels are still open access etc.. and the display of the 'not' segment may just be an artifact of the new client, and not something being fed from the server