[Opensim-dev] oddities with asset storage

[Melanie]

That won't wash.

If i give copy perm just because i need it to be no trans, that 
doesn't mean that I condone off-grid use or personal backup. It has 
to be separated from the "perms" as we know them.

Most clothing is no mod/no trans. That doesn't mean that the 
clothing creator would want me to be able to download their stuff, 
meaning I would get the raw textures on my disk, to modify and 
reupload as mine...

That that is easy to do with copybot or by getting it from the 
viewer cache is beside the point here, the amount of criminal energy 
required for content theft would be significantly reduced.

Melanie

Tommi Laukkanen wrote:
> I think somekind of hybrid of different strategies might work well. Maybe
> each storage provider could keep the assets in database and use hash to
> ensure there is no duplicates and a separate metadata entry which is ref
> counted with the binary. Anyhow this would be up to the specific storage
> provider implementation. When for one reason or another asset is referenced
> by another storage provider then the other asset provider can clone it to
> own storage. Rights for cloning can be deduced simply as follows: If you
> have right to copy the asset you have right to clone it to your own service
> provider. This would also leave distribution strategies etc. decissions for
> the specific storage provider. All we need to do is figure out where and how
> different storage providers are used. Can region have dedicated storage
> provider? Can user have own storage provider? Can grid choose external
> storage provider? How do these different storage providers play together in
> all use cases?
> 
> regards,
> Tommi
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev