WolfGang Senizen

Depending on the whole external accessing of LSD this might not be so necessary, but a function I'd like to see would be llRezObjectWithData(object,pos,vel,rot,param, ["key1","val1","key2","val2"]); Would be useful to rez a configured object, rather than the current, rez, wait for event, and handle messages to pump config into rezzed item. Also, that maybe read write and delete should have been overloaded with a list instead of adding protected versions of the functions, allowing for easy future expansion without more functions requiring multiple variations, e.g. llLinksetDataWrite(key, value, [LSD_PASS,"secret", LSD_PUBLIC, TRUE]); The same for read/delete obviously... (though some options may not apply for all) Instead of exponentially more new functions in the future.... with the current scheme if the scope were to be increased. llLinksetDataWrite(key, value); llLinksetDataWritePublic(key, value); llLinksetDataWriteProtected(key, value, pass); llLinksetDataWriteProtectedPublic(key, value, pass); Could also be further expanded to accept a parameter like LSD_TARGET_ID to allow reading a remote object in the future, with or without pins or whatever is decided (but pins seem superfluous to me given we have passwords already), though some form of secondary functions for that may be more on form with the key being the first proper argument, not a parameter in the list.

I asked my friends this, because I couldn't think of one. Apparently some of them use it to keep track of when they friended somebody, they check the acquired date on the calling card, and it tells them, You friended this person on 2019/01/25 or so. As that's about the only way they'd end up with the calling card.