SL Policy

Oz Answers TPV Policy Questions

by

Innula Zenovka post a link on SLUniverse to an Question and Answers page where Oz Linden answered residents questions about the new TPV Policy. Cummere Mayo start the thread here.

See: Questions about new TPV policy. (Questions only please.)

The most controlversal and misunderstood part of the policy is the idea of what is meant by SHARED EXPERIENCE. So, the number one question is: What is meant by shared experience?

The pertinent part of Oz’s answer is:

A shared experience change is one that modifies the definition of the elements that make up the virtual world, or how they behave, in such a way that users on other viewers don’t experience the same virtual reality.

This rule does not affect changes to rendering, user interface, or the controls a viewer offers for interacting with the world.

Read more

#SL Viewer Policy Change Meeting

by

An audio recording of the Third Party Viewer (TPV) Developers’ meeting where the Viewer Policy Changes were announced prior to the blog posting of them has made it to the net. The audio is about 2 hours long. The following is my summary of it. I was mostly interesting in the policy changes. I’ve tried to convey the meaning of statements accurately. I don’t quote but paraphrase.

You can use the time marks to find the related items. I’m not sure how well the Windows Media Player handed the time marks. Once I started moving back and forth through the recording, I think they messed up. But, I’m not going to spend two hours checking them. Also toward the end I was burning out and the discussion was less interesting for me.

You can find the original recording here: TPV Dev’s Meeting 2012-02-24.

I know the main speaker is a Linden. I’m just not sure which one. I am guessing  Oz Linden. He leads the Open Source group and some references within the recording suggest it is Oz. But, I’m not certain. So, I’ve used (? Linden) as the name in the following text. Whoever it is, they do an excellent job of facilitating the meeting.

Read more

Pages: 1 2 3 4 5 6

#SL Viewer Policy Follow Up

by

A part of the Server/Sim/Scripting User Group meeting was taken up with discussion of the viewer policy changes. It seems some of the changes have been in the works for some time. Now that they are on the verge of being implemented the Lab made the public announcement.

Viewer Identification Tags

Tankmaster Finesmith said, “So, as one of the [Firestorm] TPV devs, we’ve know for a few months now that LL has wanted to brake the viewer tags. Today [Friday] we got word that LL will be braking them next week.”

So, Jessica is right, the viewer type ID tags will be turned off next Tuesday and Wednesday. Presumably the code to do that has already made it through QA process.

Simon Linden was the meeting chairperson or facilitor and I’ll quote him several times so I think this statement is important as a framework. He said, “…I’d like to preemptively explain that I’m a coder working on the server, so I’ve mostly been out of this loop. I’m not a lawyer, from marketing or product, etc. etc.” I suppose that means we need to keep what he says in some sort of perspective.

Read more

#SL Viewer Shock Wave

by

I saw today that Linden Lab has announced revisions to their Third Party Viewer policy. The Firestorm/Phoenix tema has already posted a reaction. They are also planning to discuss the changes at their next Phoenix Hour, planned for Feb. 28 at 2 PM SLT/PST.

I think Jessica phrases their take on the meaning of the changes in a pessimistic take. However, she may well be right. It is hard to know. You can read her take on the changes on the Firestorm/Phoenix blog. See: New additions to the Third Party Viewer Policy.

You can see the policy change announcement here: Third Party Viewer Policy Changes.

These changes, if intended as Jessica takes them, will be explosive. I see the changes impacting Firestorm and other viewer negatively. Exodus and Nirans viewers may become ineligible to connect to the grid. If so, I’m sure this will create a massive amount of blow back.

Read more