<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>Again, I don't see why we need to have assetId === sha-1 hash - if the only thing we want to accomplish with it is de-duping, we just make sure to send the hash along, and any context can choose to use it to de-dupe or not.<BR>
<BR>
And to trust it or not.<BR>
<BR>
Obviously, you wouldn't trust an assetId generated by an untrusted source to represent the asset binary anyway, so quite a lot of re-hashing and checking will be done along the way anyway.<BR>
<BR>Best regards,<BR>Stefan Andersson<BR>Tribal Media AB<BR> <BR>Join the 3d web revolution : <A href="http://tribalnet.se/" target=_blank>http://tribalnet.se/</A><BR> <BR><BR><BR><BR>
<BLOCKQUOTE>
<HR id=EC_stopSpelling>
Date: Mon, 23 Jun 2008 15:59:39 -0400<BR>From: teravus@gmail.com<BR>To: opensim-dev@lists.berlios.de<BR>Subject: Re: [Opensim-dev] Proposal to eliminate the name, description and invType fields from the assets db table<BR><BR>
<DIV>I'm not convinced the SHA1 UUID will be extensible enough to allow for future plans. The idea is to not assume anything with a UUID. Adding assumptions increases scalability at the cost of extensibility.</DIV>
<DIV> </DIV>
<DIV>Best Regards</DIV>
<DIV> </DIV>
<DIV>Teravus<BR><BR> </DIV>
<DIV><SPAN class=EC_gmail_quote>On 6/23/08, <B class=EC_gmail_sendername>Melanie</B> <<A href="mailto:melanie@t-data.com">melanie@t-data.com</A>> wrote:</SPAN>
<BLOCKQUOTE class=EC_gmail_quote style="PADDING-LEFT: 1ex; BORDER-LEFT: #ccc 1px solid">Hi,<BR><BR>Sean Dague wrote:<BR>> I don't understand how your approach deals with sniffing the wire or the<BR>> cache, finding the asset UUID, and just embedding that in you items or<BR>> scripts.<BR><BR>It doesn't. Because that approach is not enjoying blanket coverage<BR>in the DMCA. Means, in the case of UUID sniffing, each _item_ is a<BR>separate violation, subject to a separate takedown order. Yes, one<BR>per prim!<BR><BR>If the texture is re-uploaded, blanket protection applies.<BR><BR>The law isn't always common sense - in fact, it mostly diverges from<BR>common sense!<BR><BR>> Anyway, it's a little moot for right now, as the current system is<BR>> there. But I really think the way forward involves us using a hashing<BR>> strategy. Once we dig in there, we'll see how hard it would be to make<BR>> UUID generation runtime configurable. And keep this in mind.<BR><BR>I'm happy if that concern is not forgotten. That is all I wanted,<BR>recognition of this as a valid concern, so no decisions are made<BR>that could ultimately lead to an entire grid being judicially shut down.<BR><BR><BR>Melanie<BR>_______________________________________________<BR>Opensim-dev mailing list<BR><A href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</A><BR><A href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target=_blank>https://lists.berlios.de/mailman/listinfo/opensim-dev</A><BR></BLOCKQUOTE></DIV><BR></BLOCKQUOTE></body>
</html>