OSSL notecard functions and threat level

Creating scripts
User avatar
Min Tigerpaw
Posts: 220
Joined: Sun Mar 24, 2013 3:52 pm
Has thanked: 325 times
Been thanked: 157 times

Re: OSSL notecard functions and threat level

Post by Min Tigerpaw » Fri Aug 08, 2014 8:21 pm

Did some checking of the os Notecard functions in the Metaverse: osGetNotecard (threat level very high) and osMakeNotecard (threat level high)
Both are used in my MT Collegeboard to save and call written and drawn content:
If I rezz the board in sandboxes of osGrid or Germangrid the board is fully functional -
I can save complex board content to a notcard inside the board with osMakeNotecard and I can call any notecard from inside the board will osGetNotecard. Same as in Kitely in my regions.

Seems the threat-level is not causing the described restrictions in some major grids. I know that it does so in Metro though. Will continue testing and vote for removing such restrictions as much as possible. As Handy wrote - it is a real nuisance not to be able to store data related to an object in-world!
We should not copy-paste the bad concepts from SL in OpenSim.
Freedom to Kitely!
User avatar
Ilan Tochner
Posts: 5128
Joined: Sun Dec 23, 2012 8:44 am
Has thanked: 2867 times
Been thanked: 2914 times

Re: OSSL notecard functions and threat level

Post by Ilan Tochner » Fri Aug 08, 2014 8:31 pm

Hi Min,

This configuration can be per region, it doesn't have to be grid wide. I suspect different regions on bring-your-own-server grids such as OSgrid and Metropolis will have different settings for this.
User avatar
Kayaker Magic
Posts: 345
Joined: Sun Dec 01, 2013 8:40 am
Has thanked: 50 times
Been thanked: 365 times

Re: OSSL notecard functions and threat level

Post by Kayaker Magic » Fri Aug 08, 2014 9:04 pm

My experience is that lots of grid owners see the THREAT LEVEL of many osFunction calls and set the threat level very low for fear of some unknown threat. OSGrid for example is made of 1000's of different computers (many running older versions of OpenSim) and you have no way of knowing what threat level is set on each. As a result, my assumption is that I CAN NEVER USE ANY osFunction calls if I expect to be able to export the resulting script. Even the functions with a treat level of "may startle kittens and small children" will be disabled somewhere in OSgrid.

I also lack confidence that the threat levels of many osFunction calls were set the way they are for ANY GOOD REASON. For example, I can see that osGetNoteCardLine() has the potential that some idiot scripter will call it in an infinite loop and tie up one of the script threads. (But llSleep() does the same thing, without the loop. I've seen flashing holiday lights based on llSleep delays bring a SIM to its knees. llSleep should have a THREAT LEVEL of "SUPER PROMPT CRITICAL MELTDOWN"!) But osMakeNotecard() and osGetNumberOfNotecardLines() are never called in a loop, they should not have the same treat level as osGetNoteCardLine(). It looks to me like someone just lumped them all together by association, not for any good reason.

Other grids add just a MakeNoteCard() function (InWorldz for example) and you have to use the normal LL dataserver process to read the notecards. Things work great over there, never heard of anyone griefing with making notecards.
User avatar
Jack Spade
Posts: 20
Joined: Thu Sep 26, 2013 9:57 pm
Has thanked: 8 times
Been thanked: 8 times

Re: OSSL notecard functions and threat level

Post by Jack Spade » Sun Aug 10, 2014 4:32 am

Handy, I expect the concern is that, because they bypass the dataserver event and execute synchronously, large number of notecard reads could be used to lag the simulator. It jumps out to me as an obvious griefing vector.
User avatar
Handy Low
Posts: 231
Joined: Fri Nov 08, 2013 3:38 pm
Location: Yorkshire, England
Has thanked: 207 times
Been thanked: 140 times

Re: OSSL notecard functions and threat level

Post by Handy Low » Sun Aug 10, 2014 9:31 am

And yet there's nothing to stop someone calling, say, llGetInventoryNumber() in a tight loop.

I've asked in the OpenSim user group - perhaps someone there will clarify the reasoning.
Handy Low
Post Reply