Reviewing BuilderBot Release

We would like to thank the people that left constructive comments and sent emails, notes regarding our request for feedback on our BuilderBot release plan.  Clearly people feel that releasing the code opensource is very troublesome and makes defending their content rights more difficult.  We can accept these concerns and will alter our plans. We did ask for feedback, we appreciate it and now will do something about it. 

We still believe that a tool like BuilderBot can be a positive thing for sim builders. I don't know how many people/companies make/have large scale builds like we did still in SL, but using Sec Inv is not an ideal solution beyond a few items. It would be great to be able to pull out old copies of our work to study them or use as a base for something new.  We wish we had a BuilderBot tool ourselves during the OpenSpace rip-off when we deleted some of our sims as a result. While we have the chunks of these areas, the sims are really gone forever. We are glad that we were able to use the BuilderBot to move our content over to our new OpenSim grids.  This is our content and we should be able to maintain it, move or do what we want with it.

While you can (and also pay for) importing content into SL, why is there no "official" way to get it out? Why is there no way to version control a build? Why wouldn't LL allow us to reimport/reload?

Anyway, some next steps based upon things we heard, discussed relating to releasing BuilderBot:

No BSD Licence

We will not put the code out under an opensource BSD licence. Our interest in providing the code open under BSD is in the spirit of what we believe is a key part of the future of software development. Libomv is BSD and we felt that we should continue to go down that path. There is a lot of interesting potential here for bots and AIs.  However, BSD does not restrict the future usage of the code enough in this instance and possibly could in the hands of malicious people be used to accelerate content theft.  We have experienced content theft via copybot type tools and others means.  We know that when you find some objects ripped, out on the grid it is very disturbing. We will try harder to make a commercial version of BuilderBot useful for legitimate practices and not easily applied to abuse.

Looking at DRM checks

We will continue to review how best to package the software including looking at DRM checks.  Assuming that the DRM checks can be added without too much effort or complication, we should be able to add that to the software offering. This is by no means foolproof, but it will make unauthorized usage more difficult and help people who only want their own stuff get their own stuff. In addition, we will review the entire release timing and what other terms maybe be needed.  We hope to have some update on this soon.

Unlikely That We Will Offer a Service

Actually a service is an interesting approach, but not for us. We would need to charge too much and we don't have the resourcing available to provide such a service properely.

Issues Relating to Content Theft

A tool or in fact copying something does not necessarily mean that there is theft or even unauthorized usage. What is critical is to know is whether or not someone has taken an illegal copy and is in fact doing something unlicensed with it. So clearly taking a section of a build and then selling it is wrong and should not be tolerated. This is very hard to track, so a seller's reputation is an important thing to consider. Know who you buy from.

There should also be some action--by grid owners. In our view, the DCMA filings at SL are just not handled in a way that is strong enough to dissuade people from ripping and getting away with it. The future grids of the metaverse should not be safe havens for rippers--if they are, then informed, concerned people should not visit these places or spend money with them.  Ultimately, if there is little benefit to taking unlicenced content then rippers will not invest in the effort to do it. Consumers have a choice where they spend their money/time.

 

More info about Copybot > Content Stealing > SL's DMCA Policy

 

 

 

Trackback URL for this post:

http://rezzable.com/trackback/2429

Comments

Somehow I get the feeling

Somehow I get the feeling that those against the builderbot are the same ones that would have been against the automobile because it would put horseshoers out of work

Good to see.

Good to see.


Seems like a measured,

Seems like a measured, responsible, mature decision.

 Oh come on, so that was only

 Oh come on, so that was only a mediatic buzz to finally say you will put a finger to the opensource community?

Self-Serving, Duplicitious, Mendacious

Self-serving, duplicitious and mendacious post here from Himoff.

Naturally, anyone who had followed the escapades of Rezzable from the beginning would see this PR stunt for what it was worth, first, a thuggish and cynical announcement that one company has the power to screw over the entire economy, a fake request for "input," and then a completely duplicitious pretense of "backing down" and "seeing reason" so that everyone can perceive this thug as somehow "willing to compromise". It's a tried-and-true Bolshevik method thatn Jonathan Himoff knows well. And it's one the Lindens, BTW, use constantly so he's in good company.

This notion of "it's our content and we'll dowhat we want to, do want we want to" is bullying infantile speciousness in a community context in a transparent virtual world. Builds seldom contain the content of only one person. And any tool that copies not just your content but everyone else's is one that you cannot use for selfish purposes because you immediately impact everyone else's rights. Sure, you can use up all the water or pollute all the water with your factory in your town because it's "your property and you can do what you want," but if that poisons all the rest of the townspeople, you are harming other's rights and the government and NGOs are right to step in and stop you. You never seemed to have learned in school that your right to swing your fist ends where another person's nose begins.

What's especially disgusting coming from this arch technocommunist is the idea that now, suddenly, this opensource code, that "everybody" has and "nothing can be done about it" can in fact be sequestered and sold as commercial code and kept from this lovely opensource community. Hahahahahahahaha. This sort of blatant hypocrisy coming from the opensource community is self-discrediting and doesn't even need me to point it out. The other dirty big story as I've noted on my blog is that big IT is always lurking in the background ready to slurp up all this honest opensource code that all these script kiddies tinker with for free What is Himoff's relationship to IBM?

When you offer a tool for sale or distribution, and incite its usage, you are participating in copyright theft. This completely fake and coy notion that tools are neutral, tools can do no wrong, and we are exempt from and legal scrutiny because we merely make tools simply doesn't fly with even the most cursory review from perspective of RL morality and RL law.

You don't put up a lock pick for sale next to each lock and pretend you didn't help with the lock picking. The 9/11 hijackers took down the pilots of the planes with box-cutters. Are box-cutters inherently evil? This is the sort of question argued in the abstract endlessly on Internet forums. No, not when a trucker buys them to rip open big cartons at his job. But, yes, when in the hands of hijackers killing pilots and crashing planes. The idea that tools always and everywhere remain neutral and disassociated from the agents and get a moral and legal pass always and everywhere in their use is one of those fallacies that power-hungry geeks use to keep imposing their tools on everyone -- into which they've coded their worldviews and agendas.

And indeed, some tools have malicious intent welded into them. If a box-cutter with the brand-name "Pilot Slasher" that was especially sharp and swift was sold at every airport newsstand, you could very well say that *that* form of box-cutter *was indeed* inherently evil because its makers welded into the simple tool not only effectiveness, but the name, place, and intent to do harm. Whereas the blunt-edged box-cutter dealer in a rural store in Maine meant only to sell his tool to truckers, store clerks and postal workers to open up big boxes. If one of those store clerks then used his box-cutter in a robbery, you could say the tool isn't "inherently evil" but its use for evil would then make everyone in every store start to think they needed to regulate the sale of box-cutters more carefully because of their propensity for use for evil. Brass knuckles are not like gloves, only for keeping your knuckles warm in cold weather.

In the case of BuilderBox, it isn't just the capacity for copying, or the lack of permission checks that was being contemplated, but the clear intent to harm. This isn't Carl Metropolitan, a builder who sells builder aids already as well as a prominent newbie-helper at NCI, with a sterling reputation, offering a builder's boon. This is RightAsRain, who has a long history of bullying the press, intimidating builders with whom he had disputes, supporting aggressively sycophantish and abusive bloggers like Vint Falken, constantly slamming land dealers and the Lindens, and announcing with dramatic self-importance that he was now leaving SL for the greener pastures of...opensim, where theft is rampant. Reputation and context are important online, of course, as in real life, and that means any tool that RaR suddenly announces for sale is then welding into it all his reputation and intentions made clear already as the most cynical and hateful ones.

To pretend that just because he didn't release this code as free and opensource -- yet -- or that just because it's a bulder's boon tool, it has no moral or legal consequences and isn't an incitement to crime is to pretend that you can hang up a box-cutter for sale next to a departing airplane called "Pilot Slasher".

The posturing about insufficient DMCA protections are the most duplicitious of all. Like Zha Ewing and Dale Innis and other Big Blue reps in SL posturing around opensource that directly profits their own company, this pretend and pious reflectiveness shouldn't fool anyone. They are for putting the stress of the problem of copyright theft not on themselves and other coders who should be building security into the client and all procedures around log-ins with the client, but on external parties. They want to tell everyone to put a Creative Commons notecard in their prim and call their lawyers. DMCA takedowns are the last step, not the first to create a protective regime around intellectual property.

The proposals made during a discussion of this disaster at the Society for Virtual Architecture last night are in sharp contrast to RaR's posturing here:

http://secondthoughts.typepad.com/second_thoughts/2009/07/concerned-sl-r...

They include things like:

o plug-in authentication only for registered opensource developers who pledge not to inject malicious code

o checking for perms even on the existing builderbot

o policy statements or change to the TOS if interpretation is not sufficiently robust that use of BuilderBot is identical to use of CopyBot in terms of how it is prosecuted as a TOS violation

Cynical technocommunists like RightAsRain think they can endlessly posture, caper, lie, and distract about their true agenda by pretend feints and thrusts like this post, and by claiming "everyone's doing it" or "security is impossible" -- until it comes time to sell their code for $100. Of course it isn't when you have good faith and good will, neither of which Jonathan Himoff has regarding Second Life and its residents.

 

 

 

 

 

What you should have said.

This is what you should have released, instead of that Linden Labs style announcement without thinking of the backlash. I applaud your efforts however, I think you were a fool to release something that had that potential to be inflamatory across so many residents. Perhaps next time you'll think more carefully about your news releases before posting them, verdad? The cynical side of me can't help but think this is *only* being released because of the flack you've gotten and the fact you're shoving off from SL. If not, then again, you should have thought about what you communicated to the public.

prok, thanks again for

prok, thanks again for proving you type faster than you read or think.

Better

This is the blog post you should have initially made, this is a lot less confrontational. Now, have you left the door open for Linden Lab to buy this tool? Have you had any discussions at all with Linden Lab about any of this?

Theft is Theft

No, those against the builderbot are not horse-riders against cars, they're the same people who are against automobile theft.

They also don't believe elevating stable boys and garage mechanics to the level of influencers and decision-makers and worse, rulers over us all, merely because they feed the horses or fix the cars. Coders are no more than rude stable boys and abusive garage mechanics who have not yet been put in their place.

Who will be buying your

Who will be buying your box-cutter, RaR, IBM?

a professional builders reaction

All would be fools to buy software that was "marketed" in such a manner. Truly in all of the 15 years of online web3d business and politics I've seen first hand publically and from behinds the scenes, this ranks as one of the most cynical, self serving, and irresponsable display's for the supposed "benefit"  of the "profession of web3d and virtual world design" as an industry.

 

 

 

 

Attention to all people that

Attention to all people that may wish to comment on our blog in future:  We are tolerant and open to comments. Our moderation policy is to allow free speach and open exchange of opinion. I feel that our site is on the edge of this approach being abused. While we can understand that people feel strongly about certain topics, we will not allow hate and abuse to over-shadow discussion. We do not believe that personal attacks, vulgar comments or threats of any kind are acceptable.  We do not condone or support this type of behaviour and will enfore our moderation policies as we see fit. Further, we will pursue all actions available for malicious activities against our sites, staff or brands. We can appreciate that some issues are sensitive and people have thier own opinions, but if these cannot be expressed with decency and respect they will be removed and people will be banned.

"Somehow I get the feeling

"Somehow I get the feeling that those against the builderbot are the same ones that would have been against the automobile because it would put horseshoers out of work" - Anonymous

Nope, there is a difference between invention-induced change of business models (the automobile putting stables out of business) and theft-of-IP-induced changes of business models (due to the basic dishonesty of the OS movement itself).     The first is called progress, the latter theft of IP.    I don't know of any content creator who is against innovation...but I do know a lot that are against scummy little content thieves and those that aid and abet them wtih tools and rationalizations.

Rezzable did the right thing in the end...but I wonder whether it was due to public opinion (and possible behind the scenes linden efforts) or a true sense of doing what is right.

 

Or Maklin was this the plan

Or Maklin was this the plan all along and the initial post was scaremongering to get attention? That first post has certainly left a bad taste in the mouth, but it has gained attention for this product.

@ Maklin -- nothing to do

@ Maklin -- nothing to do with the Lindens. I think if you ask people for their comments you should listen. We did. 

You are not at all right though about "the basic dishonesty of the OS movement"--pls step-up and suppor that wild accusation. I think you are talking nonsense on that point, perhaps fueled by misinformation from microsoft, oracle etc. OS is the future of software--maybe, but nothing dishonest about it. Theft of IP is very serious accusation and not one to be made lightly.  Any tool can be misused, I don't think we should punish the professionals by starving them of useful tools that might be used badly by petty or more serious rippers.

@ Ciaran -- no, I was dead

@ Ciaran -- no, I was dead serious about releasing under BSD. From a development perspective that is the best way, but I can accept that there are other considerations.

Glad, but still concerned

I'm glad you're taking time to think this over, but I'm still concerned that the genie that's been long out of the bottle will continue to roam free while LL is asleep at the lamp.

 

-ls/cm

@ Crap -- you gonna rub

@ Crap -- you gonna rub Kingdoom's lamp?

Wise decision

I think it is wise to have reconsidered your position. While I regret the removal of the Open Source license, and while I don't believe in the technical efficiency of any DRM system or of security by obscurity, I think it is essential to add ownership checks to your product.

Not only it will prevent thieves from stealing content "too easily", but it will also keep professional builders safe from accidentally copying bought items or their neighbours' builds.

Keep on the good work. We really need export systems for SL. Our data can't remain captive.

<Prokofy, insert long and furious Maccarthist witch hunting here>

 

Professionals? Professionals

Professionals? Professionals attempt to grow the value of a "profession" and not simply enrich their own egos or companies short term pockets by removing all value from the others in the profession's activities.

Walter, a dead professional jounalist.

@RightAsRain:

Re: "Attention to all people that may wish to comment on our blog in future..." -- sincerely, it is high time. Well said, and well done! :-)

Thank you

Thank you for taking a more responsible approach to this product, good luck with the work to get it into shape as a product that is not easily used applied to abuse.

Risky business

The terms of release are almost beside the point.  Indeed, the danger to Rezzable's business is in the now widespread knowledge that such a tool is used, copying content based only on ownership.  Not that "DRM" helps in this case, unless by "DRM" is intended a verifiable identity match with the creator of record for the copied content.

Nobody has an implicit license to copy anything from the Second Life grid that they did not themselves create.  "Permissions" are irrelevant: a full-perm item on the Second Life grid confers no rights whatsoever outside the Second Life service.

If it becomes common knowledge (a seemingly inevitable consequence of this move) that the Rezzable grid is a frequent host to content obtained without explicit license from the creators, that grid will be under constant scrutiny for any violations.  The workload in processing the relentless flood of DMCA notices will swamp any other effort in keeping the grid running.

Competent counsel will discourage this entire course of action.

Just a side note

@Prok:

"They also don't believe elevating stable boys and garage mechanics to the level of influencers and decision-makers and worse, rulers over us all, merely because they feed the horses or fix the cars. Coders are no more than rude stable boys and abusive garage mechanics who have not yet been put in their place."

I don't know whether in your line of business you happen to work with coders, but if so, I sincerely hope they catch this comment.  It would interesting to see their reaction to your malevolence towards them.

While it's unlikely, I also would be interested to see the reaction of any RL mechanics who service your car for you, upon seeing that comment.  You might just find more wrong with your car or find yourself slapped with a higher bill after they've seen the level of your disdain for them.

Your opinions about the issue at hand--the development and possible release of BuilderBot--is one thing; the sheer arrogance you display towards anyone who disagrees with you (or towards people who you deem "below" you, as it apparently seems with coders and garage mechanics) is appalling.  It is completely possible to express your distaste for a product like this without the attitude, without threats, and without unnecessary elitism.

For the record, I am not a builder nor a coder nor any kind of content creator; I am just a regular SL user who tries to support content creators, artists, and musicians in SL as much as I am able.  As such, I'm otherwise staying out of the finer points of a debate that has nothing to do with me... I just see no reason to blast people as hatefully as possible, particularly when they've done nothing more heinous than ask for opinions and feedback about a *possible* software release.

Attention RAR.

Hey, RAR

 

Whats up asshat

 

Anonymouse here again. The same one that saw through your exploiting of SL builders: getting them to do industry level work at SL rates (eg working for fuck all money) while your company pockets the cache, kudos and cash, from their labours.

The same one that predicted that you'd move everything to opensim, set up your own grid, and called out all your bullshit whining at lindenlabs as propaganda to whip your minions up into a frenzy to come with you, because once you burned your bridges in SL, if this didnt work, if they didnt come, and stay, it was curtains. I predicted this months before your 'surprise announcement'

The same one that has always seen through your plans like you drew them on a window. Yeah, its the real me. Howdy.

 

It hasnt worked, has it. You and I both know it. Numbers arent high. Diversification isnt attracting new viewers in the numbers you need. SL still has too much pull for mainstream audience to invest in your grid long term. Signups on high profile stuff are good, but the 24 hour dropout rate is high. Terrifiyingly high. Nobody is staying.

And now you're making this. Which supposedly wont be opensource. So you're paying LL a bunch of money for a license then? Better check your t's & c's , cause it has to be opensourced, or private, or paid for, if you wanna distribute something that connects to LL's grids. Aw yeah.

So here's what you're gonna do. You're gonna go along with this "not opensourceing it" thing. Its our idea, and you want to listen to us! Right? Right..  And then when LL says "naw dude" you're gonna come crying back and say "WELL lindenlabs wont LET us release this unless its opensource, they're making us give it to the hackers! its not our fault! blame lindenlabs!! bawwwww" You'll say they charge too much for a license, even though you knew those costs in advance, going into this.

In the post that you write to refute this one, you'll deny the above. Either in part or in whole. But we both know you have an angle. You're trying to smash SL wide open, so that content isnt a draw anymore, experience is. Once the marketplace for items becomes moot, what will attract people? What will make them come, and stay. And this is where you hope you can take over as market share leader, and go to potential clients with a vastly superior value proposition to your rivals. Because you think you can provide the best experience. And you dont care about literally destroying a world to succeed. You're like darth vader but skinnier and with homosexual undertones. You want to cut the hen that lays the golden eggs wide open. We all know the moral of that story. Its an arrogant position, and you're destined to fail.

In the past when I've nailed you to the fucking wall, you've stayed conspiciously silent. Whats with that? Do you consider your position so weak that it cannot withstand debate?

Everything you have ever done, even things ostensibly altruistic, have been for your own gain, to further your own aims within this sphere of virtual worlds. You came to the game a little too late to make it big, you bought your headlines with swathes of sims all, connected up.

You kept it a 'secret' about who you were, and what your plans were, to obfusicate things and create interest, Which is fine. But when the mist settled, you still hadnt come up with anything. You tried to hit the ground running, to make up speed and lost time. You failed.

Your aim was to build up a massive loyal audience, that you could then advertise to. We'd be your sheep, we'd swap our time for your adverts, it was going to be the new way. JB, SV, RS, they all said so. You know who the initials represent. You believed. I pity your naievity.

 

So dont give us this smiley crap, dont offer to shake our hands as a community with one hand while you go to stab us in the back with the other. You're here to lie cheat, and fucking steal, its a dishonest con. We arent your smiley placid sheep, You underestimated us badly, and overestimated your reach and ability.

With cool regard, I notice your latest vacancies and hirings - still paying vaastly under market value. Someone that will build, script, texture, shoot machinima and project manage for that amount of money? You should know you get what you pay for, and nobody worth hiring will work for that little money. Thats why the vacancy is unfilled after so long, even in this current economic climate. But it doesnt matter. Times are hard. Someone will need the money badly enough, and again, you'll be there, ready to exploit. You prey on the weak and needy. We are watching and we do not approve. Once again, its a calculated exploitative move.

What shall be done? Nothing. You're failing anyway. Nothing needs to be. But know that not all of us are fooled by your smiles and promises, your smoke and mirrors. We see the man behind the machine, a small frightened man acting in desperation as his house of cards falls around him.

Transmission ends.

 

I think we have seen enough

I think we have seen enough wild accusations and pathetic attempts to slander us. I can appreciate that this is hot topic for a lot of people, but I will not tolerate any further tirades and insults on this site. I think it is best practice not to say anything on the web that you wouldn't say to a person in their face. We are here in the real world. We are not concealing our identities. If someone thinks they can hide behind a keyboard and screen and blast abuse, insults and unbridled anger -- you are wrong. Your voice is not heard there is only the empty clatter of your keys and the spew of bitter thoughts in your broken mind. I will leave this hateful spew on this post as an example of the negative energy that can be blasted at web site owners, staff and the community that participates.  Ignore these people that want to pull us into their world of demons. I would urge people not to slip into their twisted world of frustration and allow dark thoughts to overwhelm a more balanced, caring approach to people. Stay positive.

re:Anonymouse/I've seen enough

From the world of aliens to the world of demons lol

Good Response

Good response..You dont have to release the source, its your choice. Good luck with sales of your tool. OpenMV still has the core source out there, so anyone with a bit of creativity can reproduce the results of your tool, why should you absorb all of the crowds hatred, its not nice.

To the screamers an haters....chill out, cut down on your salt intake, switch to decaff.

Love and Peace.

Storm in a Teacup

Secondlifers need to remember 'when the storm is over, we are all still stuck in a teacup'.

 

Ownership checks

 I wonder how ownership checks will affect backing up sims built by a team of builders ...

will there be a list of avatars one can register with the tool? or will every avatar have to backup their portion of the build?

I am betting that you don

I am betting that you don even believe yourself what you are trying to sell us here.
You guys are desperate and that is your move to satisfy investors because you know this is gonna sell and you also know that there are more potential thiefs as people that actually want to move to open sim. You also seems to ignore the re-import possibilities and since you still trying to sell us Fire for water you can't be taken seriously and have to be faught legally.

There are tools out there that respect user permission, group permission and that is the only way to proceed. Not making it open source is supposed to protect YOUR intellectual property and not ours because you have realized this might be a risky business with possible lawsuits but it will also create a revenue which you need so badly.

In your defense I was not expecting that you would act frank about your intentions and reveal the real reasons for this "products"
In the end you define yourselfs by your own actions and no matter what, when Rezzable is finally bankrupt and you are trying to get a job on the 3D development market the people will remember who you are and what you did. I'd be super careful because when one of the dozens of lwasuits is going to be succesful you have destroyed your reputation plus your financial responsibilities.

Shoving the issue over to Linden Labs might work for you and is ALL THAT YOU WANT, and you are actually provoking them to ban your own customers!

