secondlife / jira-archive

2 stars 0 forks source link

[BUG-216149] llGetObjectDetails() constant OBJECT_REZ_TIME #3602

Open sl-service-account opened 6 years ago

sl-service-account commented 6 years ago

Information

flag desc
- - -
OBJECT_REZ_TIME returns unix time object was rezzed



# Why is this feature important to you? How would it benefit the community?
Creation time was already pushed through in server release 17.08.11.328159, and while it's a nice addition to have, there's not many uses for it outside of catching copybotters, and verifying the legitimacy of a single object in say a closed source meter system, which is nice although somewhat reliant on outside communications
Rez time is already accessible by the viewer via estate menu, and being able to get this info would open up a myriad of administrative capabilities within systems regarding spam detection and reducing instances of scripted grief.
At the moment, unless you rely on a rapidly repeating sensor for collecting the first pass an object was detected, there's no reliable way of getting an object's rezzed time via scripted methods.
This is related to BUG-9666, I'm just requesting that OBJECT_REZ_TIME get pushed through because it would be incredibly useful, on par with the OBJECT_REZZER_KEY in terms of possible functionality, allowing the collection of rez time with drastically lower script time overhead compared to existing systems.

# Related Issues
BUG-9666
BUG-3958 |

Attachments

Links

Related

Original Jira Fields | Field | Value | | ------------- | ------------- | | Issue | BUG-216149 | | Summary | llGetObjectDetails() constant OBJECT_REZ_TIME | | Type | New Feature Request | | Priority | Unset | | Status | Accepted | | Resolution | Accepted | | Reporter | Dread Hudson (dread.hudson) | | Created at | 2018-04-22T00:32:48Z | | Updated at | 2019-06-17T16:35:32Z | ``` { 'Business Unit': ['Platform'], 'Date of First Response': '2019-05-03T12:22:58.865-0500', 'How would you like the feature to work?': '||flag||desc|| \r\n|OBJECT_REZ_TIME|returns unix time object was rezzed| ', 'ReOpened Count': 0.0, 'Severity': 'Unset', 'Target Viewer Version': 'viewer-development', 'Why is this feature important to you? How would it benefit the community?': "Creation time was already pushed through in server release 17.08.11.328159, and while it's a nice addition to have, there's not many uses for it outside of catching copybotters, and verifying the legitimacy of a single object in say a closed source meter system, which is nice although somewhat reliant on outside communications\r\nRez time is already accessible by the viewer via estate menu, and being able to get this info would open up a myriad of administrative capabilities within systems regarding spam detection and reducing instances of scripted grief.\r\nAt the moment, unless you rely on a rapidly repeating sensor for collecting the first pass an object was detected, there's no reliable way of getting an object's rezzed time via scripted methods.\r\nThis is related to BUG-9666, I'm just requesting that OBJECT_REZ_TIME get pushed through because it would be incredibly useful, on par with the OBJECT_REZZER_KEY in terms of possible functionality, allowing the collection of rez time with drastically lower script time overhead compared to existing systems.", } ```
sl-service-account commented 6 years ago

Dread Hudson commented at 2018-04-25T22:10:42Z

Woo, accepted within a week! Doin some great work here my dudes!

sl-service-account commented 5 years ago

Dread Hudson commented at 2019-04-23T23:49:45Z, updated at 2019-04-23T23:50:04Z

Any updates on this? It's been almost a full year since it was accepted with no word back regarding development. The framework for this function is all already there with OBJECT_CREATION_TIME, and all of the information is already being tracked as shown by being able to fetch rez time via estate menu functions.  Do you guys need help pushing this code? Is there anything I could do to expedite the process?

sl-service-account commented 5 years ago

Kyle Linden commented at 2019-05-03T17:22:59Z

Hi Dread,

Our product team drives feature development in line with our business goals. There's no way to predict when new feature request will be added to the roadmap.

One thing that may help is providing more concrete use cases for how this feature could be beneficial as well as how it may be abused.

Thank you!

sl-service-account commented 5 years ago

Dread Hudson commented at 2019-06-11T01:47:56Z

I'm not sure in what situation it could be abused, and I thought the utility of it was already explained in the Jira itself?

To sum it up, Being able to fetch OBJECT_REZ_TIME alongside the already outstandingly useful OBJECT_REZZER_KEY would be a lot more of a surefire way to handle anti-grief and spam filters for any and all systems that handle users rezzing out objects to interact with other objects, which would extend the lifetime of these systems by helping close exploits in them, which will prolong user retention and interest in them. People don't always stick around when their favourite roleplay meter is getting griefed, they get fed up and go do something else.

The case I made in lay-mans terms is this : Look at all the user created systems within secondlife that have problems with people trying to game their systems to get a leg up over other people, and how that drives people away because they don't want to deal with that, and look at all the twists and turns the developers have to go through to keep them from doing that. This would be another tool to stop people from being hyper dweebs, by closing one more vulnerability people can use to exploit user created systems, we can extend the lifetime of said systems, lessen the likelihood of them being exploited, and prolong user interest and retention in these systems.

The fact that this change is literally 2 tweaks to a function that already exists, ie OBJECT_CREATION_TIME , and that there's two other feature requests, one of which was already accepted (and leading to the implementation of OBJECT_CREATION_TIME - https://jira.secondlife.com/browse/BUG-9666), makes it kind of baffling that it hasn't been done already. I'm willing to drive down to San Francisco from Sacramento and do this for you on my next day off free of charge if you guys would like.

sl-service-account commented 5 years ago

Kyle Linden commented at 2019-06-17T16:35:33Z

I updated the internal issue with your latest comments. Thanks!