Jump to content

Oz Linden

Lindens
  • Content Count

    241
  • Joined

  • Days Won

    1

Everything posted by Oz Linden

  1. One point we'd like to correct: Moving to the cloud does not necessarily mean that we would stop running regions without avatars in them. For the time being at least, our goal is to run SL and its regions just as we do now - full time, with a substantially similar schedule for when and how they are upgraded. Doing otherwise could, as some have correctly pointed out here, introduce problems with backwards compatibility and mobility. Whether or not we will also be able to create new land products that are not always running, how to decide when they run and when they don't, and what the pricing might be for such offerings are among the things we've had discussions around internally, but not made any decisions about yet. The cloud will broaden what we might do in this and a number of other exciting ways, and we look forward to exploring them, but that will happen only after we've gotten the current service uplifted.
  2. That version of the post would make a great New Feature Request: Log in to jira.secondlife.com with your SL account Pick Create Issue (near the top right) Change the issue type from 'Bug' to 'New Feature Request' Put that nice clear description into the issue We really do read all of those, and we act on a lot of them.
  3. http://wiki.secondlife.com/wiki/Linden_Lab_Official:Alternate_Viewers#Second_Life_Release_Channel Try the Voice viewer at that URL; it has helped many people with connection problems.
  4. What problem are you trying to solve? If a login fails because the region is full, you can just select another location and try again... and Alwin is correct that you can set a preference to show your favorite locations as a menu on the login screen (that's in the LInden viewer too, Alwin)
  5. Animations are allowed to make small changes in position - otherwise dances would be pretty limited, for example. I rather like an animation that makes my avatar sit in a lotus position a few feet above the ground, for example, but as far as the simulator is concerned, I have not moved. Deliberately obnoxious people will sometimes use this to make it appear that they have entered land from which they are banned; if they're still within 10 meters of the edge, they haven't really crossed the boundary, they're just using an animation that displaces their appearance over it. Granted, on a small enough parcel that can still be annoying, but like much of Second Life that's a compromise between conflicting legitimate needs.
  6. When the microphone is greyed out and you don't have a voice dot over your head, it means that you're not connected to the voice service. Assuming you're at a place where voice is allowed, that usually means some problem with the network between you and the voice service (which is different than between you and the simulator). It often works to just disable and re-enable voice in your preferences (for voice purposes that's the same as logging out and logging back in, but is much quicker). We have been working on voice connection issues, and have a Release Candidate viewer that has some fixes that many people have found improve reliability: http://wiki.secondlife.com/wiki/Linden_Lab_Official:Alternate_Viewers
  7. That restriction is deliberate, and if there are ways to circumvent it they are bugs. Note that when you displace your avatar with an animation, all you are doing is moving where the avatar is drawn in the viewer. The simulator doesn't process animations, it just passes the animation id to any viewer that can see you; it has no idea what the animation is doing; you're not really moving the position of the avatar as far as the simulator is concerned. This sometimes leads to some odd effects.
  8. any 10.* address is a private address of some kind - it is one of the address ranges reserved for private use, and is not routable on the public internet. You may be able to find what is failing by looking in your viewer log file. See finding your log file. If you find out what it is, file a bug.
  9. Port 80 is the standard port for HTTP. It could be any number of things. Since that address is your VPN address for something rather than the real address, there's no way to know what it is.
  10. There are some previous builds that on some Windows versions may produce this error ... sorry, we think it won't happen updating from this new one to whatever comes next... Please download and install from http://wiki.secondlife.com/wiki/Linden_Lab_Official:Alternate_Viewers#Second_Life_Release_Channel [edit] To be a little more clear... the Error 22 problem is actually a bug in the update code of the older build that happens on some Windows systems, not a bug in the new build. We put a lot of effort into trying to ensure that the updater is solid before we put out a viewer precisely to avoid this kind of problem, but this one got by us - Sorry. Manually installing the new build won't crash (at least not for that reason ). As of this writing, we've had about a thousand users upgrade successfully (one way or another), and while the number of users and sessions is way too small to be a valid test, the very early numbers show a much lower crash rate than before (and lower than the default build).
  11. Your timing in asking this is very good. We're in the process of testing a form for this on LindenLab.com now; it should be available quite soon. It really isn't because we wanted to make it harder, we've just been focused on other things.
  12. For the time being at least, I don't have a solution to suggest. We have a lot of simulator hosts, and they come and go very frequently. I'm not aware of a certificate authority that provides the availability and scale we would need at a cost we could afford to provide a server certificate for each simulator host (if you find one, by all means, file a Feature Request... we'll look at it). Using wildcard certificates would seem to me to be a solution that's less secure than the problem. In the long run, I'm sure that either we'll find a way or services like SNS will allow you to provide trusted root CAs to add to their built-in list, but at present that's not something I can make any predictions about.
  13. They are not self-signed certificates. They are signed by the Linden Lab Certificate Authority, the public certificate for which is available at https://bitbucket.org/lindenlab/llca/raw/tip/LindenLab.crt you should be able to install that certificate to provide robust authentication of the script request. We do not currently have any plans to change that.
  14. We have a release candidate viewer available that improves the retries when connecting to the voice service - it may well be much better for you, especially if the problem is in something about the network you're passing through to get there. It also has other improvements to voice quality and security. Go to the Alternate Viewers page and download the Second Life Voice Viewer. Release Candidate viewers are ones that we believe are ready for general use and are making available to test that belief. Eventually, they become the default viewer.
  15. We are continuing to update the reliability and stability of the LSL HTTP functionality in LSL. The latest changes involve validating the MIME type values: The HTTP_MIMETYPE parameter to llHTTPRequest is checked. LSL will validate these for proper format; requests that attempt to send an improperly formatted type will send a debug channel error, not send the request, and return a null request key. If you use the new HTTP_ACCEPT option to llHTTPRequest (which allows you to further restrict the type your script expects), the Content-Type of the response is checked to see that it matches your restriction; if it does not, the http_response event will be a 415 error and the body will be "Unsupported or unknown Content-Type". Incoming HTTP requests to a script check to see if the Content-Type in the request is formatted correctly and that it is an allowed type (it always checked for allowed types). Previously, it was possible to send a type that was syntactically invalid but matched an allowed wildcard type. Incoming parameters are not validated. If an incoming request has an improperly formatted or unacceptable MIME type, LSL responds with a 415 error response and no event is generated for the script. Valid MIME type format looks like “type/subtype; parameters” (the semicolon and parameters may be omitted). LSL does not validate the content of the optional parameter section. Testing Your Scripts We have made simulators implementing these checks available; regions where you can test your scripts are listed below. Please do so as soon as possible and make any required changes. Agni regions: Magnum Sandbox 1 Magnum Sandbox 2 Magnum Sandbox 3 Aditi regions: Bonifacio Sandbox Artifex Examples Some examples of valid calls to llHTTPRequest include: key my_key; my_key = llHTTPRequest( “http://www.mywebsite.com/”, [ HTTP_METHOD, “POST”, HTTP_MIMETYPE, “text/plain;charset-utf8” ], “my body” ); key my_key; my_key = llHTTPRequest( “http://www.mywebsite.com/”, [ HTTP_METHOD, “POST”, HTTP_MIMETYPE, “application/x-www-form-urlencoded” ], “body=stuff” ); key my_key; my_key = llHTTPRequest( “http://www.mywebsite.com/”, [ HTTP_METHOD, “POST”, HTTP_MIMETYPE, "multipart/mixed; boundary=\"---1234567890---\"" ], “The body as multipart” ); NOTE WELL: Calls similar to the following will now be errors; they will trigger a debug error and return a Null key from llHTTPRequest. The invalid values in these examples did not trigger errors before (they probably would have caused problems on some web servers). key my_key; my_key = llHTTPRequest( “http://www.mywebsite.com/”, [ HTTP_METHOD, “POST”, HTTP_MIMETYPE, "text/application/xml” ], “my body” ); The value for HTTP_MIMETYPE has too many sections (more than one '/'); it does not follow the type/subtype pattern. Values like this one used to be on the wiki page for llHTTPRequest; they were never valid but were not checked. key my_key; my_key = llHTTPRequest( “http://www.mywebsite.com/”, [ HTTP_METHOD, “POST”, HTTP_MIMETYPE, "text/xmll charset=utf8” ], “my body” ); No semicolon after the mime type. key my_key; my_key = llHTTPRequest( “http://www.mywebsite.com/”, [ HTTP_METHOD, “POST”, HTTP_MIMETYPE, "text / xml” ], “my body” ); The value for HTTP_MIMETYPE includes spaces in the type/subtype section. key my_key; my_key = llHTTPRequest( “http://www.mywebsite.com/”, [ HTTP_METHOD, “POST”, HTTP_MIMETYPE, "text/xml\n” ], “my body” ); The value for HTTP_MIMETYPE includes a control character (A newline.) We'll be watching this thread and will try to clarify any questions or problems you encounter. Go forth and test please!
  16. Please file a Jira with the specifics for your LSL script and server.
  17. The User-Agent value identifies the HTTP client, not the host (there is a 'Server' header that identifies the server). It's rarely true that you need to manipulate the user agent value unless the server you're accessing limits or modifies responses based on it. Please do not execute a request periodically just to keep a connection open... you're consuming simulator resources. Opening a connection is pretty inexpensive.
  18. Please file a Jira on this one. Be sure to include where it is happening and an object that demonstrates the problem. We certainly didn't do anything like that on purpose, so it will take some work to figure it out but we need more specific information to start.
  19. I added the note above to the original post. Sorry that caused problems for a few services; I made the change because when we added the ability to append your own User-Agent values, we included checks on valid syntax and since our own value would not have passed that check, I thought it only fair to correct it. Perhaps that wasn't the best tradeoff, but now that it's done we won't change it again.
  20. That looks right ... what is the value of nPlayingURL ? Do you get an error message?
  21. I think you underestimate the ability of SL Residents to adapt. For some history of why we made this change, see my posts in https://community.secondlife.com/forums/topic/406941-dj-board-display-not-working-properly/ I regret that it wasn't reasonable to make an automatic adjustment in the simulator to correct this, but sometimes that's the way it works out. We try to keep disruptions like this to a minimum, and I'm making a special effort on this one to reach out to the authors of scripts that are affected. Frankly my biggest regret is that the URL hack was not noticed long ago and a better solution (like the current one) provided then (well before my time, but that's an imperfect excuse) - it should never have worked and it's surprising to me that it ever did. Software surprises you that way sometimes. We have a couple of other improvements to llHTTPRequest in the pipeline (ones that won't break anything); watch this thread for announcements when they're available for testing.
  22. In the latest main channel simulator version (2017-07-11T22:13:46.327548), we deployed some updates that changed the llHttpRequest call. These were made necessary by updates to some of the underlying HTTP libraries we use, and are intended to make HTTP use from LSL easier to debug and more robust, but in a few cases they have broken some existing scripts. This note is intended to summarize the changes and provide guidance on how to update your scripts. URLs The most important change, and the one that seems to be responsible for most of the problems that have been reported, is in the handling of the URL parameter. In previous versions, the URL was not checked, and some scripts had done things that shouldn't have worked (and now they don't): Control characters in the URL. Specifically, this has usually been newline characters. There were widely used hacks that inserted newlines in order to get around restrictions on the use of some headers, and those hacks also truncated other important headers that the simulator inserts in all requests. This will now produce a run time error without sending the request. The fix is to remove the newlines and any additional headers they were inserting; if it was the User-Agent header, there is a new parameter you can use to provide a value for that header. Spaces in the URL. Space characters are not allowed in URLs, but because many scripts insert them, we have put in special handling to convert them to a %20 in most cases. If your script is passing values returned from other LSL calls that may return spaces, you should do the replacement before putting them into the URL, like: string URL = "http://example.com/path?region=" + llEscapeURL(llGetRegionName()) depending on how your server works, you may need to substitute a plus sign ('+') for the spaces in parameter values rather than the '%20'. Header Value Changes We added a new HTTP_USER_AGENT parameter that lets you append to the User-Agent header value; in some cases, servers look for key words in this header. We made requests shorter by sending one long Accept header with all the allowed MIME types rather than many headers with one each. This made requests shorter and more compatible with more servers. As far as we know it has not caused any problems. The default User-Agent header server token value was changed from 'Second Life LSL' to 'Second-Life-LSL'; this appears to have caused problems for some servers that were checking for it. Problems If you are having problems with these changes, you may reply on this thread or file a JIRA and we'll make an effort to help you. Please include the part of the script that is making the call to llHTTPRequest and the values that are being passed to it, and describe any errors you are getting on the Debug chat channel or from your web server.
  23. The 'ping' value on the status bar cannot be compared to the times for a traceroute or ping command; it's an entirely different mechanism with quite different performance. The viewer displays the times for application messages that are processed by the simulator; those other commands display times for network packets that are handled at a much lower level and so are normally significantly faster. The login servers are separate from the simulators. To measure connectivity to login, the name to test is login.agni.lindenlab.com (which is really any one of many redundant servers). With as little as there is in your post to go on, it's impossible to guess what your problem might be but we monitor the responsiveness of login servers very very closely and they are fine, so chances are that the problem is either something in your system or in the network between you and the server.
×
×
  • Create New...