Funny trivia,
you might end up being banned yourself 
About the usage of CopyBot (because that's how your product is identified) http://wiki.secondlife.com/wiki/CopyBot#CopyBot
Future of bots https://blogs.secondlife.com/community/land/blog/2009/03/26/much-ado-abo...

No matter what, anyone who is buying this "product" is automatically commiting a crime because the usage of copy bots is not allowed.
You should put that on the box otherwise you might receive lawsuits from angry thiefs as well, lol!

@ Istephanija -- you are not

@

It is  amazing how the word

It is  amazing how the word "CopyBot" and for that matter, any utility that has the ability to copy objects in SL, can generate such unbridled fury and paranoia.

So, how do we keep the more paranoid among us from howling with great anger and issuing 100mb manifestoes (like this ersatz Prokofiev chap above)?

The best thing I think Rezzable should discard any attempt to market or distribute this code, and not make the code available to the public at all. in other words, keep it as an in house solution to moving their sims to OpenSim.

Barring that, setting up a registry that requires a check against the customer (meaning the avatar buying the BuilderBot software) for payment information and one that records each time BB is used in SL might be something to add as an accountability tool, along with basic permissions checking: avatars that don't have payment info with SL simply would not be allowed to buy BB, and users who acquire it wuold be unable to run it in SL without payment info.

I must admit, that RaR floated this "trial balloon", and like flies to meat left to spoil, it has generated much ugliness.  A softer, saner approach would have been to *presume* that the certain percentage of builders who scream "OMG! COPYBOT! ASDFG!!" (these same folks who put those annoying "!quit" spammers near their telepoints, not knowing that those things are a. annoying as hell and b. useless) would be upset much more so by a tool that could zap an entire sim and copy it regardless of who owned what that was rezzed on it.

In other words, RaR might have gotten a saner response from the community had it asked (a) "if we release this as Open Source Software, what sort of license should use, and (b) what sort of protocol should we put into it to safeguard (wihin practical limits) creators' IP rights?"

- - - - - -

As a coder with no particular stake in what Rezzable does or doesn't do with this code, I do not receive Prok's rather arrogant diatribe against car mechanics, stablehands, or coders with a smile.

Technology *is* largley neutral. The box-cutter vendor is the one who must decide how she will market her product, the same as the gun and ammunition manufacturers or cigarette makers market theirs, and just as importantly, those who buy or acquire the tools or items and subsequently use them. There are a few exceptions, perhaps... such as nuclear weapons or bouncing betty landmines whose sole design is to kill and maim (but even this is debatable, as these are design to do so to cause the "enemy" to die so they will be less likely to harm us).

Please don't tell me (Prok) that you are the sort of gal who wants the government to come and take my guns away because "guns are evil and they kill people and fuzzy little bunnies"... or take away my computer because I write code... because my guns aren't evil - nor are the "Gut Ripper" brand bullets I at "Fuzzy Bunny Killers Ltd."

The only time that these devices become an accessory to an evil act is, if through my negligence, somebody else accesses them to commit a crime, or if I willingly use them in the commission of a crime.

And it is the same with code, and car mechanic tools as well.

hugs and kisses,

-Ryoma V.

Istephanija Munro

 

"I am betting that you don even believe yourself what you are trying to sell us here.
You guys are desperate and that is your move to satisfy investors because you know this is gonna sell and you also know that there are more potential thiefs as people that actually want to move to open sim. You also seems to ignore the re-import possibilities and since you still trying to sell us Fire for water you can't be taken seriously and have to be faught legally.

There are tools out there that respect user permission, group permission and that is the only way to proceed. Not making it open source is supposed to protect YOUR intellectual property and not ours because you have realized this might be a risky business with possible lawsuits but it will also create a revenue which you need so badly."

Dear

Either you were born stupid, or you can't read. Read the updated post and you'll see it'll now respects permissions of content creators. Read it and stop crying.

Thank you.

Uneducated = Uneducated

Some of the best software on the planet is open source. Operating systems, both low and top level applications created by the open source community provide a vastly alternative and rich experience on many fronts. People are uneducated and want to remain that way. They have been raised to believe in the "Microshaft" way of doing things despite clear evidence that there remains a better way to compute. That is the bottom line. There are superior ways to compute.

In terms of not using the BSD license for the product when clearly Libomv is BSD is not what I had hoped for. I would personally prefer a software based on it's parent open source type licensing if you intend to use others work for your product. Either a binary or source that could be compiled on GNU/Linux.

This whole tirade of uneducated masses spilling their fears of content theft is ludicrous. There isn't any piece of content within the SL database that cannot be taken, abused, resold etc. by anyone with a mere entry level knowledge.  The Linden permissions system is not a true DRM and anyone wanting DRM code written to protect virtual assets are not all that bright.

Just as with any open source software, people donate or pay for the proucts within SL because they want to support the effort of the content creator. No other reason. And to believe that the better alternative is to create a software limiting, or in some way adding digital rights management type code to a product is just not the direction I would have taken.

I do think that backup tools should have been provided by Linden Lab. However, tools are needed, and many will prefer open source type tools where possible.

Most that complain have never ran a web server let alone an opensim server. They have no clue how and what is under the hood of anything they operate and want to remain ignorant and fearful.


 

 

 

True DRMs ?

Thanks Tracy for your intelligent post.

"The Linden permissions system is not a true DRM' => There is NO true DRM. The concept is flawed. For example, in second life, since your viewer needs to render objects, their data must arrive on your computer, opening the way for "theft".

It's just the same as the "analog leak" for real world DRMs. Since you need to play the music/video at the end, there is an opportunity for a guy with a microphone to or a video recorder to capture it, what would be "theft" as well.

OK, now having proved that DRMs do not work (which is by no way a new fact), we must also acknowledge that Second Life has a DRM system, and we should respect the people who rely on it to protect their intellectual property. Even if it has always been true that this DRM system can be worked around (from open source code or closed sourcce code, it does not matter). Even if I release most of my SL stuff as Open Source, no one should be ever forced to choose such a distribution model if they prefer remaining proprietary (that should prove anyone that we are not cryptocommunists). The DRM is here, it is in the genetical code of Linden Lab's product, and we must accept it even if we dislike it.

To respect the current DRM system of Second Life, it can be chosen to enforce "security by obscurity" by keeping the source code for ObjectBuilder secret. That's not really efficient, since anyone else can get or write another copy bot. The problem does not lie in the code being open, but it lies deeply into the SL client-server messages structure. Anyway, I recognize that keeping the source code for ObjectBuilder secret makes the task a little bit more difficult for the pirats. So if Rezzable does not want to release the source code, I respect their decision, because to some (limited) extent it makes sense.

OK, DRMs do not work, but we have to respect them. Security by obscurity does not work, but in this case it could help a bit. Now to the important point.

The important point is that ObjectBuilder should do the same as SecondInventory: do not allow you to save stuff you don't own. I'm sorry this makes more work for rezzable developpers, but I see this feature as mandatory. It clearly draws a clear line between a cracker tool like CopyBot, and a builder tool like Second Inventory (Meerkat checks ownership too I think - not sure).

Thanks Rezzable for thinking and asking for advice before acting.

 

Catherine--ty. Also worth

Catherine--ty. Also worth noting that the SL DRM concepts are only concepts within SL at this time. So for example, if something is +copy in SL as a matter of convenience for SL use, does that imply that it +copy to leave SL?? There is no click-wrap on digital goods in SL and TOS does not address the content creators rights at all. And what about Freebies? I made a post awhile about this topic--you might find it interesting enuff http://rezzable.com/blog/rightasrain-rimbaud/digital-content-rights-and-metaverse-trust-freedom-and-risk-opensim-grids

"Thanks Tracy for your

"Thanks Tracy for your intelligent post."

Your welcome.

"OK, now having proved that DRMs do not work (which is by no way a new fact), we must also acknowledge that Second Life has a DRM system, and we should respect the people who rely on it to protect their intellectual property."

Second Life has a permissions system backed up with a TOS. This is "NOT" what a true DRM (Digital Rights Management) code/function is, in part, or in it's entirety. And I do agree, as history has dictated, DRM doesn't work, will not work, and is flawed in concept. Linden's permission system is what it is and it's fine. Certainly better than a site with embedded no right mouse click code for  what some believe protect a site against image theft. Yet for some reason, I still run into these goofy sites on ocassion to this day.

 

 

Spot on, Tracy.SL permissions

Spot on, Tracy.

SL permissions system ≠ DRM.

A true DRM would mean implementing something along the lines of data encryption, and perhaps having content creators register with LL and generating  encrypted keys with a hashes unique to their avatars, and then some means of associating these keys with the content that would reduce the content to scrambled garble when some other avatar tried to copy or pull in an encrypted resource via its UUID.

I have a feeling though, that this is a sort of thing LL really wanted to avoid having to implement.

And my take on DRM as a flawed concept is, it's just another dimension of the "bigger wall, taller ladder" security game that has beset the proprietary software model for years. It's great fodder for copyright attorneys though - after all, they have kids to put through private school too!

GPL license.

If your software is based on OpenSL software, in fact, you are *required* to provide the software under GPL license.

Hiro -- libomv is BSD

Hiro -- libomv is BSD

SL permissions system &ne;

SL permissions system ≠ DRM.

No more than Unix perms would = DRM. No.

A true DRM would mean implementing something along the lines of data encryption, and perhaps having content creators register with LL and generating  encrypted keys with a hashes unique to their avatars, and then some means of associating these keys with the content that would reduce the content to scrambled garble when some other avatar tried to copy or pull in an encrypted resource via its UUID.

I don't even like the term DRM (Digital Rights Management). People get confused quickly and don't understand how the lower level software works which usually includes the operating system's permission system.

I have a feeling though, that this is a sort of thing LL really wanted to avoid having to implement.

Well, in my opinion the SL platform is was created for geeks.. or those whom believe they are. The software and platform doesn't appeal to everyone. But for many, the technical aspect(s) of what we have with SL is pretty exciting.

Implementing this sort of "closed minded atmosphere", even taking on the appearance of closing doors to technology advancement via open community standards, open involvement, and open ideas would be rejected by a large number of people that use SL. Just my take on it. If it were not for the open source SL Linux client, I wouldn't be interested in SL.

And my take on DRM as a flawed concept is, it's just another dimension of the "bigger wall, taller ladder" security game that has beset the proprietary software model for years. It's great fodder for copyright attorneys though - after all, they have kids to put through private school too!

I couldn't agree more.

 

I feel that any creator that

I feel that any creator that is a little tech savy already understands that there is no absolute security and that is not what people are asking for. The amount of theft will rise and fall with both the ease it is possible to conduct theft, and risk of repercussions involved. The easier it is to obtain and operate a tool for thievery and the smaller the chance of being caught or not having suffer consequences that have a bearing on the thief, the more it will prosper.

So while it's true that there is no absolute technical solution to the problem, what the technical side very well can do is eliminate a large number of 'casual' thieves by not making it easy to do and possibly provide means to increase the chances of a thief getting caught. To use an analogy thats been brought up a few times...Locks on doors arent meant to absolutely stop burglars. They do however make it more inconvenient. A small lock on a door will mean you need to kick in the door (makes noise and increases the chances of being caught) or have knowledge of locks and tools to break it silently. If there is also an alarm the person to break and enter will also need knowledge of alarm systems, thus reducing the number of potential criminals to those that are willing to take a greater risk or have knowledge of all systems in place.

As you can see from above example, the second component to the locks being a workable means to provide *some* security are the repercussions one might face for commiting a crime. In the first stage it is the responsiblity of grid operators to take a stance against violators, both by letting the populace know that it is not an accepted practice to steal and by taking strong action against those that do get caught. Turning to court frequently is an approach to solving disputes that is a common practice in the US, and indeed US citizens turn towards the courts far more frequently than for example europeans do. It's a longwinded, costly and risky process that should be reserved for the most servere cases but surely it cannot be the one and only means to solve problems of microeconomies like SL and future grids.

The outcome of an opensource project stands and falls with it's community, and i hope that most will agree with this sentiment. While i can understand the 'we want to get our things out of SL' sentiment, the approach with which this is done quite surprises me. 3D worlds are a symbiosis of technology and content. To be sucessful they need both. Sure content can be taken from SL, legally or illegally as has been prooven time and again. The question that arises to me is, do the pioneers that seek to build better world without LL and their policies really care so little about their own project that they are staggering it's success with a strange 'fuck all' attitude displayed by some. Providing some security to content where LL has failed to act thus far, would be tremendously beneficial to the project and bring residents, sim operators, supporters and attention to the project.

I know some may think that security is not their concern, but i feel that providing *some* security is both a key issue as well as a great opportunity for the OS project. The bottom line is, where will people go? To the places where all the stolen shit from SL is (some will *nod*)  or to grids where they feel a sane level of security?

 

RightAsRain Rimbaud wrote: "I


RightAsRain Rimbaud wrote: "I think we have seen enough wild accusations and pathetic attempts to slander us."

I find it hard to imagine any slander that could do more harm to your reputation than you have done yourself over the last three days.

RightAsRain Rimbaud wrote: "I think it is best practice not to say anything on the web that you wouldn't say to a person in their face."

If you had told people to their faces, "we are planning on releasing a tool to facilitate easy and quick theft of your creations", I suspect you would have gotten equally hostile responses.

RightAsRain Rimbaud wrote: "I would urge people not to slip into their twisted world of frustration and allow dark thoughts to overwhelm a more balanced, caring approach to people. Stay positive."

You took out your fustration over your company's failure in Second Life by declaring war on the thousands of moderately to hugely sucessful creators there. Does that sound like be a "positive" "balanced" and "caring" approach.

You've been treated with about as much respect and consideration as you deserve over this issue. That fact that you can't see that is the core of the problem.

 @Aveline SteinEven if

 @Aveline Stein

Even if drawing analogies between computer securities  and real home security it's just not that clear cut, penetrating in a system does not require skill, it only take skill to devise the first tool for it, after it's just a matter for any clueless person to open a program and push a button.

Hundreds of websites get defaced everydays not due to the high skill of the defacers but by exploiting known vulnerabilities in the software.

 

When it comes to computers and networks, once a security system is cracked, it's cracked for good and anybody with the proper tool will be able to make short work of it with the same efficiency as the cunning person who took the time to crack it in the first place.

The question really is that are you willing to devote a significant amount of resources to play the arm race with hundred of tousands of peoples that will see it as a challenge to break?
It means devoting significant amout of time, and money to build a protection only to see it broken and make a new one.

In my opinion, a software engineer that advocate this kind of temporary solution is either dishonest or trying to ensure he keeps his place permanently in the company.

Personality Based Organization

i wasn't privileged to invest in the "OpenSpace rip-off" (and subsequently abuse it to serve my own greed, then blame someone else for my own lack of ethical restraints when the responsible party releasing the product reigned in the abusers). Jack Linden on Openspace Policy as stated to those who couldn't avoid the chore of reading (i know, it's much easier to just work around someone elses imposition of RULES) the Lab misread the burgeoning greed of a core of residents whose stock in trade is to cheat.

i don't mean to get personal RaR, just reading your slur/opinion about the "rip-off" validates my suspicions that Prok summarized succinctly with her analogy (which should be written large and everywhere in the OpenSource community, imho). "...elevating stable boys and garage mechanics to the level of influencers and decision-makers ...".

my own impression of Open Source code isn't as egrecious as what she followed up with. there are super coders who have committed their entire being to gifting the community with their work and God bless their pointed little heads. unfortunately, we're all merely human and emotions and reactions can belie our best intents. responding to personal circumstances hidden to an apparently organized & managed entity (as Rezzable purports to be) serves Prok's point. this is not to say independant coders are mere servants. it's to illustrate that without responsible (morally responding to) management over your products expectations and responses to your gifts may not compute. we wet bodies are not all that unpredictable. thanks for asking though.:-)

as with any organized management of a commercial product, someone within that structure is bound to pipe up with: "hey, that might not be acceptable to the greater community". it's not reading tea leaves. it's listening to your heart and compatriots. mooshing a cooperative build into anonymous creator objects (hey that's a service too!) should have given someone in your organization a heart attack once they were aware "they" were releasing it to the community. if your organization is personified by you and you alone execute policies over the rest of the voices who do your bidding (code) i believe my suspicions of your character and ability to read/sense what is right and wrong are being reinforced by each post and comment you make.

if you are serious about feedback, i'd like to hear how you will move this product along. first amont my concerns, as has been earlier stated, is how would one's creator status follow a rebuild? or is that of any concern to you presently?

Kryrah wrote...

Kyrah you may call me naive but isnt that how even opensource software also works and how it benefits from the 'more eyes are better' principle? Yes stuff gets broken, but yes it also gets fixed. And if i am looking at my linux laptop there is barely one day that goes by where there isnt a patch to this or that, *and* more often than not, patches are out before a security hole creates huge mess on systems around the globe. Patches are written by people that have interest in their own security and systems. Does that mean the security is absolute? Certainly not, but it one of the major advantages OS has over slow cooprorations providing software whos interest solely lies in the money they make.

You wrote that: "The question really is that are you willing to devote a significant amount of resources to play the arm race with hundred of tousands of peoples that will see it as a challenge to break?
It means devoting significant amout of time, and money to build a protection only to see it broken and make a new one."

Do you have a login on your computer? A router and/or firewall? Do you use ssh, https or encrypt passwords on your website? Do you secure your wireless? (now *that* is really useless, is it?), Do you use PGP or keep your system updated? Because if i were to follow your logic, you should not be using or doing any of it as there is no point. It's there so it can be broken, why bother? Or IF you are using any of the above, why do you do it? Isnt it out of the same  reasons creators are asking for means to help reduce theft? To fend off the majority of simiplicistic villians?

I am not proposing this to a company, nor am i with any company or so dependant on SL that i would commit suicide if it all went to hell. I am a smalltime creator that has fun building and gets frustrated when i see people taking my things. If they had asked nicely enough in the first place they *may* even have gotten what they wanted in a legit way. Back to the point, i am proposing to the community that security certainly *is* a topic, not a one time project but an ongoing one. Much work? Yes definately(!), but it is my deep and honest belief that it is one of the key issues that can make this thing really fly.

Perhaps it is not time...yet, but i do hope that some of the fury and vengance against LL does not ruin it all before the time comes. I for one would love to see virtual worlds grow, and be a part of it, rather than see it all go boom over stupid content wars and non existant security which make the whole thing about as desirable to visit and use as a phishing site to most people.

It is good see people make

It is good see people make comments above about trying to clarify some of the licence and technical issues. I think it is very helpful and gives some useful insights into the details that actually are critical here.

Without trying to rehash a lot of points that have been already raised, I would say that our intention was and still is to provide a tool that has been useful to us to the larger community.

We built it using libomv which is opensource and someone else can also do something simillar within a short enough period of time. Our initial idea was to share this back--free and open--the way libomv is. We think still that in terms of software development that this is the most productive course. We can also understand the concerns of people that may feel this tool might cause larger scale unlicenced content copying and so we will make some changes to our plan. 

Most creators, including Rezzable, are already exposed to content theft. BuilderBot may add some risk of more theft as we advised in our initial post asking for feedback. We hope that the benefits to creators outweigh this risk. It would seem that the comments on the usefulness of the tool support this, but we will see really how many people are willing to pay for a licence in future for a product that will be more restrictive.

@ Carl, sure we have issues with LL. I don't for one second think our experience or operatons in SL are or have been a failure.Those were never my words and I reject that claim.  Quite the opposite. We have been fortuntate to have had a great run in SL, making a wide range of stunning areas, running popular sims, hosting large scale events, making machinimas, sponsoring fashion events, showcasing amazing art work and of course working with some of the best people.  We have sold tons of stuff and had millions of avatar visits hit our areas.  For a lot of reasons, now is the time for Rezzable to move-on. Others have left SL, others wiil. I don't think our departure (notwithstanding Greenies which will stay) is that remarkable.

It was never my wish to harm the people that use SL or damage business for creators and I hope our actions here will speak to that point.


So....you do intend to

So....

you do intend to release software tools that are designed to remove CMT settings as it copies all content within a particular sim?

you then intend to "sell for profit toward rezzable" a version that is limited " to only copying a creators prims or with some sort of CMT checking" within a particular sim.?

Do i have the "facts" correct?

 

walter

@Aveline SteinYou are missing

@

, protecting a system against intrusions is one thing, you have a remote user and wish to deny him access to your system.

The issue at hand, said user is already logged in and is allowed to receive the content (we want him to be able to see the textures and prims around him), there is no question in protecting the system against intrusion.

Here we have some peoples that argue LL should harden the SL viewer and/or forbid any non autorised viewer. The essence of the problem being that the viewer is running on the user's system. Usually, it's the user who own and is the "admin" of his computer, not linden labs, and thus the user can run pretty much anything on his computer, including programs that can pull prim data and textures from the sl viewer memory, you can't control what the client's computer do with the data once it land on his computer.

There isn't much that can really be done against this part because it's like putting "secure" bolts on your customer's car. He can always drill them open, it's his car after all.

Dumb question.

Dumb question:

Isn't it against Linden Lab terms of service / community standards to do anything that breaks their permission system?

Kyrah, i am reasonbly aware

Kyrah, i am reasonbly aware why it is so difficult to make this thing a little more secure is so 'impossible' as you put it. It's quite obvious that the problem isnt one that is easily solved. Yet i do feel that there got to be some, maybe crazy solution or idea out there that composes of the levels of technology, gridoperators' and user/creator/community behavior or practice that would make things a little better for everyone, and that doesnt totally cripple or ruin something else. And i do think that once there is very strong interest, a solution for 'better' security, working across all levels, could be found.

Call me crazy, the earth is not a disc.

ridiculous mentality

Dear all you people who think that releasing tools such as this is harmful:

You do not understand technology, do you?  This is a tool, and it's not a tool for content theft.  Only an idiot would say that all paperclips need to be made out of non-malleable alloys so that they can't be bent into lockpicks.  So why would you say that this software needs to be closed source?  People will copy shit from second life.

To these clowns who think that censoring software tools will actually help protect your content: EVERY TIME AN AVATAR VIEWS YOUR CONTENT, HE IS COPYING IT, IN IT'S ENTIRITY, TO HIS COMPUTER.  Let this sink in, because it's true.  That's how the thing goddamn works.  I can't see your dumb build if Second Life's servers don't send it to my computer.  My computer can only show me things that are on my computer.  That is a fundamental fact about how computers work.

If you think that any of the designs you make in second life are safe from copying, you are every bit as stupid as the web developers who back in the old days whenthe net was young, thought they could protect their images with transparent overlays or anti-right-click javascript.  They are, of course, wrong, and stupid, and I have all their images.

To extend the metaphor, asking a developer to bottle up a second life tool because you don't like the fact that it can steal your prims, makes just as much sense as asking web browser developers to disable the "view source" menu.  It's friggin' retarded, and anyone with some competence will be able to cheat anyways.

This software does not break Second Life's permissions.  Second Life's permissions simply do not extend beyond the confines of their own servers.  Second Life always gives the content to the viewer full perms, out of technical necessity.

I guess it's already been decided to make this project closed source, but that's okay.  Somebody else will see it, like it, and make an open source one.  All of you luddite content creators have already lost the war against content copying, given that CopyBot has yet to magically stop working.  All you're doing now is fighting a losing war against freedom.

@hiro

That's a good question Hiro, and the answer is: "Yes it is against tos to break the permissions system." Technically though tools such as builderbot doesn't break permissions - but like any tool which can shift or display content, it is capable of ignoring permissions if not designed to heed them. All the actual permissions magic is done on the server side by the lindens - builderbot doesn't actually break anything server side. It purely acts as a client. (It's a tricky and technical distinction, but DCMA law covers what actually constitutes "breaking" or circumvention of DRM and this isn't it.)

The lindens certainly see tos violation in such permission breaking activities as the old "dupe exploit" - where unscrupulous folk would put a bunch of items out on a sim, take them to inventory, crash the sim, then pick up the copies left after a reboot. Such exploits are a hack of the linden servers and actually do "break" permissions by producing perfect copies of entire objects with their scripts intact. Using the "dupe exploit" is effectively hacking of the LL servers and thus not tolerated. So exploits such as the one I just described certainly violate TOS. 

However, permissions only exist on the linden grid itself and any opensource viewer can choose to ignore them client side. Once the data has left the server it is outside the linden permissions system. It then becomes a legal matter about the use of the content rather than a technical "breaking" of permissions. Permissions client side work on an honors system - opensource clients generally implement permissions just like the linden grid, but occasionally (truth be known) ignore permissions to get the job done. Generally this is done invisibly, and the user experience implies that no such bypassing of perms is taking place. 

Creating full sim backups as builderbot does is quite difficult, and builderbot went through quite a few iterations before rezzable was confident that it could transfer all of the content we had created. The only prims i'm aware of that were transferred onto Rezzable grid but _didn't_ directly create or comission were the megaprims we used in our builds. (Opensim allows us to create prims of any size, so technically they aren't the same prims per se... only the size has been copied.Come to think of it I did comission some megaprims during the second round, but they weren't used in the initial greenies build.)

Apart from the creator name, and the size of the prim however, all of the actual artwork and torture of these megaprims was done by comissioned artists. (All megaprims are created by a select few hackers and shared as libraries - they're just big prims, but the name of the originator stays stuck to them.) Megaprims thus present an interesting grey area where non-team builder names can creep into a build (as creator) and cause perms problems for any system that enforces creator dependancies. The permissions system makes it difficult to deal with such an issue, and the closed Linden grid means such builds once moved off the linden grid, can not be reconstructed as we can't make megaprims at will. Megaprims are one of many problems to solve in sim duplication where the task falls outside of the classic intent of perms in protecting creator content.

There's plenty of other places where inadequacies or quirks of the permissions system (or other SL quirks) put a stop to doing backups if adhered to absolutely. The role of a backup system however is to finish the job - by brute force if required. It does nobody any good to have a backup system one then needs to go over with a fine tooth comb to see if everything has transferred correctly. Such a system could not be relied upon for incremental backups for instance. During the development of builderbot the artists that work for rezzable spent a LOT of time checking the transferred builds to ensure every detail was transferred properly before they developed a reliable system. 

So it is my belief that what builderbot does doesn't violate Linden TOS. The Lindens have made many statements about the difference between legitimate copying and what they consider a violation - namely hacking their servers directly, or engaging in  actual criminal copyright infringement. To quote them: We’re sometimes asked why Residents are allowed to have or sell copying devices.  The answer is that there are legitimate uses of a copying mechanism.  It’s the infringement that we don’t allow and won’t tolerate. (From https://blogs.secondlife.com/community/features/blog/2008/04/11/protecting-your-copyrighted-content )

Mr. Kharg,The following is a

Mr. Kharg,

The following is a list of your failures in the last post:

1. Ad hominem. Your post reeks of personal attacks.

2. "Only an idiot would say that all paperclips need to be made out of non-malleable alloys so that they can't be bent into lockpicks." - straw man. A paper clip is designed for job X (namely, clipping paper), and picking locks is job Y. Further, to use a paperclip for job Y, it must be deformed to a point where it will almost definitely never be able to perform job X again. Software that copies content being used for copying content is, in fact, a tool with inteded use X being used for use X. The difference is that the job can be performed on your own content or someone else's. For example, I can use a screwdriver to take apart my laptop. That's fine. If I use a screwdriver to take apart someone else's laptop, that's not so fine.

3. "EVERY TIME AN AVATAR VIEWS YOUR CONTENT, HE IS COPYING IT, IN IT'S ENTIRITY, TO HIS COMPUTER. " This statement is a technical fallacy. Visualization of data is not the same as the data itself. If I give you a cake, that's not the same as giving you the recipe to the cake. In the case of Second Life, some of the data is, as you point out, transmitted to the end-user's computer. However, not all of it. I realize this may be splitting hairs, but since you went to such a point as to put it in ALL CAPS, you should probably be sure to not make misleading statements that are not entirely true.
 

4. While you're correct that, indeed, content in Second Life - at least, the graphical elements of it - the rationale of "if it's possible, it's okay" is simply nihililst and pretends that social contract and laws don't exist.

5. "Second Life's permissions simply do not extend beyond the confines of their own servers." In the literal sense of "this data of whether something is no-transfer, no-build, etc is only on Second Life's servers", you're ... wrong. This same data is transmitted to the viewer. If you mean it in the figurative sense of "Second Life permissions only apply to data on the Second Life servers"... you're wrong. The permissions have to do with their use, per Terms of Service / Community Standards. Linden Lab's Terms of Service - scratch that. DMCA law indicates what is and is not appropriate fair use. Redistributing data without permission is not fair use.

Now, I'm not an advocate for extreme control of data. My personal belief is that as long as people are using data for personal use, and are not avoiding purchases that they normally would be making, if data's shared by the creator, then it's fair use. So, as a backup tool for content that you've created yourself, I see no reason why BuilderBot would be offensive. Or CopyBot. Or whatever. But should the software be used as a "You bought stuff for use in Second Life, but go make a copy and bring it to a private grid", it gets sketchy. And should the software not even do any basic checks for permissions (as any file-copying tool would need to do in say, a Unix-based environment), then the software does, in my opinion, violate terms of service / community standards of Second Life. I'm not a lawyer, but I've been pretty good at following along virtual copyright cases and predicting results.

6. "Second Life always gives the content to the viewer full perms, out of technical necessity." Incorrect. It transmits data along with a clear set of Terms of Service and Community Standards, as well as the permissions, to be used together.

6. "All you're doing now is fighting a losing war against freedom." This statement is loaded with assumptions. You assume this "war" is "stop all content theft" and that "freedom" is "all data is free".

The first problem is that the objectives of many of the people who've left comments is not to "stop all content theft" but to (a) prevent people from making non-trivial amounts of money off copyright theft. Anyone can steal a little, but to steal a a lot and make good money takes a lot of effort that can be easily seen and counteracted. (b) prevent precedent from being set of easy-to-use Second Life copyright-circumventing software from being seen as permissible. Both of those goals are goals that, in fact, people are winning.

The second problem is the idea of "freedom" is only one freedom. There are a variety of freedoms involved. Ones your "freedom" doesn't include is people to create content and be free to do business without content theft. Freedom, in the genuine sense, includes individuals being able to create Intellectual Property, own that property, do what it they like (without interfering in others' freedom) and not have this infringed.

Data and truth doesn't seek to be made free. It has to be actively pursued. The concept of the ideal that data ought to be free as a value in and of itself conflicts with other values. To make a blanket statement and refer to data freedom merely as "freedom" with no qualifiers is simple rhetoric.

7. Learn to be polite. Don't refer to folks as "You people". It's condescending, and so is your entire tone. If you're here trying to make a technical point, you're going to win no fans by being hostile.

Oh boy I love point-by-points!

Dear Hiro:

1. Yeah.

2. My point was merely that a product should not be crippled in the name of preventing abuse.  I have no problem with tools like this performing permission checks, but if it's closed source, then it won't be able to be repurposed for other tasks.  I have no idea what point you're trying to make with "Further, to use a paperclip for job Y, it must be deformed to a point where it will almost definitely never be able to perform job X again," since we're talking about software.  When you fork a piece of code you don't lose the original.

3. You're right.  It doesn't send scripts to the user's computer.  But the software doesn't claim to copy scripts, so that's irrelevant.

4. I did not say content theft is okay.  I do not engage in or condone content theft.  What I do believe in is free exchange of information, and that if a tool can be written to do something, then people should have that tool.  If you think that supporting a tool equates to supporting a given use of the tool, then you are pretending that censoring individual tools will solve the problem.  All that mentality does is lure content creators into a false sense of security, and set them up to do massive amounts of whining when another tool comes out next week.

5. Actually I did mean in the literal sense, but not quite how you interpreted it.  Real data is never no-transfer, because there is no such thing.  There can only be artificially no-copy data within a set of trusted hosts.  If there were a magical solution so that this content could actually be protected against copying, without inconveniencing legit users, then I would be all for it.  But there's not.  It's an impossible problem.  That was my point.  Again, I know that stealing is wrong and illegal and yadda yadda yadda and I don't encourage it.

6. "Freedom" is what it's called when there is open source software readily available for any purpose.  I didn't mean "freedom" as in "I stole all your prims and made them full perms so now they are free."  And easy-to-use copyright violation technologies have, throughout history, always been seen as completely permissible in the end, because easy to use copyright violation technologies also happen to be easy to use technologies for completely legitimate purposes.  Hell, the RIAA tried to stop consumer cd burners.

7. Eh, well I was in a bad mood because the "you people" in question just talked a would-be open source software developer into closed-sourcing a would-be useful project, for completely nonsense reasons.

ToS Addendum. You mentioned Linden's ToS several times.  "Terms of Service" are just that.  They aren't any sort of legal contract, and the only sort of retribution a company can actually take out on you for violating them, is terminating the service.  Making and releasing software can't violate the terms of service, for the simple reason that they are terms of <b>service</b>, not all-encompasing rules of the universe.  They have no significance outside of the service for which they are the terms.

@Pavig

Excellent technical exposition, many thanks for posting that.

"...our intention was and still is..."

"Without trying to rehash a lot of points that have been already raised, I would say that our intention was and still is to provide a tool that has been useful to us to the larger community."

You need to change your mind about that.  Providing this tool will make Rezzable business ventures a constant target of legal scrutiny for any copied content.  Perhaps you imagine you're ready for that, but think carefully about that and you'll know you're not.  Is every sim on Rezzable's grid completely devoid of any Linden textures or animations, for example?  How many full time employees are you willing to devote to processing DMCA notices, to keep your hosts on the net?

"BuilderBot may add some risk of more theft as we advised in our initial post asking for feedback. We hope that the benefits to creators outweigh this risk. It would seem that the comments on the usefulness of the tool support this, but we will see really how many people are willing to pay for a licence in future for a product that will be more restrictive."

Do you really think the supporting comments come from people who fully understand the legal implications of what they're doing, and the consequences to themselves and their service providers (Rezzable, in some cases), when they copy any unlicensed content from the Second Life grid?  I very much doubt it.  Many erroneously assume that having content permissions in Second Life grants them the same permissions on another grid.  You know it doesn't, but you also know that many will migrate purchased content outside the Second Life service, in violation of the Linden ToS.

That makes Rezzable vulnerable to legal action, both in the above-cited instance of DMCA enforcement, and in providing a tool that populates Rezzable's own for-profit ventures with infringing content.  The instant that a copied texture rezzes on the Rezzable grid, any defense that "it's just a tool for builders" is lost.  Starkly put, it becomes not just old-school Napster, but piracy-for-profit--not just civil liability, but criminal.

The end result of such a course of action would be to forever prevent Rezzable from hosting content.

 

 They should have released it

 They should have released it anonymously, but i think they kinda wanted the PR stunt

"Providing this tool will

"Providing this tool will make Rezzable business ventures a constant target of legal scrutiny for any copied content."  No it won't.  There is absolutely no legal precedent for a company being held responsible for what people do with their software, if the software also has legitimate purposes.  If on some off chance somebody managed to file a suit and the judge was drunk at the time and Rezzable lost, then the American Civil Liberties Union would support Rezzable in higher levels of court and win, because the ACLU is a wonderful organization which protects freedom of speech.

Wrong again.

@Kharg

Once again, you're showing that you're not doing much thinking or research before you type.

"There is absolutely no legal precedent for a company being held responsible for what people do with their software, if the software also has legitimate purposes."

Napster? Pirate Bay? And don't give me the "they don't have legit purposes" excuse - there's plenty of free-to-share files that can and were shared on both.

"the American Civil Liberties Union would support Rezzable in higher levels of court and win"

They would, eh? You've got a few problems with thaat. The first is that Rezzable is based in London, England, UK, which, as far as I know, is still not aa part of the United States of America, which is where the ACLU operates. Assuming the lawsuit was American-based (maybe the Philadelphia operating wing of Rezzable was sued), I haven't seen anything virtual world related hit the ACLU's radar. But assuming it did, ACLU really hasn't been focusing at all in software law. (http://news.cnet.com/2100-1025-996245.html may have had something to do with it.)

"because the ACLU is a wonderful organization which protects freedom of speech."

ACLU also doesn't have a blanket "we will defend all freedom of speech issues". They're quite opposed to, for example, church and state entanglement issues. (like when they sued to get the cross off Los Angeles County seal). So making a statement like this doesn't add anything to your argument.

If you're going to articulate an argument why Rezzable should release the software, you may want to take note from Pavig Lok. While I may not agree to all his points, Paviq states a case and supports it with rationale evidence, rather than relying on rhetoric and half-researched half-truths.

 

@ Qie-- providing a tool

@ Qie-- providing a tool and/or a service does not bind the provider to the use of it. Otherwise Linden Labs would be in court all the time for the activities it profits from in SL that result in disputes between parties using SL. I think actually LL has been able to prove that their service is a utlity and not party to things like under-age sex, illegal gambling, content theft etc.   On the content ripping issue specifically Linden has been able to avoid being called into many cases where the people that have been ripped off actually did win. Dell computers doesn't get sued, Adobe or Google when people take digital content and abuse it.

Legitmate uses of copy content are clear. And no we didn't take anything from SL and OpenSim has its own libraries. But I don't think LL would be too worried about people taking their plywood textures. There needs to be some benefit from having copied stuff and then used it to justify a legal action. So actually taking a copy is not the most serious part--using that copy without rights is where it becomes the problem.

And what is the other side of your point then? Should we just keep it and use it for our friends and people that we personally know and trust? I don't think that is fair either. So then we should all cater to the abuse of rippers and the fear of armies of unknown lawyers enforcing scary stuff.

None of this would be an issue if Linden Labs provided an adequate service to content creators to back-up, archive and export their stuff.

Interesting article from

Interesting article from Peter http://www.rezmagazine.co.uk/2009/07/short-history-of-copying.html and he links to another good piece here about Copybot issues: http://rikawatanabe.wordpress.com/2008/12/22/on-copying/#comment-341

"None of this would be an

"None of this would be an issue if Linden Labs provided an adequate service to content creators to back-up, archive and export their stuff."

No.

None of this would be an issue IF YOU HADNT entered into a service agreement with the service expectations "offered" by Linden Lab.

There was no mandate for you to spend time of money in their service, you did it for your agenda. That was Fair.

There is nothing NOT fair about you keeping your tools you made for yourself.

Such a shame for professional content makers/ and designers that you chose to use the "same worse" methods that Linden Labs uses  to " talk at"  many who already take responsability for their actions in using the SL service. FAIRNESS is allowing fhose who choose to create in 3d media online in ANY of the methods offered for over a decade ,to do so on their agreed terms.

Web3d has been online for over 15 years in many forms. Linden Lab offered one only, you chose to use it, and frankly you seem to have received more than your "fair" share of it's potential value.

Others can make their own decisions with the "consideration" of Linden Lab failings on their own. 

Thank you for your expertise and opinions about the value of your work, but allow others the same within the same agreements signed.

Yes, backup should have been an early SL consideration if they truly were "as" interested in the users services and longer term agendas, "as" their own at LL. Sadly , as it appears again, that type of fairness is rare.

Cube3

@Encore Mayne, try

@Encore Mayne, try researching what happend over Openspaces before believing the balderdash you post, try Jack's forum post in 2006. Try Zee's blog post in July 2008, try the umpteen office hour logs about the subject before you call people who followed advice from Linden Lab greedy.

@Hiro"Napster? Pirate Bay?" 

@Hiro

"Napster? Pirate Bay?"  The key technical difference is that these are data services, not software products.  If Rezzable actually made this a service and had an error in protecting content, then they might be liable.

Napster

Napster originally was not a data service. It was p2p software.

 

MegaPrims

To RightAsRain,

Most large builds in SL use megaprims extensively these days.  If the BuilderBot cannot be used to backup these then it is pretty much useless for the purposes of backing up large builds in SL.

As you probably know Megaprims cannot be made with the builder's name as creator, so the tool will have to allow backing up all you *own* as opposed to all you have *created* or fail to backup vital parts of a large SL build.

MegaPrims

To RightAsRain,

Most large builds in SL use megaprims extensively these days.  If the BuilderBot cannot be used to backup these then it is pretty much useless for the purposes of backing up large builds in SL.

As you probably know Megaprims cannot be made with the builder's name as creator, so the tool will have to allow backing up all you *own* as opposed to all you have *created* or fail to backup vital parts of a large SL build.

Sorry for the multiple posts,

Sorry for the multiple posts, I had issues when posting, please remove the duplicates.

Welcome to the Newly Acquired Conscience Society

I stand by what I said, and what I said is in fact a giant pushback to the sheer wilful and malicious arrogance we get from coders, starting with RightAs Rain and his gaspingly atrocious act here.

Once again, anyone who pushes back against the tech-thugs is then themselves accused of "forcing their opinions on others" or "arrogance".

I just can't be concerned about your beliefs in this regard precisely because there's a very urgent public task here which is to counter those who originate with the malice and the aggressiveness. No, code is not law; coders are not rulers. And indeed *they will* learn their place just like stable boys and garage mechanics. Stable boys and garage mechanics might well be noble professions and needed professions, but not when those in these jobs imagine they rule everyone and lord it over everyone and even sabotage things.

Coders are the garage mechanics of this century, imaging they have everyone over a barrel, dependent and queuing up to them. It's about putting the entire role into perspective -- and indeed into place, big time.

There aren't any "threats" in my comments but pragmatic statements of fact. Coders *are* too arrogant, aggressive and even malicious, imaging that the exigencies of technology enable them to destroy others' value and property. We've seen an appalling criminal act here perpetrated by RightAsRain which is symptomatic of a whole class warfare he and his gang are constantly waging on other people. And it's wrong. And I for one will fight it, and fight it hard.

You're weepy concerns about people aggressively imposing their views was utterly missing on the first threads where RightAsRain airly announced he'd be imposing his copyleftist technocommunist views on the entire population of Second Life. Hello? And you were missing in action. THAT didn't bother you, though you "support musicians and content creators".

Where were you when Kyrrah Abattoir was threatening "repercussions" if a JIRA expressing concern about builderbot was not closed to her whim? That's the sort of thuggish threat you have to be concerned about, not me comparing RightAsRain to a crude stable boy and an arrogant garage mechanic making others dependent on his whims.

Welcome to the Newly-Acquired Conscience Society.

 

 

 

Freedom of speech of the sort

Freedom of speech of the sort defended by the ACLU does NOT entitle you to "incitement of imminent lawless action." The Supreme Court of the U.S. hs ruled that the First Amendment does NOT protect incitement to imminent lawless action. The  case often cited is "shouting fire in a crowded theater".

RightAsRain's original and even subsequent posts are incitement to the imminent lawless action of copyright theft.

@HiroActually Napster only

@Hiro

Actually Napster only got sued because they had a centralized indexing server, ie, data service.  It was not a decentralized system.

 WOW just WOWProk stop

 WOW just WOW

Prok stop putting words in my mouth please, 

 

"Where were you when Kyrrah Abattoir was threatening "repercussions" if a JIRA expressing concern about builderbot was not closed to her whim? That's the sort of thuggish threat you have to be concerned about, not me comparing RightAsRain to a crude stable boy and an arrogant garage mechanic making others dependent on his whims."

First, you could at least try to write my name properly if you want to slander me.

Second, what i ment was simply that if you piss off the opensource developpers who worl on the SL client, there are plenty of other projects that will benefit from their expertise.

Personally if a company says me "hey come fix my stuff for free" and at the same time tells me "Umm thanks for the help but we don't want you to make this modification, now get out", I will go waste my time elsewhere.

You know, symbiotic relationships are kinda like a two way street.

ok abbatoir..so why wanting

ok abbatoir..

so why wanting to have a jira closed expressing concern about builderbot?

 

 

 

If someone copies my work

If someone copies my work without paying me for it, regardless of what they do with it, I have been ripped off.

If BuilderBot is released with the capability to copy content that does not belong to the BuilderBot's owner, that is what it will be used for. It would be unrealistic to expect otherwise, and perfectly logical to assume Rezzable sanctions the activity.

 

 

@Prok:"Once again, anyone who

@Prok:

"Once again, anyone who pushes back against the tech-thugs is then themselves accused of "forcing their opinions on others" or "arrogance"."

No one is denying you the right--nor the ability, it seems, since you're still able to post on Rezzable's response wall--to express your misgivings about BuilderBot, content creator's rights, or RightAsRain's actions.  What most people who have responded to you have been trying to point out is the TONE with which you express your displeasure.  It is entirely possible to state your piece without stooping to the level of name-calling ("tech-thugs", "copyleftist technocommunist", and other interesting ones I've seen you use).  THAT is the point I was trying to make, and others.  I have no problem at all with you being against BuilderBot or anything else; I'm not so arrogant as to assume that everyone else must agree with me or they're dead wrong.  You might try to step back and try the objective-vs-subjective thing from time to time.

"I just can't be concerned about your beliefs in this regard precisely because there's a very urgent public task here which is to counter those who originate with the malice and the aggressiveness. No, code is not law; coders are not rulers. And indeed *they will* learn their place just like stable boys and garage mechanics. Stable boys and garage mechanics might well be noble professions and needed professions, but not when those in these jobs imagine they rule everyone and lord it over everyone and even sabotage things."

No, I don't think anyone wants the coders, stable boys, and garage mechanics of the world to overthrow society as we know it; I just don't think that most of them are exactly gunning for that end.  Arrogance on the part of those in a management position is no better than arrogance on the part of the one doing the dirty work; all it ends up being is arrogance for its own sake, and either way it's bound to piss someone off.  A little humility goes a long way, regardless of your profession.

"Coders are the garage mechanics of this century, imaging they have everyone over a barrel, dependent and queuing up to them. It's about putting the entire role into perspective -- and indeed into place, big time."

Generalize much?

"There aren't any "threats" in my comments but pragmatic statements of fact. Coders *are* too arrogant, aggressive and even malicious, imaging that the exigencies of technology enable them to destroy others' value and property. We've seen an appalling criminal act here perpetrated by RightAsRain which is symptomatic of a whole class warfare he and his gang are constantly waging on other people. And it's wrong. And I for one will fight it, and fight it hard."

Fight what?  "We've seen an appalling criminal act here..."  So far, the only act I'VE seen is RightAsRain asking for opinions about a software tool he's made that happens to have both very positive capabilities (if used for its intended purpose by an honest person) and very negative capabilities (if used for unintended and illegal purposes by a dishonest person).  Is it a criminal act in the US--or the UK, where Rezzable is located--to ask for feedback about an as-yet-unreleased piece of software?  Fight it if you want, but I don't know of too many courts that will convict someone for the heinous crime of asking for feedback.

"You're weepy concerns about people aggressively imposing their views was utterly missing on the first threads where RightAsRain airly announced he'd be imposing his copyleftist technocommunist views on the entire population of Second Life. Hello? And you were missing in action. THAT didn't bother you, though you "support musicians and content creators".

Where were you when Kyrrah Abattoir was threatening "repercussions" if a JIRA expressing concern about builderbot was not closed to her whim? That's the sort of thuggish threat you have to be concerned about, not me comparing RightAsRain to a crude stable boy and an arrogant garage mechanic making others dependent on his whims."

Where was I?  I'm currently deployed in Iraq, Prokofy.  I'm sorry if that means that I can't rebut and debate as quickly as you seem to prefer, but I have other concerns here that trump flaming message boards on the internet.  I get online when I am able.

As I've said before, I'm not a coder, or business owner, or content creator in Second Life.  I'm just an average user who occasionally buys things he likes and tries to support the originators of that content when I can.  I don't apparently have the lofty view of the matter at hand that you seem to deem yourself in possession of; but I have an opinion which I am just as entitled to as you are of yours.  Keep this up, if you want to; for my part, I *refuse* to stoop to the name-calling game or unnecessarily lacing my rebuttal with negativity under misguided notion that it somehow makes my argument "stronger".

"Welcome to the Newly-Acquired Conscience Society."

Funny, I don't feel any different.  Ahh, that's right... I already have a conscience.  Thanks anyway.

Phantom Spear... The stripper....

"Phantom Spear the stripper"

When I started second live in or around 2003 or 2004, I was astonished at the work that I viewed. I was continously trying to wrap my mind around how this all worked. And today, I still do to some extent. Opensim has helped me quite a bit understand about how difficult it is to provide what Linden Lab has done as pioneers of the industry. They have produced something not seen before. Nothing of the sort had existed, and technically minded people were in awe.

I started off as an avatar named Phantom Spear. A pole dancer whom knew nothing of the sl platform or what I had seen on a television show advertising Second Life.

As a man in his mid 40's in female clothing, dancing, and having a good ol time with it. I loved it. The best skins, the best available in SL is all I would buy. I really did enjoy having fun and never took off the avatar clothes, just danced with the best of the best scripts and animations that money could buy. And put on one heck of a dancing show.

I also went to peoples areas not knowing how things worked really. I did some not so good things and ran around sims with a few things that created issues for others. Being a female in SL was harder than I had imagined (literally). And a male being female doing all of this was just hillarious to me. I laughed so hard I cryed at times. My female avatar made enemies everywhere I went. It was fun. Until Linden stepped in.

Linden didn't like it and knew what I was doing. I was causing quite a ruckus everywhere I went. I really didn't understand what SL was about, SL was small with about 6 to 10 thousand users at any given time and I was enjoying the escapades of indecency.  So they played a few games with me. And in the end, my avatar was shrunk to the size of a small mushroom and I had been placed in a box with miniature hotels and configuration. Soon after, I followed the path they knew I would and I ended up with a pole in an attic saying dance here. Believe it or not, it's true.

They shut off my access to all the buttons at the bottom of the client. I could not fly, I could not build, the lights went  out (all buttons were dark and could not be used) and the client would do nothing. The ends of the box I was in closed up and I couldn't even get out without logging off. I had no home, I had no virtual space, and I had no clue what all this was about. I couldn't click on anything. So I logged off the account, and called Linden Lab, and closed my account.

I was sent an array of things to be accepted to inventory during this time, and a mess of garbage  in which I complained to Linden Lab about. Things that were just unacceptable to me were sent.

I called Linden Lab and was told to "prove it".  They will never admit to this. You will have to believe what I am saying.

The point being, if you play by the rules, you are in. If you cannot play by the rules, Linden has more power to lock a client and do things than most would imagine. That includes Opensim devs, users, and those trying to make a go at the open source technology end. Maybe it's known, maybe it's not. But, as mentioned, Linden never open sourced the server code, so we will never know. We have a client based reverse engeneered open source program to work with. I don't believe that there was anyone that was involed at the time in Second Life that could have written scripts to do what I had witnessed.

I've learned alot in SL

I've learned of the good, and I've learned of the evil. I've been both good, and I've been not so good in SL. Which is not something I had sought to persue in either one of the directions when I signed up for the account.

I have a computer degree and over 20 years of experience in low level hardware technology and the various "wares'. I've written hardware drivers for some of the earlier computer technology. I was uneducated in how this software and the platform worked, and continue on a daily basis to understand. But I have learned just as we all do as we go.

If we are to create a tool that works, we need to obide by the terms of service to the best of our abilities. That I will agree on. However, Linden is not here to provide open source software. Linden is a hosting provider providing a proprietary platform that we have not seen in the history of computing and to this we should give our respect.

Let's not get our ideas misjudged as we have with Phantom Spear's client functions being shut off for doing the wrong things. Let's provide the tools needed and respect the platform, others rights as content creators, and give an open source solution that works. Second Inventory might work for those that enjoy Microshaft and their ways, but it doesn't mean we shouldn't have an open source software with permission checks that works. I personally cannot stand Second Inventory and their "Microsoftish" attitudes. They took open source and created Microshaft, I prefer to do the opposite. As indeed Linden has personally proven to me that they have more power in their numbers and their wallets than most of us could achieve in a life time, let alone any virtual world.

If you don't write it, someone will. It might just be me. But the tools are needed for those that want to move on.

 

 

What's here... and what is needed..IMO

What we have to this point are a few softwares that I am aware of that help with the copying of data within SL. For both backups and transfering to local or remote machines. Here's my take and/or experience with what we have.

Libomv - Libsecondlife - TestClient

1) Copybot - while it's use, it's code, and it's function were originally to be used for good purpose, it has been used for not so good purposes. Thus Linden made a point to state that it was not acceptable due to the misuse. So, this is no use in it's present form for those that want to pursue this in the proper way as it breaks the Linden Lab  Terms Of Service (TOS).

2) Second Inventory (Copybot with permissions checks) - Windows based proprietary. Bot like client where you log in and create a bot for the purpose of backing up data to local disk or for use with remote servers. You do not login with your usual SL client, you cannot view what you are doing. This software lacks quite a bit in what is really needed. It's made progress over time to where you can backup directories (folders) with it's content, but with large inventory it does take time and is a bit on the "clunky" side. For those that don't mind paying for this code. You'll have to sign up with Second Inventory and have your account tied to the machine. More or less like your hardware is tied to your Microshaft software licenses.

Restoring your work to a local or remote OpenSim grid is not all that difficult in it's process, but the way this software works is nothing as it really should do. All your work is dumped in the middle of the sim and nothing is restored as it would be done with OAR/XML. It does however give you the option to take back the import to inventory.

3) MeerKat Viewer - open source client. Now this is impressive. A client with backup capabilities that I've wanted without the fuss in terms of large build backup on the fly. A whole room, house etc.. You basically select your build and back it up to XML. It's simple, it's easy, and no hassles.

Restoring is just as easy and what's nice is that you are logged into SL or your local/remote server and watching it be placed where it should. It's not a bot client, it's an SL client with permission based backup accessible via the pie menu.It works pretty good and this is really the right direction to go in. However, this client will not backup everything as SI would do at this point. It doesn't grab prim contents, doesn't backup scripts, textures etc... and does have a few quirks of it's own. It's not really an db asset/inventory type of backup as you see with SI, but has potential to do what is needed.

I would certainly prefer to backup from within the SL client and most end users would as well I'm sure. If (or better yet when) MeerKat would have some of the function that SI had in terms of the inventory/folder type scenario coupled with allowing for emeded objects, scripts, textures and anims to be backed up.. We wouldn't even be looking any further for what we need in a tool.

But at this point, the items need be rezzed before being backed up to xml, you cannot backup from inventory with MeerKat. At least not that I am aware of.

Looking for a solution that works for everyone is not an easy task. You have those that want open source code, you have the proprietary naysayers. But in all reality, the answer to the question is to have both. Just as both are needed.

Last but not least.... Large prims (megaprims) need to be backed up no matter whom created it in SL. People build large builds using these prims to save both time and ... well... prims. So we need to be sure that the large prims can be backed up and restored to local/remote servers. Owner checks in this case.

 

Classless

as par normal, the emotional tangents seem to target what i'm sure most of you reading the issue should abide by in your every day lives. we all have masters. we all have decisions that can and do impact others in greater or lesser degrees depending on our output. let's say, instead of Prok's analogy, we're all software developers of one of the most extraordinarily revolutionary communications platform of the century. that means everyone. not just the lowly coder working in her singular cubicle.

as she insinuated, or at least how i understood her, there is no judgement in her appelations. sure, you can put a negative spin on on it, you have your own minds, but how i took it is probably in a much more naive and (yikes!) positive light. yes, i still hold out hope for humanity. :-) i saw in it that Open Source coders (and subsequent guinea pigs of said software: users) are, or should, be working in a symbiotic relationship. if you have a good relationship with your coder, your world's a much nicer place. so it is with Rezzable's product. we must all thank RaR for hopefully reflecting on just how he is to provide us with this much needed tool. we all get that. how it's brought to the world is the question.

