If you want to use X forwarding, you're probably not going to be happy with
the results. Machines on the same gigabit switch can even have poor
performance just loading or refreshing a file manager. There may be other
ways, and there are always remote desktop-type layers like NX..
Discrete
On T
/r/245/#review538
-------
On March 30, 2011, 11:49 a.m., Discrete Dreamscape wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> http://codereview.sec
---
This is an automatically generated e-mail. To reply, visit:
http://codereview.secondlife.com/r/245/
---
Review request for Viewer.
Summary
---
Resolved Linux file descriptor
It's due to libcurl, noted in STORM-809, and supposedly fixed (in the
autobuild repo)? If someone can verify that, maybe you can build it and
solve your problem, otherwise you'll have to build your own libcurl to drop
in. Another alternative seems to be maintaining your own DNS server/cache,
but th
USE_PREBUILT_LIBS doesn't make absolute sense either if you consider the
fact that your system's libraries are "prebuilt". This would imply that the
inverse of the setting would cause supporting libraries to be built from
source or some such.
I would make it something like "USE_LINDEN_LIBS".
Dis
ository]
native = LF
So if a file pattern is specifically declared to have Windows line-endings,
it should remain that way for everyone and in the repository.. probably
worth some quick testing.
Discrete
On Wed, Feb 2, 2011 at 3:06 PM, Oz Linden (Scott Lawrence) wrote:
> On 2011-02-01 1
Possible cover-all solution: use Mercurial's "eol" extension. It's worked
pretty well for me so far, and handily autofixed all the DOS endings in a
particular fork I looked at in one go. It works much like the autoprops
configuration does in Subversion; hopefully with less pain.
Enable it (should
I don't care if it's relevant; it should still be clarified. "Did
nobody think?" Of course not, nobody knew he would actually go through
with something like that.
Discrete
On Aug 21, 2010, at 11:31 AM, Katharine Berry
wrote:
>> 2) The active developer of a malicious viewer under the lolguise
thing continues.
Discrete
On Aug 21, 2010, at 11:10 AM, Brian McGroarty wrote:
> On Sat, Aug 21, 2010 at 7:46 AM, Discrete Dreamscape
> wrote:
>> This was one person's decision, and was deliberately done for the sole
>> purpose of messing with the owner of the victim site
This was one person's decision, and was deliberately done for the sole
purpose of messing with the owner of the victim site (although I'd
hardly call the particular individual a victim). Regardless, the team
was pretty disappointed. The one person currently owns all parts of
Emerald's hosting, so i
of the malicious viewer from the key developers behind
> Modularsystems
> which obviously you try to avoid.
>
> Additional question to Linden Lab: How can for repeated ToS violations
> permanently
> banned people just circumvent that ban by creating new accounts as many
This discussion seems to have been created with misleading intentions.
Because some TPV creators don't want to reveal any personal information
about themselves, they can't be posted on the TPV directory, and because of
this, it's understandable they might view the directory as unfair. But, this
do
> Hash: SHA512
>
> Discrete, in both ways you can have viewers that the users think can be
> trusted, but actually shouldn't
>
> On 29/4/2010 15:04, Discrete Dreamscape wrote:
> > A list of trusted entities is virtually always more robust and reliable
> > tha
then in
general no third party viewers would be trusted and used.
If you want a blacklist, there's already an informal one at
http://onyx.modularsystems.sl/viewer_reference.html .
On Thu, Apr 29, 2010 at 2:09 PM, Henri Beauchamp wrote:
> On Thu, 29 Apr 2010 14:04:21 -0400, Discrete Dre
A list of trusted entities is virtually always more robust and reliable than
a list of untrusted ones.
Weigh the two possibilities that would occur and their consequences, given
that the user is making assumptions, as you say:
- User believes viewers ON the whitelist are the ONLY ones that can be
Agreed, this is a major improvement.
Thanks, Joe.
On Tue, Apr 20, 2010 at 10:12 AM, Latif Khalifa wrote:
> I second that Gigs, very positive changes indeed.
>
> My thanks to Joe for making this happen.
>
> Latif
>
>
> On Tue, Apr 20, 2010 at 4:10 PM, Gigs wrote:
> > These look like positive cha
These comments are beginning to seem rather like pure speculation. If you're
concerned about your project or your liabilities, I recommend consulting
with someone from LL or with your lawyer.
Anyhow, the discussion at hand could use some more focus on what further
modifications would be appreciate
pers for other grids would need to do any changes on their
> code? And why can't a SL resident develop clients for other grids while
> keeping their SL accounts safe without being forced to jump thru hoops?
>
> On 15/4/2010 17:00, Discrete Dreamscape wrote:
> > I would assume t
I would assume that, to be more detailed, your code would either not allow
connections to the LL grid, or you would have to decline the updated
ToS/TPVp, thus not agreeing to be bound to it but also preventing you from
using the LL grid yourself.
On Thu, Apr 15, 2010 at 3:58 PM, Tigro Spottystripe
service.
On Thu, Apr 15, 2010 at 11:57 AM, Gareth Nelson wrote:
> The problem with that is a contract requires assent on both sides
>
> On Thu, Apr 15, 2010 at 4:47 PM, Discrete Dreamscape
> wrote:
> > It's possible to willingly agree to liability and wave whatever
> p
It's possible to willingly agree to liability and wave whatever protections
you wish that are normally under the GPL, which seems to be what the TPV
asks you to do. The issue most people seem to have is that it's not explicit
in this regard and it also doesn't make it clear that it is a contract
be
You can find grids exactly like you want already, but they have online
concurrencies that can be counted on one hand and are slow as molasses, plus
no one makes any content there for exactly the reasons you would like to use
them.
It would be narrow-minded to think that open source is the only bus
22 matches
Mail list logo
