[Opensim-dev] Proposal to eliminate the name, description and invType fields from the assets db table

Teravus Ovares teravus at gmail.com
Mon Jun 23 19:59:39 UTC 2008


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.

Best Regards

Teravus


On 6/23/08, Melanie <melanie at t-data.com> wrote:
>
> Hi,
>
> Sean Dague wrote:
> > I don't understand how your approach deals with sniffing the wire or the
> > cache, finding the asset UUID, and just embedding that in you items or
> > scripts.
>
> It doesn't. Because that approach is not enjoying blanket coverage
> in the DMCA. Means, in the case of UUID sniffing, each _item_ is a
> separate violation, subject to a separate takedown order. Yes, one
> per prim!
>
> If the texture is re-uploaded, blanket protection applies.
>
> The law isn't always common sense - in fact, it mostly diverges from
> common sense!
>
> > Anyway, it's a little moot for right now, as the current system is
> > there.  But I really think the way forward involves us using a hashing
> > strategy.  Once we dig in there, we'll see how hard it would be to make
> > UUID generation runtime configurable.  And keep this in mind.
>
> I'm happy if that concern is not forgotten. That is all I wanted,
> recognition of this as a valid concern, so no decisions are made
> that could ultimately lead to an entire grid being judicially shut down.
>
>
> Melanie
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://opensimulator.org/pipermail/opensim-dev/attachments/20080623/959173db/attachment-0001.html>


More information about the Opensim-dev mailing list