however we move the rock up the mountain (see? i'm building community) we all have our place. some high, some not so much. and i firmly believe that Open Source is the way to go. however, if there is not an organized coordinated development complete with QA, testing, documentation, consultation, etc it's subject to abuse. critical analysis doesn't have to be reactionary.

the most brilliant coder who may be the goto girl in complicated computations doesn't necessarily have to assume a position which provides any direction for the program. i'll do what i'm told. just pass it through the authorization reporting flow channels. some of us just don't want to deal with the super heavy political reverbs. i guess we should add a public relations position in there too, haha. each having no idea what the other is doing? no, i said i'm a positive thinker. i'd prefer everyone have that master who we can look up to in coordinating all the various duties. as brilliant as any of us might be, we are "merely" coders or some symbiotic element thereof. knowing and respecting everyone's bit (it just won't compile without it) is the high note i'm hoping RaR can assume. still a mechanic, cause we all are, but somehow given a role, and a very public one, that burns if he gets it wrong. let's hope he gets it right. more power to him. i've admired his builds. he's commanded a great amount of respect for those. but right or wrong, it's his responsibility.

thank you Ciaran for the off

thank you Ciaran for the off topic ad hominem attack. as far as i know (you can put out some extra effort and provide the links you refer to, thank you) LL's policy on initiating the Openspaces has always been up front and well understood to those doing even a limited amount of research. if your tangent is to diminish MY opinion of RaR's juvenile "blaming" LL for his own emotional responses i'd prefer RaR do that directly. perhaps further reading of RaR's opinions (jumping off the page into some other people's faces here) would adjust your adoration of He Who Can Do No Wrong. "None of this would be an issue if..." is merely another nail on the coffin called the blame game. of course, black being white, that might be one of his greatest qualities for you.

Well this was weird and disapointing

I dont know exactly what happened here, but what ever it was started off looking usefull and turned into something strange...

No tool for backing stuff up, no opensource anything, and all around no fun. I fail to see the point of all the yelling and screaming, although there were funny bits here and there thats about all the substance there was, a tiny bit of humor in a large scale pile of... something unresolved I guess.

I hope what ever happened here someone learned something from it, some how I dought anyone did.

And to the very very few people who made me laugh in this whole thing, THANKS! Have a Cookie!

As for the rest of you, well, you get to live with your selves and thats enough for me.

 

 

 

Seems like we have had enuff

Seems like we have had enuff comments by now. I am closing comments here. If anyone would like to make blog post about a related topic (or even a totally random one) pls drop me an email at rar@rezzable.com or use our contact form. But if you want to spew some diatribe, go elsewhere to vent.

Thanks to everyone for posting. Lots of interesting points raised.  I have learned many things in this and we will try to find a good solution reflecting the concerns at hand. 

The biggest open question still remains though--how can you thrive  in making digital content when it can be copied by your customers, competitors and rippers.