Loss Limit on llRequestPermissions(PERMISSION_DEBIT)

When an object requests permissions from the owner to debit money directly from the avatar's account, the script has permission to give away every linden on that avatar. I would like to propose that PERMISSION_DEBIT be handled differently. I would like to see the owner of the object be able to set an absolute limit to the amount that can be transferred.

1. This could be a property that you set on the 'general' tab of the object, or...
2. You could change the functions to llRequestPermissions( PERMISSION_DEBIT, integer amount ) where amount is the amount of money that the script can debit from the avatar. A value of 0 or -1 would give the function permission to debit all funds. You may have to replace the function with a new function since llRequestPermissions also handles other types of permissions.
   
3. You could change the verification of llRequestPermissions(PERMISSION_DEBIT), so that the owner must type in an amount after giving permissions to the script/object.

Open for your votes: Prop: 801 - Loss limits for debit permissions

I vote for removing permission debit as an option unless you own the script and the object it's in, and the script is copy/mod to you. I can't imagine agreeing to grant a script I don't have readable and editable source to PERMISSION_DEBIT.

This would break anything which works on a commission basis. TBH it comes down to a matter of trust; if you cant trust something on your account, use a mule account to hold the prims concerned.

Why would it necessarily break something with commissions? You could still write a script that required full debit permissions depending on how you implemented it. But you could also write scripts that required only a small loss-limit or or give the owner the choice.

Can you elaborate on what you mean by "anything which works on a commission basis"?