> deal with the law enforcement people
>
Chuckle @ wording ;)
--GC
___
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
a program that says things could still be protected under free speech,
and could be considered art, and manufacturing pistols isn't illegal,
even if some people kill people with them, but of course, if you build a
pistol, and then use it to kill someon
Do you understand the use-case I noted? As stated earlier: "If the
objects aren't static or if there are more avatars, then there are
several negotiation and scenarios that could happen, yet let's not
digress immediately away from the basic use-case/concept stated above."
Tigro Spottystripes w
This thread isn't about a mere box as you suggest. There thread is about
how to take physics beyond that and allow the client to do part of the
simulation, given a single use-case.
Tigro Spottystripes wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> currently attachments don't bump o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
With so many machines at their disposal, why things don't work in a more
distributed way? I can't understand why there is so much centralized stuff.
On 16/4/2010 13:20, Dale Glass wrote:
> On Thu, Apr 15, 2010 at 04:09:19PM +0200, Lance Corrimal wrote
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
visually impaired people would still need to know if the door is open,
if the trolley is on the station, if someone bumped into them etc
On 16/4/2010 12:48, Dzonatas Sol wrote:
> I don't think you thought through all cases. Consider blind users, as
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
currently attachments don't bump on anything, and animations do not
affect what the avatar collides with, avatars got a static bounding box
and that is it
On 16/4/2010 10:45, Dzonatas Sol wrote:
> That's true for the case of non-static objects. We cou
After VC90 builds Release and RelWithDebInfo the No Media Plugin notification
alarms and of course when trying video media the same notifications alarm.
Could this be related to the gstreamer problem that occured on the linux
builds? If so is there a known work around or patch.
The build was wi
The warranty disclaimer protects from liability for mistakes, not maliciousness
On Fri, Apr 16, 2010 at 5:34 PM, Tayra Dagostino
wrote:
> On Fri, 16 Apr 2010 17:11:22 +0200
> Carlo Wood wrote:
>
>> On Thu, Apr 15, 2010 at 11:28:00AM -0400, Robert Martin wrote:
>> > LL is only liable for Linden C
On 14.04.2010 01:49, Philippe (Merov) Bossut wrote:
> Hi,
>
> Whohoo!
Btw. would it be possible to configure the installer that way that it doesnt
require admin login on windows?
I guess it's probably just the "install for all users" feature of the installer.
Tillie
__
On 14.04.2010 01:49, Philippe (Merov) Bossut wrote:
> Whohoo! Yes! We now have the parabuild automated build system running
> correctly on the 3 platforms and posting results to S3 successfully! The
> only thing that's missing to make ua perfectly happy is having the
> notification email working t
On Fri, 16 Apr 2010 18:40:34 +0200
Tayra Dagostino wrote:
> Program received signal SIGSEGV, Segmentation fault.
> 0x09220aea in LLImageGL::setCategory(int) ()
>
> uhm... same of build 3318, some hint to diagnose deeper this?
>
> SG don't start, asap first login screen appear it crash...
great
Program received signal SIGSEGV, Segmentation fault.
0x09220aea in LLImageGL::setCategory(int) ()
uhm... same of build 3318, some hint to diagnose deeper this?
SG don't start, asap first login screen appear it crash...
___
Policies and (un)subscribe inf
On Fri, 16 Apr 2010 17:11:22 +0200
Carlo Wood wrote:
> On Thu, Apr 15, 2010 at 11:28:00AM -0400, Robert Martin wrote:
> > LL is only liable for Linden Core Code*
> > a TPV is only liable for code changed from LLC**
> > a user is liable for actions on the grid (and whatever changes done
> > to eit
On Thu, Apr 15, 2010 at 04:09:19PM +0200, Lance Corrimal wrote:
> - 48 hours after the server code is out in the open, the 25 groups limit has
> been lifted, AND the whole IM/group chat subsystem has been migrated to XMPP
> (including voice via XMPP); another day and there's the possibility to
>
I don't think you thought through all cases. Consider blind users, as
they would only be concerned with objects within relative space, then
even on a busy sim the sim would not have to send any updates to the client.
Even if not blind, lets say someone has their view limit set only to
relative
On Thu, Apr 15, 2010 at 11:28:00AM -0400, Robert Martin wrote:
> LL is only liable for Linden Core Code*
> a TPV is only liable for code changed from LLC**
> a user is liable for actions on the grid (and whatever changes done to
> either LLC or TP code)
That is nonsense! An open source developer c
Provided the changes can be made without being liable for damages
On Thu, Apr 15, 2010 at 04:09:19PM +0200, Lance Corrimal wrote:
> on the other hand, I would like to bet actual money on the following
> predictions:
>
> - 48 hours after the server code is out in the open, the 25 groups limit ha
That's true for the case of non-static objects. We could, however,
predict how fast an object changes and negotiate that limit, and that's
basically what there is to agree upon for what is relative.
For example, let's say an avatar moves around a sim of mostly static
objects. It can do most of
19 matches
Mail list logo
