[EMAIL PROTECTED] wrote:
I think allowing instant messages that appear to be from anyone is going to
open up cases of phishing, fraud, and/or spam. If this is all directly
available in libsecondlife, then libsecondlife users could end up seeing the
wrong end of the ban stick. My opinion is this
removed from the officially-available high level functions.
-Sam
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Hurliman
Sent: Monday, July 10, 2006 2:35 PM
To: Development list for libsecondlife
Subject: Re: [libsecondlife-dev] Inventory Upload
[EMAIL PROTECTED] wrote:
For what it's worth, I believe one of the main tenets of libsecondlife
should be the following:
Libsecondlife does not and will not enable anything that cannot already
be done manually by logging in with the official client.
The purpose of libsecondlife should be to all
dlife-dev] Inventory Upload & Fees
Tom Wilson wrote:
> I wonder if this is how the guys at the Manhattan Project felt when
> they successfully detonated the world's first nuclear bomb: we have
> this tool, but do we dare use it?
>
> I do agree that it's a bad id
3. Given the above, has anyone started implementing the code for
handling asset creation?
Yes.
It is being done slowly, and it is being done was as much co-operation
with Linden Lab as we can manage. The upload fee exploit was reported
to Linden Lab some time ago and as John H. has pointed ou
Me & John were discussing a 'update' server hosted in the gna.org
project webspace. Something that has a copy of the latest keywords.txt,
protocol.txt and what version SL likes you to login as.
The idea would be:
libsl sends it's version and it's protocl.txt/keyword.txt checksum to
--> http://
Tom Wilson wrote:
does libSL check server version numbers on login?
by keeping the libSL DLL in sync with the servers, we would get around
the upload fee problem.
It doesn't right now, but should. Before login you are supposed to
contact a server (not sure exactly how this works, it's in an
does libSL check server version numbers on login?
by keeping the libSL DLL in sync with the servers, we would get around the upload fee problem.
On 7/9/06, John Hurliman <[EMAIL PROTECTED]> wrote:
Christopher Omega wrote:> I dont think implementing the upload payment in libsecondlife would be
>
Christopher Omega wrote:
I dont think implementing the upload payment in libsecondlife would be
a good long-term solution. When LL does patch this problem and make
the deduction serverside, 3rd party devs may receive lots of users
complaining about a L$20 upload fee (both libSL and LL are deduc
I dont think implementing the upload payment in libsecondlife would be a good long-term solution. When LL does patch this problem and make the deduction serverside, 3rd party devs may receive lots of users complaining about a L$20 upload fee (both libSL and LL are deducting L$10).
Of course, this
Tom Wilson wrote:
I wonder if this is how the guys at the Manhattan Project felt when
they successfully detonated the world's first nuclear bomb: we have
this tool, but do we dare use it?
I do agree that it's a bad idea to turn libSL in to a potential
vehicle for a free upload program - espec
I wonder if this is how the guys at the Manhattan Project felt when they successfully detonated the world's first nuclear bomb: we have this tool, but do we dare use it?
I do agree that it's a bad idea to turn libSL in to a potential vehicle for a free upload program - especially when all of the
This seems like a fair and just solution, and should keep LL off our backs.
--Jesse
On 7/9/06, John Hurliman <[EMAIL PROTECTED]> wrote:
Let me add some context to this issue, and an explanation for those who
haven't taken a look. Upon login an EconomyData is sent to the client,
saying how much i
Let me add some context to this issue, and an explanation for those who
haven't taken a look. Upon login an EconomyData is sent to the client,
saying how much it costs to do various things in the game. After that
point, the client is responsible for making a payment for the correct
amount every
and seriously think about the
>> > possible fallout of what we do. I also believe if we cause too much
>> > negative effects to SL and LL, LL will change their opinion and start
>> > inhibiting libSL's development.
>> >
>> >
>> >
>>
t had my morning coffee yet….
>
>
>
>
--------
>
> *From:* [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] *On Behalf Of *Tom Wilson
> *Sent:* Sunday, July 09, 2006 8:49 AM
> *To:* Development list for libseco
gt; >
> >
> >
> > But – I haven't had my morning coffee yet….
> >
> >
> >
> > --------
> >
> > *From:* [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] *On Behalf Of *Tom W
gt;
>
>
>
>
> *From:* [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] *On Behalf Of *Tom Wilson
> *Sent:* Sunday, July 09, 2006 8:49 AM
> *To:* Development list for libsecondlife
> *Subject:* Re: [libsecond
son
*Sent:* Sunday, July 09, 2006 8:49 AM
*To:* Development list for libsecondlife
*Subject:* Re: [libsecondlife-dev] Inventory Upload & Fees
I'm sorry, but it just doesn't make sense to enforce upload payments in
libSL.
lilbSecondLife is open source, and unless you close the source (a
: Development list for
libsecondlife
Subject: Re: [libsecondlife-dev]
Inventory Upload & Fees
I'm sorry, but it just
doesn't make sense to enforce upload payments in libSL.
lilbSecondLife is open source, and unless you close the source (and obfsucate
it and use a languag
I'm sorry, but it just doesn't make sense to enforce upload payments in libSL. lilbSecondLife is open source, and unless you close the source (and obfsucate it and use a language that's NOT C#), everybody who wants to cheat and upload for free would simply modify the upload routine and rip out the
21 matches
Mail list logo
