Oz Linden

  • Content count

  • Joined

  • Last visited

  • Days Won


Oz Linden last won the day on April 25

Oz Linden had the most liked content!

Community Reputation

295 Excellent


About Oz Linden

  • Rank
    Advanced Member
  1. Thoughts on the Town Hall meeting?

    Darn... Penny is onto us...
  2. Thoughts on the Town Hall meeting?

    Ok... normally I'm happy to just listen to you all speculate about the silliest things (you often come up with good ideas I can steal that way), but this has consumed way way too much of the speculation space. We will not restrict the ability of Basic accounts to rez.
  3. We're always on the lookout for ways to do that. There are a couple of project proposals in our backlog to look at some possibilities, but I can't offer anything like a timeline.
  4. Improved region crossings is one of our active projects right now; it may take a little time to get out to most of the grid, but we've got some promising-looking changes coming.
  5. Yes, we'll continue to add to LSL. llName2Key is being tested now on parts of the Beta grid. Permanent storage is already available for scripts that are part of an Experience. Most likely, really powerful new additions (anything that imposes a significant cost to provide or that has high griefing potential) will also require an Experience. Bigger scripts are a personal favorite feature of mine... but I can't be sure when we'll be able to get them on the roadmap.
  6. That is usually the result of one of a couple of bugs in media handling, but a request that any sounds at all from outside the parcel would make a good Feature Request.
  7. I would personally love to do two-factor authentication. At the moment we've got some architectural challenges that we've got to work through to make that possible, but we're working on them. I hope that when we do it that most people will use it.
  8. Open Source... we continue to solicit features and fixes from open source developers, and don't plan to stop. Sansar tech back to SL... the way the two are built are pretty different, so bringing improvements from one to the other is usually more a case of reimplementing than just copying. We did recently poach an ex-SL Sansar developer to come back, and he brought some pretty cool rendering ideas back with him... High hardware demands vs user hardware... well, we're just trying to be really clever about it. We're committed to supporting as wide a range of hardware as we can, but getting a good video card and a lot of memory are certainly good ideas. What SL content are we surprised hasn't been created ... I expect that if I named any, someone would point out that we've had it for years (I know - it's happened many times).
  9. There are not at the moment, but it's a Feature Request we might do - please submit it.
  10. That would make a good Feature Request jira (and one we could probably do without too much trouble).
  11. We'd like to fix that. We've got some simulator changes in the development pipeline now that might help, but they're not quite ready for testing. In any event, they probably are not a complete solution, but we'll try to keep at it.
  12. Adding substantial data structure support to LSL at this point isn't a very high priority; I think we've got ample existence proof that people can do pretty amazing things without out them. That having been said, there are other things we'd like to do to make LSL more powerful, but other than a few new functions we don't have anything big on the road map for this year. Access to Avatar Complexity would be relatively easy - please file a Feature Request. Some support for redelivery is among the things we'd like to do for Marketplace - we're trying to hire a developer for that - tell your friends.
  13. I'd be interested in hearing what specific changes would make a "real" first person mode. Submit them as Feature Requests in Jira, please. We're working on a number of improvements that we are optimistic will improve framerate for most users. I'm not familiar with "vector copy" - another good candidate for a Feature Request. The chat window does support "compact" mode, and can also be set to be largely transparent. Moving it (and other floaters) outside the main viewer frame is something we've discussed many times. It's a big job; while we have some ideas on how to do it, at the moment it would mean not doing a great many other things. We'll try to get to it eventually though.
  14. I'm not sure I buy the 95% number, given how many people run it... but in any event, we have an active effort working with open source developers to bring the Linux viewer up to date. Grid scope experiences are on the road map for this year. Unless we are very very close, we prefer not to set expectations for release dates of anything - SL is so large and complex, and the number of unexpected events that can occupy developers for a time so large, that we have not found that we can accurately predict very far in advance.
  15. Cap invocation rate exceeded?

    At present, there's no way to read any HTTP headers from an http_response event. The header value is useful if your request is from an outside web request, though. The throttle allows many requests per second (no, I won't tell you exactly how many because it may change and we don't want people trying to see if they can get in just under the limit) to the scripts owned by the same owner in the same region. A good general strategy is to wait a few seconds (possibly with a little randomness added in) before retrying, and if that fails increase how long you wait by multiplying by a small number before retrying again. If all your requestors follow some method like this, eventually they'll get through.